toddbooster
6th May 2004, 11:56 AM
So, here's abit of a wierd thing...
Evertime my computer boots, the splash screen switches to show details just as it is setting up local disks. This behaviour is of course normal if there is an error on start-up, but in my case there is no error displayed of any kind.
dmesg shows nothing (that I can see) and the only error in my boot.log is mdmpd at the very end (i don't even think I know what a multi-path device is).
Pressing alt+ctrl+F1 during interactive startup did however reveal an LVM error:
Setting up Logical Volume Management: No Logical Volumes present.
Scanning all local disks, this may take a while... FAILED
(This may not be the exact syntax, I'm at work and can't quite remeber exactly but if anyone needs to know, I can find out).
This never happened with the 2.6.3 kernel from test 1 and test 2. As far as i can tell it first appeared with an update to kernel 2.6.5 for Test 2 and has been happening ever since.
I don't know if this is a bug or just some stupid configuration error on my part. Any enlightening advice would be greatly appreciated.
Evertime my computer boots, the splash screen switches to show details just as it is setting up local disks. This behaviour is of course normal if there is an error on start-up, but in my case there is no error displayed of any kind.
dmesg shows nothing (that I can see) and the only error in my boot.log is mdmpd at the very end (i don't even think I know what a multi-path device is).
Pressing alt+ctrl+F1 during interactive startup did however reveal an LVM error:
Setting up Logical Volume Management: No Logical Volumes present.
Scanning all local disks, this may take a while... FAILED
(This may not be the exact syntax, I'm at work and can't quite remeber exactly but if anyone needs to know, I can find out).
This never happened with the 2.6.3 kernel from test 1 and test 2. As far as i can tell it first appeared with an update to kernel 2.6.5 for Test 2 and has been happening ever since.
I don't know if this is a bug or just some stupid configuration error on my part. Any enlightening advice would be greatly appreciated.
