Adrian

Yea that's what I'm hoping. I'm currently running an extended test on one of the drives. Probably take another 6-8 hours to complete. When that's done, I'll try the other drive. And yup, I disabled the spindown. ok, so if the extended test passes for both, just try to start the array and then upload new diagnostics. Got it.

mediaserver-diagnostics-20220718-1723.zip FYI, this is unfortunately captured after I rebooted the server.

So something happened and 2 drives are marked red. I think one is actually dead and the other is fine. I'm running an extended SmartTest on one of them and then the other. I have dual parity. What's the process to "recover" from the two red drives if 1 or both are bad? Do I simply replace the bad drive(s) and rebuild? I've never done this with more than 1 drive.

I was trying to see if I could add a new Video path to Plex for my home videos and I guess I was poking around not really knowing what I was doing. I tried using " Add another Path, Port, Variable, Label or Device" and after I hit Add\Apply, a window popped up (the reconfiguring window) and after I closed it, now the Plex docker is missing. I'm thinking maybe some error with what I tried to add. Any idea how I can get it back without losing any of the data\history ?

Just got back in town, thank you! this worked.

So what's the default username/password to use for a new install? And where exactly is that documented, just curious to see why I had trouble finding it.

I just finally replaced my USB flash drive to a USB 3.0 drive as well as increasing the size. I just wanted to share this with you all, this little bugger is going on 10 almost 11 years and still works!

I want move some drives around. In the UI it jumps from Disk 14 to Disk 16 and it bothers me When I stop the array and reassign the drives, it says Missing Drive, so I want to make sure I don't mess this up. What would be the process? Basically I need to shift 3 drives (16->15, 17->16, 18-17). Thank you, Adrian

4x 2TB drives getting replaced by 1x 8TB drive. Lets ignore how the first drive is upgraded since you're caught up on the method used for that, ignoring the risks of losing a drive in the middle of this process. At some point 3x 2TB need to be removed from the server. Removing the drive and rebuilding parity doesn't provide parity protection during the process. Clearing the drive and then removing it provide parity protection during the entire process.

Thank you John, this is all I wanted.

Yes, except it's going go through the process of reading all the drives to essentially rebuild an empty drive and that's what I was trying to avoid. Sorry, I typed it out really fast and worded it incorrectly. I've corrected my original post. Yes I know it's more work. There's a reason I wanted to do this, I've done it before. So if you know how let me know.

I recall doing this one with some help here, but I don't see the post in my history. Basically I'm upgrading a small drive with a larger drive, but I'm trying to avoid rebuilding the drive. I've excluded the drive from the shares and I've moved all the files off it. From what I recall there was a way to zero out the drive, remove the old drive and install the new drive and then I think you would tell unraid to accept the parity info or something like that. If anyone knows what I'm referring to please link/include the steps. Thank you, Adrian

Thanks, it worked perfectly. I saw it removed from the unassigned devices. I took it out and put the new drive it and after I refreshed the screen I saw the new drive listed. I had to press a button for the clear starts in order to access the preclear button. I guess the addon didn't notice it's a different drive.

It's an LSI Logic SAS 9207-8i Storage Controller LSI00301

I have a Norco case. I have a slot reserved for where I preclear drives. After I preclear a drive, can I remove and put another drive in the slot without shutting down the server?

Thank you! You da man! That finally solved the write permissions issue! Time to run it on all my shares now To add to this. The reason I didn't try that is because it was such a weird issue, only my desktop Windows 8 had issues writing. I have a Server 2012 that I copy files from all the time and never have an issue so this never occurred to me to try.

ok, right now I'm testing it out on one of the shares which is definitely not used by any dockers. I have docker and all the files/configs on my cache drive anyways (I backed it up nightly to unraid)

I don't recall trying this. I'll let you know how it goes. Thanks!

Yes I did, but most of the issues discussed revolved around Windows 10. My Windows 10 issue I fixed. I don't have issues from Windows 2012. Only Windows 8. I don't have issues resolving the name, unraid has been set to master for years. I can read and copy files off it. I just can't write to it from Windows 8. But I went ahead and read through them all over again and I'm going to focus on the ones related to SMB version. btw, any recommendations on what version SMB should be on Windows 8 so that it plays well with unraid?

And I'm back to square one. It's stopped working in Windows 8 and of course on the day I'm ready to move files over from Windows 8. I've deleted the share, rebooted, still unable to write to unraid. I can copy/read files off it no problem.

Yea, I've had unRAID as local master for years now. That was the first thing I checked. That whole case sensitivity is what really got me. It looks like on the Windows 10 box I had to use .\username and then it finally worked. I'll keep doing some testing to make sure. Thanks, Adrian

Dam, thought I had it all. Ok, so that fixed Windows 8, but Windows 10 same issue even after renaming the user to all lowercase. I'll keep looking...

Love the new redesign!

Found this in the Unraid 5 and older forum.... Unraid doesn't let you create usernames with an uppercase, so I must have ignored that and continued to create it with lowercase...completely ignoring the fact that I had a capital letter on Windows. I renamed my user on windows to be all lowercase to match the user in unraid and poof, like magic, it works now

Help, my search skills are sucking and I can't seem to find a solution to a networking issue between Windows and Unraid. Basically I keep getting access denied errors trying to write to Unraid. I can read files, open files, but I can't copy to it with the exception of a Server 2012 R2 that I have on my network. Windows 8.1 PRO - access denied with I try to write to any share. Windows 10 - access denied with I try to write to any share. fixed Server 2012 R2 - no issues The only place that from Windows 8.1 or Windows 10 that I can write to is either the flash drive or the cache drive. I hope someone can point me in the right direction. It's been driving me nuts for several months. Unraid v6.5.3 M/B: Supermicro - X11SSM-F CPU: Intel® Xeon® CPU E3-1230 v6 @ 3.50GHz HVM: Enabled IOMMU: Enabled Cache: 128 kB, 1024 kB, 8192 kB Memory: 16 GB Single-bit ECC (max. installable capacity 64 GB) Network: eth0: 1000 Mb/s, full duplex, mtu 1500 eth1: not connected Kernel: Linux 4.14.49-unRAID x86_64 OpenSSL: 1.0.2o Thank you, Adrian