EXT3 RAID1 "Please Repair The FileSystem Manually" How ?

Hi All..here is the problem..

I have a Hardy Server..
Originally /dev/hda1 was 80Gb O/s & Swap.. /dev/hdb was 122Gb single partition../dev/hdc is a 250Gb drive was partitioned to match 122Gb.
Both 122Gb drives were configured as a mdadm software RAID 1 on /dev/md0 .. As the raid was 97% full I needed to replace the

122Gb drive so here is what I did..

I purchased a SATA PCI controller & I had a 320Gb SATA drive. The kernel picked up the controller & saw the new drive no

problems. So now i have 1xIDE 250Gb & 1x320Gb SATA drives

1st.. I used mdadam to --fail the 122Gb drive.
2nd.I used mdadm to --remove the drive..
3rd. I used mdadm to --stop /dev/md0
4th.I issued umount /dev/md0
5. I issude --zero-superblock on the 122Gb drive..
6. I then shut down & removed the old 122 drive so I should have a safe copy of my data.
7. I used Gparted to resize the 250Gb drive into a single partition..
8. I rebooted & mounted the 250 Gb all seemed fine & data all appears intact on this resized drive..
9.I must mention I did at some point use  fdisk to change the filesystem type (why I can not now remember ! Sorry..)
10 finally I fdisked the new drive to create an identical partition size (in cylinders) to the 250Gb drive .
11 I then used mdadm to --create /dev/md0, it did inform me that it appears an ext2 fs was on the drive & did I want to continue.. I

selected yes & it continued to create /dev/md0..After the syncing process I turned off the PC
This morning I rebooted & got the following messages.

fsck.ext3: Invalid argument while trying to open /dev/md0 /dev/md0:
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is vaild and it really contains an ext2

filesystem (and now swap or ufs or something else) then the superblock is corrupt, and you might try running e2fsck with an alternate

superblock:

e2fsck -b 8193 <device>
fsck died with exit status 8.
File system check failed.

Please Repair The FileSystem Manually.... HOW ! I have no idea !!
If anyone can guide me on what to do now I would be MORE than appreciative.. When i did an fdisk -l this morning I could b=not see

the /dev/md0 drive... HELP please, please remember Im a newbie so if you can hold me by the hand & guide me that would be

fantastic !!

LVL 1
mrmad1966Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

TobiasCommented:
Hi !

Try :

e2fsck -b 8193 /dev/md0

Best Regards
0
mrmad1966Author Commented:
Thank you for your response.. Unfortunatley it did not work as I was getting not more possible solutions & time was critical I had no other option than to reinstall the whole system..
Thanks
John
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.