Processing control commands:
severity -1 normal
Bug #778712 [libparted2] libparted2: Breakage of RAID GPT header
Severity set to 'normal' from 'grave'
close -1
Bug #778712 [libparted2] libparted2: Breakage of RAID GPT header
Marked Bug as done
--
778712: http://bugs.debian.org/cgi-bin
Control: severity -1 normal
Control: close -1
thanks
On Fri, 2015-02-20 at 15:12 -0500, Phillip Susi wrote:
I'm sorry; I misread what you said. I thought you said you had
removed the information about the individual disks that were members
of the array.
No problem.
At this point the array
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/19/2015 2:24 PM, jnqnfe wrote:
Firstly, I am not running fdisk or parted on the raw member disks,
I am simply running generic 'fdisk -l' and 'parted -l' commands,
which return information about all disks. To simplify matters I
removed
On Fri, 2015-02-20 at 10:16 -0500, Phillip Susi wrote:
On 2/19/2015 2:24 PM, jnqnfe wrote:
Firstly, I am not running fdisk or parted on the raw member disks,
I am simply running generic 'fdisk -l' and 'parted -l' commands,
which return information about all disks. To simplify matters I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/20/2015 12:17 PM, jnqnfe wrote:
What? I very carefully went through every one of them before
sending to ensure that only information about the array (md126) and
the array members (sdb and sdc) were included. I have just checked
back over
On Wed, 2015-02-18 at 23:27 -0500, Phillip Susi wrote:
All of the error messages shown in the logs you sent so far involve
the raw disks ( sdb, etc ) rather than the raid array. You certainly
should not be running fdisk or parted on the raw disk, and responding
to the error messages by saying
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/18/2015 4:05 PM, jnqnfe wrote:
Background = I have a 'fake-raid' RAID0 array,
created from two HDDs using my motherboard firmware. This is not
used for root, just data.
FYI, unless you have to dual boot with windows, you
Package: libparted2
Version: 3.2-6
Severity: grave
libparted2 breaks my RAID GPT header!
There appears to be a disagreement between parted and fdisk as to the
correct size. fdisk is happy after creating a GPT partition table, but
parted is not and seems to be forcibly applying what it believes
On Wed, 2015-02-18 at 16:35 -0500, Phillip Susi wrote:
On 2/18/2015 4:05 PM, jnqnfe wrote:
Background = I have a 'fake-raid' RAID0 array,
created from two HDDs using my motherboard firmware. This is not
used for root, just data.
FYI, unless you have to dual boot with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 02/18/2015 05:15 PM, jnqnfe wrote:
Then you need to only manipulate md126 and ignore sdb and sdc.
Most of what you seem to be reporting involves looking directly
at the individual disks, which you must not do as that will
present a
10 matches
Mail list logo
