gmedhi

That's it, thank you so much. I was able to mount it and add it to the array after runningwipefs -a -t zfs_member /dev/sdd1 Currently parity is running, hope everything will be fine. Thank you again.

to give some context, this disk (and the other 8TB one) was formatted as zfs sometimes back (2 years) and then I reformatted it to xfs. But that was long time ago.

please see the output: root@LEICA:~# wipefs /dev/sdd1 DEVICE OFFSET TYPE UUID LABEL sdd1 0x0 xfs 4a62aa76-7d21-4bc8-992e-b8c785935f42 sdd1 0xe8d7ff44000 zfs_member 10144205037935999564 disk4 sdd1 0xe8d7ff84000 zfs_member 10144205037935999564 disk4

correct, that's what i typed in terminal and it returned nothing. I also tried lsblk -f and saw blank under FSTYPE for the two drives.

blkid /dev/sdd1

blkid /dev/sdX1 with the correct identifier returns nothing.

Got it, let me look for it and post it after I get back from work later this evening.

ah ok, I actually didn't assign it in the array. left it unassigned. let me add it in the array and post the report.

thank you, here it is. leica-diagnostics-20260421-0001.zip

it did not mount neither I can see the file system in unassigned device after doing xfs_repair . . However I can mount it manually to /mnt/test and can see the data

I was thinking of doing that, but wanted to have an opinion from the forum before I go too far. let me try that.

nothing important, they are just media collection. however ~ 24TB, I would not like to wipe off, if there is a way to restore. I am not sure of unraid will create a new file system, as I have 2 other drives and its filesystem is intake.

So I have a situation, I wanted to shrink my array by taking out two 4TB drives and followed the Spaceinvader One guide (https://www.youtube.com/watch?v=nV5snitWrBk) I did the new config (leaving pool slot intake) and reassigned the drives (other than the two 4TB), added the parity and started the array. Once array started, I saw 2 of my older drives (16TB and 8TB) showed no file system and unmounted. I stopped the array did another new config and left the 2 drives unassigned. Started the array in maintenance mode and saw the drives showed no file system in unassigned devices . Ran a quick xfs_repair -n /dev/sdx1 and get the following message. Searching through the forum makes me feel there is no issue with the disk. Any thought what is happening or how to put these 2 drives back to array? Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - 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 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 4 - agno = 2 - agno = 11 - agno = 12 - agno = 14 - agno = 1 - agno = 8 - agno = 5 - agno = 9 - agno = 10 - agno = 3 - agno = 6 - agno = 13 - agno = 7 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting.