From: "Günther J. Niederwimmer" <gjn@gjn.priv.at>
To: linux-raid@vger.kernel.org
Subject: Re: Hello,Re: GPT Table broken on a Raid1
Date: Mon, 24 Sep 2012 09:28:10 +0200 [thread overview]
Message-ID: <4838005.Z2kBBljtsi@techz> (raw)
In-Reply-To: <8CD3CA16-FC0C-462E-BAA5-70F993300867@colorremedies.com>
Hello Chris,
Am Sonntag, 23. September 2012, 01:17:43 schrieb Chris Murphy:
> On Sep 23, 2012, at 12:47 AM, Günther J. Niederwimmer wrote:
> > OK, the system is running but never start parted or a other tool and say
> > to
> > anything yes, then you have a destroyed system :(
>
> This will not destroy anything
>
> parted -l
Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean that another operating system believes the disk is smaller.
Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel?
Now I know, do NOT Fix ;).
Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean that another operating system believes the disk is smaller.
Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? i
Warning: Not all of the space available to /dev/sda appears to be used, you
can fix the GPT to use all
of the space (an extra 4784 blocks) or continue with the current setting?
Fix/Ignore? i
Model: ATA ST3320620AS (scsi)
Disk /dev/sda: 320GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt_sync_mbr
Number Start End Size File system Name
Flags
1 1049kB 106MB 105MB fat32 EFI system partition boot
2 106MB 240MB 134MB Microsoft reserved partition
msftres
3 240MB 105GB 105GB ntfs Basic data partition
4 105GB 190GB 84,9GB ntfs Basic data partition
5 190GB 212GB 22,0GB ntfs Basic data partition
6 212GB 268GB 55,6GB ext4 Basic data partition
Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean that
another operating system believes the disk is smaller. Fix, by moving the
backup to the end (and
removing the old backup)?
Fix/Ignore/Cancel? I
Model: ATA ST3320620AS (scsi)
Disk /dev/sdb: 320GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt_sync_mbr
Number Start End Size File system Name
Flags
1 1049kB 106MB 105MB fat32 EFI system partition boot
2 106MB 240MB 134MB Microsoft reserved partition
msftres
3 240MB 105GB 105GB ntfs Basic data partition
4 105GB 190GB 84,9GB ntfs Basic data partition
5 190GB 212GB 22,0GB ntfs Basic data partition
6 212GB 268GB 55,6GB ext4 Basic data partition
Model: ATA ST3320613AS (scsi)
Disk /dev/sdc: 320GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 320GB 320GB primary ext4 type=83
Model: ATA ST3320613AS (scsi)
Disk /dev/sdd: 320GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 4392MB 4391MB primary linux-swap(v1) type=82
2 4392MB 320GB 316GB primary ext4 type=83
Model: ATA OCZ-VERTEX4 (scsi)
Disk /dev/sde: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 181MB 180MB fat32 primary boot
2 181MB 116GB 116GB primary
Model: Linux Software RAID Array (md)
Disk /dev/md126: 320GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt_sync_mbr
Number Start End Size File system Name
Flags
1 1049kB 106MB 105MB fat32 EFI system partition boot
2 106MB 240MB 134MB Microsoft reserved partition
msftres
3 240MB 105GB 105GB ntfs Basic data partition
4 105GB 190GB 84,9GB ntfs Basic data partition
5 190GB 212GB 22,0GB ntfs Basic data partition
6 212GB 268GB 55,6GB ext4 Basic data partition
> or
>
> gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.5
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 625142448 sectors, 298.1 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): AD126626-066E-448E-ABA2-1ACFDCBA8326
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 625137630
Partitions will be aligned on 2048-sector boundaries
Total free space is 102406077 sectors (48.8 GiB)
Number Start (sector) End (sector) Size Code Name
1 2048 206847 100.0 MiB EF00 EFI system partition
2 206848 468991 128.0 MiB 0C01 Microsoft reserved
part
3 468992 205297663 97.7 GiB 0700 Basic data partition
4 205297664 371181567 79.1 GiB 0700 Basic data partition
5 371181568 414189567 20.5 GiB 0700 Basic data partition
6 414189568 522733567 51.8 GiB 0700 Basic data partition
> gdisk -l /dev/sdb
GPT fdisk (gdisk) version 0.8.5
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/sdb: 625142448 sectors, 298.1 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): AD126626-066E-448E-ABA2-1ACFDCBA8326
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 625137630
Partitions will be aligned on 2048-sector boundaries
Total free space is 102406077 sectors (48.8 GiB)
Number Start (sector) End (sector) Size Code Name
1 2048 206847 100.0 MiB EF00 EFI system partition
2 206848 468991 128.0 MiB 0C01 Microsoft reserved
part
3 468992 205297663 97.7 GiB 0700 Basic data partition
4 205297664 371181567 79.1 GiB 0700 Basic data partition
5 371181568 414189567 20.5 GiB 0700 Basic data partition
6 414189568 522733567 51.8 GiB 0700 Basic data partition
> gdisk -l /dev/md126
GPT fdisk (gdisk) version 0.8.5
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Disk /dev/md126: 625137664 sectors, 298.1 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): AD126626-066E-448E-ABA2-1ACFDCBA8326
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 625137630
Partitions will be aligned on 2048-sector boundaries
Total free space is 102406077 sectors (48.8 GiB)
Number Start (sector) End (sector) Size Code Name
1 2048 206847 100.0 MiB EF00 EFI system partition
2 206848 468991 128.0 MiB 0C01 Microsoft reserved
part
3 468992 205297663 97.7 GiB 0700 Basic data partition
4 205297664 371181567 79.1 GiB 0700 Basic data partition
5 371181568 414189567 20.5 GiB 0700 Basic data partition
6 414189568 522733567 51.8 GiB 0700 Basic data partition
> I think those disks have latent GPTs on them and that's the source of the
> (likely ignorable) problem.
;)
I mean this is a little to high for me :(.
But I have one Question more.
Is this also the same Problem with the GPT Table.
I make a Test installation before, with dmraid for the Raid1. The /home
Directory on the Raid1, all other on the SSD.
After the Installation the most time the System have a Problem to mount the
"/home" or a other Partition on the Raid1 and fall down in the repair mode.
But the good thing from this, Grub2 found my Windows 7 Installation on the
Raid1 and Make a Start Entry, with mdadm this is not working, Grub2 don't
found the windows?
--
mit freundlichen Grüßen / best Regards.
Günther J. Niederwimmer
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-09-24 7:28 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-19 11:03 GPT Table broken on a Raid1 Günther J. Niederwimmer
2012-09-20 2:39 ` Chris Murphy
2012-09-20 11:05 ` Günther J. Niederwimmer
2012-09-20 17:34 ` Chris Murphy
2012-09-21 11:42 ` Günther J. Niederwimmer
2012-09-21 19:35 ` Chris Murphy
2012-09-21 22:43 ` Chris Murphy
2012-09-22 8:37 ` Günther J. Niederwimmer
2012-09-22 18:30 ` Chris Murphy
2012-09-23 6:47 ` Hello,Re: " Günther J. Niederwimmer
2012-09-23 7:17 ` Chris Murphy
2012-09-24 7:28 ` Günther J. Niederwimmer [this message]
2012-09-24 17:21 ` Chris Murphy
2012-09-24 19:06 ` Günther J. Niederwimmer
2012-09-24 20:18 ` Chris Murphy
2012-09-24 21:06 ` Günther J. Niederwimmer
2012-09-24 21:12 ` Chris Murphy
2012-09-25 8:27 ` Günther J. Niederwimmer
2012-09-25 9:28 ` John Robinson
2012-09-25 16:55 ` Chris Murphy
2012-09-26 12:17 ` Günther J. Niederwimmer
2012-09-26 19:33 ` Chris Murphy
2012-09-27 2:43 ` NeilBrown
2012-09-22 15:31 ` John Robinson
2012-09-22 18:45 ` Chris Murphy
2012-09-22 21:58 ` NeilBrown
2012-09-22 22:07 ` John Robinson
2012-09-22 22:30 ` Chris Murphy
2012-09-23 12:00 ` John Robinson
2012-09-23 17:44 ` Chris Murphy
2012-09-23 18:53 ` Chris Murphy
2012-09-24 9:37 ` John Robinson
2012-09-24 17:35 ` Chris Murphy
2012-09-24 18:17 ` Roberto Spadim
[not found] ` <CABYL=ToFtzXv95At54=jSCaD0QVSB+bdxbssda1AMw5gNBqvhg@mail.gmail.com>
2012-09-24 18:55 ` Chris Murphy
2012-09-25 7:33 ` Miquel van Smoorenburg
2012-09-21 21:30 ` Chris Murphy
2012-09-21 21:49 ` Chris Murphy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4838005.Z2kBBljtsi@techz \
--to=gjn@gjn.priv.at \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).