Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 2 Jun 2013 17:12:01 +0300
From:      Kimmo Paasiala <kpaasial@gmail.com>
To:        Alban Hertroys <haramrae@gmail.com>
Cc:        freebsd-stable@freebsd.org, Steven Hartland <killing@multiplay.co.uk>
Subject:   Re: Corrupt GPT header on disk from twa array - fixable?
Message-ID:  <CA%2B7WWSe7O9%2Bxq3UEJ%2B%2BtM1d3tphf7pWU=n4DoQY8XZq39RRScQ@mail.gmail.com>
In-Reply-To: <7ABBEE71A96E411793E41BD97DA72BCE@multiplay.co.uk>
References:  <EA2DCEC2-8B07-434B-8B60-8AB15B3788F7@gmail.com> <7ABBEE71A96E411793E41BD97DA72BCE@multiplay.co.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jun 2, 2013 at 5:02 PM, Steven Hartland <killing@multiplay.co.uk> wrote:
> Does "gpart recover ada4" help at all?
>
> Be warned this could edit the partition on the disk and make it worse, but
> I've had success in the past with it.
>
>    Regards
>    Steve
>
> ----- Original Message ----- From: "Alban Hertroys" <haramrae@gmail.com>
> To: <freebsd-stable@freebsd.org>
> Sent: Sunday, June 02, 2013 2:53 PM
> Subject: Corrupt GPT header on disk from twa array - fixable?
>
>
>
>> Hello list,
>>
>> I just replaced my home server and moved the disks from the old one over
>> to the new one. In the old server, 4 of the disks were connected to a twa
>> (3Ware 9550) controller, which of course has it's own way of marking
>> units/volumes on those disks.
>>
>> Before you start yelling at me, yes, of course I made backups ;) [*]
>>
>> The thing is, I have these disks in the new server and I found that I (to
>> my surprise) I can actually mount them! But, I'm missing a large part and I
>> am wondering if there's some method to access those last partitions too.
>>
>> Here's what gpart show says about the problematic disk:
>>
>> # gpart show /dev/ada4
>> =>      34  41942972  ada4  GPT  (931G) [CORRUPT]
>>        34       128     1  freebsd-boot  (64k)
>>       162   1048448     2  freebsd-ufs  (512M)
>>   1048610   6291456     3  freebsd-swap  (3.0G)
>>   7340066   1048576     4  freebsd-ufs  (512M)
>>   8388642   2097152     5  freebsd-ufs  (1.0G)
>>  10485794  31457211     6  freebsd-ufs  (15G)
>>  41943005         1        - free -  (512B)
>>
>> As you can see, most (about 910GB) of the disk is missing! This disk was
>> one half of a mirror on the twa controller, which had those disks split in
>> two again (I don't recall how, perhaps 2 different BSD slices?)
>> I already looked if that part may perhaps have ended up as a different
>> device. On the old server, fstab was this:
>>
>> # cat /tmp/solfertje/etc/fstab
>> # Device        Mountpoint      FStype  Options Dump    Pass#
>>
>> # These are the partitions listed above in gpart
>> /dev/da0p2      /               ufs     rw      1       1
>> /dev/da0p3      none            swap    sw      0       0
>> /dev/da0p4      /var            ufs     rw      2       2
>> /dev/da0p5      /tmp            ufs     rw      2       2
>> /dev/da0p6      /usr            ufs     rw      2       2
>>
>> # These are missing
>> /dev/da1p1      /home           ufs     rw      2       2
>> /dev/da1p2      /media          ufs     rw      2       2
>>
>> # These are on a different disk (ada2)
>> /dev/da2p1      /media2         ufs     rw      2       2
>>
>>
>> I don't _really_ need to get to those partitions, but it would be a
>> comfortable thought if it were possible somehow.
>>
>>
>> [*] The reason I was trying to access those disks anyway is that I thought
>> I forgot to backup my database tables, but it turns out I had just misplaced
>> that backup and it has been restored now.
>>
>> Alban Hertroys
>> --
>> If you can't see the forest for the trees,
>> cut the trees and you'll find there is no forest.
>>
>> _______________________________________________
>> freebsd-stable@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>>
>
>

Looking at the gpart(8) output it seems that only 20GBs of the disk is
recognized by the disk driver but the GPT table still shows the full
capacity 910GB. I'd say that the GPT table is in fact correct and if
you can somehow get the disks to be recognized with full capacity they
should be usable as they are. What does dmesg(8) say about the disks?

-Kimmo



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2B7WWSe7O9%2Bxq3UEJ%2B%2BtM1d3tphf7pWU=n4DoQY8XZq39RRScQ>