December 27, 20223 yr Community Expert Likely the new parity had an existing partition starting on sector 2048, default is 64, but Unraid will accept and use 2048 if it exists, if that was the problem, and the fdisk output would confirm, you just needed to delete the partition first.
December 27, 20223 yr Author yep, the parity check completed without issue. I think I can safely close the thread. sorry to bother everyone with this odd issue. for reference though I was able to get the fdisk output for the new parity disk/the SSD with the weird default formatting I dont know how helpful it is since I can't get unraid to mount the old parity drive anymore and I dont have the fdisk from before I just straight up copied all of the data from the old to the new, but here it is reguardless root@Kamina:~# fdisk -l /dev/sdb Disk /dev/sdb: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: CT1000BX500SSD1 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x6d4a4ae2 Device Boot Start End Sectors Size Id Type /dev/sdb1 64 1953525167 1953525104 931.5G 83 Linux Edited December 28, 20223 yr by SugoiShades
December 28, 20223 yr Community Expert 1 hour ago, SugoiShades said: can't get unraid to mount the old parity drive Parity drives have no filesystem to mount. Maybe you mean something else.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.