Description of problem: Tool is unable to create old fashion partition table on raid device (both msdos or gpt), only LVM partitioning is available. Version-Release number of selected component (if applicable): Version 0.23. Built on Wed Sep 10 13:43:38 UTC 2014.
Could you describe the symptoms further. Did an error occur? Did cockpit just ignore your wishes? Was there no option in the UI? Could you attach a screenshot? Thanks.
Created attachment 939236 [details] Snapshot1
Created attachment 939237 [details] Snapshot2
There are requested snapshot of "Format" menu. There is missing option in UI. For example something like DOS partition (not recomended for devices larger than 2TB) and GPT (up to 9.4 ZB) similary like you have done it for simple disks. There is option format RAID as extended partition (which is imho bit weird) but this option ends with error. (see attachment) Currently UI allows only LVM partitioning or formating whole device with some filesystem.
Thank you for the information! You can put a partition table on a RAID Device with Cockpit with the "Format" action of the whole device at the very top of the page. It's in the same menu as "Start" and "Stop". This is a confusing place for this option, and we should move it down to the "Content" panel. I have files https://github.com/cockpit-project/cockpit/issues/1304 for this. > There is option format RAID as extended partition (which is imho bit weird) > but this option ends with error. Yes, we should enable "Extended Partition" only for MBR partition tables. https://github.com/cockpit-project/cockpit/issues/1305 https://github.com/cockpit-project/cockpit/issues/1306
Some of the issues have been fixed upstream.
Marius is this now fixed in recent Cockpit releases?
(In reply to Stef Walter from comment #7) > Marius is this now fixed in recent Cockpit releases? No, unfortunately not. Creating a partition on a RAID device was always possible, but it is still hard to discover. We dropped the ball on this.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.