February 19, 20224 yr Hi! I'm quite new to unRAID - I built my server last spring but haven't used it much. After a couple of power shortages, I noticed that one of my four disks has a red X and says "Device is disabled, content emulated". I have tried the following guides: https://wiki.unraid.net/Manual/Storage_Management#Checking_a_File_System https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui Doing the xfs_repair didn't yield very much. Here are the logs: xfs_repair -nv from the web GUI: Phase 1 - find and verify superblock... - block cache size set to 1507224 entries Phase 2 - using internal log - zero log... zero_log: head block 106467 tail block 106467 - 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 = 1 - agno = 0 - agno = 3 - agno = 2 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. XFS_REPAIR Summary Sat Feb 19 11:49:51 2022 Phase Start End Duration Phase 1: 02/19 11:49:45 02/19 11:49:45 Phase 2: 02/19 11:49:45 02/19 11:49:45 Phase 3: 02/19 11:49:45 02/19 11:49:48 3 seconds Phase 4: 02/19 11:49:48 02/19 11:49:48 Phase 5: Skipped Phase 6: 02/19 11:49:48 02/19 11:49:51 3 seconds Phase 7: 02/19 11:49:51 02/19 11:49:51 Total run time: 6 seconds xfs_repair -v from the web GUI: Phase 1 - find and verify superblock... - block cache size set to 1507224 entries Phase 2 - using internal log - zero log... zero_log: head block 106467 tail block 106467 - scan filesystem freespace and inode maps... - found root inode chunk Phase 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 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 1 - agno = 2 - agno = 3 - agno = 0 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - 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 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... XFS_REPAIR Summary Sat Feb 19 11:53:49 2022 Phase Start End Duration Phase 1: 02/19 11:53:42 02/19 11:53:43 1 second Phase 2: 02/19 11:53:43 02/19 11:53:43 Phase 3: 02/19 11:53:43 02/19 11:53:46 3 seconds Phase 4: 02/19 11:53:46 02/19 11:53:46 Phase 5: 02/19 11:53:46 02/19 11:53:46 Phase 6: 02/19 11:53:46 02/19 11:53:49 3 seconds Phase 7: 02/19 11:53:49 02/19 11:53:49 Total run time: 7 seconds done I don't see anything helpful here, except the mention of lost+found. But I cannot find any lost+found folder on the disk. Where is it supposed to be located? How can I find out what is wrong, so that I can fix it? Is the next step really redoing a drive formatted with XFS? Isn't there any other log or diagnostics to run? The disks were new when I pruchased them last year, and haven't been used much. I'd appreciate any help!
February 19, 20224 yr Community Expert 10 minutes ago, Reyhn said: Isn't there any other log or diagnostics to run? Unraid has a GUI option under Tools->Diagnostics
February 19, 20224 yr Community Expert 5 hours ago, Reyhn said: But I cannot find any lost+found folder on the disk. Where is it supposed to be located? If the repair has been completely successful then you do not end up with a lost+foundfolder. have you tried stopping the array and restarting in normal mode. I would expect that you will now get a successful mount.
February 19, 20224 yr 6 hours ago, Reyhn said: After a couple of power shortages, I noticed that one of my four disks has a red X and says "Device is disabled, content emulated". That is not a problem with the file system, the disk needs to be rebuilt. I’m a bit rusty so I don’t dare provide instructions for that at the moment.
February 19, 20224 yr Community Expert Solution 27 minutes ago, gubbgnutten said: That is not a problem with the file system, the disk needs to be rebuilt. I’m a bit rusty so I don’t dare provide instructions for that at the moment. The process is covered here in the online documentations accessible via the ‘Manual’ link at the bottom of the GUI.
February 28, 20224 yr Author On 2/19/2022 at 12:28 PM, Michael_P said: Unraid has a GUI option under Tools->Diagnostics Thanks a lot for that! Great thinking of the developers to easily download everything like that! A great plus for UNRAID! 🙂
February 28, 20224 yr Author On 2/19/2022 at 6:13 PM, itimpi said: If the repair has been completely successful then you do not end up with a lost+foundfolder. have you tried stopping the array and restarting in normal mode. I would expect that you will now get a successful mount. OK, so no lost+found is a good thing, then 🙂 I already tried that, but I stopped the array then restarted it in normal mode several times, but nothing changed. It did not mount successfully by itself.
February 28, 20224 yr Author On 2/19/2022 at 7:27 PM, itimpi said: The process is covered here in the online documentations accessible via the ‘Manual’ link at the bottom of the GUI. Following that procedure was the solution for me. I ran the parity-check, which completed without any errors. Then I ran the SMART extended tests without any errors. I did not find any errors anywhere, which gave me the confidence to proceed with a rebuild: I stopped the array, unassigned the red-X:ed drive, started the array, checked the emulated contents, stopped the array, assigned the drive back and finally started the array once more. It's now rebuilding. Done in seven hours.
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.