[lug] how to repair GPT
dan at usrsbin.com
Wed Apr 27 12:10:25 MDT 2011
What does dmesg show, and what does fsck complain about? If the
filesystem is hosed you may get to redo it from scratch anyway. I don't
think GPT matters in this case.
I remember what that was 1.2 TB and we thought it was a lot lol!
On 4/27/2011 12:00 PM, Steve A Hart wrote:
> Hello all,
> We had a power outage this past weekend and of course my backup server
> went down (because I'm the idiot who has not gotten around to getting a
> UPS for it yet). Anyway, my 7TB raid starting showing I/O errors so I
> unmounted it.
> Disk /dev/sdd: 7494.2 GB, 7494231392256 bytes
> 255 heads, 63 sectors/track, 911121 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x00000000
> Device Boot Start End Blocks Id System
> /dev/sdd1 1 267350 2147483647+ ee GPT
> Now it refuses to mount again and fsck freaks as expected. I'm not
> fully experienced with GPT and would appreciate any advice on how to
> repair/recover this and get the raid mounted and functional.
> Since this is the storage area for my backup server, I technically can
> wipe the whole thing and start from scratch but I'd like to avoid that
> if possible.
More information about the LUG