Description of problem: Try to create software RAID from blivet-gui Version-Release number of selected component: anaconda-core-37.6-1.fc37.x86_64 The following was filed automatically by anaconda: anaconda 37.6 exception report Traceback (most recent call first): File "/usr/lib/python3.10/site-packages/blivetgui/osinstall.py", line 234, in _reraise_exception raise type(exception)(message + str(exception) + "\n" + traceback) File "/usr/lib/python3.10/site-packages/blivetgui/blivetgui.py", line 509, in add_device self._reraise_exception(result.exception, result.traceback, message, blivet.errors.PartitioningError: Failed to add the device:requested size exceeds maximum allowed Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/blivetgui/blivet_utils.py", line 1323, in add_device blivet.partitioning.do_partitioning(self.storage) File "/usr/lib/python3.10/site-packages/blivet/partitioning.py", line 618, in do_partitioning allocate_partitions(storage, disks, partitions, free, boot_disk=boot_disk) File "/usr/lib/python3.10/site-packages/blivet/partitioning.py", line 1007, in allocate_partitions partition = add_partition(disklabel, free, part_type, aligned_size, File "/usr/lib/python3.10/site-packages/blivet/partitioning.py", line 463, in add_partition raise PartitioningError(_("requested size exceeds maximum allowed")) blivet.errors.PartitioningError: requested size exceeds maximum allowed Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda --liveinst --graphical cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-WS-Live-rawh-20220429-n-0 rd.live.image rd.live.check quiet dnf.librepo.log: executable: /sbin/anaconda hashmarkername: anaconda kernel: 5.18.0-0.rc4.20220428git8f4dd16603ce834.36.fc37.x86_64 other involved packages: blivet-gui-runtime-2.3.0-5.fc37.noarch product: Fedora release: Fedora release 37 (Rawhide) release_type: pre-release type: anaconda version: rawhide
Created attachment 1876434 [details] File: anaconda-tb
Created attachment 1876435 [details] File: anaconda.log
Created attachment 1876436 [details] File: dbus.log
Created attachment 1876437 [details] File: environ
Created attachment 1876438 [details] File: journalctl
Created attachment 1876439 [details] File: lsblk_output
Created attachment 1876440 [details] File: nmcli_dev_list
Created attachment 1876441 [details] File: os_info
Created attachment 1876442 [details] File: program.log
Created attachment 1876443 [details] File: storage.log
Created attachment 1876444 [details] why I unnable create 8Tb RAID0 from two nvme ?
Similar problem has been detected: Try to create software RAID from blivet-gui addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda --liveinst --graphical cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-WS-Live-rawh-20220429-n-0 rd.live.image rd.live.check quiet dnf.librepo.log: hashmarkername: anaconda kernel: 5.18.0-0.rc4.20220428git8f4dd16603ce834.36.fc37.x86_64 other involved packages: blivet-gui-runtime-2.3.0-5.fc37.noarch package: anaconda-core-37.6-1.fc37.x86_64 packaging.log: product: Fedora reason: blivet.errors.PartitioningError: Failed to add the device:requested size exceeds maximum allowed release: Fedora release 37 (Rawhide) release_type: pre-release version: rawhide
Similar problem has been detected: Try to create btrfs volume from blivet-gui addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda --liveinst --graphical cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-WS-Live-rawh-20220429-n-0 rd.live.image rd.live.check quiet dnf.librepo.log: hashmarkername: anaconda kernel: 5.18.0-0.rc4.20220428git8f4dd16603ce834.36.fc37.x86_64 other involved packages: blivet-gui-runtime-2.3.0-5.fc37.noarch package: anaconda-core-37.6-1.fc37.x86_64 packaging.log: product: Fedora reason: blivet.errors.PartitioningError: Failed to add the device:requested size exceeds maximum allowed release: Fedora release 37 (Rawhide) release_type: pre-release version: rawhide
Created attachment 1876445 [details] why I unnable create 8Tb BTRFS volume from two nvme ?
You have an MSDOS partition table on the disks which can address only up to 2 TiB of space, blivet-gui shouldn't allow you to create a new partition past the 2 TiB mark (a probably should also show a warning when you try to use MSDOS on disk bigger than 2 TiB). If you want to use the entire disk you need to use the GPT partition table.
Created attachment 1876447 [details] screencast (In reply to Vojtech Trefny from comment #15) > You have an MSDOS partition table on the disks which can address only up to > 2 TiB of space, blivet-gui shouldn't allow you to create a new partition > past the 2 TiB mark (a probably should also show a warning when you try to > use MSDOS on disk bigger than 2 TiB). If you want to use the entire disk you > need to use the GPT partition table. At first I wanted to create a RAID using the BIOS (RAIDXpert2). But booting into Linux, I realized that Linux does not see the volume created in this way. A quick googling made it clear AMD RAID is not supported by the kernel. And it looks like it will never be supported out of the box. It was decided to create a software raid. Therefore, I booted from a bootable flash drive and deleted the rubbish that RAIDXpert2 apparently created in blivet-gui. There were no warnings when I started creating new RAID volume using blivet-gui. As it turned out later, if I deleting the rubbish partitions via gnome-disks, then blivet-gui starts working correctly. You can see it all in my video.
This bug appears to have been reported against 'rawhide' during the Fedora Linux 37 development cycle. Changing version to 37.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on None. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.