November 22, 20241 yr I added a new 10tb drive to the pool. something went wrong and now the 8th existing drive wont load. pics attached. unsure what to try
November 22, 20241 yr Community Expert If the disk is new, did you format it first? It doesn't appear to have a valid filesystem. Post the output from blkid
November 23, 20241 yr Author root@Data:~# blkid /dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="272C-EBE2" BLOCK_SIZE="512" TYPE="vfat" /dev/loop1: TYPE="squashfs" /dev/sdf1: UUID="75b92662-26cb-4550-bf13-5bdf9e89c21e" BLOCK_SIZE="4096" TYPE="xfs" PARTUUID="77f563c7-a884-4285-85cf-f256aaf88418" /dev/nvme0n1p1: UUID="820a3414-6ab9-42e0-ae94-792e4cc8fc5f" UUID_SUB="defbd4b1-130a-4e65-ba1d-54a18bda8a52" BLOCK_SIZE="4096" TYPE="btrfs" /dev/sdd1: UUID="3f75e282-f55e-4961-ac7a-4dcf3886473c" BLOCK_SIZE="4096" TYPE="xfs" PARTUUID="b1c6eded-137d-47b0-9176-05a35f77ea3d" /dev/sdb1: UUID="85accf12-355d-454c-bc03-7de44b69b98f" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="9049746d-014d-4132-a585-2a85e225dfca" /dev/loop0: TYPE="squashfs" /dev/sdc1: UUID="cf600bf2-e6c8-497d-af6a-6bf4ed663cad" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="06b4c72b-4f4f-4507-b904-5c4c66ad2159" /dev/md2p1: UUID="cf600bf2-e6c8-497d-af6a-6bf4ed663cad" BLOCK_SIZE="512" TYPE="xfs" /dev/md1p1: UUID="3f75e282-f55e-4961-ac7a-4dcf3886473c" BLOCK_SIZE="4096" TYPE="xfs" /dev/md3p1: UUID="75b92662-26cb-4550-bf13-5bdf9e89c21e" BLOCK_SIZE="4096" TYPE="xfs" /dev/loop2: UUID="741d8845-5e33-4e63-8b19-7944d7528378" UUID_SUB="d35154c1-0782-4e70-99ad-6fdfcc4be628" BLOCK_SIZE="4096" TYPE="btrfs" /dev/sde1: PARTUUID="283e7bfe-ad2d-4d5f-a73d-83fe3059df2c"
November 23, 20241 yr Community Expert That disk doesn't have a valid filesystem reported, post the output from: fdisk -l /dev/sde
November 23, 20241 yr Author root@Data:~# fdisk -l /dev/sde Disk /dev/sde: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors Disk model: WDC WD80EFZX-68U Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 3D16043F-20E0-45D7-8727-22280BB9B85C Device Start End Sectors Size Type /dev/sde1 64 15628053134 15628053071 7.3T Linux filesystem
November 23, 20241 yr Author root@Data:~# xfs_repair -n /dev/sde1 Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... ......................................................................................................................................................................................................................................................................................................................................................... I'll let you know when it finishes
November 23, 20241 yr Community Expert You can hit CTRL + C to abort, that confirms there's no valid xfs filesystem in that disk, when you say this disk was working in a pool before, do you mean a pool outside the array? If yes, do you remember the filesystem? Just in case it's from a damaged btrfs pool try also: btrfs check /dev/sde1
November 23, 20241 yr Author it was a pool inside the array. it was running xfs, like the other drives.
November 24, 20241 yr Community Expert We call those array drives, not pools, but if that was the case, it means the filesystem got damaged somehow, since parity wasn't valid, there aren't many options, you can restore the data from a backup, or if that is not available, try a file recovery app like UFS explorer.
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.