o0atomos0o

EDIT - 1/21/26: Did a backup and yolo'd updating through the Home Assistant GUI. So far so good! I am wanting to update Home Assistant Operating System from 16.3 to 17.0 as it looks like many people are reporting a smooth update with no issues. Curious if anyone has suggestions on how to do this properly when running HomeAssistant_inabox? I run most of my apps in docker but this VM/docker app always seemed like magic and I wasn't sure how it works. It works so I never questioned it. I'd image to update the operating system will require some extra steps?

Yea same. Mine is a 1080. Sadly this little issue caused me to go down the wrong road thinking my docker.img was corrupted. Had to re-add all my containers only to realize it was a GPU driver issue. Got it working! Oddly it wasn't letting me change the version. So I had to uninstall the plugin, re-install, then follow those steps. Thanks!

After reading through some similar posts, I tried installing another version of the driver but keep getting this error: +============================================================================== | WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING | | Don't close this window with the red 'X' in the top right corner until the 'DONE' button is displayed! | | WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING +============================================================================== ----------------Downloading Nvidia Driver Package v575.64.05----------------- ---------This could take some time, please don't close this window!------------ ---------------Can't download Nvidia Driver Package v575.64.05----------------What's odd is that no matter which version I choose, it will always show v575.64.05 in the error message.

I recently updated Unraid from 7.2.0 to 7.2.3 and after reboot, 3 of my containers that were dependent on my GPU are no longer starting. After a little digging I started to suspect it was an issue with my GPU and went to the Nvidia Driver Plugin and found this error: Nvidia Driver Version: 590.44.01 Open Source Kernel Module: No Installed GPU(s): NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.I looked thru the documentation in this thread but it doesn't appear anything really lines up. My GPU acceleration was working fine for these containers previously before doing an Unraid update. tower-diagnostics-20260115-1959.zip

This feels like a very dumb question but is 00:00 in UTC or my local time zone set in my settings? Bonus points for explaining. I'm mostly concerned that I know what time I'm setting to ensure my parity check happens in the most optimal idle times.

Curious if this Marshalleq ever got this issue resolved? I'm currently running a new build with AMD 1800x and Gigabyte AX370 Gaming K7 board. I'm trying to run my initial parity-sync and my server locks up (soft lock?). The web GUI will be down and the server won't send signal to the monitor but the discs are spinning. I've tried disabling c-states, ensuring memory is set to auto, and set power control with no luck. I'm now trying parity-sync with rcu_nocbs=0-15 but not feeling very optimistic.

Swapped the drive for a WD Red Pro and picked up a third. Swapped the SSD for a WD Black w/ heat sink. All drives appearing in unraid and SMART test for the SSD no longer goes past 30C. ☺️

Memtest was looking great. I swapped the cables between the 2 disks and the 12TB drive still wouldn't show. I'm gonna try to replace it tomorrow with a WD Red Pro. Hopefully that does the trick and I will update. Those WD Gold's seems to be really frigged up.

I will try a cable swap between the 2 drives (2 cables). I also am almost done with a memtest to rule out faulty memory. It's nearing completion with no errors.

I've been having some issues with getting my unraid server built. With a fresh new build I was unable to get drives to appear in my server. I have since returned drives with microcenter tested drives and replaced the PSU (Tuf Gaming 750W Gold) and cables. I also replaced sata data cables. At this point in time, my drives were all being detected in BIOS and by unraid. I'm now working with a Samsung 970 M.2 Nvme drive (cache), 18TD WD Red pro (parity), 12TB WD Gold (disk). This morning I was beginning to get my array started and was assigning drives. I began by starting expanded test but immediately got temperature warnings for my SSD. All the other drives were proceeding without errors. I was reading that Samsung has software issues with temperature and is causing my temp warnings. So I increased the threshold to 80 and chugged along assigning drives. After assigning all the drives, I restarted my server for to turn on SVM in the bios. Once it was online, my recently assigned 12TB WD Gold disk was no where to be seen. I did re-disable SVM by the way. I've scoured the forums and have tried various things such as pci=realloc=off and replacing the sata cables and switching sata ports on the mobo. Currently it's sitting in sata port 2. According to my the mobo manual (AX370 Gaming K7), port 3 is disabled with M.2 installed. I'm fully prepared to return the drive for another 18TB Red Pro because I've been having so many issues with the WD Gold drives. Perhaps the diagnostic logs can provide some clues before I try replacing the drive. I did look through the logs and am seeing errors such as Mar 23 14:38:21 ShapLabsServer kernel: ata3.00: failed to read native max address (err_mask=0x1) Mar 23 14:38:21 ShapLabsServer kernel: ata3.00: HPA support seems broken, skipping HPA handling Mar 23 14:38:21 ShapLabsServer kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300) shaplabsserver-diagnostics-20240323-1549.zip