OSNEXUS Online Documentation Site - User contributions [en]

File:Jammyefiraid1-16.png

2025-10-20T13:43:53Z

Joshua.blake:

QuantaStor 6 - Software RAID1 Install Procedure (EFI Boot BIOS Mode)

2025-10-20T13:43:41Z

Joshua.blake: /* Instructions */

Creating the software RAID1 is as easy as a few extra steps during the installation process.

Below are a few screenshots of the process to create a software RAID1 with QuantaStor 6 and newer using QuantaStor ISO media based on Ubuntu 20.04 (Focal) and 22.04 (Jammy).

=== Instructions ===

* '''Step 1''' - When first prompted, select 'Install OSNEXUS QuantaStor'. If you would like to skip checking the media, select 'Install (skip Media Check)'
[[File:jammyefiraid1-1.png|600px]]

* '''Step 2''' - Configure the networking as desired, and press the Enter key on 'Done'
[[File:jammyefiraid1-2.png|600px]]

* '''Step 3''' - Make sure 'Custom storage layout' is selected, and press the Enter key on 'Done'
[[File:jammyefiraid1-3.png|600px]]

* '''Step 4''' - Go to the first device you wish to use for RAID1, and press the Enter key. Select 'Use As Boot Device' and press the Enter key
[[File:jammyefiraid1-4.png|600px]]

* '''Step 5''' - Repeat the same step for the second device you wish to use for RAID1, and press the Enter key. Select 'Use As Another Boot Device' and press the Enter key
[[File:jammyefiraid1-5.png|600px]]

* '''Step 6''' - Go to the free space on the first device you wish to use for RAID1, and press the Enter key. Select 'Add GPT Partition' and press the Enter key
[[File:jammyefiraid1-6.png|600px]]

* '''Step 7a''' - Type the desired space in the 'Size' field. Make sure 'Leave unformatted' is in the 'Format' field. Select 'Create' and press the Enter key
[[File:jammyefiraid1-7.png|600px]]

* '''Step 7b''' - Repeat steps 6 and 7a for the second device you wish to use for RAID1

* '''Step 8''' - Select 'Create software RAID (md)' and press the Enter key
[[File:jammyefiraid1-8.png|600px]]

* '''Step 9''' - Make sure both partitions created in steps 6 and 7 are ticked. Select 'Create' and press the Enter key
[[File:jammyefiraid1-9.png|600px]]

* '''Step 10''' - Select 'Create volume group (LVM)' and press the Enter key
[[File:jammyefiraid1-10.png|600px]]

* '''Step 11''' - Make sure the software RAID created in step 8 is ticked. Select 'Create' and press the Enter key
[[File:jammyefiraid1-11.png|600px]]

* '''Step 12''' - Go to the free space below the volume group created in step 11, and press the Enter key. Select 'Create Logical Volume' and press the Enter key
[[File:jammyefiraid1-12.png|600px]]

* '''Step 13''' - Type the desired space in the 'Size' field. Make sure 'ext4' is in the 'Format' field. Make sure '/' is in the 'Mount field. Select 'Create' and press the Enter key
[[File:jammyefiraid1-13.png|600px]]

* '''Step 14''' - Go to the bottom, select 'Done' and press the Enter key
[[File:jammyefiraid1-14.png|600px]]

* '''Step 15''' - You will be prompted to 'Confirm destructive action'. Select 'Continue' and press the Enter key. This will now start installing QuantaStor.
[[File:jammyefiraid1-15.png|600px]]

After installation is complete, navigate to the 'Controllers & Enclosures' section and you'll see a Software Boot Controller listed in that section that represents your mirrored boot configuration. You can use the WUI in the future to add a replacement device as a hot-spare to repair the mirror in the event one of your boot devices needs replacement.

[[File:jammyefiraid1-16.png|600px]]

If you run into any difficulties whilst following the above steps. Please contact support@osnexus.com for assistance.

==== Previous Version ====

* [[Ubuntu Software RAID1 (UEFI)|QuantaStor 5.x Software RAID1 (EFI Boot BIOS mode)]]

Ubuntu Software RAID1 (Legacy)

2025-10-20T13:13:31Z

Joshua.blake:

Ubuntu Software RAID1 (UEFI)

2025-10-20T13:12:45Z

Joshua.blake:

'''NOTE''': This page is for older QuantaStor 4 and 5 deployments running on Ubuntu Bionic (18.04) and older, please see this page for [[QuantaStor 6 - Software RAID1 Install Procedure (EFI Boot BIOS Mode)]].

Depending on the operating system, creating the software RAID1 is as easy as a few extra steps during the installation process.

Below are a few screenshots of the process to create a software RAID1 with QuantaStor on Ubuntu Bionic (18.04). The process is almost identical with QuantaStor on Ubuntu Xenial (16.04).

If you are familiar with creating partitions and would like to see the partition table summary, please see the below image. You may also finish the installation as normal and skip ahead to step 40. If you are not familiar with the partitions, follow the instructions below.

[[File:uefiraid40.png|600px]]

There should be four partitions per device, 1MB for the biosgrub (for UEFI and legacy boot), 512MB for the EFI boot, and two RAID partitions, sized accordingly, which will be eventually be put in a RAID to be used for the root filesystem and swap. Software RAID1 is expected to be used on each of the two RAID partitions per device.

=== Instructions ===

* '''Step 1''' - When you are prompted to install QuantaStor on a disk like below, press the ‘ESC’ key
[[File:uefiraid1.png|600px]]

* '''Step 2''' - Select the ‘Partition disks’ option and press the ‘Enter’ key
[[File:uefiraid2.png|600px]]

* '''Step 3''' - You’ll be presented with your disks, depending on whether there is existing data on them, you may need to wipe the partition table. Select your first RAID device, and press the ‘Enter’ key
[[File:uefiraid3.png|600px]]

* '''Step 4''' - Select ‘<Yes>’ and press the ‘Enter’ key
[[File:uefiraid4.png|600px]]

* '''Step 5''' - Do the same for the other RAID device you intend to use. You should now be presented with your RAID devices, and they should have “FREE SPACE” beside them. Select the area below the device, where you will see the “FREE SPACE” and press ‘Enter’
[[File:uefiraid5.png|600px]]

* '''Step 6''' - Press the ‘Enter’ key to select ‘Create a new partition’
[[File:uefiraid6.png|600px]]

* '''Step 7''' - For the first partition; which will be for biosboot and for UEFI plus legacy boot. It’s not required, but we recommend creating it anyway. Enter 1MB for the partition size and press ‘Enter’ to confirm
[[File:uefiraid7.png|600px]]

* '''Step 8''' - Press the ‘Enter’ key to select ‘Beginning’
[[File:uefiraid8.png|600px]]

* '''Step 9''' - Use ‘Reserved BIOS boot area’ and press the ‘Enter’ key on ‘Done setting up the partition’ to confirm
[[File:uefiraid9.png|600px]]

* '''Step 10''' - Select the available space on the device, and press the ‘Enter’ key
[[File:uefiraid10.png|600px]]

* '''Step 11''' - Press the ‘Enter’ key to create a new partition
[[File:uefiraid6.png|600px]]

* '''Step 12''' - For the second partition; which will be for the UEFI boot, we recommend using 512MB. Enter the value in the field and press the ‘Enter’ key
[[File:uefiraid12.png|600px]]

* '''Step 13''' - Press the ‘Enter’ key to select ‘Beginning’
[[File:uefiraid8.png|600px]]

* '''Step 14''' - Use ‘EFI System Partition’ and press the ‘Enter’ key on ‘Done setting up the partition’ to confirm
[[File:uefiraid14.png|600px]]

* '''Step 15''' - Select the available space on the device, and press the ‘Enter’ key
[[File:uefiraid15.png|600px]]

* '''Step 16''' - Press the ‘Enter’ key to create a new partition
[[File:uefiraid6.png|600px]]

* '''Step 17''' - For the third partition, which will be used as one of the two RAID volumes being created, using at least 80% of the device is a good general rule. Enter “80%” and press the ‘Enter’ key to confirm
[[File:uefiraid17.png|600px]]

* '''Step 18''' - Press the ‘Enter’ key to select ‘Beginning’
[[File:uefiraid8.png|600px]]

* '''Step 19''' - Use ‘physical volume for RAID’ and press the ‘Enter’ key on ‘Done setting up the partition’ to confirm
[[File:uefiraid19.png|600px]]

* '''Step 20''' - Select the remaining space on the device, and press the ‘Enter’ key
[[File:uefiraid20.png|600px]]

* '''Step 21''' - Press the ‘Enter’ key to create a new partition
[[File:uefiraid6.png|600px]]

* '''Step 22''' - For the fourth and final partition, press the ‘Enter’ key to confirm and use the remaining space on the device
[[File:uefiraid22.png|600px]]

* '''Step 23''' - Use ‘physical volume for RAID’ and press the ‘Enter’ key on ‘Done setting up the partition’ to confirm
[[File:uefiraid23.png|600px]]

* '''Step 24''' - Repeat the earlier steps and create the partitions on the other device. Select ‘Configure software RAID’ and press the ‘Enter’ key. If prompted to write changes, select ‘<Yes> and press ‘Enter’ to confirm
[[File:uefiraid24.png|600px]]

* '''Step 25''' - Press the ‘Enter’ key to create the first RAID volume
[[File:uefiraid25.png|600px]]

* '''Step 26''' - Select ‘RAID1’ and press the ‘Enter’ key to confirm
[[File:uefiraid26.png|600px]]

* '''Step 27''' - Check that the number of active devices is set to ‘2’ and press the ‘Enter’ key to confirm
[[File:uefiraid27.png|600px]]

* '''Step 28''' - Press the ‘Enter’ key to confirm 0 spare devices, unless spare devices are configured, then change the value accordingly
[[File:uefiraid28.png|600px]]

* '''Step 29''' - Select the third partitions created on each device. Press the ‘Enter’ key to confirm
[[File:uefiraid29.png|600px]]

* '''Step 30''' - Press the ‘Enter’ key to create the second RAID volume
[[File:uefiraid25.png|600px]]

* '''Step 31''' - Select ‘RAID1’ and press the ‘Enter’ key to confirm
[[File:uefiraid26.png|600px]]

* '''Step 32''' - Check that the number of active devices is set to ‘2’ and press the ‘Enter’ key to confirm
[[File:uefiraid27.png|600px]]

* '''Step 33''' - Press the ‘Enter’ key to confirm 0 spare devices, unless spare devices are configured, then change the value accordingly
[[File:uefiraid28.png|600px]]

* '''Step 34''' - Select the fourth partitions created on each device and press the ‘Enter’ key to confirm
[[File:uefiraid34.png|600px]]

* '''Step 35''' - Select ‘Finish’ and press ‘Enter’ to confirm
[[File:uefiraid35.png|600px]]

* '''Step 36''' - Select the empty space of the first RAID volume partition and press the ‘Enter’ key
[[File:uefiraid36.png|600px]]

* '''Step 37''' - Modify the parameters for the partition to ‘Ext4 journaling file system’ and ‘/’ like the below. Select ‘Done setting up the partition’ and press the ‘Enter’ key to confirm
[[File:uefiraid37.png|600px]]

* '''Step 38''' - Select the empty space of the second RAID volume partition and press the ‘Enter’ key
[[File:uefiraid38.png|600px]]

* '''Step 39''' - Modify the parameters for the partition to swap area’ like the below. Select ‘Done setting up the partition’ and press the ‘Enter’ key to confirm
[[File:uefiraid39new.png|600px]]

* '''Step 40''' - Select ‘Finish partitioning and write changes to disk’ and press the ‘Enter’ key to confirm. The system should now start to install
[[File:uefiraid40.png|600px]]

* '''Step 41''' - Log into the system, elevate to root and check the current efibootmgr details with <code>efibootmgr -v</code>. Make a note of the file name for the ubuntu boot entry. For example “\EFI\ubuntu\shimx64.efi”. You should see something like the below
<pre>
root@qs1:~# efibootmgr -v
BootCurrent: 0005
Timeout: 0 seconds
BootOrder: 0005,0000,0001,0004,0002,0003
Boot0000* UiApp FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(462caa21-7614-4503-836e-8ab6f4662331)
Boot0001* UEFI VBOX CD-ROM VB2-01700376 PciRoot(0x0)/Pci(0x1,0x1)/Ata(1,0,0)N.....YM....R,Y.
Boot0002* UEFI VBOX HARDDISK VBf65e2ed8-da02bb65 PciRoot(0x0)/Pci(0xd,0x0)/Sata(0,65535,0)N.....YM....R,Y.
Boot0003* UEFI VBOX HARDDISK VBb000695e-353e023b PciRoot(0x0)/Pci(0xd,0x0)/Sata(1,65535,0)N.....YM....R,Y.
Boot0004* EFI Internal Shell FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(7c04a583-9e3e-4f1c-ad65-e05268d0b4d1)
Boot0005* ubuntu HD(2,GPT,e0653691-0967-413a-8951-ad25478313fe,0x1000,0xf4000)/File(\EFI\ubuntu\shimx64.efi)
</pre>

* '''Step 42''' - Use <code>dd if=/dev/sda2 of=/dev/sdb2</code> to copy the second partition data from the first device to the second device. If your two devices are not sda or sdb, change these accordingly. You should see something like the below
<pre>
root@qs1:~# dd if=/dev/sda2 of=/dev/sdb2
999424+0 records in
999424+0 records out
511705088 bytes (512 MB, 488 MiB) copied, 62.5494 s, 8.2 MB/s
</pre>

* '''Step 43''' - Using the file name for the ubuntu boot entry from step 37, use <code>efibootmgr -c -d /dev/sdb -p 1 -L "ubuntu2" -l “\EFI\ubuntu\shimx64.efi”</code>. You should see something like the below

'''IMPORTANT NOTE''' - Replace /dev/sdb with your second boot device as this could be different. The “ubuntu2” can be of your choosing, and the location of the shimx64.efi may differ.

<pre>
root@qs1:~# efibootmgr -c -d /dev/sdb -p 1 -L "ubuntu2" -l “\EFI\ubuntu\shimx64.efi”
BootCurrent: 0005
Timeout: 0 seconds
BootOrder: 0006,0005,0000,0001,0004,0002,0003
Boot0000* UiApp
Boot0001* UEFI VBOX CD-ROM VB2-01700376
Boot0002* UEFI VBOX HARDDISK VBf65e2ed8-da02bb65
Boot0003* UEFI VBOX HARDDISK VBb000695e-353e023b
Boot0004* EFI Internal Shell
Boot0005* ubuntu
Boot0006* ubuntu2
</pre>

* '''Step 44''' - Check the RAID status for your partitions before rebooting the system with <code>cat /proc/mdstat</code> if everything is healthy, you should see something like the below
<pre>
root@qs1:~# cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md1 : active raid1 sda4[0] sdb4[1]
4090880 blocks super 1.2 [2/2] [UU]

md0 : active raid1 sda3[0] sdb3[1]
16365568 blocks super 1.2 [2/2] [UU]

unused devices: <none>
</pre>

If you run into any difficulties whilst following the below steps. Please contact support@osnexus.com for assistance.

QuantaStor 6 - Software RAID1 Install Procedure (EFI Boot BIOS Mode)

2025-10-20T13:11:42Z

Joshua.blake: /* Previous Version */

Creating the software RAID1 is as easy as a few extra steps during the installation process.

Below are a few screenshots of the process to create a software RAID1 with QuantaStor 6 and newer using QuantaStor ISO media based on Ubuntu 20.04 (Focal) and 22.04 (Jammy).

=== Instructions ===

* '''Step 1''' - When first prompted, select 'Install OSNEXUS QuantaStor'. If you would like to skip checking the media, select 'Install (skip Media Check)'
[[File:jammyefiraid1-1.png|600px]]

* '''Step 2''' - Configure the networking as desired, and press the Enter key on 'Done'
[[File:jammyefiraid1-2.png|600px]]

* '''Step 3''' - Make sure 'Custom storage layout' is selected, and press the Enter key on 'Done'
[[File:jammyefiraid1-3.png|600px]]

* '''Step 4''' - Go to the first device you wish to use for RAID1, and press the Enter key. Select 'Use As Boot Device' and press the Enter key
[[File:jammyefiraid1-4.png|600px]]

* '''Step 5''' - Repeat the same step for the second device you wish to use for RAID1, and press the Enter key. Select 'Use As Another Boot Device' and press the Enter key
[[File:jammyefiraid1-5.png|600px]]

* '''Step 6''' - Go to the free space on the first device you wish to use for RAID1, and press the Enter key. Select 'Add GPT Partition' and press the Enter key
[[File:jammyefiraid1-6.png|600px]]

* '''Step 7a''' - Type the desired space in the 'Size' field. Make sure 'Leave unformatted' is in the 'Format' field. Select 'Create' and press the Enter key
[[File:jammyefiraid1-7.png|600px]]

* '''Step 7b''' - Repeat steps 6 and 7a for the second device you wish to use for RAID1

* '''Step 8''' - Select 'Create software RAID (md)' and press the Enter key
[[File:jammyefiraid1-8.png|600px]]

* '''Step 9''' - Make sure both partitions created in steps 6 and 7 are ticked. Select 'Create' and press the Enter key
[[File:jammyefiraid1-9.png|600px]]

* '''Step 10''' - Select 'Create volume group (LVM)' and press the Enter key
[[File:jammyefiraid1-10.png|600px]]

* '''Step 11''' - Make sure the software RAID created in step 8 is ticked. Select 'Create' and press the Enter key
[[File:jammyefiraid1-11.png|600px]]

* '''Step 12''' - Go to the free space below the volume group created in step 11, and press the Enter key. Select 'Create Logical Volume' and press the Enter key
[[File:jammyefiraid1-12.png|600px]]

* '''Step 13''' - Type the desired space in the 'Size' field. Make sure 'ext4' is in the 'Format' field. Make sure '/' is in the 'Mount field. Select 'Create' and press the Enter key
[[File:jammyefiraid1-13.png|600px]]

* '''Step 14''' - Go to the bottom, select 'Done' and press the Enter key
[[File:jammyefiraid1-14.png|600px]]

* '''Step 15''' - You will be prompted to 'Confirm destructive action'. Select 'Continue' and press the Enter key. This will now start installing QuantaStor.
[[File:jammyefiraid1-15.png|600px]]

After installation is complete, navigate to the 'Controllers & Enclosures' section and you'll see a Software Boot Controller listed in that section that represents your mirrored boot configuration. You can use the WUI in the future to add a replacement device as a hot-spare to repair the mirror in the event one of your boot devices needs replacement.

[[File:focalraid1-16.png|600px]]

If you run into any difficulties whilst following the above steps. Please contact support@osnexus.com for assistance.

==== Previous Version ====

* [[Ubuntu Software RAID1 (UEFI)|QuantaStor 5.x Software RAID1 (EFI Boot BIOS mode)]]

File:Jammyefiraid1-15.png

2025-10-20T13:10:39Z

Joshua.blake:

File:Jammyefiraid1-14.png

2025-10-20T13:10:27Z

Joshua.blake:

File:Jammyefiraid1-13.png

2025-10-20T13:10:15Z

Joshua.blake:

File:Jammyefiraid1-12.png

2025-10-20T13:09:32Z

Joshua.blake:

File:Jammyefiraid1-11.png

2025-10-20T13:09:16Z

Joshua.blake:

File:Jammyefiraid1-10.png

2025-10-20T13:08:00Z

Joshua.blake: Joshua.blake uploaded a new version of File:Jammyefiraid1-10.png

File:Jammyefiraid1-9.png

2025-10-20T13:07:33Z

Joshua.blake: Joshua.blake uploaded a new version of File:Jammyefiraid1-9.png

File:Jammyefiraid1-8.png

2025-10-20T13:07:15Z

Joshua.blake: Joshua.blake uploaded a new version of File:Jammyefiraid1-8.png

File:Jammyefiraid1-7.png

2025-10-20T13:06:38Z

Joshua.blake: Joshua.blake uploaded a new version of File:Jammyefiraid1-7.png

File:Jammyefiraid1-6.png

2025-10-20T13:06:10Z

Joshua.blake: Joshua.blake uploaded a new version of File:Jammyefiraid1-6.png

File:Jammyefiraid1-5.png

2025-10-20T12:55:51Z

Joshua.blake: Joshua.blake uploaded a new version of File:Jammyefiraid1-5.png

File:Jammyefiraid1-4.png

2025-10-20T12:46:04Z

Joshua.blake: Joshua.blake uploaded a new version of File:Jammyefiraid1-4.png

File:Jammyefiraid1-3.png

2025-10-20T12:45:14Z

Joshua.blake: Joshua.blake uploaded a new version of File:Jammyefiraid1-3.png

File:Jammyefiraid1-10.png

2025-10-20T12:31:02Z

Joshua.blake:

File:Jammyefiraid1-9.png

2025-10-20T12:30:43Z

Joshua.blake:

File:Jammyefiraid1-8.png

2025-10-20T12:29:35Z

Joshua.blake:

File:Jammyefiraid1-6.png

2025-10-20T12:26:40Z

Joshua.blake: Joshua.blake uploaded a new version of File:Jammyefiraid1-6.png

File:Jammyefiraid1-7.png

2025-10-20T12:26:19Z

Joshua.blake:

File:Jammyefiraid1-6.png

2025-10-20T12:23:13Z

Joshua.blake:

File:Jammyefiraid1-5.png

2025-10-20T12:22:35Z

Joshua.blake:

File:Jammyefiraid1-4.png

2025-10-20T12:22:06Z

Joshua.blake:

File:Jammyefiraid1-3.png

2025-10-20T12:21:07Z

Joshua.blake:

File:Jammyefiraid1-2.png

2025-10-20T12:20:40Z

Joshua.blake:

File:Jammyefiraid1-1.png

2025-10-20T12:13:10Z

Joshua.blake: Joshua.blake uploaded a new version of File:Jammyefiraid1-1.png

File:Jammyefiraid1-1.png

2025-10-20T12:08:37Z

Joshua.blake:

QuantaStor 6 - Software RAID1 Install Procedure (EFI Boot BIOS Mode)

2025-10-20T12:06:03Z

Joshua.blake: /* Instructions */

Creating the software RAID1 is as easy as a few extra steps during the installation process.

Below are a few screenshots of the process to create a software RAID1 with QuantaStor 6 and newer using QuantaStor ISO media based on Ubuntu 20.04 (Focal) and 22.04 (Jammy).

=== Instructions ===

* '''Step 1''' - When first prompted, select 'Install OSNEXUS QuantaStor'. If you would like to skip checking the media, select 'Install (skip Media Check)'
[[File:jammyefiraid1-1.png|600px]]

* '''Step 2''' - Configure the networking as desired, and press the Enter key on 'Done'
[[File:jammyefiraid1-2.png|600px]]

* '''Step 3''' - Make sure 'Custom storage layout' is selected, and press the Enter key on 'Done'
[[File:jammyefiraid1-3.png|600px]]

* '''Step 4''' - Go to the first device you wish to use for RAID1, and press the Enter key. Select 'Use As Boot Device' and press the Enter key
[[File:jammyefiraid1-4.png|600px]]

* '''Step 5''' - Repeat the same step for the second device you wish to use for RAID1, and press the Enter key. Select 'Use As Another Boot Device' and press the Enter key
[[File:jammyefiraid1-5.png|600px]]

* '''Step 6''' - Go to the free space on the first device you wish to use for RAID1, and press the Enter key. Select 'Add GPT Partition' and press the Enter key
[[File:jammyefiraid1-6.png|600px]]

* '''Step 7a''' - Type the desired space in the 'Size' field. Make sure 'Leave unformatted' is in the 'Format' field. Select 'Create' and press the Enter key
[[File:jammyefiraid1-7.png|600px]]

* '''Step 7b''' - Repeat steps 6 and 7a for the second device you wish to use for RAID1

* '''Step 8''' - Select 'Create software RAID (md)' and press the Enter key
[[File:jammyefiraid1-8.png|600px]]

* '''Step 9''' - Make sure both partitions created in steps 6 and 7 are ticked. Select 'Create' and press the Enter key
[[File:jammyefiraid1-9.png|600px]]

* '''Step 10''' - Select 'Create volume group (LVM)' and press the Enter key
[[File:jammyefiraid1-10.png|600px]]

* '''Step 11''' - Make sure the software RAID created in step 8 is ticked. Select 'Create' and press the Enter key
[[File:jammyefiraid1-11.png|600px]]

* '''Step 12''' - Go to the free space below the volume group created in step 11, and press the Enter key. Select 'Create Logical Volume' and press the Enter key
[[File:jammyefiraid1-12.png|600px]]

* '''Step 13''' - Type the desired space in the 'Size' field. Make sure 'ext4' is in the 'Format' field. Make sure '/' is in the 'Mount field. Select 'Create' and press the Enter key
[[File:jammyefiraid1-13.png|600px]]

* '''Step 14''' - Go to the bottom, select 'Done' and press the Enter key
[[File:jammyefiraid1-14.png|600px]]

* '''Step 15''' - You will be prompted to 'Confirm destructive action'. Select 'Continue' and press the Enter key. This will now start installing QuantaStor.
[[File:jammyefiraid1-15.png|600px]]

After installation is complete, navigate to the 'Controllers & Enclosures' section and you'll see a Software Boot Controller listed in that section that represents your mirrored boot configuration. You can use the WUI in the future to add a replacement device as a hot-spare to repair the mirror in the event one of your boot devices needs replacement.

[[File:focalraid1-16.png|600px]]

If you run into any difficulties whilst following the above steps. Please contact support@osnexus.com for assistance.

==== Previous Version ====

* [[Ubuntu Software RAID1 (Legacy)|QuantaStor 5.x Software RAID1 (Legacy Boot BIOS mode)]]

QuantaStor 6 - Software RAID1 Install Procedure (EFI Boot BIOS Mode)

2025-10-20T12:03:26Z

Joshua.blake: Created page with "Creating the software RAID1 is as easy as a few extra steps during the installation process. Below are a few screenshots of the process to create a software RAID1 with QuantaStor 6 and newer using QuantaStor ISO media based on Ubuntu 20.04 (Focal) and 22.04 (Jammy). === Instructions === * '''Step 1''' - When first prompted, select 'Install OSNEXUS QuantaStor'. If you would like to skip checking the media, select 'Install (skip Media Check)' File:focalraid1-1.png|600..."

Creating the software RAID1 is as easy as a few extra steps during the installation process.

Below are a few screenshots of the process to create a software RAID1 with QuantaStor 6 and newer using QuantaStor ISO media based on Ubuntu 20.04 (Focal) and 22.04 (Jammy).

=== Instructions ===

* '''Step 1''' - When first prompted, select 'Install OSNEXUS QuantaStor'. If you would like to skip checking the media, select 'Install (skip Media Check)'
[[File:focalraid1-1.png|600px]]

* '''Step 2''' - Configure the networking as desired, and press the Enter key on 'Done'
[[File:focalraid1-2.png|600px]]

* '''Step 3''' - Make sure 'Custom storage layout' is selected, and press the Enter key on 'Done'
[[File:focalraid1-3.png|600px]]

* '''Step 4''' - Go to the first device you wish to use for RAID1, and press the Enter key. Select 'Use As Boot Device' and press the Enter key
[[File:focalraid1-4.png|600px]]

* '''Step 5''' - Repeat the same step for the second device you wish to use for RAID1, and press the Enter key. Select 'Use As Another Boot Device' and press the Enter key
[[File:focalraid1-5.png|600px]]

* '''Step 6''' - Go to the free space on the first device you wish to use for RAID1, and press the Enter key. Select 'Add GPT Partition' and press the Enter key
[[File:focalraid1-6.png|600px]]

* '''Step 7a''' - Type the desired space in the 'Size' field. Make sure 'Leave unformatted' is in the 'Format' field. Select 'Create' and press the Enter key
[[File:focalraid1-7.png|600px]]

* '''Step 7b''' - Repeat steps 6 and 7a for the second device you wish to use for RAID1

* '''Step 8''' - Select 'Create software RAID (md)' and press the Enter key
[[File:focalraid1-8.png|600px]]

* '''Step 9''' - Make sure both partitions created in steps 6 and 7 are ticked. Select 'Create' and press the Enter key
[[File:focalraid1-9.png|600px]]

* '''Step 10''' - Select 'Create volume group (LVM)' and press the Enter key
[[File:focalraid1-10.png|600px]]

* '''Step 11''' - Make sure the software RAID created in step 8 is ticked. Select 'Create' and press the Enter key
[[File:focalraid1-11.png|600px]]

* '''Step 12''' - Go to the free space below the volume group created in step 11, and press the Enter key. Select 'Create Logical Volume' and press the Enter key
[[File:focalraid1-12.png|600px]]

* '''Step 13''' - Type the desired space in the 'Size' field. Make sure 'ext4' is in the 'Format' field. Make sure '/' is in the 'Mount field. Select 'Create' and press the Enter key
[[File:focalraid1-13.png|600px]]

* '''Step 14''' - Go to the bottom, select 'Done' and press the Enter key
[[File:focalraid1-14.png|600px]]

* '''Step 15''' - You will be prompted to 'Confirm destructive action'. Select 'Continue' and press the Enter key. This will now start installing QuantaStor.
[[File:focalraid1-15.png|600px]]

After installation is complete, navigate to the 'Controllers & Enclosures' section and you'll see a Software Boot Controller listed in that section that represents your mirrored boot configuration. You can use the WUI in the future to add a replacement device as a hot-spare to repair the mirror in the event one of your boot devices needs replacement.

[[File:focalraid1-16.png|600px]]

If you run into any difficulties whilst following the above steps. Please contact support@osnexus.com for assistance.

==== Previous Version ====

* [[Ubuntu Software RAID1 (Legacy)|QuantaStor 5.x Software RAID1 (Legacy Boot BIOS mode)]]

Bare-metal Install

2025-10-20T12:03:08Z

Joshua.blake: /* Software RAID1 for Boot/System Disk Configuration */

[[index.php?title=Category:Install guide]]
This section covers the bare-metal install process for putting QuantaStor on a physical server (rather than on a virtual machine). QuantaStor is delivered as an operating system, and thus no additional software is required on a given system. QuantaStor is Linux based, and has an extensive HCL (see [[Recommended Hardware|HCL]] in order to support server models from all major manufacturers.

== BIOS Configuration Checks ==

Proper configuration of the BIOS settings is very important to successful installation and continuous operation of the system. Settings like power save options, which could cause the system to inadvertently go to sleep or hibernate, are important to disable by putting the system into a 'Performance' power save profile.

[[File:Bios_powersave.png|300px|thumb|Enabling 'Performance' mode to ensure the system doesn't sleep/hibernate]]

=== Boot Order ===

Before installing QuantaStor from the ISO, two changes must be made to the BIOS. First the USB or CD/DVD device with the QuantaStor ISO media must be selected as the primary boot device so that the install media loads at the initial install time. Second, the system disk, (the SSD the system will boot to after installation has completed) should be the selected device to boot from and assigned to the second position in the BIOS boot order. After the installation, you should disconnect the ISO installation media.

=== Power Save Settings ===

Make sure that your storage system server is set to the 'Performance' setting. Stability problems can occur if power saving is enabled. QuantaStor is not designed for systems to hibernate or sleep like a desktop.

=== IPMI/iDRAC Settings ===

Be sure to apply an IP address to the server's IPMI port, so that you can remotely access the console. This is important for triaging connectivity and network issues.

== Boot/System Disk Configuration ==

[[File:Megaraid_disks.png|thumb|300px|Selecting drives to create a RAID1 logic disk for QuantaStor system/boot]]

=== Hardware RAID1 ===

It is highly recommended that QuantaStor is installed to a mirrored (RAID1) pair of SSDs, so that service is not interrupted in the event of a drive failure. The underlying Linux operating system for QuantaStor has support for software RAID, which could be used, but is more complex. Both hardware RAID1 and software RAID1 for boot is supported. Currently you must set aside two unpartitioned disks for QuantaStor in order to create a RAID1 device to install to. QuantaStor has a small footprint, and two small capacity 250GB SSD or NVMe drives will be adequate for the boot/system drive (any type will work HDD/SSD and SATA/SAS/NVMe). For deployment as a virtual appliance, OSNEXUS recommends 30GB for the boot device, plus the amount of GB in RAM of disk space. 50-100GB or more is recommended for larger configurations.

==== SSD Boot Media Required ====

For production deployments the boot media must be mirrored SSD or mirrored NVMe media. QuantaStor uses the boot media to run the operating system, databases for metrics, the grid configuration database, and more. HDDs have very low IOPS which under load can easily be at or below 100 IOPS. If individual I/O operations are small like 4K that equates to 400K/sec which is insufficient. For SSDs we recommend any good quality SSD mediathat is datacenter or enterprise grade SATA SSDs, SAS SSDs, or NVMe SSDs. For bare-metal installs we recommend 480GB SSDs but 240GB SSDs will do.

==== Creating Hardware RAID1 Mirrored System Disk ====

Use the BIOS based configuration on the RAID controller to create a RAID1 mirror using a pair of SSDs. Please refer to the HBA/RAID controller vendor's documentation for complete details on how to create a RAID1 mirror using a pair of SSDs. For LSI/Broadcom controllers and OEM variants this involves creating a Disk Group 0 with both disks, a single span, and a single virtual drive.

=== Software RAID1 for Boot/System Disk Configuration ===

Software RAID1 for the boot media is supported but is a bit more complex to setup. The following links have instructions on how to setup the software RAID1 mirrors.

==== [[QuantaStor 6 - Software RAID1 Install Procedure (Legacy Boot BIOS Mode)|QuantaStor 6 - Software RAID1 Install Procedure (Legacy Boot BIOS Mode)]] ====

==== [[QuantaStor 6 - Software RAID1 Install Procedure (EFI Boot BIOS Mode)|QuantaStor 6 - Software RAID1 Install Procedure (EFI Boot BIOS Mode)]] ====

QuantaStor will identify the boot media setup in a software RAID1 mirror as a special [system/boot] pool. These are automatically excluded from the web management interface (WUI) but they can be viewed using the command line utility using 'qs pool-list'. If the RAID1 mirror becomes degraded then it will appear in the WUI to make it easier to identify the bad media so it may be replaced.

== Installation Options ==

QuantaStor is available on both RHEL and Ubuntu LTS as a base Linux operating system under the storage platform.

* The standard OSNEXUS QuantaStor ISO media is derivative of '''Ubuntu LTS''' releases and is a single step install process
** Download & Install [https://osnexus.com/downloads QuantaStor ISO media] from the OSNEXUS web site (osnexus.com/downloads)

* To install QuantaStor with a '''RHEL''' base operating system it is a two step process
** Download & Instal RHEL 8.4 Install media from Redhat.com.
** Download and run the QuantaStor installation script.

Irrespective of the base OS, once the installation is done simply login via the QuantaStor web interface to manage the system. Storage Grids may be comprised of a hybrid mix of servers using Ubuntu and/or RHEL as the base OS.

''' OSNEXUS Videos '''
* [[Image:youtube_icon.png|50px|link=https://www.youtube.com/watch?v=AzBHOxnNatQ]] [https://www.youtube.com/watch?v=AzBHOxnNatQ Covers How To Install QuantaStor 5 on RHEL/CentOS 7.8 [7:20]]

== Starting the Installation from RHEL Media ==

QuantaStor 5.x releases can be installed on RHEL 8.5 and higher versions of Linux.

==== Step 1: ISO "Minimal Install" ====

After booting your server or VM to the RHEL installation ISO media choose the "Minimal Installation" option as the rest of the packages will be installed later via the QuantaStor installation script.

==== Step 2: Select Boot/System Device ====

In the RHEL installation screen choose the drive onto which you'll be installing QuantaStor. We require installing onto SSD media (100GB or larger) in a hardware RAID1 layout. If that is not available in your server you may install to a single SSD device or use software RAID1.

* NOTE: The Linux based software RAID1 option will require some additional configuration steps later on so it's not recommended without assistance from OSNEXUS Customer Support

For partitioning, chose the non-lvm option that creates the simple os layout without the /home directory and most disk space devoted to the '/' root disk directory.

==== Step 3: Set Host Name & Enable DHCP ====

Set the system host name to "quantastor" or something suitable for your environment. Next, enable at least one network port so that when the system boots it can get an initial IP address via DHCP.

* NOTE: We recommend changing all ports to static IPs after these installation steps are completed. Ports may be easily configured via the QuantaStor web management interface.

==== Step 4: Set "root" Password ====

Press "Begin Installation" to get the the next installation page where you'll be able to set the "root" user password. Set the root password to a strong password and be sure to save it in a safe place. The root user password may be needed in the future if there are network connectivity or other maintenance issues that require login via SSH or via the IPMI/iDRAC/iLO base board controller console interface. Besides special case maintenance steps (such as this install procedure) one will generally not need to login to the console/SSH. The default "admin" QuantaStor management account for managing the system is separate from the "root" user low level Linux account.

==== Step 5: Login as "root" ====

After the OS installation completes the system will reboot and you'll be presented with the login prompt. Login as the "root" user so that you can License your RHEL install with the redhat repoository servers and run the QuantaStor installation script.

Typically you will add a RHEL subscription using 'subscription-manager register' and 'subscription-manager attach' from the command line.

Full Instructions for registering the RHEL install from the command line are available here:
https://access.redhat.com/documentation/en-us/red_hat_subscription_management/1/html/quick_registration_for_rhel/registering-cmd

Note, that you will need a Full RHEL Server License and HA Addon License. The reduced Self-service Server license is not supported.

==== Step 6 (Optional): Install The Mellanox OFED for RDMA/NVMEoF and best Mellanox Performance ====

For customers with Mellanox Network Cards. The latest Mellanox Driver stack is required for advanced features such as connecting to NVMEoF devices over RDMA or to get the best performance out of 100GbE/200GbE network devices.

This can be installed using the below script:
<pre>
curl -o ./mellanox-ofed-install.sh http://packages.osnexus.com/packages-redhat/mellanox-ofed-install.sh
chmod 755 mellanox-ofed-install.sh
./mellanox-ofed-install.sh
</pre>

==== Step 7: Install QuantaStor via Script ====

Now that RHEL is installed and Licensed the QuantaStor installation script can be downloaded an run:

<pre>
curl -o ./qs_upgrade_redhat8.sh http://packages.osnexus.com/packages-redhat/qs_upgrade_redhat8.sh
chmod 755 qs_upgrade_redhat8.sh
./qs_upgrade_redhat8.sh installall
</pre>

==== Step 8: Login via Web UI ====

Once all the stages of the installation script have completed you'll be able to login to the QuantaStor web management interface as "admin" using the default password which is "password". The QuantaStor web management interface is accessible via HTTPS using any browser. Simply input the IP address of the QuantaStor server that it acquired via DHCP.

Note: Run this command to get the IP address of the system if you don't have it and are logged in via a console:

<pre>
ip addr
</pre>

==== Step 9: Basic Installation Complete ====

At this point installation is complete but we recommend rebooting/power cycling the system to make sure everything is correct from a boot media and BIOS configuration perspective.

* NOTE: If you have external JBODs we recommend running the above installation steps without those attached to make it faster and easier. Once the above steps are complete, simply shutdown the system, attach the JBODs, and boot.

==== Step 10: Apply QuantaStor License Key ====

After logging in to the QuantaStor web user interface (WUI) for the first time be sure to add your license key. If you don't have a commercial use license key you can get temporary Trial Edition licenses via the [https://osnexus.com/trynow Try Now] page. OSNEXUS non-commercial use Community Edition licenses are available via the same page.

== Starting the Installation from QuantaStor ISO/USB media ==
[[File:Rufus_screen_shot.png|thumb|300px|Preparing USB ISO media for QuantaStor install|link=QuantaStor_Installation_via_USB_Thumb_Drive]]
==== Step 1: Preparing the ISO/USB media ====
For bare-metal installation we recommend using a 8GB or larger USB stick. Once you've downloaded the ISO file from the OSNEXUS web site you can put it onto your USB device using software like [https://sourceforge.net/projects/usbwriter/ usbwriter]. Another option is to burn a DVD and use a portable USB DVD device to install from. Detailed instructions on [[QuantaStor Installation via USB Thumb Drive|how to put QuantaStor on to USB media]] is provided [[QuantaStor Installation via USB Thumb Drive|here]] for both Windows and Linux.

==== Step 2: Insert and Boot from the QuantaStor USB Install Media ====
After connecting your QuantaStor Install USB stick to the server you will see the QuantaStor screen appear and it will automatically select 'English' as the default language and begin the installation process.

==== Step 3: Selecting a hostname ====
The first question you will be asked as part of the installation process is what do you want to name the host. By default the name 'quantastor' is given, but you can give the system any valid host name. If you're setting up multiple systems you should give them each unique names. You can also change the name later through the web management interface using the Storage System Modify dialog.

==== Step 4: Selecting a network port ====
The second step in the console level installation process is the selection of which port to use for network communication during the install process. If the new QuantaStor system has a single network interface then it will automatically attempt to configure the using DHCP; if DHCP is not available then standard details will need to be provided (Static IP Address, Subnetmask, and gateway if applicable). If multiple ports are detected a menu will be provided allowing you to choose which interface to use for the management port. The installation process will use the network to try to get more recent versions of packages than those that are on the CD.

==== Step 5: Selecting the device to install the QuantaStor OS ====
Finally, the configuration wizard will ask which partitioning scheme to use. We recommend 'Guided installation, use entire disk'. If you are planning to mirror your boot drive (highly recommended) then you'll want to use the Hardware RAID controller's configuration BIOS to create a RAID1 logical drive first. The next screen will ask you which disk you want to use as the system boot disk, at that point you'll select your RAID1 mirrored system/boot drive.

<pre>WARNING, this disk will be reformatted as part of the installation process so be
careful to choose a disk that does not have data on it you need.</pre>

==== Step 6: Bare-metal Installation is Complete ====
That's all the key questions you will be asked as part of the installation process. After the installation completes the system will reboot and will start-up the QuantaStor system. At this point you can login using the 'qadmin' user account and 'qadmin' password so that you can get the IP address of the system. To get the IP address just type 'ifconfig' at the command prompt after you have logged in. You'll see an entry for 'eth0' with an IP address assigned to it. Enter that IP address into your web browser to connect to your QuantaStor storage system via your favorite web browser so that you can start to configure the rest of the system.

A video of the installation process is available on the main web site in the [http://www.osnexus.com/videos/ Videos] section.

QuantaStor 6 - Software RAID1 Install Procedure (Legacy Boot BIOS Mode)

2025-10-20T12:01:47Z

Creating the software RAID1 is as easy as a few extra steps during the installation process.

Below are a few screenshots of the process to create a software RAID1 with QuantaStor 6 and newer using QuantaStor ISO media based on Ubuntu 20.04 (Focal) and 22.04 (Jammy).

=== Instructions ===

* '''Step 1''' - When first prompted, select 'Install OSNEXUS QuantaStor'. If you would like to skip checking the media, select 'Install (skip Media Check)'
[[File:focalraid1-1.png|600px]]

* '''Step 2''' - Configure the networking as desired, and press the Enter key on 'Done'
[[File:focalraid1-2.png|600px]]

* '''Step 3''' - Make sure 'Custom storage layout' is selected, and press the Enter key on 'Done'
[[File:focalraid1-3.png|600px]]

* '''Step 4''' - Go to the first device you wish to use for RAID1, and press the Enter key. Select 'Use As Boot Device' and press the Enter key
[[File:focalraid1-4.png|600px]]

* '''Step 5''' - Repeat the same step for the second device you wish to use for RAID1, and press the Enter key. Select 'Use As Another Boot Device' and press the Enter key
[[File:focalraid1-5.png|600px]]

* '''Step 6''' - Go to the free space on the first device you wish to use for RAID1, and press the Enter key. Select 'Add GPT Partition' and press the Enter key
[[File:focalraid1-6.png|600px]]

* '''Step 7a''' - Type the desired space in the 'Size' field. Make sure 'Leave unformatted' is in the 'Format' field. Select 'Create' and press the Enter key
[[File:focalraid1-7.png|600px]]

* '''Step 7b''' - Repeat steps 6 and 7a for the second device you wish to use for RAID1

* '''Step 8''' - Select 'Create software RAID (md)' and press the Enter key
[[File:focalraid1-8.png|600px]]

* '''Step 9''' - Make sure both partitions created in steps 6 and 7 are ticked. Select 'Create' and press the Enter key
[[File:focalraid1-9.png|600px]]

* '''Step 10''' - Select 'Create volume group (LVM)' and press the Enter key
[[File:focalraid1-10.png|600px]]

* '''Step 11''' - Make sure the software RAID created in step 8 is ticked. Select 'Create' and press the Enter key
[[File:focalraid1-11.png|600px]]

* '''Step 12''' - Go to the free space below the volume group created in step 11, and press the Enter key. Select 'Create Logical Volume' and press the Enter key
[[File:focalraid1-12.png|600px]]

* '''Step 13''' - Type the desired space in the 'Size' field. Make sure 'ext4' is in the 'Format' field. Make sure '/' is in the 'Mount field. Select 'Create' and press the Enter key
[[File:focalraid1-13.png|600px]]

* '''Step 14''' - Go to the bottom, select 'Done' and press the Enter key
[[File:focalraid1-14.png|600px]]

* '''Step 15''' - You will be prompted to 'Confirm destructive action'. Select 'Continue' and press the Enter key. This will now start installing QuantaStor.
[[File:focalraid1-15.png|600px]]

After installation is complete, navigate to the 'Controllers & Enclosures' section and you'll see a Software Boot Controller listed in that section that represents your mirrored boot configuration. You can use the WUI in the future to add a replacement device as a hot-spare to repair the mirror in the event one of your boot devices needs replacement.

[[File:focalraid1-16.png|600px]]

If you run into any difficulties whilst following the above steps. Please contact support@osnexus.com for assistance.

==== Previous Version ====

* [[Ubuntu Software RAID1 (Legacy)|QuantaStor 5.x Software RAID1 (Legacy Boot BIOS mode)]]

Bare-metal Install

2025-10-20T12:01:27Z

Joshua.blake: /* Software RAID1 for Boot/System Disk Configuration */

[[index.php?title=Category:Install guide]]
This section covers the bare-metal install process for putting QuantaStor on a physical server (rather than on a virtual machine). QuantaStor is delivered as an operating system, and thus no additional software is required on a given system. QuantaStor is Linux based, and has an extensive HCL (see [[Recommended Hardware|HCL]] in order to support server models from all major manufacturers.

== BIOS Configuration Checks ==

Proper configuration of the BIOS settings is very important to successful installation and continuous operation of the system. Settings like power save options, which could cause the system to inadvertently go to sleep or hibernate, are important to disable by putting the system into a 'Performance' power save profile.

[[File:Bios_powersave.png|300px|thumb|Enabling 'Performance' mode to ensure the system doesn't sleep/hibernate]]

=== Boot Order ===

Before installing QuantaStor from the ISO, two changes must be made to the BIOS. First the USB or CD/DVD device with the QuantaStor ISO media must be selected as the primary boot device so that the install media loads at the initial install time. Second, the system disk, (the SSD the system will boot to after installation has completed) should be the selected device to boot from and assigned to the second position in the BIOS boot order. After the installation, you should disconnect the ISO installation media.

=== Power Save Settings ===

Make sure that your storage system server is set to the 'Performance' setting. Stability problems can occur if power saving is enabled. QuantaStor is not designed for systems to hibernate or sleep like a desktop.

=== IPMI/iDRAC Settings ===

Be sure to apply an IP address to the server's IPMI port, so that you can remotely access the console. This is important for triaging connectivity and network issues.

== Boot/System Disk Configuration ==

[[File:Megaraid_disks.png|thumb|300px|Selecting drives to create a RAID1 logic disk for QuantaStor system/boot]]

=== Hardware RAID1 ===

It is highly recommended that QuantaStor is installed to a mirrored (RAID1) pair of SSDs, so that service is not interrupted in the event of a drive failure. The underlying Linux operating system for QuantaStor has support for software RAID, which could be used, but is more complex. Both hardware RAID1 and software RAID1 for boot is supported. Currently you must set aside two unpartitioned disks for QuantaStor in order to create a RAID1 device to install to. QuantaStor has a small footprint, and two small capacity 250GB SSD or NVMe drives will be adequate for the boot/system drive (any type will work HDD/SSD and SATA/SAS/NVMe). For deployment as a virtual appliance, OSNEXUS recommends 30GB for the boot device, plus the amount of GB in RAM of disk space. 50-100GB or more is recommended for larger configurations.

==== SSD Boot Media Required ====

For production deployments the boot media must be mirrored SSD or mirrored NVMe media. QuantaStor uses the boot media to run the operating system, databases for metrics, the grid configuration database, and more. HDDs have very low IOPS which under load can easily be at or below 100 IOPS. If individual I/O operations are small like 4K that equates to 400K/sec which is insufficient. For SSDs we recommend any good quality SSD mediathat is datacenter or enterprise grade SATA SSDs, SAS SSDs, or NVMe SSDs. For bare-metal installs we recommend 480GB SSDs but 240GB SSDs will do.

==== Creating Hardware RAID1 Mirrored System Disk ====

Use the BIOS based configuration on the RAID controller to create a RAID1 mirror using a pair of SSDs. Please refer to the HBA/RAID controller vendor's documentation for complete details on how to create a RAID1 mirror using a pair of SSDs. For LSI/Broadcom controllers and OEM variants this involves creating a Disk Group 0 with both disks, a single span, and a single virtual drive.

=== Software RAID1 for Boot/System Disk Configuration ===

Software RAID1 for the boot media is supported but is a bit more complex to setup. The following links have instructions on how to setup the software RAID1 mirrors.

==== [[QuantaStor 6 - Software RAID1 Install Procedure (Legacy Boot BIOS Mode)|QuantaStor 6 - Software RAID1 Install Procedure (Legacy Boot BIOS Mode)]] ====

==== [[Ubuntu Software RAID1 (UEFI)]] ====

QuantaStor will identify the boot media setup in a software RAID1 mirror as a special [system/boot] pool. These are automatically excluded from the web management interface (WUI) but they can be viewed using the command line utility using 'qs pool-list'. If the RAID1 mirror becomes degraded then it will appear in the WUI to make it easier to identify the bad media so it may be replaced.

== Installation Options ==

QuantaStor is available on both RHEL and Ubuntu LTS as a base Linux operating system under the storage platform.

* The standard OSNEXUS QuantaStor ISO media is derivative of '''Ubuntu LTS''' releases and is a single step install process
** Download & Install [https://osnexus.com/downloads QuantaStor ISO media] from the OSNEXUS web site (osnexus.com/downloads)

* To install QuantaStor with a '''RHEL''' base operating system it is a two step process
** Download & Instal RHEL 8.4 Install media from Redhat.com.
** Download and run the QuantaStor installation script.

Irrespective of the base OS, once the installation is done simply login via the QuantaStor web interface to manage the system. Storage Grids may be comprised of a hybrid mix of servers using Ubuntu and/or RHEL as the base OS.

''' OSNEXUS Videos '''
* [[Image:youtube_icon.png|50px|link=https://www.youtube.com/watch?v=AzBHOxnNatQ]] [https://www.youtube.com/watch?v=AzBHOxnNatQ Covers How To Install QuantaStor 5 on RHEL/CentOS 7.8 [7:20]]

== Starting the Installation from RHEL Media ==

QuantaStor 5.x releases can be installed on RHEL 8.5 and higher versions of Linux.

==== Step 1: ISO "Minimal Install" ====

After booting your server or VM to the RHEL installation ISO media choose the "Minimal Installation" option as the rest of the packages will be installed later via the QuantaStor installation script.

==== Step 2: Select Boot/System Device ====

In the RHEL installation screen choose the drive onto which you'll be installing QuantaStor. We require installing onto SSD media (100GB or larger) in a hardware RAID1 layout. If that is not available in your server you may install to a single SSD device or use software RAID1.

* NOTE: The Linux based software RAID1 option will require some additional configuration steps later on so it's not recommended without assistance from OSNEXUS Customer Support

For partitioning, chose the non-lvm option that creates the simple os layout without the /home directory and most disk space devoted to the '/' root disk directory.

==== Step 3: Set Host Name & Enable DHCP ====

Set the system host name to "quantastor" or something suitable for your environment. Next, enable at least one network port so that when the system boots it can get an initial IP address via DHCP.

* NOTE: We recommend changing all ports to static IPs after these installation steps are completed. Ports may be easily configured via the QuantaStor web management interface.

==== Step 4: Set "root" Password ====

Press "Begin Installation" to get the the next installation page where you'll be able to set the "root" user password. Set the root password to a strong password and be sure to save it in a safe place. The root user password may be needed in the future if there are network connectivity or other maintenance issues that require login via SSH or via the IPMI/iDRAC/iLO base board controller console interface. Besides special case maintenance steps (such as this install procedure) one will generally not need to login to the console/SSH. The default "admin" QuantaStor management account for managing the system is separate from the "root" user low level Linux account.

==== Step 5: Login as "root" ====

After the OS installation completes the system will reboot and you'll be presented with the login prompt. Login as the "root" user so that you can License your RHEL install with the redhat repoository servers and run the QuantaStor installation script.

Typically you will add a RHEL subscription using 'subscription-manager register' and 'subscription-manager attach' from the command line.

Full Instructions for registering the RHEL install from the command line are available here:
https://access.redhat.com/documentation/en-us/red_hat_subscription_management/1/html/quick_registration_for_rhel/registering-cmd

Note, that you will need a Full RHEL Server License and HA Addon License. The reduced Self-service Server license is not supported.

==== Step 6 (Optional): Install The Mellanox OFED for RDMA/NVMEoF and best Mellanox Performance ====

For customers with Mellanox Network Cards. The latest Mellanox Driver stack is required for advanced features such as connecting to NVMEoF devices over RDMA or to get the best performance out of 100GbE/200GbE network devices.

This can be installed using the below script:
<pre>
curl -o ./mellanox-ofed-install.sh http://packages.osnexus.com/packages-redhat/mellanox-ofed-install.sh
chmod 755 mellanox-ofed-install.sh
./mellanox-ofed-install.sh
</pre>

==== Step 7: Install QuantaStor via Script ====

Now that RHEL is installed and Licensed the QuantaStor installation script can be downloaded an run:

<pre>
curl -o ./qs_upgrade_redhat8.sh http://packages.osnexus.com/packages-redhat/qs_upgrade_redhat8.sh
chmod 755 qs_upgrade_redhat8.sh
./qs_upgrade_redhat8.sh installall
</pre>

==== Step 8: Login via Web UI ====

Once all the stages of the installation script have completed you'll be able to login to the QuantaStor web management interface as "admin" using the default password which is "password". The QuantaStor web management interface is accessible via HTTPS using any browser. Simply input the IP address of the QuantaStor server that it acquired via DHCP.

Note: Run this command to get the IP address of the system if you don't have it and are logged in via a console:

<pre>
ip addr
</pre>

==== Step 9: Basic Installation Complete ====

At this point installation is complete but we recommend rebooting/power cycling the system to make sure everything is correct from a boot media and BIOS configuration perspective.

* NOTE: If you have external JBODs we recommend running the above installation steps without those attached to make it faster and easier. Once the above steps are complete, simply shutdown the system, attach the JBODs, and boot.

==== Step 10: Apply QuantaStor License Key ====

After logging in to the QuantaStor web user interface (WUI) for the first time be sure to add your license key. If you don't have a commercial use license key you can get temporary Trial Edition licenses via the [https://osnexus.com/trynow Try Now] page. OSNEXUS non-commercial use Community Edition licenses are available via the same page.

== Starting the Installation from QuantaStor ISO/USB media ==
[[File:Rufus_screen_shot.png|thumb|300px|Preparing USB ISO media for QuantaStor install|link=QuantaStor_Installation_via_USB_Thumb_Drive]]
==== Step 1: Preparing the ISO/USB media ====
For bare-metal installation we recommend using a 8GB or larger USB stick. Once you've downloaded the ISO file from the OSNEXUS web site you can put it onto your USB device using software like [https://sourceforge.net/projects/usbwriter/ usbwriter]. Another option is to burn a DVD and use a portable USB DVD device to install from. Detailed instructions on [[QuantaStor Installation via USB Thumb Drive|how to put QuantaStor on to USB media]] is provided [[QuantaStor Installation via USB Thumb Drive|here]] for both Windows and Linux.

==== Step 2: Insert and Boot from the QuantaStor USB Install Media ====
After connecting your QuantaStor Install USB stick to the server you will see the QuantaStor screen appear and it will automatically select 'English' as the default language and begin the installation process.

==== Step 3: Selecting a hostname ====
The first question you will be asked as part of the installation process is what do you want to name the host. By default the name 'quantastor' is given, but you can give the system any valid host name. If you're setting up multiple systems you should give them each unique names. You can also change the name later through the web management interface using the Storage System Modify dialog.

==== Step 4: Selecting a network port ====
The second step in the console level installation process is the selection of which port to use for network communication during the install process. If the new QuantaStor system has a single network interface then it will automatically attempt to configure the using DHCP; if DHCP is not available then standard details will need to be provided (Static IP Address, Subnetmask, and gateway if applicable). If multiple ports are detected a menu will be provided allowing you to choose which interface to use for the management port. The installation process will use the network to try to get more recent versions of packages than those that are on the CD.

==== Step 5: Selecting the device to install the QuantaStor OS ====
Finally, the configuration wizard will ask which partitioning scheme to use. We recommend 'Guided installation, use entire disk'. If you are planning to mirror your boot drive (highly recommended) then you'll want to use the Hardware RAID controller's configuration BIOS to create a RAID1 logical drive first. The next screen will ask you which disk you want to use as the system boot disk, at that point you'll select your RAID1 mirrored system/boot drive.

<pre>WARNING, this disk will be reformatted as part of the installation process so be
careful to choose a disk that does not have data on it you need.</pre>

==== Step 6: Bare-metal Installation is Complete ====
That's all the key questions you will be asked as part of the installation process. After the installation completes the system will reboot and will start-up the QuantaStor system. At this point you can login using the 'qadmin' user account and 'qadmin' password so that you can get the IP address of the system. To get the IP address just type 'ifconfig' at the command prompt after you have logged in. You'll see an entry for 'eth0' with an IP address assigned to it. Enter that IP address into your web browser to connect to your QuantaStor storage system via your favorite web browser so that you can start to configure the rest of the system.

A video of the installation process is available on the main web site in the [http://www.osnexus.com/videos/ Videos] section.

QuantaStor Version ChangeLog

2025-10-10T07:27:59Z

Joshua.blake: /* v6.6.0.362 (October 9th 2025) */

[[index.php?title=Category:Support guide]]
= Change Log Overview =
The change log contains a detailed summary of the changes made for each new release of QuantaStor. Each change made to QuantaStor is tracked with an engineering ticket number in the form '''[QSTOR-NNNN]'''. This information is provided so that if you're working with OSNexus support you can track the availability of a given product feature add, improvement, or maintenance fix to a specific release. For information on how to upgrade your storage system please see the [[QuantaStor Upgrade Guide|Upgrade Guide]].

== Versioning System ==
QuantaStor version numbers consist of four (4) parts. A major number (M), minor number (N), maintenance update number (U) and build number (B) of the form M.N.U.B such as 6.0.2.006.

QuantaStor upgrades go directly from whatever version you are running to the latest version, with no interim steps so for example if you are at v6.0.1 you will upgrade directly to the latest version which may be v6.1.2

== Product Update Types ==

==== Major Updates (X.y.z) ====
If the first digit in the version number has changed this indicates a major product release such as QuantaStor v5 to QuantaStor v6. Major releases generally come with a new underlying Linux platform as the basis. For example, the standard ISO install for QuantaStor v5 is based on Ubuntu 18.04 whereas QuantaStor v6 is based on Ubuntu 20.04. Major product releases generally include new features and maintenance updates and are supported on multiple underlying Linux platforms. For example, QuantaStor v6 is available as an upgrade on Ubuntu 18.04 and Ubuntu 20.04 based systems as well as RHEL and RHEL derivative platforms. Platform upgrades to move systems forward (eg 18.04 to 20.04) are made generally available in the first feature update release, such as QuantaStor 6.1.

==== Feature Updates (x.Y.z) ====
If the second digit in the version number has changed this indicates a feature release such as 6.'''1''' going to 6.'''2'''. Feature releases add new product features as well as a maintenance updates. No additional licensing is required to access any new features that added but note that QuantaStor licenses do not include licenses for 3rd party products and services that may integrate with QuantaStor.

==== Maintenance Updates (x.y.Z) ====
If the third digit of the version number has changed this such as 6.0.'''2''' or 6.0.'''3''' it represents a maintenance update to address one or more support tickets. These updates generally do not contain new features, only fixes to address specific issues. Maintenance releases generally ship every 4 to 8 weeks. All maintenance "aka hot-fix" releases are provided against the current stable release so upgrading to the latest QuantaStor version is generally required to apply them.

==== Build Number (x.y.z.BBB) ====
The build number and corresponding build reference hash can be largely ignored. The build number simply increments with each commit that is made to the source tree. The hash is provided to make it easier for OSNEXUS support and engineering to quickly confirm difference between your current running release and any more modern release.

== Boot Install Image and other downloads ==
=== ISO/DVD/USB Boot Install Image ===

* The latest version of QuantaStor can be found on our [https://downloads.osnexus.com downloads page here].

* [[QuantaStor Installation via USB Thumb Drive|Bootable Flash Drive instructions.]]

NOTE: Archived older versions of QuantaStor ISO install media and CLI tools can be found [https://downloads.osnexus.com.s3.us-east-1.amazonaws.com/list.html here].

= Recent Change Logs =

== v6.6.0.362 (October 9th 2025) ==

=== [[QuantaStor 6.6.0 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.6.0 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.6.0 Upgrade Instructions| upgrading to QuantaStor v6.6.0]].

=== Release Notes ===

Ceph Scale-out Block, Object and File
* Block rename of object pool group. [ QSTOR-11336 ]
* Add a fix so auto-tier rules can be set on multiple ceph clusters [ QSTOR-11323 ]
* Fixes bug with OSD replace prepare context menu button when called from the enclosure view. [ QSTOR-11313 ]
* Fixed: added duplicate zone check for Object Group Create [ QSTOR-11266 ]
* Add indication on the journal group if it is encrypted. [ QSTOR-11261 ]
* Updated Ceph version on Focal and Jammy platforms to 18.2.7 [ QSTOR-11129 ]
* Generate proper caps for keyring when using additional pools in CephFS [ QSTOR-11106 ]
* Display S3 user information in the delete user dialog to distinguish between S3 user and local user. [ QSTOR-10723 ]
* New feature adds the ability to modify RGW settings. Added the ability to add and remove load balancers on each Ceph cluster member. [ QSTOR-10623 ]
* Added support for Portal Groups for FC and iSCSI Targets [ QSTOR-10533 ]
* Add the ability to control synchronization for selected buckets in two objects storage clusters. [ QSTOR-10346 ]
* Add ability to specify multiple pools in a ceph file system. [ QSTOR-8674 ]

Dashboards and Analytics
* Add a new bucket dashboard that reports Average Total Objects and Average Utilized Space. [ QSTOR-11259 ]

Disk Management
* Adds an NVMe quick format to the Physical Disk Format dialog using the secure erase options. [ QSTOR-10688 ]

Enclosures and Controllers
* Fixed various items related to Linux Software RAID adapter support. [ QSTOR-11198 ]

Multitenancy
* Scope the access of user accounts so that they can only manage users, buckets, keys and other resources related to the tenant in the resource group they're a member of [ QSTOR-11326 ]
* Allow CephFS shares to be added to a Resource Group. [ QSTOR-11007 ]

Network Shares
* Share rename needs a force flag as it may disconnect NFS clients. [ QSTOR-11337 ]
* Provides an optional backported version of samba via a 'qs_samba_jammy_optional.sh' install script that includes a version of samba required to address the ad rfc2307 changes Microsoft introduced in KB5062572. Note this samba version does not include sssd support and so will not be installed by default. It should only be used for those customers using ad rfc2307 mode. [ QSTOR-11319 ]

Security
* Adds the ability to add and remove SSL certificate templates. Using those templates you can update the certificates for HaProxy and Rados gateways configured for HTTPS. [ QSTOR-9016 ]

Service Core
* Eliminates common errors in active directory join process, prepopulating dialog from previously joined systems [ QSTOR-11015 ]
* Added support for shutting down or restarting multiple systems at once [ QSTOR-10022 ]

Storage Volumes
* Allow rename of Scale Out block storage volumes [ QSTOR-11311 ]
* Fix an event issue where the Volumes count was not getting updated in the central Host grid view. [ QSTOR-11038 ]

Universal Containers
* Add Universal Container support to the server and the Create Config dialog in the WUI. [ QSTOR-11194 ]

Upgrade Manager and Installer
* verified that packages are being installed properly with the new iso filtering stuff [ QSTOR-11030 ]

Web Manager
* Minor fix to the modify Network Port dialog. [ QSTOR-11302 ]
* Added the ability to save a local copy of a report schedule. [ QSTOR-11217 ]
* Simplifies active directory join and leave process, allowing multiple systems to join or leave at once [ QSTOR-8771 ]

== v6.5.12.005 (September 22nd 2025) ==

=== [[QuantaStor 6.5.12 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.5.12 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.5.12 Upgrade Instructions| upgrading to QuantaStor v6.5.12]].

=== Release Notes ===

Enclosures and Controllers
* Fixed vendor/model defaulting, improved enclosure layout auto-selection in the Modify Storage System dialog (including correct child-layout selection to choose the primary NVMe drive group), and resolved an invalid enclosureLayoutId that prevented layout auto-detection. [ QSTOR-11263 ]

Security
* Fixed: disable gzip compresson on web and api ports by default. [ QSTOR-11210 ]
* Fixed: internal qs-statsd/qs_restd service port 5173 moved to localhost only as it should not be presented as an external port. [ QSTOR-11210 ]
* Fixed: reduced syslog logging of qs-statsdb/qs_restd. [ QSTOR-11210 ]
* Added: DROP rules to block ICMP timechecks [ QSTOR-11210 ]
* Updated SSL Ciphers and TLS1.3 support for the web and API ports [ QSTOR-11210 ]
* Fixed: Set pcsd api port 2224 to bind to localhost only by default [ QSTOR-11210 ]

== v6.5.11.029 (August 28th 2025) ==

=== [[QuantaStor 6.5.11 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.5.11 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.5.11 Upgrade Instructions| upgrading to QuantaStor v6.5.11]].

=== Release Notes ===

Alerts and Configuration Analysis
* Added support for SMTP servers that allow open relay with no username/password to the Alert Manager [ QSTOR-11167 ]

Ceph Scale-out Block, Object and File
* Fixed an issue with multiple alerts occurring for long running OSD replace prepare tasks. [ QSTOR-11276 ]
* Fixed some corner case issues with long running OSD replace prepare tasks. [ QSTOR-11276 ]
* Added support for larger MDB devices upto 2100GB [ QSTOR-11274 ]
* Added support for encryption bypass on OSD create while still encrypting wal/db journal devices. [ QSTOR-11260 ]

Disk Management
* Fixed an issue with running the disk read performance test benchmark on very fast modern media. [ QSTOR-11296 ]

Enclosures and Controllers
* Fixed Enclosure and Controller discovery support for SAS3516 based SAS controllers [ QSTOR-11267 ]

High Availability Failover
* Fix an issue with VIF used for scale-out file usage after rebooting all nodes in the cluster. [ QSTOR-11265 ]

Network Interfaces
* Fixed: added gfortran-11 dependency to jammy repository required for LTS mellanox ofed install to succeed [ QSTOR-11285 ]
* Add QS cli command to hide disabled Network Ports [ QSTOR-10898 ]
* Fixed an issue where VLAN and VIF interfaces would not report their bond mode correctly if their parent interfaces was a bonded port. [ QSTOR-10754 ]

Network Shares
* Adds support for multiple HA VIF redirects and smart network filtering for NFSv4 referrals [ QSTOR-11278 ]
* Minor fix to skip NFS export commands for scale out shares. [ QSTOR-11275 ]

Quantastor CLI
* Provide a utility to create temporary log download links via qs-download-link [ QSTOR-11273 ]

SCSI / NVMe Target
* Fixed: Added logic to always default FC ports to target mode for supported FC target card models from QLogic. Ports can still be explicitly set to initiator mode if the user so chooses. [ QSTOR-10744 ]

Service Core
* Fixed: added the option to cancel the Physical Disk Identify task if the duration for the identify task is longer than the user wants. [ QSTOR-11258 ]
* Provide a download link for log collection in case logs cannot be uploaded from a Quantastor system [ QSTOR-11116 ]

Upgrade Manager and Installer
* Fixed: added proxy settings to the /etc/apt/apt.conf.d/80proxy file [ QSTOR-11281 ]
* Fixed: added logic to the upgrade manager and qs-upgrade command to check for missing version pinning if qs-util aptnopin has been run on the system. The upgrade task will fail early if correct pinning is not in place advising running qs-util aptpin. [ QSTOR-11277 ]

Web Manager
* Fixed: clarified text in create resource group for network share access of service containers [ QSTOR-11187 ]

== v6.5.10.013 (August 12th 2025) ==

=== [[QuantaStor 6.5.10 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.5.10 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.5.10 Upgrade Instructions| upgrading to QuantaStor v6.5.10]].

=== Release Notes ===

Ceph Scale-out Block, Object and File
* Fixed an issue where the access key and secret key were not updating in the UI in instances with multiple object storage users across multiple ceph clusters in the same grid. [ QSTOR-11254 ]
* Fixed an issue with the cephfs mounts if communication is lost with the active MDS and a new MDS is elected. [ QSTOR-10738 ]

Enclosures and Controllers
* Fix an enclosure refresh issue via the event path where the underlying disk were not getting refreshed. [ QSTOR-11247 ]
* Fixed: Added additional checks for enclosure id on enclosures that fail to report correctly on older firmwares. [ QSTOR-11227 ]

Service Core
* Fixed: replaced size with maxsize in the ceph, radosgw and haproxy logrotate definitions so that they rotate as expected on their daily rotations as well as when reaching the max size definition. [ QSTOR-11253 ]
* Fix an underlying dashboard issue where new diskio entries were not properly added to the telegraf.conf file on new deployments. [ QSTOR-11246 ]
* Fix: Optimize the restarting of influx and telegraf. [ QSTOR-11246 ]

== v6.5.9.003 (August 5th 2025) ==

=== [[QuantaStor 6.5.9 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.5.9 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.5.9 Upgrade Instructions| upgrading to QuantaStor v6.5.9]].

=== Release Notes ===

Enclosures and Controllers
* Fixed an issue with slotmap updates when changing the slotmap in the enclosure and controllers section. [ QSTOR-11245 ]

Service Core
* Fixed an issue where QuantaStor was restarting the influxdb service when it was not needed. [ QSTOR-11244 ]
* Fixed: separated the influxdb, telegrafd and QuantaStor stats_db service restart logic to allow more granular control. [ QSTOR-11244 ]

== v6.5.8.008 (July 31st 2025) ==

=== [[QuantaStor 6.5.8 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.5.8 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.5.8 Upgrade Instructions| upgrading to QuantaStor v6.5.8]].

=== Release Notes ===

Ceph Scale-out Block, Object and File
* Fixed a small issue with the ceph osd reweight script progress trace. [ QSTOR-11234 ]

Enclosures and Controllers
* Add support for Supermicro ASG-2115S-NE332R system enclosure layouts [ QSTOR-11237 ]

Network Shares
* Fixed: Disable security features options in Network Share Create/Modify dialogs when the share is from a Scale-out File Pool. [ QSTOR-11235 ]
* Fixed: Remove redundant "NFS Security Mode" on the share advanced tab. [ QSTOR-11235 ]
* Fixed an issue with clearing the manage gids setting on Jammy platforms [ QSTOR-11225 ]
* Fixed an issue with setting specific nfs v3 or v4 server configurations on Focal platforms [ QSTOR-11225 ]
* Fixed a conflict with the nfs mountd ports between scale-out and scale-up nfs modes. [ QSTOR-11212 ]
* Fixed detection of nfs scale-out mode when it is configured at the time of ceph scale-out filesystem creation. [ QSTOR-11212 ]

Upgrade Manager and Installer
* Added a check to disable the grub os prober by default to prevent adding of any block devices with OS data other than the installed QuantaStor OS disk to the grub boot loader. [ QSTOR-11199 ]

== v6.5.7.004 (July 24th 2025) ==

=== [[QuantaStor 6.5.7 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.5.7 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.5.7 Upgrade Instructions| upgrading to QuantaStor v6.5.7]].

=== Release Notes ===

Network Shares
* Fixed an issue with network share cifs/smb settings such as ignore system acls introduced in the 6.5.1 release. [ QSTOR-11224 ]
* Removed the API underscore to space conversion logic in cifs/smb settings introduced in 6.5.1. REST API's should use proper url encoding like %20 when sending strings that contain spaces via curl or other http calls. [ QSTOR-11224 ]

Storage Pool Management
* Fixed a path naming issue for the sedutil-cli binaries used for SED disk encryption. [ QSTOR-11221 ]
* Added Several small enhancements and fixes for the sedutil-cli tool usage and SED supported disk discovery [ QSTOR-11219 ]

== v6.5.6.052 (July 16th 2025) ==

=== [[QuantaStor 6.5.6 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.5.6 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.5.6 Upgrade Instructions| upgrading to QuantaStor v6.5.6]].

=== Release Notes ===

Alerts and Configuration Analysis
* Fix minor issue with Corvault log collection. [ QSTOR-11201 ]
* Added alerts to notify the user as they approach quota limits for S3C buckets [ QSTOR-11055 ]
* Fixed an issue with the IPMI Ip addresses showing up in the Health Check reports. [ QSTOR-10356 ]

Ceph Scale-out Block, Object and File
* Fixed radosgw logging logrotation not always occurring on fresh installs. [ QSTOR-11176 ]
* Fixed: radosgw logging now defaults to rotating at 100MB [ QSTOR-11176 ]
* Fixed: haproxy logging now defaults to rotating at 100MB [ QSTOR-11176 ]
* Improved logic for Ceph OSD Gentle Reweight. [ QSTOR-11163 ]
* Fixed an issue with the version check when upgrading the the scale-out ceph MDS, RGW and other daemons. [ QSTOR-11138 ]
* Fixed a few corner cases with ensuring successful Ceph upgrades. [ QSTOR-11138 ]
* Allow compression support for Ceph RBD pools. [ QSTOR-11131 ]
* Added Object User quota usage information to the Object User grid [ QSTOR-10722 ]

Dashboards and Analytics
* Add Pool, volume and share space usage trending dashboards (Early Access). [ QSTOR-11076 ]
* Add Pool, volume and share space usage trending dashboard routes and toggle buttons. [ QSTOR-11076 ]
* Expand the trending time scale for Tenants and Owners to make use of longer retention policies (e.g. 'Last 30 Days'). [ QSTOR-11076 ]
* Fix InfluxDB trending continuous query settings in qs\_statsdb.sh. [ QSTOR-11076 ]

Disk Management
* Add Multipath and HA support for SED Disks. [ QSTOR-11172 ]
* Added Hardware Encryption Storage Pool create support for Seagate ST20000NM000D Enterprise SED drives. [ QSTOR-11065 ]

Enclosures and Controllers
* Fixes intermittent boot time OSD start issue with Corvault media. [ QSTOR-11195 ]
* Adds encryption bypass mode to avoid applying double (hardware plus software) encryption to Corvault media. [ QSTOR-11195 ]
* Added enclosure layout for Supermicro SYS-221H-TN24R systems. [ QSTOR-11154 ]

High Availability Failover
* Fixed an issue with Storage pool import of a previously exported pool that has iofencing on nvme disks. [ QSTOR-11173 ]

Network Shares
* Add new cyphers for active directory join. [ QSTOR-11183 ]
* Added sync flag by default to NFS mount for ceph object storage ganesha shares [ QSTOR-11181 ]
* Adjust minor Network Share quota alert levels. [ QSTOR-11171 ]
* Add larger record size upto 8M for Network Shares on ZFS Storage Pools. [ QSTOR-10118 ]
* Added support for hidden shares that end in a '$' as 'Browseable (admin-only) shares in the CIFS/SMB Options tab of the Network Share Create/Modify Dialogs. [ QSTOR-9222 ]

Service Core
* Optimize database reads for large clusters. [ QSTOR-11178 ]
* Added qs-util dbdiff for use to compare osn.db database versions [ QSTOR-10566 ]
* Added https as the default preferred method for support log bundle upload. [ QSTOR-9875 ]

Universal Containers
* Added initial support for a universal container system [ QSTOR-11162 ]

Upgrade Manager and Installer
* Added logic to fix the /boot/efi based on a efi partition label for Software RAID and EFI installs [ QSTOR-11140 ]

Web Manager
* Revise the Object User Access Key Manager to include Storage URLs in the Copy to Clipboard action. [ QSTOR-11177 ]
* Improved fieldset placements for network share create/modify dialogs. [ QSTOR-11156 ]
* SED Pool management - Reorder SED columns in PD grid. Move to the right of the "Correlated Device" column. Revise the SED capability detection to check for non-enterprise. [ QSTOR-11146 ]

== v6.5.5.039 (May 29th 2025) ==

=== [[QuantaStor 6.5.5 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.5.5 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.5.5 Upgrade Instructions| upgrading to QuantaStor v6.5.5]].

=== Release Notes ===

Ceph Scale-out Block, Object and File
* Fixes bug in osd gentle reweight script that was bottlenecking performance. [ QSTOR-11123 ]
* Added logic to auto-clean up volume objects for non-QuantaStor managed ceph rbd's (rbd's created directly by the client using client rbd drivers/software). [ QSTOR-11112 ]
* Add warnings for the user if OSD or journal delete is being used on a device with duplicate PVs due to multi-pathing mapping. [ QSTOR-11099 ]
* Added 'qs-ceph' utility commands to modify compression options on Ceph pools. [ QSTOR-11096 ]
* Added compression ratio column in storage pools grid. [ QSTOR-11087 ]

Enclosures and Controllers
* Added support for discovery of RMSP3JD160J controllers. [ QSTOR-11107 ]
* Add validation for both primary and secondary IPs during External System Credentials Add. [ QSTOR-11009 ]

High Availability Failover
* Fixed a very rare corner case where a Manual HA failover task could generate unexpected errors due to a background periodic storage pool scan. [ QSTOR-11111 ]
* Added the option to set a Site Cluster Member Node as Manual Standby. [ QSTOR-11105 ]
* Fixed an issue where nodes could come out of standby status on a reboot too early before grid communication was established. [ QSTOR-11105 ]
* Enhanced HA Failover times for Storage Volumes for Fibre Channel clients. [ QSTOR-11105 ]
* Enhanced Fiber Channel High availability ALUA Changes to occur more quickly and to more quickly advertise failed paths to clients like VMware so that they can resume I/O to healthy available paths sooner. [ QSTOR-11105 ]
* Enhanced the logic used for High Availability Storage SCSI Target decoupling during a Storage Pool export. This can help greatly reduce the failover time for very Large configurations with thousands of volumes or volume snapshots. [ QSTOR-10969 ]

Network Interfaces
* Fixes bug that was blocking users from creating a static route with the same destination subnet across different systems. [ QSTOR-11125 ]
* Fixed a bug in static route validation logic and allow users to delete malformed static route entries. [ QSTOR-11115 ]

Network Shares
* Allow rename of nested shares [ QSTOR-11046 ]
* Added logic to help persist and manage NFS options for NFS version and nfs --manage-gids flags [ QSTOR-11001 ]

REST API
* Add an API to clear missing shares or volumes from the QS database. [ QSTOR-11117 ]

Remote Replication, Snapshots and Backup Policies
* Clarify concurrency options for backup policies. [ QSTOR-11004 ]

Security
* Added explicit modprobe disable and blacklist of ksmbd module to address any CVE-2025-37899 concerns. [ QSTOR-11134 ]

Service Core
* Enhanced the Core QuantaStor service management thread scaling. [ QSTOR-10767 ]
* Fixed a small memory leak with debug log tracing [ QSTOR-10689 ]

Storage Pool Management
* Updated sedutil-cli that supports a wider range of encrypted devices. [ QSTOR-11088 ]
* Restores sedutil / Storage Pool encryption support for SED Ruby NVMe devices. [ QSTOR-11088 ]
* Removed restriction to satisfy the VDEV count of N+1 to create a RAIDZx(RAID50/60/etc) array on a ZFS scale-up Storage pool when passing in a Set Disk Size instead of using the 'auto' option. [ QSTOR-11086 ]

== v6.5.4.016 (April 29th 2025) ==

=== [[QuantaStor 6.5.4 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.5.4 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.5.4 Upgrade Instructions| upgrading to QuantaStor v6.5.4]].

=== Release Notes ===

Dashboards and Analytics
* Fix issue where the dashboard of a newly created volume was not showing performance data after it had been assigned because of a pending Telegraf restart required. [ QSTOR-11077 ]
* Show CPU Temp and Power Usage in the System Dashboard (new Sensors button). [ QSTOR-11029 ]

High Availability Failover
* Unblocked creating HA ViF if there is an HA irrelavant bond in active-backup mode and unblocked modifying an HA irrelavant bond. [ QSTOR-11073 ]
* Fixed an issue when modifying non-name fields of an HA group. [ QSTOR-11071 ]

Network Interfaces
* Fixed bugs in validation logic for static route create and delete. [ QSTOR-11056 ]

Network Shares
* Ensure 'Browseable' is checked on SMB network shares when Browseable (Access Based) is checked. This ensures that authenticated clients who have pre-assigned browseable access can see the share offered by the QuantaStor but prevents non-authenticated users from seeing the share. [ QSTOR-11078 ]

Remote Replication, Snapshots and Backup Policies
* Minor log file cleanup after backup job is finished. [ QSTOR-11044 ]
* Add the ability to rollback a read-write Storage Volume or Network Share snapshot to it's underlying snapshot. [ QSTOR-9820 ]

Storage Pool Management
* Fixed an issue with Storage Pool auto-start on reboot for software encrypted storage pools. [ QSTOR-11081 ]

== v6.5.3.021 (April 9th 2025) ==

=== [[QuantaStor 6.5.3 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.5.3 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.5.3 Upgrade Instructions| upgrading to QuantaStor v6.5.3]].
=== Release Notes ===

Ceph Scale-out Block, Object and File
* Improved timeout handling for QuantaStor coordinated task system. [ QSTOR-11022 ]

Disk Management
* Added Hardware Encryption Storage Pool create support for Seagate ST20000NM000D Enterprise SED drives. [ QSTOR-11032 ]

Enclosures and Controllers
* Added Hardware Enclosure support for Dell PowerEdge R7615 [ QSTOR-11043 ]
* Added Hardware Enclosure support for Supermicro AS-1115CS-TNR [ QSTOR-11043 ]
* Optimized performance and fixed issues when rendering systems with attached CORVAULT external systems. [ QSTOR-11039 ]
* Optimize the rendering of enclosures. Fix drawer rendering issue where extra slots were appearing. [ QSTOR-11014 ]

Network Interfaces
* Fixed an issue with static route netmask CIDR calculations. [ QSTOR-11048 ]

Network Shares
* Update Network Share Namespace on all nodes to reflect any modification to NFS access entries to share that is part of a Namespace. [ QSTOR-11042 ]
* Online newly promoted Network Share Snapshots. [ QSTOR-11021 ]
* Add post share create and modify script callouts. [ QSTOR-11016 ]
* Fixed mount paths for enabled snapshots of Network Share when Share is renamed. [ QSTOR-11012 ]
* Add the ability to prioritize NFS access rules in /etc/exports file. [ QSTOR-10552 ]

SNMP
* Regen SNMP for 6.5.3 [ QSTOR-11054 ]

Security
* Added docker http proxy override [ QSTOR-11040 ]
* Updated Tomcat version to 9.0.102.0 [ QSTOR-11013 ]

Upgrade Manager and Installer
* Fixed various issues with the OVA vApp properties being set after VM image cloning. Added additional properties to the OVA by default. [ QSTOR-10508 ]

== v6.5.2.070 (March 27th 2025) ==

=== [[QuantaStor 6.5.2 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.5.2 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.5.2 Upgrade Instructions| upgrading to QuantaStor v6.5.2]].
=== Release Notes ===

Alerts and Configuration Analysis
* Added SED version of Micron 7300 drives to firmware check for Config Analyzer [ QSTOR-10933 ]

Ceph Scale-out Block, Object and File
* Update AWS cli. [ QSTOR-10956 ]
* Extend Resource Groups to support adding S3 Tenant resource type. [ QSTOR-10808 ]
* Extended timeouts for logical volume allocation commands when creating Ceph OSDs. [ QSTOR-10930 ]
* Added more permissive check when running Ceph OSD replace prepare operation. (CLI only) [ QSTOR-10914 ]
* Add a qs-ceph command to allow switching between fuse and kernel mount for cephFS to allow user comparison of fuse versus the faster kernel option. [ QSTOR-10905 ]
* Adds additional Ceph coordinator election mode that maps to the site-cluster. [ QSTOR-10795 ]

Dashboards and Analytics
* Added Jammy platform support for the ceph prometheus install script [ QSTOR-10949 ]

Enclosures and Controllers
* Strip whitespace characters from primary and secondary IPs during External System Credentials Add. [ QSTOR-10896 ]
* Add validation for External System Credentials during creation. [ QSTOR-10826 ]

High Availability Failover
* Fixed a bug with creation grid master (gm) Site Cluster vifs. [ QSTOR-10996 ]
* Implemented new naming schema for underlying Site Cluster HA Groups. [ QSTOR-10904 ]

Network Interfaces
* Fixed an issue with deleting bonded interfaces leaving slave interfaces tagged as slaves. [ QSTOR-10931 ]
* Updates for mellanox ofed lossless networking support to work better with newer model cards. [ QSTOR-10779 ]

Network Shares
* Fixes bug where having 'gmt' or 'GMT' in the name of a network share would cause issues with NFS protocol. [ QSTOR-10982 ]
* Fix the mount paths for read-write GMT snapshots. [ QSTOR-10938 ]
* Add mountaddr to the view mount instructions for Network Share. [ QSTOR-10923 ]
* Add crossmnt option in the NFS exports for newly created shares. Also skip adding the default export for .zfs directory. [ QSTOR-10806 ]
* Add the ability to clone a GMT snapshot and promote it.
Add QS CLI to copy share permissions. [ QSTOR-10580 ]

REST API
* Handle empty lists from the curl calls to Quantastor APIs. [ QSTOR-10939 ]

Remote Replication, Snapshots and Backup Policies
* Fixed up dead links which were created after running some types of auto-tier Backup Policies. [ QSTOR-10934 ]

SNMP
* Update SNMP MIB [ QSTOR-11019 ]

Security
* Prevent MFA passcodes with leading 0 from being truncated. [ QSTOR-10852 ]

Service Core
* Fixes an issue where role-creation would fail due to deprecated permission-definitions. [ QSTOR-10988 ]

Storage Pool Management
* Added support for the creation of mirror sets consisting of "quad-mirrors" (4-way mirror sets) for both the data device groups in the pool and also the "special" devices, such as "dedup" and "metadata offload" devices. [ QSTOR-10893 ]

Storage Volumes
* Add more detail for logical and physical space utilization for volumes. [ QSTOR-10981 ]

Upgrade Manager and Installer
* Deprecates legacy package version pinning for the packages.osnexus.com mirror server that was causing issues with some ceph cluster upgrades [ QSTOR-10990 ]
* Added protections in qs\_distupgrade.sh for lvm snapshots that could cause issues with the platform upgrade. [ QSTOR-10970 ]
* Resolved multiple items that were causing issues with installing QuantaStor on redhat based platforms when STIG enforcement policies were present. [ QSTOR-10958 ]
Note: the qs_upgrade_redhat8.sh install/upgrade script temporarily sets selinux to permissive mode and temporarily disables fapolicyd if it is enabled when the script is running and restores them to their original state when the script completes.

Web Manager
* Auto select S3 tenant for S3 User when user create is invoked from context menu on the S3 tenant. [ QSTOR-11010 ]
* Increase the width of grids to show the 'Correlated Device' column in the Add Log/Cache/Metadata Device to Pool dialog w/o the need for scrolling. [ QSTOR-10951 ]
* Add an option to upload logs with no truncation. [ QSTOR-10925 ]
* Add drawer support for the Corvault enclosure layout and rendering engine in the WUI. [ QSTOR-10796 ]

== v6.5.1.058 (February 12th 2025) ==

=== [[QuantaStor 6.5.1 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.5.1 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.5.1 Upgrade Instructions| upgrading to QuantaStor v6.5.1]].
=== Release Notes ===

Ceph Scale-out Block, Object and File
* General improvements to OSD drive replacement process. Added additional LVM clean up logic. Fixed issues with device correlation for multipath devices and encrypted drives. [ QSTOR-10915 ]
* Allow deleting journals from the UI via Ceph journal delete dialog [ QSTOR-10890 ]

Dashboards and Analytics
* Add gridPreferredPort check to the WUI dashboard service (qsrestd) if set on a Storage System. [ QSTOR-10866 ]

Disk Management
* Fixed: New systems and clean QuantaStor service configurations databases will initialize Multipath autoconfig support as enabled by default. [ QSTOR-10900 ]
* Increased timeouts and other optimizations for large multipath configurations. [ QSTOR-10881 ]
* Added protections to prevent QuantaStor service from running multiple blkid instances if one is already running. [ QSTOR-10881 ]
* Unblocked adding disk as a scale-up pool spare with a larger block size. [ QSTOR-10876 ]

Enclosures and Controllers
* Add Enclosure mapping support for HPE ProLiant DL325 Gen10. [ QSTOR-10899 ]
* Fixed an issue with Hardware Disk Identify for Storage Pool Physical Disks where the controller was not properly selected in the dialog. [ QSTOR-10858 ]
* Fixed an issue with applying External System Profile A+B. [ QSTOR-10840 ]

High Availability Failover
* Fixed an issue with automatically starting HA scale-up ZFS pools if both HA nodes are booted at the same time. [ QSTOR-10902 ]
* Added a a check to ensure the luks crypttab was upto date after encrypted ha pool failover. [ QSTOR-10901 ]
* Added VLAN interfaces to allowed interfaces for Site Cluster heartbeat rings. [ QSTOR-10871 ]
* Added better logic for smb/nfs service management for Scale-up HA configurations with shares on multiple storage pools in the same HA cluster. [ QSTOR-10762 ]
* Fixed an issue with Resource Group Service configs starting on a node after the node had previously hosted the service. [ QSTOR-10762 ]
* Fixed: added a unique name check for HA group create/modify. [ QSTOR-10311 ]

NAS Gateway / Cloud Containers
* Change Seagate Lyve Cloud endpoints [ QSTOR-10868 ]

Network Interfaces
* Fixed an issue with calling iptables commands when distupgrading from older distributions. [ QSTOR-10860 ]

Network Shares
* Minor fix to allow creation of GMT snapshots for volumes from the Web UI. [ QSTOR-10873 ]
* Fixed an issue with spaces in the curl command issued to Quantastor. [ QSTOR-10838 ]
* Fix issue where renaming a share that contained a nested share failed. [ QSTOR-10811 ]
* Allow setting Samba share as read-only using ZFS. The new support has been added to the Network Share create and modify dialogs on the Advanced settings tab. [ QSTOR-10755 ]
* Fixed an issue which created duplicate mounts for nested shares. [ QSTOR-10704 ]
* Exposed ZFS 'Case Sensitivity' option at share creation time. [ QSTOR-8869 ]

REST API
* Fixed the POST command in the REST API [ QSTOR-10844 ]

Remote Replication, Snapshots and Backup Policies
* Fix an issue with auto tiering in backup policies. [ QSTOR-10845 ]
* Refined the Backup Policy Create and Modify dialogs. [ QSTOR-10843 ]
* Fixed an issue with Backup Policy tasks completing when the underlying file copy or move process process had returned. [ QSTOR-10839 ]
* Add alerting when replication fails. [ QSTOR-10799 ]

SNMP
* Updated SNMP MIB [ QSTOR-10922 ]

Service Core
* Fixed an issue that could sometimes cause performing a reboot or shutdown of the storage system via the QuantaStor UI to fail. [ QSTOR-10917 ]
* Fix an issue with database backups on the storage pools. [ QSTOR-10907 ]
* Fixed an issue with creating encrypted pools when an underlying disk is read-only. [ QSTOR-10886 ]
* Fixed a disk discovery issue when discoverying a large number of disks. [ QSTOR-10875 ]
* Fixed QuantaStor service builds for Redhat based distros. [ QSTOR-10846 ]
* Added /var/opt/osnexus/quantastor/touchfiles/tf_sendlogs_ping_check.disable touchfile to bypess the icmp ping check and allow sending logs from the UI/qs cli. [ QSTOR-10556 ]

Storage Pool Management
* Fix an issue with pick a smaller hotspare disk getting picked for metadata offload if disk goes missing. [ QSTOR-10877 ]
* Add storage capacity properties for metadata offload VDEV [ QSTOR-10661 ]

Upgrade Manager and Installer
* Added a blacklist of the bnxt\_re driver to prevent issues for normal network operations for the bnxt_en driver loading on network controllers that have rdma support enabled in their firmware by default. [ QSTOR-10918 ]
* Added elbencho benchmarking tool to quantastor utilities. [ QSTOR-10892 ]
* Added support for Focal 20.04 to Jammy 22.04 Platform upgrades via qs-distupgrade [ QSTOR-10547 ]
* Fix telegraf start failures at startup due to invalid config file errors. [ QSTOR-10353 ]

Web Manager
* Fixed a minor truncation issue with trigger Backup Policy dialog [ QSTOR-10919 ]
* Add a Description column to the share and snapshot grid and default to hidden. [ QSTOR-10882 ]
* Minor fix to NTP server add dialog to prevent empty entries in the dialog. [ QSTOR-10870 ]
* Auto select first row in NTP and DNS settings dialogs. [ QSTOR-10867 ]
* Improve the host assign volume dialog. [ QSTOR-10862 ]

== v6.5.0.246 (January 9th 2025) ==

=== [[QuantaStor 6.5.0 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.5.0 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.5.0 Upgrade Instructions| upgrading to QuantaStor v6.5.0]].
=== Release Notes ===

Alerts and Configuration Analysis
* Increased HA health checks on Systems with local HA Pools. [ QSTOR-10746 ]
* Fixed: sending logs from specific grid nodes will now send logs only from the selected nodes. [ QSTOR-10694 ]

Ceph Scale-out Block, Object and File
* Fixes issue with access permissions for ceph client admin keyring file. [ QSTOR-10818 ]
* Fixed issues related to encrypted OSD replace operations. [ QSTOR-10786 ]
* Fixed an issue with wal journal device discovery and association with osds. [ QSTOR-10751 ]
* Deprecated replica=2 as a creation option from Ceph Scale-out storage. Replica=2 did not provide enough redundancy for consistent normal storage operations in the event of an osd or storage system outage. [ QSTOR-10748 ]
* Added the force flag checkbox to the Create S3 Storage Class dialog. [ QSTOR-10734 ]
* Fixed bugs in Ceph upgrade stage completion and failure alerting. [ QSTOR-10730 ]
* Fixed an OSD discovery issue on large Scale-out configurations. [ QSTOR-10717 ]
* Fixed an OSD discovery issue on large Scale-out configurations. [ QSTOR-10716 ]
* Fixed an OSD discovery issue on large Scale-out configurations. [ QSTOR-10708 ]
* Improve ceph discovery. [ QSTOR-10675 ]
* Add metadata pool utilization for Ceph Object Pool Group and Ceph File System [ QSTOR-10650 ]
* Disabled OSD auto restart. auto restart can be activated using the touchfile '/var/opt/osnexus/quantastor/touchfiles/tf\_ceph\_osd\_auto\_start.enable' [ QSTOR-10632 ]
* Ensure the Tenant and User grid's bucket count column is updated after the delete bucket operation via events. [ QSTOR-10610 ]
* Fixed a bug with Ceph OSD 'Last Rekey Date' field not being updated properly. [ QSTOR-10509 ]
* Updated default Ceph version to Reef 18.2.4 for new Focal and Jammy platform deployments. [ QSTOR-10415 ]

Dashboards and Analytics
* Add a new Ceph Member selection combo to the Ceph Pool dashboard. [ QSTOR-10798 ]
* Add Tenant and Owner usage dashboards to the Bucket menu area. [ QSTOR-10698 ]
* Add CPU Temp and Power Usage to the Grid Dashboard's System Tiles. [ QSTOR-10427 ]
* Change the grid CPU metric to use system\_usage which matches the metric used in the System dashboard. The overlapping text issue is no longer an issue as Highcharts has been replaced with Chart.js. [ QSTOR-10263 ]
* Add power usage and average CPU temp sparklines to the System Tile dashboards in the grid view. [ QSTOR-10013 ]
* Removed resource column from Health Checker/Config Analyzer. [ QSTOR-5515 ]

Disk Management

* Removed the multipath autoconf touchfile support which fixes issues where disabling multipath autoconfig would not apply. [ QSTOR-10706 ]
Enclosures and Controllers
* Addes enclosure layour for Supermicro Server SYS-F629P3-RC1B FatTwin 4-Node 24+12 bay [ QSTOR-10853 ]
* Fixed an issue with disk discovery when a CORVAULT is attached. [ QSTOR-10664 ]
* Added the ability to blink empty slots on jbod hardware that supports that feature. This action is accomplished using sg\_ses commands. [ QSTOR-10618 ]
* Added functionality to treat enclosures accidentally unplugged as MISSING, so that when reconnected their user-set properties are not lost . [ QSTOR-10542 ]

High Availability Failover
* Fixed an issue with post failover storage pool update tasks being stuck in a running state for nodes where the HA storage pool was previously evicted from due to an automatically triggered failover event. [ QSTOR-10485 ]

Kernel and Drivers
* Updated ZFS driver version to 2.2.6 [ QSTOR-10647 ]
* Updated scst iSCSI/FC Target driver to 3.9.0 [ QSTOR-10534 ]

Licensing
* Fixup old license keys to work with new format. [ QSTOR-10788 ]
* Added Express Edition Licenses [ QSTOR-10619 ]
* Show TB Utilized in the License grid and property view. [ QSTOR-8009 ]

NAS Gateway / Cloud Containers
* Fix wrap and truncation issues in the Cloud Add Credential dialog for Spanish. [ QSTOR-10792 ]

Network Shares
* Retain include line position in smb.conf [ QSTOR-10800 ]
* Minor fix to retain the share description when creating a Network Share. [ QSTOR-10793 ]
* Enhance the network share CLI search to support paging (similar to buckets). [ QSTOR-10757 ]
* Fix minor share name and snapshot name validation. [ QSTOR-10520 ]
* Added additional share name validation to share modify cli and API calls. [ QSTOR-10519 ]
* Add SSSD support [ QSTOR-10445 ]
* Implemented ransomware detection for Network Shares. [ QSTOR-10391 ]

Quantastor CLI
* Fixed qs cli disk-list filters for ssd, and nvme disk types. [ QSTOR-10515 ]
* Fixed the filtering for qs cli disk-list --filter="\[unused\]" and --filter="\[used\]" commands [ QSTOR-10482 ]

Remote Replication, Snapshots and Backup Policies
* Remove SSH keys after replication links are deleted [ QSTOR-10782 ]
* Fix minor argument validation for replication schedule create and snapshot schedule create. [ QSTOR-10732 ]
* Added monitoring for file modify events to enable continuous data protection on modified files. [ QSTOR-10557 ]
* Added ability for Snapshot Schedules and Replication Schedules to absorb old snapshots. [ QSTOR-10524 ]
* Create local delta Snapshot on source when Replication Schedule is skipped. [ QSTOR-10357 ]
* Change the control in the 'Update Selections for Replication Schedule' dialog to be a dual chooser. [ QSTOR-10351 ]

SCSI / NVMe Target
* Added a remote Fibre Channel port list to the fc target port section of the UI and 'qs fc-remote-port-enum' CLI command. [ QSTOR-10541 ]
* Added the Fiber Channel Issue LIP dialog to the UI that can be used to issue a lip on a specific FC port. [ QSTOR-10226 ]

SNMP
* Update SNMP MIB [ QSTOR-10847 ]

Security
* Fixed a bug in the 2FA login process. [ QSTOR-10841 ]
* Added support for a custom iptables include script under
/var/opt/osnexus/quantastor/iptables.qscustom [ QSTOR-10794 ]
* Updated tomcat package version to 9.0.96.0 [ QSTOR-10691 ]

Service Core
* Fix a small memory leak [ QSTOR-10778 ]
* Revise the server S3 modify API to accept spaces for the Display Name property. [ QSTOR-10724 ]
* Fixed some issues with writing the Chrony conf file on platforms that have chrony installed (like Jammy) [ QSTOR-10293 ]

Storage Pool Management
* Allow trim schedule to run nightly. [ QSTOR-10652 ]

Storage Volumes
* Allow minimum of <4MB for Storage Volume QoS Control limits. [ QSTOR-10765 ]
* Updated Storage Volume QoS controls to use cGroups v2 for modern linux kernels/platforms. [ QSTOR-10529 ]

Upgrade Manager and Installer
* Added logic to temporarily disable the upmap balancer during ceph upgrade. [ QSTOR-10702 ]
* Fixed an issue where Storage System Upgrade tasks were showing 25% progress but transitioned to the 'Completed' stage. [ QSTOR-10673 ]
* Install sssd packages by default on focal and newer platforms. [ QSTOR-10549 ]
* chrony is now the default time daemon for ubuntu 22.04 jammy and newer platforms. [ QSTOR-10273 ]
* Added 22.04 Jammy as a new Platform for QuantaStor [ QSTOR-10225 ]

Web Manager
* Disable the 'Start Upgrade' button in the Upgrade dialog until the system update check is complete. [ QSTOR-10776 ]
* Show the Tag/Alt Name value along with the Controller name in the identify dialog if provided. [ QSTOR-10775 ]
* Decrease the replication detail chart update frequency. [ QSTOR-10753 ]
* Added email validation check for the Alert Manager dialog [ QSTOR-10590 ]
* Added Timezone configuration as a step in the getting started guide. [ QSTOR-10502 ]

== v6.4.5.001 (November 1st 2024) ==

=== [[QuantaStor 6.4.5 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.4.5 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.4.5 Upgrade Instructions| upgrading to QuantaStor v6.4.5]].

=== Release Notes ===

Ceph Scale-out Block, Object and File
* Fixed an error with Ceph Bucket Discovery tasks. [ QSTOR-10707 ]

== v6.4.4.013 (October 25th 2024) ==

=== [[QuantaStor 6.4.4 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.4.4 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.4.4 Upgrade Instructions| upgrading to QuantaStor v6.4.4]].

=== Release Notes ===

Ceph Scale-out Block, Object and File
* Added a fix for Seagate Corvault based Ceph deployments to ensure ceph LVM layer is started on system boot. [ QSTOR-10686 ]
* Added qs-osd-compact script to assist with OSD compaction on a per system basis. [ QSTOR-10668 ]
* Fixed an issue with Ceph OSD Journal device discovery for encrypted Ceph Clusters. [ QSTOR-10666 ]
* Extend timeouts for OSD restart stage of the Ceph upgrade task. [ QSTOR-10665 ]
* Fixes bug were OSDs lose journal device correlation after OSD reweight operation. [ QSTOR-10657 ]

Enclosures and Controllers
* Fixed an issue with enclosure and disk slot identity correlation information. [ QSTOR-10681 ]

High Availability Failover
* Disables the PCS daemon WebUI by default. [ QSTOR-10692 ]
* Adds a check for versions older than 6.4.3 to auto-disable the new health checks logic that is not compatible with older versions. [ QSTOR-10692 ]

Upgrade Manager and Installer
* Fixed: the qs_upgrade_redhat8.sh script now automatically removes legacy centos repos that are no longer needed for Redhat platform deployments. [ QSTOR-10676 ]

== v6.4.3.021 (October 10th 2024) ==

=== [[QuantaStor 6.4.3 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.4.3 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.4.3 Upgrade Instructions| upgrading to QuantaStor v6.4.3]].

=== Release Notes ===

Alerts and Configuration Analysis
* Fixed a incorrect encrypted ZFS pool check check in the Config Analyzer for encrypted Ceph clusters with encrypted OSDs. [ QSTOR-10643 ]

Ceph Scale-out Block, Object and File
* Optimized scale-out ceph bucket discovery for very large number of S3 buckets. [ QSTOR-10621 ]
* Ceph OSD create and delete operations will no longer fail due to services being masked. [ QSTOR-10617 ]
* Made some improvements to the Veeam SOSAPI update cycle. [ QSTOR-10616 ]
* Fixed an issue with creating Ceph Storage Classes of the same name on different Ceph Clusters. [ QSTOR-10592 ]
* Default to http based checks from the haproxy load balancer to backend http radosgw instances. [ QSTOR-10559 ]

NAS Gateway / Cloud Containers
* Add a rescan for cloud containers so that data is refreshed if uploaded from another S3 gateway. [ QSTOR-10627 ]

Network Shares
* Fix an issue with trusted domain users not found in the Active Directory User search dialog. [ QSTOR-7353 ]

Remote Replication, Snapshots and Backup Policies
* Enabled Continuous Data Protection and Auto-tiering on Backup Policies using the SMB protocol. [ QSTOR-10601 ]

Security
* Added http proxy support for Upgrades, Support Log submission and License Key Activation. [ QSTOR-10432 ]

Upgrade Manager and Installer
* Fix triggering Ceph cluster upgrades when there are multiple scale-out storage Ceph clusters in the same QuantaStor Storage Grid. [ QSTOR-10612 ]
* Fixed an issue with the Ganesha 5.9 libntirpc dependency. This change was shipped earlier with a respin of QuantaStor 6.4.3 to include the missing updated library in the update repo and in the ISO and OVA image. [ QSTOR-10576 ]

== v6.4.2.053 (September 19th 2024) ==

=== [[QuantaStor 6.4.2 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.4.2 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.4.2 Upgrade Instructions| upgrading to QuantaStor v6.4.2]].

=== Release Notes ===

Alerts and Configuration Analysis
* Fixed tolerances for alerting on changes in PSU status and other IPMI sensors. [ QSTOR-10447 ]

Ceph Scale-out Block, Object and File
* Adds total Object count to S3 tenant and user objects [ QSTOR-10606 ]
* Improved logic to ensure Scale-out Object Storage Class Auto-Tiering Rules were applied correctly on all nodes after an update. [ QSTOR-10599 ]
* Unblocked file quotas for CephFS Shares. [ QSTOR-10584 ]

Enclosures and Controllers
* Added Enclosure for Tyan Transport SX TS70-B8056. [ QSTOR-10597 ]
* Fixed an issue with enclosure support for Supermicro SSG-621E-ACR16L [ QSTOR-10563 ]

NAS Gateway / Cloud Containers
* Fix a regression with NFS and SMB access for cloud container shares. [ QSTOR-10588 ]

Network Shares
* Fixed an issue where the quota field was incorrectly disabled in the network share modify and create dialogs for nested shares on zfs storage pools. [ QSTOR-10602 ]
* Implemented ability to adjust Network Shares permission settings via a specified permissions mask. [ QSTOR-10147 ]

Quantastor CLI
* Fix a minor regression with share name now showing in the output of "qs share-list" [ QSTOR-10587 ]

Remote Replication, Snapshots and Backup Policies
* Show more informative errors when a Backup Job fails. [ QSTOR-10575 ]
* Fixed an issue where multiple snapshots were wrongfully created. [ QSTOR-10564 ]
* Fix an issue with removing excess snapshots for a backup policy with cephFS shares. [ QSTOR-10560 ]
* Add maximum total snapshots for replication, snapshot and backup schedules. [ QSTOR-10539 ]
* Fixed an issue where GMT Snapshots were disappearing. [ QSTOR-10538 ]
* Fix an issue with resume replication not updating the replication reports. [ QSTOR-10536 ]
* Added auto-tier stubbing minimum file size threshold. [ QSTOR-10505 ]

SCSI / NVMe Target
* Added support for setting specific LUN numbers on Storage volumes for Fibre Channel access. This is available in the Advanced tab of the Storage Volume Create and Modify dialogs. [ QSTOR-10544 ]

Service Core
* Improved efficiency for Ceph Bucket discovery. New Default behavior is to skip collecting life cycle policy and object locking data on the bucket. Contact support to enable object locking discovery on buckets. [ QSTOR-10600 ]

Upgrade Manager and Installer
* Added script to fix RGW configurations on clusters created on older versions of QuantaStor. [ QSTOR-10569 ]
* Added support for Ceph Reef 18.x upgrades. [ QSTOR-10493 ]

Web Manager
* Make the info fields, in the Snapshot Rollback Point fieldset of the Rollback Storage Volume dialog, read-only. [ QSTOR-10596 ]
* Hide the timezone column in the Upgrade Manager dialog. [ QSTOR-10540 ]
* Change S3 Bucket Search panel location from North to West of screen. [ QSTOR-10405 ]

== v6.4.1.011 (August 6th 2024) ==

=== [[Upgrade Instructions]] ===
Click [[QuantaStor 6.4.1 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.4.1 Upgrade Instructions| upgrading to QuantaStor v6.4.1]].

=== Release Notes ===

Enclosures and Controllers
* Fixed an issue with the Supermicro NVMe Enclosure mappings for the SBB-SSG-221E and SSG-641E [ QSTOR-10506 ]

Network Interfaces
* Fixed: Infiniband Devices should now have the correct Make and Model displayed in the Network interface section. [ QSTOR-10448 ]

Network Shares
* Fixed an issue with updating the status of Backup Policy Jobs. [ QSTOR-10517 ]

Remote Replication, Snapshots and Backup Policies
* Fixed: Shows the last 14 days in the replication schedule dashboard regardless of the replication schedule configuration. Fix an issue where not all series data was appearing despite being in a completed state. [ QSTOR-10528 ]
* Fixed an issue with duplicate Replication tasks. [ QSTOR-10526 ]
* Correct the max temporary snapshots retained for volumes in a replication schedule. [ QSTOR-10525 ]
* Add the ability to discover partially transferred chkpnts if replication is interrupted on the first transfer. [ QSTOR-10500 ]

Upgrade Manager and Installer
* Fixed: optimized dependency checker for qs-upgrade script. [ QSTOR-10531 ]

== v6.4.0.174 (July 18th 2024) ==

=== [[Upgrade Instructions]] ===
Click [[QuantaStor 6.4.0 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.4.0 Upgrade Instructions| upgrading to QuantaStor v6.4.0]].

=== Release Notes ===

Alerts and Configuration Analysis
* Fixed an issue with adding new ITSM webhook integrations. [ QSTOR-10480 ]
* Added support for Microsoft Teams to ITSM integrations. [ QSTOR-10458 ]
* Added the ability to easily extend ITSM integrations with new integration modules with qs_alerthandlers.conf file. [ QSTOR-10458 ]
* Include storage volumes in pool reports. [ QSTOR-10083 ]

Ceph Scale-out Block, Object and File
* Fixed an issue where the wrong libntirpc library was installed for nfs-ganesha. [ QSTOR-10463 ]
* Added a Copy to Clipboard Button for a selected access key and changed the double click on access/secret key behavior to copy to clipboard for the S3 User Access Key Manager Dialog. [ QSTOR-10428 ]
* Added a check to the S3 User Access Key Manager Dialog to ensure only the selected key text is shown when the user clicks the 'Show Key Text' button on the dialog. [ QSTOR-10428 ]
* Added block for more than 2 S3 Gateway loadbalancer modes configured at the same time. [ QSTOR-10407 ]
* Added a new feature for data pool capacity based, overflow rules for ceph object storage. Added support for a force flag for the auto tiering rules, that will overwrite any client side storage class specifications. [ QSTOR-10379 ]
* Add reporting for object storage usage. Periodic reports can be generated as part of "Report Schedules" by enabling "Object Zone Usage Report". [ QSTOR-10355 ]
* Added object count for Ceph Buckets. [ QSTOR-10348 ]
* Updated the default access permissions for Ceph keyring files. [ QSTOR-10325 ]
* Updated ceph cluster scale-out OSD osd_op_queue setting to wpq by default. The setting will take effect for any new OSDs on creation. Existing OSDs will use the new setting on OSD service restart (system reboot, encrypted OSD re-keying or manual OSD service restart) [ QSTOR-10123 ]
* Improved an error message when creating a Site Vif with Block Storage use case. [ QSTOR-9984 ]
* Added ability to enable a size quota and a file number quota on cephFS Shares. [ QSTOR-7344 ]

Enclosures and Controllers
* Fixed an issue where a disconnected JBOD could leave the enclosure object around on LSI HBAs. [ QSTOR-10503 ]
* Fixed: a modify of enclosure or system layout to something other than default will also set the same layout on the corresponding system or enclosure(s) that are currently set to default. [ QSTOR-10496 ]
* Fixed an issue with using the wrong LED control Utility for disk identification on Supermicro NVMe storage systems. [ QSTOR-10469 ]
* Added support for Supermicro SBB-SSG-221E-DN2R24R to enclosure/server views. [ QSTOR-10460 ]
* Added Support for Supermicro SSG-641E-E1CR36L/H to enclosure/server views. [ QSTOR-10429 ]
* Prevent a missing disk from being blinked. [ QSTOR-10179 ]

High Availability Failover
* Fixed an issue that could terminate the qs_pool_export script early on ha failover without final logging. [ QSTOR-10514 ]
* Fixed: added a check for HA VIFs to the network port offline dialog. This prevents a possible split cluster scenario. [ QSTOR-10414 ]
* Updated Task error messages to include the system where an error occurred for HA Storage pool failover tasks. [ QSTOR-10248 ]
* Added periodic HA failover group health checks for client and media connectivity. An alert will be raised If a health check fails that could indicate an issue with the future success of a High Availability failover from the primary to secondary node. [ QSTOR-9380 ]

Network Interfaces
* Prevent modifying parent port when static route is configured. [ QSTOR-10200 ]
* Fixed: removed iscsi and nvmeof portal configuration options on all grid vifs. client access should be configured through HA or Site cluster vifs only. [ QSTOR-9974 ]

Network Shares
* Fixed: NFS remove client access dialog and the qs share-client-remove CLI command now default to immediately terminate client connections for removed export rules, enhancing security. An option to retain client connections is available in the UI ("Retain Client Connections") and CLI (--retain-client-connection=true). [ QSTOR-10431 ]

Remote Replication, Snapshots and Backup Policies
* Fixed an issue with Remote Replication reporting incorrect snapshot count. [ QSTOR-10476 ]
* Added a ZFS quantastor:scheduletype property to snapshots so that it is clearer what type of schedule created the snapshot. [ QSTOR-10421 ]
* Fix duplicate entries in replication dashboard. [ QSTOR-10385 ]
* Use raw mode for ZFS send and receive. Use on the wire compression if the source is not compressed. [ QSTOR-10153 ]

SNMP
* Update SNMP MIB [ QSTOR-10512 ]

Security
* Added feature to replace the OSD encryption keys for a given Ceph cluster. [ QSTOR-10283 ]
* Improved qs-util wrapper script so that user is prompted for secret passphrase. Passphrase will remain hidden. [ QSTOR-9982 ]

Service Core
* Fix minor trace message for Maintenance schedules. [ QSTOR-10416 ]
* Added a check to the QuantaStor system startup to ensure that LUKS encrypted Physical disks devices provided to QuantaStor via the iSCSI Software adapter are opened after system boot. [ QSTOR-10257 ]

Upgrade Manager and Installer
* Added support for customizing OVF templates with passwords and license keys. [ QSTOR-10451 ]
* Fixed an issue with the archived centos ganesha mirrors in the qs_upgrade_redhat8.sh install and upgrade script. [ QSTOR-10446 ]

Web Manager
* Fixed an issue where the User Web Customization rules were not being properly applied when the rules were defined in the Role create or modify dialog. [ QSTOR-10513 ]
* Fixed the text highlight and other colors used in the UI to be consistent across elements. [ QSTOR-10470 ]
* Update: Replaced all instances of 'double click to reveal plain text' on password fields with an explicit eyeball reveal button to allow users to show plain text. [ QSTOR-10410 ]
* Updated web manager tomcat and Java runtime dependencies. [ QSTOR-9492 ]

== v6.3.7.011 (June 18th 2024) ==

=== [[QuantaStor 6.3.7 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.3.7 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.3.7 Upgrade Instructions| upgrading to QuantaStor v6.3.7]].

=== Release Notes ===

Ceph Scale-out Block, Object and File
* Fixed an issue with creating Erasure Coded Ceph Object Storage Classes in the Web UI. [ QSTOR-10434 ]

Dashboards and Analytics
* Fixed the install-ceph-prometheus scripts to always have a default fallback install version if the latest version is not available. [ QSTOR-10441 ]
* Updated wiki documentation for the Prometheus and Grafana Integration guide to reflect changes from latest Grafana 11.0 release. [ QSTOR-10441 ]

Enclosures and Controllers
* Fixed several items and updated logic for External System Corvault support. [ QSTOR-10235 ]

Kernel and Drivers
* * Fixed an issue with modern mellanox OFED installs using the mellanox-ofed-install.sh script and legacy ConnectX-3 Based Mellanox HBA's [ QSTOR-10295 ]

Network Shares
* Added logic to always bind mount the /export paths on Network Shares even if the share has no NFS access rules and is set to disabled and SMB/CIFS disabled. This includes Nested shares under Parent Network Shares. No noticeable increase in failover times was detected when testing on a Large HA config with many Network Shares including many Nested Shares and snapshots. [ QSTOR-10424 ]
* Fixed an issue with the Network Share snapshot count property. [ QSTOR-10329 ]
* Re-enabled the Network Share Snapshot count column by default in the Network Share Grid View. [ QSTOR-10329 ]

Storage Volumes
* Fixed an issue where FC ALUA standby LUN devices for Storage Volumes would not appear as non-rotational(SSD) to clients when on an SSD or NVMe based Storage Pool. Note: a reboot is required to reload the SCST kernel driver stack on the system for the fix to take effect. [ QSTOR-10417 ]
* Fixed an issue with presenting pass-through Storage Volumes as non-rotational(SSD) to clients. [ QSTOR-10417 ]

Upgrade Manager and Installer
* Updated mellanox-ofed-install.sh script to support latest Mellanox OFED 24.04-0.6.6.0 [ QSTOR-10438 ]
* Added a lts optional flag to the mellanox-ofed-install.sh for installing Mellanox OFED version 5.8-4.1.5.0. [ QSTOR-10438 ]

Web Manager
* Fix a minor ribbon bar alignment and spacing issue between elements by making a deferred force layout call during context switching. [ QSTOR-10413 ]
* Fixed an issue where some elements of the Ribbon Bar would not be visible or would somehow be under the visible section of the UI. [ QSTOR-10413 ]
* Removed the ZFS share encryption tab from the create and modify network share dialogs. The ZFS Share encryption feature is still available for share creation via the CLI but is not recommended for most users due to ZFS driver level issues. When the ZFS driver issues are resolved in a future ZFS release, the encryption tab will be re-enabled. [ QSTOR-10352 ]

== v6.3.6.003 (June 4th 2024) ==

=== [[QuantaStor 6.3.6 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.3.6 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.3.6 Upgrade Instructions| upgrading to QuantaStor v6.3.6]].

=== Release Notes ===
Remote Replication, Snapshots and Backup Policies
* Added a check to enforce 'Enable target checkpoint recovery (unchecking will perform full replication)' setting on Remote Replication Schedules. This helps ensure that no additional _chkpnt is created for a share or volume if one already exists for the source and target replication association. [ QSTOR-10419 ]
* Fixed an issue with replication report showing synchronizing state forever. [ QSTOR-10419 ]

Security
* Added qs-util wuicustomcerts command to allow creation of a /var/opt/osnexus/quantastor/ssl/nginx_quantastor_ssl_custom.conf nginx override config so that users can customize certificate paths and ciphers from the QuantaStor defaults for the Web UI. [ QSTOR-9037 ]

== v6.3.5.020 (May 23rd 2024) ==

=== [[QuantaStor 6.3.5 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.3.5 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.3.5 Upgrade Instructions| upgrading to QuantaStor v6.3.5]].

=== Release Notes ===

Ceph Scale-out Block, Object and File
* Fixed an issue where s3 gateway create was creating load balancers with https->https mode when https->http mode was passed in. [ QSTOR-10399 ]
* Fixed some issues with discovery of the http/https mode for the S3 load balancer. [ QSTOR-10399 ]
* Further optimizations and fixes related to Grid communication and Ceph Scale-out Object discovery on Object Storage Pools with a large number of buckets. [ QSTOR-10380 ]
* Fixed an issue with adding and removing RGW instances on the same node via different IP addresses. [ QSTOR-10370 ]

High Availability Failover
* Added logic to limit number of open threads and open file handles needed to unmount shares for the HA storage pool failover process. This fixes an issue with deployments that have a large amount of shares, including nested shares and share snapshots. [ QSTOR-10373 ]
* Added more coverage for the auto close open file handles logic during HA storage pool failover to help unmount shares under the nfs /exports path as well as nested shares/snapshots. [ QSTOR-10373 ]

Multitenancy
* Fixed some issues with Multitenancy Container discovery and database table updates. [ QSTOR-10363 ]

Network Interfaces
* Added a exact match filter config file /var/opt/osnexus/quantastor/conf/qs_portFilter.conf for interface names that allows users to blacklist interfaces they do not want QuantaStor to see and/or manage. [ QSTOR-9664 ]

Network Shares
* Fixed an issue with the Network Share samba audit logging feature when upgrading from a legacy audit logging config. [ QSTOR-10390 ]

Quantastor CLI
* Update qs-iostat utility to python3. [ QSTOR-10152 ]

Security
* Adds support for controlling the sample period over which bad login attempts can trigger a short or permanent lock. [ QSTOR-10374 ]
* Adds support for controlling the duration of the short lock. [ QSTOR-10374 ]
* Fixes a security bug where good login attempts could mask bad login attempts by clearing the bad login attempt sample set for a given user. [ QSTOR-10374 ]
* Changes the special rules around bad login attempts for the 'admin' user, now allowing it to be locked. [ QSTOR-10374 ]
* Adds a touch file to unlock the 'admin' user account. [ QSTOR-10374 ]
* Adds a touch file to block the permanent locking of the 'admin' user account, which is similar to the current behavior. [ QSTOR-10374 ]

Storage Volumes
* Fixed an issue where iSCSI CHAP was not being correctly enabled in the iSCSI target on volumes when configured. [ QSTOR-10398 ]
* Fixed an issue with Fibre Channel Storage Volumes being presented after Storage System boot for Single QuantaStor node deployments (non-HA). [ QSTOR-10277 ]

== v6.3.4.003 (May 14th 2024) ==

=== [[QuantaStor 6.3.4 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.3.4 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.3.4 Upgrade Instructions| upgrading to QuantaStor v6.3.4]].

=== Release Notes ===

Web Manager
* Optimized WebUI login time for Large Scale-out Object deployments. [ QSTOR-10365 ]
* Fixed an issue where the WUI idle logout timer would be reached even when browsing inside of the WUI for various different sections. [ QSTOR-10361 ]

== v6.3.3.033 (May 1st 2024) ==

=== [[QuantaStor 6.3.3 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.3.3 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.3.3 Upgrade Instructions| upgrading to QuantaStor v6.3.3]].

=== Release Notes ===

Ceph Scale-out Block, Object and File
* Added qs_rgw_iam_policy.sh script for generating S3api IAM compatible bucket policies. [ QSTOR-10336 ]
* Added FQDN specific string validation to the Modify Realm/Zone Group dialog. [ QSTOR-10320 ]
* Fixed some items with the Modify Realm/Zone Group task. [ QSTOR-10320 ]
* Added a drop-down to the Create Storage Class Dialog with pre-defined S3 Storage Classes supported by most S3 CLI and S3 Library based clients. Users can still create a custom Storage class if they so choose and use their own custom S3 API implementation that supports Custom S3 Storage Classes. [ QSTOR-10232 ]
* Fixed some issues with adding/removing S3 Gateways with Load Balancers. [ QSTOR-9848 ]

High Availability Failover
* Added a force flag to the Remove Site Cluster Virtual Interface dialog. [ QSTOR-8276 ]
* Added logic to auto re-apply iofencing to devices that are re-added to the system due to prior physical removal or power loss of the device/device enclosure. [ QSTOR-5475 ]
* Fixed an issue with enabling client connectivity on HA Groups and implemented more safe guards. [ QSTOR-3432 ]

Network Shares
* Add touch file to limit discovery of snapshots of nested shares. [ QSTOR-10334 ]
* Fixed: Network Share rename will correctly remount the /export/ NFS mount location to the new name. [ QSTOR-10318 ]
* Fix minor message during share disable with active SMB clients. [ QSTOR-10292 ]
* Share disable will close open file handles to the share when accessed via SMB. [ QSTOR-10291 ]
* Fixed an issue where Network sub-share alias shares would not start properly after Storage Pool HA Failover. [ QSTOR-10278 ]
* Fixed an issue where share alias advanced settings allowed modification after an HA failover. [ QSTOR-10276 ]

Remote Replication, Snapshots and Backup Policies
* Fix update selections for a replication schedule for cases where source is on a HA pool. [ QSTOR-10310 ]
* Fixed an issue with Windows Previous Versions on share-alias. [ QSTOR-10274 ]
* Added a check to ensure no duplicate share alias names are created on the same parent share. [ QSTOR-10274 ]

Security
* Fixed an issue where the Security Manager > Default Login Username field was not initializing to 'admin' for default installs and upgrades. [ QSTOR-10323 ]

Upgrade Manager and Installer
* Added logic to remove legacy google-compute-engine-oslogin and/or google-guest-agent on upgrade. These packages caused systems to not shutdown properly when installed. [ QSTOR-10340 ]
* Added a check to ensure the ledmon service is disabled by default. This is to ensure that there are no conflicts with the QuantaStor managed Disk Identify logic. [ QSTOR-10313 ]

Web Manager
* Added paging support to S3 Bucket search [ QSTOR-10324 ]

== v6.3.2.025 (April 15th 2024) ==

=== [[QuantaStor 6.3.2 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.3.2 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.3.2 Upgrade Instructions| upgrading to QuantaStor v6.3.2]].

=== Release Notes ===

Ceph Scale-out Block, Object and File
* Added search capability to the S3 Bucket section of the Web UI. [ QSTOR-10288 ]
* Added Rule Sorting and an explicit rule remove button to the Storage Class Auto-Tiering Rules Dialog. [ QSTOR-10287 ]
* Added: You can now add the FQDN's for DNS names that you want the S3 Gateways to respond to via the Modify Realm/Zone Group Dialog. Note: you must add the FQDN's of the hosts or an FQDN alias e.g. s3.yourdomain.net (like used by DNS round robin) for the HAproxy load balancer to work properly. [ QSTOR-10285 ]
* Fixed issues with Ceph S3 Bucket discovery with a large amount of buckets. [ QSTOR-10261 ]
* Fixed some items related to Veeam SOSAPI integration based on testing in Veeam Certifcation scripts. [ QSTOR-10243 ]

Enclosures and Controllers
* Fixed an issue where Dell RAID Controllers were being discovered twice in due to new support for the controllers discovery in Broadcom storcli utilities. [ QSTOR-10244 ]

High Availability Failover
* Fixed an issue where rebooting an active High Availability storage node would cause ZFS encrypted shares to go offline for any active pools on that node prior to automatic failover. [ QSTOR-10218 ]

Network Interfaces
* Fixed an issue where legacy VLAN interfaces that had the RX/TX optimizations flag set would not allow modification of the interface for any other setting. [ QSTOR-10272 ]

Not Set
* Added logic to prioritize high-speed data ports by default in the Ceph Cluster create and S3 gateway create dialogs. [ QSTOR-10266 ]
* Fixed usable space calculation on Object Pool Group when there are multiple Pools or Storage Classes using the same OSD's. [ QSTOR-10264 ]
* Fixed an issue with modifying a network share after after a custom veto files setting had been added to the samba cifs options. Now the veto files merge as a set with the default .qssnaps veto files used by the VSS GMT snapshots feature. [ QSTOR-10249 ]

Security
* Updated the OSNEXUS Security Notice service [https://services.osnexus.com/security/](https://services.osnexus.com/security/) for bionic and focal platform support. [ QSTOR-10269 ]

Service Core
* Added support for replacing ntpd with chronyd in Ubuntu Focal platform based deployments. [ QSTOR-10239 ]

== v6.3.1.009 (April 1st 2024) ==

=== [[QuantaStor 6.3.1 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.3.1 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.3.1 Upgrade Instructions| upgrading to QuantaStor v6.3.1]].

=== Release Notes ===

Alerts and Configuration Analysis
* Fixed an issue where a pool running a scrub would report as degraded in the Config Analyzer health report. [ QSTOR-10258 ]

Ceph Scale-out Block, Object and File
* Added qs-rgw-moveobjects script to allow easier s3api copy-object of a buckets contents to a different storage class. [ QSTOR-10268 ]
* Changed haproxy load-balancer to use balance source mode by default. [ QSTOR-10260 ]
* Fixed an issue with the Storage Class Auto-Tiering rules where multipart uploads with Capacity Operators of greater than or greater and equal to the Capacity Threshold would not be uploaded to the correct storage class. [ QSTOR-10254 ]

Enclosures and Controllers
* Changed qs-util seagate-ap-split mode command to use zone 5 [ QSTOR-10259 ]

Web Manager
* Increased default max bucket count for S3 user to 100K. [ QSTOR-10256 ]
* Added new Grid Preferred Port status column in the Network Port Grid. It's hidden by default. [ QSTOR-10256 ]
* Fixed s3 gateway dialog height so it can show more nodes in the grid. [ QSTOR-10256 ]
* Fixed s3 tenant create, if "Display Name" is not specified use the "Name" (display name is no longer mandatory in dialog). [ QSTOR-10256 ]

== v6.3.0.268 (March 20th 2024) ==

=== [[QuantaStor 6.3.0 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.3.0 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.3.0 Upgrade Instructions| upgrading to QuantaStor v6.3.0]].

=== Release Notes ===

Alerts and Configuration Analysis
* Fixed an issue where md software raid os partitions where being reported in the config analyzer as offline storage pools. [ QSTOR-10168 ]
* Fixed an issue where non-management ports were being flagged in the config analyzer for iSCSI acess being enabled. [ QSTOR-9891 ]

Ceph Scale-out Block, Object and File
* Blocked creating new OSDs when the OSD service is masked. [ QSTOR-10212 ]
* Show the S3 Object Storage Pool as the root node in the S3 User's and Tenant tree. [ QSTOR-10156 ]
* Show the S3 Object Storage Pool as the root node in the bucket tree. [ QSTOR-10150 ]
* Add support for multiple data pools for storage classes for Ceph Object Storage Pool. [ QSTOR-10137 ]
* Add auto tiering capability to ceph buckets. [ QSTOR-10125 ]
* Change the Ceph block storage pool to default to replica=3 for performance. [ QSTOR-10062 ]
* For CephFS, the min_size for the metadata pool should be 2. [ QSTOR-10015 ]
* Introduce safe disk replacement for Ceph OSDs. [ QSTOR-9937 ]
* Applied adjustments to Ceph Clusters for optimized scrubs on smaller and denser clusters. [ QSTOR-9900 ]
* Updated NFS Ganesha to 5.7 [ QSTOR-9821 ]
* Add support for Ceph Multi-site bucket replication. [ QSTOR-6570 ]

Disk Management
* Added support for ScaleFlux CSD 3000 SSDs that support builtin compression provisioning. [ QSTOR-10198 ]
* Fixed an issue with disk correlation by serial number on Broadcom/LSI 93XX series HBAs. [ QSTOR-10194 ]
* Show osd number in 'qs disk-list'. [ QSTOR-9717 ]

Enclosures and Controllers
* Add enclosure view for the ASUS 2u24 NVMe. [ QSTOR-10202 ]
* Fix controller selection issue in the 'Identify Hardware Controller Disk Device' dialog for when the selected object in the Physical Disk tree is a Physical Disk and not the Disk itself. [ QSTOR-10195 ]
* Updated wddcs tool to 3.2.8.0 [ QSTOR-10166 ]
* Added to feature to create or delete multiple External System Volume configurations. [ QSTOR-10061 ]

High Availability Failover
* Fixed an issue with the Create HA Failover Group Dialog when there are active FC sessions on volumes on the selected pool. [ QSTOR-10169 ]
* Changed NVMe reservations to use cptpl=2 when available so that iofencing is cleared on power on of a nvme drive. [ QSTOR-10124 ]

Licensing
* Added logic to auto-fetch new QuantaStor License Server ca certificates during online license activation. [ QSTOR-10174 ]

NAS Gateway / Cloud Containers
* Update rclone version. [ QSTOR-9512 ]

Network Interfaces
* Show static route parent port in the respective grid and delete dialog. [ QSTOR-10199 ]
* Fixed an issue with onlining/restarting offline VLAN interfaces. [ QSTOR-10180 ]
* Fixed an issue with VLAN ontop of Bonded ports on VM deployed QuantaStor instances. [ QSTOR-10180 ]
* Improve the Network bond mode descriptions, in the 'Create Bonded Port' dialog, for those that require managed switches. [ QSTOR-9842 ]
* Added IP address place holder for DHCP interfaces that have no assigned IP address. [ QSTOR-9828 ]
* Fixed an issue with downing virtual interfaces when converting to HA virtual interface. [ QSTOR-9774 ]

Network Shares
* Minor Web UI fix to display share quota percent utilization. [ QSTOR-10121 ]
* Implemented a Real Time Auto Copy feature to enhance data protection for Network Shares. [ QSTOR-9929 ]
* Updated Focal platform Samba to 4.18.6 backported from ubuntu upstream release. [ QSTOR-9924 ]
* Show parent shares in the 'qs share-list' command results. [ QSTOR-9702 ]

Quantastor CLI
* Update qs-iostat utility to python3. [ QSTOR-10152 ]

Remote Replication, Snapshots and Backup Policies
* Add the ability to force create symbolic links for backup policy outbound-move to cloud containers without a delay of 24 hours. [ QSTOR-10136 ]
* Update Replication Report Summary object as failed if source system reboots right after schedule is triggered. [ QSTOR-10097 ]

SNMP
* Regen SNMP MIB for 6.3 [ QSTOR-10228 ]

Security
* Updated JQuery version used in the QuantaStor WebUI to 3.7.1 [ QSTOR-10064 ]
* Add Audit Log Viewing to the Storage System menus. [ QSTOR-10031 ]

Storage Pool Management
* Improved logic for replacing zpool UNAVAIL disks that are identified by their id instead of a device path as the disk is no longer present or visible to the OS. [ QSTOR-10129 ]

Upgrade Manager and Installer
* Automatically disable and mask uefi fwupd service on platforms that include it to prevent unplanned firmware updates. [ QSTOR-10205 ]
* Fixed: the low boot space warning for kernel upgrades now correctly appears in the Upgrade Manager task failure message. [ QSTOR-10185 ]
* Fixed an issue where the scst/zfs userspace packages were not being pinned on security updates. [ QSTOR-10185 ]
* Fixed an issue where qstortarget was incorrectly selected during security updates but fails due to existing pinning rules. qstortarget now correctly only gets selected for install on kernel/driver upgrades. [ QSTOR-10185 ]

Web Manager
* Minor fix to show NA for share-alias space columns. [ QSTOR-10227 ]
* Login dialog shown after service restart is complete. [ QSTOR-10007 ]

== v6.2.8.016 (March 5th 2024) ==

=== [[QuantaStor 6.2.8 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.2.8 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.2.8 Upgrade Instructions| upgrading to QuantaStor v6.2.8]].

=== Release Notes ===

Enclosures and Controllers
* Fixed Hardware Disk to Physical disk slot correlation issues. [ QSTOR-10135 ]
* Improved Enclosure object guid uniqueness to better support more complex/multipath setups for hardware disk to physical disk mapping. [ QSTOR-10135 ]
* Added Hardware Enclosure Serial\# property and logic to discover serial\# when available. [ QSTOR-10102 ]

Multitenancy
* Updated Resilio container image to 3.8.1.2250 [ QSTOR-10162 ]
* Fix errors with Resilio container errors seen after upgrade. [ QSTOR-10099 ]

Remote Replication, Snapshots and Backup Policies
* Fixed an issue that could sometimes cause duplicate snapshot objects to appear for snapshot schedules with nested shares and recursive snapshot enabled. [ QSTOR-10159 ]
* Added a check to temporarily prevent adding ZFS dataset encrypted Network Shares to remote replication schedules until the Open ZFS issue \#12014 is resolved in an upcoming ZFS release. [ QSTOR-10145 ]
* Fixed an issue with using Windows Restore Previous Versions on remote Replica \_chkpnt Network Shares. [ QSTOR-10065 ]

SCSI / NVMe Target
* Updated SCST driver to 3.8.0.9038-f134517-qs01 to support latest available linux kernels for Focal platform and Focal cloud platform kernels. [ QSTOR-10151 ]

Upgrade Manager and Installer
* Added Kernel Driver Support for QuantaStor installation on Ubuntu 20.04 images on Azure, AWS and Google Cloud. [ QSTOR-10138 ]

== v6.2.7.002 (February 23rd 2024) ==

=== [[QuantaStor 6.2.7 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.2.7 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.2.7 Upgrade Instructions| upgrading to QuantaStor v6.2.7]].

=== Release Notes ===

Licensing

* Updated license manager certificates for online license activation. [ QSTOR-10154 ]

== v6.2.6.024 (February 8th 2024) ==

=== [[QuantaStor 6.2.6 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.2.6 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.2.6 Upgrade Instructions| upgrading to QuantaStor v6.2.6]].

=== Release Notes ===

Enclosures and Controllers

* Added support for iofencing NVMe disks that do not support cdw11 [ QSTOR-10087 ]
* Added an Alert for when a OS Software RAID1 mirror enters a degraded state. [ QSTOR-10080 ]
* Added support LSI-3008C0 model controllers. [ QSTOR-9841 ]
* Added a check to hardware Enclosure Discovery to automatically filter out enclosures that do not have any drive slots. [ QSTOR-9716 ]

High Availability Failover

* Fixed an issue with the I/O fencing tool where it was reporting not-supported on reservation capable nvme devices. [ QSTOR-10114 ]

Network Interfaces

* Updated static routes to use modern ip route syntax with the 'proto static' option. [ QSTOR-10103 ]
* Updated netplan conversion to by default create static routes using ip route to match the original netplan static route rules. [ QSTOR-10103 ]

Storage Pool Management

* Fixed: Activate HA Failover Group now works for Storage Pools in a degraded state missing a few devices. [ QSTOR-10100 ]
* Fixed: Create HA Failover Group now allows a force option if there are a small number of drives missing on the secondary node. Note that the operation will still be blocked if most/all of the drives are missing from the secondary node. [ QSTOR-10100 ]
* Added support for Zero Touch Maintenance Automatic Global Hot spare marking of Hardware RAID0 Passthrough units. [ QSTOR-9865 ]

Storage Volumes

* Fixed: NVMe Target Storage volumes now persist their serial numbers correctly on reboot [ QSTOR-9992 ]
* Fixed: the NVMe Target now correctly re-exports the allowed portals on system boot. [ QSTOR-9992 ]

Upgrade Manager and Installer

* Updated mellanox-ofed-install.sh script to support the latest Focal platform 5.15.0-91-generic kernel. [ QSTOR-10117 ]
* Updated the GPG repo keys for QuantaStor RedHat / and Almalinux platform installs [ QSTOR-10107 ]
* Fixed a incorrect error log when upgrading the Kernel and Drivers on the Ubuntu Focal platform. The upgrade would succeed when the error was seen, but it was unclear to the user without full log analysis. [ QSTOR-10106 ]
* Updated upgrade manager logic to ensure recommended dependency packages are always selected for install during core service and security upgrades. [ QSTOR-10101 ]
* Fixed an issue with the qs-distupgrade script where some QuantaStor core package changes were not being applied after a platform dist-upgrade from bionic to focal. [ QSTOR-10132 ]
* Added better logging of systemctl service enablement and restart during qstorservice package installs. [ QSTOR-10134 ]

== v6.2.5.032 (January 18th 2024) ==

=== [[QuantaStor 6.2.5 Upgrade Instructions| Upgrade Instructions]] ===
Click [[QuantaStor 6.2.5 Upgrade Instructions| here]] for instructions on [[QuantaStor 6.2.5 Upgrade Instructions| upgrading to QuantaStor v6.2.5]].

=== Release Notes ===

Alerts and Configuration Analysis
* Added ssh port 22 to network connectivity checker tests. [ QSTOR-10092 ]

Ceph Scale-out Block, Object and File
* Fix bug where ceph monitor daemon is disabled. [ QSTOR-10095 ]
* Added script to setup Ceph multi-site replication. [ QSTOR-10075 ]

Enclosures and Controllers
* Updated storcli version to 007.2705.0000.0000 [ QSTOR-10072 ]
* Added feature for turning off hwDisk identification for all disks, including all empty slots. [ QSTOR-10036 ]
* Added feature for turning off hwDisk identification for all disks, including all empty slots. [ QSTOR-9825 ]

Kernel and Drivers
* Updated Linux Kernel to 5.15.0-91-generic for Focal platforms [ QSTOR-10025 ]
* Linux Kernel 5.15.0-91-generic includes fixes for NFS v3 lockd that would cause file handles to be left open for NFSv3 clients when attempting to stop the nfs server before ZFS pool export during HA failover. [ QSTOR-10025 ]
* Updated ZFS to 2.1.14.qs25 for Focal platforms [ QSTOR-10025 ]

Multitenancy
* Fix an issue with missing Service Configs. [ QSTOR-10079 ]
* Add the ability to sync nested shares when parent share is selected in Resilio. Optionally skip changing the share permissions when user is specified in the config file. [ QSTOR-10070 ]

Network Shares
* Block rename of nested shares. [ QSTOR-10091 ]
* Add the ability to enable and clone a GMT snapshot [ QSTOR-4145 ]

Remote Replication, Snapshots and Backup Policies
* Fixed an issue where Remote Replication Schedules can fail if 2 source snapshots have the same created timestamp. [ QSTOR-10059 ]
* Fix a minor issue with File Age settings in the Backup Schedule Modify dialog. [ QSTOR-10056 ]
* Properly transition a Replication task and Replication Report to the 'failed' status if the source system loses power during the Replication. [ QSTOR-10041 ]
* Add a warning if checkpoint is selected in create snapshot schedule. [ QSTOR-10038 ]

Storage Volumes
* Fixed an issue with zfs storage volumes being correctly marked as missing if the underlying zfs zvol or snapshot is removed or unavailable. [ QSTOR-10086 ]

Upgrade Manager and Installer
* Added a --password option to the qs\_install.sh script to allow users to provide the QuantaStor admin user password as well as the same password for the default qadmin shell account. [ QSTOR-10085 ]

Web Manager
* Clear the replica summary graph when there are no report entries. [ QSTOR-10057 ]
* Fix enclosure graph rendering issue where a selected system with multiple valid controllers was not being render because of one underlying MD BOOT Controller. [ QSTOR-10055 ]

= Archived Change Logs =

== [[Change Log Archive 2023]] ==

== [[Change Log Archive 2022]] ==

== [[Change Log Archive 2021]] ==

== [[Change Log Archive 2020]] ==

== [[Change Log Archive 2019]] ==

== [[Change Log Archive 2018]] ==

== [[Change Log Archive|Change Log Archive pre-2018]] ==

Select the link above to see the [[Change Log Archive]] of older revisions.

QuantaStor Upgrade Guide

2025-09-05T07:39:48Z

Joshua.blake: /* Pre-Upgrade Checklist for Scale-Up */

QuantaStor is regularly evolving to add new features, make it more robust, and better performing. As such we release minor updates to QuantaStor on a regular basis and you can view the [http://www.osnexus.com/news News] section or review the [[QuantaStor Version ChangeLog|Change Log]] to get all the details about what has changed since the build that you're running.

== Web Based Upgrade Procedure ==

Upgrading QuantaStor to the latest version is made easy using the
[https://wiki.osnexus.com/index.php?title=Storage_System_Upgrade_Manager Storage System Upgrade Manager Dialog] that's integrated into the web management interface. Alternatively you can run this command to upgrade your system at the console or via an SSH session:

== Console Based Upgrade Procedure ==

<pre>
sudo qs-upgrade
</pre>

=== Upgrading Specific Components ===

<pre>
sudo apt-get update
sudo apt-get install qstormanager qstorservice qstortarget qstortomcat
</pre>

The qstormanager qstorservice qstortarget components are 'user-mode' and have no impact on workloads. The qstortarget package includes device drivers and should only be upgraded when you can take a maintenance window to reboot the appliance.

==== Details ====
The first part of the update process 'apt-get update' tells the system to update it's information about what packages are available from the OS NEXUS package server (http://packages.osnexus.com/packages). The second part tells the system to install the latest versions of the qstormanager, qstorservice, and qstortarget packages.

Often times an upgrade will only apply new qstormanager and qstorservice packages as it's fairly rare that we upgrade the driver package (qstortarget). Since upgrading drivers including the iSCSI target driver can interrupt iSCSI access to your volumes we always note in the ChangeLog which releases have driver and or kernel packages available.

==== Web UI Blank Screen ====

'''Important!''' After upgrading, be sure to clear the cache of any web browsers that were running the QuantaStor Manager web UI. If you don't clear the browser cache you'll end up using the cached copy of the UI which may not be compatible with the new version of the service.

==== Custom Configuration File Changes ====

On occasion we'll update the QuantaStor configuration file /etc/quantastor.conf and in such cases you'll get a message from the installer asking whether or not it's OK to overwrite the installed file with the package maintainers configuration file. This is to prevent the installer from overwriting your custom changes to the /etc/quantastor.conf file. If you've made changes to the /etc/quantastor.conf file then choose 'N' otherwise choose 'Y'. If you haven't made any changes, then it doesn't really matter, either choice is fine. The service has default settings built-in so the quantastor.conf configuration file is not required. If the file is missing or a new configuration setting is missing the QuantaStor service automatically uses it's own stored default which is fine for 99% of all configurations.

==== XenServer Virtual Appliance Upgrades ====
The one exception is the configuration file for the XenServer PV Virtual Appliance / VM. It requires that unidentifiable devices be usable, so it requires the 'allow_unident=1' setting which defaults to 'allow_unident=0'. So if you're upgrading a QuantaStor XenServer PV VM be sure to '''not''' overwrite the config file, and if you do, be sure to edit /etc/quantastor.conf to set the allow_unident configuration setting back to 1 otherwise your Physical Disks will not be discovered.

== Package Details ==

=== qstorservice ===
The QuantaStor core services package is called qstorservice. It contains the service, database, and all the surrounding components that are required for the storage system to run. You can start and stop the QuantaStor service manually with these following commands respectively:
"sudo service quantastor stop" and
"sudo service quantastor start".
As part of the installation process the QuantaStor service is restarted and while it is starting up you will not have access to login to the storage system via the Web Management interface for about 60 seconds. Starting and stopping the QuantaStor service will in no way interrupt access to you iSCSI disks / storage volumes.

=== qstortarget ===
The QuantaStor iSCSI target is a customized version of the open source SCST driver and includes support for iSCSI, FC, and Infiniband. If you upgrade the target mode driver your system will continue to function normally but your new drivers will not become active until after you reboot. You can manually restart the driver like so:
<pre>
service iscsi-target restart
service quantastor restart
</pre>
=== qstortomcat ===
QuantaStor's web management interface is served by the Apache Tomcat web server. The Tomcat package is just an embedded packaging of the Tomcat web server plus our iptables configuration script. The web management interface packages are included in the qstormanager package.
=== qstormanager ===
The qstormanager package contains the QuantaStor Manager web management interface and it depends on the qstortomcat package. It depends on qstortomcat as it contains a specially configured version of Apache Tomcat which is installed to /opt/osnexus/quantastor/tomcat. The QuantaStor Manager package brings the Java servlet backend component that runs under Apache Tomcat as well as all the front-end QuantaStor Manager JavaScript that runs in the browser.

== Recommended Distribution Upgrade Method for Scale-Up Systems ==

=== Pre-Upgrade Checklist ===
# It is recommended that you schedule a downtime work window, as '''a reboot will be required''' after a distro upgrade.
# For more complex upgrades we recommend scheduling time with OSNEXUS support for assistance
# Execute the distribution upgrade within a ‘screen’ session to prevent issues in case of network disconnection.
# It is advisable to stop clients from using the system, including stopping or pausing virtual machines that are consuming storage volumes presented from QuantaStor.
# Submit logs from all nodes to Support using the ‘[https://wiki.osnexus.com/index.php?title=Send_Support_Log_Files Send Support Logs]’ option in the WUI.
# Place the cluster into ‘[https://wiki.osnexus.com/index.php?title=Enter_Site_Cluster_Maintenance_Mode Maintenance Mode]’ to prevent automatic failover during the upgrade.
# For systems running 18.04 Bionic, it is required to upgrade through 20.04 Focal and then to 22.04 Jammy. To avoid any risks during the upgrade, it may be easier to make a backup of the osn.db and other relevant configuration files, and reinstall. OSNEXUS Support will best guide you on this.

=== Upgrade QuantaStor Version ===
OSNEXUS recommends that QuantaStor is upgraded to the most recent version with a full upgrade before performing a distribution upgrade. You can do this from the WUI (Web User Interface) using the ‘[[Upgrade Manager]]’ and specifying to include the kernel. A full upgrade, depending on the version you are originating from, may require a reboot. The WUI should inform you if this is the case, but it is generally a good idea to reboot the system anyway, just to ensure it can boot normally. This is good preparation for the distribution upgrade.

=== Upgrade Ubuntu OS Distribution ===
Note: This procedure upgrades the Ubuntu operating system to the next major version and updates QuantaStor to the latest release supported by that version.

To upgrade the distribution for QuantaStor Scale-Up systems, follow these steps:

'''Upgrade from 18.04 Bionic to 20.04 Focal'''

# Ensure that QuantaStor node is upgraded (including Kernel) to the most recent version using the ‘[[Upgrade Manager]]’
# Reboot to ensure that the system boots without an issue
# The site cluster HA (High Availability) between Bionic and Focal is not compatible. Site cluster VIFs must be deleted and migrated to local VIFs, along with deleting the site cluster configuration from all nodes.
# Ensure you are in a screen session as per the '''Pre-Upgrade Checklist for Scale-Up.'''
# Log in as root and execute the command '''''qs-distupgrade'''''.
# If you are not using ‘screen’, then you may be prompted "Do you want to continue without session continuation protection provided by the screen. (y/n) default: no ?", you can '''choose 'y' or 'n'. Please note that your input is taken straight away without pressing the Enter key'''.
# When asked "Do you want to proceed with the distribution upgrade for the base platform. (y/n) ?", '''type 'y'. Please note that your input is taken straight away without pressing the Enter key.'''
# When prompted "Do you wish to gather logs (y/n) Default:no ?", '''type 'y'. * Please note that your input is taken straight away without pressing the Enter key.'''
# Wait for the upgrade process to complete.
# Reboot the server. Check if the system comes online and is healthy (as confirmed with '''''qs-showlog -f''''' or in /var/log/qs/qs_service.log when the services start), then proceed to upgrade the other system.
# Repeat steps 1-10 on all nodes within the cluster.
# Once all systems are upgraded, do not recreate the cluster yet. Continue upgrading to 22.04 Jammy.

'''Upgrade from 20.04 Focal to 22.04 Jammy'''

# If you are upgrading from 18.04 Bionic to 20.04 Focal, do not recreate the cluster yet and skip steps 3 and 4. The cluster should only be recreated once all nodes have been upgraded to the latest OS and QuantaStor version. Otherwise, follow the procedure as documented.
# Ensure you are in a screen session as per the '''Pre-Upgrade Checklist for Scale-Up.'''
# For HA (High Availability) setup, via the WUI perform a failover of the pool(s) to one system before performing a full upgrade (including reboot).
# Place the cluster into ‘[https://wiki.osnexus.com/index.php?title=Enter_Site_Cluster_Maintenance_Mode Maintenance Mode]’.
# Ensure that QuantaStor node is upgraded (including Kernel) to the most recent version using the ‘[https://wiki.osnexus.com/index.php?title=Upgrade_Manager Upgrade Manager]’
# Log in as root and execute the command '''''qs-distupgrade'''''.
# If you are not using ‘screen’, then you may be prompted "Do you want to continue without session continuation protection provided by the screen. (y/n) default: no ?", you can '''choose 'y' or 'n'. Please note that your input is taken straight away without pressing the Enter key.'''
# When asked "Do you want to proceed with the distribution upgrade for the base platform. (y/n) ?", '''type 'y'. Please note that your input is taken straight away without pressing the Enter key.'''
# When prompted "Do you wish to gather logs (y/n) Default:no ?", '''type 'y'. * Please note that your input is taken straight away without pressing the Enter key.'''
# Wait for the upgrade process to complete.
# Reboot the server. Check if the system comes online and is healthy (as confirmed with '''''qs-showlog -f''''' or in /var/log/qs/qs_service.log when the services start), then proceed to upgrade the other system.
# Repeat steps 2-11 on all nodes within the cluster.

''* Gathering and submitting logs to OSNexus support will better assist in resolving any encountered issues.''

QuantaStor Upgrade Guide

2025-09-05T07:39:03Z

Joshua.blake: /* Recommended Upgrade Method for Scale-Up Systems */

QuantaStor is regularly evolving to add new features, make it more robust, and better performing. As such we release minor updates to QuantaStor on a regular basis and you can view the [http://www.osnexus.com/news News] section or review the [[QuantaStor Version ChangeLog|Change Log]] to get all the details about what has changed since the build that you're running.

== Web Based Upgrade Procedure ==

Upgrading QuantaStor to the latest version is made easy using the
[https://wiki.osnexus.com/index.php?title=Storage_System_Upgrade_Manager Storage System Upgrade Manager Dialog] that's integrated into the web management interface. Alternatively you can run this command to upgrade your system at the console or via an SSH session:

== Console Based Upgrade Procedure ==

<pre>
sudo qs-upgrade
</pre>

=== Upgrading Specific Components ===

<pre>
sudo apt-get update
sudo apt-get install qstormanager qstorservice qstortarget qstortomcat
</pre>

The qstormanager qstorservice qstortarget components are 'user-mode' and have no impact on workloads. The qstortarget package includes device drivers and should only be upgraded when you can take a maintenance window to reboot the appliance.

==== Details ====
The first part of the update process 'apt-get update' tells the system to update it's information about what packages are available from the OS NEXUS package server (http://packages.osnexus.com/packages). The second part tells the system to install the latest versions of the qstormanager, qstorservice, and qstortarget packages.

Often times an upgrade will only apply new qstormanager and qstorservice packages as it's fairly rare that we upgrade the driver package (qstortarget). Since upgrading drivers including the iSCSI target driver can interrupt iSCSI access to your volumes we always note in the ChangeLog which releases have driver and or kernel packages available.

==== Web UI Blank Screen ====

'''Important!''' After upgrading, be sure to clear the cache of any web browsers that were running the QuantaStor Manager web UI. If you don't clear the browser cache you'll end up using the cached copy of the UI which may not be compatible with the new version of the service.

==== Custom Configuration File Changes ====

On occasion we'll update the QuantaStor configuration file /etc/quantastor.conf and in such cases you'll get a message from the installer asking whether or not it's OK to overwrite the installed file with the package maintainers configuration file. This is to prevent the installer from overwriting your custom changes to the /etc/quantastor.conf file. If you've made changes to the /etc/quantastor.conf file then choose 'N' otherwise choose 'Y'. If you haven't made any changes, then it doesn't really matter, either choice is fine. The service has default settings built-in so the quantastor.conf configuration file is not required. If the file is missing or a new configuration setting is missing the QuantaStor service automatically uses it's own stored default which is fine for 99% of all configurations.

==== XenServer Virtual Appliance Upgrades ====
The one exception is the configuration file for the XenServer PV Virtual Appliance / VM. It requires that unidentifiable devices be usable, so it requires the 'allow_unident=1' setting which defaults to 'allow_unident=0'. So if you're upgrading a QuantaStor XenServer PV VM be sure to '''not''' overwrite the config file, and if you do, be sure to edit /etc/quantastor.conf to set the allow_unident configuration setting back to 1 otherwise your Physical Disks will not be discovered.

== Package Details ==

=== qstorservice ===
The QuantaStor core services package is called qstorservice. It contains the service, database, and all the surrounding components that are required for the storage system to run. You can start and stop the QuantaStor service manually with these following commands respectively:
"sudo service quantastor stop" and
"sudo service quantastor start".
As part of the installation process the QuantaStor service is restarted and while it is starting up you will not have access to login to the storage system via the Web Management interface for about 60 seconds. Starting and stopping the QuantaStor service will in no way interrupt access to you iSCSI disks / storage volumes.

=== qstortarget ===
The QuantaStor iSCSI target is a customized version of the open source SCST driver and includes support for iSCSI, FC, and Infiniband. If you upgrade the target mode driver your system will continue to function normally but your new drivers will not become active until after you reboot. You can manually restart the driver like so:
<pre>
service iscsi-target restart
service quantastor restart
</pre>
=== qstortomcat ===
QuantaStor's web management interface is served by the Apache Tomcat web server. The Tomcat package is just an embedded packaging of the Tomcat web server plus our iptables configuration script. The web management interface packages are included in the qstormanager package.
=== qstormanager ===
The qstormanager package contains the QuantaStor Manager web management interface and it depends on the qstortomcat package. It depends on qstortomcat as it contains a specially configured version of Apache Tomcat which is installed to /opt/osnexus/quantastor/tomcat. The QuantaStor Manager package brings the Java servlet backend component that runs under Apache Tomcat as well as all the front-end QuantaStor Manager JavaScript that runs in the browser.

== Recommended Distribution Upgrade Method for Scale-Up Systems ==

=== Pre-Upgrade Checklist for Scale-Up ===
# It is recommended that you schedule a downtime work window, as '''a reboot will be required''' after a distro upgrade.
# For more complex upgrades we recommend scheduling time with OSNEXUS support for assistance
# Execute the distribution upgrade within a ‘screen’ session to prevent issues in case of network disconnection.
# It is advisable to stop clients from using the system, including stopping or pausing virtual machines that are consuming storage volumes presented from QuantaStor.
# Submit logs from all nodes to Support using the ‘[https://wiki.osnexus.com/index.php?title=Send_Support_Log_Files Send Support Logs]’ option in the WUI.
# Place the cluster into ‘[https://wiki.osnexus.com/index.php?title=Enter_Site_Cluster_Maintenance_Mode Maintenance Mode]’ to prevent automatic failover during the upgrade.
# For systems running 18.04 Bionic, it is required to upgrade through 20.04 Focal and then to 22.04 Jammy. To avoid any risks during the upgrade, it may be easier to make a backup of the osn.db and other relevant configuration files, and reinstall. OSNEXUS Support will best guide you on this.

=== Upgrade QuantaStor Version ===
OSNEXUS recommends that QuantaStor is upgraded to the most recent version with a full upgrade before performing a distribution upgrade. You can do this from the WUI (Web User Interface) using the ‘[[Upgrade Manager]]’ and specifying to include the kernel. A full upgrade, depending on the version you are originating from, may require a reboot. The WUI should inform you if this is the case, but it is generally a good idea to reboot the system anyway, just to ensure it can boot normally. This is good preparation for the distribution upgrade.

=== Upgrade Ubuntu OS Distribution ===
Note: This procedure upgrades the Ubuntu operating system to the next major version and updates QuantaStor to the latest release supported by that version.

To upgrade the distribution for QuantaStor Scale-Up systems, follow these steps:

'''Upgrade from 18.04 Bionic to 20.04 Focal'''

# Ensure that QuantaStor node is upgraded (including Kernel) to the most recent version using the ‘[[Upgrade Manager]]’
# Reboot to ensure that the system boots without an issue
# The site cluster HA (High Availability) between Bionic and Focal is not compatible. Site cluster VIFs must be deleted and migrated to local VIFs, along with deleting the site cluster configuration from all nodes.
# Ensure you are in a screen session as per the '''Pre-Upgrade Checklist for Scale-Up.'''
# Log in as root and execute the command '''''qs-distupgrade'''''.
# If you are not using ‘screen’, then you may be prompted "Do you want to continue without session continuation protection provided by the screen. (y/n) default: no ?", you can '''choose 'y' or 'n'. Please note that your input is taken straight away without pressing the Enter key'''.
# When asked "Do you want to proceed with the distribution upgrade for the base platform. (y/n) ?", '''type 'y'. Please note that your input is taken straight away without pressing the Enter key.'''
# When prompted "Do you wish to gather logs (y/n) Default:no ?", '''type 'y'. * Please note that your input is taken straight away without pressing the Enter key.'''
# Wait for the upgrade process to complete.
# Reboot the server. Check if the system comes online and is healthy (as confirmed with '''''qs-showlog -f''''' or in /var/log/qs/qs_service.log when the services start), then proceed to upgrade the other system.
# Repeat steps 1-10 on all nodes within the cluster.
# Once all systems are upgraded, do not recreate the cluster yet. Continue upgrading to 22.04 Jammy.

'''Upgrade from 20.04 Focal to 22.04 Jammy'''

# If you are upgrading from 18.04 Bionic to 20.04 Focal, do not recreate the cluster yet and skip steps 3 and 4. The cluster should only be recreated once all nodes have been upgraded to the latest OS and QuantaStor version. Otherwise, follow the procedure as documented.
# Ensure you are in a screen session as per the '''Pre-Upgrade Checklist for Scale-Up.'''
# For HA (High Availability) setup, via the WUI perform a failover of the pool(s) to one system before performing a full upgrade (including reboot).
# Place the cluster into ‘[https://wiki.osnexus.com/index.php?title=Enter_Site_Cluster_Maintenance_Mode Maintenance Mode]’.
# Ensure that QuantaStor node is upgraded (including Kernel) to the most recent version using the ‘[https://wiki.osnexus.com/index.php?title=Upgrade_Manager Upgrade Manager]’
# Log in as root and execute the command '''''qs-distupgrade'''''.
# If you are not using ‘screen’, then you may be prompted "Do you want to continue without session continuation protection provided by the screen. (y/n) default: no ?", you can '''choose 'y' or 'n'. Please note that your input is taken straight away without pressing the Enter key.'''
# When asked "Do you want to proceed with the distribution upgrade for the base platform. (y/n) ?", '''type 'y'. Please note that your input is taken straight away without pressing the Enter key.'''
# When prompted "Do you wish to gather logs (y/n) Default:no ?", '''type 'y'. * Please note that your input is taken straight away without pressing the Enter key.'''
# Wait for the upgrade process to complete.
# Reboot the server. Check if the system comes online and is healthy (as confirmed with '''''qs-showlog -f''''' or in /var/log/qs/qs_service.log when the services start), then proceed to upgrade the other system.
# Repeat steps 2-11 on all nodes within the cluster.

''* Gathering and submitting logs to OSNexus support will better assist in resolving any encountered issues.''

QuantaStor Upgrade Guide

2025-09-05T07:38:38Z

Joshua.blake:

QuantaStor is regularly evolving to add new features, make it more robust, and better performing. As such we release minor updates to QuantaStor on a regular basis and you can view the [http://www.osnexus.com/news News] section or review the [[QuantaStor Version ChangeLog|Change Log]] to get all the details about what has changed since the build that you're running.

== Web Based Upgrade Procedure ==

Upgrading QuantaStor to the latest version is made easy using the
[https://wiki.osnexus.com/index.php?title=Storage_System_Upgrade_Manager Storage System Upgrade Manager Dialog] that's integrated into the web management interface. Alternatively you can run this command to upgrade your system at the console or via an SSH session:

== Console Based Upgrade Procedure ==

<pre>
sudo qs-upgrade
</pre>

=== Upgrading Specific Components ===

<pre>
sudo apt-get update
sudo apt-get install qstormanager qstorservice qstortarget qstortomcat
</pre>

The qstormanager qstorservice qstortarget components are 'user-mode' and have no impact on workloads. The qstortarget package includes device drivers and should only be upgraded when you can take a maintenance window to reboot the appliance.

==== Details ====
The first part of the update process 'apt-get update' tells the system to update it's information about what packages are available from the OS NEXUS package server (http://packages.osnexus.com/packages). The second part tells the system to install the latest versions of the qstormanager, qstorservice, and qstortarget packages.

Often times an upgrade will only apply new qstormanager and qstorservice packages as it's fairly rare that we upgrade the driver package (qstortarget). Since upgrading drivers including the iSCSI target driver can interrupt iSCSI access to your volumes we always note in the ChangeLog which releases have driver and or kernel packages available.

==== Web UI Blank Screen ====

'''Important!''' After upgrading, be sure to clear the cache of any web browsers that were running the QuantaStor Manager web UI. If you don't clear the browser cache you'll end up using the cached copy of the UI which may not be compatible with the new version of the service.

==== Custom Configuration File Changes ====

On occasion we'll update the QuantaStor configuration file /etc/quantastor.conf and in such cases you'll get a message from the installer asking whether or not it's OK to overwrite the installed file with the package maintainers configuration file. This is to prevent the installer from overwriting your custom changes to the /etc/quantastor.conf file. If you've made changes to the /etc/quantastor.conf file then choose 'N' otherwise choose 'Y'. If you haven't made any changes, then it doesn't really matter, either choice is fine. The service has default settings built-in so the quantastor.conf configuration file is not required. If the file is missing or a new configuration setting is missing the QuantaStor service automatically uses it's own stored default which is fine for 99% of all configurations.

==== XenServer Virtual Appliance Upgrades ====
The one exception is the configuration file for the XenServer PV Virtual Appliance / VM. It requires that unidentifiable devices be usable, so it requires the 'allow_unident=1' setting which defaults to 'allow_unident=0'. So if you're upgrading a QuantaStor XenServer PV VM be sure to '''not''' overwrite the config file, and if you do, be sure to edit /etc/quantastor.conf to set the allow_unident configuration setting back to 1 otherwise your Physical Disks will not be discovered.

== Package Details ==

=== qstorservice ===
The QuantaStor core services package is called qstorservice. It contains the service, database, and all the surrounding components that are required for the storage system to run. You can start and stop the QuantaStor service manually with these following commands respectively:
"sudo service quantastor stop" and
"sudo service quantastor start".
As part of the installation process the QuantaStor service is restarted and while it is starting up you will not have access to login to the storage system via the Web Management interface for about 60 seconds. Starting and stopping the QuantaStor service will in no way interrupt access to you iSCSI disks / storage volumes.

=== qstortarget ===
The QuantaStor iSCSI target is a customized version of the open source SCST driver and includes support for iSCSI, FC, and Infiniband. If you upgrade the target mode driver your system will continue to function normally but your new drivers will not become active until after you reboot. You can manually restart the driver like so:
<pre>
service iscsi-target restart
service quantastor restart
</pre>
=== qstortomcat ===
QuantaStor's web management interface is served by the Apache Tomcat web server. The Tomcat package is just an embedded packaging of the Tomcat web server plus our iptables configuration script. The web management interface packages are included in the qstormanager package.
=== qstormanager ===
The qstormanager package contains the QuantaStor Manager web management interface and it depends on the qstortomcat package. It depends on qstortomcat as it contains a specially configured version of Apache Tomcat which is installed to /opt/osnexus/quantastor/tomcat. The QuantaStor Manager package brings the Java servlet backend component that runs under Apache Tomcat as well as all the front-end QuantaStor Manager JavaScript that runs in the browser.

== Recommended Upgrade Method for Scale-Up Systems ==

=== Pre-Upgrade Checklist for Scale-Up ===
# It is recommended that you schedule a downtime work window, as '''a reboot will be required''' after a distro upgrade.
# For more complex upgrades we recommend scheduling time with OSNEXUS support for assistance
# Execute the distribution upgrade within a ‘screen’ session to prevent issues in case of network disconnection.
# It is advisable to stop clients from using the system, including stopping or pausing virtual machines that are consuming storage volumes presented from QuantaStor.
# Submit logs from all nodes to Support using the ‘[https://wiki.osnexus.com/index.php?title=Send_Support_Log_Files Send Support Logs]’ option in the WUI.
# Place the cluster into ‘[https://wiki.osnexus.com/index.php?title=Enter_Site_Cluster_Maintenance_Mode Maintenance Mode]’ to prevent automatic failover during the upgrade.
# For systems running 18.04 Bionic, it is required to upgrade through 20.04 Focal and then to 22.04 Jammy. To avoid any risks during the upgrade, it may be easier to make a backup of the osn.db and other relevant configuration files, and reinstall. OSNEXUS Support will best guide you on this.

=== Upgrade QuantaStor Version ===
OSNEXUS recommends that QuantaStor is upgraded to the most recent version with a full upgrade before performing a distribution upgrade. You can do this from the WUI (Web User Interface) using the ‘[[Upgrade Manager]]’ and specifying to include the kernel. A full upgrade, depending on the version you are originating from, may require a reboot. The WUI should inform you if this is the case, but it is generally a good idea to reboot the system anyway, just to ensure it can boot normally. This is good preparation for the distribution upgrade.

=== Upgrade Ubuntu OS Distribution ===
Note: This procedure upgrades the Ubuntu operating system to the next major version and updates QuantaStor to the latest release supported by that version.

To upgrade the distribution for QuantaStor Scale-Up systems, follow these steps:

'''Upgrade from 18.04 Bionic to 20.04 Focal'''

# Ensure that QuantaStor node is upgraded (including Kernel) to the most recent version using the ‘[[Upgrade Manager]]’
# Reboot to ensure that the system boots without an issue
# The site cluster HA (High Availability) between Bionic and Focal is not compatible. Site cluster VIFs must be deleted and migrated to local VIFs, along with deleting the site cluster configuration from all nodes.
# Ensure you are in a screen session as per the '''Pre-Upgrade Checklist for Scale-Up.'''
# Log in as root and execute the command '''''qs-distupgrade'''''.
# If you are not using ‘screen’, then you may be prompted "Do you want to continue without session continuation protection provided by the screen. (y/n) default: no ?", you can '''choose 'y' or 'n'. Please note that your input is taken straight away without pressing the Enter key'''.
# When asked "Do you want to proceed with the distribution upgrade for the base platform. (y/n) ?", '''type 'y'. Please note that your input is taken straight away without pressing the Enter key.'''
# When prompted "Do you wish to gather logs (y/n) Default:no ?", '''type 'y'. * Please note that your input is taken straight away without pressing the Enter key.'''
# Wait for the upgrade process to complete.
# Reboot the server. Check if the system comes online and is healthy (as confirmed with '''''qs-showlog -f''''' or in /var/log/qs/qs_service.log when the services start), then proceed to upgrade the other system.
# Repeat steps 1-10 on all nodes within the cluster.
# Once all systems are upgraded, do not recreate the cluster yet. Continue upgrading to 22.04 Jammy.

'''Upgrade from 20.04 Focal to 22.04 Jammy'''

# If you are upgrading from 18.04 Bionic to 20.04 Focal, do not recreate the cluster yet and skip steps 3 and 4. The cluster should only be recreated once all nodes have been upgraded to the latest OS and QuantaStor version. Otherwise, follow the procedure as documented.
# Ensure you are in a screen session as per the '''Pre-Upgrade Checklist for Scale-Up.'''
# For HA (High Availability) setup, via the WUI perform a failover of the pool(s) to one system before performing a full upgrade (including reboot).
# Place the cluster into ‘[https://wiki.osnexus.com/index.php?title=Enter_Site_Cluster_Maintenance_Mode Maintenance Mode]’.
# Ensure that QuantaStor node is upgraded (including Kernel) to the most recent version using the ‘[https://wiki.osnexus.com/index.php?title=Upgrade_Manager Upgrade Manager]’
# Log in as root and execute the command '''''qs-distupgrade'''''.
# If you are not using ‘screen’, then you may be prompted "Do you want to continue without session continuation protection provided by the screen. (y/n) default: no ?", you can '''choose 'y' or 'n'. Please note that your input is taken straight away without pressing the Enter key.'''
# When asked "Do you want to proceed with the distribution upgrade for the base platform. (y/n) ?", '''type 'y'. Please note that your input is taken straight away without pressing the Enter key.'''
# When prompted "Do you wish to gather logs (y/n) Default:no ?", '''type 'y'. * Please note that your input is taken straight away without pressing the Enter key.'''
# Wait for the upgrade process to complete.
# Reboot the server. Check if the system comes online and is healthy (as confirmed with '''''qs-showlog -f''''' or in /var/log/qs/qs_service.log when the services start), then proceed to upgrade the other system.
# Repeat steps 2-11 on all nodes within the cluster.

''* Gathering and submitting logs to OSNexus support will better assist in resolving any encountered issues.''

QuantaStor Upgrade Guide

2025-09-05T07:35:46Z

Joshua.blake:

QuantaStor is regularly evolving to add new features, make it more robust, and better performing. As such we release minor updates to QuantaStor on a regular basis and you can view the [http://www.osnexus.com/news News] section or review the [[QuantaStor Version ChangeLog|Change Log]] to get all the details about what has changed since the build that you're running.

== Web Based Upgrade Procedure ==

Upgrading QuantaStor to the latest version is made easy using the
[https://wiki.osnexus.com/index.php?title=Storage_System_Upgrade_Manager Storage System Upgrade Manager Dialog] that's integrated into the web management interface. Alternatively you can run this command to upgrade your system at the console or via an SSH session:

== Console Based Upgrade Procedure ==

<pre>
sudo qs-upgrade
</pre>

=== Upgrading Specific Components ===

<pre>
sudo apt-get update
sudo apt-get install qstormanager qstorservice qstortarget qstortomcat
</pre>

The qstormanager qstorservice qstortarget components are 'user-mode' and have no impact on workloads. The qstortarget package includes device drivers and should only be upgraded when you can take a maintenance window to reboot the appliance.

==== Details ====
The first part of the update process 'apt-get update' tells the system to update it's information about what packages are available from the OS NEXUS package server (http://packages.osnexus.com/packages). The second part tells the system to install the latest versions of the qstormanager, qstorservice, and qstortarget packages.

Often times an upgrade will only apply new qstormanager and qstorservice packages as it's fairly rare that we upgrade the driver package (qstortarget). Since upgrading drivers including the iSCSI target driver can interrupt iSCSI access to your volumes we always note in the ChangeLog which releases have driver and or kernel packages available.

==== Web UI Blank Screen ====

'''Important!''' After upgrading, be sure to clear the cache of any web browsers that were running the QuantaStor Manager web UI. If you don't clear the browser cache you'll end up using the cached copy of the UI which may not be compatible with the new version of the service.

==== Custom Configuration File Changes ====

On occasion we'll update the QuantaStor configuration file /etc/quantastor.conf and in such cases you'll get a message from the installer asking whether or not it's OK to overwrite the installed file with the package maintainers configuration file. This is to prevent the installer from overwriting your custom changes to the /etc/quantastor.conf file. If you've made changes to the /etc/quantastor.conf file then choose 'N' otherwise choose 'Y'. If you haven't made any changes, then it doesn't really matter, either choice is fine. The service has default settings built-in so the quantastor.conf configuration file is not required. If the file is missing or a new configuration setting is missing the QuantaStor service automatically uses it's own stored default which is fine for 99% of all configurations.

==== XenServer Virtual Appliance Upgrades ====
The one exception is the configuration file for the XenServer PV Virtual Appliance / VM. It requires that unidentifiable devices be usable, so it requires the 'allow_unident=1' setting which defaults to 'allow_unident=0'. So if you're upgrading a QuantaStor XenServer PV VM be sure to '''not''' overwrite the config file, and if you do, be sure to edit /etc/quantastor.conf to set the allow_unident configuration setting back to 1 otherwise your Physical Disks will not be discovered.

== Package Details ==

=== qstorservice ===
The QuantaStor core services package is called qstorservice. It contains the service, database, and all the surrounding components that are required for the storage system to run. You can start and stop the QuantaStor service manually with these following commands respectively:
"sudo service quantastor stop" and
"sudo service quantastor start".
As part of the installation process the QuantaStor service is restarted and while it is starting up you will not have access to login to the storage system via the Web Management interface for about 60 seconds. Starting and stopping the QuantaStor service will in no way interrupt access to you iSCSI disks / storage volumes.

=== qstortarget ===
The QuantaStor iSCSI target is a customized version of the open source SCST driver and includes support for iSCSI, FC, and Infiniband. If you upgrade the target mode driver your system will continue to function normally but your new drivers will not become active until after you reboot. You can manually restart the driver like so:
<pre>
service iscsi-target restart
service quantastor restart
</pre>
=== qstortomcat ===
QuantaStor's web management interface is served by the Apache Tomcat web server. The Tomcat package is just an embedded packaging of the Tomcat web server plus our iptables configuration script. The web management interface packages are included in the qstormanager package.
=== qstormanager ===
The qstormanager package contains the QuantaStor Manager web management interface and it depends on the qstortomcat package. It depends on qstortomcat as it contains a specially configured version of Apache Tomcat which is installed to /opt/osnexus/quantastor/tomcat. The QuantaStor Manager package brings the Java servlet backend component that runs under Apache Tomcat as well as all the front-end QuantaStor Manager JavaScript that runs in the browser.
== Pre-Upgrade Checklist for Scale-Up ==

# It is recommended that you schedule a downtime work window, as '''a reboot will be required''' after a distro upgrade.
# For more complex upgrades we recommend scheduling time with OSNEXUS support for assistance
# Execute the distribution upgrade within a ‘screen’ session to prevent issues in case of network disconnection.
# It is advisable to stop clients from using the system, including stopping or pausing virtual machines that are consuming storage volumes presented from QuantaStor.
# Submit logs from all nodes to Support using the ‘[https://wiki.osnexus.com/index.php?title=Send_Support_Log_Files Send Support Logs]’ option in the WUI.
# Place the cluster into ‘[https://wiki.osnexus.com/index.php?title=Enter_Site_Cluster_Maintenance_Mode Maintenance Mode]’ to prevent automatic failover during the upgrade.
# For systems running 18.04 Bionic, it is required to upgrade through 20.04 Focal and then to 22.04 Jammy. To avoid any risks during the upgrade, it may be easier to make a backup of the osn.db and other relevant configuration files, and reinstall. OSNEXUS Support will best guide you on this.

== Upgrade QuantaStor Version ==
OSNEXUS recommends that QuantaStor is upgraded to the most recent version with a full upgrade before performing a distribution upgrade. You can do this from the WUI (Web User Interface) using the ‘[[Upgrade Manager]]’ and specifying to include the kernel. A full upgrade, depending on the version you are originating from, may require a reboot. The WUI should inform you if this is the case, but it is generally a good idea to reboot the system anyway, just to ensure it can boot normally. This is good preparation for the distribution upgrade.

== Upgrade Ubuntu OS Distribution ==
Note: This procedure upgrades the Ubuntu operating system to the next major version and updates QuantaStor to the latest release supported by that version.

To upgrade the distribution for QuantaStor Scale-Up systems, follow these steps:

'''Upgrade from 18.04 Bionic to 20.04 Focal'''

# Ensure that QuantaStor node is upgraded (including Kernel) to the most recent version using the ‘[[Upgrade Manager]]’
# Reboot to ensure that the system boots without an issue
# The site cluster HA (High Availability) between Bionic and Focal is not compatible. Site cluster VIFs must be deleted and migrated to local VIFs, along with deleting the site cluster configuration from all nodes.
# Ensure you are in a screen session as per the '''Pre-Upgrade Checklist for Scale-Up.'''
# Log in as root and execute the command '''''qs-distupgrade'''''.
# If you are not using ‘screen’, then you may be prompted "Do you want to continue without session continuation protection provided by the screen. (y/n) default: no ?", you can '''choose 'y' or 'n'. Please note that your input is taken straight away without pressing the Enter key'''.
# When asked "Do you want to proceed with the distribution upgrade for the base platform. (y/n) ?", '''type 'y'. Please note that your input is taken straight away without pressing the Enter key.'''
# When prompted "Do you wish to gather logs (y/n) Default:no ?", '''type 'y'. * Please note that your input is taken straight away without pressing the Enter key.'''
# Wait for the upgrade process to complete.
# Reboot the server. Check if the system comes online and is healthy (as confirmed with '''''qs-showlog -f''''' or in /var/log/qs/qs_service.log when the services start), then proceed to upgrade the other system.
# Repeat steps 1-10 on all nodes within the cluster.
# Once all systems are upgraded, do not recreate the cluster yet. Continue upgrading to 22.04 Jammy.

'''Upgrade from 20.04 Focal to 22.04 Jammy'''

# If you are upgrading from 18.04 Bionic to 20.04 Focal, do not recreate the cluster yet and skip steps 3 and 4. The cluster should only be recreated once all nodes have been upgraded to the latest OS and QuantaStor version. Otherwise, follow the procedure as documented.
# Ensure you are in a screen session as per the '''Pre-Upgrade Checklist for Scale-Up.'''
# For HA (High Availability) setup, via the WUI perform a failover of the pool(s) to one system before performing a full upgrade (including reboot).
# Place the cluster into ‘[https://wiki.osnexus.com/index.php?title=Enter_Site_Cluster_Maintenance_Mode Maintenance Mode]’.
# Ensure that QuantaStor node is upgraded (including Kernel) to the most recent version using the ‘[https://wiki.osnexus.com/index.php?title=Upgrade_Manager Upgrade Manager]’
# Log in as root and execute the command '''''qs-distupgrade'''''.
# If you are not using ‘screen’, then you may be prompted "Do you want to continue without session continuation protection provided by the screen. (y/n) default: no ?", you can '''choose 'y' or 'n'. Please note that your input is taken straight away without pressing the Enter key.'''
# When asked "Do you want to proceed with the distribution upgrade for the base platform. (y/n) ?", '''type 'y'. Please note that your input is taken straight away without pressing the Enter key.'''
# When prompted "Do you wish to gather logs (y/n) Default:no ?", '''type 'y'. * Please note that your input is taken straight away without pressing the Enter key.'''
# Wait for the upgrade process to complete.
# Reboot the server. Check if the system comes online and is healthy (as confirmed with '''''qs-showlog -f''''' or in /var/log/qs/qs_service.log when the services start), then proceed to upgrade the other system.
# Repeat steps 2-11 on all nodes within the cluster.

''* Gathering and submitting logs to OSNexus support will better assist in resolving any encountered issues.''

Ubuntu Software RAID1 (UEFI)

2025-08-26T11:25:03Z

Joshua.blake:

'''NOTE''': This page is for older QuantaStor 4 and 5 deployments running on Ubuntu Bionic (18.04) and older, please see this page for [https://wiki.osnexus.com/index.php?title=QuantaStor_6_-_Software_RAID1_Install_Procedure deploying software RAID1 boot with QuantaStor 6 and newer].

Depending on the operating system, creating the software RAID1 is as easy as a few extra steps during the installation process.

Below are a few screenshots of the process to create a software RAID1 with QuantaStor on Ubuntu Bionic (18.04). The process is almost identical with QuantaStor on Ubuntu Xenial (16.04).

If you are familiar with creating partitions and would like to see the partition table summary, please see the below image. You may also finish the installation as normal and skip ahead to step 40. If you are not familiar with the partitions, follow the instructions below.

[[File:uefiraid40.png|600px]]

There should be four partitions per device, 1MB for the biosgrub (for UEFI and legacy boot), 512MB for the EFI boot, and two RAID partitions, sized accordingly, which will be eventually be put in a RAID to be used for the root filesystem and swap. Software RAID1 is expected to be used on each of the two RAID partitions per device.

=== Instructions ===

* '''Step 1''' - When you are prompted to install QuantaStor on a disk like below, press the ‘ESC’ key
[[File:uefiraid1.png|600px]]

* '''Step 2''' - Select the ‘Partition disks’ option and press the ‘Enter’ key
[[File:uefiraid2.png|600px]]

* '''Step 3''' - You’ll be presented with your disks, depending on whether there is existing data on them, you may need to wipe the partition table. Select your first RAID device, and press the ‘Enter’ key
[[File:uefiraid3.png|600px]]

* '''Step 4''' - Select ‘<Yes>’ and press the ‘Enter’ key
[[File:uefiraid4.png|600px]]

* '''Step 5''' - Do the same for the other RAID device you intend to use. You should now be presented with your RAID devices, and they should have “FREE SPACE” beside them. Select the area below the device, where you will see the “FREE SPACE” and press ‘Enter’
[[File:uefiraid5.png|600px]]

* '''Step 6''' - Press the ‘Enter’ key to select ‘Create a new partition’
[[File:uefiraid6.png|600px]]

* '''Step 7''' - For the first partition; which will be for biosboot and for UEFI plus legacy boot. It’s not required, but we recommend creating it anyway. Enter 1MB for the partition size and press ‘Enter’ to confirm
[[File:uefiraid7.png|600px]]

* '''Step 8''' - Press the ‘Enter’ key to select ‘Beginning’
[[File:uefiraid8.png|600px]]

* '''Step 9''' - Use ‘Reserved BIOS boot area’ and press the ‘Enter’ key on ‘Done setting up the partition’ to confirm
[[File:uefiraid9.png|600px]]

* '''Step 10''' - Select the available space on the device, and press the ‘Enter’ key
[[File:uefiraid10.png|600px]]

* '''Step 11''' - Press the ‘Enter’ key to create a new partition
[[File:uefiraid6.png|600px]]

* '''Step 12''' - For the second partition; which will be for the UEFI boot, we recommend using 512MB. Enter the value in the field and press the ‘Enter’ key
[[File:uefiraid12.png|600px]]

* '''Step 13''' - Press the ‘Enter’ key to select ‘Beginning’
[[File:uefiraid8.png|600px]]

* '''Step 14''' - Use ‘EFI System Partition’ and press the ‘Enter’ key on ‘Done setting up the partition’ to confirm
[[File:uefiraid14.png|600px]]

* '''Step 15''' - Select the available space on the device, and press the ‘Enter’ key
[[File:uefiraid15.png|600px]]

* '''Step 16''' - Press the ‘Enter’ key to create a new partition
[[File:uefiraid6.png|600px]]

* '''Step 17''' - For the third partition, which will be used as one of the two RAID volumes being created, using at least 80% of the device is a good general rule. Enter “80%” and press the ‘Enter’ key to confirm
[[File:uefiraid17.png|600px]]

* '''Step 18''' - Press the ‘Enter’ key to select ‘Beginning’
[[File:uefiraid8.png|600px]]

* '''Step 19''' - Use ‘physical volume for RAID’ and press the ‘Enter’ key on ‘Done setting up the partition’ to confirm
[[File:uefiraid19.png|600px]]

* '''Step 20''' - Select the remaining space on the device, and press the ‘Enter’ key
[[File:uefiraid20.png|600px]]

* '''Step 21''' - Press the ‘Enter’ key to create a new partition
[[File:uefiraid6.png|600px]]

* '''Step 22''' - For the fourth and final partition, press the ‘Enter’ key to confirm and use the remaining space on the device
[[File:uefiraid22.png|600px]]

* '''Step 23''' - Use ‘physical volume for RAID’ and press the ‘Enter’ key on ‘Done setting up the partition’ to confirm
[[File:uefiraid23.png|600px]]

* '''Step 24''' - Repeat the earlier steps and create the partitions on the other device. Select ‘Configure software RAID’ and press the ‘Enter’ key. If prompted to write changes, select ‘<Yes> and press ‘Enter’ to confirm
[[File:uefiraid24.png|600px]]

* '''Step 25''' - Press the ‘Enter’ key to create the first RAID volume
[[File:uefiraid25.png|600px]]

* '''Step 26''' - Select ‘RAID1’ and press the ‘Enter’ key to confirm
[[File:uefiraid26.png|600px]]

* '''Step 27''' - Check that the number of active devices is set to ‘2’ and press the ‘Enter’ key to confirm
[[File:uefiraid27.png|600px]]

* '''Step 28''' - Press the ‘Enter’ key to confirm 0 spare devices, unless spare devices are configured, then change the value accordingly
[[File:uefiraid28.png|600px]]

* '''Step 29''' - Select the third partitions created on each device. Press the ‘Enter’ key to confirm
[[File:uefiraid29.png|600px]]

* '''Step 30''' - Press the ‘Enter’ key to create the second RAID volume
[[File:uefiraid25.png|600px]]

* '''Step 31''' - Select ‘RAID1’ and press the ‘Enter’ key to confirm
[[File:uefiraid26.png|600px]]

* '''Step 32''' - Check that the number of active devices is set to ‘2’ and press the ‘Enter’ key to confirm
[[File:uefiraid27.png|600px]]

* '''Step 33''' - Press the ‘Enter’ key to confirm 0 spare devices, unless spare devices are configured, then change the value accordingly
[[File:uefiraid28.png|600px]]

* '''Step 34''' - Select the fourth partitions created on each device and press the ‘Enter’ key to confirm
[[File:uefiraid34.png|600px]]

* '''Step 35''' - Select ‘Finish’ and press ‘Enter’ to confirm
[[File:uefiraid35.png|600px]]

* '''Step 36''' - Select the empty space of the first RAID volume partition and press the ‘Enter’ key
[[File:uefiraid36.png|600px]]

* '''Step 37''' - Modify the parameters for the partition to ‘Ext4 journaling file system’ and ‘/’ like the below. Select ‘Done setting up the partition’ and press the ‘Enter’ key to confirm
[[File:uefiraid37.png|600px]]

* '''Step 38''' - Select the empty space of the second RAID volume partition and press the ‘Enter’ key
[[File:uefiraid38.png|600px]]

* '''Step 39''' - Modify the parameters for the partition to swap area’ like the below. Select ‘Done setting up the partition’ and press the ‘Enter’ key to confirm
[[File:uefiraid39new.png|600px]]

* '''Step 40''' - Select ‘Finish partitioning and write changes to disk’ and press the ‘Enter’ key to confirm. The system should now start to install
[[File:uefiraid40.png|600px]]

* '''Step 41''' - Log into the system, elevate to root and check the current efibootmgr details with <code>efibootmgr -v</code>. Make a note of the file name for the ubuntu boot entry. For example “\EFI\ubuntu\shimx64.efi”. You should see something like the below
<pre>
root@qs1:~# efibootmgr -v
BootCurrent: 0005
Timeout: 0 seconds
BootOrder: 0005,0000,0001,0004,0002,0003
Boot0000* UiApp FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(462caa21-7614-4503-836e-8ab6f4662331)
Boot0001* UEFI VBOX CD-ROM VB2-01700376 PciRoot(0x0)/Pci(0x1,0x1)/Ata(1,0,0)N.....YM....R,Y.
Boot0002* UEFI VBOX HARDDISK VBf65e2ed8-da02bb65 PciRoot(0x0)/Pci(0xd,0x0)/Sata(0,65535,0)N.....YM....R,Y.
Boot0003* UEFI VBOX HARDDISK VBb000695e-353e023b PciRoot(0x0)/Pci(0xd,0x0)/Sata(1,65535,0)N.....YM....R,Y.
Boot0004* EFI Internal Shell FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(7c04a583-9e3e-4f1c-ad65-e05268d0b4d1)
Boot0005* ubuntu HD(2,GPT,e0653691-0967-413a-8951-ad25478313fe,0x1000,0xf4000)/File(\EFI\ubuntu\shimx64.efi)
</pre>

* '''Step 42''' - Use <code>dd if=/dev/sda2 of=/dev/sdb2</code> to copy the second partition data from the first device to the second device. If your two devices are not sda or sdb, change these accordingly. You should see something like the below
<pre>
root@qs1:~# dd if=/dev/sda2 of=/dev/sdb2
999424+0 records in
999424+0 records out
511705088 bytes (512 MB, 488 MiB) copied, 62.5494 s, 8.2 MB/s
</pre>

* '''Step 43''' - Using the file name for the ubuntu boot entry from step 37, use <code>efibootmgr -c -d /dev/sdb -p 1 -L "ubuntu2" -l “\EFI\ubuntu\shimx64.efi”</code>. You should see something like the below

'''IMPORTANT NOTE''' - Replace /dev/sdb with your second boot device as this could be different. The “ubuntu2” can be of your choosing, and the location of the shimx64.efi may differ.

<pre>
root@qs1:~# efibootmgr -c -d /dev/sdb -p 1 -L "ubuntu2" -l “\EFI\ubuntu\shimx64.efi”
BootCurrent: 0005
Timeout: 0 seconds
BootOrder: 0006,0005,0000,0001,0004,0002,0003
Boot0000* UiApp
Boot0001* UEFI VBOX CD-ROM VB2-01700376
Boot0002* UEFI VBOX HARDDISK VBf65e2ed8-da02bb65
Boot0003* UEFI VBOX HARDDISK VBb000695e-353e023b
Boot0004* EFI Internal Shell
Boot0005* ubuntu
Boot0006* ubuntu2
</pre>

* '''Step 44''' - Check the RAID status for your partitions before rebooting the system with <code>cat /proc/mdstat</code> if everything is healthy, you should see something like the below
<pre>
root@qs1:~# cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md1 : active raid1 sda4[0] sdb4[1]
4090880 blocks super 1.2 [2/2] [UU]

md0 : active raid1 sda3[0] sdb3[1]
16365568 blocks super 1.2 [2/2] [UU]

unused devices: <none>
</pre>

If you run into any difficulties whilst following the below steps. Please contact support@osnexus.com for assistance.

Ubuntu Software RAID1 (UEFI)

2025-08-26T11:24:53Z

Joshua.blake:

NOTE: This page is for older QuantaStor 4 and 5 deployments running on Ubuntu Bionic (18.04) and older, please see this page for [https://wiki.osnexus.com/index.php?title=QuantaStor_6_-_Software_RAID1_Install_Procedure deploying software RAID1 boot with QuantaStor 6 and newer].

Depending on the operating system, creating the software RAID1 is as easy as a few extra steps during the installation process.

Below are a few screenshots of the process to create a software RAID1 with QuantaStor on Ubuntu Bionic (18.04). The process is almost identical with QuantaStor on Ubuntu Xenial (16.04).

If you are familiar with creating partitions and would like to see the partition table summary, please see the below image. You may also finish the installation as normal and skip ahead to step 40. If you are not familiar with the partitions, follow the instructions below.

[[File:uefiraid40.png|600px]]

There should be four partitions per device, 1MB for the biosgrub (for UEFI and legacy boot), 512MB for the EFI boot, and two RAID partitions, sized accordingly, which will be eventually be put in a RAID to be used for the root filesystem and swap. Software RAID1 is expected to be used on each of the two RAID partitions per device.

=== Instructions ===

* '''Step 1''' - When you are prompted to install QuantaStor on a disk like below, press the ‘ESC’ key
[[File:uefiraid1.png|600px]]

* '''Step 2''' - Select the ‘Partition disks’ option and press the ‘Enter’ key
[[File:uefiraid2.png|600px]]

* '''Step 3''' - You’ll be presented with your disks, depending on whether there is existing data on them, you may need to wipe the partition table. Select your first RAID device, and press the ‘Enter’ key
[[File:uefiraid3.png|600px]]

* '''Step 4''' - Select ‘<Yes>’ and press the ‘Enter’ key
[[File:uefiraid4.png|600px]]

* '''Step 5''' - Do the same for the other RAID device you intend to use. You should now be presented with your RAID devices, and they should have “FREE SPACE” beside them. Select the area below the device, where you will see the “FREE SPACE” and press ‘Enter’
[[File:uefiraid5.png|600px]]

* '''Step 6''' - Press the ‘Enter’ key to select ‘Create a new partition’
[[File:uefiraid6.png|600px]]

* '''Step 7''' - For the first partition; which will be for biosboot and for UEFI plus legacy boot. It’s not required, but we recommend creating it anyway. Enter 1MB for the partition size and press ‘Enter’ to confirm
[[File:uefiraid7.png|600px]]

* '''Step 8''' - Press the ‘Enter’ key to select ‘Beginning’
[[File:uefiraid8.png|600px]]

* '''Step 9''' - Use ‘Reserved BIOS boot area’ and press the ‘Enter’ key on ‘Done setting up the partition’ to confirm
[[File:uefiraid9.png|600px]]

* '''Step 10''' - Select the available space on the device, and press the ‘Enter’ key
[[File:uefiraid10.png|600px]]

* '''Step 11''' - Press the ‘Enter’ key to create a new partition
[[File:uefiraid6.png|600px]]

* '''Step 12''' - For the second partition; which will be for the UEFI boot, we recommend using 512MB. Enter the value in the field and press the ‘Enter’ key
[[File:uefiraid12.png|600px]]

* '''Step 13''' - Press the ‘Enter’ key to select ‘Beginning’
[[File:uefiraid8.png|600px]]

* '''Step 14''' - Use ‘EFI System Partition’ and press the ‘Enter’ key on ‘Done setting up the partition’ to confirm
[[File:uefiraid14.png|600px]]

* '''Step 15''' - Select the available space on the device, and press the ‘Enter’ key
[[File:uefiraid15.png|600px]]

* '''Step 16''' - Press the ‘Enter’ key to create a new partition
[[File:uefiraid6.png|600px]]

* '''Step 17''' - For the third partition, which will be used as one of the two RAID volumes being created, using at least 80% of the device is a good general rule. Enter “80%” and press the ‘Enter’ key to confirm
[[File:uefiraid17.png|600px]]

* '''Step 18''' - Press the ‘Enter’ key to select ‘Beginning’
[[File:uefiraid8.png|600px]]

* '''Step 19''' - Use ‘physical volume for RAID’ and press the ‘Enter’ key on ‘Done setting up the partition’ to confirm
[[File:uefiraid19.png|600px]]

* '''Step 20''' - Select the remaining space on the device, and press the ‘Enter’ key
[[File:uefiraid20.png|600px]]

* '''Step 21''' - Press the ‘Enter’ key to create a new partition
[[File:uefiraid6.png|600px]]

* '''Step 22''' - For the fourth and final partition, press the ‘Enter’ key to confirm and use the remaining space on the device
[[File:uefiraid22.png|600px]]

* '''Step 23''' - Use ‘physical volume for RAID’ and press the ‘Enter’ key on ‘Done setting up the partition’ to confirm
[[File:uefiraid23.png|600px]]

* '''Step 24''' - Repeat the earlier steps and create the partitions on the other device. Select ‘Configure software RAID’ and press the ‘Enter’ key. If prompted to write changes, select ‘<Yes> and press ‘Enter’ to confirm
[[File:uefiraid24.png|600px]]

* '''Step 25''' - Press the ‘Enter’ key to create the first RAID volume
[[File:uefiraid25.png|600px]]

* '''Step 26''' - Select ‘RAID1’ and press the ‘Enter’ key to confirm
[[File:uefiraid26.png|600px]]

* '''Step 27''' - Check that the number of active devices is set to ‘2’ and press the ‘Enter’ key to confirm
[[File:uefiraid27.png|600px]]

* '''Step 28''' - Press the ‘Enter’ key to confirm 0 spare devices, unless spare devices are configured, then change the value accordingly
[[File:uefiraid28.png|600px]]

* '''Step 29''' - Select the third partitions created on each device. Press the ‘Enter’ key to confirm
[[File:uefiraid29.png|600px]]

* '''Step 30''' - Press the ‘Enter’ key to create the second RAID volume
[[File:uefiraid25.png|600px]]

* '''Step 31''' - Select ‘RAID1’ and press the ‘Enter’ key to confirm
[[File:uefiraid26.png|600px]]

* '''Step 32''' - Check that the number of active devices is set to ‘2’ and press the ‘Enter’ key to confirm
[[File:uefiraid27.png|600px]]

* '''Step 33''' - Press the ‘Enter’ key to confirm 0 spare devices, unless spare devices are configured, then change the value accordingly
[[File:uefiraid28.png|600px]]

* '''Step 34''' - Select the fourth partitions created on each device and press the ‘Enter’ key to confirm
[[File:uefiraid34.png|600px]]

* '''Step 35''' - Select ‘Finish’ and press ‘Enter’ to confirm
[[File:uefiraid35.png|600px]]

* '''Step 36''' - Select the empty space of the first RAID volume partition and press the ‘Enter’ key
[[File:uefiraid36.png|600px]]

* '''Step 37''' - Modify the parameters for the partition to ‘Ext4 journaling file system’ and ‘/’ like the below. Select ‘Done setting up the partition’ and press the ‘Enter’ key to confirm
[[File:uefiraid37.png|600px]]

* '''Step 38''' - Select the empty space of the second RAID volume partition and press the ‘Enter’ key
[[File:uefiraid38.png|600px]]

* '''Step 39''' - Modify the parameters for the partition to swap area’ like the below. Select ‘Done setting up the partition’ and press the ‘Enter’ key to confirm
[[File:uefiraid39new.png|600px]]

* '''Step 40''' - Select ‘Finish partitioning and write changes to disk’ and press the ‘Enter’ key to confirm. The system should now start to install
[[File:uefiraid40.png|600px]]

* '''Step 41''' - Log into the system, elevate to root and check the current efibootmgr details with <code>efibootmgr -v</code>. Make a note of the file name for the ubuntu boot entry. For example “\EFI\ubuntu\shimx64.efi”. You should see something like the below
<pre>
root@qs1:~# efibootmgr -v
BootCurrent: 0005
Timeout: 0 seconds
BootOrder: 0005,0000,0001,0004,0002,0003
Boot0000* UiApp FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(462caa21-7614-4503-836e-8ab6f4662331)
Boot0001* UEFI VBOX CD-ROM VB2-01700376 PciRoot(0x0)/Pci(0x1,0x1)/Ata(1,0,0)N.....YM....R,Y.
Boot0002* UEFI VBOX HARDDISK VBf65e2ed8-da02bb65 PciRoot(0x0)/Pci(0xd,0x0)/Sata(0,65535,0)N.....YM....R,Y.
Boot0003* UEFI VBOX HARDDISK VBb000695e-353e023b PciRoot(0x0)/Pci(0xd,0x0)/Sata(1,65535,0)N.....YM....R,Y.
Boot0004* EFI Internal Shell FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(7c04a583-9e3e-4f1c-ad65-e05268d0b4d1)
Boot0005* ubuntu HD(2,GPT,e0653691-0967-413a-8951-ad25478313fe,0x1000,0xf4000)/File(\EFI\ubuntu\shimx64.efi)
</pre>

* '''Step 42''' - Use <code>dd if=/dev/sda2 of=/dev/sdb2</code> to copy the second partition data from the first device to the second device. If your two devices are not sda or sdb, change these accordingly. You should see something like the below
<pre>
root@qs1:~# dd if=/dev/sda2 of=/dev/sdb2
999424+0 records in
999424+0 records out
511705088 bytes (512 MB, 488 MiB) copied, 62.5494 s, 8.2 MB/s
</pre>

* '''Step 43''' - Using the file name for the ubuntu boot entry from step 37, use <code>efibootmgr -c -d /dev/sdb -p 1 -L "ubuntu2" -l “\EFI\ubuntu\shimx64.efi”</code>. You should see something like the below

'''IMPORTANT NOTE''' - Replace /dev/sdb with your second boot device as this could be different. The “ubuntu2” can be of your choosing, and the location of the shimx64.efi may differ.

<pre>
root@qs1:~# efibootmgr -c -d /dev/sdb -p 1 -L "ubuntu2" -l “\EFI\ubuntu\shimx64.efi”
BootCurrent: 0005
Timeout: 0 seconds
BootOrder: 0006,0005,0000,0001,0004,0002,0003
Boot0000* UiApp
Boot0001* UEFI VBOX CD-ROM VB2-01700376
Boot0002* UEFI VBOX HARDDISK VBf65e2ed8-da02bb65
Boot0003* UEFI VBOX HARDDISK VBb000695e-353e023b
Boot0004* EFI Internal Shell
Boot0005* ubuntu
Boot0006* ubuntu2
</pre>

* '''Step 44''' - Check the RAID status for your partitions before rebooting the system with <code>cat /proc/mdstat</code> if everything is healthy, you should see something like the below
<pre>
root@qs1:~# cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md1 : active raid1 sda4[0] sdb4[1]
4090880 blocks super 1.2 [2/2] [UU]

md0 : active raid1 sda3[0] sdb3[1]
16365568 blocks super 1.2 [2/2] [UU]

unused devices: <none>
</pre>

If you run into any difficulties whilst following the below steps. Please contact support@osnexus.com for assistance.

Ubuntu Software RAID1 (UEFI)

2025-08-26T11:24:21Z

Joshua.blake:

NOTE: This page is for older QuantaStor 4 and 5 deployments running on Ubuntu Bionic and older, please see this page for [https://wiki.osnexus.com/index.php?title=QuantaStor_6_-_Software_RAID1_Install_Procedure deploying software RAID1 boot with QuantaStor 6 and newer].

Depending on the operating system, creating the software RAID1 is as easy as a few extra steps during the installation process.

Below are a few screenshots of the process to create a software RAID1 with QuantaStor on Ubuntu Bionic. The process is almost identical with QuantaStor on Ubuntu Xenial.

If you are familiar with creating partitions and would like to see the partition table summary, please see the below image. You may also finish the installation as normal and skip ahead to step 40. If you are not familiar with the partitions, follow the instructions below.

[[File:uefiraid40.png|600px]]

There should be four partitions per device, 1MB for the biosgrub (for UEFI and legacy boot), 512MB for the EFI boot, and two RAID partitions, sized accordingly, which will be eventually be put in a RAID to be used for the root filesystem and swap. Software RAID1 is expected to be used on each of the two RAID partitions per device.

=== Instructions ===

* '''Step 1''' - When you are prompted to install QuantaStor on a disk like below, press the ‘ESC’ key
[[File:uefiraid1.png|600px]]

* '''Step 2''' - Select the ‘Partition disks’ option and press the ‘Enter’ key
[[File:uefiraid2.png|600px]]

* '''Step 3''' - You’ll be presented with your disks, depending on whether there is existing data on them, you may need to wipe the partition table. Select your first RAID device, and press the ‘Enter’ key
[[File:uefiraid3.png|600px]]

* '''Step 4''' - Select ‘<Yes>’ and press the ‘Enter’ key
[[File:uefiraid4.png|600px]]

* '''Step 5''' - Do the same for the other RAID device you intend to use. You should now be presented with your RAID devices, and they should have “FREE SPACE” beside them. Select the area below the device, where you will see the “FREE SPACE” and press ‘Enter’
[[File:uefiraid5.png|600px]]

* '''Step 6''' - Press the ‘Enter’ key to select ‘Create a new partition’
[[File:uefiraid6.png|600px]]

* '''Step 7''' - For the first partition; which will be for biosboot and for UEFI plus legacy boot. It’s not required, but we recommend creating it anyway. Enter 1MB for the partition size and press ‘Enter’ to confirm
[[File:uefiraid7.png|600px]]

* '''Step 8''' - Press the ‘Enter’ key to select ‘Beginning’
[[File:uefiraid8.png|600px]]

* '''Step 9''' - Use ‘Reserved BIOS boot area’ and press the ‘Enter’ key on ‘Done setting up the partition’ to confirm
[[File:uefiraid9.png|600px]]

* '''Step 10''' - Select the available space on the device, and press the ‘Enter’ key
[[File:uefiraid10.png|600px]]

* '''Step 11''' - Press the ‘Enter’ key to create a new partition
[[File:uefiraid6.png|600px]]

* '''Step 12''' - For the second partition; which will be for the UEFI boot, we recommend using 512MB. Enter the value in the field and press the ‘Enter’ key
[[File:uefiraid12.png|600px]]

* '''Step 13''' - Press the ‘Enter’ key to select ‘Beginning’
[[File:uefiraid8.png|600px]]

* '''Step 14''' - Use ‘EFI System Partition’ and press the ‘Enter’ key on ‘Done setting up the partition’ to confirm
[[File:uefiraid14.png|600px]]

* '''Step 15''' - Select the available space on the device, and press the ‘Enter’ key
[[File:uefiraid15.png|600px]]

* '''Step 16''' - Press the ‘Enter’ key to create a new partition
[[File:uefiraid6.png|600px]]

* '''Step 17''' - For the third partition, which will be used as one of the two RAID volumes being created, using at least 80% of the device is a good general rule. Enter “80%” and press the ‘Enter’ key to confirm
[[File:uefiraid17.png|600px]]

* '''Step 18''' - Press the ‘Enter’ key to select ‘Beginning’
[[File:uefiraid8.png|600px]]

* '''Step 19''' - Use ‘physical volume for RAID’ and press the ‘Enter’ key on ‘Done setting up the partition’ to confirm
[[File:uefiraid19.png|600px]]

* '''Step 20''' - Select the remaining space on the device, and press the ‘Enter’ key
[[File:uefiraid20.png|600px]]

* '''Step 21''' - Press the ‘Enter’ key to create a new partition
[[File:uefiraid6.png|600px]]

* '''Step 22''' - For the fourth and final partition, press the ‘Enter’ key to confirm and use the remaining space on the device
[[File:uefiraid22.png|600px]]

* '''Step 23''' - Use ‘physical volume for RAID’ and press the ‘Enter’ key on ‘Done setting up the partition’ to confirm
[[File:uefiraid23.png|600px]]

* '''Step 24''' - Repeat the earlier steps and create the partitions on the other device. Select ‘Configure software RAID’ and press the ‘Enter’ key. If prompted to write changes, select ‘<Yes> and press ‘Enter’ to confirm
[[File:uefiraid24.png|600px]]

* '''Step 25''' - Press the ‘Enter’ key to create the first RAID volume
[[File:uefiraid25.png|600px]]

* '''Step 26''' - Select ‘RAID1’ and press the ‘Enter’ key to confirm
[[File:uefiraid26.png|600px]]

* '''Step 27''' - Check that the number of active devices is set to ‘2’ and press the ‘Enter’ key to confirm
[[File:uefiraid27.png|600px]]

* '''Step 28''' - Press the ‘Enter’ key to confirm 0 spare devices, unless spare devices are configured, then change the value accordingly
[[File:uefiraid28.png|600px]]

* '''Step 29''' - Select the third partitions created on each device. Press the ‘Enter’ key to confirm
[[File:uefiraid29.png|600px]]

* '''Step 30''' - Press the ‘Enter’ key to create the second RAID volume
[[File:uefiraid25.png|600px]]

* '''Step 31''' - Select ‘RAID1’ and press the ‘Enter’ key to confirm
[[File:uefiraid26.png|600px]]

* '''Step 32''' - Check that the number of active devices is set to ‘2’ and press the ‘Enter’ key to confirm
[[File:uefiraid27.png|600px]]

* '''Step 33''' - Press the ‘Enter’ key to confirm 0 spare devices, unless spare devices are configured, then change the value accordingly
[[File:uefiraid28.png|600px]]

* '''Step 34''' - Select the fourth partitions created on each device and press the ‘Enter’ key to confirm
[[File:uefiraid34.png|600px]]

* '''Step 35''' - Select ‘Finish’ and press ‘Enter’ to confirm
[[File:uefiraid35.png|600px]]

* '''Step 36''' - Select the empty space of the first RAID volume partition and press the ‘Enter’ key
[[File:uefiraid36.png|600px]]

* '''Step 37''' - Modify the parameters for the partition to ‘Ext4 journaling file system’ and ‘/’ like the below. Select ‘Done setting up the partition’ and press the ‘Enter’ key to confirm
[[File:uefiraid37.png|600px]]

* '''Step 38''' - Select the empty space of the second RAID volume partition and press the ‘Enter’ key
[[File:uefiraid38.png|600px]]

* '''Step 39''' - Modify the parameters for the partition to swap area’ like the below. Select ‘Done setting up the partition’ and press the ‘Enter’ key to confirm
[[File:uefiraid39new.png|600px]]

* '''Step 40''' - Select ‘Finish partitioning and write changes to disk’ and press the ‘Enter’ key to confirm. The system should now start to install
[[File:uefiraid40.png|600px]]

* '''Step 41''' - Log into the system, elevate to root and check the current efibootmgr details with <code>efibootmgr -v</code>. Make a note of the file name for the ubuntu boot entry. For example “\EFI\ubuntu\shimx64.efi”. You should see something like the below
<pre>
root@qs1:~# efibootmgr -v
BootCurrent: 0005
Timeout: 0 seconds
BootOrder: 0005,0000,0001,0004,0002,0003
Boot0000* UiApp FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(462caa21-7614-4503-836e-8ab6f4662331)
Boot0001* UEFI VBOX CD-ROM VB2-01700376 PciRoot(0x0)/Pci(0x1,0x1)/Ata(1,0,0)N.....YM....R,Y.
Boot0002* UEFI VBOX HARDDISK VBf65e2ed8-da02bb65 PciRoot(0x0)/Pci(0xd,0x0)/Sata(0,65535,0)N.....YM....R,Y.
Boot0003* UEFI VBOX HARDDISK VBb000695e-353e023b PciRoot(0x0)/Pci(0xd,0x0)/Sata(1,65535,0)N.....YM....R,Y.
Boot0004* EFI Internal Shell FvVol(7cb8bdc9-f8eb-4f34-aaea-3ee4af6516a1)/FvFile(7c04a583-9e3e-4f1c-ad65-e05268d0b4d1)
Boot0005* ubuntu HD(2,GPT,e0653691-0967-413a-8951-ad25478313fe,0x1000,0xf4000)/File(\EFI\ubuntu\shimx64.efi)
</pre>

* '''Step 42''' - Use <code>dd if=/dev/sda2 of=/dev/sdb2</code> to copy the second partition data from the first device to the second device. If your two devices are not sda or sdb, change these accordingly. You should see something like the below
<pre>
root@qs1:~# dd if=/dev/sda2 of=/dev/sdb2
999424+0 records in
999424+0 records out
511705088 bytes (512 MB, 488 MiB) copied, 62.5494 s, 8.2 MB/s
</pre>

* '''Step 43''' - Using the file name for the ubuntu boot entry from step 37, use <code>efibootmgr -c -d /dev/sdb -p 1 -L "ubuntu2" -l “\EFI\ubuntu\shimx64.efi”</code>. You should see something like the below

'''IMPORTANT NOTE''' - Replace /dev/sdb with your second boot device as this could be different. The “ubuntu2” can be of your choosing, and the location of the shimx64.efi may differ.

<pre>
root@qs1:~# efibootmgr -c -d /dev/sdb -p 1 -L "ubuntu2" -l “\EFI\ubuntu\shimx64.efi”
BootCurrent: 0005
Timeout: 0 seconds
BootOrder: 0006,0005,0000,0001,0004,0002,0003
Boot0000* UiApp
Boot0001* UEFI VBOX CD-ROM VB2-01700376
Boot0002* UEFI VBOX HARDDISK VBf65e2ed8-da02bb65
Boot0003* UEFI VBOX HARDDISK VBb000695e-353e023b
Boot0004* EFI Internal Shell
Boot0005* ubuntu
Boot0006* ubuntu2
</pre>

* '''Step 44''' - Check the RAID status for your partitions before rebooting the system with <code>cat /proc/mdstat</code> if everything is healthy, you should see something like the below
<pre>
root@qs1:~# cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md1 : active raid1 sda4[0] sdb4[1]
4090880 blocks super 1.2 [2/2] [UU]

md0 : active raid1 sda3[0] sdb3[1]
16365568 blocks super 1.2 [2/2] [UU]

unused devices: <none>
</pre>

If you run into any difficulties whilst following the below steps. Please contact support@osnexus.com for assistance.