BigHairyWookie

Ok, I think I've figured it out. I had to change all of my shares to Private, add my user with R/W access and add that user into the Windows Credentials. Which seems to have restored access

I've just noticed since upgrading to 6.11.3 that I've lost all access to my network shares from all of my Windows pc's in the house. Tried browsing by using \\tower & \\ip.address, adding "ntlm auth = Yes" to "Settings/SMB/SMB Extras/Samba extra configuration", and also enabling insecure guest logons in gpedit, but nothing is working. GUI access is still working fine and none of my settings have change recently, so really not sure what's going on. Does anyone have any ideas? tower-diagnostics-20221113-1956.zip

Thanks, 3.8 seems to have fixed the issue, must've been a driver thing like you say.

The latest version on T-Rex seems to be giving me some errors and not starting Version 3.6.1 works fine I checked all my configs and they haven't changed, so I'm not quite sure what's going on. Switching to the cuda10-latest tag does work, but I noticed that it was using v0.24.2 of t-rex nvidia-smi output: Any thoughts to what the problem might be?

I'm getting the same things as well. I did get it to work again by rolling back to 1.7.0 but had to re-create my config. Looks like it's put some IPv6 code into the nginx conf file, I don't seem to be able to comment it out or remove it, it just gets re-created. In the Docker setting I put the following the the repository section jlesage/nginx-proxy-manager:v1.7.0

Thought I'd post a quick update. I successfully ran the parity check, removed the SATA card and some of the disks. It gave me the opportunity to actually use one of the drives as an on-site backup, which is probably better for my sanity. I've also added the syslog mirror to the flash drive, just in case. Just need to remember to move this off the flash at some point. So far we've been running for nearly 21 hours with no errors. I'll slowly start to add the plugins back in now.

Ok, I've managed to get the disks mounted and the array started. I basically shutdown the server, removed the flash disk, created a copy, re-imaged the flash drive and copied the Configs folder back over. One drive has come back as Unmountable: no file system, but it's a drive with no data on, so I'm not fussed about that. It's currently started and doing a parity check. I think I might wait for that to complete before doing anything else. @testdasi I replaced the power supply a few weeks ago with a brand new 650w. There was a 430w in there before which I realised wasn't going to cut it with all the new drives. Interesting point about the SATA PCI card, I might try removing that. I currently have both parity drives and one array drive on it, so I'll guess I'll need to be careful how I move stuff around.

Ok, I get that. I really don't know where to start now, short of ripping it all apart and starting again

Unfortunately every time I start the array normally the whole system freezes. I can't get to any diagnostics. I've just been trying to run an xfs_repair on the array disks and this's fine on disks 2-4 but on disk 1 there was metadata to be replayed, so I did the xfs_repair with -L and the whole system froze again. So I'm starting to lean towards that disk as the issue. Just tried starting the array without disk 1 and the whole server froze again.

Hi there I'm only a couple of weeks into using Unraid and I've suddenly starting getting loads of instability issues, where the server suddenly freezes. No response from the gui, can't ping the server, no ssh access, console unresponsive. At first I thought this was down to a plugin, but I've now removed all plugins and I'm still getting the problem. In fact it's now gone so far that after the latest lockup I can't actually start the array, in normal or safe mode, with or without a gui. Can anyone help with some ideas on what to do? **Edit** I can start the array in maintenance mode if I boot in safe mode but don't appear to be able to mount the disks. tower-diagnostics-20200329-1128.zip