Tisrok

Great suggestion. After several restarts of both machines, deleting all credentials through win cred manager twice, I can now access it. But only using it's name ( \\tower ) but not the local IP. Strange, but if I try to connect to it's IP, I get access denied using the same exact credentials. It works enough for me to not care about the discrepancy but still. Win 11 has been a true bundle of joy for an old XP guy like me.

My situation is as follows. I needed to move files from my backup share to my appdata share. It demanded permission from unix user All shares are set to public, and export enabled. On Win 11, where I'm trying to do this all from, I can't sign into the \\tower at all, it pulls a credential pop up, i enter my root user credentials, doesn't work. Enter windows creds, also doesn't work. I'm 100% sure the user/pass are correct. I get an error saying "\\tower\share not accessible and might not have permissions to use this network resource, contact the administrator to see if you have permissions. Multiple connections to a server or shared resource by the same user, using more than one username, are not allowed. Disconnect all previous connections to the server or shared resource and try again" I'm pulling my hair out trying to fix this. Diagnostics attached. tower-diagnostics-20240731-0157.zip

Everything worked out. Parity was successfully rebuilt. Old parity drive swapped, old data drive swapped, all is running perfect and no data loss.

Thanks to you and the mod, this worked. I rebuilt the parity on the formerly removed 1TB drive (about two hours). Verified everything was in order, which it was (unraid is awesome) Then followed the procedure but starting with the parity drive. Stopped the array. Unassigned 4TB parity drive. Shut down. Installed 12TB parity drive. Booted up. Assigned new drive to old drives slot. Started array. Rebuilding currently, should take about 20 hours for my array. After it completes, I'll install the new data drive using the same process. Thanks again.

Thank you for the help, that sounds like the logical solution. I'll give it a try.

Greetings, I'm having issues replacing some drives with new larger ones. My current config, A 4TB parity drive, several 4TB data drives, and a few 1TB data drives. I'm trying to switch one of those 1TB data drives out for a 12TB one, and then the parity drive from 4 to 12TB as well after. I followed the "safer method" procedure in the Unraid Docs. Stopped the array, replaced a 1TB data drive with the new 12TB. Assigned the new drive to old slot in the GUI. Started the array. Array receives a start error. First it said "wrong disk" now it just says "Disk in parity slot is not biggest." If I were to swap that 4TB parity with new 12TB parity, correct me if I'm wrong but wouldn't it fail to rebuild my data drive? Not sure what I'm missing here but any help would be appreciated. Thanks ahead.