On Tue, Dec 1, 2020 at 1:38 PM Tom Horsley <horsley1953@xxxxxxxxx> wrote: > > On Tue, 1 Dec 2020 13:33:22 -0700 > Chris Murphy wrote: > > > Yep. For sure the kernel is what's responsible for reading the > > partition table. And that alone would cause a spin up. e.g. > > But why would it need to scan when it is shutting down the > system (which is my case :-). Ohhhh. Yeah. Hmm. Not sure. You could set both 'systemd.log_level=debug udev.log_priority=debug' and then boot once and reboot without. Then look at: journalctl -b-1 for clues why that device is being looked at, at all. I don't know if there's some sort of udev tear down of things, I don't know why it would be necessary. But *shrug*. My suspects are systemd because that's responsible for running the fstab generator, so there may be dev units based on the fstab entry that somehow cause this. And also udev. And when does it spin up? Use Esc to see what jobs are running and if spinup happens before the umounts of /home /boot /boot/efi or after that. If it's after that - then it might even be after / goes ro in which case it's not logged. And in that case there's this: https://freedesktop.org/wiki/Software/systemd/Debugging/#index2h1 >I swear it didn't use to do that, > then a few releases ago (probably several releases ago) it > starting hanging on shutdown till the disks spin up. I'm not sure I've noticed one way or another when the drive I have spins up. I just assumed it was the *firmware* that's doing it on UEFI. Not anything to do with Linux. I'll try to pay attention to the NUC next time I do an update and reboot. -- Chris Murphy _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
