Quote:
Device Boot Start End Blocks ID System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 14 9964 79931407+ 8e Linux LVM
cat /boot/grub/grub.conf returns
No such file or directory
cat /etc/fstab returns
No such file or directory
Sounds like the disk is done for!
|
Actually, that's quite good... last two commands didn't work because the fs on the partitions haven't been
mounted yet.
Looks like hda1 is your boot partition and hda2 is an LVM volume holding the root partition.
Check the physical integrity of the drives: memtest86
Check the filesystems:
Testing the boot partition is easy:
# fsck /dev/hda1
... with any luck, it is the boot partition that has the missing journal.
Restore the journal to the boot partition as follows:
# tune2fs /dev/hda1 -O has_journal
I don't think so though: your error messages suggest that it is the logical volume that is missing a journal.
Testing the logical volume:
# vgscan
# vgchange -ay
# fsck /dev/VolGroup00/LogVol00
With any luck, this is possible:
# tune2fs /dev/VolGroup00/LogVol00 -O has_journal
... assuming the journal is the problem.
To examine the files, you need to mount the filesystems... as follows:
# mount /dev/VolGroup00/LogVol00 /mnt
# mount /dev/hda1 /mnt/boot
# chroot /mnt
# cat /boot/grub/grub.conf
# cat /etc/fstab
This will help you understand the layout.
Hopefully all that has fixed the problem someplace, and you can reboot normally.
Quote:
I tried to follow the procedure the guy outlined in the link you recommended where I do the linux rescue and kill the machine to try and force the machine to ask for a disk check on reboot but I was never prompted to do a disk check.
|
Ahhh... well... just as well I talked you through the above ain't it? Did you remember to boot from HDD the second time?