tzotz

Hi guys, I've been using unraid for quite some time now - I have set up a root user and password and also another user with another password. On mt desktop machine I can access the server from chrome using "http://tower" supplying my root+password, also I can access my shares when I click on the unraid root from windows explorer without being asked for my credentials. I have another computer on my local network, there I can log in from chrome just as before but trying to access my shares from windows explorer I received the message below regardless of which user/password pair I supply. What gives? Thank in advance for your help, best, tzotz

Problem solved although I can't really say why. I changed permissions for "Everyone" and I could create a folder then changed it back to what it was and I could create a folder where I couldn't do it before. Why? I don't know - it works. Thanks.

Sorry I forgot to name the share it's "backups"

Attaching diagnostics logs now. tower-diagnostics-20230504-1851.zip

Hi guys, I'm getting this error message 0x8007045D when I try to create a folder on one (and only one) of my shares. The complete message is attached. This only happens on one specific share and not on other shares. Any suggestions as to why? If more information is needed just name it. Thanks for your help, tzotz

Hi, done, array is in operation again. Thanks for all your help. Best, tzotz

Thanks, but no, I only have one slot where the old drive is currently connected. Will report outcome of the procedure. Thanks again, tzotz

Thanks JorgeB, Just to make sure, follow this procedure? Stop the array Unassign the old drive if still assigned (to unassign, set it to No Device) Power down Pull the old drive Install the new drive Power on Assign the new drive in the slot of the old drive Go to the Main -> Array Operation section Put a check in the Yes, I'm sure checkbox (next to the information indicating the drive will be rebuilt), and click the Start button The rebuild will begin, with hefty disk activity on all drives, lots of writes on the new drive and lots of reads on all other drives All of the contents of the old drive will be copied onto the new drive, making it an exact replacement, except possibly with more capacity than the old drive. Thanks again.

tower-diagnostics-20230330-2228.ziptower-diagnostics-20230330-2228.zip Hi JorgeB, The above zip is the diagnostics taken after parity sync. Parity is no longer orange in the drive display. Now, what to do in order to replace my 1 TB drive with the old 3TB parity and rebuild it. Do I have to prepare it in any way? Thanks, best, tzotz

When should diagnostics be run - I'll comply.

tower-diagnostics-20230329-1712.zip These diagnostics were taken with the original data disk and the new parity (after it was synched for 13 hours). Thanks guys for all your help.

I left the new parity which was synched and put back the 1Tb that was previously replaced. Start says "Start will start Parity-Sync and/or Data-Rebuild." If I click on start is there any risk to disks 1 thru 5? Is there a safe way to verify that parity is valid without any risk of data disks being ompromised? I honestly don't know how to go from here? Your help is greatly appreciated. Thanks

The dashboard says: Isn't that enough?

HI Jorge, thanks for your response - I'm afraid I don't follow - first I replaced the parity and synched it judging by the array activity all the disks were read and the parity rewritten - and still not valid parity? thanks also why disk disk 2 in error when I didn't touch it? I only replaced disk 3?

Hi' itimp, thank you for this prompt response - Parity was synched for 13 hours - why all that time if it wasn't rebuilt. Anyway - Do I have to return the 1TB that I meant to replace and rebuild parity? - please tell me how so I won't make a mistake here. Thanks.