danimal86

Interesting. I'm using both my old and new drives are both USB2 drives and i'm using one of those adapters to take a mobo usb2 connector and gives an usb port inside the case. I'll keep an eye out to see if it comes back. Would my diagnostics show that error now that i've migrated over to a new flash drive.

My parity check is complete and i gave Limetech the goahead to transfer my license. I did a flash backup and used that with the USB creation tool to make a new flash drive. I then copied the pro.key that they sent me with the one on the flash drive and plugged er' in and booted er' up. Another parity check has been started, hopefully this USB IS NOT READ-WRITE is behind me (it popped back up since then). Anyone know what is the cause of this kind of error? Is it an issue with the physical drive or a software thing?

The new .key will be provided by unraid support?

Ok, i'm going to wait till the parity check is closer to being complete before i have them transfer the license. Once its transfered, i should be able to make a fresh flash drive backup, use the USB creator tool to make the new flash drive, and then copy the config file from the old flash drive to the new flash drive and boot it up?

Ooooooo. That will make things much easier! So what happens after they issue me a new key?

I got an email back from unraid support. "What is the new USB GUID? In order for us to issue you a replacement key, please email us from the account used to purchase Unraid and provide both the previous and new Flash GUIDs. If you cannot access the old GUID, attaching a purchase receipt or old license keyfile will suffice." I'm trying to figure out how to do this without a lot of down time. The parity check is running now and should be done late tomorrow. So once my parity check is complete, i can swap flash drives back over to the new one and get the new guid, send that to them and wait for a response with a new key? It took them about 4ish hours to respond, so i guess thats not the end of the world as far as down time goes. Is there a better way, or any way to get the new flash guid off of the drive itself?

Looks like my flash drive wasn't black listed. I was able to swap the flash drive back to the old one and get the array running, but upon starting the array it started a parity check.....14tb seems like it take about 30hrs. At least this will buy me some time to get a response back from unraid support. And it looks like the apps tab is back now.

I know you guys are doing your best to answer stuff as quickly as possible, so i dont want to be pushy, but i'll bump it up if i haven't heard anything in a few hours. I reached out to support via the link on the "enter the code we sent to your email" pop up page. Said it could take up to 3 days 😵 for a response. I'll try shutting down and seeing if the old flash drive hasn't been blacklisted.

Man i wish you would have responded sooner lol, i already made a new flash drive from a backup I made a backup this morning and used the usb creation tool to make a new flashdrives on a kingston usb2.0 metal drive and popped it in the server first issue was it said i had 2 keys (i upgraded from plus to pro during the sale), so i shutdown pulled the flash drive, deleted the "plus.key" from my config file. now it says The registered GUID does not match the USB Flash boot device GUID. I tried to do the "replace key" and i'm not getting anything in my email. Edit: i still have my old flash drive, should i just throw it back in, or have i already passed the point of no return?

If i want to just re-create the flash drive from the backup, is there a procedure to do or do i just unzip and copy?

Is it safe to make a backup now since that error showed up? edit: i had made a backup when i initially saw the error and just did one now, both completed successfully

The server is on a ups and haven't had any power outages. I haven't shut down/restarted the server in about a month. I'm really scared (admittedly) to shut down the server and not be able to get it back up.

So i got a critical error about my usb drive not being read-write. It popped up a few days ago, and i had been busy and not able to troubleshoot it till now. The server has been working fine since the error came up (plex/arr's....) but now that i'm looking at the server, i'm seeing that my Apps tab to get to CA isn't there and i cant update some plugins (CA, Unsassigned Devices, and CA Backup/Restore Appdata), but i was able to updated dockers just fine. The error hasn't come back since i first saw it, is it possible that it was a false alarm, is there any way to check it? If not, I'm guessing i should re-create my flash drive? Its been a while since i built the server and haven't messed with the flash drive at all. I can create a flash drive backup right now, but is that safe to do? I'm not sure if its a problem with the physical flash drive, or some sort of software error.

i guess i dont really have all the knowledge of how unriad and the parity works (i guess that's what i'm here for) my old thinking is that, the drive im replacing only has 1tb of data on it, it would only write 1tb of data to the new drive. Sound like i've got some learning to do. 🙂

Bummer! Ohh well, another 28hrs of rebuild

Well the parity check after both parity drives were swapped is done and completed with 0 errors. Looks like its time to start to swap drives. will the data drive rebuilds take just as long as the parity drives? The drives im replacing only have 1.25tb's on them.

Thanks for explaining this. I unchecked it and started a check, I also just checked under my scheduler settings and it was set to write corrections by default, i went ahead and set it to No now. i went back and looked at my parity check history and it shows 0 errors going back as far as April of 2020 (thats as far as it shows and i have it set to check the 1st of the month)

Second parity rebuild is done. I've never forced a manual parity check outside of the normal monthly automatic parity check and haven't noticed the little "write corrections to parity" What does it do? Keep it checked?

Dang, this is a long process! Ha. When i do the rebuild of the data drives, since its only writing around 1.25tb to each drive, that should go quicker? or will it take as long as the parity rebuild?

Sounds good. Is the parity check going to take the same amount of time as the rebuild?

About 2.5hrs left to go and then i'll be doing a parity check before starting to swap drives. Anything on the parity check that i should look for, or just see if it say "completed with zero errors"?

well its back up to over 200mb/s. Really interesting how on the first parity rebuild, it want fast to slow.....on the second it went slow to fast.

Sweet graph. is that a plugin?

Ok, thats good to know. Its going slower and slower as time goes. Hopefully it will speed up in after it passes that 3tb

is it normal for the second parity drive rebuild to go slower than the first?