Leaderboard

Hey there Unraid community! Just wanted to take a moment between all the present opening, food eating, and carrol singing to wish everyone here happy holidays! Thank you all for being so awesome!! All the best, Team LT (Tom, Jon, and Eric) Sent from my Pixel 3 XL using Tapatalk

better storage setup ability to add more nifty things via docker ability to run more vm's including a firewall your coolness factor increases by a factor of 5 virtual 10gbe connection to server from windows vm vs buying 10gbe hardware. ability to divide resources and not waste them if someone watches plex while you're gaming on a standalone computer, your game can suffer vs on unraid you can isolate them from each other did i mention your coolness factor increases by a factor of 5?

Apologies if this has been covered recently, but I thought I'd share a success that may or may not be helpful to some. Specs: i7-4770, 16GB, Q87, IGD, GT730, I was playing around with a Win10 VM and everything was working great - until I rebooted the server. I wasn't trying to pass through the only GPU as the server was given the onboard. Anyway, a bunch of messing around happened (BIOS dumps/stubs/etc.) and I tracked down the problem: It turns out the motherboard BIOS will 'overwrite' the GPU selection setting (igd vs. pcie) if it doesn't detect a monitor connected to what has been selected. I was trying to run the server headless so I had the only monitor connected to the "passthroughed" GPU. This didn't seem to change regardless of the BIOS settings (auto, specified, multi-monitor... didn't matter) Obviously this is a good idea if you're trying to get a normal computer to post but has the bios setting mis-selected; that way you can still see the boot menu. Oddly enough, this doesn't change the selection in the BIOS settings, but I feel that unRaid/KVM gets confused and can't passthrough what has now become the de facto default GPU. So, if I have the monitor connected via HDMI to the onboard during server boot, then swap it over to the card after unRaid has loaded, but before starting the Win10 VM, everything works great literally every time. If I leave the monitor connected to the passthrough GPU during a server reboot: Code 43 literally every time. I have repeated/verified this more than 10 times (usually because I forget to swap the cables.) I haven't tried a dummy HDMI or VGA plug as of yet. That is the next step.

Everything looks fine, though not much to see since diags are after rebooting, but only worth posting new ones if you have some issue.

Very cool. Does this allow for the handling of subfolders by chance?

Edit: I fixed the issue by deleting the mariaDB appdata directory and re-installing. Good evening, I'm having a bit of an issue with my new docker install of mariaDB. I just set the password and then started the docker container, and when I send the command: mysql -uroot -p and then type in my password all I get back is: ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES) Within the docker container logs this is what I am seeing: _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30_config: executing... [cont-init.d] 30_config: exited 0. [cont-init.d] 40-initialise-db: executing... [cont-init.d] 40-initialise-db: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. 181004 19:03:40 mysqld_safe Logging to syslog. 181004 19:03:40 mysqld_safe Starting mysqld daemon with databases from /config/databases I noticed that the advice to one poster was to view the first post and perform the steps there and as I don't have a backup because this is a new install I just performed the following: docker exec -it mariadb bash mv /config/log/ /config/log-old/ exit docker restart mariadb However I am still getting the same results. I have copied and pasted the password directly from the docker editing page, typed it in manually and still I get the same message. Am I missing something really simple here? Thank you in advance for your help