January 1, 20251 yr Hello, Hoping I've not done too much to ruin things here. I had an unassigned drive that I thought I would add to my cache pool, thinking I could keep it and the existing separate. Having stopped the array, added the drive to the cache pool, restarted the array (so far so good), stopped the balancer and run the option to change to single mode, I then decided I didn't want to add this second drive to the cache after all. The balancer had finished its tasks. Still all seemed fine. I then stopped the array again, moved this second drive back to unassigned, went to start the array and the status shown in this issue's title now shows, with nothing in appdata seeing as it lives in my cache. I have attached my diagnostics, and am very much hoping that I've not done something fatal. Thanks in advance. rincewind-diagnostics-20250101-1308.zip
January 1, 20251 yr Community Expert You cannot remove a pool member if the profile is set to single, only if it's a redundant pool, post the output from btrfs fi show
January 1, 20251 yr Author # btrfs fi show Label: none uuid: 6576e5a5-69ac-4e75-940e-ac87ffe76bc4 Total devices 1 FS bytes used 360.00KiB devid 1 size 20.00GiB used 536.00MiB path /dev/loop2 Label: none uuid: 91612829-f0d4-4cbc-88d5-4186d01e40a2 Total devices 2 FS bytes used 63.68GiB devid 1 size 117.38GiB used 79.05GiB path /dev/sde1 *** Some devices missing Thank you
January 1, 20251 yr Author fwiw I did try and put the drive in question back, however then they both showed up as Unmountable: Unsupported or no file system
January 1, 20251 yr Author 7 minutes ago, JorgeB said: Is the NVMe the other device that was part of the pool? yes
January 1, 20251 yr Author I guess it's worth asking at what point I should consider just restoring a backup too, and whether that might be a good time to move the smaller of the 2 drives we're talking about to unassigned and the larger to the cache. Clearly it would be better if I can resurrect this, but I'm happy to be pragmatic about it.
January 2, 20251 yr Community Expert Type: sfdisk /dev/nvme0n1 then type 2048 and hit enter and post the results
January 2, 20251 yr Author # sfdisk /dev/nvme0n1 Welcome to sfdisk (util-linux 2.38.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK Disk /dev/nvme0n1: 465.76 GiB, 500107862016 bytes, 976773168 sectors Disk model: CT500P3SSD8 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes sfdisk is going to create a new 'dos' disk label. Use 'label: <name>' before you define a first partition to override the default. Type 'help' to get more information. >>> 2048 Created a new DOS disklabel with disk identifier 0xa2bbd386. Created a new partition 1 of type 'Linux' and of size 465.8 GiB. Partition #1 contains a btrfs signature. Do you want to remove the signature? [Y]es/[N]o:
January 2, 20251 yr Community Expert Type N and hit Enter to keep the signature, then type write and Enter again, then post the output from btrfs fi show
January 2, 20251 yr Author # btrfs fi show Label: none uuid: 6576e5a5-69ac-4e75-940e-ac87ffe76bc4 Total devices 1 FS bytes used 360.00KiB devid 1 size 20.00GiB used 536.00MiB path /dev/loop2 Label: none uuid: 91612829-f0d4-4cbc-88d5-4186d01e40a2 Total devices 2 FS bytes used 63.68GiB devid 1 size 117.38GiB used 79.05GiB path /dev/sde1 devid 2 size 465.76GiB used 50.00GiB path /dev/nvme0n1p1
January 2, 20251 yr Community Expert Now unassign any assigned pool devices, start array, stop array, assign both pool device to the pool, start array and post new diags.
January 2, 20251 yr Author It currently looks like this: Sorry, I'm not 100% sure what to do with regards "unassign any assigned pool devices". If I unassign will it lose all my data on the cache?
January 2, 20251 yr Author If I'm losing data, I may just add the nvme drive back to the cache and not worry about the smaller one, however if I need both to preserve data, if only at least initially, then I'm happy to do that.
January 2, 20251 yr Community Expert 6 minutes ago, GeeBee said: It currently looks like this: Do what I posted above, it should reimport the pool with all its data.
January 2, 20251 yr Author Ok, have done, thank you. Diagnostics attached. I guess at this point it's probably worth asking how I might go about removing the smaller of the 2 disks from the cache pool, and whether I need to do something with the balancer. I'm guessing that there is a wiki page for the former. rincewind-diagnostics-20250102-1125.zip
January 2, 20251 yr Community Expert Pool mounted and seems OK, to remove a device you first must rebalance to raid1, click on the pool, scroll down to the balance status section, and convert to raid1, after that, you can follow this: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/#findComment-480418
January 2, 20251 yr Author Thank you very much, really appreciate your help. Do you have a kofi link or similar?
January 2, 20251 yr Author 11 minutes ago, JorgeB said: Pool mounted and seems OK, to remove a device you first must rebalance to raid1, click on the pool, scroll down to the balance status section, and convert to raid1, after that, you can follow this: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/#findComment-480418 Just to check, this seems to be for replacing a single drive with another, as opposed to removing one. Am I right in thinking it's essentially the same thing? So in essence it's a case of adding the array as secondary storage and running mover to duplicate the files, then stopping the array, unassigning the disk I no longer want and then changing the mover direction back from array to cache before then removing secondary storage again? Seeing as I've now rebalanced to be on Raid1, am I not able to just unassign? I thought Raid1 was mirrored. Thanks again.
January 2, 20251 yr Community Expert That link if for removing a pool device, but basically, and after it's balanced to raid 1, you just need to stop the array, unassign the device you want to remove and start the array:
January 2, 20251 yr Author Hmm, ok. It seems that seeing as the disk I want to keep is in the 2nd slot, I can't quite do what I need to. When I try and just unassign the disk in slot 1, it says something about incorrect number. If I try and unassign the disk in slot 1 and reassign the disk in slot 2 to slot 1, I get an error about mismatch. Any thoughts?
January 2, 20251 yr Community Expert Solution 24 minutes ago, GeeBee said: It seems that seeing as the disk I want to keep is in the 2nd slot, I can't quite do what I need to. Doesn't matter what device you want to keep, but I forgot that since the pool was single profile before, it may not update automatically after the balance, re-import the pool again, and it should correct that: 3 hours ago, JorgeB said: unassign any assigned pool devices, start array, stop array, assign both pool device to the pool, start array and post new diags.
January 2, 20251 yr Author Perfect, thank you. Doing this has allowed me to add them back and then remove the one I don't want in there. Do you have a kofi or similar link you can share?
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.