Please bear with me as I'm really new to Unraid and only have limited experience with LInux in general. I don't know if what I'm wanting is even feasible but I figured I'd ask.

 

I set up a new Unraid server using a mini PC attached via USB to a 4-bay enclosure (DAS, no RAID). After a couple of days, the 4th drive failed. Bought a new drive. That one failed too. I started to suspect there was an issue with the 4th slot in the enclosure. Keep in mind, the array was still running with the first 3 drives operational and the 4th drive being emulated. So I ended up buying a different enclosure. My goal is to just swap out all of the drives to the new enclosure without having to wipe/reload everything from backup. The main issue seems to be that while the old enclosure (Mediasonic ProBox) passed through the actual drive info (name, serial #, etc.), the new enclosure makes all the drives appear as JMicron_Generic_DISKXX. When trying to assign drives back to the existing array, Unraid shows "Wrong" next to the disk. Is there a way to manually change the JMicron name back to the original name of the drive? Or is there another workaround? Or am I just going to have to wipe all these drives and reload all my data from backup? 

USB not recommended for array or pools for many reasons. You are experiencing some of those reasons.

1 minute ago, trurl said:

USB not recommended for array or pools for many reasons. You are experiencing some of those reasons.

Yeah... I became aware of that after I had already bought everything for the new setup. But here we are ¯\_(ツ)_/¯

The disk problems were probably disconnects due to USB, nothing really wrong with the disks. One of the reasons USB not recommended.

 

The changed identifications is another reason.

 

Possibly presenting the wrong capacity for a disk is another, which can mean it thinks your parity disk is too small, or something wrong with partitions when you try to migrate to another enclosure.

 

If you insist on using USB maybe best to forget about parity since disconnects will make the array out-of-sync and require rebuild.

 

Look for USB that support UASP for better results.

Okay, I think I actually figured it out and it was way easier than I expected. I just did a new configuration and made sure I checked the box saying parity was already valid. I did had to rescan my Plex libraries but so far things are looking good.

If it worked then why did plex need to be rescanned. Something must not be working right.

 

Don't be surprised if you continue to experience disconnects.

 

And New Config means you can't rebuild anything except parity, so if there is a data disk problem that won't fix it.

 

26 minutes ago, trurl said:

The disk problems were probably disconnects due to USB, nothing really wrong with the disks.

 

32 minutes ago, Millhouse125 said:

old enclosure (Mediasonic ProBox) passed through the actual drive info

You were probably better off with the Mediasonic.

 

Can you even get SMART reports from that other enclosure?

28 minutes ago, trurl said:

why did plex need to be rescanned

Possibly there were emulated writes to a disabled data disk, and those writes were lost when you didn't rebuild the disk but did New Config instead.

 

If so, that would mean parity isn't completely in sync.

 

You should do a parity check. Probably should have done one after the migration anyway.