[CLUE-Tech] Software raid is a strange thing

[cuteredstorm]

I have had a raid 0 field up for a few months. Then i
added a new ide controller that mixed up the order of
ide controllers (the one on the mobo was ide4,ide5).
I fixed this by passing arguments to the kernel in the
form of ide0=0xsomenumber and so on for each drive.
This had worked without problems and all the drives
got their original names back. The raid had also
started (i will post the dmesg details below) and
reported no errors. 
When i tried to mount it however it reported bad
superblock. I had then tried each superblock the
mke2fs suggested. I had also used a superblock finderm
that found superblocks, but unfortunately their
positions were all exactly 32 greater than the ones
suggested by the mke2fs. 
Normally i used e2fsck -b #number -n /dev/md0 but 6
screens of inode errors in a second and then it
stopped. Surprisingly i got the same errors for each
superblock copy. Since i doubt running e2fsck without
-n would solve anything i had not done that.
I wonder if there is anything i can do to save the
data (it's not something i can lose my job over, but i
would still like to have it).

The info:~# cat /proc/mdstat
Personalities : [linear] [raid0]
read_ahead 1024 sectors
md0 : active raid0 hdh1[1] hdg1[0] hdf1[3] hde1[2]
      312599872 blocks 64k chunks

# cat /etc/raidtab
raiddev /dev/md0
        raid-level      0
        nr-raid-disks   4
        persistent-superblock 1
        chunk-size      64
        device          /dev/hde1
        raid-disk       0
        device          /dev/hdf1
        raid-disk       1
        device          /dev/hdg1
        raid-disk       2
        device          /dev/hdh1
        raid-disk       3

md: linear personality registered as nr 1
md: raid0 personality registered as nr 2
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
 [events: 00000023]
 [events: 00000023]
 [events: 00000023]
 [events: 00000023]
md: autorun ...
md: considering hdh1 ...
md:  adding hdh1 ...
md:  adding hdg1 ...
md:  adding hdf1 ...
md:  adding hde1 ...
md: created md0
md: bind<hde1,1>
md: bind<hdf1,2>
md: bind<hdg1,3>
md: bind<hdh1,4>
md: running: <hdh1><hdg1><hdf1><hde1>
md: hdh1's event counter: 00000023
md: hdg1's event counter: 00000023
md: hdf1's event counter: 00000023
md: hde1's event counter: 00000023
md0: max total readahead window set to 1024k
md0: 4 data-disks, max readahead per data-disk: 256k
raid0: looking at hdg1
raid0:   comparing hdg1(78148096) with hdg1(78148096)
raid0:   END
raid0:   ==> UNIQUE
raid0: 1 zones
raid0: looking at hdh1
raid0:   comparing hdh1(78150592) with hdg1(78148096)
raid0:   NOT EQUAL
raid0:   comparing hdh1(78150592) with hdh1(78150592)
raid0:   END
raid0:   ==> UNIQUE
raid0: 2 zones
raid0: looking at hde1
raid0:   comparing hde1(78150592) with hdg1(78148096)
raid0:   NOT EQUAL
raid0:   comparing hde1(78150592) with hdh1(78150592)
raid0:   EQUAL
raid0: looking at hdf1
raid0:   comparing hdf1(78150592) with hdg1(78148096)
raid0:   NOT EQUAL
raid0:   comparing hdf1(78150592) with hdh1(78150592)
raid0:   EQUAL
raid0: FINAL 2 zones
raid0: zone 0
raid0: checking hdg1 ... contained as device 0
  (78148096) is smallest!.
raid0: checking hdh1 ... contained as device 1
raid0: checking hde1 ... contained as device 2
raid0: checking hdf1 ... contained as device 3
raid0: zone->nb_dev: 4, size: 312592384
raid0: current zone offset: 78148096
raid0: zone 1
raid0: checking hdg1 ... nope.
raid0: checking hdh1 ... contained as device 0
  (78150592) is smallest!.
raid0: checking hde1 ... contained as device 1
raid0: checking hdf1 ... contained as device 2
raid0: zone->nb_dev: 3, size: 7488
raid0: current zone offset: 78150592
raid0: done.
raid0 : md_size is 312599872 blocks.
raid0 : conf->smallest->size is 7488 blocks.
raid0 : nb_zone is 41747.
raid0 : Allocating 333976 bytes for hash.
md: updating md0 RAID superblock on device
md: hdh1 [events: 00000024]<6>(write) hdh1's sb
offset: 78150592
md: hdg1 [events: 00000024]<6>(write) hdg1's sb
offset: 78148096
md: hdf1 [events: 00000024]<6>(write) hdf1's sb
offset: 78150592
md: hde1 [events: 00000024]<6>(write) hde1's sb
offset: 78150592
md: ... autorun DONE.

Thank you for Your help,
 Cute

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com