February 22, 20251 yr I noticed I was getting some errors with my cache drive (reallocated sector count is 244) and thought it would be smart to move all of my shares over to the array so that I could replace the cache drive. I set all my shares to cache->array. After having issues with my mover after updating to 7.0.0, I removed the Mover tuning plugin and the mover finally started to work. However, I woke up today and now it appears that my entire array is set to read-only... I am not sure what to do, I am a novice when it comes to Unraid, using it mainly as a Plex server and to store important files. I ran a SMART short self-test on the cache drive and here were the results: 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: 8460 hours (352 days + 12 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 a8 30 73 1c 40 Error: UNC at LBA = 0x001c7330 = 1864496 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 08 a8 30 73 1c 40 15 9d+04:27:20.485 READ FPDMA QUEUED 2f 00 01 30 03 00 40 0f 9d+04:27:20.485 READ LOG EXT 2f 00 01 30 00 00 40 0f 9d+04:27:20.485 READ LOG EXT 2f 00 01 00 00 00 40 0f 9d+04:27:20.485 READ LOG EXT 2f 00 01 30 00 00 40 0f 9d+04:27:20.485 READ LOG EXT Error 129 occurred at disk power-on lifetime: 8460 hours (352 days + 12 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 78 30 73 1c 40 Error: UNC at LBA = 0x001c7330 = 1864496 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 08 78 30 73 1c 40 0f 9d+04:27:20.314 READ FPDMA QUEUED 2f 00 01 30 03 00 40 03 9d+04:27:20.314 READ LOG EXT 2f 00 01 30 00 00 40 03 9d+04:27:20.314 READ LOG EXT 2f 00 01 00 00 00 40 03 9d+04:27:20.314 READ LOG EXT 2f 00 01 30 00 00 40 03 9d+04:27:20.314 READ LOG EXT Error 128 occurred at disk power-on lifetime: 8460 hours (352 days + 12 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 18 30 73 1c 40 Error: UNC at LBA = 0x001c7330 = 1864496 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 08 18 30 73 1c 40 03 9d+04:27:20.148 READ FPDMA QUEUED 60 08 10 28 73 1c 40 02 9d+04:27:20.148 READ FPDMA QUEUED 60 08 08 20 73 1c 40 01 9d+04:27:20.148 READ FPDMA QUEUED 60 08 00 18 73 1c 40 00 9d+04:27:20.148 READ FPDMA QUEUED 60 08 f0 10 73 1c 40 1e 9d+04:27:20.148 READ FPDMA QUEUED Error 127 occurred at disk power-on lifetime: 8460 hours (352 days + 12 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 38 60 6f 1c 40 Error: UNC at LBA = 0x001c6f60 = 1863520 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 08 38 60 6f 1c 40 07 9d+04:27:19.242 READ FPDMA QUEUED 60 00 30 60 ad 1c 40 06 9d+04:27:19.242 READ FPDMA QUEUED 2f 00 01 30 03 00 40 16 9d+04:27:19.242 READ LOG EXT 2f 00 01 30 00 00 40 16 9d+04:27:19.242 READ LOG EXT 2f 00 01 00 00 00 40 16 9d+04:27:19.242 READ LOG EXT Error 126 occurred at disk power-on lifetime: 8460 hours (352 days + 12 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 b0 60 6f 1c 40 Error: UNC at LBA = 0x001c6f60 = 1863520 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 08 b0 60 6f 1c 40 16 9d+04:27:18.984 READ FPDMA QUEUED 60 00 a8 60 ad 1c 40 15 9d+04:27:18.984 READ FPDMA QUEUED 60 00 a0 60 a3 1c 40 14 9d+04:27:18.984 READ FPDMA QUEUED 2f 00 01 30 03 00 40 1a 9d+04:27:18.984 READ LOG EXT 2f 00 01 30 00 00 40 1a 9d+04:27:18.984 READ LOG EXT I ran SMART self-tests on my 3 array drives and my parity drive as well. Drive 3 of the array had these errors: ATA Error Count: 4 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 4 occurred at disk power-on lifetime: 6029 hours (251 days + 5 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 -- -- -- -- -- -- -- 84 43 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 b8 50 88 80 a4 40 08 2d+07:00:10.868 READ FPDMA QUEUED 60 88 48 00 7f a4 40 08 2d+07:00:10.866 READ FPDMA QUEUED 60 40 40 c0 79 a4 40 08 2d+07:00:10.861 READ FPDMA QUEUED 60 40 38 80 74 a4 40 08 2d+07:00:10.860 READ FPDMA QUEUED 61 a0 30 a0 6a a4 40 08 2d+07:00:10.858 WRITE FPDMA QUEUED Error 3 occurred at disk power-on lifetime: 1640 hours (68 days + 8 hours) When the command that caused the error occurred, the device was doing SMART Offline or Self-test. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 43 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 40 90 38 9d 6a 40 08 2d+20:07:16.930 READ FPDMA QUEUED 60 40 88 f8 97 6a 40 08 2d+20:07:16.925 READ FPDMA QUEUED 60 40 80 b8 92 6a 40 08 2d+20:07:16.922 READ FPDMA QUEUED 60 40 78 78 8d 6a 40 08 2d+20:07:16.920 READ FPDMA QUEUED 60 40 70 38 88 6a 40 08 2d+20:07:16.917 READ FPDMA QUEUED Error 2 occurred at disk power-on lifetime: 1633 hours (68 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 -- -- -- -- -- -- -- 84 43 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 40 88 60 13 46 40 08 2d+13:43:39.316 READ FPDMA QUEUED 60 40 80 20 13 46 40 08 2d+13:43:39.298 READ FPDMA QUEUED 60 40 78 e0 0d 46 40 08 2d+13:43:39.298 READ FPDMA QUEUED 60 40 70 a0 08 46 40 08 2d+13:43:39.298 READ FPDMA QUEUED 60 40 68 60 03 46 40 08 2d+13:43:39.296 READ FPDMA QUEUED Error 1 occurred at disk power-on lifetime: 527 hours (21 days + 23 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 -- -- -- -- -- -- -- 84 43 00 00 00 00 00 Error: ICRC, ABRT at LBA = 0x00000000 = 0 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 60 40 50 90 46 9f 40 08 6d+04:22:09.734 READ FPDMA QUEUED 60 80 58 d0 4b 9f 40 08 6d+04:22:09.713 READ FPDMA QUEUED 60 40 48 50 41 9f 40 08 6d+04:22:09.713 READ FPDMA QUEUED 60 40 40 10 3c 9f 40 08 6d+04:22:09.713 READ FPDMA QUEUED 60 40 38 d0 36 9f 40 08 6d+04:22:09.713 READ FPDMA QUEUED Update as I am writing all of this, I stopped the array and rebooted the server. After running the SMART tests on all the drives I started up the array and now I can write to my shares again. And I just realized that I reboot before capturing the syslog.. So I'll probably never know what happened. Still a little freaked out and not sure what happened. Should I buy a replacement SSD for my cache? How do I make sure I get all the files off of my previous cache? Looks like even after running that mover, ~120gb of files remained on the cache. Just want to make sure I do things properly and don't experience any data loss. Thanks!
February 23, 20251 yr Community Expert If it happens again, grab the diags before rebooting, or if you have a recent Unraid release and the save syslog to flash drive on reboot is active, it can still be in the diags as syslog-previous.
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.