I added to
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/573618
--
Ubiquity can't find the sata hard disk (promise 376 chip)
https://bugs.launchpad.net/bugs/543008
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
As already stated this is no bug in dmraid!
Also this is not a support forum!
To detect if there is a promise array disk dmraid scans the metadata offsets
for "Promise Technology, Inc."
This string has to be on the disks at that specific location on the disks you
have and this is created by the
My problem is that the system won't boot if the hard drive don't have the
"raid" metadata... in earlier versions of Ubuntu this was not a problem...
I wish I can send you my computer so you can use it like a rat-lab, THEN you
can said is a problem that can't be solved in dmraid... but if you only
I see no value in insults.
I hit this problem. It is real. This launchpad entry helped me work
around the problem. I expect never to hit it again. I'm here to help
make things better for other Ubuntu users.
My disk drive has never been used in RAID and yet dmraid detected that it had.
How co
This is not a bug in dmraid.
It is just the way it works.
If your drives have the promise metadata on them they must have been used for
that purpose.
It can't just magically appear on the disk. You probably have setup the disks
in the proimise BIOS controller!
--
Ubiquity can't find the sata h
Attempting to insult me with diagnosis you seem to be a psychiatrist.
Hope you are not.
I think this bug related to dmraid. Hard drives never been powered on,
BIOS never been configured to support RAID. I see that with my eyes at
least on 4 completely new parts.
Ok, I'll ask ubiquity developers t
Attempting to insult me by association with another entity you seem to
have a pathological hatred for is a violation of the Ubuntu Code of
Conduct. I suggest you find a better outlet for your frustration.
What you might do is file a feature enhancement request for ubiquity to
show disks that are
@Phillip Susi, millions of potential Ubuntu users thanks you. Seems like
you are working for MS. I meet this bug with three last releases at home
computer, and four computers at lab where I work. Thank you again, next
release we meet the same (at least 2 y.o. bug).
People, seems we must go to #ubi
** Changed in: dmraid (Ubuntu)
Status: Confirmed => Invalid
--
Ubiquity can't find the sata hard disk (promise 376 chip)
https://bugs.launchpad.net/bugs/543008
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
I experienced this too when trying to install Ubuntu 10.04 i386
(released version).
My computer is an old eMachine, with the original disk. It has never
been RAIDed. Heck, the machine doesn't have the appropriate controller
and has never had a second drive.
I had a difficult time figuring out w
After erasing the metadata you need to restart your machine so that dmraid is
unloaded and the disk is allowed to be sda.
So boot with the live CD and erase the metadata, reboot, then install.
--
Ubiquity can't find the sata hard disk (promise 376 chip)
https://bugs.launchpad.net/bugs/543008
You
The problem is that when the metadata is erased, Ubuntu installs correctly
but after the reboot it won't boot, it seems that the configuration requires
that the array is present (even if not used like array)...
But I repeat the nodmraid option in the livecd should be exactly that,
disable the dmra
Then your belief that the drive has never been part of a raid array
seems to be incorrect. If you reinstall dmraid and run sudo dmraid -n
/dev/sda ( assuming that sda is the drive in question ) and it prints
out the metadata, then the drive was, and for our purposes, still is,
part of a raid array
I have the same issue. MSI K7N2 Delta-ILSR with one 300GB SATA drive on
the Promise controller integrated into the motherboard. The drive has
never been part of a RAID array, it's just set up on the controller so
that the rest of the system can see it. The 10.04 installer (and 9.10)
doesn't see the
Fresh install Lucid 10.04 (release) on MSI G33M MS-7357 ver 1 caused
the same bug. Removing 'dmraid' package solved problem.
** Changed in: dmraid (Ubuntu)
Status: Invalid => Confirmed
--
Ubiquity can't find the sata hard disk (promise 376 chip)
https://bugs.launchpad.net/bugs/543008
You
AFAIK, the nodmraid boot option just prevents dmraid from being run to
activate raid arrays. Removing the package should have no further
effect beyond that. blkid should still identify the drive as a raid
member, which I believe causes the installer to not show it.
--
Ubiquity can't find the sa
Ok, lets guess that is a misconfiguration of my system, but isn't
supposed that the nodmraid option should ignore the metadata of the
drrive? or disable it self (dmraid) so it can work like is not
installed?
Why I have to uninstall/remove/purge dmraid to be able to make it work
like it always work
I'm marking this bug as invalid since this is a system configuration
error, not a bug. I believe that Ubiquity intentionally does not
display disks that have been identified by blkid as members of a dmraid
set, since you are supposed to use the raid device, not the underlying
physical disks. At a
** Description changed:
Binary package hint: dmraid
I'm trying to install Ubuntu 10.04 Beta 1, but the installer do not
detect the hard drive I have. In LiveCD mode I can see, mount and work
with the partitions of my hard drive but the installer just don't see
it...
My motherboar
Tried to boot with the 'nodmraid' option and it didn't work,
I remove the raid using the bios utility, but it didn't work,
then I erase the metadata using the -E swith of dmraid and It works, it shows
up in ubiquity, and was able to install Ubuntu, but is by far more easy to
simply uninstall dmr
Yes, if you previously used the disks in raid mode and no longer wish
you, then you need to remove the raid metadata from the disks by either
destroying the raid set with the bios utility, or the -E switch to
dmraid. Simply disabling the raid mode in the bios leaves the metadata
on disk and the bi
Sometimes dmraid finds metadata when it shouldn't (either because of
previous uses of dmraid, or because of a bug). Have you tried booting
with the 'nodmraid' option? It's on the F6 menu on the live CD because
some people need this.
Your syslog confirms this:
Mar 20 20:54:59 ubuntu activate-d
** Description changed:
- Binary package hint: ubiquity
+ Binary package hint: dmraid
I'm trying to install Ubuntu 10.04 Beta 1, but the installer do not
detect the hard drive I have. In LiveCD mode I can see, mount and work
with the partitions of my hard drive but the installer just don'
** Description changed:
Binary package hint: ubiquity
I'm trying to install Ubuntu 10.04 Beta 1, but the installer do not
detect the hard drive I have. In LiveCD mode I can see, mount and work
with the partitions of my hard drive but the installer just don't see
it...
Maybe is th
** Attachment added: "/var/log/partman"
http://launchpadlibrarian.net/41454093/partman
--
Ubiquity can't find the sata hard disk (promise 376 chip)
https://bugs.launchpad.net/bugs/543008
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "/var/log/syslog"
http://launchpadlibrarian.net/41454085/syslog
--
Ubiquity can't find the sata hard disk (promise 376 chip)
https://bugs.launchpad.net/bugs/543008
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "/var/log/installer/debug"
http://launchpadlibrarian.net/41454022/debug
--
Ubiquity can't find the sata hard disk (promise 376 chip)
https://bugs.launchpad.net/bugs/543008
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
** Attachment added: "Here are the files /var/log/syslog
/var/log/installer/debug /var/log/partman"
http://launchpadlibrarian.net/41453782/debuginfo.tar.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/41451007/Dependencies.txt
** Attachment removed: "Here are the
28 matches
Mail list logo
