[Bug 1074606] Re: gparted identifying incorrect raid arrays

Phillip Susi psusi at ubuntu.com
Mon Dec 3 19:34:11 UTC 2012


** Branch linked: lp:~psusi/ubuntu/quantal/gparted/drop-swraid

** Changed in: gparted (Ubuntu Quantal)
       Status: New => In Progress

** Changed in: gparted (Ubuntu Quantal)
     Assignee: (unassigned) => Phillip Susi (psusi)

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gparted in Ubuntu.
https://bugs.launchpad.net/bugs/1074606

Title:
  gparted identifying incorrect raid arrays

Status in Gnome Partition Editor:
  Confirmed
Status in “gparted” package in Ubuntu:
  In Progress
Status in “gparted” source package in Quantal:
  In Progress

Bug description:
  On startup, gparted complains with several popups that it has an
  internal parted bug trying to stat /dev/md/XXXX.  This appears to be
  caused by its reliance on running mdadm --examine --scan to identify
  raid arrays.  Recent versions of mdadm now report the existence of
  "containers" that are not usable block devices, but gparted thinks
  they are.  It also reports the preferred major number rather than the
  actual.  In other words, if the metadata says it is supposed to be
  /dev/md0, that is what mdadm reports, however it may have been
  activated as /dev/md127 instead, causing gparted to try to use a
  device that does not exist.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gparted/+bug/1074606/+subscriptions




More information about the foundations-bugs mailing list