2Piececombo

When I attempt to reinstall the container, this is all I get: docker run -d --name='adminer' --net='bridge' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="pieserv" -e HOST_CONTAINERNAME="adminer" -e 'ADMINER_DESIGN'='flat' -e 'ADMINER_PLUGINS'='' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8080]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/selfhosters/unRAID-CA-templates/master/templates/img/adminer.png' -p '8181:8080/tcp' 'adminer' 142ad3e3853233481831a9cb80ba486da8f6980bb81cb0698765dafa8f54d07c The command finished successfully!

I had adminer working just fine at one point. Then it no longer worked. I removed it, checking the box to delete the image too, and checked appdata cleanup to ensure nothing was left behind. I redownloaded it, it finished successfully, but didnt auto start. Upon manually starting, nothing happens. I figured since it doesn't have an appdata folder, something could have been cached in RAM, so I again removed/deleted image, and even deleted the template, then rebooted and reinstalled. Same thing, didnt auto start and cant manually start. The log for adminer contains nothing except: exec /usr/local/bin/entrypoint.sh: no such file or directory exec /usr/local/bin/entrypoint.sh: no such file or directory ** Press ANY KEY to close this window ** Not sure if the image isnt actually being deleted, because upon redownload it's almost instant, like it's not actually doing anything. Is there some sort of cache I should clear? Or a way to manually remove an image? Attached diags as usual. Cheers pieserv-diagnostics-20221030-2114.zip

Ive run into a problem. My scripts work great when stopping/starting the array. It takes some time to write out the data from RAM to the cache, so when I stop the array I see it re-trying over and over to while it waits for the script to finish. But eventually once the script is done copying data, the array stops and all is well. The issue is rebooting. If my understanding is correct, reboot will kill anything still running, this means my script dies and not all the data is copied out of RAM to the cache. I just learned this the hard way after a reboot and now nextcloud is broken. For reference, the scripts are: at start of array: rsync -ar /mnt/user/ramcache/appdata/ /tmp/appdata/ docker start nextcloud docker start mariadb at stop of array: rsync -ar /tmp/appdata/ /mnt/user/ramcache/appdata/ Is there some way to force the system to let the script finish instead of killing it? The performance benefit of having nextcloud, and even mariadb in ram is incredible and I don't want to have to give it up. Is there perhaps a better way than userscrips to achieve what im doing? Cheers

this is probably a dumb question, but when a script is set to run at stop of the array, does that mean it waits til the array is stopped to run? I just want to be sure the container will be stopped before it tries to copy data.

I realized start/stop of array are triggers. That should work. Im using rsync with the -a flag, that seems like it should preserve and file perms/attributes

I've been using nextcloud for quite some time and I love it. What I don't love is how slow it is when using the webui. My appdata lives on an nvme cache. Sadly my mobo only has pcie 2.0 slots, so the speed is somewhat limited, but its still painfully slow. As a test, I moved the appdata for nextcloud into /tmp, and it runs great! The UI is responsive and snappy and performance is awsome. Obviously ram gets wiped every reboot, but is there any realistic way to have a certain folder moved into ram at boot, then moved out of ram for a shutdown? I suspect simply moving the data is easy enough with userscripts. Perhaps even a scipt to start that particular container only after the data has been moved to RAM. But what about a script that runs on shutdown, after the containers are stopped, to move the data out of ram? Any suggestions are welcome :) Some people have lots of ram, and I feel like having an option to load appdata for specific dockers into RAM would actually be pretty nice. Theres a million posts out there complaining about how slow nextcloud is. But running it in RAM is a night and day difference.

Update appears to have done the trick! Thanks Jorge

Okay thats good to know. I'm 1/3 of the way through a preclear on a new disk, but once that's done I'll update mark solution if all goes well. Cheers

The ones I posted were after a reboot, in basically the same state it's currently in. But in any case, here pieserv-diagnostics-20221020-0030.zip

After closer inspection it seems like the devices I removed, even when re-assigned, are showing as unassigned. Clicking on the settings for a pool says the filesystem is xfs.

I stopped the array, removed one drive from each pool and mounted them manually to check if the data was still there. It was. I reassigned the drives to their respective pools and started the array. Both pools now seem to be fine. Rebooted and back to the same issue. Any ideas how to fix this?

Seemingly out of nowhere, both my cache pools (one made up of 2x1tb nvmes, and the other made up of 2x500gb sata ssds) are showing as invalid pool config. Surely it's not hardware as 2 different pools did this at the same time. I rebooted hoping whatever had happened would fix itself, but no luck. grabbed diags after reboot. I found this thread and tried the command, but all I got back was No valid Btrfs found on /dev/sdj Open ctree failed Anything else I can try other than removing the drives from the pool, copying data off, and rebuilding? Cheers pieserv-diagnostics-20221019-2204.zip

I thought the CPU error I was seeing was related to memory that needed to be reseated. During the CPU swap a RAM module must have developed a poor connection, because after re-seating them all it was fine and the server ran for about 9 hours without issue, then about 2 minutes ago it rebooted out of nowhere again. Now Im seeing the CPU errors again. Im going to have to assume the motherboard is faulty, I don't know what else it could be. The strangest part to me is that it has never once crashed while booted into windows/linux/etc. ONLY unraid. Regardless, I'm going to replace the mobo. I said previously that the mobo had been replaced, and that's sorta true. I had ordered another, installed it in this server, and still experienced a problem (this was 8-10 months ago) so I put the original mobo back in and built a second server with the new mobo. It's a Tyan S7012, which are still available new on ebay. Im going to pick up yet another one, swap the board out, and see what happens. If I still have problems im going to nuke this install of unraid completely and start over. I dont have the space to completely back up my media library, but oh well that can always be.... reacquired

Well I'm at a complete loss now... Finally had some time to look into what going on. My IPMI is now showing over 400 events. (see pic below) The same two things over and over again.. But the timestamps make absolutely no sense. I booted up the server, and when I tired to access the webui i get an nginx error. I log into the terminal and the aspect ratio is super wierd, it shows I have no dockers isntalled, all my cache drives are showing as unassigned, and it freezes, then reboots. This is with no GPU installed, btw. So where before I would only have issues WITH a gpu, it's not just gone to absolute shit. I think im going to have to backup all my data and assume this server is going to fail completely sooner than later. I dont think its going to stay alive long enough for me to grab diags anymore, so maybe syslog will give some idea.... Question, does the syslog include any sensitive info? Or am I goo to post it? I've not seen anything sensitive as I scrolled through it, but I want to be sure before I post it. Also, I watched the entire boot up process, and something about CPU errors. I have another pair of CPUs im going to drop in and see what happens. Wish me luck...

Possibly, unless it's somehow specific to certain GPUs. Both the GPUs I had wer older, a Quadro 600, and then a Quadro P600. I dont recall if you specified what card you have, but maybe it's related to this. I'm going to try a different card at some point and see what happens, though I have a very interesting update.. My server ran for at least 12 hours in safe mode with array started and docker running. Only thing disabled were plugins I believe. Then at some point I heard the beeps my mobo makes when it reboots. I presume it booted back to normal (not safemode) and then booted/crashed repeatedly til I just turned it off. I haven't had any time to look into why it might have shut off in safe mode, but when I power it back on ill grab diags and the mirror to USB syslog and post them here.

Small follow up, I've booted into safe mode, started array and docker, and it has not crashed, and the onboard graphics is displaying the console as normal. This makes me think that the nvidia driver plugin is somehow to blame for my issues. Thoughts?

Follow up, booted the server up in safe mode (so no nvidia plugin) and the output is displaying properly.

Powered down my server and reisntalled the GPU, booted back up normally, and within 5 mins it shutdown again. It's 100%, without a doubt, related to the GPU. I will try again but booted into safe mode and post results. @alexbn71 I wanted to ask you, when you have a GPU isntalled, does your onboard graphics display the unraid boot process/login screen normally? My BIOS is set to force display out the onboard graphics (so unraid does display login/console out the GPU display) and it works as normal, up until the boot process is complete and it goes to the login screen. I just get a black screen and am not able to use the local console. The webui is still fine and accessible, but not locally. Do you have this same behavior? I thought it might be something to do with the nvidia driver plugin, so I posted on the support page. The author claimed the issue was due to me still being on 6.9 and said the issue would go away once I upgraded to 6.10.3.. Well, it didn't. Curious if you have this issue as well

@ich777 So it's been two months since I last posted regarding my issues. I have since updated unraid to 6.10.3 as you suggested, but the problem persists. The problem being that unraid boots up and outputs display on the onboard display adapter, but as soon as it hits the login screen the display shows a blank page. The server is still accessible via the webui and everything seems to work fine. You mentioned previously that this would be resolved upon upgrading to 6.10, however this issue is still there. Additionally, and possibly related, I have crashing/shutdown issues that only seem to occur while a GPU is connected to my system. I've documented the issue HERE. I have tested EVERY piece of hardware in my server. The crashing issue has happened with two different GPUs. I understand if the shut downs are not something you have any input on, I just figured I'd mention is in case it helps in some way. Id really like to know why unraid will not display past the boot process with a GPU isntalled. (and no, the login is not showing while connected to the GPU display either) I've included diags, and can supply any other info if needed. Cheers diagnostics-20220821-1744.zip

I have not run in safe mode with the GPU installed, but I guess I should give it a go. @Frank1940 suppose this is the cause, are you aware of any remedies for this problem? Or what causes it? I've never heard of an issue like this with docker, but I'm clearly no expert.

BIOS is up to date. To my knowledge, the bottom pcie slot in my mobo is the only one that does not support use of a graphics card (mob is Tyan S7012)

I have extensively tested cooling by booting into another OS and running a stress test for well over an hour. The PSU has been replaced previously as well with a 850w Gold rated supply from evga. It should be noted that this shutdown only occurs while in unraid. I can leave the GPU in and boot into something else and there are no issues. Every piece of hardware has been replaced/tested out. All RAM, both CPUs, the mobo, HBA, and PSU. There is no hardware issue here. This shutdown have occurred with 2 different GPUs. Neither of which even use additional power from the PSU

Same thing for me as well. Syslogging to a second unraid server and there's nothing of note there. The logs just end when the shutdown occurs.

Nope. Solid as a rock since I took the GPU out..

Has it crashed again since?