March 22, 20233 yr unRAID 6.9.1 1 parity drive I had 2 distinct drives fail over a period of 2 weeks. I rebuilt the first one successfully. And then the second drive failed (unreadable / unmountable) - it's possible that this drive was intermittently failing whilst the drives were being rebuilt. Since then all of the shares are still defined within UNRAID, but when accessed by anything they show as 0 files. Within the unRAID GUI it shows the size of the total array is correct and the size of the individual shares is correct. I'm thinking that there was a point at which there were actually 2 failed drives which then meant that the array was incomplete?? and that's why the shares are now showing as empty. I made all of the individual drive shares available and they appear to have the correct sizing (except for one of the repaired drives - disk 4) - which is totally empty 😐 Looking for options. It's mostly a media archive so the content isn't CRITICAL. I have the old "failing" drives, as well as another unRAID server which has SOME of the content on it. Options 1. Delete the array config and start again - presuming that I can use all the existing drives "as-is" and just recreate the shares (as the folders are still present - except for disk 4) and then attempt to copy back the content from the external (failed) drives 2. copy the content to the /disk 4 share? and see if that will get the rest of the shares to be available again? 3. something else to try and get the shares available again (open to suggestions) ctu-diagnostics-20230322-1824.zip
March 22, 20233 yr Community Expert Check filesystem on disk17, you should also update to latest stable.
March 22, 20233 yr Author Solution 2 hours ago, JorgeB said: Check filesystem on disk17, you should also update to latest stable. Thanks ...that picked up a lot of issues. May I ask what pointed you suggest that option?
March 22, 20233 yr Community Expert The syslog: Mar 22 14:19:50 ctu kernel: XFS (md17): Metadata corruption detected at xfs_dinode_verify+0xe6/0x581 [xfs], inode 0x80000080 dinode Mar 22 14:19:50 ctu kernel: XFS (md17): Unmount and run xfs_repair md17 is disk17
March 22, 20233 yr Author Thank you @JorgeB My content is visible on the network again - now I just have to restore the "empty" disk content from the old drive
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.