Re: RAID Failed?
- From: "WizardofOS" <tomislav.mihalicek@xxxxxxxxxxx>
- Date: Sat, 3 Jun 2006 00:13:00 +0200
LMAO
"Steve Foley" <steve.foley@xxxxxxxxxxxxxx> wrote in message
news:AYO_f.2135$aE.1551@xxxxxxxxxxx
"dnoyeB" <Fake@xxxxxxxxxxxxxxxxx> wrote in message
news:9YKdnVFMUoywJ6fZnZ2dnUVZ_sidnZ2d@xxxxxxxxxxxxxx
What do you mean by compensating? Doing its job?
Yes
I suspect this drive is going bad. I don't know if I should order new
drives before I power cycle the computer, or after...
You really need to find the appropriate utilities for your raid setup to
determine exactly what the problem is.
The nicest one I saw was on an old VAX system. It would send me an email
stating that an error had occurred on such-and-such a device. After
getting
two or three of these messages, I would order a replacement drive. When I
removed the bad one, I received an email stating that the drive was
offline.
When I inserted the replacement, I received another one stating that the
new
hardware had been installed, and was being rebuilt. When it was done I
received a final email saying the array was now 'optimal'.
Worst case was on an IBM server. An error message appeared. I called in an
IBM service tech. He replaced the drive and 'had to run a utility'. The
utility initialized the array, erasing everything on it. He left saying
"It's working correctly now - sorry, we're not responsible for data...."
9:16
Steve Foley wrote:
Sounds like you've got a flakey drive, and the RAID is compensating.
"dnoyeB" <Fake@xxxxxxxxxxxxxxxxx> wrote in message
news:6IydnT_Sg_T6AafZRVn-vg@xxxxxxxxxxxxxx
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
--
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
.
- Prev by Date: Re: Which distro?
- Next by Date: Re: test
- Previous by thread: Re: Which distro?
- Next by thread: Re: test
- Index(es):
Relevant Pages
|
