Trying to change a Stripe pool to Mirror pool with a "smaller" drive

How do I untangle this? My new drive (should have also been 1TB haha) is just a little smaller then the old one. I want a mirror with these two drives. how do i change the smaller one to the main one now as it wont let me replace it with the new one as its “too small”.
Does someone have an idea?
Thanks in advance :slight_smile:
https prnt.sc/_U-I8aKt9Hax
https prnt.sc/5CPJpPZ-FjaO

You cannot somehow make a drive bigger.

Create the mirror with the smaller drive, then move any data you have to it, then destroy the old pool and attach the bigger drive to the new mirror.

the problem is that this is the pool containing parts of the system dataset. cant i just

  1. add to stripe
  2. make sure data from sdb is moved to sdd
  3. remove sdb
  4. readd sdb to create mirror
    would that work somehow?

You can move the system dataset to whichever pool you want from the WebUI.

You have to:

  1. Create a new pool with “sdd”;
  2. Move the data;
  3. Destroy the old “sdb pool”;
  4. Add sdb to the new “sdd pool” that holds the data.

Do note that “sdb” and “sdd” are NOT permanent names and may change at any time, in order to identify the drives use the serial number or, in this case, the total size.

1 Like

If you do want to do it “without interrupting service”, you can indeed add the new drive as new vdev, remove the old vdev (from GUI) and then use it to extend the new, smaller drive. You’re at risk for a longer period, but as you’re running a single drive pool I guess that’s not much of a concern to you.

5 Likes

Awesome, thats exactly what I wanted! And it will automatically move all the data to the new drive or how can I make sure?

Yes, when you remove the first drive in the gui it will evacuate to the second drive.

(This takes time)

2 Likes

This was a secondary benefit of buffering with a default 2 GiB “swap partition” during pool creation and vdev addition.

Even without using swap, it can prevent these situations.

I’m assuming you created this pool on a recent version of SCALE?

idk what you are talking about with the swap but here is the background story on this system… this is a old optiplex micro mashine bought used on ebay. i5.9500T 32GB RAM in 2023. this pool was probably created the end of 2023 (whatever SCALE version was newest back then) eversince the system was continuously updated and the pool upgraded with its newest features… just because of lazyness I just now bought the drive to finally do a mirror for this actually very important pool… i did a mirror for the boot pool beginning of 2024 i think… but yeah so everything working fine for quiete some time even with a really suboptimal setup in place :sweat_smile:

Thanks for everyone helping out! It worked perfectly with the approach from @etorix thx a lot :slight_smile:
The transfer took about an hour in the end, very easy and without interrupting service! lovely!
https prnt.sc/8qkFyggHcCOB

1 Like