Hello Everyone,
I performed an in place upgrade from Leap 42.3 to 15. I have a dual boot system, with Windows 10 on separate physical drive. When booting into Leap, the boot process pauses, with the following message:
****] A start job is running for dev-sda2.device (1m /1m30s)
After a 1m30s count pause, the following is displayed:
Depend Dependency failed for resume of hibernation using device dev/sda2
The system then proceeds with the booting process.
sda is my Windows drive, but when I go into the YaST partitioner I don’t see dev/sda2 listed, only dev/sda1.
Anyone have any insight and or suggestions about this?
I have read here in several threads that Windows will not shutdown propperly by default, but will do a sort of hibernate and thus leave disks in a unusable state for other OSs in a multi-boot environment. To prevent thus fast boot must be switched off.
Device Start End Sectors Size Type
/dev/sdb1 2048 208895 206848 101M EFI System
/dev/sdb2 208896 37961727 37752832 18G Microsoft basic data
/dev/sdb3 37961728 289619967 251658240 120G Microsoft basic data
/dev/sdb4 289619968 1953523711 1663903744 793.4G Microsoft basic data
Device Start End Sectors Size Type
/dev/sdc1 2048 923647 921600 450M Windows recovery environment
/dev/sdc2 923648 1128447 204800 100M EFI System
/dev/sdc3 1128448 1161215 32768 16M Microsoft reserved
/dev/sdc4 1161216 1953523711 1952362496 931G Microsoft basic data
OK, I went into UEFI utility and checked my boot options. fastboot was already disabled. While I was in there I disabled secure boot, but made no difference.
The “resume=” parameter is the hibernation image. Normally, this is the same as the swap partition.
The problem with using “/dev/sda2”, is that the device name can change depending on what hardware is plugged in. So referencing the swap partition by UUID is safer.
I got that UUID from your listing of “/etc/fstab”, though it was hard to read (seems to have been all wrapped into one long line).