I upgraded from 6.2.2 to 6.2.4 this morning, after reboot the server wouldn't boot.

Looked in the BIOS and yup flash drive is not being detected.

Plugged the drive into Windoze OS and it doesn't even power on.

I have a second Unraid Key with a separate/other flash drive, however how to I boot this properly or mount drives as not to overwrite current array data?

Also note worthy I do not have a backup of the old Flash drive.

Make a new Unraid USB.  Boot up.  Assign all your drives as data drives.  The one/two that have no file system are your parity drive(s).  So stop array and reassign as such. Need to setup your share and Unraid preferences again, as well as your docker containers, but all your data will be unharmed.  Should be able to work out which is your cache drive and assign as such. 

 

 

 

Safer yet is to use the unassigned devices plugin, with all disks unassigned all but parity should have the mount option and the filesystem shown, the one without it is your parity.

 

Starting all disks as data disks also works but it will cause some parity sync errors, enough that it can cause some filesystem issues (like an unmountable disk) if a disk needs to be rebuilt before they are corrected, but it shouldn't compromise data.

Safer yet is to use the unassigned devices plugin, with all disks unassigned all but parity should have the mount option and the filesystem shown, the one without it is your parity.

 

Starting all disks as data disks also works but it will cause some parity sync errors, enough that it can cause some filesystem issues (like an unmountable disk) if a disk needs to be rebuilt before they are corrected, but it shouldn't compromise data.

 

That's a good idea.  Wouldn't have thought of that.  Suppose you could start the array in maintenance mode?

Yeah, got the idea last time I needed to do that, with the array stopped it should look like the example below.

Safer yet is to use the unassigned devices plugin, with all disks unassigned all but parity should have the mount option and the filesystem shown, the one without it is your parity.

 

Starting all disks as data disks also works but it will cause some parity sync errors, enough that it can cause some filesystem issues (like an unmountable disk) if a disk needs to be rebuilt before they are corrected, but it shouldn't compromise data.

I will give that a try.

Yeah, got the idea last time I needed to do that, with the array stopped it should look like the example below.

Managed to grab these before upgrade..

I was removing a couple old HDDs that were no longer in use.

 

 

Important one is parity, if you're sure it's still the same you can use that, if you assign a data disk as parity you'll lose data.

Biggest pain I found is setting up all the plugins/dockers/weird little "tweaks" I've made over the years.  The data is the easy part.

Safer yet is to use the unassigned devices plugin, with all disks unassigned all but parity should have the mount option and the filesystem shown, the one without it is your parity.

 

Starting all disks as data disks also works but it will cause some parity sync errors, enough that it can cause some filesystem issues (like an unmountable disk) if a disk needs to be rebuilt before they are corrected, but it shouldn't compromise data.

 

This one?

https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices.plg

Yes

Biggest pain I found is setting up all the plugins/dockers/weird little "tweaks" I've made over the years.  The data is the easy part.

Backup your appdata and your flash drive. 

Yes

So when I select the right parity drive, it tells me that all the data will be erased when the array is started.

It's just a warning so people make sure it's not a data drive, make sure you select the "parity is already valid" checkbox before starting the array, your it will start a parity sync.

It's just a warning so people make sure it's not a data drive, make sure you select the "parity is already valid" checkbox before starting the array, your it will start a parity sync.

Let me see if I got this straight

 

I select the proper Parity drive and assign it.

I do the same to the cache drives.

And I mount all the disks via Unassigned Devices plugin, or just mount them in Unraid like I normally would?

Before I start the Array I check off "Parity is Already Valid".

Start array.

 

I'm not sure what role exactly the Unassigned devices plugin plays here, is it just to check what is contained on the drives so I select the right one?

However since I have an up to date list of the array devices, I can just proceed to assign all the drives to the array?

No, you assign all disks, including parity, data and cache, check the box "parity is already valid" and start array.

Biggest pain I found is setting up all the plugins/dockers/weird little "tweaks" I've made over the years.  The data is the easy part.

Backup your appdata and your flash drive. 

 

I would have if you'd been bothered to write a plugin to do it earlier.  I do now use CA to backup everything.  OP might want to look at that......

Biggest pain I found is setting up all the plugins/dockers/weird little "tweaks" I've made over the years.  The data is the easy part.

Backup your appdata and your flash drive. 

 

I would have if you'd been bothered to write a plugin to do it earlier.  I do now use CA to backup everything.  OP might want to look at that......

Want to hear a funny story I was looking at it prior to rebooting the system and I actually had CA backup installed.

I was thinking, should I, or shouldn't I?

 

No, you assign all disks, including parity, data and cache, check the box "parity is already valid" and start array.

Sweet I got all my shares up and running now I have to mount the disk with all my docker containers and docker configurations on them.

Thanks.

Want to hear a funny story I was looking at it prior to rebooting the system and I actually had CA backup installed.

I was thinking, should I, or shouldn't I?

CA Backup would have saved a ton of trouble here.  Due to an edge-case scenario, it renames the super.dat file that stores your drive assignments, so you either just rename it back, or the backup also creates a text file that details the drive assignments as of the backup in plain english.

Biggest pain I found is setting up all the plugins/dockers/weird little "tweaks" I've made over the years.  The data is the easy part.

Backup your appdata and your flash drive. 

 

I would have if you'd been bothered to write a plugin to do it earlier.  I do now use CA to backup everything.  OP might want to look at that......

Want to hear a funny story I was looking at it prior to rebooting the system and I actually had CA backup installed.

I was thinking, should I, or shouldn't I?

 

No, you assign all disks, including parity, data and cache, check the box "parity is already valid" and start array.

Sweet I got all my shares up and running now I have to mount the disk with all my docker containers and docker configurations on them.

Thanks.

 

You should have....