February 6, 201313 yr Hi Just built my first sever after getting annoyed by my drobo. I brought 2 new 3tb drives and precleared them once each, but after looking at the SMART status i am rather worried. I have attached a screen grab of what i am seeing and SMART reports. I think my parity drive is not well, is this right? Lloyd Parity.txt Disk1.txt
February 6, 201313 yr Click on the sm link. When disk the last ATA error occur? Reseat or replace the SATA cable.
February 7, 201313 yr Author Hi, the errors all occured during a parity check i will use a different sata cable just to make sure Error 12 occurred at disk power-on lifetime: 183 hours (7 days + 15 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 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 08:09:26.770 READ DMA EXT 27 00 00 00 00 00 e0 00 08:09:26.769 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 08:09:26.745 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 08:09:26.726 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 08:09:26.705 READ NATIVE MAX ADDRESS EXT
February 7, 201313 yr Hi, the errors all occured during a parity check i will use a different sata cable just to make sure Error 12 occurred at disk power-on lifetime: 183 hours (7 days + 15 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 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 00 ff ff ff ef 00 08:09:26.770 READ DMA EXT 27 00 00 00 00 00 e0 00 08:09:26.769 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 a0 00 08:09:26.745 IDENTIFY DEVICE ef 03 46 00 00 00 a0 00 08:09:26.726 SET FEATURES [set transfer mode] 27 00 00 00 00 00 e0 00 08:09:26.705 READ NATIVE MAX ADDRESS EXT This is an UNC error reported by the disk, not a CRC error detected by the disk controller or disk electronics. A cable would not be the cause. UNC = UN-Correctable read error of a sector (data on disk sector does not match its affiliated checksum at the end of the sector) CRC = cyclic redundancy check on communications across the cable to/from the drive. Get a "smart" report from the drive. Odds are very high you have a sector pending re-allocation. Joe L.
February 7, 201313 yr Author Hi Joe There is a smart report attached to my initial post if this helps. It shows 20 Reported_Uncorrected, which i assume is the same. Lloyd
February 7, 201313 yr Hi Joe There is a smart report attached to my initial post if this helps. It shows 20 Reported_Uncorrected, which i assume is the same. Lloyd The SMART report was for disk1. The the screen capture shows sector errors on the parity drive and /dev/sdg Get smart reports for those drives.
February 7, 201313 yr I had the same errors on a Seagate 1T drive but not the same counts. Ran the disk for 4.5 years and replaced it still working. Run another check and see what happens with it. I'd be more concerned about the pending sectors on sdg.
February 7, 201313 yr Author All the drives not in the array are in the proccess of being precleared so hopefully that should give the drive chance to reassign them
Archived
This topic is now archived and is closed to further replies.