ded32 1 Posted January 22 Posted January 22 Hi, To try Emby server, I installed lastest Synology SPK: emby-server-synology72_4.9.3.0_x86_64.spk on Synology RackStation (RS 3618xs) running latest DSM 7. Unfortunately there were no option to uninstall this SPK via Package Center. I don't see the package item in "Installed Packages". How can I uninstall it? Thank you in advance.
Luke 42077 Posted January 22 Posted January 22 HI, then it sounds like it's not installed. I would just delete the server data folder if it is there: Emby Server Data Folder
ded32 1 Posted January 22 Author Posted January 22 Thank you. I did so, rebooted the NAS, but see many Emby traces on the system: user 'emby', group 'emby', package 'emby' in a package lists, etc etc What should I do?
Luke 42077 Posted January 22 Posted January 22 Are you ultimately planning to reinstall? If so then I think you can do that now.
ded32 1 Posted January 23 Author Posted January 23 (edited) Yes I want to completely uninstall it. I tried to use Emby Synology package published in DSM Package Center, ver. 4.8.11.0-724081100. I installed and then uninstalled it through Package Center interface. After that I got problems from NFS and authorization on my RackStation (called NAS3 below). 1. In Synology Central Management System (CMS) now I see NAS3 as offline. When I detach it and attach back, CMS viewer shows NAS3 configuration is very slowly (3-15-10 min) and only once without updating, and then NAS3 becomes offline in CMS (actually the server is online). 2. I got problems with NFS shares. When I mount a directory hosted on NAS3 (Synology RS 3618xs, DSM 7.3.2 latest update), to a directory on any another Synology NAS in the same local network (say DS 1813+, DSM 6.2.4 latest update), using a command like sudo mount -v -t nfs NAS3:/volume1/shared ./access_to_rs3618xs (tried also -o hard / -o soft, with or without -o nfsvers=3) mount command sometimes connects OK, but sometimes shows that output: # sudo mount -v -t nfs -o hard,nfsvers=3 NAS3:/ ./access_to_rs3618xs mount.nfs: timeout set for Thu Jan 22 10:40:39 2026 mount.nfs: trying text-based options 'hard,nfsvers=3,nolock,addr=192.168.0.63' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: trying 192.168.0.63 prog 100003 vers 3 prot TCP port 2049 mount.nfs: prog 100005, trying vers=3, prot=17 mount.nfs: trying 192.168.0.63 prog 100005 vers 3 prot UDP port 892 mount.nfs: portmap query retrying: RPC: Timed out mount.nfs: prog 100005, trying vers=3, prot=6 mount.nfs: trying 192.168.0.63 prog 100005 vers 3 prot TCP port 892 mount.nfs: portmap query failed: RPC: Timed out mount.nfs: trying text-based options 'hard,nfsvers=3,nolock,addr=192.168.0.63' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: trying 192.168.0.63 prog 100003 vers 3 prot TCP port 2049 mount.nfs: prog 100005, trying vers=3, prot=17 mount.nfs: trying 192.168.0.63 prog 100005 vers 3 prot UDP port 892 mount.nfs: portmap query retrying: RPC: Timed out mount.nfs: prog 100005, trying vers=3, prot=6 mount.nfs: trying 192.168.0.63 prog 100005 vers 3 prot TCP port 892 mount.nfs: portmap query failed: RPC: Timed out mount.nfs: trying text-based options 'hard,nfsvers=3,nolock,addr=192.168.0.63' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: trying 192.168.0.63 prog 100003 vers 3 prot TCP port 2049 mount.nfs: prog 100005, trying vers=3, prot=17 mount.nfs: trying 192.168.0.63 prog 100005 vers 3 prot UDP port 892 mount.nfs: portmap query retrying: RPC: Timed out mount.nfs: prog 100005, trying vers=3, prot=6 mount.nfs: trying 192.168.0.63 prog 100005 vers 3 prot TCP port 892 mount.nfs: portmap query failed: RPC: Timed out mount.nfs: trying text-based options 'hard,nfsvers=3,nolock,addr=192.168.0.63' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: trying 192.168.0.63 prog 100003 vers 3 prot TCP port 2049 mount.nfs: prog 100005, trying vers=3, prot=17 mount.nfs: trying 192.168.0.63 prog 100005 vers 3 prot UDP port 892 mount.nfs: portmap query retrying: RPC: Timed out mount.nfs: prog 100005, trying vers=3, prot=6 mount.nfs: trying 192.168.0.63 prog 100005 vers 3 prot TCP port 892 mount.nfs: portmap query failed: RPC: Timed out mount.nfs: trying text-based options 'hard,nfsvers=3,nolock,addr=192.168.0.63' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: trying 192.168.0.63 prog 100003 vers 3 prot TCP port 2049 mount.nfs: prog 100005, trying vers=3, prot=17 mount.nfs: trying 192.168.0.63 prog 100005 vers 3 prot UDP port 892 mount.nfs: portmap query retrying: RPC: Timed out mount.nfs: prog 100005, trying vers=3, prot=6 mount.nfs: trying 192.168.0.63 prog 100005 vers 3 prot TCP port 892 mount.nfs: portmap query retrying: RPC: Timed out mount.nfs: Connection timed out In the cases when mount command is OK, after that, when I try to access the directory mounted, ./access_to_rs3618xs, for the first time, I see a very long delay, about 3-6 min, and after that the access becomes OK. I test it by trying to ls ./access_to_rs3618xs to get directory listing, but it may be any command which tries to access. Immediately after this delay, dmesg | tail or /var/log/messages shows this: 2026-01-22T17:30:33+03:00 NAS3 kernel: [192345.848665] INFO: task mountd:4205 blocked for more than 120 seconds. 2026-01-22T17:30:33+03:00 NAS3 kernel: [192345.855982] Tainted: P O 4.4.302+ #86009 2026-01-22T17:30:33+03:00 NAS3 kernel: [192345.862311] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 2026-01-22T17:30:33+03:00 NAS3 kernel: [192345.879191] ffff88096d457c58 ffff88096d454000 ffff8810396c8d00 ffff88001f07e800 2026-01-22T17:30:33+03:00 NAS3 kernel: [192345.887585] ffff88096d458000 ffff88001f07e800 ffff881012758d7c 00000000ffffffff 2026-01-22T17:30:33+03:00 NAS3 kernel: [192345.895965] ffff881012758d80 ffff88096d457c70 ffffffff8157b820 ffff881012758d78 2026-01-22T17:30:33+03:00 NAS3 kernel: [192345.904348] Call Trace: 2026-01-22T17:30:33+03:00 NAS3 kernel: [192345.907183] [<ffffffff8157b820>] schedule+0x30/0x80 2026-01-22T17:30:33+03:00 NAS3 kernel: [192345.912831] [<ffffffff8157ba99>] schedule_preempt_disabled+0x9/0x10 2026-01-22T17:30:33+03:00 NAS3 kernel: [192345.920033] [<ffffffff8157d13f>] __mutex_lock_slowpath+0x8f/0xf0 2026-01-22T17:30:33+03:00 NAS3 kernel: [192345.926946] [<ffffffff811891fb>] ? lookup_fast+0xbb/0x330 2026-01-22T17:30:33+03:00 NAS3 kernel: [192345.933174] [<ffffffff8157d1b2>] mutex_lock+0x12/0x30 2026-01-22T17:30:33+03:00 NAS3 kernel: [192345.939019] [<ffffffff81189f81>] walk_component+0x211/0x400 2026-01-22T17:30:33+03:00 NAS3 kernel: [192345.945456] [<ffffffff8118b1ac>] path_lookupat+0x8c/0x220 2026-01-22T17:30:33+03:00 NAS3 kernel: [192345.951693] [<ffffffff8118e775>] filename_lookup+0x95/0x130 2026-01-22T17:30:33+03:00 NAS3 kernel: [192345.958120] [<ffffffff81180ce2>] ? cp_new_stat+0x112/0x120 2026-01-22T17:30:33+03:00 NAS3 kernel: [192345.964449] [<ffffffff811430a6>] ? kzfree+0x26/0x30 2026-01-22T17:30:33+03:00 NAS3 kernel: [192345.970093] [<ffffffff8119673d>] ? dput.part.0+0x1d/0x1e0 2026-01-22T17:30:33+03:00 NAS3 kernel: [192345.976332] [<ffffffff8118e45b>] ? getname_flags+0x4b/0x180 2026-01-22T17:30:33+03:00 NAS3 kernel: [192345.982756] [<ffffffff8118e8c1>] user_path_at_empty+0x31/0x40 2026-01-22T17:30:33+03:00 NAS3 kernel: [192345.989372] [<ffffffff811df2d8>] SyS_name_to_handle_at+0x48/0x1b0 2026-01-22T17:30:33+03:00 NAS3 kernel: [192345.996378] [<ffffffff8157ec4a>] entry_SYSCALL_64_fastpath+0x1e/0x93 I see that mountd daemon hangs, but i have no idea what could be the reason. I suspect that may be problems in authorization but it is only a suppose. When connecting to NAS3 from other hosts (including VirtualDSM 6.2.4 hosted on the same physical server, NAS3) I'm getting the same long waits. I haven't seen this problem before. I didn't configure any hard/soft in those days except installing/uninstalling Emby. These problems are very annoying and made my work broken. Can you help what are the reasons for this and how to solve this problem? Edited January 23 by ded32
Luke 42077 Posted January 23 Posted January 23 Hi, and you think these issues are related to installing and uninstalling the emby package?
ded32 1 Posted January 23 Author Posted January 23 Yes, this issues appeared immediately after installing and uninstalling the emby package. I did nothing with the server in weeks. By the way, emby traces in package lists, users/groups etc are still in the system after uninstalling the emby package. I suspect that the reasons of the issues are in problems in uninstalling of the package. Please help me to restore server to the working state.
Luke 42077 Posted January 24 Posted January 24 On 1/22/2026 at 11:00 PM, ded32 said: Yes, this issues appeared immediately after installing and uninstalling the emby package. I did nothing with the server in weeks. By the way, emby traces in package lists, users/groups etc are still in the system after uninstalling the emby package. I suspect that the reasons of the issues are in problems in uninstalling of the package. Please help me to restore server to the working state. I know this may seem backwards, but what if you install again and then try to uninstall?
ded32 1 Posted January 25 Author Posted January 25 I tried to install/uninstall Emby Synology package published in DSM Package Center to clean Emby traces in the server configuration. But after that, I got errors in NFS authentication (timeouts and "error 13" messages). I installed/uninstalled Emby Synology package once more + rebooting, the timeouts are still exist
ded32 1 Posted February 4 Author Posted February 4 11 hours ago, Luke said: Hi, did you figure anything out? No; the same status. Need your help 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now