All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: Daniel Sanabria <sanabria.d@gmail.com>
Cc: Chris Murphy <lists@colorremedies.com>,
	Wols Lists <antlists@youngman.org.uk>,
	Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Inactive arrays
Date: Wed, 14 Sep 2016 10:10:47 -0600	[thread overview]
Message-ID: <CAJCQCtQ3kAKd4U=MgVawU9D6QKuxC+XjLYR6EyL87wuyBvvmtg@mail.gmail.com> (raw)
In-Reply-To: <CAHscji1wVYzpzu8X+GYuuxZPdLzY-f+8oogyH7ttqVwMJe2=iQ@mail.gmail.com>

On Wed, Sep 14, 2016 at 9:47 AM, Daniel Sanabria <sanabria.d@gmail.com> wrote:
> [root@lamachine ~]# gdisk /dev/sdc
>
> GPT fdisk (gdisk) version 1.0.1
>
> Warning! Disk size is smaller than the main header indicates! Loading
> secondary header from the last sector of the disk! You should use 'v' to
> verify disk integrity, and perhaps options on the experts' menu to repair
> the disk.
>
> Caution: invalid backup GPT header, but valid main header; regenerating
> backup header from main header.
>
> Warning! One or more CRCs don't match. You should repair the disk!
>
> Partition table scan:
>   MBR: not present
>   BSD: not present
>   APM: not present
>   GPT: damaged
>
> Found invalid MBR and corrupt GPT. What do you want to do? (Using the
> GPT MAY permit recovery of GPT data.)
>  1 - Use current GPT
>  2 - Create blank GPT
>
> Your answer: 1
>
> Command (? for help): x
>
> Expert command (? for help): v
>
> Caution: The CRC for the backup partition table is invalid. This table may
> be corrupt. This program will automatically create a new backup partition
> table when you save your partitions.
>
> Problem: The secondary header's self-pointer indicates that it doesn't reside
> at the end of the disk. If you've added a disk to a RAID array, use the 'e'
> option on the experts' menu to adjust the secondary header's and partition
> table's locations.
>
> Problem: Disk is too small to hold all the data!
> (Disk size is 5860531055 sectors, needs to be 5860533168 sectors.)
>
> The 'e' option on the experts' menu may fix this problem.
>
> Problem: GPT claims the disk is larger than it is! (Claimed last usable
> sector is 5860533134, but backup header is at
> 5860533167 and disk size is 5860531055 sectors.
> The 'e' option on the experts' menu will probably fix this problem
>
> Identified 4 problems!
>
> Expert command (? for help): p
> Disk /dev/sdc: 5860531055 sectors, 2.7 TiB
> Logical sector size: 512 bytes
> Disk identifier (GUID): 6DB70F4E-D8ED-4290-AA2E-4E81D8324992
> Partition table holds up to 128 entries
> First usable sector is 2048, last usable sector is 5860533134
> Partitions will be aligned on 2048-sector boundaries
> Total free space is 516987791 sectors (246.5 GiB)
>
> Number  Start (sector)    End (sector)  Size       Code  Name
>    1            2048      4294969343   2.0 TiB     FD00
>    2      4294969344      5343545343   500.0 GiB   8300
>
> Expert command (? for help):

Use the e command. That should fix the 3 main problems, and then a new
CRC is automatically computed for the two headers and two tables at
write time.


-- 
Chris Murphy

  reply	other threads:[~2016-09-14 16:10 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-02  7:36 Inactive arrays Daniel Sanabria
2016-08-02 10:17 ` Wols Lists
2016-08-02 10:45   ` Daniel Sanabria
2016-08-03 19:18     ` Daniel Sanabria
2016-08-03 21:31       ` Wols Lists
2016-09-11 18:48     ` Daniel Sanabria
2016-09-11 20:06       ` Daniel Sanabria
2016-09-12 19:41         ` Daniel Sanabria
2016-09-12 21:13           ` Daniel Sanabria
2016-09-12 21:37             ` Chris Murphy
2016-09-13  6:51               ` Daniel Sanabria
2016-09-13 15:04                 ` Chris Murphy
2016-09-12 21:39             ` Wols Lists
2016-09-13  6:56               ` Daniel Sanabria
2016-09-13  7:02                 ` Adam Goryachev
2016-09-13 15:20                 ` Chris Murphy
2016-09-13 19:43                   ` Daniel Sanabria
2016-09-13 19:52                     ` Chris Murphy
2016-09-13 20:04                       ` Daniel Sanabria
2016-09-13 20:13                         ` Chris Murphy
2016-09-13 20:29                           ` Daniel Sanabria
2016-09-13 20:36                           ` Daniel Sanabria
2016-09-13 21:10                             ` Chris Murphy
2016-09-13 21:46                               ` Daniel Sanabria
2016-09-13 21:26                             ` Wols Lists
2016-09-14  4:33                         ` Chris Murphy
2016-09-14 10:36                           ` Daniel Sanabria
2016-09-14 14:32                             ` Chris Murphy
2016-09-14 14:57                               ` Daniel Sanabria
2016-09-14 15:15                                 ` Chris Murphy
2016-09-14 15:47                                   ` Daniel Sanabria
2016-09-14 16:10                                     ` Chris Murphy [this message]
2016-09-14 16:13                                       ` Chris Murphy
2016-09-14 18:16                                         ` Daniel Sanabria
2016-09-14 18:37                                           ` Chris Murphy
2016-09-14 18:42                                           ` Wols Lists
2016-09-15  9:21                                             ` Brad Campbell

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='CAJCQCtQ3kAKd4U=MgVawU9D6QKuxC+XjLYR6EyL87wuyBvvmtg@mail.gmail.com' \
    --to=lists@colorremedies.com \
    --cc=antlists@youngman.org.uk \
    --cc=linux-raid@vger.kernel.org \
    --cc=sanabria.d@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.