Kaydol

Flood göndermek, insanların floodlarını okumak ve diğer insanlarla bağlantı kurmak için sosyal Floodlar ve Flood Yanıtları Motorumuza kaydolun.

Oturum aç

Flood göndermek, insanların floodlarını okumak ve diğer insanlarla bağlantı kurmak için sosyal Floodlar ve Flood Yanıtları Motorumuza giriş yapın.

Şifremi hatırlamıyorum

Şifreni mi unuttun? Lütfen e-mail adresinizi giriniz. Bir bağlantı alacaksınız ve e-posta yoluyla yeni bir şifre oluşturacaksınız.

3 ve kadim dostu 1 olan sj'yi rakamla giriniz. ( 31 )

Üzgünüz, Flood yazma yetkiniz yok, Flood girmek için giriş yapmalısınız.

Lütfen bu Floodun neden bildirilmesi gerektiğini düşündüğünüzü kısaca açıklayın.

Lütfen bu cevabın neden bildirilmesi gerektiğini kısaca açıklayın.

Please briefly explain why you feel this user should be reported.

BBY 14TB Drive SMART Errors

Hello all, I scooped a few of the 14tb blackfriday drives from best buy to put my plex collection on, and replace the 3tb drives that I’ve been using. I ran the smartctl short test, long test, and a 24 hour test with stressdisk. After the 24 hour stressdisk run smartctl is reporting an error log on one of the drives.

Could you all help me understand what it’s talking about?

Should I return the drive?

Thanks!

SMART Error Log Version: 1
ATA Error Count: 130 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It “wraps” after 49.710 days.

Error 130 occurred at disk power-on lifetime: 49 hours (2 days + 1 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
— — — — — — —
10 51 00 00 86 6e 40 Error: IDNF at LBA = 0x006e8600 = 7243264

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ——————–
35 da 00 00 86 6e 40 00 2d+00:58:18.695 WRITE DMA EXT
35 da 00 00 85 6e 40 00 2d+00:57:48.643 WRITE DMA EXT
35 da 00 00 84 6e 40 00 2d+00:57:48.641 WRITE DMA EXT
35 da 00 00 83 6e 40 00 2d+00:57:48.639 WRITE DMA EXT
35 da 00 00 82 6e 40 00 2d+00:57:48.638 WRITE DMA EXT

Error 129 occurred at disk power-on lifetime: 48 hours (2 days + 0 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
— — — — — — —
10 51 00 00 9e 21 40 Error: IDNF at LBA = 0x00219e00 = 2203136

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ——————–
35 da 00 00 9e 21 40 00 2d+00:45:50.462 WRITE DMA EXT
35 da 00 00 9d 21 40 00 2d+00:45:20.382 WRITE DMA EXT
35 da 00 00 9c 21 40 00 2d+00:45:20.380 WRITE DMA EXT
35 da 00 00 9b 21 40 00 2d+00:45:20.378 WRITE DMA EXT
35 da 00 00 9a 21 40 00 2d+00:45:20.376 WRITE DMA EXT

Error 128 occurred at disk power-on lifetime: 48 hours (2 days + 0 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
— — — — — — —
10 51 00 00 10 55 40 Error: IDNF at LBA = 0x00551000 = 5574656

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ——————–
35 da 00 00 10 55 40 00 2d+00:43:15.667 WRITE DMA EXT
35 da 00 00 0f 55 40 00 2d+00:42:45.614 WRITE DMA EXT
35 da 00 00 0e 55 40 00 2d+00:42:45.612 WRITE DMA EXT
35 da 00 00 0d 55 40 00 2d+00:42:45.610 WRITE DMA EXT
35 da 00 00 0c 55 40 00 2d+00:42:45.607 WRITE DMA EXT

Error 127 occurred at disk power-on lifetime: 48 hours (2 days + 0 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
— — — — — — —
10 51 00 00 59 2c 40 Error: IDNF at LBA = 0x002c5900 = 2906368

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ——————–
35 da 00 00 59 2c 40 00 2d+00:38:18.039 WRITE DMA EXT
35 da 00 00 58 2c 40 00 2d+00:37:48.022 WRITE DMA EXT
35 da 00 00 57 2c 40 00 2d+00:37:48.020 WRITE DMA EXT
35 da 00 00 56 2c 40 00 2d+00:37:48.015 WRITE DMA EXT
35 da 00 00 55 2c 40 00 2d+00:37:48.013 WRITE DMA EXT

Error 126 occurred at disk power-on lifetime: 48 hours (2 days + 0 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
— — — — — — —
10 51 00 00 6a 9f 40 Error: IDNF at LBA = 0x009f6a00 = 10447360

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
— — — — — — — — —————- ——————–
35 da 00 00 6a 9f 40 00 2d+00:32:22.167 WRITE DMA EXT
35 da 00 00 69 9f 40 00 2d+00:31:52.123 WRITE DMA EXT
35 da 00 00 68 9f 40 00 2d+00:31:52.119 WRITE DMA EXT
35 da 00 00 67 9f 40 00 2d+00:31:52.117 WRITE DMA EXT
35 da 00 00 66 9f 40 00 2d+00:31:52.116 WRITE DMA EXT

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 49 –
# 2 Extended offline Completed without error 00% 23 –
# 3 Short offline Completed without error 00% 0 –

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Benzer Yazılar

Yorum eklemek için giriş yapmalısınız.

1 Yorumu

  1. Do you have the aggregate smart attributes?

    It may be fine, could be a messy power off right after a short test was run at 48 hours life or something