February 23, 20233 yr Last night I was having some issues with my dockers, and I just bounced the unraid instance. when it came back, the cache pool was missing one of the members (2 member ssd pool.) I started clicking around trying to see what my options where. I was trying to remove one of the members, so that it would start up with the single drive, but it seemed to live updated. so I had clicked to remove that pool, but I tried to add it back and add my single drive with 1 member of pool (the non-failed ssd). after a reboot there, it says that the drive is unmountable, and now I don't have any of my cache data. what are the next steps? waldorf-diagnostics-20230223-0858.zip
February 23, 20233 yr Community Expert On mobile now so haven't looked at diagnostics yet. 7 minutes ago, PatrickRobbins said: bounced the unraid instance. Do you mean you are running Unraid in a VM?
February 23, 20233 yr Author 4 minutes ago, trurl said: On mobile now so haven't looked at diagnostics yet. Do you mean you are running Unraid in a VM? Sorry, no. I just restarted via the web Gui.
February 23, 20233 yr Author I think that I had a typical 2 issue problem. I had turned on VMs and tried out some new OS images, and that was keeping my system from bringing up the webui after a reboot. I have turned off VMs currently and got the sytem back up and running, and after a few reboots have the system up and running. I think that I just have to replace one of my cache drives. it is throwing many smart errors. (it showed back up in the system eventually.)
February 23, 20233 yr Author Warning: ATA error count 46 inconsistent with error log pointer 5 ATA Error Count: 46 (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 46 occurred at disk power-on lifetime: 5537 hours (230 days + 17 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 41 f8 e8 59 db 40 Error: UNC at LBA = 0x00db59e8 = 14375400 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 50 f8 e8 59 db 40 08 18d+16:00:40.851 READ FPDMA QUEUED 61 08 88 e0 59 db 40 08 18d+16:00:40.589 WRITE FPDMA QUEUED 61 08 80 d8 59 db 40 08 18d+16:00:40.589 WRITE FPDMA QUEUED 61 08 10 d0 59 db 40 08 18d+16:00:40.589 WRITE FPDMA QUEUED 61 08 b8 c8 59 db 40 08 18d+16:00:40.589 WRITE FPDMA QUEUED Error 45 occurred at disk power-on lifetime: 5410 hours (225 days + 10 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 41 d8 18 86 82 40 Error: UNC at LBA = 0x00828618 = 8554008 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 d8 18 86 82 40 08 13d+09:30:49.381 READ FPDMA QUEUED 60 68 d0 b0 85 82 40 08 13d+09:30:48.119 READ FPDMA QUEUED 60 00 c8 b0 84 82 40 08 13d+09:30:48.118 READ FPDMA QUEUED 60 40 c0 70 84 82 40 08 13d+09:30:48.117 READ FPDMA QUEUED 60 a0 b8 d0 83 82 40 08 13d+09:30:48.114 READ FPDMA QUEUED Error 44 occurred at disk power-on lifetime: 5410 hours (225 days + 10 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 41 68 78 71 82 40 Error: UNC at LBA = 0x00827178 = 8548728 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 00 68 78 71 82 40 08 13d+09:30:47.755 READ FPDMA QUEUED 60 40 60 38 71 82 40 08 13d+09:30:47.247 READ FPDMA QUEUED 60 58 58 d0 de 6b 40 08 13d+09:30:47.242 READ FPDMA QUEUED 60 40 50 90 de 6b 40 08 13d+09:30:47.242 READ FPDMA QUEUED 60 00 40 b0 6e 82 40 08 13d+09:30:47.236 READ FPDMA QUEUED Error 43 occurred at disk power-on lifetime: 5369 hours (223 days + 17 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 41 60 58 fd b9 40 Error: UNC at LBA = 0x00b9fd58 = 12189016 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 80 60 58 fd b9 40 08 11d+16:00:35.154 READ FPDMA QUEUED 61 08 10 50 fd b9 40 08 11d+16:00:35.014 WRITE FPDMA QUEUED 61 08 78 48 fd b9 40 08 11d+16:00:35.014 WRITE FPDMA QUEUED 61 08 d8 40 fd b9 40 08 11d+16:00:35.014 WRITE FPDMA QUEUED 61 08 08 38 fd b9 40 08 11d+16:00:35.014 WRITE FPDMA QUEUED Error 42 occurred at disk power-on lifetime: 5237 hours (218 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 -- -- -- -- -- -- -- 40 41 68 90 23 a1 40 Error: UNC at LBA = 0x00a12390 = 10560400 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 68 90 23 a1 40 08 6d+03:59:29.842 READ FPDMA QUEUED 60 08 60 08 24 a1 40 08 6d+03:59:29.335 READ FPDMA QUEUED 06 01 01 00 00 00 a0 08 6d+03:59:29.326 DATA SET MANAGEMENT 60 58 58 c8 bf e3 40 08 6d+03:59:29.325 READ FPDMA QUEUED 60 20 50 a8 bf e3 40 08 6d+03:59:29.325 READ FPDMA QUEUED
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.