tidusjar Posted November 1, 2021 Share Posted November 1, 2021 (edited) Hi all, I've got the following error on the Main tab for one of my disks, but then another disk is showing as "Device is Disabled". This is all after a powercut I had yesterday. Attached is my diagnostics after starting the array Any idea what I need to do to resolve this? My disk/hardware knowledge is not great server-diagnostics-20211101-1109.zip Edited November 1, 2021 by tidusjar Quote Link to comment
JorgeB Posted November 1, 2021 Share Posted November 1, 2021 Disk4 dropped before disk1 started rebuilding, so rebuilt disk1 will be corrupt, was this done on top of the old disk or a new one? Problems with disks 1 and 4 look power/connection related, replace cables. Quote Link to comment
tidusjar Posted November 2, 2021 Author Share Posted November 2, 2021 So I’ve now replaced both disks cables and still no luck. any other suggestions? Quote Link to comment
trurl Posted November 2, 2021 Share Posted November 2, 2021 3 minutes ago, tidusjar said: replaced both disks cables Fixing the connection problem was required before you can fix disabled and/or unmountable, but fixing the connection won't fix disabled and/or unmountable. You still have more work to do. Attach new diagnostics to your NEXT post in this thread. Quote Link to comment
trurl Posted November 2, 2021 Share Posted November 2, 2021 Also, you didn't answer this question: On 11/1/2021 at 7:51 AM, JorgeB said: was this done on top of the old disk or a new one? Quote Link to comment
tidusjar Posted November 2, 2021 Author Share Posted November 2, 2021 Apologies. I’ve not replaced any drives. I didn’t even realise disk 1 was being rebuilt. When I noticed this error I did remove the disk and then re-add it which may have caused that? attached is the new diagnostics server-diagnostics-20211102-2128.zip Quote Link to comment
trurl Posted November 2, 2021 Share Posted November 2, 2021 Post a screenshot of Main - Array Operation. Quote Link to comment
tidusjar Posted November 2, 2021 Author Share Posted November 2, 2021 Here you go Quote Link to comment
trurl Posted November 2, 2021 Share Posted November 2, 2021 OK, that's what I thought from diagnostics but just wanted to make sure. Do you have a spare disk you can use to rebuild disk4? Quote Link to comment
tidusjar Posted November 3, 2021 Author Share Posted November 3, 2021 I do not currently have any spare. Do we think disk 1 is dead? Quote Link to comment
JorgeB Posted November 3, 2021 Share Posted November 3, 2021 Don't think there would be much point in rebuilding disk4, since disk1 is corrupt a rebuilt disk4 would also be corrupt, best bet is to do a new config to re-enable disk4, as for disk1 you can run a filesystem check but most likely there won't be much of use there. Quote Link to comment
tidusjar Posted November 3, 2021 Author Share Posted November 3, 2021 3 minutes ago, JorgeB said: Don't think there would be much point in rebuilding disk4, since disk1 is corrupt a rebuilt disk4 would also be corrupt, best bet is to do a new config to re-enable disk4, as for disk1 you can run a filesystem check but most likely there won't be much of use there. Ok So replace disk1 then? How do i do a new config to disk4? Is there a link on the wiki anywhere? Quote Link to comment
JorgeB Posted November 3, 2021 Share Posted November 3, 2021 1 hour ago, tidusjar said: So replace disk1 then? No, check filesystem. 1 hour ago, tidusjar said: How do i do a new config to disk4? -Tools -> New Config -> Retain current configuration: All -> Apply Then start array to begin a parity sync (or check parity is already valid before array start and then run a correcting check). Quote Link to comment
tidusjar Posted November 3, 2021 Author Share Posted November 3, 2021 23 minutes ago, JorgeB said: No, check filesystem. -Tools -> New Config -> Retain current configuration: All -> Apply Then start array to begin a parity sync (or check parity is already valid before array start and then run a correcting check). Filesystem check output: Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the 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. And Parity sync is now running Quote Link to comment
JorgeB Posted November 3, 2021 Share Posted November 3, 2021 32 minutes ago, tidusjar said: No modify flag set Once the sycn finishes run it again without -n or nothing will be done, did disk4 mount correctly? Quote Link to comment
tidusjar Posted November 3, 2021 Author Share Posted November 3, 2021 3 minutes ago, JorgeB said: Once the sycn finishes run it again without -n or nothing will be done, did disk4 mount correctly? Ok will do, As far as I'm aware disk4 is now in a correct state and no longer emulated too Quote Link to comment
JorgeB Posted November 3, 2021 Share Posted November 3, 2021 Didn't even noticed that the emulated disk4 was now mounting, so maybe disk1 can still be fixed, but kind of surprising due to all the errors during the rebuild. 1 Quote Link to comment
tidusjar Posted November 3, 2021 Author Share Posted November 3, 2021 Sync finished with 0 errors. For some reason there's no File System Check available for disk1 now. The option is completely missing. It appears for all of the other disks Here's a screenshot of Main Quote Link to comment
trurl Posted November 3, 2021 Share Posted November 3, 2021 It doesn't know what filesystem to check since that disk is FS=auto. Do you know what filesystem it is supposed to be? Quote Link to comment
trurl Posted November 3, 2021 Share Posted November 3, 2021 2 minutes ago, trurl said: Do you know what filesystem it is supposed to be? Looks like it was XFS according to your earlier diagnostics. Quote Link to comment
trurl Posted November 3, 2021 Share Posted November 3, 2021 You can check it from the command line. https://wiki.unraid.net/Manual/Storage_Management#Running_the_Test_using_the_command_line Quote Link to comment
tidusjar Posted November 3, 2021 Author Share Posted November 3, 2021 Done, yeah it was XFS I had to use the `-L` option as it was complaining Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - 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 = 0 - agno = 3 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (213:549485) is ahead of log (1:2). Format log to cycle 216. done Quote Link to comment
trurl Posted November 3, 2021 Share Posted November 3, 2021 Is the disk mountable now? Do you have any lost+found? 1 Quote Link to comment
tidusjar Posted November 3, 2021 Author Share Posted November 3, 2021 Oh wow, I unassigned the drive, re-assigned it and now it's mountable and everything seems normal? Quote Link to comment
trurl Posted November 3, 2021 Share Posted November 3, 2021 2 minutes ago, trurl said: Do you have any lost+found? See if you have a user share named lost+found. Repair will put any folders or files it can't figure out there. Quote Link to comment
Recommended Posts
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.