-
SFHS crashing
I am not sure where to start but SFHS appears to be crashing for me. When I do "df -h | grep shfs" it does not show the /mnt/user or /mnt/user0 I did change my cache drives AND move to ZFS a week or two ago and have been pretty much hands off my server other than getting into VMs, automated media adding and jellyfin until I upgraded from 7.1.4 and then a day or two later tried to add another container. Fresh power power cycle everything works fine for a while. I can us my jellyfin, plex, ARR stack, and VMs appear to be working like normal. the df command 12459 /usr/libexec/unraid/shfs /mnt/user -disks 15 -o default_permissions,allow_other,noatime -o remember=0 root@Tower:~# ls -ld /mnt/user /mnt/user0 df -h | grep shfs pgrep -a shfs drwxrwxrwx 1 nobody users 60 Oct 23 07:00 /mnt/user/ drwxrwxrwx 1 nobody users 60 Oct 23 06:57 /mnt/user0/ shfs 22T 19T 3.4T 85% /mnt/user0 shfs 22T 19T 3.4T 85% /mnt/user 12448 /usr/libexec/unraid/shfs /mnt/user0 -disks 14 -o default_permissions,allow_other,noatime 12459 /usr/libexec/unraid/shfs /mnt/user -disks 15 -o default_permissions,allow_other,noatime -o remember=0Then if i open up palmr (what i use to share some files) or go into any of my docker configs and try to adjust a folder path the shfs crashes root@Tower:~# ls -ld /mnt/user /mnt/user0 df -h | grep shfs pgrep -a shfs ls: cannot access '/mnt/user': Transport endpoint is not connected ls: cannot access '/mnt/user0': Transport endpoint is not connected df: /mnt/user0: Transport endpoint is not connected df: /mnt/user: Transport endpoint is not connected Unraid stays up and no visible issues (dockers stay up, vm stays up) but they dont actually work since they cant access the data paths I hope that makes sense! tower-diagnostics-20251023-0657.zip
-
7.0.1 - Wrong pool state after replacing failed cache drive
root@Tower:~# btrfs fi show warning, device 1 is missing Label: none uuid: 985ca7ab-96c4-4a7c-a0ed-81e5d5d0bddb Total devices 2 FS bytes used 22.13GiB devid 2 size 1.86TiB used 275.01GiB path /dev/sdf1 *** Some devices missing
-
7.0.1 - Wrong pool state after replacing failed cache drive
Hi, I had a cache drive fail. Unraid was still up and working, did a clean shutdown to replace and am now getting a "Wrong pool state". I tried starting the array with the new drive, without the new drive selected, without either drive selected, in maintenance mode. Not sure what the next step is but really don't want to have to delete the pool and redo all of my dockers and such Looked threw a couple of forum and reddit posts and those were the steps i understood how to do. Thanks for reading and maybe helpingtower-diagnostics-20250503-2331.zip
bighick
Members
-
Joined
-
Last visited