antonio montagnani wrote: > 2007/7/25, Mikkel L. Ellertson <mikkel@xxxxxxxxxxxxxxxx>: >> >> If the partitions are all there, then the next step is to check the >> partitions. You can run fschk on the /boot partition to see if it is >> correct. If you are using lvm, then checking the other partitions >> gets a bit more complicated. Because you can still read /boot, I >> would read /boot/grub/grub.conf and see what volume group the root >> partition is on. You should see something like: >> >> title Fedora Core (2.6.20-1.2962.fc6) >> root (hd0,0) >> kernel /vmlinuz-2.6.20-1.2962.fc6 ro >> root=/dev/VolGroup00/LogVol00 rhgb quiet >> >> This tells me that the root file system is on Volume Group 0, >> Logical Volume 0, so I know that there is at least one Volume Group, >> and it has at least one Logical Volume. I also know their names. >> >> I am not that good with lvm yet, so I usually work with the LVM man >> pages open in one VT, and work in the other to diagnose the >> problems. Hopefully someone that is better with LVM will post how to >> check/repair LVM problems. If not, and you determine that it is a >> LVM problem, I will do my best to walk you through it... >> >> I have found the SystemRescue CD handy for doing this type of work... >> >> http://www.sysresccd.org/Main_Page >> >> > Dispositivo Boot Start End Blocks Id System > /dev/sdb1 * 1 13 104391 83 Linux > /dev/sdb2 14 19457 156183930 8e Linux LVM > [root@Casa ~]# > and then??? tnx for help... (any way I am learning, but I have all > backups !!) > From another message, I see that you ran fsck on /dev/sdb1, so I would run something like this: mkdir /mnt/tmp mount /dev/sdb1 /mnt/tmp cat /mnt/tmp/grub/grub.conf This should get you the volume Group and Logical Volume for the root directory. Hopefully, you are not using another Linux system that uses LVM, and has the same Volume Group name. (This is why I like to boot from a live CD for doing this.) You can also get the information by running pvscan. If you do NOT have conflicting Volume Groupe names, you can try running vgmknodes to create the device files necessary to access the Logical Volumes. You can then try running fsck on the Logical Volumes, and hopefully fix them. If vgmknodes does not work, then you will have to try dmsetup. (It has been a while sense I have done this, and I am a bit hazy about all the details - sorry.) For future use, you may want to look at the vgcfgbackup and vgcfgrestore that will let you backup and restore the configuration information for the drive. If you store a backup copy in /boot, or on a removable media, it makes working with the Volume Group a lot easier. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup!
Attachment:
signature.asc
Description: OpenPGP digital signature
