May 20, 20251 yr Hey allI am also having this problem where the disk shows as unmountable:wrong or no filesystem.But when I run filecheck it shows no corruption.Also when in maintenance mode it does not show this error.Any help would be appreciated
May 21, 20251 yr Community Expert 7 hours ago, Fence said:I am also having this problem where the disk shows as unmountable:wrong or no filesystem.Please post the diagnostics.
May 21, 20251 yr Here is a fresh diagnostic, I don't know if that helpstower-diagnostics-20250521-2159.zip
May 21, 20251 yr Community Expert Start the array in maintenance mode and post the output from:xfs_repair -v /dev/md11p1
May 21, 20251 yr Phase 1 - find and verify superblock... - block cache size set to 690952 entriesPhase 2 - using internal log - zero log...zero_log: head block 536 tail block 536 - scan filesystem freespace and inode maps... - found root inode chunkPhase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - process newly discovered inodes...Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 3 - agno = 2 - agno = 1 - agno = 0 - agno = 6 - agno = 4 - agno = 5 - agno = 7Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - reset superblock...Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - traversal finished ... - moving disconnected inodes to lost+found ...Phase 7 - verify and correct link counts...Maximum metadata LSN (13:560) is ahead of log (13:536).Format log to cycle 16.
May 21, 20251 yr Community Expert I would expect that starting the array in Normal mode would now result in disk11 mounting fine and showing all its data.
May 21, 20251 yr Community Expert xfs is still detecting corruption:May 22 00:15:58 Tower kernel: XFS (md11p1): Filesystem needs repair. Please run xfs_repair.May 22 00:15:58 Tower root: mount: /mnt/disk11: mount() failed: Structure needs cleaning.But if xfs_repair cannot fix it, I'm afraid that not much more we can do, you need to ask for help on the xfs mailing list or use a file recovery app like UFS explorer.Don't think that's the issue, but to rule out any Unraid driver issue, you can see if the disk mounts outside the array:stop the arraytype mkdir /x, thenmount -t xfs /dev/sdg1 /x
May 21, 20251 yr root@Tower:~# mkdir /xroot@Tower:~# mount -t xfs /dev/sdg1 /xmount: /x: mount() failed: Structure needs cleaning. dmesg(1) may have more information after failed mount system call.
May 21, 20251 yr Community Expert 1 hour ago, Fence said:Should I replace the disk and rebuild from parity ?Parity doesn't typically help with filesystem issues, you can see if it helps by just disabling the disk, stop array, unassign the disk, start the array, but note that it will make the array unprotected until the rebuild is done, and like mentioned, most likely it won't help.
May 21, 20251 yr The drive was fine when I powered down the server , do you think this might be an Unraid issue as I have had several issues in the last few months for no reason
May 22, 20251 yr Thanks for your help Jorge , I will try doing a rebuild otherwise I just have to see whats missing and go to the backup.
May 23, 20251 yr Author Some not so great news! Got some more errors at random and followed the following process:"Stop the array, unassign the disk, start the array in maintenance mode, stop it again, reassign the drive to the same slot. The idea is to start the array temporarily with the drive “missing” so it changes from “disabled” to “emulated” status, then to stop it and “replace” the drive to get it back to “active” status."Like before, however upon restarting the array I had the below:3 unmountable drives.... currently my server is rebuilding, should I be worried about this? Unfortunately I have to wait 24hours for it to sort itself out before I see how the rebuilding process went.datavault972-diagnostics-20250523-2047.zip
May 24, 20251 yr Community Expert Rebuilding an unmountable disk will result in an unmountable disk, not much point, and you can destroy the good filesystem, there are errors in multiple disks, check/replace cables for those disks, especially anything they have in common, like a power splitter or miniSAS cable, then post new diags after array start.
May 28, 20251 yr Author Hi @JorgeB sorry I missed your post as I was away and when I had come back (on sunday) my array was fine after letting it rebuild. However now my PArity drive is disabled.I have tried un-assigning and reassigning the drive while stopping the array but that has not solved the problem. attached are my diags.For added context my setup is as follows:Server:Lenovo M90si7 10700 @ 2.9ghz16gb DDR4 I have 12HDDs connected to the PC via MINI SAS SFF 8644 cables to an LSI 9206-16e SAS HBA card.I use normal 15 pin splitter cables to power the HDDs and they are all powered by a high quality brand name (can't remember it right now) PSUOn 5/24/2025 at 8:43 AM, JorgeB said:Rebuilding an unmountable disk will result in an unmountable disk, not much point, and you can destroy the good filesystem, there are errors in multiple disks, check/replace cables for those disks, especially anything they have in common, like a power splitter or miniSAS cable, then post new diags after array start.datavault972-diagnostics-20250528-1842.zip
May 28, 20251 yr Community Expert 23 minutes ago, Tuntira said:I have tried un-assigning and reassigning the drive while stopping the array but that has not solved the problem.You have to unassign, start array, stop array, re-assign, start array.
July 13, 2025Jul 13 Author HI all,I'm having more issues with my server. On Friday I had one of my discs give me the "Disk is disabled" error. So I stopped array, put it in maintenance mode and tried to fix it. Unfortunately I now have ANOTHER disc giving me the issue (a different one). I've added the logs to this post. Any help would be appreciated. I am starting to think that it is something other than my HDDs datavault972-diagnostics-20250713-2048.zip
July 14, 2025Jul 14 Community Expert Check/replace cables for disk2 and post new diags after array start.
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.