eliptical

Thank you, parity build is underway!

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.

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

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

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

Thank you. I was able to get started again with a new install, but I don't see a vconfig folder to copy over. I was only able to manually copy the data from the bad flash drive. Is it possible to get the old configuration restored that way? The bigger issue now appears to be replacing the key. The docs show Replace Key as an option, but the registration options in the WebGUI I see are start free trial, purchase key, redeem activation code, and recover key. Recover key looks like the closest option, but that says it's for the existing GUID. Do I need to open a support ticket because of the new GUID?

I had been working on my system this morning, and had a unclean shutdown, but it was working normally afterwards. Hours later I found an error saying the key was invalid or missing. I think it said this can be caused by corruption. I copied the key to the drive from my PC and I ran a disk check from Windows, which it came back error free. Putting the drive back in gave the same key error. I tried to backup the flash, but gave me a 404 error instead of downloading. This isn't exactly a big shock since the drive wasn't brand new, and was made by Inland. It's a miracle it lasted this long. I was able to copy the data off it manually, but the USB utility wasn't able make the replacement drive bootable using the custom install process. I'm wondering is it safe to run the USB utility to make a fresh install on a new drive, and copy over the configuration files from the old one?