Konstellis

Danke!

Warum genau wäre eine Anpassung auf overlay2 sinnvoll? Die ganzen legacy datasets stören mich eigentlich gar nicht...

Hi! Und erst einmal Danke für deinen Erfahrungsbericht! Ich habe das gleiche Problem, dass die ganzen Legacy-Datasets nicht unter /mnt/cache/docker einsortiert werden, da dieser Ordner selbst kein Dataset ist. Habe versucht den Docker-Ordner (manuell) zu konvertieren (so wie ich es auch mit den einzelnen Ordnern in appdata gemacht habe), aber wenn ich das mache, starten die Docker nicht mehr und im Syslog gibt es folgende Fehlermeldung: Sep 29 20:45:03 Storage rc.docker: duckdns: Error response from daemon: error creating zfs mount: mount cache/docker/4c17bbd6779a9461fc2016a714acd5f4c006d048a751732777892419299d9832:/var/lib/docker/zfs/graph/4c17bbd6779a9461fc2016a714acd5f4c006d048a751732777892419299d9832: no such file or directory Sep 29 20:45:03 Storage rc.docker: Error: failed to start containers: duckdns Habe die Konvertierung deshalb wieder rückgängig gemacht, sodass /mnt/cache/docker wieder ein normaler Ordner ist und nun laufen die Docker wieder. Hast du in deiner Lösung den Docker-Ordner konvertiert oder hast du alle Container in einem frischen Docker-Dataset neu aufgezogen?

Hi! Und erst einmal Danke für deinen Erfahrungsbericht! Ich habe das gleiche Problem, dass die ganzen Legacy-Datasets nicht unter /mnt/cache/docker einsortiert werden, da dieser Ordner selbst kein Dataset ist. Habe versucht den Docker-Ordner (manuell) zu konvertieren (so wie ich es auch mit den einzelnen Ordnern in appdata gemacht habe), aber wenn ich das mache, starten die Docker nicht mehr und im Syslog gibt es folgende Fehlermeldung: Sep 29 20:45:03 Storage rc.docker: duckdns: Error response from daemon: error creating zfs mount: mount cache/docker/4c17bbd6779a9461fc2016a714acd5f4c006d048a751732777892419299d9832:/var/lib/docker/zfs/graph/4c17bbd6779a9461fc2016a714acd5f4c006d048a751732777892419299d9832: no such file or directory Sep 29 20:45:03 Storage rc.docker: Error: failed to start containers: duckdns Habe die Konvertierung deshalb wieder rückgängig gemacht, sodass /mnt/cache/docker wieder ein normaler Ordner ist und nun laufen die Docker wieder. Hast du in deiner Lösung den Docker-Ordner konvertiert oder hast du alle Container in einem frischen Docker-Dataset neu aufgezogen?

It worked. Thank you so much!

Thanks for the swift answer! Unfortunately, it is still shown as busy. May it have something to do with the drive being formatted as encrypted xfs? I would like to keep it encrypted...

Hi Guys. I was just looking for a way to disable reflink to reduce the FS overhead on the disk size and found this topic. If I try to use makfx.xfs on the disk I get "mkfs.xfs: cannot open /dev/md2p1: Device or resource busy" (also in maintenance mode). If I stop the array, the device cannot be found obvsl: "Error accessing specified device /dev/md2p1: No such file or directory" What do I need to do to apply the command?

This is a BUMP, as the problem persists for me and others... Out of nowhere I could not access my shares from my windows 10 workstation anymore. I am getting the error "0x80070035 The network path was not found." At first I suspected the UnRAID Box (6.11.5) to be the issue because I changed the root password. But then I noticed that my W10 Laptop has access to the shares. On my workstation I already tried the following: in registry \LanmanWorkstation\Parameters: set AllowInsecureGuestAuth to 1 deleted login credentials (there were no unraid-related credentials anyway...) Network security: LAN Manager authentication level -> Send LM & NTLM-use NTLMv2 session security if negotiated re-installed SMB 1.0/CIFS in Windows features disabled windows firewall re-enabled netbios network reset set network to public (and back to private bc it didnt help) switched network discovery back and forth I hope somebody has another idea... Thanks! Edit: I removed all users except "root" and am finally able to access the shares. However, I am not able to move files over to the server. It says "You need permission to perform this action - Try again - Cancel". What a mess is this?? Edit2: Now it works. Had to set all shares to "public" instead of "secure".

Hi Guys, I am super frustrated. Out of nowhere I could not access my shares from my windows 10 workstation. I am getting the error "0x80070035 The network path was not found." At first I suspected the UnRAID Box (6.11.5) to be the issue because I changed the root password. But then I noticed that my W10 Laptop has access to the shares. On my workstation I already tried the following: in registry \LanmanWorkstation\Parameters: set AllowInsecureGuestAuth to 1 deleted login credentials (there were no unraid-related credentials anyway...) Network security: LAN Manager authentication level -> Send LM & NTLM-use NTLMv2 session security if negotiated re-installed SMB 1.0/CIFS in Windows features disabled windows firewall re-enabled netbios network reset set network to public (and back to private bc it didnt help) switched network discovery back and forth I hope somebody has another idea... Thanks!

Thank you for your reply! So there is no way to make an SMB share remotely accessible with read-only permissions?

Hey guys, I would like to make my SMB shares remotely accessible to a guest (read-only) via wireguard. The shares are set to "Secure" and a guest account is present. How can I create a WG tunnel/peer which is exclusively tied to the guest account? Thanks and regards! JP