SuperW2

Thanks for the attempt... I'm kind of desperate... I tried to manually kill emhttp and rerun from the command line "/usr/local/sbin/emhttp &" (searching the forum and trying anything that might help.... Getting a "segfault at 530 ip <long string> sp <another long string> error 4 in ehmttp[<one more slightly less long string>] emhttp isn't designed to be restarted anymore Grrr.... Thanks... I was able to boot on a new USB stick (trial version)... obviously not going to mount any of the drives or whatever, but I can see that it's booted, am able to see the webconsole, etc. At least tells me that network is OK, and hopefully my Server HW... Not sure where to go from here. -W

Thanks for the attempt... I'm kind of desperate... I tried to manually kill emhttp and rerun from the command line "/usr/local/sbin/emhttp &" (searching the forum and trying anything that might help.... Getting a "segfault at 530 ip <long string> sp <another long string> error 4 in ehmttp[<one more slightly less long string>]

How do I get that if I can get to a GUI? from command prompt diagnostics ignore any errors. File will be saved somewhere (can't remember where off the top of my head) on the flash drive OK, here is the Diag Zip... I pulled Disk 6 out hoping that the server would boot without it but no change... and my powerdown/shutdown scripts are doing nothing, so I've had to hard power the thing each time media-diagnostics-20160508-1622.zip

How do I get that if I can get to a GUI?

On 6.2.0-beta21... Rebooted server and can longer access GUI. Can Ping server from Windows PC, can SSH, able to log in directly on server but no Web GUI... Have 2 NIC's both plugged in... tried swapping cables etc (which I tihnk you can see at end of Syslog. Getting some "<My IP> linkdown" message above my Login prompt on server console, which I'm never really seen before. Other than some new HD Address (one old and on new, no changes to anyting settings or otherwise to my server recently). Anything in my Syslog jump out to anyone? -SW2 syslog.txt

Thanks All, I'd kind of forgotten about a PreCleaer until after I initially posted (been a while since I've added any new drives) and no, nothing super duper secret or sensitive that I'm too worried about, just get paranoid from my "day job" where everything is flagged as confidential and the security folks get all in a tissy worried about RMA'ing drives that might contain data. I'm in the process of pulling all the data off of it before I do anything and having to split among the free space of several other of my drives. I will likely pull it out and run the Seatools first just to see if it flags a code for warranty replacement and then

Q1) A recent parity check revealed a one drive with a few read errors. It happens to be a Seagate drive and I want to run their tools to see if it flags an issue to possibly get addressed/replaced under warranty. Is there a way to run Seatools software while the drive is in my array (an App or Docker or something), or do I need to remove from my Server, plug into my Windows PC and run Seatools from there? Q2) Is it recommended practice to upgrade HDD Firmware to the "latest" version if the vendor has released new ones as good general practice, or only if there is an issue identified that is affecting one of my drives/FW version? I've never upgraded any FW on any HDD, so unsure if it's really necessary or recommended. Q3) In the event that the drive in Q1 is bad and needs to be replaced, is there a Secure Deletion (DBAN/DoD Wipe kind of thing) App/Docker, etc that I could run on the drive while it's still in my server, or will that also need to take place physically outside the server/array. Or should I/can I just another run a Pre Clear on the drive before sending back to vendor? Thanks SW2

Yah that seemed to work after several start/stops and waiting some time after re-starting... I'll just try to keep it running from now on! Thanks!

Updated the other day (maybe a couple weeks ago, whever the last update happened) now cannot start the Handbrake Docker... it had previously been working fine... sparklyballs/handbrake:latest Here is Log error. Fatal server error: Server is already active for display 1 If this server is no longer running, remove /tmp/.X1-lock and start again. Openbox-Message: Failed to open the display from the DISPLAY environment variable.

See here OK, I tried, but it's almost 10X bigger than the maximum attachment size the forum allows me to post... (almost 1.8MB) Other options are put it on a download site like pastebin, mediafire, etc; or your own ftp site; or a 'cloud' site like your own dropbox; and provide us an accessible URL. Or you can examine it for the one file that's blowing it up, and remove that, and post the rest. Tell us what you had to remove, and we can examine the rest and determine how badly we need what's removed. I rebooted (after running NFS repair) and the log file seems small now, and attached to my Original Post #110... I also left the Dropbox link to the "before". Interestingly enough after rebooting my user / disk share issue reported seem to at least for now to have gone away....Will continue to monitor -Sw2

I'm not sure exactly where to place this or if it's Beta related or not (only noticed with 6.2.0B18 and now 19) I have User Shares ("TV" in this case) with Several "Included" Disks (and "None" in Excluded)... When I browse the user Share on Windows 10, not all of the files on all of the Disk shares appear... in fact nothing after Jan 15, 2016. But if I browse the Disk Share directly ("\\Media\Disk15" for example) I see all of the files and folders that I expect to see in the User Share under a "TV" folder off the root of that disk share. I don't use the Cache drive on my user shares, and have both SMB/NFS Export to Yes/Public. I can browse to one of the "included" disk shares manually in Windows Explorer and I see all of the recent files/folders that don't appear in the User Share. If I browse via the UnRaid console using the "view" explorer looking icon from the Share Tab the files are also not I originally had "All" disks included and excluded just those not associated with that specific user share and saw the same issue. No idea where to even start... this affect anything connecting to that user share (specifically Plex). I've not made any changes to any of my user share settings since installing 6.2B18/19. I rebooted (after running NFS repair and the log file seems small now, and attached Here is the original.... https://www.dropbox.com/s/dl7qm547hqimb5j/media-diagnostics-20160321-1848.zip?dl=0 -SW2 media-diagnostics-20160321-1912.zip

Do you have a cache device in your system? Yes, and already had an "appdata" and "vm" share on the cache drive. The ISO folder is a subfolder on my "backup" user share (which is part of the main array, not cache drive) And part of my log file Mar 11 14:05:19 media emhttp: shcmd (658): /etc/rc.d/rc.libvirt start |& logger Mar 11 14:05:19 media root: no image mounted at /etc/libvirt Mar 11 14:05:21 media emhttp: shcmd (678): /etc/rc.d/rc.libvirt start |& logger Mar 11 14:05:21 media root: no image mounted at /etc/libvirt Ok, in the VMs tab under the Libvirt storage location, type /mnt/user/system/libvirt/libvirt.img Then enable VMs and click apply. OK, that worked!

Do you have a cache device in your system? Yes, and already had an "appdata" and "vm" share on the cache drive. The ISO folder is a subfolder on my "backup" user share (which is part of the main array, not cache drive) And part of my log file Mar 11 14:05:19 media emhttp: shcmd (658): /etc/rc.d/rc.libvirt start |& logger Mar 11 14:05:19 media root: no image mounted at /etc/libvirt Mar 11 14:05:21 media emhttp: shcmd (678): /etc/rc.d/rc.libvirt start |& logger Mar 11 14:05:21 media root: no image mounted at /etc/libvirt

Had a Windows VM setup before Upgrade but was not set to autostart. After 6.20b18 upgrade now unable to even access the VM tab to review the changes made on Post 1 of this thread. In VM Manager in Settings just have a "You must reboot for changes to take effect" regardless of whatever settings have no "VM Tab". I have set to "no", rebooted, set to "yes" rebooted again an no change.

That did the trick and I'm back in business on both! Thanks for the quick reply... as always, great work with your UnRaid Docker Apps! -SW2

Just updated to the latest Binhex Sickbeard and Sabnzbd and now neither will start. Both had been working flawlessly since install... Binhex Deluge also update, but it still seems to start OK... Sickbeard Log file 016-02-21 19:56:41,032 DEBG 'sickbeard' stdout output: Starting up Sick Beard 507 2016-02-21 19:56:41,032 DEBG 'sickbeard' stderr output: File "/usr/lib/sickbeard/SickBeard.py", line 323, in main sickbeard.initialize(consoleLogging=consoleLogging) File "/usr/lib/sickbeard/sickbeard/__init__.py", line 681, in initialize logger.sb_log_instance.initLogging(consoleLogging=consoleLogging) File "/usr/lib/sickbeard/sickbeard/logger.py", line 99, in initLogging self.cur_handler = self._config_handler() File "/usr/lib/sickbeard/sickbeard/logger.py", line 111, in _config_handler file_handler = logging.FileHandler(self.log_file_path, encoding='utf-8') File "/usr/lib/python2.7/logging/__init__.py", line 905, in __init__ 2016-02-21 19:56:41,033 DEBG 'sickbeard' stderr output: StreamHandler.__init__(self, self._open()) File "/usr/lib/python2.7/logging/__init__.py", line 937, in _open 2016-02-21 19:56:41,033 DEBG 'sickbeard' stderr output: stream = codecs.open(self.baseFilename, self.mode, self.encoding) File "/usr/lib/python2.7/codecs.py", line 896, in open 2016-02-21 19:56:41,033 DEBG 'sickbeard' stderr output: file = __builtin__.open(filename, mode, buffering) IOError: 2016-02-21 19:56:41,033 DEBG 'sickbeard' stderr output: [Errno 13] Permission denied: '/config/Logs/sickbeard.log' 2016-02-21 19:56:41,049 DEBG fd 8 closed, stopped monitoring (stderr)> 2016-02-21 19:56:41,049 DEBG fd 6 closed, stopped monitoring (stdout)> 2016-02-21 19:56:41,049 INFO exited: sickbeard (exit status 1; not expected) 2016-02-21 19:56:41,050 DEBG received SIGCLD indicating a child quit 2016-02-21 19:56:42,051 INFO gave up: sickbeard entered FATAL state, too many start retries too quickly

Just updated to the latest Binhex Sickbeard and Sabnzbd and now neither will start. Both had been working flawlessly since install... Binhex Deluge also update, but it still seems to start OK... Here is SAB log file 2016-02-21 19:54:59,397 DEBG fd 8 closed, stopped monitoring (stderr)> 2016-02-21 19:54:59,397 DEBG fd 6 closed, stopped monitoring (stdout)> 2016-02-21 19:54:59,397 INFO exited: sabnzbd (exit status 2; not expected) 2016-02-21 19:54:59,398 DEBG received SIGCLD indicating a child quit 2016-02-21 19:55:02,402 INFO spawned: 'sabnzbd' with pid 27 2016-02-21 19:55:02,594 DEBG 'sabnzbd' stdout output: Error: Can't write to logfile 2016-02-21 19:55:02,609 DEBG fd 8 closed, stopped monitoring (stderr)> 2016-02-21 19:55:02,610 DEBG fd 6 closed, stopped monitoring (stdout)> 2016-02-21 19:55:02,610 INFO exited: sabnzbd (exit status 2; not expected) 2016-02-21 19:55:02,610 DEBG received SIGCLD indicating a child quit 2016-02-21 19:55:03,611 INFO gave up: sabnzbd entered FATAL state, too many start retries too quickly

Then I tried to do a repair (by blanking out the options in the "Check Filesystem Status" on the Disk 9 Page and get the following... Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... 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. When I try to mount the filesystem, the system just HANG'S and won't start... SO. I guess I have to try the -L and then repair??? Help!

Looking at the XFS repair on Disk 9... No clue what this all means, but it certainly "sounds" bad... Phase 1 - find and verify superblock... Phase 2 - using internal log - scan filesystem freespace and inode maps... out-of-order bno btree record 91 (72556437 131314) block 0/1 out-of-order bno btree record 102 (83548277 2354) block 0/1 out-of-order cnt btree record 20 (18038001 1) block 0/2 out-of-order cnt btree record 21 (50010339 1) block 0/2 out-of-order cnt btree record 22 (50010343 1) block 0/2 out-of-order cnt btree record 23 (70860475 1) block 0/2 out-of-order cnt btree record 24 (70860527 1) block 0/2 out-of-order cnt btree record 25 (73211771 1) block 0/2 out-of-order cnt btree record 26 (73226357 1) block 0/2 out-of-order cnt btree record 27 (73685354 1) block 0/2 out-of-order cnt btree record 28 (77686589 1) block 0/2 out-of-order cnt btree record 85 (1261386 23) block 0/2 block (0,1261400-1261400) multiply claimed by cnt space tree, state - 2 agf_freeblks 26931021, counted 27667652 in ag 0 ir_freecount/free mismatch, inode chunk 0/40785952, freecount 12 nfree 4 inode chunk claims used block, inobt block - agno 0, bno 18020273, inopb 8 agi_freecount 385, counted 393 in ag 0 agi_freecount 385, counted 377 in ag 0 finobt agi unlinked bucket 0 is 122490240 in ag 0 (inode=122490240) sb_ifree 7838, counted 7849 sb_fdblocks 65573345, counted 65581531 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... found inodes not in the inode allocation tree - process known inodes and perform inode discovery... - agno = 0 imap claims in-use inode 40785991 is free, would correct imap imap claims in-use inode 40785992 is free, would correct imap imap claims in-use inode 40785993 is free, would correct imap imap claims in-use inode 40785994 is free, would correct imap data fork in ino 77200554 claims free block 9650102 data fork in ino 566881623 claims free block 72556437 data fork in ino 623478740 claims free block 83590138 - 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 = 1 - agno = 0 - agno = 2 - agno = 5 - agno = 7 - agno = 6 - agno = 3 - agno = 4 No modify flag set, skipping phase 5 Inode allocation btrees are too corrupted, skipping phases 6 and 7 No modify flag set, skipping filesystem flush and exiting.

And 1 pass, no errors... I can let it run overnight, but I really need to figure out what's up with me Server first! (never had anything that led me to believe that i'd ever had any memory issues). -SW

Running Memtest now...

Thanks that allowed me to start the WebGUI... Checked "Maintenance Mode" box and then Start... It Immediately started a Parity Check... assume I need to let that finish? How do I start an XFS check on disk9? Also, might be a silly question, but I don't see a Memtest option in the GUI or know how to run from console. -Wade I'm surprised that it started a parity check even in maintenance mode. I assume that you wound up doing an unclean shutdown. Shouldn't hurt to stop it (you can always run it again). Memtest you can only get to locally with a keyboard and mouse attached. Right when it starts booting, you'll see an option to run memtest Ah yah, remember the Memtest on the boot, but it's been a couple years since I've booted with a monitor attached...

Thanks that allowed me to start the WebGUI... Checked "Maintenance Mode" box and then Start... It Immediately started a Parity Check... assume I need to let that finish? How do I start an XFS check on disk9? Also, might be a silly question, but I don't see a Memtest option in the GUI or know how to run from console. -Wade

Was getting a couple odd I/O error messages in Windows when attempting to write to a couple of my user shares, so I thought a reboot might be in order... After reboot, I'm unable to access WebGUI at all, I can Ping and Telnet into the console remotely (no local physical monitor/kb on my server). Attached is the ZIP file from running "Diagnostics" on Telnet session but here is the end part of Syslog where stuff hit's the fan apparently! Dec 12 13:38:46 media kernel: XFS (md9): xfs_do_force_shutdown(0x8) called from line 1008 of file fs/xfs/xfs_trans.c. Return address = 0xffffffff812743f4 Dec 12 13:38:46 media kernel: XFS (md9): Corruption of in-memory data detected. Shutting down filesystem Dec 12 13:38:46 media kernel: XFS (md9): Please umount the filesystem and rectify the problem(s) Dec 12 13:38:46 media kernel: XFS (md9): Failed to recover EFIs Dec 12 13:38:46 media kernel: XFS (md9): log mount finish failed Dec 12 13:38:46 media kernel: XFS (md9): xfs_log_force: error -5 returned. Dec 12 13:38:46 media kernel: XFS (md9): xfs_log_force: error -5 returned. <<--- (and hundreds/thousands more of these) HELP! Please and thank you! -Sw2 media-diagnostics-20151212-1459.zip

Ah...I am using 2 different AdBlockers in Chrome (AdBlock Plus and UBlock Origin) but nothing in FF. I will add my server to the whitelist domains and give it another shot on next reboot.