Timeline for Unreasonable boot time in Pop OS 22.04
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 13 at 15:12 | comment | added | Marcus Müller | @Moltimor these health checks simply don't check the same things as whatever fails. No magic there – the firmware of the drive simply can't try to read everything in self-check, nor can it try all possible combinations of commands and controller firmware state when doing a test. | |
| Jun 13 at 15:05 | comment | added | Moltimor | @MarcusMüller I'm curious about how can everything seems fine in a health check but the disk fails in a real world scenario. Any idea what could be happening in these situations? | |
| Jun 11 at 15:43 | comment | added | Marcus Müller | @oldfred I actually do have a Lexar SSD with the same problem as OP – the SMART equivalent for NVMe is clean as can be. So, don't put too much hopes into that. | |
| Jun 11 at 15:38 | comment | added | oldfred | While not always 100% correct I would check drive with Smart Status. help.ubuntu.com/community/Smartmontools If you have gnome and then gnome-disks, it is in icon in upper right corner. Or install: ubuntuforums.org/… | |
| Jun 11 at 11:18 | history | answered | Marcus Müller | CC BY-SA 4.0 |