LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Fedora (https://www.linuxquestions.org/questions/fedora-35/)
-   -   How can I tell Fedora to activate a non-standard logical volume during boot? (https://www.linuxquestions.org/questions/fedora-35/how-can-i-tell-fedora-to-activate-a-non-standard-logical-volume-during-boot-419510/)

PTrenholme 02-25-2006 03:49 PM

How can I tell Fedora to activate a non-standard logical volume during boot?
 
I had a disk crash, and installed a new FC4 on a new disk before I figured out how to run fsck on a logical volume. (You have to do it through /dev/mapper since the mapper "exposes" the ext3 file system "hidden" in the logical volume.)

So, O.K., now I had a new FC4 and an old one. But, since they both used the same "logical volume" name, only one could be accessed at a time. So I renamed the new logical volume to FC4_00.

But now I can't boot the new system. When Fedora initialized the logical volumes during the boot, it found both of them, but it only activated VolGroup00, the old volume group.

My grub.conf looks (in part) like this:
Code:

title Old Fedora Core 4 (2.6.15-1.1831)
  root (hd1,1)
  kernel /vmlinuz-2.6.15-1.1831_FC4smp ro root=/dev/VolGroup00/LogVol00 rhgb quiet
  initrd /initrd-2.6.15-1.1831_FC4smp.img
title New Fedora Core 4 (2.6.15-1.1831)
  root (hd1,1)
  kernel /vmlinuz-2.6.15-1.1831_FC4smp ro root=/dev/FC4_00/LogVol00 rhgb quiet
  initrd /initrd-2.6.15-1.1831_FC4smp.img

So, my question is: "How do I tell the boot process to activate FC4_00?" :scratch:

Edit: Oh, I just realized I hadn't described the specific symptom. Because the FC4_00 is not activated, the boot process can't write to /dev, and so it can't create any /dev/tty, thus causing a "kernel panic" and halt. Note that this seems to imply that the root= line in the load command was processed. Just prior to the "panic," there's a message that the mount of root failed with a error 6, and that's preceded by the message I mentioned that LVM found two logical volumes, but activated the wrong one. (Um, all that is seen when the "quiet" option is removed from the 'kernel" line, above.)

PTrenholme 02-26-2006 08:55 AM

Solved it!
 
The problem is that VolGrp00 is hardcoded in the nash init script (inside the initrd...img compressed file. (See this note for details of editing.)

The solution is to remove VolGrp00 from the end of the vgchange line, so nash will "activate" all the volume groups, since the volume group name is optional in the vgchange command. (If you have some groups that you don't want activated, deactivated them in /etc/rc.local later.)

Edit: Fixed URL


All times are GMT -5. The time now is 01:52 AM.