[Top] [All Lists]

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

To: Roger Willcocks <roger@xxxxxxxxxxxxxxxx>
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:46:48 +0100
Cc: Eric Sandeen <sandeen@xxxxxxxxxxx>, 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=YEKrM84rZsjLkjeYEFnw6jd+MEIWwvFL+KEJ7vHGoMI=; b=dt0Zgh/jLsBUEATZW51IfM2yfb6APe7163Pqc4CUWlL3G12bcnCg8i3G4huS14e0D5 Kqr0z7Jdo4E0GuLCvA5IH4qKUZjgN+WjN4BkTGdkP5q0wCf/A7N8p1PQ0Xrnhd88keDM EU1aeOtHlHv529vA/XMBDLv40q0JjkJ53Ppms=
In-reply-to: <1327414341.24535.582.camel@xxxxxxxxxxxxxxxxxxxxxxxx>
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>
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!
<Prev in Thread] Current Thread [Next in Thread>