Damien Le Moal <dlemoal@xxxxxxxxxx> writes: > In the hybernate (suspend to disk) case, yes, but not in the suspend > to RAM No; in BOTH cases. In S3, the PSU is shut down and only aux power is maintained to keep the sdram in auto refresh mode. The main power rails that power the disk drives are shut down. The drive can not tell whether suspend to disk or suspend to ram was used. > Depends on the disk implementation. Not all disks put their metadata on media. > So some disks can start replying to commands like IDENTIFY even with > the disks Yes, the standard allows either way and I'm sure that there are both out there, I just thought that the incomplete IDENTIFY because it needs the media case was the more common of the two. At least I think my WD drives do that. > not fully spun up yet. This difference shows up with (sometimes) seeing > "IDENTIFY failed" due to a timeout on resume. I have old drives that are slow to > spinup and show that. But that is handled with the retries with increased > timeouts. I think it would be nice to patch that though, with longer timeout for > IDENTIFY on resume, to avoid these error messages. Isn't the timeout like 10 or 20 seconds and typical spinup times only 3-4? Still, yes, a little longer timeout for the IDENTIFY after resume might be a good idea. > I am not following. What problem are you trying to fix ? I would like my archive disks to PuiS and just remain in standby after a system resume, because I hardly ever access them. Thus it's putting unneccesary wear and tear on them to spin up, then spin right back down every time I system suspend and resume. I suspend/resume my desktop at least once a day, but I can see this being an even larger problem on a NAS that wants to use opportunistic suspend to save power. Just because you say, want to connect to the management web interface, or have a scheduled cron job every hour that forces it to wake up from system suspend does not mean that the disk, or all disks, need to spin up each time. Laptops also tend to system suspend/resume more frequently, it it seems to be becoming at least somewhat common to have a HDD for archive, and an SSD/NVME to run the system on, and the HDD is not likely going to be accessed every time the system suspends and resumes, so why bother spinning it up automatically?
