** No longer affects: null
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742145
Title:
dmraid interferes with mdadm
To manage notifications about this bug go to:
Well, looks like it, yes.
I ended up completely nulling out the HD's because dmraid kept refusing
deleting both the RAID set (can't be done for DDF1) and the metadata
(gave errors no matter what) and completely rebuilding the array again.
Problem is resolved now.
Although it continues to elude
hm. Since that is not the case, I'm rather suspicious of messing with my
metadata ;-) I'll try that tonight, after backing up everything on the
disks.
And/or perhaps I'll try reproducing this in a VM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Wait, is the raid bios intel, or adaptec? Adaptec uses DDF, so if you
set it up with the adaptec bios, that would explain it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742145
Title:
dmraid
The mobo is a SuperMicro one with a very very weird option to choose (I
kid you not) between Intel MSM or Adaptec BIOS for the SATA ports.
However, neither have been active to my knowledge, certainly not in a
RAID6 config, as neither support this.
It is unlikely but possible I once configured a
It looks like at some point you had the Adaptec bios enabled and created
a raid array named bigass and then disabled the bios, leaving the ddf
metadata on the disks. Erasing it will resolve your issue. I will
close this bug now.
** Changed in: dmraid (Ubuntu)
Status: Incomplete =
root@ubuntu:/lib/udev# dmraid -r
/dev/sdh: ddf1, .ddf1_disks, GROUP, ok, 3906572288 sectors, data@ 0
/dev/sdg: ddf1, .ddf1_disks, GROUP, ok, 3906572288 sectors, data@ 0
/dev/sdf: ddf1, .ddf1_disks, GROUP, ok, 3906572288 sectors, data@ 0
/dev/sde: ddf1, .ddf1_disks, GROUP, ok, 3906572288 sectors,
Also, note that the attached Debian bug 534274 reports the same issue,
but fails to consider my scenario as a valid setup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742145
Title:
dmraid
** Tags added: mdadm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/742145
Title:
dmraid interferes with mdadm
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ddf is an ataraid metadata format. I believe that recently mdadm has
added support for it as well, but it is not mdadm's native format and
used to only be handled by dmraid. How did you build this raid array?
Also you said you upgraded from lucid to natty, but this is not directly
possible. Did
That debian bug is actually unrelated. It is about a set of disks that
already is being used as part of a dmraid array and the person also
wanted to use them as part of an mdadm array, which is an invalid
configuration. In your case, you have an array that is using a format
that is now
11 matches
Mail list logo
