April 17, 20179 yr Hey guys, Have been running unraid 6.x.x for about 6 months now without any issues, however have been struggling lately and from the screenshot, I assume my array will not mount? (see attached) This started after I installed an owncloud docker, it was playing up and not quite working as intended, so I stopped the docker, but then I got a execution error. I look at what my Unraid is outputting to its console as the GUI crashed at the same time, it was just spamming code, too fast for me to capture. It basically left me with no choice but to shutdown my machine ungracefully, as I couldn't even putty to the console. Now I am faced with this, any idea's what is going on? I assume "sh: line 1: 3582 killed" means a something failed to mount? At this stage, I have access to the console, but the GUI is no longer working. As someone that is fairly new to linux, id appreciate any help here as my searches have turned up nothing in regards to this -addy Edited April 17, 20179 yr by Addy
April 17, 20179 yr Community Expert If enable disable array auto-start by editing disk.cfg on your flash drive (config/disk.cfg) and changing startArray="yes" to "no". Then start the array in maintenance mode and check filesystem on disk1 (md1):
April 17, 20179 yr Author 3 minutes ago, johnnie.black said: If enable disable array auto-start by editing disk.cfg on your flash drive (config/disk.cfg) and changing startArray="yes" to "no". Then start the array in maintenance mode and check filesystem on disk1 (md1): Hi Johnnie, Thanks for the reply, I made sure everything is unmount via command and ran xfs_repair -v /dev/md1 Is this the same thing? If not ill do this
April 17, 20179 yr Author 1 hour ago, johnnie.black said: If enable disable array auto-start by editing disk.cfg on your flash drive (config/disk.cfg) and changing startArray="yes" to "no". Then start the array in maintenance mode and check filesystem on disk1 (md1): Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... Metadata corruption detected at xfs_agf block 0x3a3832a1/0x200 flfirst 118 in agf 2 too large (max = 118) agf 118 freelist blocks bad, skipping freelist scan agi unlinked bucket 19 is 170633939 in ag 1 (inode=707504851) sb_icount 66304, counted 66368 sb_ifree 8449, counted 8513 sb_fdblocks 52431787, counted 52439479 - 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 - 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 = 0 - agno = 1 - agno = 3 - agno = 5 - agno = 2 - agno = 6 - agno = 7 - agno = 4 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... disconnected inode 707504851, would move to lost+found Phase 7 - verify link counts... would have reset inode 707504851 nlinks from 0 to 1 No modify flag set, skipping filesystem flush and exiting. Above is the output for Disk1, doesnt seem to have found any issues , it used xfs_repair -n
April 17, 20179 yr Author 4 hours ago, johnnie.black said: Remove the no modify flag -n Thanks for your help Johnny, got it all up and running. Had to do -L aswell, but seems to be going alright now
Archived
This topic is now archived and is closed to further replies.