Package: libparted2
Severity: grave
With a 'fake RAID' RAID0 device constructed using motherboard firmware,
which has a GPT partitioning table setup using fdisk (gparted failed me
- see #778683), opening gparted now results in errors in relation to the
RAID member disks.
Specifically, I firstly get the following error regarding the first disk
in the RAID array:
Title: Libparted bug found!
Message: Invalid argument during seek for read on /dev/sdb
Clicking on 'ignore' then results in this followup message:
Title: Libparted bug found!
Message: The backup GPT table is corrupt, but the primary appears OK, so
that will be used.
fdisk seems perfectly happy with the setup. Presumably libparted is not
processing the member disks as actually being part of an array.
Marking as grave on the off chance of data loss with libparted not
processing things properly here, and the possibility of users fiddling
with things in gparted in relation to it (e.g. trying to correct the
'unrecognised partition table' status of member disks, wiping out their
array.
Should array members even be listed in gparted?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
