mudboy

Sent

When I try to activate, I get the following message: The error is: Unknown option: --no-optional-locks. I assume there is a lockfile somewhere that might need to be deleted or something, as I initially had some misconfigurations.

Getting this on the 6.4 RC8 release. Warning: Illegal string offset 'PK1334PEKDAGZS' in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 187 Fatal error: Uncaught Error: Cannot use string offset as an array in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php:187 Stack trace: #0 /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php(86): Get_JSON_Config_File() #1 /usr/local/emhttp/plugins/serverlayout/php/serverlayout_layout.php(2): require_once('/usr/local/emht...') #2 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(378) : eval()'d code(1): include('/usr/local/emht...') #3 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(378): eval() #4 /usr/local/emhttp/plugins/dynamix/template.php(62): require_once('/usr/local/emht...') #5 {main} thrown in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 187 Not sure if that's a 6.4 beta issue, or something else, but thought I would mention it in case it's a 6.4 related issue.

anyone else have this problem that is running the ombi docker container?

I'm getting this too. This is from just after reboot... If it gets stuck again I'll try to post one from that state. tower-diagnostics-20170416-0839.zip

Stopped array, I took the drive out of the array, formatted it as ext4, reformatted as xfs, re-added to array, and started array, and let it do a parity rebuild.

/dev/md7 errors abound, yet the disk passes smart test, I have reformatted it, and let parity try to rebuild, and still get these. unraid_kernal.txt tower-diagnostics-20170304-0918.zip

Is there a working comskip + transcode Userscript that people are using to remove commercials and transcode to H.264?

That resolved it. With -L. Sent from my iPhone using Tapatalk

One last log to post... This was a tail -f of /var/log/syslog while I started the array. Dec 14 21:04:30 Tower emhttp: shcmd (341): set -o pipefail ; mount -t xfs -o noatime,nodiratime /dev/md2 /mnt/disk2 |& logger Dec 14 21:04:30 Tower kernel: XFS (md2): Mounting V5 Filesystem Dec 14 21:04:30 Tower kernel: XFS (md2): Starting recovery (logdev: internal) Dec 14 21:04:32 Tower kernel: XFS (md2): Internal error XFS_WANT_CORRUPTED_GOTO at line 3156 of file fs/xfs/libxfs/xfs_btree.c. Caller xfs_free_ag_extent+0x419/0x558 Dec 14 21:04:32 Tower kernel: CPU: 5 PID: 7487 Comm: mount Not tainted 4.4.30-unRAID #2 Dec 14 21:04:32 Tower kernel: Hardware name: Gigabyte Technology Co., Ltd. Z97X-UD7 TH/Z97X-UD7 TH-CF, BIOS F4 05/30/2014 Dec 14 21:04:32 Tower kernel: 0000000000000000 ffff88045ecdba38 ffffffff8136f79f ffff88047b14c820 Dec 14 21:04:32 Tower kernel: 0000000000000000 ffff88045ecdba50 ffffffff81275fd0 ffffffff812465ad Dec 14 21:04:32 Tower kernel: ffff88045ecdbac0 ffffffff8125a774 ffffffff8125998e 000000005ec1c1d0 Dec 14 21:04:32 Tower kernel: Call Trace: Full file is attached... BringUpArrayCrash.txt

One other thing I noticed is that while crashed it seemed to be spamming the hell out of my LAN. My guess is lots of broadcast traffic, but didn't fireup wireshark to confirm. Follow on NOte, System does boot up in Safe Mode, and array will start in maintenance Mode... I saw an error message related to /dev/sdo, and removed it, rebooted, and still have the same problem.

Here's the Syslog syslog.txt

My Unraid array crashed, and when I rebooted it (it was totally non-responsive), it didn't come up. I've done Memtest and it passed without errors... System halts as array tries to come online, or, if not trying to come online, unraid will stop responding within a couple of minutes of reboot while I'm trying to get in and do stuff... I can reboot the unit locally, and have done that a few times.. If I hard reboot, the array will come back up, but I'm not able to get to the GUI, although I did one time... Very odd. Attached is a syslog and diag pack, as well as some screenshots from the crash window from different crashes. tower-diagnostics-20161214-1834.zip

OK, it's the full version string, with the hyphenated numbers at the end. basically all the numbers in the filename string from the one you downloaded... To edit the version bring up the docker and slide the advanced view bar... I had an additional problem in that when I did this, one of the elements of the init script was hanging. usermod -o -u 99 abc in 10-adduser... I needed to kill this to get it to proceed...

For those of us with Plex Pass, can anyone hint at the proper format for the Version String? Build number included? PM would be great.

Also seeing this after I deployed a docker container and removed it. container was syncthing from jfgardim if it matters. running 6.1.3

please share!