May 8, 20251 yr Community Expert Something went really wrong tonight after I ran new config, and two of my xfs disks are now showing unsupported or no filesystem. All disks were showing auto filesystem, I started the array and only two of my disks came back as xfs mounted, of course a parity sync started which means my parity data is no longer valid... I did not format or do anything with else with these disks. I was trying to simply take one of my empty disks (former disk5), and slot it in for parity2. root@Tower:~# blkid /dev/sdb1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="12F3-2F19" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="f7850c60-01" /dev/sdc1: LABEL="zfs" UUID="2102369910678992796" UUID_SUB="10755710579023684102" BLOCK_SIZE="4096" TYPE="zfs_member" /dev/loop1: BLOCK_SIZE="131072" TYPE="squashfs" /dev/sdm1: LABEL="cache" UUID="1551826738277468454" UUID_SUB="7613256705955010305" BLOCK_SIZE="4096" TYPE="zfs_member" /dev/sdk1: LABEL="cache" UUID="1551826738277468454" UUID_SUB="1717029409727760252" BLOCK_SIZE="4096" TYPE="zfs_member" /dev/md4p1: UUID="a6a5c82d-35fb-4d4b-ad33-77d63b7ef916" BLOCK_SIZE="512" TYPE="xfs" /dev/loop0: BLOCK_SIZE="131072" TYPE="squashfs" /dev/sdn3: BLOCK_SIZE="512" UUID="4CC07D0EC07D000E" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="71143671-a7a5-4c75-82bf-e392dc7fa9f6" /dev/sdn1: LABEL_FATBOOT="NTFS" LABEL="NTFS" UUID="C878-46AD" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="Basic data partition" PARTUUID="2ae20b36-b82e-4338-9332-03c53a9f7664" /dev/sdn4: BLOCK_SIZE="512" UUID="AC3A06833A064AB2" TYPE="ntfs" PARTUUID="d3845781-9f8d-4620-82ad-71e81f0a8c1c" /dev/sdn2: PARTLABEL="Microsoft reserved partition" PARTUUID="6f35769b-0dfe-4bd2-8991-c1e73f6088e2" /dev/sdl1: LABEL="cache" UUID="1551826738277468454" UUID_SUB="15743817999972033493" BLOCK_SIZE="4096" TYPE="zfs_member" /dev/sdj1: LABEL="cache" UUID="1551826738277468454" UUID_SUB="16464870163669679467" BLOCK_SIZE="4096" TYPE="zfs_member" /dev/md3p1: UUID="1add063d-71eb-4b1a-8336-4b5543a146f9" BLOCK_SIZE="512" TYPE="xfs" root@PlexRAID:~# xfs_repair -nv /dev/sdd1 Phase 1 - find and verify superblock... - block cache size set to 1445120 entries Phase 2 - using internal log - zero log... zero_log: head block 2361908 tail block 2361908 - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 8 - agno = 1 - agno = 3 - agno = 6 - agno = 4 - agno = 5 - agno = 7 - agno = 10 - agno = 9 - agno = 2 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. root@PlexRAID:~# xfs_repair -nv /dev/sde1 Phase 1 - find and verify superblock... - block cache size set to 1445120 entries Phase 2 - using internal log - zero log... zero_log: head block 567083 tail block 567083 - scan filesystem freespace and inode maps... - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 1 - agno = 3 - agno = 8 - agno = 5 - agno = 6 - agno = 0 - agno = 4 - agno = 9 - agno = 10 - agno = 2 - agno = 7 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. Both of these appear to return 0 when using "echo $?" plexraid-diagnostics-20250508-0000.zip Edited May 8, 20251 yr by MowMdown
May 8, 20251 yr Community Expert Post output from wipefs /dev/sde1 wipefs /dev/sdd1 Note that despite the name, this won't wipe out anything as written.
May 8, 20251 yr Author Community Expert 3 hours ago, JorgeB said: Post output from wipefs /dev/sde1 wipefs /dev/sdd1 Note that despite the name, this won't wipe out anything as written. root@PlexRAID:~# wipefs /dev/sdd1 DEVICE OFFSET TYPE UUID LABEL sdd1 0x0 xfs 0da6224a-a8f2-468a-a965-29926b90b524 sdd1 0xae9fff44000 zfs_member 16481084777083266639 disk2 sdd1 0xae9fff84000 zfs_member 16481084777083266639 disk2 root@PlexRAID:~# wipefs /dev/sde1 DEVICE OFFSET TYPE UUID LABEL sde1 0x0 xfs 3dd155dd-ea99-43f5-8d0b-7883b96afaae sde1 0xae9fff44000 zfs_member 8582965978458800897 disk1 sde1 0xae9fff84000 zfs_member 8582965978458800897 disk1 Here's some more info if helpful. root@PlexRAID:~# wipefs /dev/sdd* DEVICE OFFSET TYPE UUID LABEL sdd 0x200 gpt sdd 0xae9fffffe00 gpt sdd 0x1fe PMBR sdd1 0x0 xfs 0da6224a-a8f2-468a-a965-29926b90b524 sdd1 0xae9fff44000 zfs_member 16481084777083266639 disk2 sdd1 0xae9fff84000 zfs_member 16481084777083266639 disk2 root@PlexRAID:~# wipefs /dev/sde* DEVICE OFFSET TYPE UUID LABEL sde 0x200 gpt sde 0xae9fffffe00 gpt sde 0x1fe PMBR sde1 0x0 xfs 3dd155dd-ea99-43f5-8d0b-7883b96afaae sde1 0xae9fff44000 zfs_member 8582965978458800897 disk1 sde1 0xae9fff84000 zfs_member 8582965978458800897 disk1 Edit: I also cannot mount them with unassigned devices. The mount button stays greyed out. Edited May 8, 20251 yr by MowMdown
May 8, 20251 yr Community Expert Solution There's an old zfs signature on both, assuming xfs is the current one, so "auto" won't work, you can manually set the filesystem to xfs for those disks, or delete the extra signatures, this should be perfectly safe, and I have never seen it cause issues before, but can't guarantee 100%: wipefs -a -t zfs_member /dev/sde1 wipefs -a -t zfs_member /dev/sdd1
May 8, 20251 yr Author Community Expert I thought about setting the FS to XFS but I didn't want to do anything destructive without checking in here first. Setting fs to xfs allowed the disks to mount prooperly, i will still attempt to wipe the zfs signatures to avoid this. Come to think of it, back when zfs was introduced into unraid, I did format them in zfs to try it in the array as a "hybrid" solution before reverting back to xfs. I wonder if this has something to do with how unraid changed the way it looks for a partition. Either way it's much appreciated. (check your paypal)
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.