Extend storage HDD (Free)

StarWind VTL, VTL Free, VTL Appliance

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

Post Reply
adminr
Posts: 13
Joined: Tue Jan 14, 2025 12:11 pm

Mon Feb 03, 2025 8:48 am

Hello ,

How to stop syncing between nodes with PowerShell to increase storage capacity. To extend volume isn`t problem, but
in case extending virtual HDD there is a little be challenge. You can get vSphere error "200 Failed: synchronizer has invalid state" if syncing won`t stopped.

What is an algorithm to extend virtual HDD ? For example I have storage RAID-5 in the begging I provide HDD with 100 GB for StarWind VMs.
Now I want to increase it to 500GB and StarWind shouldn't broke previously create image and able to use all new capacity.
yaroslav (staff)
Staff
Posts: 3242
Joined: Mon Nov 18, 2019 11:11 am

Mon Feb 03, 2025 9:20 am

Hi,

you do not need to stop synchronization to expand the underlying storage.
shutdown the CVM
resize the physical/virtual disk on hypervisor server
boot the CVM
run commands:
$ sudo lsblk # to determinate volume name, path, vgname, lvname
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sr0 11:0 1 1024M 0 rom
vda 252:0 0 30G 0 disk
├─vda1 252:1 0 1M 0 part
├─vda2 252:2 0 244M 0 part /boot/efi
├─vda3 252:3 0 488M 0 part /boot
└─vda4 252:4 0 29.3G 0 part
└─main-root 253:3 0 29.3G 0 lvm /
vdb 252:16 0 20G 0 disk
└─vdb1 252:17 0 20G 0 part
└─vgvdb1-volume1 253:0 0 19G 0 lvm /mnt/vdb1/volume1
vdc 252:32 0 27G 0 disk
└─vdc1 252:33 0 27G 0 part
└─vgvdc1-volume2 253:1 0 10G 0 lvm /mnt/vdc1/volume2
vdd 252:48 0 15G 0 disk
└─vdd1 252:49 0 10G 0 part
└─md0 9:0 0 10G 0 raid0
└─vgmd0-volume3 253:2 0 4G 0 lvm /mnt/md0/volume3
$ sudo systemctl stop starwind-virtual-san
$ sudo umount /mnt/md0/volume3 # sudo umount /mnt/<path to volume>
$ sudo vgchange -an vgmd0 # sudo vgchange -an <volume group name>
$ sudo growpart /dev/vdd 1 # sudo growpart /dev/<disk without partition> <partition>
$ sudo /opt/starwind/starwind-san-and-nas-console/Scripts/hardware/hardware.py PvResize --device /dev/vdc1
$ sudo python /opt/starwind/starwind-san-and-nas-console/Scripts/hardware/hardware.py UpdateInitramfs
$ sudo vgchange -ay vgmd0
$ sudo mount -a
$ sudo systemctl start starwind-virtual-san
Then you should be able to create new volumes or extend existing ones from the web console.
You should be able to expand the storage after that (make sure the HA devices are synchronized before growing them).
adminr
Posts: 13
Joined: Tue Jan 14, 2025 12:11 pm

Mon Feb 03, 2025 3:20 pm

Code: Select all

$ sudo /opt/starwind/starwind-san-and-nas-console/Scripts/hardware/hardware.py PvResize --device /dev/vdc1
the device is actually vdd1 , is it correct ? Is that a typo, right ? --device /dev/vdd1

the instruction helps me to extend a partition but unfortunately I get a broken LUN. What did I miss?
Attachments
sync2.png
sync2.png (8.13 KiB) Viewed 14374 times
yaroslav (staff)
Staff
Posts: 3242
Joined: Mon Nov 18, 2019 11:11 am

Mon Feb 03, 2025 4:24 pm

It was a sample command, you are welcome to modify those commands accordingly.
The screenshot below shows that there is something wrong with the imagefile there. Please make sure that the devices are available at the path specified in the management console and that there are corresponding files under /opt/starwind/starwind-virtual-san/drive-c/starwind/headers.
adminr
Posts: 13
Joined: Tue Jan 14, 2025 12:11 pm

Tue Feb 04, 2025 6:48 am

I tried it twice. always the same result.

1 . Creating two HA LUN 2Gb for each server with Create HA_2.ps1. Everything looks and works fine.
2. Stop one server. Extended storage.
3. do your instruction
4. Power on the server
5. I do the same thing for second
6. And I get result from my last screen shot.

All image files on the place in dedicated folders.
yaroslav (staff)
Staff
Posts: 3242
Joined: Mon Nov 18, 2019 11:11 am

Tue Feb 04, 2025 6:59 am

This is very weird: this guide has helped many users to grow their underlying storage.
There must be something wrong with your system. Log a call with us https://www.starwindsoftware.com/support-form use 1276802 as your case reference.
Post Reply