lonebear

ETA Self solved. I just replaced a disk. Running data-rebuild as is expected and wanted. However, after about 5 minutes the rebuild stops. I have stopped all containers, and am not writing or reading from the array. I have also removed dynamix scheduler to make sure that there is no app/program/plugin that will touch the rebuild. This will obviously make the rebuild take forever. Help!

Just because I like grasping as straws, I tried this...again...and it worked as well as it has all other times. Which is not at all. First network path not found then no permission, even though I can 'access' via nfs/tcpip. and it is a share set to public in SMB/CIFS and NFS

Finally got around to trying this. Even with a server reboot still no SMB access.

I'm leaning 99.999% some change that M$ made during a patch. Tested by creating a new stand-alone linux file server. Could not connect with main machine. Luckily for me, this summer is the 'refresh main box' summer.

Post reboot it looks like my cache (SSD) failed. "unmountable dsk present." First thing I'll do is change any and all shares to not use cache. Is there anything else? I have apparantly lost docker and all the apps there, including plex. ETA1: and yet more oddness. my /dev/sdx have 2 different ownerships, some are root:disk and others are root:plugdev ETA2: Yup totally hosed: btrfs check --repair /dev/sdj1 enabling repair mode WARNING: Do not use --repair unless you are advised to do so by a developer or an experienced user, and then only after having accepted that no fsck can successfully repair all types of filesystem corruption. Eg. some software or hardware bugs can fatally damage a volume. The operation will start in 10 seconds. Use Ctrl-C to stop it. 10 9 8 7 6 5 4 3 2 1 Starting repair. Opening filesystem to check... Checking filesystem on /dev/sdj1 UUID: 0c527032-0726-4a31-a2f2-e5ff18ec2bc8 repair mode will force to clear out log tree, are you sure? [y/N]: y ERROR: failed to write super block for devid 1: flush error: Input/output error ERROR: failed to zero log tree: -5 WARNING: fsync on device 1 failed: Input/output error I expect I need to get a new cache drive then rebuild somehow.

Version 6.11.5 Yet again, no changes on my side. Server is running parity check right now. In the middle of some file moves form Win10 onto the server I get "Error 0x8000FFFF:Catastrophic failure" I am connecting with IP to the NFS, as CIFS/windows shares have not worked for over a year. The server will be rebooted as a check. But I'm not expecting it to work. As expected, the microsoft forums are useless. Any clues/ideas/directions?

Thanks for the idea, but nope. As I said too many times above. I changed nothing. If there was a win10 patch that changed things I haven't been able to find it. I'm just dealing with the annoying permissions and other issues until I get my next system.

And big thanks. Watching syslog shows no errors on statup. I may make this a quarterly scan just because.

um... a big duh to me. Trying proper command now. I blame not enough coffee.

in /var/log/syslog May 14 07:14:34 Tower kernel: XFS (md8): metadata I/O error in "xfs_da_read_buf+0x9a/0xff [xfs]" at daddr 0x302f87cf0 len 8 error 74 stopping and running xfs_repair on any disk gets me root@Tower:/var/log# xfs_repair -n /dev/sdc Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... ...................................................................................................................................................................................................^C Am I going to have to figure out how to rebuild from scratch? tower-diagnostics-20230514-0713.zip

been there, done that. numerous times.

It. Is. Not. Unraid. I've gotten that through my thick skull. I can get to the shares from another new-build windows box. Something that I can not figure out changed on my Win10 box. (As I'm sure I mentioned upthread). Any pointer to UnRAID fixes and changes will be ignored.

@Wadzwigidy I looked, but I do not have a plugin "unassigned devices", nor do I have "enable SMB security" as an option. Also, based on testing from a new-build server the problem is with the virus called Windows 10. I can connect to the smb shares from the new-build, but not from current desktop. Thankfully, a new desktop is in the plans for the very near future.

will try that sometime this weekend. thanks again for the side directions to look at.

@JonathanM tried new user. same failure.

Thank you @JonathanM I will try a new user.. Strongly doubt it is hardware as NFS connects, Plex connects, all other apps and utilities work.

looks like it's all my fault. even though i made no changes on my main computer I was able to connect using SMB using another box. I will give up with anger at M$ for making whatever change they did to my main system. The best I can do now is bring up systems 1 and 2 and see if I can look through all listed and tested network configs to see if i can find a difference. Until I replace my current desktop in a year or so UnRAID is now in a less useful state for me.

To clean the system: all shares on unraid are back to how they were (yes/public) for all shares I want to export. A new? oddness. When I go to Network / ip address I can see all NFS shares and go into them, but attempting to mount creates an error.

Running from original install on the box from manufacturer. Not a custom anything. No changes have been made by me before the shares failed. ALL changes have been done since NFS and SMB failed. The system is now even less useful as I can only see/access one of my regular shares, which were all accessible under NFS before I tried all these 'fixes'. And before you ask, I have rebooted the windows box after each attempted fix.

@trurlI will find/build a new win box sometime today. I personally changed nothing. I do allow windows to update its own security.

details grabbed from my systems. Win: ip WIRED ipv4 IP DHCP mask 255.255.255.0 gw 192.168.1.1 dns (google for testing) No IPv6 Credential Manager win credential to IP using user/password SMB 1.0 ALL off SMB Direct on UnRAID: network settings protocol IPv4 only nfs enable: yes smb enable smb: Yes (Workgroup) enable smb multi channel: no macos: no netbios: yes share: jeff nfs export yes security public smb export yes security public

Yup. even worse now. Can not even mount NFS shares. Going backwards at light speed now.

@shpitz461 I have never had IPv6 running. All the other questions have been tried and answered.

Already done. As stated in the fact that I've run through all the steps in the multi page pdf that everyone points to. It was set this way when it stopped working.

checked my /etc/sabba/smb-shares.conf and all shares show there with correct options