LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices

Reply
 
Search this Thread
Old 07-21-2009, 08:54 PM   #1
zogthegreat
Member
 
Registered: Apr 2009
Location: Montreal, Canada
Distribution: Fedora, CentOS, Ubuntu
Posts: 47

Rep: Reputation: 16
invalid metadata checksum error, (I think)


Hi everyone,

I am have a problem with a back-up machine that I had built to hold my data while I rebuilt my server. The hardware is as follows:

motherboard: ECS k7S5A w/ AMD Athlon 1800 cpu
memory: 1 gig PC133 SDRAM
HD: 1 WD 120 gig IDE + 1 Seagate 250 gig IDE in a JBOD
NIC: Realtech gigbit
OS: CentOS 5.2

The system setup and ran fine for a few months. Had a power failure in my neighborhood and when I rebooted the machine, the system loads until

unmounting old /dev
unmounting old /proc
unmounting old /sys
exec of init (/sbin/init) fails!!!: No such file or directory
Kernel panic - not syncing: Attempted to kill init!

From there my system locks and the lights on the keyboard start flashing.

I tried to use a CentOS dvd in "linux rescue" mode. The system displays a message in the background "invalid metadata checksum in area 1 /dev/hda" then loads the screen that tells me to mount the system image with the "chroot /mnt/sysimage". When I try to do this, I get the following error, "chroot cannot run command bin bash' no such file or directory".

Does anyone have any suggestions?

Thanks

zog
 
Old 07-22-2009, 03:23 PM   #2
mostlyharmless
Senior Member
 
Registered: Jan 2008
Distribution: Slackware -current (multilib) with kernel 3.16.2
Posts: 1,571
Blog Entries: 13

Rep: Reputation: 182Reputation: 182
Sounds like your JBOD is busted to me. I presume it is firmware set up by the motherboard. You might want to check that the firmware/BIOS is still set to JBOD, as sometimes a power out can reset the BIOS to default, which is not JBOD. If you're real lucky, it might have diagnostics of your JBOD array.

If that doesn't do it, you'll need to mount the rescue CD with possibly dmraid to mount your array (though I don't know if it does JBOD) and possibly testdisk to see if you can rescue your data. I'm not familiar with the Centos rescue CD; you might want to try something independent and fully featured; e.g. Knoppix. Could be one of the drives or the mobo/controller has a problem (or not); you'll have to investigate....

That's where I'd start; I hope that helps.

Last edited by mostlyharmless; 07-22-2009 at 03:25 PM. Reason: added info
 
Old 07-22-2009, 06:18 PM   #3
zogthegreat
Member
 
Registered: Apr 2009
Location: Montreal, Canada
Distribution: Fedora, CentOS, Ubuntu
Posts: 47

Original Poster
Rep: Reputation: 16
hi mostlyharmless,

I solved the problem with the following:

I downloaded "System Rescue CD" from http://www.sysresccd.org. Although I used this cd, I probably could have used Knoppix.

I started with:

root@sysresccd /root % lvm pvscan

PV /dev/sdb1 VG VolGroup00 lvm2 [111.78 GB / 0 free]
PV /dev/sda2 VG VolGroup00 lvm2 [232.78 GB / 0 free]

I than ran the following:

root@sysresccd /root % fsck -f /dev/VolGroup00/LogVol01

I was required to constantly hit the y key in order to continue. I could/should have used the -P argument, as it was, I had to set a weight on the "y" key. After 7 hours, I got the following output:

/dev/VolGroup00/LogVol00: ***** FILE SYSTEM WAS MODIFIED *****
/dev/VolGroup00/LogVol00: 89641/90079232 files (4.1% non-contiguous), 85329392/90062848 blocks

I then did this:

root@sysresccd# lvm lvscan

ACTIVE '/dev/VolGroup00/LogVol00' [343.56 GB] inherit
ACTIVE '/dev/VolGroup00/LogVol01' [1.00 GB] inherit

root@sysresccd /root % mount /dev/VolGroup00/LogVol00 /mnt/part1
root@sysresccd /root % mount /dev/VolGroup00/LogVol01 /mnt/part2
root@sysresccd /root % cd /mnt/part1
root@sysresccd /mnt/part1 % ls
bin dev home lost+found misc net proc sbin srv tmp var
boot etc lib media mnt opt root selinux sys usr

All of my data was there and I am able to copy it over to my new server using scp.

Hope this helps someone else.

zog
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Metadata file does not match checksum error olracdor Linux - Newbie 1 11-16-2008 05:59 AM
Livna - Metadata file does not match checksum captainxark Fedora 1 07-29-2008 09:14 PM
Fedora 8: Inkscape metadata checksum mismatch!! Hitboxx Fedora 3 12-31-2007 08:27 PM
metadata file does not match checksum ? anilbh Fedora 4 04-15-2007 01:08 PM
LVM Error: incorrect metadata area header checksum neillans Linux - General 1 02-28-2006 03:06 PM


All times are GMT -5. The time now is 09:47 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration