gabrieleancora

Thanks Jorge, I followed your advice and re-created a new flash drive and after booting the system with a new unraid installation (to check if the disks were all recognized, i did NOT start the array), I copied the old config folder to the usb and on new boot all the config was there. Furthermore there were also the dockers I created after the backup, I guess those config are saved in appdata. After starting the array it did a parity check but luckily it finished without errors and now everything is working fine. Thanks again!

It sounds janky to me too, but I could also try to manually upgrade the backup file using the https://docs.unraid.net/unraid-os/manual/upgrade-instructions/#manual-upgrade-or-downgrade guide...?

Good afternoon everyone, the USB with Unraid OS recently died recently and I just bought a new one to use. I was planning to use the backup I made some time ago, but I discovered it's on version 6.12.15 of Unraid, while I have upgraded to Unraid 7.1.3 before it died. What are my options? Should it be safe to restore this old backup, then upgrade and just after start the various VM/Dockers? Or should I give up, do a fresh install and then re-configure everything manually? Thanks

I'm still getting alerts every ~12h/24h, with pollonly in the settings I wasn't getting any (I removed it) 12-08-2024 23:43, 13-08-2024 18:18, 14-08-2024 07:02 and 14-08-2024 19:05 Attached the logs with level 2. I still got full log file but now I have increased to 512mb so if you need more let me know. nut-debug-20240814191233.zip

Hello, I let it test for 24h and got 3 alerts, at 10:54 of the 11 of august, at 23:08 of the same day and at 13:53 of the 12th of August. Attached are the logs (the syslog was full I hope they recorded at least one event). I'll lower the debug level to 2 just to avoid filling the syslog...nut-debug-20240812190804.zip

I think this time I got it right.: nut-debug-20240811101308.zip Like before for now I only got one alert around 15 min after activating NUT, will let you know if it happens again. nut-debug-20240811101308.zip

Uh I was asleep and didn't see your message. Anyway I'm attaching the log level 6 log, I received just only one alert around 15 minutes after I re-enabled the plugin and then nothing, could it be that the fix is working from the second time on...?nut-debug-20240810104424.zip I'll change the config and the log level and let you know if something changes.

I saw your comment on the github issue, I will remove the pollonly and raise the log level to debug 6, I will download the log in 12h~ and let you know how many alerts do i get.

Hello, I installed the latest preview version of NUT in my Unraid server but I'm still receiving alerts regarding the battery replacement. I attached the debug log. edit: I'm adding back the pollonly config line to ups.conf just to avoid mail spam... nut-debug-20240809195153.zip

Well you were right. I actually noticed that but I didn't think it would affect so much, especially since my moving procedure has been to take /boot via scp and paste it in the new usb ... Thanks for the help!

Good afternoon everyone, I need some support because I can't figure out what is happening to my NAS. Recently I bought an internal usb header and today I wanted to install it, so from the GUI I stopped the whole array, checked that everything was shut and shut down the system. After installing the header I moved the USB stick (and cleaned a bit of dust..) but when I rebooted the webgui wasn't working at all. I SSH'd in and figured out that nginx and php-fpm didn't start automatically (strange...), so I started them manually and the webgui returned back, but just after doing a login I get a 500 error. Digging a bit further I found an error related to a plugin in the /var/log/phplog plugin so I disabled the one I though was the problem (by adding .old to the plg file), but even after restarting the nginx and php daemons (and doing a reboot) it still isn't working. Can you help me figuring out what is wrong? I think the web daemons not starting automatically is also probably related to all of this. I'm attaching the diagnostic command output (where I manually added the phplog file under /log) and the list of installed plugins. tower-diagnostics-20240608-1416.zip

So since the drivers are automatically loaded I just need to map the /dev/dri path to the docker and they can share it happily?

Thanks for the quick answer! I won’t assign a gpu to both a docket and a vm to avoid troubles. But I’m not sure why would I need to disable the intel igpu drivers: I do already see the entries in /dev/dri (as far as I have understood from here the drivers are loaded already: so why would I unload the drivers by putting the file in /etc/modprobe.d? Aren’t the driver used by the docker themselves?

Hello everyone! After a couple of weeks of fiddling and testing, following a lot of guides and topics on this forum, I think I can say I have reached a "stable" server. I wanted to have some confirmations regarding GPU and iGPU usages, since I have read too many posts from various times so I would like to know if I have understood correctly everything. Keep in mind that what I'm saying and asking is referring to Unraid version 6.12.8 and I only have an integrated GPU. Intel GPU drivers are now automatically enabled. (In fact I have video output from the hdmi port, not that I use it). BUT I have to install intel_gpu_top to be able to view the stats in the dashboard with the GPU statistics plugin. (In fact I have both of them installed). To enable QuickSync transcoding (and nothing more) in a docker, since now intel GPU drivers are automatically loaded on boot, I just have to add a new device and point it to "/dev/dri" and eventually select the right option inside the docker application (for example on Plex enable "use hardware decoding"). I can do this for multiple dockers and they can share the same iGPU at the same time without problems. At the same time, I can assign the iGPU to multiple VMs, but only one of that can boot at the time and use the GPU. This is necessary if I want to do use that gpu at all, from HW transcoding to do 3D rendering. Am I right? Also I'm not sure if at the same time I can run an hardware transcode using the Plex configured at the point 3. I could, theoretically, install the plugin "Intel-GVT-g" and enable it by adding a line in /etc/modprobe.d/i915.conf. By doing so I would disable the existing intel drivers but I would be able to virtually split the iGPU and assign it to multiple VMs and use it at the same time. Would that preclude me to use the HW transcoding on the Plex configured at the point 3? Plugging a dummy HDMI to an iGPU port helps to mitigate a lot of issues, so it's nice to have it. If you add a discrete GPU you can dedicate it to one or more VM, following the same rules of the point 4 (so it can be configured to multiple VMs but it can be used by one at the time). Also here having a dummy plug helps. Did I understood everything correctly? If I just want to have a Plex server and maybe another transcoding docker, do I have only to follow steps 1,2,3 and 6? I'm asking all of this because by following multiple guides I found myself disabling drivers, adding files, enabling and disabling GVT-d only to realize that I was following out of date information or guides that weren't really for my use case. Thanks a lot to everyone in advance!