March 31, 20251 yr Hello every one, I'm ask for some help because today one of my array disk has suddenly been showed as unmountable. I applied the "drive show as unmountable" then the "checking a file system" until de the point 8. procedure from Unraid documentation. The test procedure show me this result : No file system corruption detected Here is the log of the check: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 2 - agno = 3 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. It went very quick, I cannot imagine that there were any relevant check done... I appriciate your help on this topic! Edited March 31, 20251 yr by jo-sebove
April 1, 20251 yr Community Expert 10 hours ago, jo-sebove said: It went very quick, I cannot imagine that there were any relevant check done... It is very quick if there is no serious issue. You need to run without -n to get any fix done (or use the Fix button if on Unraid 7).
April 1, 20251 yr Author 8 hours ago, itimpi said: It is very quick if there is no serious issue. You need to run without -n to get any fix done (or use the Fix button if on Unraid 7). Could you explain me what the -n means and where I can change this. I'm a beginner in Unraid use. And also I run Unraid 7 but don't see the "fix" button. Edited April 1, 20251 yr by trurl delete lots of attached files that should have been a single zip
April 1, 20251 yr Community Expert The diagnostics are a single zip file. Sounds as if you have your system set to automatically open zip files? You should upload the single zip file. 1 hour ago, jo-sebove said: Could you explain me what the -n means and where I can change this. I'm a beginner in Unraid use. And also I run Unraid 7 but don't see the "fix" button. On Unraid 6 you could provide the parameters for the xfs_repair and by default it added -n (which makes it a check without doing a repair). On Unraid 7 you do not provide parameters to xfs_repair after running the check from the GUI then if a repair is now required a Fix button should now appear.
April 1, 20251 yr Author No fix button has appeared after checking and the disk still shows as unmountable unraid-diagnostics-20250401-1140.zip
April 1, 20251 yr Community Expert Disk is mounted, it's also disabled, but that's a different issue, I don't see an extra disk being detected, what happened to old disk1?
April 1, 20251 yr Author I don't know what append to Disk1, it is still physically in the server and I din't do any thing but rebooting the server and starting the array in maintenance mode since the disk has been disable. I got a message with quite a few errors for the disk but has I came it was already disable.
April 1, 20251 yr Community Expert 2 hours ago, jo-sebove said: don't know what append to Disk1, it is still physically in the server Shutdown, check its connections, reboot, start the array in normal (not maintenance) mode, and post new diagnostics.
April 2, 20251 yr Author I have checked each connection wich seems to be fine and also switched every single cables and ports on the mother board ti see if the failure moves. It didn't changed any thing. unraid-diagnostics-20250402-1025.zip
April 2, 20251 yr Community Expert Swap cables between the missing disk and another one, then see if it's detected in the board BIOS, if not, it's likely dead.
April 2, 20251 yr Author I have swap every single cable, and took pictures of the bios drive statuts:
April 2, 20251 yr Community Expert Solution According to the last diagnostics you posted Unraid is seeing disk1 and the SMART information for it looks fine. If so then you can check that the data in the emulated disk1 looks correct, and if so clear the disabled status by Rebuilding the disk onto itself. If you have a spare disk then you can rebuild onto that drive instead keeping the original disk1 intact in case the rebuild fails for some reason as that gives additional recovery options.
April 2, 20251 yr Author I have a spare drive I will tri rebuilding on the spare drive since the emulated data looks fine.
April 2, 20251 yr Author The rebuild has finished without issue. I still wonder what happened to this disck, do you think it is salvageable?
April 2, 20251 yr Community Expert 56 minutes ago, jo-sebove said: I still wonder what happened to this disck, do you think it is salvageable? A disk can be disabled for many reasons other than the drive failing. You can run an extended SMART test on it and if it passes that without error it is probably fine.
April 4, 20251 yr Author I ran an extended SMART test and it shows there is in fact something wrong with the disk : ATA Error Count: 499 (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 499 occurred at disk power-on lifetime: 11202 hours (466 days + 18 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 41 80 10 28 7e 40 Error: Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- Error 498 occurred at disk power-on lifetime: 11185 hours (466 days + 1 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 00 00 00 00 00 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 -- -- -- -- -- -- -- -- ---------------- -------------------- Error 497 occurred at disk power-on lifetime: 11181 hours (465 days + 21 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 00 00 00 00 00 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 -- -- -- -- -- -- -- -- ---------------- -------------------- Error 496 occurred at disk power-on lifetime: 11171 hours (465 days + 11 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 00 00 00 00 00 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 -- -- -- -- -- -- -- -- ---------------- -------------------- Error 495 occurred at disk power-on lifetime: 11169 hours (465 days + 9 hours) When the command that caused the error occurred, the device was in an unknown state. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 00 00 00 00 00 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 -- -- -- -- -- -- -- -- ---------------- -------------------- Does it makes sense to tri repairing this disk?
April 4, 20251 yr Community Expert 6 hours ago, jo-sebove said: ran an extended SMART test The portion of the SMART report you posted doesn't show the result of the test. It's after the section you posted, and looks like this: SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 12369 -
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.