February 10, 20224 yr Hey, i work with unraid for 17 days now and it worked good for me. Tonight i got some Errors from Disk 1. Can someone please help? SMART Error Log Version: 1 ATA Error Count: 66 (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 66 occurred at disk power-on lifetime: 424 hours (17 days + 16 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 -- -- -- -- -- -- -- 04 61 46 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 46 00 00 00 a0 08 14d+14:50:26.171 SET FEATURES [Set transfer mode] ec 00 00 00 00 00 a0 08 14d+14:50:26.170 IDENTIFY DEVICE ec 00 00 00 00 00 a0 08 14d+14:50:26.157 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 14d+14:50:26.156 SET FEATURES [Set transfer mode] Error 65 occurred at disk power-on lifetime: 424 hours (17 days + 16 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 -- -- -- -- -- -- -- 04 61 46 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 46 00 00 00 a0 08 14d+14:50:26.156 SET FEATURES [Set transfer mode] ec 00 00 00 00 00 a0 08 14d+14:50:26.155 IDENTIFY DEVICE ec 00 00 00 00 00 a0 08 14d+14:50:26.148 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 14d+14:50:26.147 SET FEATURES [Set transfer mode] Error 64 occurred at disk power-on lifetime: 424 hours (17 days + 16 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 -- -- -- -- -- -- -- 04 61 46 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 46 00 00 00 a0 08 14d+14:50:26.147 SET FEATURES [Set transfer mode] ec 00 00 00 00 00 a0 08 14d+14:50:26.146 IDENTIFY DEVICE ec 00 00 00 00 00 a0 08 14d+14:50:26.141 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 14d+14:50:26.140 SET FEATURES [Set transfer mode] Error 63 occurred at disk power-on lifetime: 424 hours (17 days + 16 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 -- -- -- -- -- -- -- 04 61 46 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 46 00 00 00 a0 08 14d+14:50:26.140 SET FEATURES [Set transfer mode] ec 00 00 00 00 00 a0 08 14d+14:50:26.139 IDENTIFY DEVICE ec 00 00 00 00 00 a0 08 14d+14:50:26.132 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 14d+14:50:26.131 SET FEATURES [Set transfer mode] Error 62 occurred at disk power-on lifetime: 424 hours (17 days + 16 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 -- -- -- -- -- -- -- 04 61 46 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 46 00 00 00 a0 08 14d+14:50:26.131 SET FEATURES [Set transfer mode] ec 00 00 00 00 00 a0 08 14d+14:50:26.130 IDENTIFY DEVICE ec 00 00 00 00 00 a0 08 14d+14:50:26.124 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 14d+14:50:26.123 SET FEATURES [Set transfer mode] SMART Extended Self-test Log (GP Log 0x07) not supported SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] Selective Self-tests/Logging not supported Hope you can help me.
February 10, 20224 yr Community Expert Disk is fine, connection problems. Check connections, both ends, SATA and power, including splitters. Emulated disk1 mounts, you can rebuild the disk to itself. https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself
February 10, 20224 yr Author Thank you very much! Seems to work. I have changed the Sata Cables to shorter ones and did it after the wiki. One Last question. Is somewhere discribed how to interpret the smart log-files? Would be helpfull for the future
February 11, 20224 yr Community Expert You can see which SMART attributes Unraid monitors by default in Disk Settings. For any WD disks, you should also monitor 1 and 200. Unraid will give a SMART warning on the Dashboard page for each disk for these monitored attributes. You can also click on each disk and go to its Attributes and these would be highlighted. You can run an extended SMART test. I could see from the SMART report in your diagnostics that you had already just finished doing that test. Your syslog is where the connection problems appeared. Setup Notifications to alert you immediately by email or other agent as soon as a problem is detected.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.