03.03.2012 2:04, Whit Blauvelt пишет:
Thanks Robin,

That's getting me closer - since it's enough to find this background info
with a nice diagram:


Is there a method to move LBA-34 through LBA-1 - or recreate them from the
primary - so as to avoid the bad sector?
According to your partition table you do not use GPT. Check that:

#parted /dev/sda print

Model: LSI MR9280-4i4e (scsi)
Disk /dev/sda: 20.0TB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system  Name     Flags
 1      1049kB  20.0TB  20.0TB               primary  lvm

You may use hdparm --repair-sector to write zero. Ensure that you do not miss with sector number with hdparm --read-sector

 I find mention of using parted in
similar circumstances for a corrupt secondary table, but not for one that
falls on a bad sector. This is one such mention:


Alternately, is there a way to instruct Linux not to obsess over a bad
alternate GPT header? I should back up the primary in any case, but why is
Linux worrying about the secondary?


On Fri, Mar 02, 2012 at 06:39:08PM +0000, Robin H. Johnson wrote:
On Fri, Mar 02, 2012 at 12:31:25PM -0500, Whit Blauvelt wrote:
I have an ASUS Eee 1001P that's just developed a bad sector:
LBA-1 on disk is where the alternate GPT header would be stored.
(LBA-1 for the header, LBA-33..LBA-2 for the data).

Robin Hugh Johnson
Gentoo Linux: Developer, Trustee & Infrastructure Lead
E-Mail     : robbat2@gentoo.org
GnuPG FP   : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
Smartmontools-support mailing list