Jack Schneider wrote: > It booted to the correct grub menu then to Busy Box. I am thinking it > goes to BB because it can't find /var and or /usr on the md1/sda5 LVM > partition. Very likely. > I checked /proc/mdstat and lo & behold there was md1:active > with correct partitions and md0: active also correct partitions... That is good news to hear. Becuase it should mean that all of your data is okay on those disks. That is always a comfort to know. > So here I sit with a root prompt from Busy Box.... I checked mdadm > --examine for all known partitions and mdadm --detail /mdo & /md1 > and all seems normal and correct. No Errors. Yeah! :-) > Both /etc/fstab and /etc/mtab show entries for /dev/md126.. > What the ... ? That does seem strange. Could the tool you used previously have edited that file? You said you were using /dev/md1 as an lvm volume for /var, /home, swap and other. As I read this it means you would only have /dev/md0 for /boot in your /etc/fstab. Right? Something like this from my system: /dev/md0 /boot ext2 defaults 0 2 You /var, /home and swap would use the lvm, right? So from my system I have the following: /dev/mapper/v1-var /var ext3 defaults 0 2 /dev/mapper/v1-home /home ext3 defaults 0 2 Those don't mention /dev/md1 (which showed up for you as /dev/md126) at all. They would only show up in the volume group display. If you are seeing /dev/md126 in /etc/fstab then it is conflicting information. You will have to sort out the information conflict. Do you really have LVM in there? Certainly if the "/dev/md0 /boot" boot line is incorrect then you should correct it. Edit the file and fix it. If your filesystem is mounted read-only at that point you will need to remount it read-write. mount -n -o remount,rw / Bob
Attachment:
signature.asc
Description: Digital signature