I was a dummy and previously unplugged my USB stick and had to reinstall. Once reinstalled and waited until my parity drives resynced, and now my Windows 11 machine will not connect to it. I have confirmed that the server has an IP address, and when you put that address into the address bar it takes you to the server. I'm unsure how what else to do. I have also attached the diagnostic files from the server.

tower-diagnostics-20250803-0634.zip

Edited August 3, 2025Aug 3 by wannabemedic33

Not sure where you are having problems. Are you able to open the WebGUI? I assume that you are at this point since you have attached your diagnostics and it showed successful user login.

Did you use the /config folder from the previous install on the USB stick to assign the parity and data drives?

Did you use a some other method to assign them?

Does the GUI show the array is running?

Could you provide a screenshot of the MAIN tab of the GUI showing the drive assignments and data usage stats? (obscure the SN of the HD's)

Did you go to SETTINGS and make sure that SMB was enabled?

So, I used a fresh install to reapply the unraid OS to the same USB. The server rebooted and showed that the data was still on the drives, but parity had to resync. That took most of the night but on the unraid side it looks like everything came back together. When I try to map the share to windows it says that the drive is currently mapped to a user with a different username and password. I did change my SMB share from public to private, but unsure if that would stop since I know my username and password. SMB is enabled, which I confirmed in settings, and the GUI shows the array running. I have attached a picture of the running array as well.

So what I've decided to do, which may not have been ideal is I took the array offline, did new config, and will just start from scratch. I'm not sure what else to do and that seemed like the most straight forward option since there cannot be an existing share if its a brand new share.

It looks like only Disk 1 has data on it.

Next you have only share and this is it configuration info (from you diagnostics)

And this what I would expect to be seeing:

Open the SHARE settings and make sure you are exporting the share via SMB. (It is 'off' by default!)

You can also go to the SHARES tab and click on this symbol to the left of the share and look at the files in that share.

Clicking on the blue share name will take to share settings.

5 minutes ago, wannabemedic33 said:

since there cannot be an existing share if its a brand new share

Actually Unraid will automatically create a User Share corresponding to each top level folder on the drives.

However this share will be created with default values which may mean the SMB Export option will be set to No so it is not visible on the network. If you want it visible on the network then you nead to set the appropriate Export setting.

IF you look at the SAHRES tab, it will tell what is being shared via each sharing protocol. See here:

If you see a '-' symbol the share is not being exported. If you don't see the protocol, it is not "turned" on.

I understand. Is there a way to take the array down and start over? erasing the data and starting new? The share does show to be exporting and be in SMB. Unfortunately you were correct in that it is only showing disk 1 and not the whole array. I am went to tools and hit new config hoping that i could create a share from scratch but it does not look like that was possible and it is just recreating the old share. Here is what windows shows when i try to map the drive.

Start here:

https://forums.unraid.net/topic/191221-some-musings-on-smb-and-samba-and-unraid-and-windows/#findComment-1561581

Read the next two posts after this. Before trying to 'map' a drive, first make sure that you can see it in Windows File Explorer. (IF you can not access it via Windows File Explorer, you can not map it!) It is also important to realize that you can end up with your Windows client being logged onto Unraid using Guest credentials--depending on you making changes to Windows to allow that --and Windows will only allow one login to each server. So anytime you want to try a new SMB configuration, you have to reboot your Windows client. So if you make changes as described in the above link, remember to do the reboot after you finish all of them

You would use \\Tower in File Explorer to get to your server.