Hi guys, relatively new to Unraid but long time linux user. My server is an intel nuc and only 1 18TB usb drive in the array. I wanted to expand the storage so added another 18TB drive, this time in a mediasonic 4 bay usb enclosure. My thinking was to use unbalance to move the data from the usb drive to the new drive. I do use hardlinks so I did add the H flag to unbalance to preserve hardlinks but drive was close to full so ran out of space. So I added another 18TB drive to the mediasonic enclosure and started unbalance again. unbalance reported it finished the move over night. Next morning the last drive added is showing Device is disabled, contents emulated.

I have reseated the drive with no luck.

Currently the array says "Too many wrong and/or missing disks!"

Attached are diagnostics from right after it happened, before reboot. Second diagnostic is from now.

 

Running unraid Version: 6.12.3

 

I do not have a parity drive. The last 18TB drive was supposed to become the parity drive once data was moved correctly.

 

Thanks in advance.

nassie-diagnostics-20230828-0043.zip nassie-diagnostics-20230828-1140.zip

Edited August 28, 20232 yr by NorseRider
Added unraid version and last line about no parity drive

USB not recommended for array or pools for many reasons. Since you don't have parity yet there is no way the disabled disk can be emulated.

 

New Config will let you get the array going again, but with USB you will likely continue to experience this problem and others.

 

Best to not even try parity with USB since disconnects like this may be frequent, making the array out-of-sync, requiring rebuild, possibly frequently. Without parity, nothing to be out-of-sync (but of course, no possibility of rebuild).

Hi trurl, Thank you for your reply. I was also confused why it would say emulated when I don't have a parity drive.

 

New config should have "Preserve current assignments - ALL"?

 

Long term goal is to build a new proper server and not use USB drives. I will skip parity until i build a real server.

Disk shows as wrong, not as emulated, and it's wrong because the capacity changed by a few bytes, this can happen with USB enclosures, you can do a new config and will be able to start the array but the disk might not mount, if it doesn't don't format and try the UD plugin and/or using the original enclosure it it's now using a different one.

Thank you very much trurl andJorgeB! I did New config with preserve all and the disks turned blue and I was able to start the array and most of the data is restored, but disk 3, the last disk added, is showing "unmountable unsupported or no file system".

Should i 1. remove the disk from the array and do new config with only the 2 good drives, mount the last disk with unassigned devices and see if i can copy the data off the drive or 2. restart the array in maint mode and try xfs_repair? If xfs_repair would it be xfs_repair -v /dev/md3p1

 

 

nassie-diagnostics-20230828-1404.zip

1 minute ago, NorseRider said:

Should i 1. remove the disk from the array and do new config with only the 2 good drives, mount the last disk with unassigned devices and see if i can copy the data off the drive

You can try this but based on the syslog, there's no valid filesystem in that disk, so most likely it won't mount with UD either, are you using a different enclosure with that disk? USB enclosures are not always transparent, they can change the partition size, some WD enclosures also encrypt the data, making the disk unreadable on a different enclosure or directly connected to a SATA controller.

The disk3 that is missing now was previously in this enclosure. I put back in the enclosure when I ran out of space and restarted unbalance and about 5TB was written to it. I am going to try and re seat it and see if it comes back. I will update this post as I go. Thank you guys for all the help so far.