Fiest 7.01 installation disk partition util broke
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ubiquity (Ubuntu) |
Invalid
|
Undecided
|
Colin Watson | ||
Bug Description
Fiest 7.01 Herd 4 installation disk partition util doesnt work for me when i have both of my Sata drives plugged in at the same time.
In edgy 6.01 it didnt have any problems detecting both drives(both 80 gig maxtor sata drives on my built in Nvidia raid controller), and showing the correct information and giving me the normal choices for partitioning.
In feist herd 4, the partitioner loads after a long delay, with corrupt information on the first disk(sata0), which has a windows install on it, as well as on (sata1) that has been formated with a linux file system. It never gives me the choice for manual or guided install. It starts giving me the choice to write the changes that have already ben made, which are jiberish lol.
If i unplug one of the drives, the partitioner seems to load normally in good time, giving me the option to use guided or manual install like i believe is the norm.
Sorry for the lack of technical information, Again, it worked ok in Edgy.
I havent tryed fiesty herd 1,2 or 3 yet so i cant know if it workes then.
| Changed in ubiquity: | |
| status: | Incomplete → Invalid |

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http:// wiki.ubuntu. com/DebuggingKe rnelProblems . Thanks in advance!