Kernel Panic. (linux server crash)

[sjaxso]

My server is kaput. It runs Linux, Fedora Core 5, 64 bit. It has two SATA drives, which it puts into one big virtual drive.
When I got to work today after the weekend, it was dead. It hasn't gone down in 18 months, but it was locked up. So I rebooted, and it says :

2 Logical Volumes now active
VF: Can't find ext3 filesystem on dev dm-0
mount: error mounting /dev/root on /sysroot as ext3: Invalid argument
--
Kernel panic - not synching: Attempted to kill init!


My entire business is on there. When if first set up Fedora, I intended to have one big drive for data, and the OS on the other drive. I do that with Windows too, at home. But through the install process, it persuaded me to do this large volume group. I don't know what has happened. It's stuffed.

I have rescue disks - partition managers see the partitions, but won't do anything with them, because they are ext3.

My next plan is to put another drive in, and install a fresh OS and spend two months (probably) reconfiguring everything, and hope my data is still there on the current disks. That's the only thing I can see to do.

Oh yeah, please don't tell me what a twat I am for not backing up, I know: I was going to do it manana. Honest.

[sjaxso]

OK, cool. I picked up ubuntu from the cover of a magazine and it runs as a live CD... This is where I'm at:


I have two SATA disks set up as a logical volume - VolGroup00. I came in one morning and it was locked up - I rebooted and got a kernel panic, couldn't find the filesystem:
____
2 Logical Volumes now active
VF: Can't find ext3 filesystem on dev dm-0
mount: error mounting /dev/root on /sysroot as ext3: Invalid argument
--
Kernel panic - not synching: Attempted to kill init!
____

My grub config (on disk1) looks like this:
___
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.20-1.2307.fc5)
root (hd0,0)
kernel /vmlinuz-2.6.20-1.2307.fc5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.20-1.2307.fc5.img
title Fedora Core (2.6.18-1.2239.fc5)
root (hd0,0)
kernel /vmlinuz-2.6.18-1.2239.fc5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.18-1.2239.fc5.img
_______

It's logical disk business that is throwing me. I've mounted and can see both HDDs, here -
ubuntu@ubuntu:/mnt/disk1$ ls
config-2.6.18-1.2239.fc5 lost+found
config-2.6.20-1.2307.fc5 System.map-2.6.18-1.2239.fc5
grub System.map-2.6.20-1.2307.fc5
initrd-2.6.18-1.2239.fc5.img vmlinuz-2.6.18-1.2239.fc5
initrd-2.6.20-1.2307.fc5.img vmlinuz-2.6.20-1.2307.fc5

ubuntu@ubuntu:/mnt/disk2$ ls -l
total 0

- So this is what I don't understand. Disk 2 appears empty, which makes sense because I don't have a great deal of data on the system anyway... But where is the filesystem? I mean, where are my files? If I can just liberate my data, I'll be laughing.

[ls354]

Read it all specially the end it may help = http://www.linuxforums.org/forum/ins...-core-5-a.html

[sjaxso]

Read it all specially the end it may help = http://www.linuxforums.org/forum/ins...-core-5-a.html

Hi, can you repost that link, please?

[ls354]

http://www.linuxforums.org/forum/ins...-core-5-a.html

Read it all

[sjaxso]

OK, thanks, that is of some assistance.

My problem now is that I can't mount the VolGroup -
___
ubuntu@ubuntu:/dev/mapper$ sudo mount -t lvm2 /dev/VolGroup00/LogVol00 /mnt/VolGroup00/LogVol00
mount: unknown filesystem type 'lvm2'
ubuntu@ubuntu:/dev/mapper$ sudo mount -t ext3 /dev/VolGroup00/LogVol00 /mnt/VolGroup00/LogVol00
mount: wrong fs type, bad option, bad superblock on /dev/VolGroup00/LogVol00,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
_______

It doesn't recognise the filetype!

It's killing me.