Hi,

I recently upgraded to unraid 6.3.2 and had 4x 2TB drives (1 parity and 3x data drives).

I also recently purchased a new larger 6TB drive (3/2/2017) and assigned it as the new parity drive and then reclaimed the previous 2TB parity drive as a data disk. I did a pre-clear on the existing 2TB parity drive, formatted and assigned as a data drive. All went well and I've been saving data to this new drive that's been added to the array.

 

Today, I stopped the array to reboot the server and I noticed in the web gui that it's detecting this data drive as new with a message "ALL DATA ON THIS DISK WILL BE ERASED WHEN ARRAY IS STARTED" (see attached screen shot).

 

I don't know why UnRaid is detecting this as a new drive and I'm nervous to start the array as I don't want all the data on this disk to get cleared out.

 

Any ideas what's happening here?

 

Thanks in advance for any assistance.

- Mike

 

 

 

Sometimes the USB drive is corrupted and becomes read-only. It prevents important configuration files from being written back the the USB. That may have happened and the array never fully recognized the fact that disk4 was in the array.

 

I would shutdown and remove the USB and put into a workstation and run chkdsk and let it repair any corruption. (refer to wiki for exact instsructions)

 

Edit the file called disk.cfg in the config directory using an editor that handles Linux formatted text files, like Notepad2. Look for a line that says 

 

startArray="yes"

 

and change it to

 

startArray="no"

 

Then put USB stick back into the server and boot. Suggest running in safe mode. Do a new config, reassign all drives to their slots, and trust parity. Start the array. See if the G4S drive is mounted and disk4 has the content you expect. 

 

Do not do any writes to the array yet. Start a non-correcting parity check.

 

After 3 minutes check for sync errors: 

 

- If disk4 was not mounted or was missing files, and you are getting thousands and thousands of sync errors. Stop the check, stop the array, run diagostics and report back with diagnostics file

- If disk4 looked good, and you have zero sync errors, everything is probably good. Boot into regular mode, You might still want to run a correcting check and let it verify all is good, and correct anything.

- If disk4 looked good, and you have some but not many sync errors, you'll need to run a correcting check. Up to you whether to boot into regular mode or stay in safe mode for the correcting check.

- If anything else happens - take a diagnostics file and post it.

 

Hopefully you'll have the second outcome and all will be well.

 

 

Hi @bjp999,

 

Thanks so much for the detailed response. I indeed had the second outcome. I've now rebooted into regular mode and I'm running a correcting parity check now.

 

Massive thanks for the quick response and assistance. All is well with the world again...

 

Thanks again.

 

 

1 hour ago, WatchoutMac said:

Hi @bjp999,

 

Thanks so much for the detailed response. I indeed had the second outcome. I've now rebooted into regular mode and I'm running a correcting parity check now.

 

Massive thanks for the quick response and assistance. All is well with the world again...

 

Thanks again.

 

 

 

Excellent. Glad to help!

 

Enjoy your array!