[lug] how to repair GPT

[Aaron D. Johnson]

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