February 22, 20179 yr Unraid Version 6.3.1 Docker Was Set up SABNZBD, Couchpotato, SickBeard Installed Plugins: = CA Backup / Restore Appdata Part of the CA family, CA Backup / Restore Appdata will either manually or on a schedule, automatically backup your docker appdata for easy restoring in case of a cache drive failure Andrew Zawadzki 2017.01.09 unknown CA Cleanup Appdata Part of the CA family, Cleanup Appdata will scan your appdata share to determine which folders are no longer in use (due to an uninstalled docker application) and prompt you to remove them) Andrew Zawadzki 2017.01.28 unknown Community Applications A Plugin to keep your docker application lists up to date and easily sort them by category and add them to your running containers. unRaid v6.1+ only. Andrew Zawadzki 2017.02.12 unknown Dynamix webGui The Dynamix webGui is the latest iteration of the unRAID Server OS System Management Utility. Built upon Simple Features, it provides real-time screen updates, tabbed viewing and many more enhancements. Bergware 2017.02.02 unknown built-in Fix Common Problems A Plugin to diagnose and suggest fixes for common problems, configuration mistakes, etc. Andrew Zawadzki 2017.02.18 unknown unRAID Server OS unRAID Server OS by Lime Technology, Inc.. LimeTech 6.3.1 unknown built-in ------------------------------------- Description of problem: Started getting some problems writing to the array. (It was getting low on space, I admit, but I had about 4TB left) Looked at the troubleshooting page. Grabbed "Fix Common Problems" and found some issues. (And at this point, I don't even remember what they were because I really thought this problem was resolved at that point... /me dumb user) I had some older docker plugins that had a bunch of data in the Appdata share and ran CA Cleanup Appdata. It seemed to 'hang' (I let it run all night). The server did not respond so I rebooted after a while (Yes, now, I read that was not something I should have done.. .sorry). Unraid comes up and I can get to the menus but if I try to start the array it locks up (Unraid menu/app won't respond, nothing is accessible). ------------------------------------- The server will boot and I can get to Unraid menus but if I try to start it in other than 'maintenance' mode it crashes Unraid. Tried starting in maintenance mode and then doing a 'power down' option from the menu, hoping for a clean start. **I'm a Linux NOOB, but, am willing to read/try things.. I just don't want to make any more mistakes or risk losing data. Thanks for any/all help! Went 441 days without a problem! unraid-diagnostics-20170222-1541.zip Edited February 22, 20179 yr by Nada_Mucho
February 23, 20179 yr Definitely won't be anything from Appdata Cleanup Go to Fix Common Problems, and pop it into troubleshooting mode. Then attempt to start the array.(normally, not in maintenance mode) After you get sick of waiting for it to start, either hard reset it or from the command line powerdown -r Then post the diagnostics file and the FCPsyslog_tail.txt file that will be stored in the logs folder on the flash drive. Odds on you've got corruption on one of the disks, (or maybe something else going on). Those files will tell us what.
February 23, 20179 yr Your disks' SMART reports look good. Your syslog also looks good, as far as it goes. The only obvious issue there is that it has registered an unclean shutdown and will want to do a parity check once the problem is fixed. I understand that the problem happens when you start the array in normal mode so do as Squid suggests to provide more diagnostics to work on.
March 27, 20179 yr Author Hello .. I'm sorry I disappeared. Had a business trip and returned home to flooding so had other priorities for a long while. Short version: Annoying floods and my yard and garage got messed up but no real damage so I'm getting back to business. Spring is here! My Server is still down but nothing has changed for a month so if you're still willing to take a look I've attached my log files and diagnostics. Should it matter to you I copy/pasted the FCPsyslog_tail.txt into Notepad on Windows 10, just in case that somehow bungs it up for Unix guys. FCPsyslog_tail.txt unraid-diagnostics-20170223-0644.zip
March 30, 20179 yr On 3/26/2017 at 9:31 PM, Nada_Mucho said: Hello .. I'm sorry I disappeared. Had a business trip and returned home to flooding so had other priorities for a long while. Short version: Annoying floods and my yard and garage got messed up but no real damage so I'm getting back to business. Spring is here! My Server is still down but nothing has changed for a month so if you're still willing to take a look I've attached my log files and diagnostics. Should it matter to you I copy/pasted the FCPsyslog_tail.txt into Notepad on Windows 10, just in case that somehow bungs it up for Unix guys. FCPsyslog_tail.txt unraid-diagnostics-20170223-0644.zip You need to check disk filesystem on disk 4 https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems
April 1, 20179 yr Author I ran the Check Disk with -nv and it produced this output: Not available Phase 1 - find and verify superblock... - block cache size set to 1446776 entries Phase 2 - using internal log - zero log... zero_log: head block 388734 tail block 347312 - scan filesystem freespace and inode maps... Metadata corruption detected at xfs_agf block 0x1/0x200 flfirst 118 in agf 0 too large (max = 118) agf 118 freelist blocks bad, skipping freelist scan agi unlinked bucket 0 is 463817920 in ag 0 (inode=463817920) agi unlinked bucket 1 is 463817921 in ag 0 (inode=463817921) agi unlinked bucket 2 is 463817922 in ag 0 (inode=463817922) agi unlinked bucket 3 is 463817923 in ag 0 (inode=463817923) agi unlinked bucket 43 is 467329963 in ag 0 (inode=467329963) agi unlinked bucket 51 is 463817779 in ag 0 (inode=463817779) agi unlinked bucket 53 is 463818037 in ag 0 (inode=463818037) agi unlinked bucket 63 is 463817919 in ag 0 (inode=463817919) sb_icount 305472, counted 305408 sb_ifree 11591, counted 11652 sb_fdblocks 499997310, counted 497078807 - 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 The drive did not mount and unraid locked up so I rebooted. So.. I read about xfs_repair and ran this, thinking it was the next step Last was Sat Apr 1 14:12:50 2017 on /dev/pts/0. root@unraid:~# xfs_repair -v /dev/md4 Phase 1 - find and verify superblock... - block cache size set to 1446776 entries Phase 2 - using internal log - zero log... zero_log: head block 388734 tail block 347312 ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. I stopped at this point because I'm not sure if I should do -L or not... anything else I should try? ----------------------------------- Update: I read all afternoon about what alternatives there were or other things I could try and based on what I think happened, which is I may have put a plugin to write to a disk instead of a share, my main data that I care about would be okay. So, I ran xfs_repair - L and it seems to have worked! All my critical files are okay. Just to be safe, I'm moving them to a non-Unraid disk tonight. Is there anything else I need to do to make my Unraid server totally healthy again? Or is that it? In any case, THANKS SO MUCH for your posts and advice! Edited April 2, 20179 yr by Nada_Mucho I ran xfs_repair -L after reading all I could on the subject
Archived
This topic is now archived and is closed to further replies.