[Bug 1074606] Re: gparted raid wrong information

[Phillip Susi]

** Bug watch added: GNOME Bug Tracker #678379
   https://bugzilla.gnome.org/show_bug.cgi?id=678379

** Also affects: gparted via
   https://bugzilla.gnome.org/show_bug.cgi?id=678379
   Importance: Unknown
       Status: Unknown

** Changed in: gparted (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gparted (Ubuntu)
       Status: Invalid => Triaged

** Summary changed:

- gparted raid wrong information
+ gparted identifying incorrect raid arrays

** Description changed:

- Hi,
- 
- I have noticed that information about raid (in my case raid0 arrays) are
- completely wrong.
- 
- Partition name is wrong - !!!  it is always adding 'p1' at the end of the device name (partition). 
- Label is wrong - is not detected at all.
- flags is empty
- Managed flags is empty.
- used and unused is empty.
- 
- The thing is that I am normally running on that OS instance without any
- problem. Fsck saying it is clean.
- 
- lsb_release -rd
- Description:	Ubuntu 12.10
- Release:	12.10
- 
- apt-cache policy gparted
- gparted:
-   Installed: 0.14.0-1~getdeb1
-   Candidate: 0.14.0-1~getdeb1
-   Version table:
-  *** 0.14.0-1~getdeb1 0
-         500 http://archive.getdeb.net/ubuntu/ quantal-getdeb/apps amd64 Packages
-         100 /var/lib/dpkg/status
-      0.12.1-1 0
-         500 http://archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages
- 
- apt-cache policy libparted0debian1
- libparted0debian1:
-   Installed: 2.3-10ubuntu2
-   Candidate: 2.3-10ubuntu2
-   Version table:
-  *** 2.3-10ubuntu2 0
-         500 http://archive.ubuntu.com/ubuntu/ quantal/main amd64 Packages
-         100 /var/lib/dpkg/status
- 
- This errors have apperead in the previous versions of gparted as well
- BUT not all of them. From the version 14 release it is all information
- wrong and it is not even possible to change them. It is only valid for
- raid0 arrays. I am not aware of if those errors appeared on other raid
- level configurations.
- 
- Let me know if you need more information.
- 
- 
- Regards,
- M.
+ 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.

-- 
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:
  Unknown
Status in “gparted” package in Ubuntu:
  Triaged

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