I'm new to launchpad, but I've been using Ubuntu personally and at work for
many years now. I never had this problem until yesterday.
A 250GB Disk with Ubuntu 14.04 32bit installed. Put it into a new computer
which is capable of 64bit. Realized that a reinstall would be the best option
and
If you no longer wish to use the drives in raid mode, you must destroy
the raid volume with either the bios utility, or dmraid -E.
** Changed in: ubiquity (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hahahaha!
Being Aug.2013 and this problem/bug remains the same :D
openSUSE installs easily in that hdd with raid, but it does not detect any
windows to dual boot.
Ubuntu's 12.04, 12.10 and 13.04 just do not see any hdd/partition. Really sad.
I will have to backup Windows and try to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubiquity (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/573618
Title:
** Tags added: ubiquity-2.2.23
** Tags added: lucid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/573618
Title:
Installer does not detect hard drive partitions
To manage notifications about this
I have add this bug on two different computers (one never had any raid
activated) with 2 versions of ubuntu : 10.10 and 11.04.
I am quite disappointed by Ubuntu, seeing as this bug is not even taken care
of, more than a year later.
Especially since it breaks user experience so bad.
Meanwhile
In my case, I had two WD 160GB SATA HDD's that had been part of a
Asus/Promise raid configuration on another system, that I wanted to
reuse again on newer systems used for Ubuntu/Windows dual boot. I had to
both go back and use the BIOS raid setup on that older system to remove
them from the raid
I just installed a completely new hard drive in my system (I guess it
has no RAID fingerprints on it by default that I have to delete), booted
with the Kubuntu-10.10 CD and... run into just this bug again. Too
bad...
--
Installer does not detect hard drive partitions
See this bug that has been determined (correctly, I think) to be not a
dmraid bug https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/543008
My particular experience was quite a surprise and wasted a lot of time.
Some details are in that bug report.
dmraid decided that my (only) disk was part
The solution in this link (sudo apt-get remove dmraid) worked for me,
however the nodmraid boot option didn't (assuming I did it correctly).
At least one of the drives in the system has been used for RAID in the
past which likely explains the cause. There is perhaps a problem though
that
Today I had a similar experience and so did:
http://www.longren.org/2010/05/11/how-to-make-ubuntu-recognize-all-
drives-during-install/
I had to remove dmraid from the livecd session to see all the drives in
my computer. Even though I don' use raid!
--
Installer does not detect hard drive
** Attachment added: syslog
http://launchpadlibrarian.net/47243096/syslog
--
Installer does not detect hard drive partitions
https://bugs.launchpad.net/bugs/573618
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: partman
http://launchpadlibrarian.net/47243135/partman
--
Installer does not detect hard drive partitions
https://bugs.launchpad.net/bugs/573618
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
13 matches
Mail list logo