jo-sebove

My spare disk has now some usage! Thank you everyone for your support, I really appreciate. 👍

The only other information provided is this one :"Completed: read failure"

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?

The rebuild has finished without issue. I still wonder what happened to this disck, do you think it is salvageable?

I have a spare drive I will tri rebuilding on the spare drive since the emulated data looks fine.

I have swap every single cable, and took pictures of the bios drive statuts:

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

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.

Here it comes! unraid-diagnostics-20250401-1852.zip

No fix button has appeared after checking and the disk still shows as unmountable unraid-diagnostics-20250401-1140.zip

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.

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!