One of my new HDs is clicking every hour or so, but I can't figure out which
one is dying because it seems that the RAID layer is blocking my access to
the SMART information. How can I read the SMART information from each
drive?
"Phil, Non-Squid" <phil_leeDELETEME@hotmail.com> wrote in message
news:464a8cbc$0$9009$4c368faf@roadrunner.com...
> One of my new HDs is clicking every hour or so, but I can't figure out
> which one is dying because it seems that the RAID layer is blocking my
> access to the SMART information. How can I read the SMART information
> from each drive?
>
> --
> Phil
About the only thing you can do is to take down the Raid0 array and read the
data for the drives individually. I would copy the contents of the array to
a single drive (if it is crucial data) because I doubt the array will be
recoverable. I only use Raid0 for video editing and processing and then
store the finished product to large single drives. Raid0 is good for speed
and bad for critical storage or OSs because of this particular problem. I
have few HDD problems, but when I do it is almost always on a Raid0
array.......bad luck I guess.......:-)
"Ed Medlin" <edmedlin@yahoo.com> wrote in message
news:lAC2i.6462$H_.694@newssvr21.news.prodigy.net. ..
>
> "Phil, Non-Squid" <phil_leeDELETEME@hotmail.com> wrote in message
> news:464a8cbc$0$9009$4c368faf@roadrunner.com...
>> One of my new HDs is clicking every hour or so, but I can't figure out
>> which one is dying because it seems that the RAID layer is blocking my
>> access to the SMART information. How can I read the SMART information
>> from each drive?
>>
>> --
>> Phil
> About the only thing you can do is to take down the Raid0 array and read
> the data for the drives individually. I would copy the contents of the
> array to a single drive (if it is crucial data) because I doubt the array
> will be recoverable. I only use Raid0 for video editing and processing and
> then store the finished product to large single drives. Raid0 is good for
> speed and bad for critical storage or OSs because of this particular
> problem. I have few HDD problems, but when I do it is almost always on a
> Raid0 array.......bad luck I guess.......:-)
Err, I think you may have missed the part about my array being RAID 1..
"Phil, Non-Squid" <phil_leeDELETEME@hotmail.com> wrote in message
news:464b32e4$0$4677$4c368faf@roadrunner.com...
>
> "Ed Medlin" <edmedlin@yahoo.com> wrote in message
> news:lAC2i.6462$H_.694@newssvr21.news.prodigy.net. ..
>>
>> "Phil, Non-Squid" <phil_leeDELETEME@hotmail.com> wrote in message
>> news:464a8cbc$0$9009$4c368faf@roadrunner.com...
>>> One of my new HDs is clicking every hour or so, but I can't figure out
>>> which one is dying because it seems that the RAID layer is blocking my
>>> access to the SMART information. How can I read the SMART information
>>> from each drive?
>>>
>>> --
>>> Phil
>> About the only thing you can do is to take down the Raid0 array and read
>> the data for the drives individually. I would copy the contents of the
>> array to a single drive (if it is crucial data) because I doubt the array
>> will be recoverable. I only use Raid0 for video editing and processing
>> and then store the finished product to large single drives. Raid0 is good
>> for speed and bad for critical storage or OSs because of this particular
>> problem. I have few HDD problems, but when I do it is almost always on a
>> Raid0 array.......bad luck I guess.......:-)
>
> Err, I think you may have missed the part about my array being RAID 1..
>
> --
> Phil
Sorry Phil......:-). Getting old is a bi&$%. I could have sworn it said
raid0. You should be able to remove one drive, check it, and replace it and
then check the other then rebuild the array as long as the data isn't
changed on either. When or if you find the bad drive just replace it with
one the same (size is all that matters) then rebuild the array and the data
should be back across the array. Backup first as always.........sorry
again....
Ed Medlin wrote:
> "Phil, Non-Squid" <phil_leeDELETEME@hotmail.com> wrote in message
> news:464b32e4$0$4677$4c368faf@roadrunner.com...
>>
>> "Ed Medlin" <edmedlin@yahoo.com> wrote in message
>> news:lAC2i.6462$H_.694@newssvr21.news.prodigy.net. ..
>>>
>>> "Phil, Non-Squid" <phil_leeDELETEME@hotmail.com> wrote in message
>>> news:464a8cbc$0$9009$4c368faf@roadrunner.com...
>>>> One of my new HDs is clicking every hour or so, but I can't figure
>>>> out which one is dying because it seems that the RAID layer is
>>>> blocking my access to the SMART information. How can I read the
>>>> SMART information from each drive?
>>>>
>>>> --
>>>> Phil
>>> About the only thing you can do is to take down the Raid0 array and
>>> read the data for the drives individually. I would copy the
>>> contents of the array to a single drive (if it is crucial data)
>>> because I doubt the array will be recoverable. I only use Raid0 for
>>> video editing and processing and then store the finished product to
>>> large single drives. Raid0 is good for speed and bad for critical
>>> storage or OSs because of this particular problem. I have few HDD
>>> problems, but when I do it is almost always on a Raid0
>>> array.......bad luck I guess.......:-)
>>
>> Err, I think you may have missed the part about my array being RAID
>> 1..
>> --
>> Phil
> Sorry Phil......:-). Getting old is a bi&$%. I could have sworn it
> said raid0. You should be able to remove one drive, check it, and
> replace it and then check the other then rebuild the array as long as
> the data isn't changed on either. When or if you find the bad drive
> just replace it with one the same (size is all that matters) then
> rebuild the array and the data should be back across the array.
> Backup first as always.........sorry again....
>
>
> Ed
I did as you said and noticed that one drive had a bit worse stats than the
other (seek errors were at something like 38 vs. 40 or something) The
overall health and performance of one was 31% and the other was 38% I think.
Both are identical Seagates, and I read something about Seagates having
horrible SMART scores in Speedfan, so I really don't know what to do next.
I think I'm just going to tough it out until one of them goes kaput in the
next 5 years, then replace it.
I'm considering RMAing each one individually, too. This way, I could
rebuild the array while I'm at work and then RMA the other one and rebuild
it again. I think I'll do that.
"Phil, Non-Squid" <notsure@iwanttogiveyou.this> wrote in message
news:464e1e94$0$12466$4c368faf@roadrunner.com...
> Ed Medlin wrote:
>> "Phil, Non-Squid" <phil_leeDELETEME@hotmail.com> wrote in message
>> news:464b32e4$0$4677$4c368faf@roadrunner.com...
>>>
>>> "Ed Medlin" <edmedlin@yahoo.com> wrote in message
>>> news:lAC2i.6462$H_.694@newssvr21.news.prodigy.net. ..
>>>>
>>>> "Phil, Non-Squid" <phil_leeDELETEME@hotmail.com> wrote in message
>>>> news:464a8cbc$0$9009$4c368faf@roadrunner.com...
>>>>> One of my new HDs is clicking every hour or so, but I can't figure
>>>>> out which one is dying because it seems that the RAID layer is
>>>>> blocking my access to the SMART information. How can I read the
>>>>> SMART information from each drive?
>>>>>
>>>>> --
>>>>> Phil
>>>> About the only thing you can do is to take down the Raid0 array and
>>>> read the data for the drives individually. I would copy the
>>>> contents of the array to a single drive (if it is crucial data)
>>>> because I doubt the array will be recoverable. I only use Raid0 for
>>>> video editing and processing and then store the finished product to
>>>> large single drives. Raid0 is good for speed and bad for critical
>>>> storage or OSs because of this particular problem. I have few HDD
>>>> problems, but when I do it is almost always on a Raid0
>>>> array.......bad luck I guess.......:-)
>>>
>>> Err, I think you may have missed the part about my array being RAID
>>> 1..
>>> --
>>> Phil
>> Sorry Phil......:-). Getting old is a bi&$%. I could have sworn it
>> said raid0. You should be able to remove one drive, check it, and
>> replace it and then check the other then rebuild the array as long as
>> the data isn't changed on either. When or if you find the bad drive
>> just replace it with one the same (size is all that matters) then
>> rebuild the array and the data should be back across the array.
>> Backup first as always.........sorry again....
>>
>>
>> Ed
>
> I did as you said and noticed that one drive had a bit worse stats than
> the other (seek errors were at something like 38 vs. 40 or something) The
> overall health and performance of one was 31% and the other was 38% I
> think. Both are identical Seagates, and I read something about Seagates
> having horrible SMART scores in Speedfan, so I really don't know what to
> do next. I think I'm just going to tough it out until one of them goes
> kaput in the next 5 years, then replace it.
>
> I'm considering RMAing each one individually, too. This way, I could
> rebuild the array while I'm at work and then RMA the other one and rebuild
> it again. I think I'll do that.
>
> --
> Phil
I think that is probably the best course to take. It may not happen often,
but if you happen to lose both drives then you are up the creek. I wasn't
aware that Seagates scored like that in Speedfan. Did you isolate the drive
that is making the noise? If you did, RMA that one first.....
> but if you happen to lose both drives then you are up the creek. I wasn't
> aware that Seagates scored like that in Speedfan. Did you isolate the
> drive that is making the noise? If you did, RMA that one first.....
If there's an issue with Speedfan, you could check again with dtemp.
How to tell which RAID 1 drive is failing? 
Linear Mode
