JorgeB

Yes.

That won't help, that is part of the enclosure, added to all disks, it might work with a different enclosure, but again, not recommended.

It will only work if you can change this part: Feb 27 11:41:29 Tower emhttpd: WDC_WD80_EZAZ-11TDBA0_152D00539000-0:0 (sdi) 512 15628053168 Which likely isn't possible.

This is the result of using USB enclosures, both identify the disk the same way, so for Unraid that is the same disk and can't be assigned twice.

Only issue I see for now is a single right error on cache2: Feb 26 19:19:36 PaulServer kernel: BTRFS info (device sde1): bdev /dev/sde1 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 You might want to take a look at this. Also, I asked for the diagnostics, not just the syslog:

Please post the diagnostics: Tools -> Diagnostics It might also help if you better describe step by step what you did.

https://forums.unraid.net/topic/57181-docker-faq/?do=findComment&comment=564309

You need to copy the data on that disk elsewhere, using e.g. UD, then you can add the disk to the array and have Unraid re-format it.

I missed this part before, in this case it's normal for Unraid to complain about the partition, since the now 2TB disk has a 1.5TB partition, and Unraid requires a single partition using the entire disk, but like mentioned UD won't mind.

Assuming they are genuine the 9207 would be a better option, cables are the correct ones (forward breakout), can't speak about their quality.

Alternately, and likely a better idea, try to mount the disk outside the array with UD, UD doesn't care about the correct partition layout.

Yep: Feb 19 18:48:59 Unraid kernel: XFS (md1): metadata I/O error in "xlog_bread_noalign" at daddr 0x575e237d len 1 error 5 Feb 19 18:48:59 Unraid kernel: XFS (md1): failed to find log head Feb 19 18:48:59 Unraid kernel: XFS (md1): log mount/recovery failed: error -5 Feb 19 18:48:59 Unraid kernel: XFS (md1): log mount failed But now you're seeing an unsupported partition layout error, this is likely the result of the source disk being USB, that or ddrescue failed to copy the complete mbr because of bad sectors.. Best bet here would be to add a parity disk, let it sync, then disable disk1, Unraid will recreate the partition for the emulated disk, then it might still need xfs_repair, but it also might mount immediately.

IIRC original disk needed xfs_repair, so the clone will also need it.

You need to format the disks, next to array stop/start buttons.

Tools -> New config -> Keep all assignments -> Apply Then assign new disk

I didn't re-read the thread and didn't remember you didn't have parity originally.

If there's no parity you can add the drive to the array, it won't be cleared.

You don't need dockers, you can use midnight commander (mc on the console)

Alternatively you can mount it with UD and copy the data to the array.

Diags are after rebooting, try again and grab new ones if it happens again, if the GUI doesn't respond use the console and type diagnostics, if that also doesn't work enable syslog server and try again.

Sure

If it's not listed on the devices it's not an Unraid problem, if it was listed and no driver loaded then it could be. Try a different computer/board if you can just to make sure the NIC is working.

The diagnostics you posted were not saved during a parity check, and I don't see anything abnormal, except for a constant UPS communication error, grab new ones during a check, from the console if necessary, to see if there's something there.

It would be the easiest way to find out if it's a disk problem or not.

NIC is detected but fails to initialize: Feb 26 21:00:29 Tower kernel: atlantic: FW kickstart failed Feb 26 21:00:29 Tower kernel: atlantic: probe of 0000:09:00.0 failed with error -5 Maybe a firmware issue?