I have 2 8TB WD Purple drives that I'd like to add to my array of 2 drives, each 8TB. I want one in data and the other in parity. I'm unable to mount them, an error says check syslog. These entries are from after trying.

Jan 26 08:39:45 NAS unassigned.devices: Mounting partition 'sdd1' at mountpoint '/mnt/disks//mnt/edvr/5'...

Jan 26 08:39:45 NAS unassigned.devices: Mount cmd: /sbin/mount -t 'ext4' -o rw,relatime,nodev,nosuid '/dev/sdd1' '/mnt/disks//mnt/edvr/5'

Jan 26 08:39:46 NAS unassigned.devices: Mount of 'sdd1' failed: 'mount: /mnt/disks/mnt/edvr/5: /dev/sdd1 already mounted on /mnt/disks/mnt/edvr/5. dmesg(1) may have more information after failed mount system call.'

Jan 26 08:39:46 NAS unassigned.devices: Partition '/mnt/edvr/5' cannot be mounted.

Jan 26 08:39:51 NAS unassigned.devices: Mounting partition 'sdb1' at mountpoint '/mnt/disks//mnt/edvr/1'...

Jan 26 08:39:51 NAS unassigned.devices: Mount cmd: /sbin/mount -t 'ext4' -o rw,relatime,nodev,nosuid '/dev/sdb1' '/mnt/disks//mnt/edvr/1'

Jan 26 08:39:51 NAS unassigned.devices: Mount of 'sdb1' failed: 'mount: /mnt/disks/mnt/edvr/1: /dev/sdb1 already mounted on /mnt/disks/mnt/edvr/1. dmesg(1) may have more information after failed mount system call.'

Jan 26 08:39:51 NAS unassigned.devices: Partition '/mnt/edvr/1' cannot be mounted.

With the drives in the desired slots the system shows a message next to the array start "Disk in parity slot is not biggest." Switching between in the new drives in the parity 2 slot doesn't solve this.

I ran SMART tests on both, and they completed without errors. They don't show up in preclear, and I don't see anywhere in Unassigned Devices to format them as preclear suggests.

Have I missed something?

edit: I just noticed, if I remove the parity 2 drive the array can start. Does that need to be done before the parity 2 drive can be added or do I still have an issue on my hands?

eliptical-diagnostics-20260126-1221.zip

Edited January 26Jan 26 by eliptical
additional information.

Try updating to 7.2.3 first and retest, previous 7.2.x release have an issue detecting partition changes, if it still fails after that with parity2 installed, post new diags.

Same outcome since the update. I can't mount either disk, but the array will start with one in data 2 and no parity 2.

eliptical-diagnostics-20260126-1558.zip

Diags are still from 7.2.2

1 hour ago, JorgeB said:

Diags are still from 7.2.2

But I think I see the problem: parity2 has an existing 1MiB aligned

type wipefs -a /dev/sdX

Replace X with the correct parity2 identifier, then, and since you are still on 7.2.2, you need to reboot for Unraid to detect the change, then try again.

I ran the command and it returned this result.

type wipefs -a /dev/sdd

wipefs is /sbin/wipefs

bash: type: -a: not found

bash: type: /dev/sdd: not found

I pulled diags after the reboot as well. You were right about the 1MiB aligned, it shows that for both new drives is in parity 2.

eliptical-diagnostics-20260127-0957.zip

The 'type' is meant to be omitted from the command. It is just an indication that you need to type the command in at the console level.

Yeah, sorry about that, highlited the whole line accidentally, corrected it.

2 hours ago, itimpi said:

The 'type' is meant to be omitted from the command. It is just an indication that you need to type the command in at the console level.

Oops, thanks. I'm still cutting my teeth.

I can now start the array with the new parity drive or data drive but not both. Next to the Start button it says "You may not add new disk(s) and also remove existing disk(s)." I'm not removing anything that was already in the array though.

That's normal; do one, then the other.

51 minutes ago, JorgeB said:

That's normal; do one, then the other.

Thank you, parity build is underway!