Using scheduled suspend and wake-on-lan was a nice idea to save power without manually turning on/off my headless “server”. Unfortunately the SSD does not work on resume in Linux. The HDDs come back fine, are accessible, but the SSD with the OS on throws sense errors - so that makes it a bit useless.

Not a fancy NVMe SSD, which had resume issues for a while. Just a boring Kingston SATA one in a middle-aged Dell Optiplex. Type off stuff that is old enough, but new enough, that it usually works. Oh wells!

Show thread

@dctrud Since the server runs most of what it needs in RAM, do you think it might make more sense to move the OS to the HDD

@brandon the HDDs are 2x3TB in a RAID mirror, and 1x5TB for backup, and all LUKS encrypted so not messing around to swap that about any time soon, as it’d be one of those sliding piece puzzles. I’ll just switch it on and off the manual way until it inevitably starts working in some future kernel. It did resume ok in the past, when it was a desktop with same SSD.

@dctrud Some folks have reported success with a similar environment with `acpiphp.disable=1` in their grub env

@brandon that’s the fix for the common NVMe / PCIe suspend resume issues as the flag disable PCIe hot plug. Unfortunately this is a SATA SSD so no dice.

@brandon it’s all good. Would have been a nice to have WOL, not a disaster for it to not work at present. I spend much of my work time looking into complex file system issues on big HPC parallel file systems, so don’t have much patience to mess with storage things when I’m done with work 😀

Sign in to participate in the conversation

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.