Expanding VDEV, Electricity went off

[TNSC_H]

Hi everyone!

I was adding another HDD to the exisiting VDEV. It was on about 28% and my electricty went off. I’ve switched back on everything, entered true nas interface and HDD was just addeded to the VDEV HDD list. No percentage whatssoever.
What should I do in this case ?I don’t belive the new disk was addedd because I have a Raidz2 VDEV consisted of 4 6TB drives. I’ve added another 6Tb, so it’s now only 10.45 TiB of usable space. While it should be closer to 16+ Tb.

[etorix]

vdev expansion should resume after interruptions.
You may check with sudo zpool status in the shell.

[TNSC_H]

Right, thank you!
So TrueNAs returned the following:

what means that there is no expansion in the background ? or it’s finished?

[etorix]

31.69% done, 09:50:05 to go

But… do I see a pool name with spaces? You’re asking for trouble.

[TNSC_H]

@etorix

31.69% done, 09:50:05 to go

Oh, I see. Thank you !

@etorix

But… do I see a pool name with spaces? You’re asking for trouble.

Yeah, I use “children” data sets names without spaces, but I I’m not sure where to change the main data pool name.

[etorix]

Captain @Stux has you covered… even without a video:

HOWTO: Rename a ZFS pool

The basic process to rename a ZFS pool is to export it from the GUI, import it in the CLI with the new name, then export it again, and re-import it in the GUI. I find I normally want to do this after creating a new pool (with perhaps a different set of disks/layout), replicating my old pool to the new pool, and then I want to rename the new pool to the same as the old pool, and then all the shares work correctly, and its fairly transparent. Mostly. (tested with TrueNAS CORE 12U8-1. Works with …

[TNSC_H]

@HOWTO: Rename a ZFS pool

The basic process to rename a ZFS pool is to export it from the GUI, import it in the CLI with the new name, then export it again, and re-import it in the GUI. I find I normally want to do this after creating a new pool (with perhaps a different set of disks/layout), replicating my old pool to the new pool, and then I want to rename the new pool to the same as the old pool, and then all the shares work correctly, and its fairly transparent. Mostly. (tested with TrueNAS CORE 12U8-1. Works with …

Hmm. Thanks, but sounds pretty complicated, and unreliable.
I wonder why I can’t rename the main data pool by using “Data set details” Edit tab.
I have a “name and options” window there, but I can not enter anything there.
If it’s that critical why I can not change it

[Jorsher]

You have to follow the directions, you can’t just rename from the GUI.

Don’t worry, it’s more reliable than your electricity.

[TNSC_H]

So the double export / import is the only way.
But, your post doesn’t answer my question - if naming the data pool without spaces that critical - why it is possible in the first place, and why there is no option of renaming data pool afterwards?

[Jorsher]

It’s not guaranteed to break anything, it’s just possible that some things won’t play nice. I wouldn’t call it ‘critical,’ just not ‘best practice.’ That’s why it’s allowed. Wait til you see the things the shell will let you flat-out break.

You could make a feature request to rename pools. I don’t think it’s something people do frequently and I’m sure it’s possible to break things by renaming it, too.

[etorix]

Specifically, the middleware should manage, but spaces, or other special characters which require escaping, make CLI operations more difficult and could cause issues with third-party scripts.
Best to take a deep breath now and rename Main Data Pool to Main_Data_Pool or MainDataPool. It can only make your life easier.

[winnielinnie]

Don’t forget to update any references to the old mount paths.

Things like jail mountpoints, data directories for apps, SMB shares, and so on, might still be pointing to /mnt/Main Data Pool/some/directory after you rename the pool.