Scott Balkum

Ok, I did all of those steps. One of my disconnected drives was able to be corrected. The other disconnected drive could not. But, bringing up the array with the new config and the 1 saved drive allowed it to come up with dual parity acting properly, protecting the 2 bad drives. I am now able to copy data off without failing. Thank you so much for your efficient and willing help. I sent some beer money, as much as I could. I know a little helps more than nothing. Thank you.

Disk 10 and 20 are currently unmountable because they had disconnected before disk 12 showed all the error. Can I put those 2 disks back in as 10 and 20 and Unraid will see the data on it as valid? Is that what doing the new config will do?

Is there a best way to reintroduce the 2 disconnected drives back in and accept the data that is on them as accurate?

Attached is the smart report for the drive. It doesn’t look good. WDC_WD30EZRS-00J99B0_WD-WCAWZ0131800-20240403-1013.txt

Here are the diags. tower-diagnostics-20240402-1049.zip

Since I haven’t written any data, is there any way I can reconnect those 2 drives that vanished and came back? I feel like if I can get those back, the other errors from other disks won’t be a problem.

Ok, Stopped it and restarted. It has come up. I am copying some data off of it. It shows 2 drives emulated and the rest are online but there are errors copying some data so I have lost some of it for sure. Sounds like I need to get what I can off of it and then completely rebuild UNRAID and ditch the cheap SATA controllers and probably get rid of the old 3TB drives.

I need to let it finish rebuilding right? Before I started the rebuild, all the data appeared to be there.

System has been fine for a while. I do power it off when not in use for long terms. I had it powered up about a week now and was moving data over. Everything was fine. It started performing a parity check so I stopped copying data and just let it run. This morning it had amassed millions of errors and had dumped 4 drives as unavailable. I shut it all down and was able to get 2 back but the other 2 were not coming back. Running dual parity so I kicked off a rebuild and now a 3rd drive is kicking out millions of errors and estimates 400+ days for rebuild. Been running for many hours. What should I be doing different? I’m a little worried about the data. I’m a bit of a data horder and this my be my calling to learn to stop but, for now. What can I do? tower-diagnostics-20240401-2355.zip

Ok, I have discovered the issue, Not Unraid at all. Robocopy was having conflicts with the date and rewriting the dates to 1980. This appears to be a common issue when writing between NTFS and a Linux FS when using Robocopy. I found the files, deleted all the 1980's and then reran without using the /zb switch and added the /fft switch. This resolved the issue and it is now writing properly to cache at 200MB/s

Is it possible that it is attempting to copy files within the folder structure? I have it set to spilt automatically as required. But I'm wondering if its just finishing the structure?

I am running a robocopy script that is copying over about 10TB at a time. It obviously fills up the cache pool at 2TB. I then stop the Robocopy and run Mover.. When you rerun robocopy, it verifies each file and won't write/overwrite a file that is already there and the same/newer. So, when you run the script after filling up the cache and moving, it does verify all those files, but that takes about 5 minutes or so and then it would write to the cache normally. It has been working well for the 23TB I've copied so far. But, now, it isn't. Robocopy will show on the screen the files it is skipping.

Well, I take that back. It seems to have copied 1 large file to cache and then went back to the array. sigh. Attaching the diagnostics.

Well, When copying the files to Unraid array directly, I end up with a write speed of about 7-8MB/s which is extremely low. Writing to the cache I get 100-200MB/s. And oddly, Mover gets about 40MB/s to the array so the net result is it is much faster to copy to the cache and Move than direct. Out of shear curiosity, I tried copying to the array from another machine and it did successfully go to the cache. so, I restarted the original machine and now it is writing to cache. I can't explain that at all but it seems to be working at least now. Not sure if you need my diagnostics since this is working now?

I have a new Unraid install, 6.9.2. I have 16 drives and 2 parity drives in an array. I have 2 1TB SSDs in a raid0 cache pool. I have been moving lots of data over and this has been working great. I fill up the cache and then run mover to move to array. I've moved 23TB so far. Today, copying files over, it is not using my cache at all. It is writing to the array directly. Cache is online and I can see the file structure. My data share is set to "Yes: Cache" and has been unchanged? I am at a complete loss here. I've restarted, taken the array offline, changed the cache settings on share to none and then back again, no change. Cache is basically empty. If I run mover, it scans and completes in 1 minute and doesn't seem to move anything. Any thoughts?