April 21Apr 21 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 chunkPhase 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 = 7No modify flag set, skipping phase 5Phase 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.
April 21Apr 21 Community Expert Are you storing anything important on these drives? If not, doing a wipe with a software such as Disk Wipe and then putting them back in the array might help. If there is important data on them you could make a clone and then wipe the issued disk and then re-install the data
April 21Apr 21 Community Expert Also, Unraid can create a new file system on drives when you first have an array I think, is there a setting in Unraid that can do that?
April 21Apr 21 Author 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.
April 21Apr 21 Community Expert I have done some research, and the issue is in your code, you said 'xfs_repair -n /dev/sdx1'. The -n in this code means no changes, try running that code but remove the -n, so make it 'xfs_repair /dev/sdx1'
April 21Apr 21 Author I was thinking of doing that, but wanted to have an opinion from the forum before I go too far. let me try that.
April 21Apr 21 Author 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
April 21Apr 21 Community Expert Please post the diagnostics after array start, when they don't mount.
April 21Apr 21 Community Expert The two disks assigned to the array are mounting, which are the problem disks?
April 21Apr 21 Author 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.
April 21Apr 21 Community Expert You can leave them unassigned for now; just post the output fromblkid /dev/sdX1Replace X with the correct identifier
April 21Apr 21 Author Got it, let me look for it and post it after I get back from work later this evening.
April 22Apr 22 Community Expert 59 minutes ago, gmedhi said:blkid /dev/sdX1 with the correct identifier returns nothing.What is the actual command you used? No reason to not post it with the correct identifier.
April 22Apr 22 Author 7 minutes ago, trurl said:What is the actual command you used? No reason to not post it with the correct identifier.blkid /dev/sdd1
April 22Apr 22 Author 1 hour ago, The-Vault Master said:Was that the actually command you used and it didn't post?correct, that's what i typed in terminal and it returned nothing. I also tried lsblk -fand saw blank under FSTYPE for the two drives.
April 22Apr 22 Community Expert That suggests multiple signatures; post the output fromwipefs /dev/sdd1Note that despite the name, this as written won't wipe anything.
April 22Apr 22 Author please see the output:root@LEICA:~# wipefs /dev/sdd1DEVICE OFFSET TYPE UUID LABELsdd1 0x0 xfs 4a62aa76-7d21-4bc8-992e-b8c785935f42 sdd1 0xe8d7ff44000 zfs_member 10144205037935999564 disk4sdd1 0xe8d7ff84000 zfs_member 10144205037935999564 disk4
April 22Apr 22 Author 9 minutes ago, gmedhi said:please see the output:root@LEICA:~# wipefs /dev/sdd1DEVICE OFFSET TYPE UUID LABELsdd1 0x0 xfs 4a62aa76-7d21-4bc8-992e-b8c785935f42sdd1 0xe8d7ff44000 zfs_member 10144205037935999564 disk4sdd1 0xe8d7ff84000 zfs_member 10144205037935999564 disk4to 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.
April 22Apr 22 Community Expert Solution That is what is causing the issue, but if the XFS is the current filesystem, you can remove only the zfs signature:wipefs -a -t zfs_member /dev/sdd1
April 23Apr 23 Author 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/sdd1Currently parity is running, hope everything will be fine.Thank you again.
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.