Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
06-26-2009, 09:57 AM
|
#1
|
Member
Registered: Dec 2005
Distribution: FC8, FC9, FC10
Posts: 30
Rep:
|
mdadm failed disk, why?
I have a Raid 1 with 2 WDC WD800JD, mdadm failed one of them and I'm not sure why. What should I check first? I looked at SMART and I did not see anything or maybe I missed it. I've run badblocks with a read only test and did not find any errors, I'm in the process of doing a read right test with badblocks now it looks like it has made to the 4 write read phase and nothing so far.
Is there a way to clear the failure and re-add the drive to the RAID and see if it happens again?
I'm running Fedora Core 10 2.6.27.12-170.2.5.fc10.i686
|
|
|
06-26-2009, 06:16 PM
|
#2
|
Senior Member
Registered: Jan 2008
Distribution: Arch/Manjaro, might try Slackware again
Posts: 1,859
|
I believe that if you remove the disk from the array and add it back again that that will clear the F flag.
Remove:
mdadm /dev/md{0,1..} -r /dev/hda{1,2...}
Add:
mdadm /dev/md{0,1..} -a /dev/hda{1,2...}
See what happens, assuming it gets sync'd:
mdadm --detail /dev/md{0,1..}
Hope that helps and you haven't tried all that already...
|
|
|
06-27-2009, 01:20 PM
|
#3
|
Member
Registered: Dec 2005
Distribution: FC8, FC9, FC10
Posts: 30
Original Poster
Rep:
|
I think I've done that in the past. I did try it again and we will see how long it will last. I was able to find a SMART error from the past.
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
Please note the following marginal Attributes:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
200 Multi_Zone_Error_Rate 0x0009 200 001 051 Pre-fail Offline In_the_past 0
Does anyone know of a way to clear out the error log of SMART or is this what mdadm is seeing and causing it to kick out the drive?
Thanks
|
|
|
06-28-2009, 10:36 PM
|
#4
|
Senior Member
Registered: Jan 2008
Distribution: Arch/Manjaro, might try Slackware again
Posts: 1,859
|
I believe you can turn SMART off, actually, though you might not want to do that. However, I don't think mdadm monitors SMART or cares about that.
|
|
|
All times are GMT -5. The time now is 06:27 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|