devilwarriors

PS C:\Windows\system32> Get-SmbClientNetworkInterface Interface Index RSS Capable RDMA Capable Speed IpAddresses Friendly Name --------------- ----------- ------------ ----- ----------- ------------- 20 False False 1 Gbps {fe80::85cb:98c2:bc87:82bc} Local Area Connection 7 False False 1 Gbps {fe80::d76:4935:570c:9565, 192.168.1.230} Ethernet 22 False False 0 bps {fe80::17ef:e2d0:f1b1:bd24} WiFi 14 False False 0 bps {fe80::791d:739b:c6ec:1a2} Local Area Connection* 1 4 False False 0 bps {fe80::f50b:d9c5:f10e:91c4, 192.168.137.1} Local Area Connection* 10 17 False False 3 Mbps {fe80::a948:2a38:36b5:c55d} Bluetooth Network Connection 3 PS C:\Windows\system32> Get-SmbShare Name ScopeName Path Description ---- --------- ---- ----------- ADMIN$ * C:\Windows Remote Admin C$ * C:\ Default share D$ * D:\ Default share E$ * E:\ Default share F$ * F:\ Default share G$ * G:\ Default share H$ * H:\ Default share IPC$ * Remote IPC S$ * S:\ Default share Users * C:\Users Hmm, not really seeing anything related to my NAS, and I'm not really sure how to interpret that information. edit: `Get-SmbConnection` return nothing.

So I do have it set to private and I looked in the credential manager and I can indeed see the credential for my NAS server. With TOWER as the network address.

I'm on windows 10, also to be clear it's not a new windows install, it's been working fine for years. Though thinking about it, it does kind of started around the time windows did an update. I'm still on windows 10 tho, it wasn't the windows 11 update, I've been ignoring that one. Edit: And I do have SMB signing enabled and it was previously properly set up on this machine by having the same password as my user on windows like you link describes. I don't want other people on this network to have access to those shares so disabling it wouldn't be an option.

For about two week I've been intermittently unable to access my share until I reboot, at which point it worked for a bit. Since yesterday, I just can't access it at all, I just get a "Windows cannot access \\TOWER". Even after rebooting and even keeping it off all day today, it still won't work. But I just tried it on Steam deck and I can connect there all fine. I've saw in the log that every minute or so I get a hundred of those errors from the IP of this computer. Jun 16 19:27:09 Tower nginx: 2025/06/16 19:27:09 [error] 7709#7709: *38398 limiting requests, excess: 20.653 by zone "authlimit", client: 192.168.1.230, server: , request: "PROPFIND /login HTTP/1.1", host: "tower" Jun 16 19:27:09 Tower nginx: 2025/06/16 19:27:09 [error] 7709#7709: *38400 limiting requests, excess: 20.631 by zone "authlimit", client: 192.168.1.230, server: , request: "PROPFIND /login HTTP/1.1", host: "tower" Jun 16 19:27:09 Tower nginx: 2025/06/16 19:27:09 [error] 7709#7709: *38402 limiting requests, excess: 20.609 by zone "authlimit", client: 192.168.1.230, server: , request: "PROPFIND /login HTTP/1.1", host: "tower" Jun 16 19:27:09 Tower nginx: 2025/06/16 19:27:09 [error] 7709#7709: *38404 limiting requests, excess: 20.588 by zone "authlimit", client: 192.168.1.230, server: , request: "PROPFIND /login HTTP/1.1", host: "tower"I found a post suggesting to use tcpview to find what is doing the calls. It's from a process called schost.exe, does a batch of 100 calls at the same time every minute or so. Any idea what could be doing that? A bit lost here.

Lot of confusing information about how to rebuild a disk. Do I stop the array, remove the disk, run a preclear on it and then put it back and it should rebuild? Any tutorial you could link if it's not that? Thanks!

It's @bmartino1 who mentioned this a few messages up. I'll just rebuild the disk normally.

I had that question earlier, should I still go ahead with a reset of super.dat and should I do it after or before rebuilding the disk?

Yes I moved it to disk 2 while the disk was still emulated in case I need to get rid of it.

I've ran the unbalance plugin just to move the stuff to another disk but haven't went ahead with zeroing it or any of the other step that were talked in that video. Awaiting further instructions before I do anything else. Would for sure rather save the disk as it's pretty new.

Done, Here the diagnostic. tower-diagnostics-20240522-2222.zip

Can you clarify what you mean here? I think your talking about the order that the sata cable are connected to the motherboard.. but a quick google search lead me back to a post on this forum saying it doesn't matter. The disk is pretty new so I hope it's the cable, I will replace it as soon I find one and will report back. Thanks

Here the diagnostic. The error the drive give is "UDMA CRC error count". I've read on this forum from a google search that it's possible it's the cable that is badly connected and I did open the back of the case which is quite tight. It's quite possible I pinched a cable or it's not connected completely. Is that a possibility from what you see from the smart file or does it really look that bad? Is it safe to flush the super.dat file while one drive is down or should I empty and remove it first? I saw a video tutorial on how to use the unbalance plugin to empty a drive, do I need to do that or can I just remove it from the array and it will put the emulated data on the other drives? I'm lucky that it currently only has 2.5Tb of data that could be moved easily on the 3 other smaller drives. tower-diagnostics-20240519-1738.zip

So I got lucky and the Frankenstein of a USB drive that I rebuild form the files I managed to pull from the old drive and diagnostic files seem to have worked. I did had to reselect my drive, so maybe super.dat was corrupted, but everything is back and the dockers even work as normal without me doing anything. Would still love to know what I lost with losing `/config/secrets.tbd`. But that server is decided to ruin my week-end and so I woke up this morning to my largest and most recent disk having been disabled and now being emulated. Last night it threw 2 smart errors for the first time before bed. Here is the smart file, any idea if it's dead already or what? ST12000VN0008-2PH103_ZL2EM5E5-20240519-0728.txt

The USB drive would no longer mount on windows or mac, but I tried it on linux on my stream deck and I'm able to mount it. The same files were corrupted, but somehow `super.dat` copied fine. Not sure if it's uncorrupted yet, but some hope there. So now with this I'm only missing `secrets.tbd` and `parity-check.log`, assuming I can use `docker.cfg` and `Main.cfg` from the log zip. I tried running fsck.ext4 but it complained about the drive being read-only. I ran it with the `-n` param and it told me that I have a bad magic number in the super-block...

Hi, Woke up this morning to an unresponsive server and after a reset I plugged it to a screen to see that it was blocked on an error about a corrupted bzfirmware file. It appears the firmware main file got corrupted as well as some other files on my USB and I looked everywhere and I don't have a backup sadly. I managed to backup some of the file on the USB before it stopped working for good. It gives me a "Data error (cyclic redundancy check)" error and I can't open it anymore. Those are the files that were corrupted. I couldn't open them or copy them, it gave me a read-only error. bzfirmware /config/docker.cfg /config/parity-check.log /config/secrets.tbd /config/super.dat /shares/Main.cfg Which from what I found appear to be all the important one 😕 So I got a few questions here. 1- What is `Secrets.tbd` and how screwed I am from losing that. 2- There is a 6 months old `tower-diagnostics-20231120-2001.zip` file that contains my `Main.cfg`, `docker.cfg` and `super.dat` files. Is the `super.dat` file the real thing.. or has part of the info been retracted for privacy reasons, like how the `Main.cfg` file has is name partially masked by dashes? 3- Any suggestion of a software that I could try to rescue the files or is it fried. I only have one parity drive so from what I got it should be easy to restructure everything. The parity drive should be the one that I can't mount. Any suggestion on how to proceed with that? I am not much of an unraid expert. Just bough a new USB drive so I can reinstall unraid on it. Thanks!