Arcadejunkie

turns out he messed with the card. I reseated it and all was good......(Only so much I could do remotely)

Had a disk fail while out of town and my kid tried to swap it out and caused me more problems so I had him shut down the server till I had time to mess with it. I got it booted up but get this when launching plex docker.....assuming it has something to do with my nvidia card but don't know what to do to fix it. Can anybody point me in the right direction? (I tried posting in docker forum as well but doesnt look like there has been many response to help over ther in last month or so) Aug 15 18:05:27 Tower rc.docker: binhex-plexpass: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running prestart hook #0: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy' Aug 15 18:05:27 Tower rc.docker: nvidia-container-cli: initialization error: nvml error: driver not loaded: unknown Aug 15 18:05:27 Tower rc.docker: Error: failed to start containers: binhex-plexpass

Had a drive crash and had problems with the rebuild and lost data. Had to let this sit for a month and now finally getting back to it and I can't get plex to launch and I get the following in the log files. Can anybody point me in the right direction to get this back up and running? Aug 15 18:05:27 Tower rc.docker: binhex-plexpass: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running prestart hook #0: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy' Aug 15 18:05:27 Tower rc.docker: nvidia-container-cli: initialization error: nvml error: driver not loaded: unknown Aug 15 18:05:27 Tower rc.docker: Error: failed to start containers: binhex-plexpass

Unfortunately, on this one here there’s no limitations as to the number of drives and there’s nothing I can see as far as a bios on these so nothing I can see to disable :-(

https://a.co/d/08Rkh3w This is the hba

Ok but with no drive attached system still posts and boots into Unraid just fine and that is with both hba’s installed. It is also the exact same hba board as the first one (amazon reorder) I can understand it might have a different firmware but it would be newer so would assume it should work. Not trying to argue, just trying to ensure what I’m telling you is as accurate as possible

Sorry, I forgot to list that. Yes, the flash drive is listed as the first boot device and there’s a UFEI flash drive listed as the second boot device and I disabled the third one just to be sure.

Ok so I know this is old HW but it is what I've got. It's a Fatality z97x killer board. I have 7 sata drives and 1 M.2 drive. I have 3 of the drives using onboard sata controllers and then I have a 4 port hba for the other 4. This config has been working just fine for several years. I finally got to the point I needed to expand some drive space. So I ordered the exact came HBA and put it in my next slot and put in the new drive. Upon doing so I boot to a flashing cursor. If I pull the new drive of but leave the HBA in it will boot so its something with that drive. Tried a different drive and it does the same thing. Really need the space. Anybody have any suggestions?

Not sure how I obtained this as I thought I got it from community apps. However....got binhex and all is good....thx for the help....(I'll get this yet!) lol

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='krusader' --net='bridge' --privileged=true -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'USER_ID'='99' -e 'GROUP_ID'='100' -e 'DISPLAY_WIDTH'='1280' -e 'DISPLAY_HEIGHT'='768' -e 'KEEP_APP_RUNNING'='1' -p '6080:5800/tcp' -p '6090:5900/tcp' -v '/mnt/disks/':'/unraid_unassigned_disks':'rw,slave' -v '/mnt/user/':'/unraid_shares':'rw' -v '/boot/':'/unraid_flashdrive':'rw' -v '/mnt/user/appdata/krusader':'/config':'rw' 'djaydev/krusader' 69bea31bf8f08be67fb1ee51cb9eefe17eb32943b08452f740b3c6c60aca05eb The command finished successfully!

tower-diagnostics-20191205-2159.zip

If this is the wrong location to post this I apologized, but when I clicked on support it brought me here. I an very new to Unraid and I'm giving it my best and it's still beating me, lol. I installed this docker a few days ago and it worked perfectly. Now when I try to go into it all I get is a black screen taking up part of the screen and nothing else. I have tried to update it and I have removed and reinstalled it as well as rebooted the server and all have not fixed it. Can anybody help point me in the direction of what I did wrong or how to fix this?

WOW......Feeling soo stupid.....lol found it and got it updated......I was assuming I had to edit a script or something much harder than that lol......got my drives preclearing now....hopefully by the weekend I can setup my array and really start to get this going......thx again for the help from all!

I have not done that (Completly new and don't know how) I thought I found a thread saying this issue was because this was starting at sector 64 which is what mine were doing so I do think this would fix it. Is there a thread somewhere that can point me to the updated plugin?

Hello, I have ran preclear on two separate disks and both fail writing zeroes to the drive saying it failed mbr write. These are being run on 10g drives and happens about 24 hours in. Is there something I’m doing wrong? TIA