Public bug reported:
Hardware RAID controller, disabled in card BIOS (no volumes in array),
two HD's connected, both at same size, working as normal IDE A and B
with completely different partitions.
Fdisk -l after booting from desktop CD shows both drives as expected
(sda/sdb with all partitions), gparted looks fine, too. No RAID mapping,
no fakeraid, normal IDE behaviour.
Starting installation and choosing manual partitioning shows only first
drive as mapped devices. After installation sdb became a real clone of
sda and both are combined as a RAID array (I tested with forensics, the
contents are the same on both disks).
I expected the same behavior as netboot and alternate install offers:
You have to activate RAID *manually*. Automatic activation of RAID array
(how? controller is still "unconfigured" in its BIOS) may be highly
insecure for unexperienced users because of the risk of data loss. What
confuses me is that the methods for experienced users (alternate/PXE)
contain a simple switch, while the way to work around under graphical
interface is uninstalling dmraid in the running live system via aptitude
and remove dm_raid45 module afterwards manually. Then both disks will
show as expected in manual partitioning.
If it's not a bug but a feature, it should be clearly documented in the
installation process I think.
** Affects: ubuntu
Importance: Undecided
Status: New
** Description changed:
Hardware RAID controller, disabled in card BIOS (no volumes in array),
two HD's connected, both at same size, working as normal IDE A and B
with completely different partitions.
Fdisk -l after booting from desktop CD shows both drives as expected
(sda/sdb with all partitions), gparted looks fine, too. No RAID mapping,
no fakeraid, normal IDE behaviour.
Starting installation and choosing manual partitioning shows only first
drive as mapped devices. After installation sdb became a real clone of
sda and both are combined as a RAID array (I tested with forensics, the
contents are the same on both disks).
I expected the same behavior as netboot and alternate install offers:
You have to activate RAID *manually*. Automatic activation of RAID array
- (how? controller is still "unconfigured" in its BIOS) is highly insecure
- for unexperienced users because of the risk of data loss. What confuses
- me is that the methods for experienced users (alternate/PXE) contain a
- simple switch, while the way to work around under graphical interface is
- uninstalling dmraid in the running live system via aptitude and remove
- dm_raid45 module afterwards manually. Then both disks will show as
- expected in manual partitioning.
+ (how? controller is still "unconfigured" in its BIOS) may be highly
+ insecure for unexperienced users because of the risk of data loss. What
+ confuses me is that the methods for experienced users (alternate/PXE)
+ contain a simple switch, while the way to work around under graphical
+ interface is uninstalling dmraid in the running live system via aptitude
+ and remove dm_raid45 module afterwards manually. Then both disks will
+ show as expected in manual partitioning.
If it's not a bug but a feature, it should be clearly documented in the
installation process I think.
--
Hardware RAID enabled without confirmation in desktop install
https://bugs.launchpad.net/bugs/592892
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
