gekoch

no thats not a problem since the LXC runs on cache where there is plenty space left. not anymore, removed all of them. Thats why I like to run all python scripts on this lxc

yeah i had to use kill. I now moved all files to a new cache drive. I tried to start the LXC, but cant, even If i use a backup: lxc-start DebianLXC lxc-start: DebianLXC: ../src/lxc/lxccontainer.c: wait_on_daemonized_start: 837 Received container state "ABORTING" instead of "RUNNING" lxc-start: DebianLXC: ../src/lxc/tools/lxc_start.c: lxc_start_main: 307 The container failed to start lxc-start: DebianLXC: ../src/lxc/tools/lxc_start.c: lxc_start_main: 310 To get more details, run the container in foreground mode lxc-start: DebianLXC: ../src/lxc/tools/lxc_start.c: lxc_start_main: 312 Additional information can be obtained by setting the --logfile and --logpriority options Creating a new container works however EDIT: lxc-start -n DebianLXC -F lxc-start: DebianLXC: ../src/lxc/network.c: setup_hw_addr: 3864 Address already in use - Failed to perform ioctl lxc-start: DebianLXC: ../src/lxc/network.c: lxc_network_setup_in_child_namespaces_common: 3911 Address already in use - Failed to setup hw address for network device "eth0" lxc-start: DebianLXC: ../src/lxc/network.c: lxc_setup_network_in_child_namespaces: 4062 Address already in use - Failed to setup netdev lxc-start: DebianLXC: ../src/lxc/conf.c: lxc_setup: 3896 Failed to setup network lxc-start: DebianLXC: ../src/lxc/start.c: do_start: 1273 Failed to setup container "DebianLXC" lxc-start: DebianLXC: ../src/lxc/sync.c: sync_wait: 34 An error occurred in another process (expected sequence number 3) lxc-start: DebianLXC: ../src/lxc/start.c: __lxc_start: 2114 Failed to spawn container "DebianLXC" lxc-start: DebianLXC: ../src/lxc/tools/lxc_start.c: lxc_start_main: 307 The container failed to start lxc-start: DebianLXC: ../src/lxc/tools/lxc_start.c: lxc_start_main: 312 Additional information can be obtained by setting the --logfile and --logpriority options The same problem as before... I think there is something wring with my network config...

No idea either... No idea what or who has created those files... I will test this how can I kill no the container? do i need to search the id of the application via ps -ef and then kill it?

I did now a scrub manually: Scrub started: Fri Jan 17 08:54:00 2025 Status: finished Duration: 0:05:24 Total to scrub: 164.00GiB Rate: 517.33MiB/s Error summary: no errors found and here are the diagnostics nas-diagnostics-20250117-0859.zip

its me again... Now my container seems to be stuck and I can't even force kill it with: lxc-stop DebianLXC -k

yeah why not and of course I can help and test things

Yes I use macvlan since I use an unifi system and when I started with Unraid i had a lot of problems with ipvlan. Reboot is not important for me. I just tested it once and the container did not reboot thats why I wrote here. The container seems now to be damaged somehow. I cant get it back up and running. So i made a new one and copied the data over and now that works again. But I don't know why it failed suddendly No even the new one cant be restarted successfully... So from the beginning I was not able to successfully restart a container via the reboot command within the container.

Interesting you mention this since this morning i get this error when starting the container: root@NAS:~# lxc-start -F DebianLXC lxc-start: DebianLXC: ../src/lxc/network.c: setup_hw_addr: 3864 Cannot assign requested address - Failed to perform ioctl lxc-start: DebianLXC: ../src/lxc/network.c: lxc_network_setup_in_child_namespaces_common: 3911 Cannot assign requested address - Failed to setup hw address for network device "eth0" lxc-start: DebianLXC: ../src/lxc/network.c: lxc_setup_network_in_child_namespaces: 4062 Cannot assign requested address - Failed to setup netdev lxc-start: DebianLXC: ../src/lxc/conf.c: lxc_setup: 3896 Failed to setup network lxc-start: DebianLXC: ../src/lxc/start.c: do_start: 1273 Failed to setup container "DebianLXC" lxc-start: DebianLXC: ../src/lxc/sync.c: sync_wait: 34 An error occurred in another process (expected sequence number 3) lxc-start: DebianLXC: ../src/lxc/start.c: __lxc_start: 2114 Failed to spawn container "DebianLXC" lxc-start: DebianLXC: ../src/lxc/tools/lxc_start.c: lxc_start_main: 307 The container failed to start lxc-start: DebianLXC: ../src/lxc/tools/lxc_start.c: lxc_start_main: 312 Additional information can be obtained by setting the --logfile and --logpriority options "Cannot assign requested address" What address? Mac address? I can still create a new one that is working but I can't start the one that was running the past few days...

thx for testing

that's exactly what i did. The restart button in Unraid works but the reboot command withing the LXC does not reboot the LXC.

Sending SIGTERM to remaining processes... Sending SIGKILL to remaining processes... All filesystems, swaps, loop devices, MD devices and DM devices detached. Halting system.

Ok here is the last part of the log that might be interesting: All filesystems, swaps, loop devices, MD devices and DM devices detached. Rebooting. lxc-start: DebianLXC: ../src/lxc/network.c: setup_hw_addr: 3864 Address already in use - Failed to perform ioctl lxc-start: DebianLXC: ../src/lxc/network.c: lxc_network_setup_in_child_namespaces_common: 3911 Address already in use - Failed to setup hw address for network device "eth0" lxc-start: DebianLXC: ../src/lxc/network.c: lxc_setup_network_in_child_namespaces: 4062 Address already in use - Failed to setup netdev lxc-start: DebianLXC: ../src/lxc/conf.c: lxc_setup: 3896 Failed to setup network lxc-start: DebianLXC: ../src/lxc/start.c: do_start: 1273 Failed to setup container "DebianLXC" lxc-start: DebianLXC: ../src/lxc/sync.c: sync_wait: 34 An error occurred in another process (expected sequence number 3) lxc-start: DebianLXC: ../src/lxc/start.c: __lxc_start: 2114 Failed to spawn container "DebianLXC" lxc-start: DebianLXC: ../src/lxc/tools/lxc_start.c: lxc_start_main: 307 The container failed to start lxc-start: DebianLXC: ../src/lxc/tools/lxc_start.c: lxc_start_main: 312 Additional information can be obtained by setting the --logfile and --logpriority options the cache is btrfs

interesting, I made a new container with the save distribution and release and there the reboot does work for the new container! Can I somehow transfer all the settings and installation to the new container? EDIT: Strange. I created a new container, and now the reboot function no longer works. Even in the container where it was working before, the reboot function has stopped working.

hmm I rebooted unraid and tested again, but still same issue...

ok here are the files nas-diagnostics-20250113-1445.zip

when I'm in my lx containers cli and like to reboot the container and use the command reboot it does shutdown but does not start again. i need to manualy start the lxc in the unraid menu again. Is this normal?

yep I had already figured it out currently only the drivers 550.40.07 do work Andy

Great, thx 550.40.07 is working well Andy

When I check the website for the same card I see this driver version: After installing 550.54.14 on unraid 6.12.8 transcoding with emby is not working anymore. switching back to 535.154.05 is solving the problem but why? Andy

Hy It took me several days to figure this one out but I'm still not sure what causes the problem. My Setup: I have an nvidia T1000 in my unraid server used to transcode movies especialy when using emby. When I start an mkv file with emby it starts transcoding with ffmpeg. On Unraid 6.12.6 this works flawless. However after updating to 6.12.8 emby can't transcode it using ffmpeg. Attached two log files. Both with the same movie one with the old and one with the new unraid version. In the log file running the new unraid version you can see the error: 17:25:44.862 [h264_nvenc @ 0x114dd40] Failed locking bitstream buffer: invalid param (8): ~hfE? 17:25:44.862 Error submitting video frame to the encoder 17:25:44.872 [libmp3lame @ 0x10c74c0] 3 frames left in the queue on closing 17:25:45.121 Conversion failed! I'm not sure what exactly causes the problem so I hope someone can help me.... Thx Andy new OS 6.12.8.txt old OS 6.12.6.txt

after 48h of uptime no crash! Thx a lot for the help, seems resolved with the ipvlan setting.

ok thx for the explanation. In an earlier post I did add the syslog file directly from the log file folder. So the system is currently running on 6.12.2 for the past 2 hours, fingers crossed

ok thx did switch it to ipvlan, now udpate again to 6.12.2 and test it if the server is stable?

here is the file the crash should be around 01:30 in the morning of the 27.06.2023 syslog

so this is not the file in the diagnostic file?