GreyPorts

I was aware about the write penalty, but I'm in a write once read many situation so I wasn't worried about it. But once I get this figured out looks like I'll be moving the SSDs to their own pool for trim support. Thank you for the info.

Unfortunately, the first two methods are not working. # mount -o rescue=all,ro /dev/md8p1 /temp mount: /temp: can't read superblock on /dev/md8p1. dmesg(1) may have more information after failed mount system call. # btrfs restore -v /dev/md8p1 /mnt/disk11/disk8/ bad tree block 22036480, fsid mismatch, want=af861c02-cf4b-4881-885b-de00568816f6, have=c8202876-5861-4c83-9adc-f0229dcb0934 ERROR: cannot read chunk root Could not open root, trying backup super bad tree block 22036480, fsid mismatch, want=af861c02-cf4b-4881-885b-de00568816f6, have=c8202876-5861-4c83-9adc-f0229dcb0934 ERROR: cannot read chunk root Could not open root, trying backup super bad tree block 22036480, fsid mismatch, want=af861c02-cf4b-4881-885b-de00568816f6, have=c8202876-5861-4c83-9adc-f0229dcb0934 ERROR: cannot read chunk root Could not open root, trying backup super

Ope, it was not stopped, my apologies. Here are all the commands re-run: # fdisk -l /dev/nvme0n1 Disk /dev/nvme0n1: 2.91 TiB, 3200631791616 bytes, 6251233968 sectors Disk model: 7335943:ICDPC5ED2ORA6.4T 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: gpt Disk identifier: 0CB7D80D-4016-4C94-B80E-31F90C675075 Device Start End Sectors Size Type /dev/nvme0n1p1 2048 6251233934 6251231887 2.9T Linux filesystem # fdisk -l /dev/nvme0n1p1 Disk /dev/nvme0n1p1: 2.91 TiB, 3200630726144 bytes, 6251231887 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes # blkid /dev/nvme0n1 /dev/nvme0n1: PTUUID="0cb7d80d-4016-4c94-b80e-31f90c675075" PTTYPE="gpt" # blkid /dev/nvme0n1p1 /dev/nvme0n1p1: UUID="af861c02-cf4b-4881-885b-de00568816f6" UUID_SUB="289aa7a7-fe78-47f8-bbaa-fffe0e08018e" BLOCK_SIZE="4096" TYPE="btrfs" PARTUUID="87b90c73-ce2b-497b-a003-c87b420736a7" # wipefs /dev/nvme0n1 DEVICE OFFSET TYPE UUID LABEL nvme0n1 0x200 gpt nvme0n1 0x2e934855e00 gpt nvme0n1 0x1fe PMBR # wipefs /dev/nvme0n1p1 DEVICE OFFSET TYPE UUID LABEL nvme0n1p1 0x10040 btrfs af861c02-cf4b-4881-885b-de00568816f6 # gdisk -l /dev/nvme0n1 GPT fdisk (gdisk) version 1.0.10 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/nvme0n1: 6251233968 sectors, 2.9 TiB Model: 7335943:ICDPC5ED2ORA6.4T Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): 0CB7D80D-4016-4C94-B80E-31F90C675075 Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 6251233934 Partitions will be aligned on 2048-sector boundaries Total free space is 2014 sectors (1007.0 KiB) Number Start (sector) End (sector) Size Code Name 1 2048 6251233934 2.9 TiB 8300 # btrfs fi show Label: none uuid: f30f243b-8b30-41a6-952e-afaafaa26cc0 Total devices 1 FS bytes used 69.82GiB devid 1 size 465.76GiB used 178.06GiB path /dev/nvme2n1p1 Label: none uuid: bffc9ef3-ee50-418f-bac7-cd6a64b54f12 Total devices 1 FS bytes used 15.39GiB devid 1 size 2.91TiB used 18.02GiB path /dev/nvme3n1p1 Label: none uuid: 8e566c16-4fb3-4758-b658-8966961c62de Total devices 1 FS bytes used 2.70TiB devid 1 size 2.91TiB used 2.74TiB path /dev/nvme1n1p1 Label: none uuid: 334323b3-fc02-4417-912d-5ae3f6f95a94 Total devices 1 FS bytes used 144.00KiB devid 1 size 2.91TiB used 2.02GiB path /dev/nvme4n1p1 Label: none uuid: af861c02-cf4b-4881-885b-de00568816f6 Total devices 1 FS bytes used 144.00KiB devid 1 size 2.91TiB used 2.02GiB path /dev/nvme0n1p1

No, it wasn't encrypted. You also didn't specify a sub-command so if I used the wrong one let me know. gdisk -l /dev/nvme0n1 GPT fdisk (gdisk) version 1.0.10 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/nvme0n1: 6251233968 sectors, 2.9 TiB Model: 7335943:ICDPC5ED2ORA6.4T Sector size (logical/physical): 512/512 bytes Disk identifier (GUID): 0CB7D80D-4016-4C94-B80E-31F90C675075 Partition table holds up to 128 entries Main partition table begins at sector 2 and ends at sector 33 First usable sector is 34, last usable sector is 6251233934 Partitions will be aligned on 2048-sector boundaries Total free space is 2014 sectors (1007.0 KiB) Number Start (sector) End (sector) Size Code Name 1 2048 6251233934 2.9 TiB 8300

It is supposed to be Disk 8 in my main array.

Below is the output, there was a long pause before listing the last device /dev/md8p1 btrfs fi show Label: none uuid: 150ff018-e98f-4c90-a72a-bbcf1d5e34f9 Total devices 1 FS bytes used 1.56TiB devid 1 size 3.64TiB used 2.93TiB path /dev/mapper/md1p1 Label: none uuid: 190e5ea3-f793-4c9b-846c-05550170b52c Total devices 1 FS bytes used 1.93TiB devid 1 size 3.64TiB used 2.03TiB path /dev/mapper/md2p1 Label: none uuid: 7f725a93-85bb-4acc-95d9-f21f8f14fc53 Total devices 1 FS bytes used 2.75TiB devid 1 size 3.64TiB used 3.07TiB path /dev/mapper/md3p1 Label: none uuid: 957a6269-e988-4cb5-935c-34365f4d2d50 Total devices 1 FS bytes used 1.69TiB devid 1 size 3.64TiB used 1.86TiB path /dev/mapper/md4p1 Label: none uuid: 6d056dae-4b96-4056-b78f-a07448134c5b Total devices 1 FS bytes used 1.73TiB devid 1 size 3.64TiB used 1.85TiB path /dev/mapper/md5p1 Label: none uuid: 745a2f17-23b5-4d3e-8f07-6c6355ecc9ee Total devices 1 FS bytes used 1.12TiB devid 1 size 3.64TiB used 1.39TiB path /dev/mapper/md6p1 Label: none uuid: c5209253-5822-4afa-989e-a16028621fa1 Total devices 1 FS bytes used 1.22TiB devid 1 size 3.64TiB used 1.50TiB path /dev/mapper/md7p1 Label: none uuid: 8e566c16-4fb3-4758-b658-8966961c62de Total devices 1 FS bytes used 2.70TiB devid 1 size 2.91TiB used 2.74TiB path /dev/md9p1 Label: none uuid: bffc9ef3-ee50-418f-bac7-cd6a64b54f12 Total devices 1 FS bytes used 15.39GiB devid 1 size 2.91TiB used 18.02GiB path /dev/md10p1 Label: none uuid: 334323b3-fc02-4417-912d-5ae3f6f95a94 Total devices 1 FS bytes used 144.00KiB devid 1 size 2.91TiB used 2.02GiB path /dev/md11p1 Label: none uuid: f30f243b-8b30-41a6-952e-afaafaa26cc0 Total devices 1 FS bytes used 69.82GiB devid 1 size 465.76GiB used 83.06GiB path /dev/nvme2n1p1 Label: none uuid: 674c66eb-9da8-4298-8a5a-03c140b10a99 Total devices 1 FS bytes used 2.62GiB devid 1 size 100.00GiB used 7.02GiB path /dev/loop2 Label: none uuid: 588fe46c-0f80-4c70-bd73-86b2e66c4050 Total devices 1 FS bytes used 744.00KiB devid 1 size 1.00GiB used 126.38MiB path /dev/loop3 Label: none uuid: af861c02-cf4b-4881-885b-de00568816f6 Total devices 1 FS bytes used 144.00KiB devid 1 size 2.91TiB used 2.02GiB path /dev/md8p1

I upgraded my system to 7.0.0 and installed a new set of NVMe drives. They worked fine for a week or two then after a reboot I received the "unmountable: wrong or no file system" error. I have since updated to 7.0.1 . fdisk -l /dev/nvme0n1 Disk /dev/nvme0n1: 2.91 TiB, 3200631791616 bytes, 6251233968 sectors Disk model: 7335943:ICDPC5ED2ORA6.4T 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: gpt Disk identifier: 0CB7D80D-4016-4C94-B80E-31F90C675075 Device Start End Sectors Size Type /dev/nvme0n1p1 2048 6251233934 6251231887 2.9T Linux filesystem -------------------------------------------------------------------- fdisk -l /dev/nvme0n1p1 fdisk: cannot open /dev/nvme0n1p1: No such file or directory -------------------------------------------------------------------- blkid /dev/nvme0n1 /dev/nvme0n1: PTUUID="0cb7d80d-4016-4c94-b80e-31f90c675075" PTTYPE="gpt" -------------------------------------------------------------------- blkid /dev/nvme0n1p1 # Blank output -------------------------------------------------------------------- wipefs /dev/nvme0n1 DEVICE OFFSET TYPE UUID LABEL nvme0n1 0x200 gpt nvme0n1 0x2e934855e00 gpt nvme0n1 0x1fe PMBR -------------------------------------------------------------------- wipefs /dev/nvme0n1p1 wipefs: error: /dev/nvme0n1p1: probing initialization failed: No such file or directory unraid1-diagnostics-20250330-1834.zip