[Top] [All Lists]

Re: How to fix bad superblock or xfs_repair: error - read only 0 of 512

To: Eric Sandeen <sandeen@xxxxxxxxxxx>
Subject: Re: How to fix bad superblock or xfs_repair: error - read only 0 of 512 bytes
From: Christian Kildau <lists@xxxxxxxxxxxxx>
Date: Tue, 24 Jan 2012 16:52:28 +0100
Cc: Roger Willcocks <roger@xxxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unixhosts.org; s=google; h=subject:mime-version:from:in-reply-to:date:cc:message-id:references :to:x-mailer:x-gm-message-state:content-type :content-transfer-encoding; bh=bsj19P1KKAiB573fT4aKNqVtpOPQ45ABm1a6Bf/ztf0=; b=YwRQ2y88VGJsJrEu08T6RfTo/R/WwzvKxZn75fpaKgXUlTCkYY/hOwpcGA7bcj51aH iGlSYHWROF7HAsmL6zNWIBKKRMptfjHlaoOpER2bsNnzm0DjEFV7eNWiAk8phKt2ritF Mg8LqmInv6XTwyh/7vZCpIbJe2NSXBUpCIGX8=
In-reply-to: <4F1ED341.4010108@xxxxxxxxxxx>
References: <CALx8gnT9tdPRGfVR0puoSVYz_MDDs4FtWtodST5x29GDnL3A_w@xxxxxxxxxxxxxx> <20120123043117.GH15102@dastard> <92CDAC52-1BA1-43A8-8470-0E2DCD916610@xxxxxxxxxxxxx> <4F1E3BD0.7080604@xxxxxxxxxxx> <B1F1FDAB-0D48-48FE-8FFC-F0567780E052@xxxxxxxxxxxxx> <1327414341.24535.582.camel@xxxxxxxxxxxxxxxxxxxxxxxx> <4D396236-D516-4948-8F43-1AED88539BC4@xxxxxxxxxxxxx> <4F1ED341.4010108@xxxxxxxxxxx>
On Jan 24, 2012, at 4:50 PM, Eric Sandeen wrote:

> On 1/24/12 9:46 AM, Christian Kildau wrote:
>> On Jan 24, 2012, at 3:12 PM, Roger Willcocks wrote:
>>> On Tue, 2012-01-24 at 11:13 +0100, Christian Kildau wrote:
>>>> Top posting... sorry.
>>>> I have now found dozens of other users with a similar issue! e.g.
>>>> http://www.linuxquestions.org/questions/linux-general-1/cannot-mount-hard-disk-block-count-exceeds-size-of-device-bad-partition-table-880149/
>>>> To make it short all of these users were running ext4 and a fs resize to 
>>>> the new geometry fixed their problems! Sadly XFS doesn't support shrinking 
>>>> the fs(?).
>>> It seems fairly clear that your drive or the bios is lying about its
>>> capacity. The filesystem occupies the entire disk, but the disk has
>>> become 'smaller'. A quick web search suggests a 'hidden protected area'
>>> - the two block counts in this link line up with the before and after
>>> sizes you're seeing:
>>> http://lime-technology.com/forum/index.php?topic=13440.0;wap2
>>> It would be instructive to see what 'hdparm -N /dev/sdd' says on your
>>> system. And a dmesg log would be handy too.
>>> Note that this is /not/ a problem with xfs. The right fix is to tell the
>>> drive to report its actual capacity, not to shrink the filesystem.
>> I do understand that is definitely not an XFS issue, but some strange issue 
>> with ubuntu or their kernel patches...
>> I got my data back by dumping the entire hdd (it was partitionless 
>> nevertheless) to a bigger 2TB hdd.
>> XFS mounts without any problems and I can restore my data.
>> Thanks all for your help!
> It's likely still missing the end of the filesystem, though.
> Can you run the hdparm command Roger suggested on your original hard drive, 
> please?

Sure, here it is:

 max sectors   = 2930275055/2930277168, HPA is enabled
<Prev in Thread] Current Thread [Next in Thread>