Here is some info from smartctl:

Error 52 occurred at disk power-on lifetime: 56 hours (2 days + 8 hours)
When the command that caused the error occurred, the device was active or idle.

 After command completion occurred, registers were:
 ER ST SC SN CL CH DH
 -- -- -- -- -- -- --
40 51 20 df 0c af fd Error: UNC 32 sectors at LBA = 0x0daf0cdf = 229575903

 Commands leading to the command that caused the error were:
 CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
 -- -- -- -- -- -- -- --  ----------------  --------------------
 c8 00 20 df 0c af fd 00      00:02:39.192  READ DMA
 c8 00 04 3f 2f 00 f0 00      00:02:39.192  READ DMA
 c8 00 20 1f 01 00 f0 00      00:02:39.187  READ DMA
 c8 00 04 3f ce 9d fd 00      00:02:39.178  READ DMA
 c8 00 20 ff ce 9d fd 00      00:02:39.170  READ DMA

Error 51 occurred at disk power-on lifetime: 56 hours (2 days + 8 hours)
When the command that caused the error occurred, the device was active or idle.

 After command completion occurred, registers were:
 ER ST SC SN CL CH DH
 -- -- -- -- -- -- --
 40 51 01 df 0c af fd  Error: UNC 1 sectors at LBA = 0x0daf0cdf = 229575903

 Commands leading to the command that caused the error were:
 CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
 -- -- -- -- -- -- -- --  ----------------  --------------------
 c8 00 01 df 0c af fd 00      00:02:27.781  READ DMA
 c8 00 20 df 0c af fd 00      00:02:27.777  READ DMA
 c8 00 10 ff 44 b0 fd 00      00:02:27.769  READ DMA
 c8 00 04 f7 40 b0 fd 00      00:02:27.763  READ DMA
 c8 00 04 ef 40 b0 fd 00      00:02:27.754  READ DMA

Error 50 occurred at disk power-on lifetime: 56 hours (2 days + 8 hours)
When the command that caused the error occurred, the device was active or idle.

 After command completion occurred, registers were:
 ER ST SC SN CL CH DH
 -- -- -- -- -- -- --
40 51 20 df 0c af fd Error: UNC 32 sectors at LBA = 0x0daf0cdf = 229575903

 Commands leading to the command that caused the error were:
 CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
 -- -- -- -- -- -- -- --  ----------------  --------------------
 c8 00 20 df 0c af fd 00      00:02:27.781  READ DMA
 c8 00 10 ff 44 b0 fd 00      00:02:27.777  READ DMA
 c8 00 04 f7 40 b0 fd 00      00:02:27.769  READ DMA
 c8 00 04 ef 40 b0 fd 00      00:02:27.763  READ DMA
 c8 00 04 7b 35 b0 fd 00      00:02:27.754  READ DMA

Error 49 occurred at disk power-on lifetime: 56 hours (2 days + 8 hours)
When the command that caused the error occurred, the device was active or idle.

 After command completion occurred, registers were:
 ER ST SC SN CL CH DH
 -- -- -- -- -- -- --
 40 51 01 df 0c af fd  Error: UNC 1 sectors at LBA = 0x0daf0cdf = 229575903

 Commands leading to the command that caused the error were:
 CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
 -- -- -- -- -- -- -- --  ----------------  --------------------
 c8 00 01 df 0c af fd 00      00:01:31.550  READ DMA
 c8 00 80 df 0c af fd 00      00:01:31.548  READ DMA
 c8 00 80 5f 0c af fd 00      00:01:31.546  READ DMA
 c8 00 80 df 0b af fd 00      00:01:31.545  READ DMA
 c8 00 80 5f 0b af fd 00      00:01:31.535  READ DMA

Error 48 occurred at disk power-on lifetime: 56 hours (2 days + 8 hours)
When the command that caused the error occurred, the device was active or idle.

 After command completion occurred, registers were:
 ER ST SC SN CL CH DH
 -- -- -- -- -- -- --
40 51 80 df 0c af fd Error: UNC 128 sectors at LBA = 0x0daf0cdf = 229575903

 Commands leading to the command that caused the error were:
 CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
 -- -- -- -- -- -- -- --  ----------------  --------------------
 c8 00 80 df 0c af fd 00      00:01:31.550  READ DMA
 c8 00 80 5f 0c af fd 00      00:01:31.548  READ DMA
 c8 00 80 df 0b af fd 00      00:01:31.546  READ DMA
 c8 00 80 5f 0b af fd 00      00:01:31.545  READ DMA
 c8 00 80 df 0a af fd 00      00:01:31.535  READ DMA



Matt Juszczak wrote:

Hi all,

I recently bought a 160 gig hard drive at the store after my 40 gig started failing with similar messages to the ones below. The 40 gig eventually actually died after a few days (as in click click, boom, no longer detecting).

Now the 160 GB is giving me fsck errors all of a sudden, as seen below. Is my luck just that bad? Is the drive in the store also bad? This just seems like it could be a bad controller or something too, since its happened to two drives in a row...... and one of them was a new drive.

Any ideas would be appreciated.... if I'm gonna take the drive back to the store, I'd like to do it soon.

Regards,

Matt Juszczak



Mounting root from ufs:/dev/ad0s1a
WARNING: /tmp was not properly dismounted
WARNING: /usr was not properly dismounted
WARNING: /var was not properly dismounted
WARNING: /hd2 was not properly dismounted
ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> LBA=2 29575903 ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> LBA=2 29575903 ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> LBA=2 29575903 ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> LBA=2 29575903 ad1: FAILURE - READ_DMA status=51<READY,DSC,ERROR> error=40<UNCORRECTABLE> LBA=2 29575903

_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


!DSPAM:432ffb0e33195578212324!


_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to