JorgeB

Mar 3 05:00:40 Tower kernel: XFS (md1): Unmount and run xfs_repair Check filesystem on disk1.

Mount the old disk with UD then use your favorite tool, you can use krusader, midnight commander (mc on the console), windows explorer, etc.

That's the low end for a single stream, multiple streams from the same disk can get slower due to random access, you'd need to test to see how many streams it can handle. Yes, usually around 115MB/s usable.

It's Unraid.

If you want to change the filesystem you need to move the data elsewhere, then change filesystem by formatting, then restore the data, more info below:

6Gb/s is the interface, normal reads will never get close that that, it should be around 250MB/s max in the outer tracks, slowing down as it starts using the inner tracks, max speed at the most inner tracks should be around 100MB/s.

If don't have enough space on the array on can do this: -do a new config with the larger cloned disk and all the remaining disks -start array to begin parity sync, the cloned disk will be unmountable due to unsupported partition layout -wait for the parity sync to finish -stop array -unassign that disk -start array, emulated disk will now have the correct 10TB partition created and should mount immediatly -stop array -re-assign the disk to rebuild on top, now using the new larger partition.

You can't do this, formatting will delete everything and update parity accordingly, restore the data from the old disk.

Yes, you can add another member later, but first you need to remove the second member from the pool by doing the steps outlined above.

Acknowledge current SMART attributes and keep monitoring, it's showing some issues but nothing fatal for now.

No. What do you mean parity? There's no parity with pools, pool is in raid1 (mirror) so the remaining device will have all the data.

Looks like a connection problem, check/replace cables/slot on party and try again.

You can't do this, and it shouldn't be allowed, it is because of a bug , by doing this the removed device won't be deleted from the pool, so when you assign it to a different pool both will show the same content, to correctly remove the device do this: -stop array -if docker/VM services are using the pool temporarily disable them -unassign all pool devices -start array -stop array -assign all pool devices to the same pool (there can't be a data on this device will be deleted in front of any pool member) -start array (you can re-enable docker/VM services now) -stop array -unassign the pool member you want to removed -start array -once the balance and device delete finishes you can stop the array to re-assign the removed device to a new pool

HBA is failing to initialize: Mar 2 18:25:15 kellyridge kernel: mpt2sas_cm0: port enable: FAILED with timeout (timeout=300s) You should upgrade the firmware since it's very old, can also try a different PCIe slot if available.

Disk4 is OK, it's smaller than the other ones so it slows down sooner, disk3 needs to be replaced.

Unraid won't accept that since it requires the partition to use the full device capacity, but you can always copy data from the clone to other drives after mounting it with for example UD pluign.

Yes, get the non F model, as for the board it should work fine, just not sure about the NIC, should be fine with v6.10-rc, might not be with v6.9.x, and it's still a Realtek NIC, Intel would be better, also consider getting the non WIFI model since you won't be using that, unless you want to use it with a VM.

The problem is not free space, it's free unallocated space. Possibly, I don't use it but remember reading it uses a lot of small files.

This and it's possible to list the corrupt files, unlike with the other option, unless there are pre-existing checksums.

Cache filesystem is fully allocated so you need to re-balance to free up some unallocated space for new metadata chunks to be created, more info below: https://forums.unraid.net/topic/62230-out-of-space-errors-on-cache-drive/?do=findComment&comment=610551 On a side note there's a very high metadata usage compared to data, not that this is necessarily bad, just unusual, do you have a lot small of files up to 2KB?

You can add parity first, but there will be read errors from disk2 during the sync, so Unraid won't be able to then correctly rebuild it.

Without parity Unraid does a read check, the errors are no sync errors, but read errors, from disk2 which is failing, since there's no parity best way to try and recover as much data as possible is to use ddrescue, then you can sync parity with the cloned disk.

The bad RAM corrupted the filesystem, best way forward is to backup the pool, reformat then restore the data.

That's a SMART warning, might or note be serious, need the SMART report. That's from the UD plugin, you can remove them from there, or toggle the historical devices button to not show then.

Since the emulated disk is mounting the partition was successfully recreated, now: -stop the array -re-assign disk4 -start array to begin rebuild Once that's done you need to repeat the process for all the other data disks, one at a time or two at a time since you have dual parity, also recommend replacing those controllers with recommended LSI HBAs ASAP.