[mythtv-users] Totally OT - but need help wit RAID5 array

James Pifer jep at obrien-pifer.com
Thu Nov 16 20:02:16 UTC 2006


On Thu, 2006-11-16 at 19:47 +0000, Robin Hill wrote:
> On Thu Nov 16, 2006 at 02:31:08PM -0500, James Pifer wrote:
> 
> > > > [root at storage ~]# mdadm --force --assemble /dev/md0 /dev/hdb /dev/hdc
> > > > mdadm: --assemble would set mdadm mode to "assemble", but it is already set to "manage".
> > > > 
> > > > What command(s) should I be using?
> > > > 
> > > Yeah, mdadm is very picky about the order of options.  Try:
> > >         mdadm --assemble /dev/md0 --force /dev/hdb /dev/hdc
> > > 
> > 
> > ok, did that:
> > [root at storage ~]# mdadm --assemble /dev/md0 --force /dev/hdb /dev/hdc
> > mdadm: forcing event count in /dev/hdb(0) from 57595 upto 57602
> > mdadm: /dev/md0 has been started with 2 drives (out of 3).
> > 
> > 
> > Tried to mount it, I got this error:
> > storage kernel: journal commit I/O error
> > 
> > If I try to ls anything I get this:
> > [root at storage ~]# ls /storage/backups
> > ls: reading directory /storage/backups: Input/output error
> > 
> > I unmounted it and tried running fsck /dev/md0 and got:
> > fsck 1.38 (30-Jun-2005)
> > e2fsck 1.38 (30-Jun-2005)
> > fsck.ext3: Attempt to read block from filesystem resulted in short read while trying to open /dev/md0
> > Could this be a zero-length partition?
> > 
> Oh dear, that doesn't look good :(  Are you getting any disk errors in
> /proc/dmesg?
> 

It's not good. See below. In my searching about this problem I found
some references to people using a Windows program called Winhex to
recover data from drives, even RAID drives. What are the chances I could
recover anything that way? Even just some of the stuff?

Thanks,
James

Nov 16 14:56:42 storage kernel: EXT3-fs: INFO: recovery required on readonly filesystem.
Nov 16 14:56:42 storage kernel: EXT3-fs: write access will be enabled during recovery.
Nov 16 14:56:45 storage kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Nov 16 14:56:45 storage kernel: hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=12110000, high=0, low=12110000, sector=12110000
Nov 16 14:56:45 storage kernel: ide: failed opcode was: unknown
Nov 16 14:56:45 storage kernel: end_request: I/O error, dev hdb, sector 12110000
Nov 16 14:56:45 storage kernel: raid5:md0: read error not correctable (sector 12110000 on hdb).
Nov 16 14:56:45 storage kernel: raid5: Disk failure on hdb, disabling device. Operation continuing on 1 devices
Nov 16 14:56:45 storage kernel: Buffer I/O error on device md0, logical block 3027510
Nov 16 14:56:45 storage kernel: lost page write due to I/O error on md0
Nov 16 14:56:45 storage kernel: Buffer I/O error on device md0, logical block 3022379
Nov 16 14:56:45 storage kernel: lost page write due to I/O error on md0
Nov 16 14:56:45 storage kernel: Buffer I/O error on device md0, logical block 3023410
Nov 16 14:56:45 storage kernel: lost page write due to I/O error on md0
Nov 16 14:56:45 storage kernel: Buffer I/O error on device md0, logical block 3024435
Nov 16 14:56:45 storage kernel: lost page write due to I/O error on md0
Nov 16 14:56:45 storage kernel: Buffer I/O error on device md0, logical block 3026485
Nov 16 14:56:45 storage kernel: lost page write due to I/O error on md0
Nov 16 14:56:46 storage kernel: Buffer I/O error on device md0, logical block 3029560
Nov 16 14:56:48 storage kernel: lost page write due to I/O error on md0
Nov 16 14:56:54 storage kernel: Buffer I/O error on device md0, logical block 3032635
Nov 16 14:56:56 storage kernel: lost page write due to I/O error on md0
Nov 16 14:56:57 storage kernel: Buffer I/O error on device md0, logical block 3035710
Nov 16 14:56:57 storage kernel: lost page write due to I/O error on md0
Nov 16 14:56:57 storage kernel: Buffer I/O error on device md0, logical block 3038785
Nov 16 14:56:57 storage kernel: lost page write due to I/O error on md0
Nov 16 14:56:57 storage kernel: Buffer I/O error on device md0, logical block 3041860
Nov 16 14:56:57 storage kernel: lost page write due to I/O error on md0
Nov 16 14:56:57 storage kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Nov 16 14:56:57 storage kernel: hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=12122312, high=0, low=12122312, sector=12122312
Nov 16 14:56:57 storage kernel: ide: failed opcode was: unknown
Nov 16 14:56:57 storage kernel: end_request: I/O error, dev hdb, sector 12122312
Nov 16 14:56:57 storage kernel: raid5:md0: read error not correctable (sector 12122312 on hdb).
Nov 16 14:56:57 storage kernel: printk: 4559 messages suppressed.
Nov 16 14:56:57 storage kernel: Buffer I/O error on device md0, logical block 3031610
Nov 16 14:56:57 storage kernel: lost page write due to I/O error on md0
Nov 16 14:56:57 storage kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Nov 16 14:56:57 storage kernel: hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=12134624, high=0, low=12134624, sector=12134624
Nov 16 14:56:57 storage kernel: ide: failed opcode was: unknown
Nov 16 14:56:57 storage kernel: end_request: I/O error, dev hdb, sector 12134624
Nov 16 14:56:57 storage kernel: raid5:md0: read error not correctable (sector 12134624 on hdb).
Nov 16 14:56:57 storage kernel: Buffer I/O error on device md0, logical block 3033660
Nov 16 14:56:57 storage kernel: lost page write due to I/O error on md0
Nov 16 14:56:59 storage kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Nov 16 14:56:59 storage kernel: hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=12244384, high=0, low=12244384, sector=12244384
Nov 16 14:56:59 storage kernel: ide: failed opcode was: unknown
Nov 16 14:57:01 storage kernel: end_request: I/O error, dev hdb, sector 12244384
Nov 16 14:57:04 storage kernel: raid5:md0: read error not correctable (sector 12244384 on hdb).
Nov 16 14:57:04 storage kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Nov 16 14:57:04 storage kernel: hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=12252592, high=0, low=12252592, sector=12252592
Nov 16 14:57:04 storage kernel: ide: failed opcode was: unknown
Nov 16 14:57:04 storage kernel: end_request: I/O error, dev hdb, sector 12252592
Nov 16 14:57:04 storage kernel: raid5:md0: read error not correctable (sector 12252592 on hdb).
Nov 16 14:57:04 storage kernel: printk: 60 messages suppressed.
Nov 16 14:57:04 storage kernel: Buffer I/O error on device md0, logical block 3063142
Nov 16 14:57:04 storage kernel: lost page write due to I/O error on md0
Nov 16 14:57:04 storage kernel: hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Nov 16 14:57:04 storage kernel: hdb: dma_intr: error=0x40 { UncorrectableError }, LBAsect=12256696, high=0, low=12256696, sector=12256696
Nov 16 14:57:04 storage kernel: ide: failed opcode was: unknown
Nov 16 14:57:04 storage kernel: end_request: I/O error, dev hdb, sector 12256696
Nov 16 14:57:04 storage kernel: raid5:md0: read error not correctable (sector 12256696 on hdb).
Nov 16 14:57:04 storage kernel: RAID5 conf printout:
Nov 16 14:57:04 storage kernel:  --- rd:3 wd:1 fd:2
Nov 16 14:57:04 storage kernel:  disk 0, o:0, dev:hdb
Nov 16 14:57:04 storage kernel:  disk 1, o:1, dev:hdc
Nov 16 14:57:04 storage kernel: RAID5 conf printout:
Nov 16 14:57:04 storage kernel:  --- rd:3 wd:1 fd:2
Nov 16 14:57:04 storage kernel:  disk 1, o:1, dev:hdc
Nov 16 14:57:04 storage kernel: kjournald starting.  Commit interval 5 seconds
Nov 16 14:57:04 storage kernel: EXT3-fs: recovery complete.
Nov 16 14:57:04 storage kernel: EXT3-fs: mounted filesystem with ordered data mode.
Nov 16 14:57:08 storage kernel: EXT3-fs error (device md0): ext3_get_inode_loc: unable to read inode block - inode=49153, block=99350
Nov 16 14:57:18 storage kernel: EXT3-fs error (device md0): ext3_get_inode_loc: unable to read inode block - inode=20512769, block=41025538
Nov 16 14:57:27 storage kernel: EXT3-fs error (device md0): ext3_get_inode_loc: unable to read inode block - inode=17907713, block=35815426




More information about the mythtv-users mailing list