Sandorr

I installed your Lychee docker today and I get the webUI configuration screen. However, I get failures when attempting to create the database from the initial UI screen 'unable to create database - access denied'. I only filled out username and password as the other options say 'optional'. I also made sure data and uploads were set to 777 and everything in /data is nobody users. Any tricks to get this working?

Just reporting this issue, have not seen it before. I am going to move my image to another ssd (xfs) outside of the array anyway. Brought up the system on beta14, deleted my current docker.img using the new 'delete image' feature in the gui (on a brrfs pool - cache drive). I then attempted to recreate it from the gui and it just hangs on the docker screen. I checked syslog and saw this: Feb 21 14:30:58 Iron php: Creating new image file for Docker: /mnt/cache/docker/docker.img size: 32G Feb 21 14:30:59 Iron php: Btrfs v3.18.2#012See http://btrfs.wiki.kernel.org for more information.#012#012Turning ON incompat feature 'extref': increased hardlink limit per file to 65536#012Turning ON incompat feature 'skinny-metadata': reduced-size metadata extent refs#012fs created label (null) on /mnt/cache/docker/docker.img#012#011nodesize 16384 leafsize 16384 sectorsize 4096 size 32.00GiB Feb 21 14:30:59 Iron kernel: BTRFS: device fsid 4cff6c9a-f60b-4ea8-8507-8c21376ef7b5 devid 1 transid 4 /dev/loop2 Feb 21 14:30:59 Iron kernel: BTRFS info (device loop2): disk space caching is enabled Feb 21 14:30:59 Iron kernel: BTRFS: has skinny extents Feb 21 14:30:59 Iron kernel: BTRFS: flagging fs with big metadata feature Feb 21 14:30:59 Iron kernel: BTRFS: creating UUID tree Feb 21 14:30:59 Iron php: Resize '/var/lib/docker' of 'max' Feb 21 14:30:59 Iron php: starting docker ... Feb 21 14:30:59 Iron kernel: BTRFS: new size for /dev/loop2 is 34359738368 Feb 21 14:30:59 Iron kernel: ip_tables: © 2000-2006 Netfilter Core Team Docker did not come alive in the GUI. I am going to remove it and try again on an XFS SSD outside of the array.

Thanks for the info! I was able to do the same thing!

This should work even though I am using a cache pool?

I believe I used the instructions here: Command Line Method Lime Technology - unRAID Server Community » Company » Announcements » unRAID 6 Beta 6: Btrfs Quick-Start Guide http://lime-technology.com/forum/index.php?topic=33806.0

I only rebooted once after the install asked for the reboot. I have attatched my syslog for your review. Thanks in advance! syslog.txt

I updated to beta13 today through the webgui. After the reboot, my cache drive pool is also showing unformated. I assume I have lost the syslog since I rebooted (as instructed by the webgui after the update). From reading this thread, it sounds like this is being addressed in beta14. Since that is not available, is there a working method to go back to beta13 or to extract my data from the pool and reformat? SanDisk_SDSSDH2064G_125150403747 (sdt) * 64.0 GB Unformatted 90 1 0 btrfs SanDisk_SDSSDH2064G_125150404363 (sdj) * 64.0 GB - - 492 2 0 btrfs Total Pool of two disks * 0 B 0 B 0 B 582 3 0

I love this addon, really great work. Is there a way to include additonal arguments to the docker call? I wanted to experiment with linking docker containers as described below using the --link argument. Is there a way to do this currently using a template? Or a manual method? Ideas?...

Upgraded from 10a to 12. All working as expected so far. Love the dynamix integration.

That step took some time on my system too, so just be patient. Thanks BRit, beer it is.....

I installed from the extensions page, but it is still sitting at: syncing... Has been stuck there for a while, should I be concerned or just crack a beer and wait it out? I am preclearing two WD Red 3TB drives as well, perhaps not the best time to do an upgrade....

The command you used would be ok if that was your 'cache' device, but if that was an array device, resizing the partition like that invalidates parity. For that reason, I edited your post and deleted those lines because I don't want anyone else to do that. I'll post correct instructions later... Sounds good, thanks for the update. I will watch for the correct instructions later. Meanwhile...I will start a parity rebuild... Parity check should be fine. If the replacement disk was precleared you should not see many parity errors. If not you'd see a bunch. But either way the parity check will correct then (if you run a correcting check) and be faster than a build. Thanks for the info, I will give it a shot.

The command you used would be ok if that was your 'cache' device, but if that was an array device, resizing the partition like that invalidates parity. For that reason, I edited your post and deleted those lines because I don't want anyone else to do that. I'll post correct instructions later... Sounds good, thanks for the update. I will watch for the correct instructions later. Meanwhile...I will start a parity rebuild...

Code used to just do an unconditional "resize" upon every mount, and that was not an issue because with reiserfs it just was a no-op. But with btrfs/xfs there needs to be a little more sophistication in the coding. I didn't want to delay beta7 another week to get this in, so left auto-resize out until next release. If someone needs to do an expansion before beta8 I will post instructions. Yes. Can you post the instructions for 'If someone needs to do an expansion before beta8 I will post instructions.'? [Edited to delete lines that can cause invalid parity - limetech]

Unraid 6 Beta 6 PlugIn/Extension OpenVPN Client Docker Manager Docker SABnzbd NZBGet Deluge NzbDrone Headphones Couch Potato NZB MegasearcH Madsonic KVM Win81Pro - Blue Iris (Security Cameras) WILL ADD WHEN AVAILABLE Dynamix Cache Dirs