Dear RAID gurus,

I have a RAID array with two disks operating in linear mode, as per the
following raidtab:

raiddev /dev/md0
   raid-level                linear
   nr-raid-disks             2
   nr-spare-disks            0

   device                    /dev/sdb2
   raid-disk                 0
   device                    /dev/sdc1
   raid-disk  

This configuration was setup under Redhat 5.2 with raidtools 0.50. The
other day I upgraded the system to RH 6.1 (raidtools 0.90). The array
fails to initialize, and the following messages appear in the syslog:

May 26 10:41:22 cdfrh1 kernel: SCSI device sdc: hdwr sector= 512 bytes. Sectors=
 97693755 [47702 MB] [47.7 GB] 
May 26 10:41:22 cdfrh1 kernel:  sdc: sdc1 
May 26 10:41:22 cdfrh1 kernel: autodetecting RAID arrays 
May 26 10:41:23 cdfrh1 kernel: (read) sdb2's sb offset: 9052544 [events: 0000000
0] 
May 26 10:41:23 cdfrh1 kernel: md: invalid raid superblock magic on sdb2 
May 26 10:41:23 cdfrh1 kernel: md: sdb2 has invalid sb, not importing! 
May 26 10:41:23 cdfrh1 kernel: could not import sdb2! 
May 26 10:41:23 cdfrh1 kernel: autostart sdb2 failed! 
May 26 10:41:23 cdfrh1 kernel: bind<sdb2,1> 
May 26 10:41:23 cdfrh1 kernel: nonpersistent superblock ... 
May 26 10:41:23 cdfrh1 kernel: no chunksize? 
May 26 10:41:23 cdfrh1 kernel: bind<sdc1,2> 
May 26 10:41:23 cdfrh1 kernel: nonpersistent superblock ... 
May 26 10:41:23 cdfrh1 kernel: no chunksize? 
May 26 10:41:23 cdfrh1 kernel: sdc1's event counter: 00000000 
May 26 10:41:23 cdfrh1 kernel: sdb2's event counter: 00000000 
May 26 10:41:23 cdfrh1 kernel: md: bug in file md.c, line 1588 
May 26 10:41:23 cdfrh1 kernel:  
May 26 10:41:23 cdfrh1 kernel:        ********************************** 
May 26 10:41:23 cdfrh1 kernel:        * <COMPLETE RAID STATE PRINTOUT> * 
May 26 10:41:23 cdfrh1 kernel:        ********************************** 
May 26 10:41:23 cdfrh1 kernel: md0: <sdc1><sdb2> array superblock: 
May 26 10:41:23 cdfrh1 kernel:   SB: (V:0.90.0) ID:<c5e95de4.3cc17aee.5e81f108.f
dfb910a> CT:392e8cc8 
May 26 10:41:23 cdfrh1 kernel:      L-1 S09052627 ND:2 RD:2 md0 LO:0 CS:0 
May 26 10:41:23 cdfrh1 kernel:      UT:00000000 ST:0 AD:2 WD:2 FD:0 SD:0 CSUM:42
0c5963 E:00000000 
May 26 10:41:23 cdfrh1 kernel:      D  0:  DISK<N:0,sdb2(8,18),R:0,S:6> 
May 26 10:41:23 cdfrh1 kernel:      D  1:  DISK<N:1,sdc1(8,33),R:1,S:6> 

                (etc. etc.)

I also tried upgrading the configuration using mkraid:

% /sbin/mkraid --upgrade /dev/md0
handling MD device /dev/md0
analyzing super-block
cannot upgrade magic-less superblock on /dev/sdb2 ...
mkraid: aborted, see the syslog and /proc/mdstat for potential clues.

Finally, fsck yields:

/sbin/fsck /dev/md0
Parallelizing fsck version 1.17 (26-Oct-1999)
e2fsck 1.17, 26-Oct-1999 for EXT2 FS 0.5b, 95/08/09
fsck.ext2: Attempt to read block from filesystem resulted in short read
while trying to open /dev/md0
Could this be a zero-length partition?

Can this filesystem be saved, or do I need to blow it away and start
over...?

Thanks for any help you can provide.

                        Regards,

                          David Gerdes

--------------------------------------
David Gerdes, University of Michigan
(734) 647-3807 / (734) 936-1817 FAX
[EMAIL PROTECTED]
http://umaxp1.physics.lsa.umich.edu/~gerdes/

Reply via email to