You are not logged in.
Pages: 1
From cold boot (HDD spun down), with the system booting from SSD. Root etc is all on SSD.
As the SSD is functional the boot process starts, and during boot I hear the HDDs spin up and before the spin-up has completed I'd dropped into the emergency shell.
Warm boot and the boot process proceeds to GUI without any issues and the system is happy.
Root filesystem etc aren't on those HDDs, so no idea why it cares if they're spun up or not.
Any suggestions on how to either force the drives to start to spin up quicker (grub?) or make the boot process not halt because it can't see the drives?
As an aside, I've also proven it's the spin-up causing it by removing all the HDDs entirely and booting fine.
Last edited by wingwing (2020-05-01 17:07:33)
Offline
What output is produced when system drops to the emergency shell? If systemd has started at that point what is the contents of the journal for that boot?
If systemd has not started the output of dmesg instead. It may require dumping the output to a filesystem backed by SSD then post its contents from live media if you do not have networking in the emergency shell.
Last edited by loqs (2020-04-30 18:59:13)
Offline
Does your bios have a hard disk spin up delay setting?
Offline
BIOS doesn't have spin control. The drives are hanging off a RAID card (in JBOD mode) but no options in there.
I've just upgraded linux et-al and <sigh> the problem appears to have gone away. So, thank you for the replies and if a future upgrade breaks it I'll have another go.
Offline
Please do not use [closed], as this denotes a locked thread.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Pages: 1