dellorianes

I am having problems with the removal of orphan images, during the docker updating process, since some weeks ago. Asking help to AI (Claude), this is the answered we arrive after some days and trials: Please, take as it is, I am zero in linux computing: Descripción: When updating multiple containers at once ("Update All"), the update_container script fails to clean up orphaned images because $oldImageID is always empty. Root cause: In update_container, $oldImageID is obtained by calling getImageID($Repository) which searches images by tag. When processing multiple containers in the same PHP process (passed as *-separated arguments), by the time the second container is processed, Docker has already reassigned the :latest tag to the newly pulled image from the first iteration. The old image is now dangling (no tag), so getImageID() returns null and the cleanup step is skipped. Affected file: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/update_container Proposed fix: Obtain $oldImageID directly from the running container's image reference before pulling, instead of searching by tag: php $oldContainerDetails = $DockerClient->getContainerDetails($Name); $oldImageRaw = $oldContainerDetails['Image'] ?? ''; $oldImageID = strpos($oldImageRaw, 'sha256:') === 0 ? substr($oldImageRaw, 7, 12) : null; if (!$oldImageID) $oldImageID = $DockerClient->getImageID($Repository);Reproduced on: Unraid 7.2.4, Docker 27.5.1

Does Unraid have the uvcvideo module? I would like to use it with a video capture card, with OBS for streaming.

I am having the same problem as Thunderhead. With his permission and without the intention of hogging his thread, please, find my diagnostics file attached.nasdiego-diagnostics-20250423-0903.zip

Please, find it attached bkp-diegonas-diagnostics-20241112-1701.zip

Thank you for answering. OK, I think I have removed the root folder in /boot/config/ssh/root What can I do in order to reactivate the ssh service? Is it possible to uninstall and intall again the ssh service in order to have a brand new configuration? Thank you Regards

Hello, I was testing the spaceinvaderone ssh access tutorial in youtube and now I can not access ssh to my server. I can not access via command line to the folder /root/.ssh of my server If I access as root and try to cd /root/.ssh says "bash: cd: /root/.ssh: Not a directory" If I try to create a folder .ssh inside /root it says "mkdir: cannot create directory ‘.ssh’: File exists" The folder ssh in the usb flash exist (with several key files). If I remove all the keys and data, after enable ssh or reboot the sistem all the files apears there again. bkp-diegonas-diagnostics-20241112-0921.zip

Have you been able to solve it? The same thing happens to me as it does to you. It doesn't matter if I delete it from the Flash Drive or from /root/.ssh, as soon as I restart the server everything is restored.

Since some days I found that Emby Docker is spending a lot of system resources. Their logs are full of this: Info App: Entry point completed: Emby.Server.Implementations.IO.LibraryMonitorStartup. Duration: 0.0178886 seconds Info App: Starting entry point Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.AutomaticRestartEntryPoint. Duration: 0.0004245 seconds Info App: Starting entry point Emby.Server.Implementations.EntryPoints.KeepServerAwake Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.KeepServerAwake. Duration: 0.0001085 seconds Info App: Starting entry point Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.LibraryChangedNotifier. Duration: 0.0011258 seconds Info App: Starting entry point Emby.Server.Implementations.EntryPoints.ServerEventNotifier Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.ServerEventNotifier. Duration: 0.0023471 seconds Info App: Starting entry point Emby.Server.Implementations.EntryPoints.StartupWizard Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.StartupWizard. Duration: 0.0002163 seconds Info App: Starting entry point Emby.Server.Implementations.EntryPoints.SystemEvents Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.SystemEvents. Duration: 0.0003186 seconds Info App: Starting entry point Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier Info App: Entry point completed: Emby.Server.Implementations.EntryPoints.UserDataChangeNotifier. Duration: 8.1E-05 seconds Info App: Starting entry point Emby.Server.Implementations.Channels.ChannelsEntryPoint Info App: Entry point completed: Emby.Server.Implementations.Channels.ChannelsEntryPoint. Duration: 0.0056427 seconds Info App: Starting entry point Emby.LiveTV.EntryPoint Info VaapiCodecProvider: ProcessRun 'ffdetect_vaencdec' Execute: /bin/ffdetect -hide_banner -show_program_version -loglevel 48 -show_error -show_log 40 vaencdec -print_format json Info LibraryMonitor: Watching directory with new FileSystemWatcher for /config/data/livetv/recordings for item 67505 Info LiveTV: Loading live tv data from /config/data/livetv/timers Info VaapiCodecProvider: ProcessRun 'ffdetect_vaencdec' Process exited with code 0 - Succeeded Info App: Entry point completed: Emby.LiveTV.EntryPoint. Duration: 0.0285124 seconds Info App: Starting entry point Emby.LiveTV.RecordingNotifier Info App: Entry point completed: Emby.LiveTV.RecordingNotifier. Duration: 0.0018785 seconds Info App: Starting entry point Emby.ActivityLog.ActivityLogEntryPoint Info App: Entry point completed: Emby.ActivityLog.ActivityLogEntryPoint. Duration: 0.0026949 seconds Info App: Starting entry point Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint Info App: Entry point completed: Emby.Server.MediaEncoding.Api.EncodingManagerEntryPoint. Duration: 0.0017118 seconds Info App: Starting entry point Emby.Notifications.NotificationManagerEntryPoint Info Notifications: Registering event nofitier Emby Server User Notifications Info App: Entry point completed: Emby.Notifications.NotificationManagerEntryPoint. Duration: 0.0108064 seconds Info App: Starting entry point Emby.Server.Sync.SyncNotificationEntryPoint Info App: Entry point completed: Emby.Server.Sync.SyncNotificationEntryPoint. Duration: 0.0015602 seconds Info App: Starting entry point EmbyServer.Windows.LoopUtilEntryPoint Info App: Entry point completed: EmbyServer.Windows.LoopUtilEntryPoint. Duration: 9.19E-05 seconds Info App: All entry points have started And top file is attached. Any idea? Thank you

I am also trying to delete them but I cant. Whatever rebooting the NAS, the ssh keys appears again. Also with known_host and authorized files. I try in maintenace mode and safe mode but I can´t.

HI, I found today several repeated errors about muy nvidia GPU. Jan 21 05:29:45 NASDiego kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Find attached diagnostics. Regards nasdiego-diagnostics-20240122-1707.zip

Some have suffer a crack in the docker? When I try to start it appears the following error message

ok, thank you very much. I will try.

I am suffering randomly disconnections from unraid in my network. Sometimes it resolves by itself in 1 or 2 hours, reconnecting, but other times unraid never connect again to the network and I have hard reset it. During the disconnection I cannot access unraid gui, nor docker, nor VM. I cannot also access it via ssh nor ping the server. Please, find attached the diagnostic file of my server after a lost and connecting again to network. Thank you in advance. Regards llorianes-diagnostics-20231220-1426.zip

No, only moving. one film, for example in disk 1, if renamed, is moved to disk 3 (this could be understandable if disk 3 is emptier than 1) ut it also happens in the film is in disk 3 and while ranaming it is moving also to disk 3 (I made trials). Anycase I rename a film it is moved + renamed. I want only to rename. Is that correct?

Hi, Is it possible to only rename a file and a folder? Anytime I try to do that, filebot renames it but it move the files. Is there a way to only rename them? An operation that can makes in a second spends 20 minutes for a single film (if I have to rename all the movies speds one week).

Absolutly true. Thank you very much. My apologues

Hi, I have been using luckybackup for some weeks but I have a problem with the schedule. I have two tasks scheduled and "cronIT" as per: Time (hour:min): 1:0 Day of week: Monday and another for Thursday month: any Day of Month: any I want a backup every monday and Thursday at 01:00 The problem is that no back is made. The only way I can get a backup is doing it manually. Someone can hel me? Thank you

Hi, I am transferring files (movies) from one share folder to another share folder. I am having very high loads in top window. Is that normal? I havnasdiego-diagnostics-20230822-1223.zipe a i7 9700 (8 cores) cpu. nasdiego-diagnostics-20230822-1223.zip

some help?

I have connected my main Unraid server with a remote server via Wireguard, with a server to server peer. I can ping servers from both sides. What I want now is to make a backup of my main server onto my remote server using luckybackup but the container can not ping the remote server. (10.253.0.6). I think it is a setting up iptables network issue or something. Someone can give me a tuto, please?? Thank you Regards

After removing that, SMB server started to work again. Fix common problems also warned me to change macvlan to ipvlan in Docker settings. Thank you very much. Now, I also have this warning after reset. Should I do something with them? May 16 07:26:52 NASDiego kernel: Warning: PCIe ACS overrides enabled; This may allow non-IOMMU protected peer-to-peer DMA May 16 07:26:52 NASDiego kernel: ACPI: Early table checksum verification disabled May 16 07:26:52 NASDiego kernel: floppy0: no floppy controllers found May 16 07:26:52 NASDiego kernel: i915 0000:00:02.0: [drm] failed to retrieve link info, disabling eDP May 16 07:26:57 NASDiego mcelog: failed to prefill DIMM database from DMI data May 16 07:27:28 NASDiego kernel: ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20220331/utaddress-204) May 16 07:27:55 NASDiego rpc.statd[10765]: Failed to read /var/lib/nfs/state: Success May 16 07:28:05 NASDiego kernel: BTRFS info (device sdi1): using crc32c (crc32c-intel) checksum algorithm May 16 07:28:35 NASDiego kernel: BTRFS info (device loop2): using crc32c (crc32c-intel) checksum algorithm May 16 07:28:40 NASDiego kernel: BTRFS info (device loop3): using crc32c (crc32c-intel) checksum algorithm

Tryed safe mode and continued the same. Upgraded to 6.12-rc5 and the same again. Find diagnostics attached. May 15 22:47:17 NASDiego kernel: Warning: PCIe ACS overrides enabled; This may allow non-IOMMU protected peer-to-peer DMA May 15 22:47:17 NASDiego kernel: ACPI: Early table checksum verification disabled May 15 22:47:17 NASDiego kernel: floppy0: no floppy controllers found May 15 22:47:17 NASDiego kernel: Bluetooth: hci0: FW download error recovery failed (-19) May 15 22:47:17 NASDiego kernel: i915 0000:00:02.0: [drm] failed to retrieve link info, disabling eDP May 15 22:47:26 NASDiego mcelog: failed to prefill DIMM database from DMI data May 15 22:47:27 NASDiego smbd[1563]: tdb(/var/lib/samba/private/secrets.tdb): tdb_transaction_recover: failed to read recovery record May 15 22:47:27 NASDiego smbd[1563]: Failed to open /var/lib/samba/private/secrets.tdb May 15 22:47:27 NASDiego smbd[1564]: tdb(/var/lib/samba/private/secrets.tdb): tdb_transaction_recover: failed to read recovery record May 15 22:47:27 NASDiego smbd[1564]: Failed to open /var/lib/samba/private/secrets.tdb May 15 22:47:27 NASDiego smbd[1564]: exit_daemon: daemon failed to start: smbd can not open secrets.tdb, error code 13 May 15 22:47:27 NASDiego winbindd[1577]: tdb(/var/lib/samba/private/secrets.tdb): tdb_transaction_recover: failed to read recovery record May 15 22:47:27 NASDiego winbindd[1577]: Failed to open /var/lib/samba/private/secrets.tdb May 15 22:47:59 NASDiego kernel: ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20220331/utaddress-204) nasdiego-diagnostics-20230515-2252.zip

Sorry, my English is not as well as I want but I undertooth in @dlandon post that someone (I didn't get alluded to due to I am not in v6.12-rc5) that posts 6.12-rc5 diagnostics to evaluate. I also understand that the problems of @OneMeanRabbit started when he upgraded to 6.12-rc5. So, being me in 6.11.5, are you recommending me to upgrade to 6.12-rc5? Thank you

Up

root@NASDiego:~# ls -la /var/lib/ total 16 drwxr-xr-x 14 root root 280 Nov 20 22:27 ./ drwxr-xr-x 15 root root 360 Dec 31 2019 ../ drwxr-xr-x 2 root root 40 Oct 6 2022 arpd/ drwxr-xr-x 2 messagebus root 60 May 11 15:24 dbus/ drwxr-x--- 2 root root 40 Aug 28 2022 dhcpcd/ drwx--x--- 1 root root 254 May 11 16:18 docker/ drwxr-xr-x 10 root root 220 Nov 20 22:26 libvirt/ drwxr-xr-x 6 rpc rpc 220 May 11 16:18 nfs/ drwx------ 7 root root 140 May 11 15:25 nginx/ drwxrwxr-x 2 ntp ntp 60 May 11 21:24 ntp/ drwxrwx--- 2 root apache 100 May 11 21:45 php/ drwxr-xr-x 6 root root 160 Nov 20 22:26 pkgtools/ drwxr-xr-x 4 root root 80 Nov 15 21:10 samba/ drwxr-xr-x 2 root root 40 May 1 2022 swtpm-localca/ root@NASDiego:~# ls -la /var/lib/samba/ total 0 drwxr-xr-x 4 root root 80 Nov 15 21:10 ./ drwxr-xr-x 14 root root 280 Nov 20 22:27 ../ drwxrwx--- 2 root root 40 Nov 15 21:10 bind-dns/ drwx------ 3 root root 100 May 11 16:18 private/ Thank you again