-
Guest has not initialised the display (yet)
I had the same problem and finally figured it out. I had some trouble with the explanation in this thread earlier so I thought I would write it out so people could understand it better: When you select a driver, it needs to run on a bus, and then a slot on that bus. For virtual drivers, it should be running on bus=00x0. Then each VM has a slot. so if you spin up the 8th vm, it should get bus 00x0 and slot 0x08. For whatever reason The VM can end up using/detecting incorrect PCI graphics bus for its VM Console video driver. This can occur when you make a change a VMs video driver (Selecting QXL, Cirrus, passthgough, etc) or just by starting and stopping the vm, and creating a new one So to fix it we need to edit the template of the vm. the GUI does not show us these advance options, so we need to edit the xml file that the template is made from. Right click you VM and select Edit. On the edit page, select the "FORM VIEW" button at the top right, and toggle it to "XML VIEW". Now you can edit the xml of the VM Look for the <video> section of code. You can see mine below, and for some strange reason it was on bus 0x08, slot 0x01. <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x08' slot='0x01' function='0x0'/> </video> I then checked the XML files of my other 2 VMs and they were set to bus='0x00', slot='0x01' And bus='0x00', slot='0x02' Which is accurate because the VM video driver should be on bus 0x00. So I changed my xml for my non working vm to be bus='0x00', slot='0x03' (Giving it its own slot that is unused by the other Vms). This solves the issue. Bonus: If you are dealing with pass-through video, you can find out your Graphics cards Bus and Slot by running this command: lspci -nn | grep VGA For me this returned: 07:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU116 [GeForce GTX 1660 Ti] [10de:2182] (rev a1) And from this I can see that my Graphics card is on Bus 07, slot 00 (The numbers at the front)
-
[Support] kru-x - wordpress
3 Things need to be done in mysql. Create new database Create new user Grant permissions for created user to created database. Once thats all done, ensure the unraid templates variables all match. So if your database name is 'website', then your WORDPRESS_DB_NAME value should be 'website'. Make sure all fields match exactly, it is case sensitive too. But if youre still having the error, you can figure out whats going on with some better logs. On the Unraid template, goto the bottom and click "Add another Path, Port, Variable, Label or Device" Then add This: Config Type: Variable Name: WORDPRESS_DEBUG Key:WORDPRESS_DEBUG Value: false Default Value: true Description: Enable debug screen on error Now when you start up you will get a much more detailed description of whats going on instead of just "Error establishing a database connection."
-
Repeatedly failing Unraid server - USB blacklisted | Flash Device Error | Cannot Allocate Memory
Glad to hear. So it was the same issue (A docker causing a memory overflow) Just happened to me again. Was like, "WTF did my USB stick die?" Nope, same problem as before. I replaced my router and I forgot to setup forwarding for my cameras, so the Shinobi docker was throwing up errors again and flooded Unraids Memory. Thank goodness I knew about this problem now. Years later and it looks like its not being addressed on Unraids end (Either by proper alerts/logs, or the prevention of dockers being able to fill up memory like that). I've edited the title and main post to help others find this thread, as I am sure many more people will run into the same issue with various docker containers.
-
[Support] MattFaz Repo
Edit: Solved my own issue (Which is what usually happens). Anyway, the solution was to uncheck "Confidential" when creating a new client in Firefly 3. I spun up firefly 3 docker. got it working Spun up firefly3 data importer docker, but this is where the problem begins. I have to enter 2 fields here: Firefly III URL: Client ID: So I head over to my firefly3 instance, click profile, click oauth and create a client using the callback url I was given from the importer (http://192.168.1.102:8401/callback) Ok back to Importer. Client ID appears to be 2. Not sure what to enter for Firefly III url? I enter the url for my firefly 3 instance (seems obvious). I enter: http://192.168.1.102:8400 Ok got the info I need: Firefly III URL: http://192.168.1.102:8400 Client ID: 2 I push submit. It appears to work because if I put other data, I get nothing, but putting the data as is, I get this: Firefly III v6.1.16 Authorization Request Application "firefly" is requesting permission to access your financial administration. Would you like to authorize firefly to access these records? You will be redirected to http://192.168.1.102 which will then be able to access your Firefly III data. I click Authorize, but then get a 500 Server Error Log shows this: [2024-05-20 21:55:14] production.ERROR: Client exception when decoding response: Client error: `POST http://192.168.1.102:8400/oauth/token` resulted in a `401 Unauthorized` response: {"error":"invalid_client","error_description":"Client authentication failed","message":"Client authentication failed"} [2024-05-20 21:55:14] production.ERROR: Response from server: "{"error":"invalid_client","error_description":"Client authentication failed","message":"Client authentication failed"}" [2024-05-20 21:55:14] production.ERROR: View [error] not found. {"exception":"[object] (InvalidArgumentException(code: 0): View [error] not found. at /var/www/html/vendor/laravel/framework/src/Illuminate/View/FileViewFinder.php:139)
-
[Plugin] Docker Compose Manager
Its been 2.5 years. Has anything new changed? I updated this plugin and I still dont see anything. So I have to make a stack through the GUI instead of using the Docker-Compose command through command line? What are my migration steps to do this? All my files for Jitsi are in /mnt/disks/NVME/appdata/jitsi\github\docker-jitsi-meet but the Stack I made with this GUI is pointing to (/boot/config/plugins/compose.manager/projects/Jitsi) .Do I have to move all the files in there? This is on the boot stick tho. Maybe Im still confused as to what this plugin actually does?
-
Action Center Enabled
For anyone who wants this banner gone (Everybody it seems haha), You can block the element with ublock origin or whatever ad blocker youre using. It gets rid of All banner notifications, but if you're like me, you would rather see nothing than have to deal with seeing Action Center Enabled every month. Cheers
-
[Support] Octoprint docker template - Spants
Has anybody figure out how to update the docker container and NOT lose all your plugins? Im running such an old version of Octoprint but if I try to update, all my plugins are missing. I think the problem is because the Actual plugins are not installed in the /octoprint folder, Only the settings for the plugins are. And the Actual plugins are installed somewhere on the image that gets overwritten when you update the docker. This is why if you re-install the plugins you had, they come back already configured (Because the settings are in the octoprint folder, but not the actual plugins) To fix this we need to add a line mapping the folder of the plugins to our Appdata folder. But I dont know what folder that is
-
Repeatedly failing Unraid server - USB blacklisted | Flash Device Error | Cannot Allocate Memory
I did eventually resolve the issue. The problem was that the hard drive I have been recording all my Camera footage to (With Shinobi) had died and Shinobi was constantly throwing up errors. These errors were essentially 1000+ a minute and so after a day or 2, the memory would get flooded and cause this meltdown on unraid. I didnt notice because using Shinobi, I could still see the camera streams and dont often check the saved footage and in the software, there was no obvious errors posted unless you poked around and looked for the logs. So the problem was being caused by the Shinobi docker. But thats not to say others cant have the same problem caused by different issues with other dockers. Whats clear here is Unraid failed to provide any sort of logs/indication that the problem was being caused by memory overflow from a docker. So if youre having this problem yourself, I recommend going down to 0 dockers, and enabling one after each week of stability to make sure no one individual docker is causing your problem, since one definitely COULD be From Unraids end, I would like to see some improvements made to the error reporting system. A docker (Any docker container) should not be allowed to get out of control like this where it takes down my entire server, and then the server doesnt even tell me anything thats wrong and just stops working, throwing up USB not recognized errors. How about an error that says something like "hey you have a docker thats utilizing 80+% of all your memory. Or "memory usage is increasing in this docker, etc etc. SOME sort of indication that could help troubleshoot. I wasted WAY too much time trying to solve this issue and unraids logging was useless in trying to diagnose the issue.
-
Disk2: device is disabled, contents emulated unraid
Replying to myself cause I figured it out from another, slightly different thread. You need to do these steps to get it working again Stop the array Set the failed disk to "no device" Start the array Stop the array Now the device will be re-enabled. Set the disk back to the hard drive Start the array. The data on the drive will be rebuilt from the parity
-
Disk2: device is disabled, contents emulated unraid
As the title says, I get this error. I accidently pulled out a SATA cord from one of the drive will the computer was on. So now I am getting this error, even after I plugged the cable back in and rebooted. I stopped the array, put it in maintenance mode, ran a check, rand smart disk check. I dont see any errors? This is what I get when I run repair on it. Afterwards its still the same. Even after I start the array no longer in maintenance mode or restart. What do I do here?
-
Repeatedly failing Unraid server - USB blacklisted | Flash Device Error | Cannot Allocate Memory
So I replaced the motherboard completely, and the problem happened again. This time on the new board I was able to retain a bit of control tho. I can actually access terminal and the GUI. The Gui shows memory usage at 0. But doing the top command, I can see memory is being used. Below are the logs: Edit: I was able to partially recover the system somehow. Since I had a bit of control I slowly navigated over to the docker tab and shutdown my jellyfin and shinobi (security camera) dockers. I'm not sure if this helped or not, but ffmpeg was using a lot of cpu so I killed those 2 dockers. After like 10 more minutes it just suddenly recovered (kinda). By Kinda I mean almost everything seems ok, but my reverse proxy wasnt working. Still needed to reboot the system to fix things. At least I was able to actually stop the array
-
Repeatedly failing Unraid server - USB blacklisted | Flash Device Error | Cannot Allocate Memory
Tried disabling C-states and no help, just failed again. I managed to somewhat load part the apps page and got this message. Why am I out of memory? I have 64 GB of ram on this machine, and usually only 30% is in use. OR is this just a generic message from some other failure?
-
Repeatedly failing Unraid server - USB blacklisted | Flash Device Error | Cannot Allocate Memory
Its an Asrock B550 Itx motherboard. It turns out there was an internal header. I bought a cable to get the USB 2.0 functionality from that internal header. So now Im running Unraid on USB 2.0 and on a USB 2.0 stick. The same problem continues to happen. Its happened 3 more times since I last posted. I dont have logs from the last 3 times cause my main computer died. But now I setup syslog server on my laptop which im on until I fix my main computer, so once it fails again ill have logs. But the symptoms of a fail remain the same: - Unraid is pingable - Cannot GUI or SSH into machine - Dockers stop working - Array contionues to work, Network shares are accessible - Hard reboot of powerbutton required to fix back to normal - Plugging in HDMI to use local command prompt, I just see a message saying out of resources and cant type anything. Now I have rebooted, heres some hardware info from my dashboard: Description UnRaid Server Custom Registration Unraid OS Plus Uptime 11 minutes Motherboard Temperature: ⋅⋅⋅ °C ASRock B550 Phantom Gaming-ITX/ax American Megatrends International, LLC., Version L2.61 BIOS dated: Tue 14 Feb 2023 12:00:00 AM PST Processor Load: 4%Temperature: 59.4 °C Processor Load: 6%Temperature: 58 °C AMD Ryzen 5 5600X 6-Core @ 3700 MHz Hide details Overall Load:6% CPU 0 - HT 62%19% CPU 1 - HT 76%4% CPU 2 - HT 81%9% CPU 3 - HT 93%5% CPU 4 - HT 106%7% CPU 5 - HT 112%2% Memory 64 GiB DDR4 Utilization: 22% Maximum size: 128 GiBRAM22%Flash22% Usable size: 62.7 GiBLog1%Docker48% Interface Inbound: 85.2 KbpsOutbound: 127.5 Kbps Mode of operation bond0fault-tolerance (active-backup), mtu 1500 bond1bond down eth02500 Mbps, full duplex, mtu 1500 loloopback Power UPS Model: Back-UPS RS 1500MS2 UPS Load: 144 W (16 %) UPS status:Online Battery charge:99 % Runtime left:44 minutes Nominal power:900 W Output voltage:- GPU Load: 0% Temperature: 43 °C Processes: 0 NVIDIA GeForce GTX 1660 Ti PCIe Gen (Max): 1 (3) Lanes (Max): 16 (16) Load - Memory0%0% Encoder - Decoder0%0% GPU - Memory (MHz)300405 Fan - Power30%19W PCI Bus Rx/Tx (MB/s)00 Power State - ThrottlingP8Yes (gpu_idle) Active Apps
-
Repeatedly failing Unraid server - USB blacklisted | Flash Device Error | Cannot Allocate Memory
i've tried 2 different flash drives One USB 3 and the other USB 2, in 5 different ports. There is no USB 2.0 ports on my motherboard, only 3.2 and 3.0
-
Repeatedly failing Unraid server - USB blacklisted | Flash Device Error | Cannot Allocate Memory
Hello, anybody have any ideas? It just failed again. Was up for 4 days this time, but alas, same issue! Here is a bit of the log for this time
007craft
Members
-
Joined
-
Last visited