butlerpeter

Just wanted to come and confirm that the new docker stop/start script functionality worked great. Thanks for adding that.

Knowing that the script got called (or not) should be enough for now. Thanks.

Thanks for that - I've just put my scripts in place - will see what happens next time containers are updated. Incidentally - does anything get logged anywhere when the scripts are called?

Yes that should do the job. Thanks

Bumping as a reminder as requested.

Is there any possibility for the ability to run a custom script after dockers have been updated? I have a self built docker container which doesn't get updated very often. But it depends on a mariadb container that does get updated. When the weekly docker update process happens, if the mariadb container has been updated then my custom one falls over. It's a simple fix for me to ssh in and restart that container, but if it was possible to script it then it would save me having to (remember to) check.

Excellent news. Look forward to it being merged and released.

Recently had a bit of a strange issue with the mariadb container. It's had been running fine for weeks, ever since migrating to it from a container from another author. Yesterday I did the upgrade to unRAID 6.1.7, so during the course of stopping the array to reboot the dockers were stopper. The upgrade went to plan, rebooted the server, started the array again and all of my docker containers came back up - or so I thought. It was only some hours later that I noticed something was wrong with the mariadb container. Looking in the logs (which I don't have to hand unfortunately) I saw continuous, repeated, failed attempts to start mariadb. There was a log message about it having not been shutdown cleanly (sorry I don't have the exact text), with messages about recovering from a crash, and then each attempt to start was followed by a message saying that the table mysql.users didn't exist (again sorry for not having the exact text). Looking at the /config/databases folder I saw that the owner of the mysql directory had been changed from 'nobody' to '103' - 103 seems to be the uid of the mysql user inside the container. "chown -R nobody:users mysql" fixed the complaint about the mysql.users table. But then there was a similar message about another mysql.*something* table, and when I looked the owner of the mysql folder had changed to 103 again. Changing the owner back to nobody this time fixed things and mariadb started up correctly. I suspect that what happened was that there was an unclean shutdown (of mariab) and when starting up again it attempted to recover and during that process tries to ensure that it has correct access so changes the owner of the folder to the mysql user. Which then leads to access problems and stops it accessing those mysql.* tables. I wonder if the mariadb startup script "/usr/bin/mysqld_safe" (I think!) should be changed to take into account the uid that has been specified for the container to run as, instead of just using the mysql user? Hope that makes sense!

I am not sure the licensing would allow it. This one instead - better fork of it: http://forums.nzedb.com/index.php Myk Newznab+ cant be forked so whatever that is it is not a fork of Newznab+ (at least a legal one) It could be a fork of Newznab (non plus) but thats like putting a bigger engine in a cheap car and claiming its as good as a Ferrari. I have been thinking about it an NN+ could be put in a docker if the user was able to define the SVN URL and pass as a variable. I have a docker container running for nZEDb - it is configured to access the nZEDb files from a mapped volume, so that nZEDb is installed outside of the docker. I have it that way because I already had it installed and couldn't be bothered with getting the container to do the installing, and my Linux scripting isn't the greatest. It works well though, I have it connecting to a database hosted in needos mariadb container. It would need more work to make it suitable for distribution through the docker hub but, if there is interest I could post the dockerfile I used to build it.

I couldn't find one either, but I did discover that the StarTech PEXSATA24E is the same card, and is available in the UK. http://www.ebuyer.com/162229-startech-com-2-port-esata-4-port-sata-pci-express-x4-sata-pexsata24e I ordered one from ebuyer last week and installed it at the weekend. I currently it setup to enable the 2 esata ports, and have my cache drive connected to one of the internal ports (eliminating the esata to sata cable coming in through the rear of the chassis). At some point, when required, I'll look into getting hold of one (or more) of the external enclosures discussed in this thread and connecting up to the new esata ports. As an update - I got to the point of needing more hdd space, and with my Microserver drive bays being full I needed an external enclosure. So I got one of these - http://www.hornettek.com/hdd-enclosure/3-5-quad-bay-jbod/hornettek-enterprise-4x.html and have it connected via esata to one of the esata ports on the StarTech card. The product info for the enclosure says that it supports up to 3TB drives, but at the same time I ordered a Seagate 4TB and put it in the enclosure "just to see if it would work". Happily it seems to work fine, although I do only have the 1 drive in there at the moment. If I get issues in the future when adding more drives I'll just put any 4TB ones into the Microserver and move the <= 3TB ones into the enclosure. I haven't done any scientific testing, but access and data transfer speeds seem fine. Will wait until the next scheduled parity check to see if there is any great effect there. The only issue is that the drive I the enclosure isn't reporting any SMART data. Apparently that is an issue with the controller in the enclosure and only affects the first disk that is enumerated in it. So far so good - would recommend it. Especially for users in the UK where there seems to be a lack of suitable JBOD enclosures. I couldn't find the previously mentioned Sans Digital oes anywhere for a decent price.

I couldn't find one either, but I did discover that the StarTech PEXSATA24E is the same card, and is available in the UK. http://www.ebuyer.com/162229-startech-com-2-port-esata-4-port-sata-pci-express-x4-sata-pexsata24e I ordered one from ebuyer last week and installed it at the weekend. I currently it setup to enable the 2 esata ports, and have my cache drive connected to one of the internal ports (eliminating the esata to sata cable coming in through the rear of the chassis). At some point, when required, I'll look into getting hold of one (or more) of the external enclosures discussed in this thread and connecting up to the new esata ports.

That's the one I have connected to my N40L. Only had it a few weeks though, and not had any power issues in that time I'm currently running 2x 3TB WD Greens (1 is parity), 2x 1.5TB Samsungs and the 250GB Microserver drive as cache

That Sans Digital enclosure looks like exactly the kind of thing I had in mind when asking my question, a few days ago, about possible future storage expansion for my Microserver. Am still alittle confused by what sort of controller card I'd need to be able to hook one of those enclosures up to my Microserver. Does anybody have any suggestions on what card I should be looking at? Ideally I'd want for Unraid to see the individual drives in the enclosure, and for a setup where performance of the enclosure drives isn't hampered too much. Peter

Guys, I've had my N40L running nicely for about 6 months now. The original 250GB drive (cache) and a 3TB WD (parity) are installed in the ODD bay, and I've got another 3TB WD and 2x1.5TB Samsungs as data drives. I'm in no desparate need to upgrade the storage at the moment, and if I did I still have a free bay and 2x1.5TB data drives which could be upgraded to 3TB. But, with half an eye on future expansion, I was wondering about the possibility of hooking up an external drive cage of some description (in my mind I imagine it holding another 4 drives), along with some sort of controller card to provide the connections to the external cage. Question I have is, what exactly should I be looking for to achieve that? Has anybody hooked up anything like that to a Microserver? Any specific cards or cages I should keep an eye out for? I guess it would make sense if the controller card also had an internal port so that I could lose the esata-in-through-the-back arrangement that I have now. As I said, I'm in no need of extra space for the time being, but it would be good to know what I'm looking for when the time does come. And I guess other Microserver owners might find any information useful as well Cheers Peter