Timeline for "Input/output error" on wake from suspend
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 26 at 9:06 | comment | added | ProgrammingLlama |
Well, I received a Western Digital WDS200T3X0G-EC today, and used dd to clone the data from the Viper VP4000 NVMe to the new drive. Booted into the OS, suspended, and it came right back fully functional as expected. Thank you so much for pointing me in the right direction!
|
|
| Sep 24 at 1:12 | vote | accept | ProgrammingLlama | ||
| Sep 23 at 9:16 | comment | added | ProgrammingLlama | I see. I've tried your proposed solution, and unfortunately it didn't work. The firmware updater says there are no updates available for the NVMe drive, so that's a no go either. I'll leave this open a bit longer to see if anyone else has any suggestions, though I suspect you're probably correct. I think I'll have to try a different NVMe drive while I can still return this one. Thank you for your assistance thus far. | |
| Sep 23 at 9:13 | comment | added | Marcus Müller | yes, this looks like the nvme just doesn't support actual sleep and waking from it accordiing to protocol. I can't say whether the alternatives are better. | |
| Sep 23 at 9:06 | comment | added | ProgrammingLlama | So is this likely to be the actual NVMe device itself at fault, and not a Linux issue per se? I'm still in the returns window for the NVMe (a Viper VP4000 Mini 2TB), so I could probably send it back and replace it with something else. Would NVMes from Crucial or WD be better, if you know? | |
| Sep 23 at 8:55 | history | answered | Marcus Müller | CC BY-SA 4.0 |