EXT3 RAID1 "Please Repair The FileSystem Manually" How ?
Posted on 2008-10-30
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
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