[lug] how to repair GPT

[Steve A Hart]

Thanks Zan, but I just found a hard drive with errors so that really 
puts a nail in the coffin.  I've got to replace the drive so it's just 
easier at this point to start from scratch.  It's no loss as long my 
main server and clients behave until I get the backup server back on 
it's feet.

cheers

Steve

On 04/27/2011 02:24 PM, Zan Lynx wrote:
> Before you give up did you try taking fsck's advice and using a backup
> superblock?
>
> On 4/27/2011 2:00 PM, Steve A Hart wrote:
>> OK, well I let fsck run with it and many errors still keep cropping up
>> so I think I'm just going to call it and wipe the thing.  Yes, fsck is
>> trying to read past the end of the block device due to bad info in the
>> filesystem's superblock.  Fsck actually finishes but the filesystem
>> still does not come up clean.  It ends with:
>>
>> Creating journal (32768 blocks):  Done.
>>
>> *** journal has been re-created - filesystem is now ext3 again ***
>>
>> raid: ***** FILE SYSTEM WAS MODIFIED *****
>> raid: 134/457416704 files (17.9% non-contiguous), 389194178/1829645824
>> blocks
>> Error writing block 550731776 (Attempt to write block from filesystem
>> resulted in short write).  Ignore error? yes
>>
>> Error writing block 644972544 (Attempt to write block from filesystem
>> resulted in short write).  Ignore error? yes
>>
>> I initially thought it was a GPT problem but it's just easier now to
>> reinitialize the filesystem.
>>
>> I'm going to run the built in diagnostics on the RAID itself to make
>> sure the hardware is fine and then reinitialize the filesystem.  Then
>> I'm going to buy a frickin UPS!
>>
>> Thanks for all the advice Dan and Aaron!
>>
>> cheers
>>
>> Steve
>>
>>
>>
>> On 04/27/2011 12:23 PM, Aaron D. Johnson wrote:
>>> Steve A Hart writes
>>>> dmesg shows repeated messages like this:
>>>> --------------------------------------------
>>>>
>>>> Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00
>>>> Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00
>>>> Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00
>>>> Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00
>>>> Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00
>>>> Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00
>>>> sd 4:0:4:0: [sdd] Unhandled error code
>>>> sd 4:0:4:0: [sdd] Result: hostbyte=DID_SOFT_ERROR driverbyte=DRIVER_OK
>>>> sd 4:0:4:0: [sdd] CDB: Read(16): 88 00 00 00 00 03 68 71 7f f8 00 00 00
>>>> 08 00 00
>>>> end_request: I/O error, dev sdd, sector 14637170680
>>>
>>> Doesn't look too healthy.  What does "badblocks -s -v /dev/sdd" tell
>>> you about reading from the disk?
>>>
>>>> fsck from util-linux-ng 2.17.2
>>>> e2fsck 1.41.12 (17-May-2010)
>>>> fsck.ext2: Superblock invalid, trying backup blocks...
>>>> fsck.ext2: Bad magic number in super-block while trying to open /dev/sdd
>>>
>>> Is this filesystem really on /dev/sdd and not on a partition on that
>>> disk, say /dev/sdd1?  What does /proc/partitions say about the
>>> partitions on the /dev/sdd device?
>>>
>>> - Aaron
>>> _______________________________________________
>>> Web Page:  http://lug.boulder.co.us
>>> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
>>> Join us on IRC: irc.hackingsociety.org port=6667 channel=#hackingsociety
>>

-- 
Steve Hart
Systems Administrator
Colorado Center for Astrodynamics Research
University of Colorado Boulder
shart at colorado.edu
(303)492-8109