SATA problem?

[Stuart Biggerstaff]

Sorry about the lack of subject line.

What won't boot is the spare PC I mention.  The original disk has apparently deteriorated to the degree that if connected to that PC's controller it tries to access the disk and reboots.  So I can't do further diagnostics on it.  The server boots--though sometimes has problems if only one of the disks is physically present.

Removing the replacement and booting it in a PC, it passed Seagate's short test but showed "SMART TRIPPED Warranty validation code A9E7D26A".  The disk had all the array data as far as I could tell, even when I deleted its formatting and let it rebuild again.  And when I communicated the error to the vendor they were happy to replace it.  they probably will be less agreeable a second time if it's likely the problem is in the system


Stuart Biggerstaff

-----Original Message-----
From: linux-users-bounces+biggers=lindahall.org at linux-sxs.org [mailto:linux-users-bounces+biggers=lindahall.org at linux-sxs.org] On Behalf Of Lonni J Friedman
Sent: Tuesday, August 07, 2012 3:54 PM
To: linux-users at linux-sxs.org
Subject: Re:

On Tue, Aug 7, 2012 at 1:52 PM, Kevin O'Gorman <kogorman at gmail.com> wrote:
> On Tue, Aug 7, 2012 at 1:48 PM, Stuart Biggerstaff
> <biggers at lindahall.org> wrote:
>> The system is a Dell Poweredge R410, with two SATA disks in RAID 1.  It has been running for about three years.  Just over a month ago, disk 0 gradually failed.  And running diagnostics on it has confirmed it to be bad--at least initially, now it's dead and a PC won't even boot with it connected.
>>
>> A replacement turned up as predicted to fail (by the system LED) once the RAID array was synchronized.  Pulling it and connecting it to a spare PC to run Seagate's diagnostics showed "SMART has been tripped" and the seller was willing to replace it as defective.
>>
>> But the second replacement is showing evidence it is failing.  So now trying to figure how the SATA interface can work to the extent it properly reads and writes the drive, but causes it to go bad.  Or else I've gotten two defective hard drives.  Has anyone seen a situation where a disk has been broken by a system that is able to successfully access it?
>
> I never have.
>
> You might get more responses if your thread had a subject line.


I've never come across anything like this either.  I also don't
understand how one of two disks in a RAID1 array failing would cause a
system to stop booting.  Sounds to me like you've got far bigger
problems than just a bad disk.
_______________________________________________
Linux-users mailing list
Linux-users at linux-sxs.org
http://mailman.celestial.com/mailman/listinfo/linux-users