Sascha_B

The same behavior occurred to me after updating to version 6.12.1. I noticed it after receiving this message in the syslog: Jun 28 02:04:34 Zeus elogind-daemon[1503]: Failed to save session data /run/systemd/sessions/c6: No space left on device Jun 28 02:04:34 Zeus elogind-daemon[1503]: Failed to save user data /run/systemd/users/0: No space left on device. The entry "--no-healthcheck" resolved the issue, thank you!

I got the message too, but only when backing up from Unraid to an SMB share Feb 2 09:07:58 Zeus CA Backup/Restore: Using command: cd '/mnt/user/appdata/' && /usr/bin/tar -caf '/mnt/remotes/RASPBERRYPI_unraid/Appdata/[email protected]/CA_backup_PlexMediaServer.tar.gz' 'PlexMediaServer' >> /var/lib/docker/unraid/ca.backup2.datastore/appdata_backup.log 2>&1 & echo $! > /tmp/ca.backup2/tempFiles/backupInProgress && wait $! Feb 2 09:07:58 Zeus CA Backup/Restore: Backing Up: PlexMediaServer Feb 2 09:10:01 Zeus kernel: traps: lsof[27292] general protection fault ip:1545e1c8c4ee sp:2671bcf0f5eda277 error:0 in libc-2.36.so[1545e1c74000+16b000] Feb 2 09:13:00 Zeus kernel: traps: lsof[3838] general protection fault ip:14e7050494ee sp:650e1fbe4da98bf6 error:0 in libc-2.36.so[14e705031000+16b000] Feb 2 09:13:28 Zeus kernel: traps: lsof[5592] general protection fault ip:149963e844ee sp:7baf20f44494db8e error:0 in libc-2.36.so[149963e6c000+16b000]

I also have these errors in the libvirt log every 10 minutes. My system behaves exactly the same way. After a reboot, the VM run again, the log entries come back. My behavior is in this thread

I had a similar entry, looks like this is an orphan Docker adapter that is no longer used. route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.178.1 0.0.0.0 UG 1004 0 0 br0 10.253.0.2 0.0.0.0 255.255.255.255 UH 0 0 0 wg0 172.31.200.0 0.0.0.0 255.255.255.0 U 0 0 0 br-af3bd9cc0c24 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0 192.168.178.0 0.0.0.0 255.255.255.0 U 1004 0 0 br0 I found this with the following command docker network ls NETWORK ID NAME DRIVER SCOPE 9c73f7ae825c br0 macvlan local 42c79c489b86 bridge bridge local e86908c40902 host host local ce3ed75d3fe3 none null local af3bd9cc0c24 wg0 bridge local Then I deleted it with the command: docker network prune WARNING! This will remove all custom networks not used by at least one container. Are you sure you want to continue? [y/N] y Deleted Networks: wg0 br0 Even after a restart, this is no longer displayed and Docker is running. route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.178.1 0.0.0.0 UG 1004 0 0 br0 10.253.0.2 0.0.0.0 255.255.255.255 UH 0 0 0 wg0 172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0 192.168.178.0 0.0.0.0 255.255.255.0 U 1004 0 0 br0

Hello, everyone! I noticed this behavior after putting the libvirt image on a new SSD. I stopped VM Manager, put the share on the new SSD, copied the libvirt file, checked permissions and started VM Manager again. Before restarting the VM Manager or after rebooting the server, it looks like this. virsh # net-list --all Name State Autostart Persistent -------------------------------------------- default active yes yes virsh # net-edit default <network> <name>default</name> <uuid>62eaa0bf-331c-47ac-9189-56a25fa38d2c</uuid> <forward mode='nat'/> <bridge name='virbr0' stp='on' delay='0'/> <mac address='52:54:00:e5:88:d8'/> <ip address='192.168.122.1' netmask='255.255.255.0'> <dhcp> <range start='192.168.122.2' end='192.168.122.254'/> </dhcp> </ip> </network> route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.178.1 0.0.0.0 UG 1004 0 0 br0 10.253.0.2 0.0.0.0 255.255.255.255 UH 0 0 0 wg0 172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 172.31.200.0 0.0.0.0 255.255.255.0 U 0 0 0 br-af3bd9cc0c24 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0 192.168.178.0 0.0.0.0 255.255.255.0 U 1004 0 0 br0 When I restart the VM Manager, virbr0 does not start again automatically and the VM are no longer displayed but the following error under VMS Libvirt Service failed to start. This can only be fixed by restarting the Docker Service. After that, the VMs are displayed again, but virbr0 does not start automatically. In the routing table, virbr0 is no longer displayed and all VMs that use this adapter do not start and show the following error: Cannot get interface MTU on 'virbr0': No such device virsh shows the following output virsh net-list --all Name State Autostart Persistent ---------------------------------------------- default inactive yes yes If I start the adapter manually, everything goes back to normal virsh net-start default Network default started virsh net-list --all Name State Autostart Persistent -------------------------------------------- default active yes yes Even after a server restart everything starts normally. Is this behavior normal? A second question would be, how do I find out what kind of interface this is? -> br-af3bd9cc0c24 Edit: Found it, was an orphan Docker Adapter Thanks in advance, Sascha zeus-diagnostics-20230119-1221.zip

I disabled the spin down, unfortunately, no values are displayed after hours.

Do you mean Settings - Disk Settings - Tunable (poll_attributes): 1800 It´s set.

Are the values not read out via SMART? There are values displayed everywhere, but not in the dashboard. Is it possible to connect the LSI controller to the backplane of the HP?

Where can I start? My Unraid Version is 6.7.2. The HDD Controller is an P420i in HBA Mode. zeus-diagnostics-20191005-0857.zip

I have the problem that with none of the hard disks the temperature is indicated. All hard drives are active. The temperature can be read out with SMART Tools. Only the temperature of a unassigned device is displayed.