You are not logged in.
Hi,
for some time now booting on my machine (64bit) has failed intermittently because dev-mapper couldn't find the LVM volumes on one of my drives. The reason for this turned out to be that there is no device node for that drive. As far as I can tell, it doesn't show up in the logs at all. It is recognized in BIOS without problems. The other two drives are fine. The only "solution" I've found so far is "reboot until it works".
Broken harddrive or something else?
My ship don't crash! She crashes, you crashed her!
Offline
Sounds like a timing issue. Maybe sometimes it tries to setup the device mapper before the module for the disk controller is loaded.
Maybe you could try to add a custom initcpio hook that puts a couple second delay in the bootup before the device mapper hook.
Offline
Good idea. I'll have a look at that. This isn't about my root filesystem, btw., that isn't on lvm but on its own, standard SSD. Aren't LVM hooks only needed for the root FS?
I hate errors that aren't properly reproducible. Change stuff and wait. And if nothing happens, you still don't know if you've fixed it ...
Last edited by lastchancetosee (2013-05-01 08:19:45)
My ship don't crash! She crashes, you crashed her!
Offline
Maybe it helps to remove the LVM hooks, so that the setup of device mapper is executed later, after the initramfs.
Offline
I tried removing the lvm hook, that didn't help. Most of the time the problem is solved by a reboot, which makes me think that it really is a hardware problem, maybe the HD taking a long time to spin up or something like that.
My ship don't crash! She crashes, you crashed her!
Offline