Re: RAID Failed?



sort of. When I installed my 3ware hardware raid controller on my new Mandrake 2006 server, smartctrl is there too. i need to get it scheduled and whatnot. no more fake or soft raid for me. im sick of it.

the drive was bad. a 3rd drive that i had copied stuff onto during this failure went bad as well. luckily i had also forced myself copied to cdrom.

Gotta love Maxtor...In fairness they were probably cooking for 3 years now. But when i put the drive on the dead shelf I noticed a twin :P obviously that '3rd' drive was the 2nd drive in an old raid set a while back...



Thomas Worthington wrote:
Have you installed and run smartctl to get a health check on the drives?

TW

On Mon, 10 Apr 2006 18:56:54 +0100, dnoyeB <Fake@xxxxxxxxxxxxxxxxx> wrote:

my raid is spitting errors into the log and whatnot. I am trying to figure out the problem but am not entirely sure how to go about it. Can you interpret this info?

output from '/proc/mdstat'
Personalities : [raid1]
read_ahead 1024 sectors
md0 : active raid1 hdg1[1]
39097152 blocks [2/1] [_U]

output from 'lsraid -a /dev/md0'
[dev 9, 0] /dev/md0 00000000.00000000.00000000.00000000 online
[dev ?, ?] (unknown) 00000000.00000000.00000000.00000000 missing



output from 'tail -f /var/log/messages'
Apr 10 13:40:56 erasmus kernel: hdg: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Apr 10 13:40:56 erasmus kernel: hdg: dma_intr: error=0x40 { UncorrectableError }, LBAsect=30408783, sector=30408720
Apr 10 13:40:56 erasmus kernel: end_request: I/O error, dev 22:01 (hdg), sector 30408720
Apr 10 13:40:56 erasmus kernel: raid1: hdg1: rescheduling block 30408720
Apr 10 13:40:56 erasmus kernel: raid1: hdg1: unrecoverable I/O read error for block 30408720
Apr 10 13:40:56 erasmus kernel: EXT3-fs error (device md(9,0)): ext3_get_inode_loc: unable to read inode block
- inode=1896839, block=3801090

this type of stuff has been happening for over a week now. Do I need to reset my computer? Maybe the HD locked up or something? I don't want to reset it because this is actually not the first time drives have started to do this on this computer. When I reset typically it cant find drives and whacky stuff happens. I leave computer off for a few days and then it starts up and runs for several months without a hitch. Everything is backed up so I can reset it. Just am not looking forward to the attempt...

This is RH9 on an ABIT NV7-133R (nforce) board I believe with external graphics).








--
Thank you,



"Then said I, Wisdom [is] better than strength: nevertheless the poor man's wisdom [is] despised, and his words are not heard." Ecclesiastes 9:16
.