Ben/Daniel,

I had a feeling it was to do with connectivity after pulling it out and putting 
it back in. Some of the error messages disappeared, however the software raid 
was still degrading. I then replaced the SATA cable and it seems to be all good 
now. Didn't think it would be something so simple.

FYI, smartctl couldn't report on it initially. Both drives passed the self 
assessment after having rebuilt the array. Thanks again both for the help.

Regards,
HD Nguyen

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of 
Hongduc Nguyen
Sent: Friday, June 19, 2009 10:17 AM
To: '[email protected]'
Subject: [SLUG] RAID1 issues

Hi sLUG,

Was hoping someone can help confirm or point me in the right direction with 
this error on my server. SDA is a brand new drive, it was replacing another 
disk which was displaying similar symptoms. Is it the motherboard, or am I just 
unlucky and got another bad drive?

DMESG (snippet):
raid1: Disk failure on sda3, disabling device.
        Operation continuing on 1 devices
sd 0:0:0:0: SCSI error: return code = 0x00040000
end_request: I/O error, dev sda, sector 1087
raid1: sda1: rescheduling sector 1024
sd 0:0:0:0: SCSI error: return code = 0x00040000
end_request: I/O error, dev sda, sector 1087
raid1: Disk failure on sda1, disabling device.
        Operation continuing on 1 devices
raid1: sdb1: redirecting sector 1024 to another mirror

var/log/messages:
Device: /dev/sda, not capable of SMART self-check
Device: /dev/sda, failed to read SMART Attribute Data

Thanks,
HD Nguyen

________________________________
Please consider our environment before printing this email.
This e-mail and any files transmitted with it are privileged and confidential 
information intended for the use of the addressee. The confidentiality and/or 
privilege in this e-mail is not waived, lost or destroyed if it has been 
transmitted to you in error. If you have received this e-mail in error you must 
(a) not disseminate, copy or take any action in reliance on it; (b) notify 
[email protected] and the sender immediately; and (c) delete the 
original e-mail.
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
--
Message  protected by MailGuard: e-mail anti-virus, anti-spam and content 
filtering.
http://www.mailguard.com.au

Click here to report this message as spam:
https://login.mailguard.com.au/report/1xHNCYpRok/3NKJhpPCKbnaOfL26WDS7F/0


Please consider our environment before printing this email.
This e-mail and any files transmitted with it are privileged and confidential 
information intended for the use of the addressee. The confidentiality and/or 
privilege in this e-mail is not waived, lost or destroyed if it has been 
transmitted to you in error. If you have received this e-mail in error you must 
(a) not disseminate, copy or take any action in reliance on it; (b) notify 
[email protected] and the sender immediately; and (c) delete the 
original e-mail.

Please consider our environment before printing this email.
This e-mail and any files transmitted with it are privileged and confidential 
information intended for the use of the addressee. The confidentiality and/or 
privilege in this e-mail is not waived, lost or destroyed if it has been 
transmitted to you in error. If you have received this e-mail in error you must 
(a) not disseminate, copy or take any action in reliance on it; (b) notify 
[email protected] and the sender immediately; and (c) delete the 
original e-mail.
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html

Reply via email to