** Changed in: partman-md (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1028677
Title:
mdadm should be used for fakeraid (instead of dmraid)
To manage n
** Attachment removed: "9A9E9871BAFD82D7.jpg"
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1028677/+attachment/4930725/+files/9A9E9871BAFD82D7.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
** Attachment removed: "35324259F192B015F0A1268765F023DE.jpg"
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1028677/+attachment/4912009/+files/35324259F192B015F0A1268765F023DE.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
** Attachment removed: "34FA0C76F7D8764FA2D3E075E88F3194.jpg"
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1028677/+attachment/4909919/+files/34FA0C76F7D8764FA2D3E075E88F3194.jpg
** Attachment removed: "1012B0581A606EFCF4CE59003639DAF5.jpg"
https://bugs.launchpad.net/ubuntu/+source
At the moment mdadm with imsm metadata is totally broken on xenial (and
I suspect on all ubuntu distros with systemd). Due to incorrect ordering
of things at shutdown machines with arrays assembled at boot with mdadm
and imsm metadata may hang and the array is resynced everytime even if
the bios sh
Here are a set of notes I made for myself because I did this often
enough I didn't want to forget. I hope this helps.
-John
New procedure for using Ubuntu Desktop installer (until they fix it)
1) Launch UEFI setup at star
Just attempted this without much thinking:
http://pastebin.com/eWy2n0hq
Similar situation as reported by b-candler.
Upon reboot after that, the system root drive was /dev/sda ,/dev/sdb
unused.
If I try to force an mdadm assemble, it only pulls in /dev/sdb since sda is in
use by the operating sy
What is the latest here? I've spent an hour scouring forums and other
such places in an attempt to find concise instructions on how to migrate
an existing system running "FakeRAID" (raid1) from dmraid to mdadm.
If no such documentation exists, I'd be more than happy to create it,
however I will ne
I see this issue is addressed in latest 14.04 ubuntu and bahavior is
changed, at least on new installations it is default to mdadm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1028677
Title:
mdadm
I have a 12.04 system with fakeraid for the root partition across
/dev/sda and /dev/sdb. I want to convert it from using dmraid to mdadm
(so I can monitor it with /proc/mdstat for instance)
mdadm is 3.2.5, and it says in the manpage it can understand ddf and
imsm metadata, and this indeed seems to
@Dmitrijs: I totally agree with your comment #8
It seems that something is moving in debian about fakeraid & mdadm: they
have working patches, see their bug 699434,
http://bugs.debian.org/699434, and metabug 699430
http://bugs.debian.org/699430.
** Bug watch added: Debian Bug tracker #699434
@Andreas the idea is transition to mdadm for those formats that it does
support and continue using dmraid for the rest.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1028677
Title:
mdadm should be u
Well, I think it would be nice to replace dmraid sometime in the future
with mdadm, however, first mdadm would need to support most devices from
dmraid like e.g. also the Promise Fasttrak Metadata (after all those are
used for AMD RAID controller)
--
You received this bug notification because you
also dmraid make ubiquity crash when dualbooting with intel smart
response technology powered windows. (see bug marked as duplicate)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1028677
Title:
mdad
Just for reference, #957494 is an incomplete fix for the readonly issue
mentioned above. mdmon is still missing in the initrd which leads to
read-only arrays. Inclusion of mdmon into the image fixes this. However,
system shutdown is still broken in this case.
--
You received this bug notification
It is critical to replace dmraid with mdadm as dmraid is unable to deal
with large disk sizes. For a 3TB imsm raid1 dual-boot ('fakeraid') in my
case the disks were shown as ~746GB sized and dmraid -an would not
release them. So the only way was to boot the live cd with nodmraid and
manually instal
Ok. Both ubiquity and the debian-installer use a piece of software for
partitioning collectively known as partman.
Partman has many "plugins" for setting up different file systems and
things.
Partman-md is a single package which handles mdadm based RAID.
Partman-md upstream is at:
Vcs-Browser:
** Also affects: partman-md (Ubuntu)
Importance: Undecided
Status: New
** Changed in: debian-installer (Ubuntu)
Status: New => Invalid
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
** Changed in: partman-md (Ubuntu)
Status: New => Confirmed
--
You recei
Well, alternate cd has mdadm, but it isn't used for fakeraid.
If you setup a fakeraid volume from the bios, and then start a new install, you
are forced to use dmraid.
If you don't setup a raid volume with the bios, you are offered the chance of
setup a linux software raid with mdadm, but this i
I was under impression that alternative/server CDs did offer mdadm, and
supported activating dmraid.
** Also affects: debian-installer (Ubuntu)
Importance: Undecided
Status: New
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mdadm (Ubuntu)
20 matches
Mail list logo
