Ubuntu 8.10 kills WinXP on SATA RAID array without warning.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Installation environment: Gigabyte GA-EP45-UD3R motherboard with:
Intel ICH10R chipset.
Memory: 4GB
Drives configured as:
SATA-1 & SATA-2 ==> RAID (2 x 75GB) configured as Vol 0
SATA-3 ==> STD IDE, 1TB - unused/empty
SATA-4 ==> STD IDE, 1TB - unused/empty
Existing Software Configuration:
1. Windows XP already installed on SATA-1&2/RAID, formatted as FAT32, and configured to dual-boot with Win98 DOS.
2. Aim to put Ubuntu 8.10 on one or other spare/empty drives (but not on RAID Vol-0).
Results:
3. Ubuntu couldn't recognize the RAID drive/configura
4. Ubuntu gave no warning that it was about to attempt a write to an unknown configuration (even though it warned of the unrecognized drive(s)--displayed numerous errors).
5. The RAID configuration was destroyed (the WinXP &DOS partition damaged and the WinXP/DOS installation lost).
6. After the attempted Ubuntu installation, the RAID BIOS reported that [only] disk 0 RAID configuration was faulty.
Whilst nuking Windows installations appeals to my sensibility, I at least want to control the process. (Ubuntu gave no inkling that it was going to do so).
Similarly, on non-RAID Win/NTFS installations the Ubuntu partitioner also gives no warning (it implies it will install on the partition but it doesn't warn that everything on the partition will be destroyed*). Ubuntu's superlative ability to kill Windows without warning has led to a blanket ban on any Linux disks being allowed into my IT environment, Not a good way to win friends and influence people, let alone convert Windows users over to Ubuntu.
* Keep in mind that many Windows users are familiar with Linux installations that install on existing Windows/NTFS partitions without damaging them, thus they wrongly assume the Ubuntu partitioner is just preparing the existing partition for its installation (rather than destroying it and remaking a Linux one). Clearly, Ubuntu needs to issue dire warnings before destroying existing data.
P.S.: Despite having to select "I Don't Know" to the question about the version number (in order that this brain-dead form allow this bug to be submitted), the Ubuntu version number is 8.10 (reported in 'About'). It is the 32-bit version of a commercial double-sided disk (64-bit on the flipside) that came with a current issue of Linux Magazine.
What options did you choose in the installer?