https://qa.mandrakesoft.com/show_bug.cgi?id=2305
Product: drakxtools
Component: diskdrake
Summary: System fails to boot after initializing Logical Volume
Management for 2nd time
Version: 9.1-4mdk
Platform: PC
OS/Version: All
Status: UNCONFIRMED
Severity: blocker
Priority: P1
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
I did a fresh install of 9.1 rc1. (I am using LVM on this particular system).
The install went normally (except for the printer problem. I disconnected the
printer first).
At the partitioning section, I selected "use existing partitions", and indicated
to format all but my /home, and /Data partitions.
The disk lay out looks like:
/dev/Rootvg/rootlv 126931 56205 64173 47% /
/dev/Rootvg/Datalv 24802424 3468088 20074408 15% /Data
/dev/hda1 3583944 2613084 970860 73% /Win98
/dev/hdb1 124427 9130 108873 8% /boot
/dev/Rootvg/homelv 4128448 749620 3169116 20% /home
/dev/Rootvg/optlv 2064208 32828 1926524 2% /opt
none 95292 0 95292 0% /dev/shm
/dev/Rootvg/tmplv 126931 4751 115627 4% /tmp
/dev/Rootvg/usrlv 3096336 2301816 637236 79% /usr
/dev/Rootvg/locallv 2064208 32912 1926440 2% /usr/local
/dev/Rootvg/srclv 2064208 226184 1733168 12% /usr/src
/dev/Rootvg/varlv 507748 51027 430507 11% /var
The system booted the first time after the install.
When I tried to re-boot the machine, it failed during boot with:
.
.
Remounting root filesystem in read-write mode [ok]
Setting up Logical Volume Management <- Passes this one!
vgchange -- volume group "Rootvg" already active <- As is should be.
Activating swap partitions:
Finding module dependencies
Starting up RAID devices <- Huh? I don't have any!
Setting up Logical Volume Management: <- Again?!?! This one hangs.
It hangs at the second attempt to load Logical Volume Management. The only way
to get the box back is to re-install it with a different OS.
I've tried this 4 times, with the same result every time. There were no changes
made to the box while it was booted the first time.
Thank you!
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
