This bug was fixed in the package dmraid - 1.0.0.rc15-11ubuntu1
---
dmraid (1.0.0.rc15-11ubuntu1) karmic; urgency=low
* debian/dmraid-activate: Remove the special-casing of the root
device which breaks in many situations and leaves the raw devices
exposed. This was
** Changed in: dmraid (Debian)
Status: New = Fix Released
--
Dual-boot install using mdadm root fails to boot
https://bugs.launchpad.net/bugs/392510
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Branch linked: lp:~tormodvolden/dmraid/karmic
--
Dual-boot install using mdadm root fails to boot
https://bugs.launchpad.net/bugs/392510
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
In the hope of getting this fixed for Karmic...
** Attachment added: dmraid_1.0.0.rc15-11ubuntu1.debdiff
http://launchpadlibrarian.net/32454945/dmraid_1.0.0.rc15-11ubuntu1.debdiff
--
Dual-boot install using mdadm root fails to boot
https://bugs.launchpad.net/bugs/392510
You received this bug
Forgot to change maintainer.
** Attachment added: dmraid_1.0.0.rc15-11ubuntu1.debdiff
http://launchpadlibrarian.net/32455567/dmraid_1.0.0.rc15-11ubuntu1.debdiff
--
Dual-boot install using mdadm root fails to boot
https://bugs.launchpad.net/bugs/392510
You received this bug notification
Tormod Volden ha scritto:
I reopen this bug so don't lose it off the radar. Giuseppe, do you have
any comments here or on the Debian bug?
I already cherry-picked your [f333bc0] (nodmraid boot option), but I have some
doubts about [54b8d6f]. Reverting that change will break all broken
I reopen this bug so don't lose it off the radar. Giuseppe, do you have
any comments here or on the Debian bug?
** Changed in: dmraid (Ubuntu)
Status: Fix Released = Confirmed
--
Dual-boot install using mdadm root fails to boot
https://bugs.launchpad.net/bugs/392510
You received this bug
We have to fix this. It also kicks in when booting a Desktop CD on a
machine which has dmraid disks. The raw partitions on the dmraid disk
will not be hidden as they should, and show up in the file browser. If
the user now double-clicks on one it will be mounted as a normal
partition and the RAID
I pushed a fix here http://git.debian.org/?p=users/tormod-
guest/dmraid.git;a=summary
--
Dual-boot install using mdadm root fails to boot
https://bugs.launchpad.net/bugs/392510
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I haven't looked deeply into the mdraid/dmraid conflict, but if I understand
correctly, the patch
- was added to accommodate broken setups which we do not want to support
- breaks (with possible data-loss) valid setups (as in my example above)
--
Dual-boot install using mdadm root fails to boot
Tormod Volden ha scritto:
With and /home on dmraid on two other disks /dev/sda and /dev/sdb I
meant that /dev/sdaX and /dev/sdbX will be part of a dmraid array. But
/dev/sdc which contains my root is not part of an array.
Ok, then /dev/sdc will not be removed.
Then Christian and other
Ok, then /dev/sdc will not be removed.
If I understand Use the -Z flag only if root partition is mountd in a
dmraid array. correctly, the partitions on the two (dmraid member)
disks /dev/sda and /dev/sdb will be exposed, in my example above. This
is why I think this patch is wrong.
I don't
Tormod Volden ha scritto:
Ok, then /dev/sdc will not be removed.
If I understand Use the -Z flag only if root partition is mountd in a
dmraid array. correctly, the partitions on the two (dmraid member)
disks /dev/sda and /dev/sdb will be exposed, in my example above. This
is why I think
In your example above, if your /dev/sdc is not part of an array, kernel will
not
remove it. If it happens this is a bug.
If /dev/sda and /dev/sdb are part of an array, they will be removed, and this
is
*not* a bug, why it should be..?
This is what I do not understand. The way I read the
Tormod Volden ha scritto:
In your example above, if your /dev/sdc is not part of an array, kernel will
not
remove it. If it happens this is a bug.
If /dev/sda and /dev/sdb are part of an array, they will be removed, and
this is
*not* a bug, why it should be..?
This is what I do not
I am not happy with this solution. What if I have / on one disk /dev/sdc
and /home on dmraid on two other disks /dev/sda and /dev/sdb? I think my
motherboard and BIOS would allow this. I would sure want /dev/sdaX and
/dev/sdbX to be hidden by the -Z flag.
What I think should be done instead:
1)
Tormod Volden ha scritto:
I am not happy with this solution. What if I have / on one disk /dev/sdc
and /home on dmraid on two other disks /dev/sda and /dev/sdb? I think my
motherboard and BIOS would allow this. I would sure want /dev/sdaX and
/dev/sdbX to be hidden by the -Z flag.
if
if /dev/sdaX and /dev/sdbX aren't part of a dmraid array kernel will
not remove them.
With and /home on dmraid on two other disks /dev/sda and /dev/sdb I
meant that /dev/sdaX and /dev/sdbX will be part of a dmraid array. But
/dev/sdc which contains my root is not part of an array.
It is
This bug was fixed in the package dmraid - 1.0.0.rc15-10build1
---
dmraid (1.0.0.rc15-10build1) karmic; urgency=low
* Fake sync with Debian.
dmraid (1.0.0.rc15-10) unstable; urgency=low
* [1a1b752] debian/dmraid-activate: Use the -Z flag only if root
partition is mountd in
What you have to understand is that DMRAID is just a driver for the bios
raid setups.
When you create a RAID from the BIOS it does a RAID1 or whatever on the
entire array using all the drives you select. You cant do a partial bios
raid setup as this is illogical.
When you use mdadm to create a
Yes, i understand that it's a driver for BIOS magic that i'd rather not
use.
When you create a RAID from the BIOS it does a RAID1 or whatever on the
entire array using all the drives you select. You cant do a partial bios
raid setup as this is illogical.
Is there a usage scenario where this
That wiki page is a little old: https://wiki.ubuntu.com/DmraidSupport
Ubuntu must support it if its in the installer CD and in the main repos so I'm
unsure if that is just outdated like most of the online documentation.
I have been using dmraid (and bios raid) for years and have had no
issues so
Interesting, thanks for the info. Sorry to flog this to death.
Online ubuntu docs with respect to dmraid are definitely somewhat
scattered and of varying levels of authority. From a naive newer is
better perspective, the page you mention was last edited 2008-08-06,
long before jaunty went live,
I want to reiterate that the original bug was reported against the
_alternate_ install cd. If i understand correctly, the alternate
install cd is required to install using any raid functionality. The
initramfs installed by the alternate cd included mdadm, which was
unexpectedly difficult to
A conf file might be a nice workaround and should keep everyone happy.
So I would vote option 2 although support would still be fairly limited.
--
Dual-boot install using mdadm root fails to boot
https://bugs.launchpad.net/bugs/392510
You received this bug notification because you are a member
** Bug watch added: Debian Bug tracker #534274
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534274
** Also affects: dmraid (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534274
Importance: Unknown
Status: Unknown
--
Dual-boot install using mdadm root fails to
** Changed in: dmraid (Debian)
Status: Unknown = New
--
Dual-boot install using mdadm root fails to boot
https://bugs.launchpad.net/bugs/392510
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hi,
Tormod Volden ha scritto:
Luke and danwood76, it seems like you haven't read the original bug
report correctly. He does not want to use dmraid in Linux, only his
Windows partition uses dmraid. His problem is that dmraid is
The dmraid-activate script uses the newly introduced -Z flag to
After you apt-get remove you must rebuild the initramfs (sudo update-
initramfs -u -k all), as described in my post. From your post it sounds
like the uninstall from apt will remove the initramfs hooks just not
rebuild the array.
As luke said you have one or the other, there is no advantage of
Luke and danwood76, it seems like you haven't read the original bug
report correctly. He does not want to use dmraid in Linux, only his
Windows partition uses dmraid. His problem is that dmraid is
unconditionally installed when a fakeraid is detected on his disks.
And clearly it must be a bug
After reading the bug more deeply Giuseppe states that it does invoke
the update-initramfs but only on the latest kernel.
The thing I dont understand is why you would want to use mdadm and
dmraid together, each provides the same functionality although dmraid
allows you to boot off of RAIDs other
You cannot have mdadm and dmraid co-exist, unless the mdadm partitions
and the dmraid array are on separate drives. YOu can only have one or
the other.
So if you have WIndows sitting on fakeraid/dmraid array, you install
Ubuntu using the laternate CD, and when it asks for you to activate the
SATA
Just to reiterate, I achieved the desired results described in the
original bug after extensive research, trial and error before i filed
the bug.
To get rid of dmraid you just don't install it. The live cd doesn't
have the dmraid package preloaded
Ok. But that's not at issue. The alternate
To get rid of dmraid you just don't install it.
The live cd doesn't have the dmraid package preloaded and I'm sure getting rid
of dmraid is as simple as un-installing it through apt and rebuilding the
initramfs. (2 commands from the terminal)
This is no bug in dmraid.
--
Dual-boot install
Also you could purge the fakeraid from the drives by clearing the
metadata at the end of the disks and then dmraid wouldn't even load.
--
Dual-boot install using mdadm root fails to boot
https://bugs.launchpad.net/bugs/392510
You received this bug notification because you are a member of Ubuntu
35 matches
Mail list logo
