Bug#778683: Error creating partition table on RAID device
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 tags 778683 + moreinfo thanks I can't really follow your very well, but it sounds like you did simply select the wrong device in gparted. If you can reproduce this using just parted showing how would make things clear. If you can only reproduce it in gparted, then more detailed steps of how, as well as a copy of the gparted log file should help track down the problem there. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (MingW32) iQEcBAEBAgAGBQJU5NaVAAoJENRVrw2cjl5RJT0H/3/mVrSSxGrWUyBrNKWY5ko6 o6YpqfSdLF/xHBRGAvKsCaw7g8Uv/GDrJXaIg3IUU4Ba8b3S+lKsmQ/UbZFARSQH FWWUBsrJmJARjs7T7azxjUDbipVFJZQxxoNKKPqzeNwGhXIGHM8WVmffP1YUOYzK 00Of92sZffPyw2DdTIJaHtJNFMJiVkdf7K7RRkURzHvSoA8uEw2ezQVjaHJmQ1OA 8Bdc759gi+OrjDGRALJrA86ztLNvqFOa9nb5PQ491jfkBSHyrYVziGZ8HIgkEmZ0 drDyEA9pMH8obz+EEDTOw6HbMFS9xghAtcbKKALaQRkbc+wDEJK3ovQh476mabQ= =uEDM -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778683: Info received (Bug#778683: Error creating partition table on RAID device)
Investigating with fdisk I discovered that after this the second disk in the array was reported to have the following issue: 'MBR/GPT mismatches'. I managed to get things fixed and the partition table created successfully with fdisk instead. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778683: Error creating partition table on RAID device
Control: close -1 thanks (resending, forgot to cc bug) On Wed, 2015-02-18 at 13:14 -0500, Phillip Susi wrote: tags 778683 + moreinfo thanks I can't really follow your very well, but it sounds like you did simply select the wrong device in gparted. If you can reproduce this using just parted showing how would make things clear. If you can only reproduce it in gparted, then more detailed steps of how, as well as a copy of the gparted log file should help track down the problem there. You caught me just in time, as I'm intending to actually use this and so it won't be practical to test afterwards. I recreated the RAID array and tried again, and while I have found a serious issue, I can't reproduce the original issue reported in this particular bug, so I'll close this and write up a new report for the other issue. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778683: Error creating partition table on RAID device
Package: libparted After creating a RAID0 device via motherboard firmware, and installing mdadm, applying a partition table using gparted (gpt) resulted in gparted issuing an error. The error reads: Title: Libparted bug found! Message: Invalid argument during seek for read on /dev/sdb Note, It was specifically the /dev/md126 device that I had selected when I asked it to create the partition table, just to be clear. **This error does not occur when trying to do the same thing but specifying mbr instead of gpt.** -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#778683: Error creating partition table on RAID device
Error reoccurs upon reopening gparted if you shut down gparted after the failed creation of a gpt partition table. If you successfully create an msdos partition table and reopen, no error from the previous gpt failure (I don't know whether creating an msdos partition table wipes any gpt table, so I don't know if that should have been expected and doesn't need stating). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
