fulknerra

I had another similar outage last week and this week after disabling macvlan, full lock up but no kernel panics and nothing really in the syslog. This time I was able to specifically correlate it to the APPDATA BACKUP plugin unfortunately as that doesn't log to syslog I can't pinpoint what action the backup plugin was doing, Disabling the functions of the backup has stopped all lockups so I believe it was a mix of macvlan and the backup. I have the following settings enabled backuptype: stop,backup,start each container delete older than: 7days keep at least: 3 appdata sources: /mnt/user/appdata /mnt/cache/appdata destination: /mnt/user/backup use compression: yes, normal verify: yes ignore errors: no backup flash: yes backup VM Meta: yes Checking on the backup directory for any of the previous backups, the container data is all there but what is missing is the flashbackup and the VM meta data, so I am assuming that the system locks up when it attempts to backup the flashdrive. I'm not entirely sure why this happens, but my system has been stable since disabling this function. leaving this information here for anyone else who might stumble across the same issue.

This appears to have resolved the issue, going on more than 4 days of uptime now, which is the best I've seen all month. Thanks

I use a the br0 network so that I can assign individual IPs to every docker and have them be accessible by the host, does ipvlan still allow the same type of setup?

Seems that every other day my unraid box is fully freezing and I have to hard power down, cant tell if its a kernel panic or something else. If I console into the box it just shows an unresponsive login prompt. Syslog (attached) shows a handful of error messages that seem concerning but nothing at the point of failure. At first I was doing a backup of appdata/unraid every night, along with a TRIM, and plugin update check. I've since scheduled all my backups/trims to happen on different days, I also noticed that before every freeze the plugin updater was running, so I removed it, with these changes the freezing is still happening. After the last crash I ran a parity check and noticed that it resolved 5K errors within the first few hours of running but none after that. memtest passed 48/48 tests no errors stresslinux showed no faults ran full SMART tests on the drives, seems healthy. Not sure what I should be looking at resolve this problem Tower.log tower-diagnostics-20231122-0913.zip

It appears that the HBA was improperly flashed, after following a few online guides and flashing SAS9300_8i_IT.bin (via UEFI) I was able to get the device functioning and Unraid now detects the new drives. Thanks for your help JorgeB

The distributor I purchased from stated that the card was flashed in IT mode (and it's missing its bios rom) but I'm guessing it wasn't flashed correctly. It's an LSI SAS9340-8i - But I can only find the FW for the LSI SAS9341-8i from my reading the only difference is that the sas ports on the 40 are on top and the 41 are on the side, if the SAAS3008 chip is the same do you know if I can just flash the SAS9341-8i FW to the card?

I am not able to get my newly installed HBA card to load on my box. changed pci ports updated bios forced pci to gen3 disabled fast boot set pci=realloc=off & iommu=soft in syslinux.cfg I can see the controller in lspci dmesg shows the following error not sure what to try next, any direction is appreciated. tower-diagnostics-20220524-2159.zip

Yup I read up to step 4 and assumed I knew the rest, sorry for wasting your time and thanks for the pointer.

Removed it and rebooted, but still getting the same error when trying to set the GPU -

I can't seem to get passthrough to work Intel® Core™ i3-10100 gpu_top works fine and reports performance intel-gpu-top: Intel Cometlake (Gen9) The intel gvt-g shows available modes and I am able to bind it to a vm the vga controller is in its own iommu group IOMMU group 1:[8086:9bc8] 00:02.0 VGA compatible controller: Intel Corporation CometLake-S GT2 [UHD Graphics 630] (rev 03) but I am unable to bind the GPU to the vm when using Q35-5.1 machine type. I get an error VM creation error XML error: 'model' attribute in <hostdev> is only supported when type='pci' I've tried setting the guc/huc firmware to both 'default' and '2' but it hasnt made a difference, not quite sure what I'm doing wrong. tower-diagnostics-20220107-1322.zip