mount: Structure needs cleaning

mount: Structure needs cleaning

[MikeJeezy]

I have two 2TB xfs volumes and earlier today the /var/log/messages shows
"xfs_force_shutdown" after many errors (attached) 
http://old.nabble.com/file/p33393100/var-log-message.txt var-log-message.txt
.  Are there any options to try before running "xfs_repair -L"?   The
volumes contain several millions files so that I my last resort.  I'm a
novice at best in Linux.
-- 
View this message in context: http://old.nabble.com/mount%3A-Structure-needs-cleaning-tp33393100p33393100.html
Sent from the Xfs - General mailing list archive at Nabble.com.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: mount: Structure needs cleaning

[Stan Hoeppner]

On 2/25/2012 9:15 PM, MikeJeezy wrote:
> 
> I have two 2TB xfs volumes and earlier today the /var/log/messages shows
> "xfs_force_shutdown" after many errors (attached) 
> http://old.nabble.com/file/p33393100/var-log-message.txt var-log-message.txt
> .  Are there any options to try before running "xfs_repair -L"?   The
> volumes contain several millions files so that I my last resort.  I'm a
> novice at best in Linux.

Googling "XFS_WANT_CORRUPTED_RETURN at line 280" turns up a whole lot of
information on this.  This is an Oct 2008 response to another user with
this problem, from XFS developer Dave Chinner, one of the resident
experts on this list:

"The freespace btrees are getting out of sync for some reason.

That is, when we go to allocate an extent, we have to update two
free space btrees. This shutdown:

> XFS internal error XFS_WANT_CORRUPTED_RETURN at line 280 of file
fs/xfs/xfs_alloc.c.  Caller 0xf88e0018

Indicates the extent being allocated was not found in one of the
two trees.

This corruption could have happened a long time ago in the past, and
it may simply be coincidental that you've tripped over this at
roughly the same time you upgraded the kernel.

Can you run xfs_check on the filesystem to determine if a freespace
tree is corrupted (post the output if it is), then run xfs_repair
to rebuild them?"

So, run "xfs_check /dev/sde1" and post the output here.  Then await
further instructions.  Don't flush the log as that's probably not the
problem.  Doing so will delete pending metadata changes and could cause
you more headaches.

-- 
Stan

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: mount: Structure needs cleaning

[MikeJeezy]

On 02/25/2012 10:35pm, Stan Hoeppner wrote:
>Can you run xfs_check on the filesystem to determine if a freespace
>tree is corrupted (post the output if it is), then run xfs_repair
>to rebuild them?"

Thank you for responding.  This is a 24/7 production server and I did not
anticipate getting a response this late on a Saturday, so I panicked quite
frankly, and went ahead and ran "xfs_repair -L" on both volumes.  I can now
mount the volumes and everything looks okay as far as I can tell.  There
were only 2 files in the "lost+found" directory after the repair.  Does that
mean only two files were lost?  Is there any way to tell how many files were
lost?

>This corruption could have happened a long time ago in the past, and
>it may simply be coincidental that you've tripped over this at
>roughly the same time you upgraded the kernel.

It would be nice to find out why this happened.  I suspect it is as you
suggested, previous corruption and not a hardware issue, because I have
other volumes mounted to other VM's that are attached to the same SAN
controller / RAID6 Array... and they did not have any issues - only this one
VM.

>So, run "xfs_check /dev/sde1" and post the output here.  Then await
>further instructions.  

Can I still do this (or anything) to help uncover any causes or is it too
late?  I have also run yum update on the server because it was out of date.
-- 
View this message in context: http://old.nabble.com/mount%3A-Structure-needs-cleaning-tp33393100p33393429.html
Sent from the Xfs - General mailing list archive at Nabble.com.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: mount: Structure needs cleaning

[Stan Hoeppner]

On 2/26/2012 1:22 AM, MikeJeezy wrote:
> 
> 
> On 02/25/2012 10:35pm, Stan Hoeppner wrote:
>> Can you run xfs_check on the filesystem to determine if a freespace
>> tree is corrupted (post the output if it is), then run xfs_repair
>> to rebuild them?"
> 
> Thank you for responding.  This is a 24/7 production server and I did not
> anticipate getting a response this late on a Saturday, so I panicked quite
> frankly, and went ahead and ran "xfs_repair -L" on both volumes.  I can now

I wasn't sure how big a pickle you were in so I jumped in and tried to
help best I could.

> mount the volumes and everything looks okay as far as I can tell.  There
> were only 2 files in the "lost+found" directory after the repair.  Does that
> mean only two files were lost?  Is there any way to tell how many files were
> lost?

I'm not sure.  If this is free space btree corruption then you shouldn't
have lost any user files.  Others might answer this better than me.

>> This corruption could have happened a long time ago in the past, and
>> it may simply be coincidental that you've tripped over this at
>> roughly the same time you upgraded the kernel.

Note the text above is something I quoted from Dave's 2008 response to
another user with the same problem.  In that case he had just upgraded
his kernel and suspected that as the cause.  It was not.

> It would be nice to find out why this happened.  I suspect it is as you
> suggested, previous corruption and not a hardware issue, because I have
> other volumes mounted to other VM's that are attached to the same SAN
> controller / RAID6 Array... and they did not have any issues - only this one
> VM.

Are those other VMs using XFS filesystems?

Found this in the list archive:

On 9/19/2011 9:27 AM, Christoph Hellwig wrote:

> Given that before ~2.6.35 LVM/device mapper was not able to pass through
> cache flush requests that is your most likely culprit.  A repair will
> rebuild the freespace btrees, and make sure to keep the write caches
> down the whole stack disabled.

What kernel version are you running?  Are you using LVM under XFS?  What
fstab mount options?  Does your SAN array have battery backed write
cache?  Are the individual drive caches in the underlying array disabled?

>> So, run "xfs_check /dev/sde1" and post the output here.  Then await
>> further instructions.  
> 
> Can I still do this (or anything) to help uncover any causes or is it too

If you already ran a repair and it fixed the damage then the check won't
show anything.

> late?  I have also run yum update on the server because it was out of date.

Answering the questions above may lead us to a possible/plausible cause.

-- 
Stan

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: mount: Structure needs cleaning

[Dave Chinner]

On Sat, Feb 25, 2012 at 11:22:29PM -0800, MikeJeezy wrote:
> 
> 
> On 02/25/2012 10:35pm, Stan Hoeppner wrote:
> >Can you run xfs_check on the filesystem to determine if a freespace
> >tree is corrupted (post the output if it is), then run xfs_repair
> >to rebuild them?"
> 
> Thank you for responding.  This is a 24/7 production server and I did not
> anticipate getting a response this late on a Saturday, so I panicked quite
> frankly, and went ahead and ran "xfs_repair -L" on both volumes.

The only reason for running xfs-repair -L is if you cannot mount the
filesystem to replay the log. i.e. on a shutdown like this, the
usual process is:

<shutdown>
umount <dev>
mount <dev>
umount <dev>
xfs_repair <dev>

The only reason for needing to run "xfs-repair -L <dev>" is if the
mount after the shutdown fails to run log recovery.

> I can now
> mount the volumes and everything looks okay as far as I can tell.  There
> were only 2 files in the "lost+found" directory after the repair.  Does that
> mean only two files were lost?  Is there any way to tell how many files were
> lost?

YOu can only find out by looking at what the output of xfs_repair
told you about trashing inodes/directories.

> >This corruption could have happened a long time ago in the past, and
> >it may simply be coincidental that you've tripped over this at
> >roughly the same time you upgraded the kernel.
> 
> It would be nice to find out why this happened.  I suspect it is as you
> suggested, previous corruption and not a hardware issue, because I have
> other volumes mounted to other VM's that are attached to the same SAN
> controller / RAID6 Array... and they did not have any issues - only this one
> VM.
> 
> >So, run "xfs_check /dev/sde1" and post the output here.  Then await
> >further instructions.  
> 
> Can I still do this (or anything) to help uncover any causes or is it too
> late?  I have also run yum update on the server because it was out of date.

Too late. As it is, xfs-check is deprecated. use "xfs_repair -n
<dev>" to check a filesystem for errors without modifying/fixing
anything.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: mount: Structure needs cleaning

[MikeJeezy]

>The only reason for running xfs-repair -L is if you cannot mount the
>filesystem to replay the log. i.e. on a shutdown like this, the
>usual process is:

Right, when I tried to mount the volume it said "Structure needs cleaning"

>You can only find out by looking at what the output of xfs_repair
>told you about trashing inodes/directories.

Is this only output to the screen or to a log somewhere?

> On 02/26/2012 11:07am, Stan Hoeppner wrote: 
>Are those other VMs using XFS filesystems? 

What kernel version are you running?  

2.6.18-274.18.1.el5

>Are you using LVM under XFS?  

No

>What fstab mount options?  

/dev/sdd1               /mnt/ob1               xfs     defaults        0 0
/dev/sde1               /mnt/ob2               xfs     defaults        0 0

>Does your SAN array have battery backed write cache?  

This one does not currently, but I have ordered BBWC for it.

>Are the individual drive caches in the underlying array disabled? 

Write cache: enabled
Read ahead: enabled

-- 
View this message in context: http://old.nabble.com/mount%3A-Structure-needs-cleaning-tp33393100p33397518.html
Sent from the Xfs - General mailing list archive at Nabble.com.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: mount: Structure needs cleaning

[Stan Hoeppner]

On 2/26/2012 9:11 PM, MikeJeezy wrote:

>> On 02/26/2012 11:07am, Stan Hoeppner wrote: 
>> Are those other VMs using XFS filesystems? 
> 
> What kernel version are you running?  
> 
> 2.6.18-274.18.1.el5

I'm not familiar enough with Red Hat kernel revs to know if all relevant
patches are included in this kernel.  There are a few Red Hat devs here
who should have more insight on this.

>> Are you using LVM under XFS?  
> 
> No
> 
>> What fstab mount options?  
> 
> /dev/sdd1               /mnt/ob1               xfs     defaults        0 0
> /dev/sde1               /mnt/ob2               xfs     defaults        0 0
> 
>> Does your SAN array have battery backed write cache?  
> 
> This one does not currently, but I have ordered BBWC for it.

Good.  I suggest disabling the SAN controller's write caching until the
BBWC is installed and verified to be functioning correctly.

>> Are the individual drive caches in the underlying array disabled? 
> 
> Write cache: enabled
> Read ahead: enabled

In the case of a SAN array or PCIe RAID controller, this dmesg output is
telling you about the state of the controller's cache, not the
individual drive caches.  Enable/disable of the drive caches should be
an option in the controller firmware interface.  You want the individual
drive write caches disabled.  Leaving their read caches enabled is fine.

The reason is that a power drop, kernel panic, or hardware lockup
(thermal etc) clears the drive write caches before the blocks are
written to the platters.  It is suspected that many/most of these free
space btree corruptions, such as yours here, are caused by data in
caches not being flushed to the platters.  SAN/RAID controllers with
BBWC usually guarantee data in the write cache gets properly flushed to
the platters when the system comes back up.

So, way back when, you may have had a system (VM) crash of one kind or
another, or an improper shutdown (VM power-off), then rebooted, and
everything seemed fine.  Months later, you discover you have a corrupted
free space btree, which was caused by the crash long ago, that everyone
forgot about, never documented, etc.

-- 
Stan

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: mount: Structure needs cleaning

[MikeJeezy]

> You want the individual drive write caches disabled.  Leaving their read
caches enabled is fine.
>
>The reason is that a power drop, kernel panic, or hardware lockup
>(thermal etc) clears the drive write caches before the blocks are
>written to the platters.  It is suspected that many/most of these free
>space btree corruptions, such as yours here, are caused by data in
>caches not being flushed to the platters.  SAN/RAID controllers with
>BBWC usually guarantee data in the write cache gets properly flushed to
>the platters when the system comes back up. 

Makes total sense. Thanks so much.
-- 
View this message in context: http://old.nabble.com/mount%3A-Structure-needs-cleaning-tp33393100p33401743.html
Sent from the Xfs - General mailing list archive at Nabble.com.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: mount: Structure needs cleaning

[Dave Chinner]

On Sun, Feb 26, 2012 at 07:11:58PM -0800, MikeJeezy wrote:
> 
> 
> 
> >The only reason for running xfs-repair -L is if you cannot mount the
> >filesystem to replay the log. i.e. on a shutdown like this, the
> >usual process is:
> 
> Right, when I tried to mount the volume it said "Structure needs cleaning"

OK, so you've done the right thing. I always like to check first ;)

> >You can only find out by looking at what the output of xfs_repair
> >told you about trashing inodes/directories.
> 
> Is this only output to the screen or to a log somewhere?

Only to stdout.

> > On 02/26/2012 11:07am, Stan Hoeppner wrote: 
> >Are those other VMs using XFS filesystems? 
> 
> What kernel version are you running?  
> 
> 2.6.18-274.18.1.el5

If you are running RHEL, you should really report problems through
the support channel.

> >Does your SAN array have battery backed write cache?  
> 
> This one does not currently, but I have ordered BBWC for it.
> 
> >Are the individual drive caches in the underlying array disabled? 
> 
> Write cache: enabled

There's your problem. You should read all the relevant sections on
write caches in the XFS FAQ. e.g:

http://xfs.org/index.php/XFS_FAQ#Q._Which_settings_does_my_RAID_controller_need_.3F

Cheers,

Dave.

-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: mount: Structure needs cleaning

[Brian Candler]

On Tue, Feb 28, 2012 at 12:48:13PM +1100, Dave Chinner wrote:
> > Write cache: enabled
> 
> There's your problem. You should read all the relevant sections on
> write caches in the XFS FAQ. e.g:
> 
> http://xfs.org/index.php/XFS_FAQ#Q._Which_settings_does_my_RAID_controller_need_.3F

As a side question to this: if I am using Linux's md software RAID with an
HBA, and XFS is using write barriers (as I believe it does by default), is
it still necessary to disable write caching on the drives?

My reading of the FAQ suggests that the write barrier by itself should be
sufficient - but this requires that the md RAID driver implements write
barriers correctly.  I seem to remember reading a long time ago that LVM
and/or dmraid didn't, although that may be different now.

Incidentally I'm using 'mdadm ... -b internal' to ensure that the RAID array
marks dirty areas, so that if a write part-completes (e.g.  a block is
written to only one half of a RAID1) then at next power-up this should be
made consistent again.

Regards,

Brian.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: mount: Structure needs cleaning

[Dave Chinner]

On Tue, Feb 28, 2012 at 09:14:41AM +0000, Brian Candler wrote:
> On Tue, Feb 28, 2012 at 12:48:13PM +1100, Dave Chinner wrote:
> > > Write cache: enabled
> > 
> > There's your problem. You should read all the relevant sections on
> > write caches in the XFS FAQ. e.g:
> > 
> > http://xfs.org/index.php/XFS_FAQ#Q._Which_settings_does_my_RAID_controller_need_.3F
> 
> As a side question to this: if I am using Linux's md software RAID with an
> HBA, and XFS is using write barriers (as I believe it does by default), is
> it still necessary to disable write caching on the drives?

No. The MD layers pass the correct flushes to the drives now.

> My reading of the FAQ suggests that the write barrier by itself should be
> sufficient - but this requires that the md RAID driver implements write
> barriers correctly.  I seem to remember reading a long time ago that LVM
> and/or dmraid didn't, although that may be different now.

It has since about 2.6.35.

> Incidentally I'm using 'mdadm ... -b internal' to ensure that the RAID array
> marks dirty areas, so that if a write part-completes (e.g.  a block is
> written to only one half of a RAID1) then at next power-up this should be
> made consistent again.

Assuming that the dirty area tracking uses write cache flushes
correctly.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: mount: Structure needs cleaning

[Brian Candler]

On Wed, Feb 29, 2012 at 02:50:44PM +1100, Dave Chinner wrote:
> > > http://xfs.org/index.php/XFS_FAQ#Q._Which_settings_does_my_RAID_controller_need_.3F
> > 
> > As a side question to this: if I am using Linux's md software RAID with an
> > HBA, and XFS is using write barriers (as I believe it does by default), is
> > it still necessary to disable write caching on the drives?
> 
> No. The MD layers pass the correct flushes to the drives now.

Thank you: that's very clear and very helpful.

Regards,

Brian.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Mount: Structure needs cleaning

[tommason]

Hi,

First up - my knowledge of linux is pretty sparse - I've used it a few times
before, so please be gentle!

I've had a neil poulton network space for some time now - it freaked out a
while ago and I managed to rig it up to a Ubuntu liveCD via a SATA dock and
rescue the files.

This has now happened again - the drive would not get out of a cycle and was
not spinning properly. Bring out the dock and liveCD (this time Knoppix).
All good. This time however as I eagerly copied files to another drive (a
USB powered lacie rugged thing) and left it overnight i woke up to an error.
I was copying around 500GB in a few diffferent chunks. The first error it
reported was I think error 15? mount structure needs cleaning...

I then tried with a Ubuntu liveCD - same error. This is maybe where I made a
bit of an error of my own. In an attempt to shake it out of it's stupor I
'stupidly' plugged it into windows and opened up the disk utility (sorry I'm
generally mac based) and deleted in total 5 partitions (3x8mb, 1x250odd mb &
1x600mbish partition) This left the partition that I assumed contained all
my files: a 920GB partition. Tried to look at it again on Linux & (both
Knoppix & Ubuntu) and the error message had changed slightly. It now reads:
"Error mounting /dev/sdc2 at
/media/ubuntu/e8b90eb2-8718-4964-939d-8a2b899b68bd: Command-line `mount -t
"xfs" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdc2"
"/media/ubuntu/e8b90eb2-8718-4964-939d-8a2b899b68bd"' exited with non-zero
exit status 32: mount: Structure needs cleaning"

This drive has all my audio and video stored on it! Any help to move me
toward a solution would be much appreciated!

Thanks for your time...

Tom 



--
View this message in context: http://xfs.9218.n7.nabble.com/Mount-Structure-needs-cleaning-tp35026.html
Sent from the Xfs - General mailing list archive at Nabble.com.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: Mount: Structure needs cleaning

[Brian Foster]

On Sun, Oct 12, 2014 at 01:43:28AM -0700, tommason wrote:
> Hi,
> 
> First up - my knowledge of linux is pretty sparse - I've used it a few times
> before, so please be gentle!
> 
> I've had a neil poulton network space for some time now - it freaked out a
> while ago and I managed to rig it up to a Ubuntu liveCD via a SATA dock and
> rescue the files.
> 
> This has now happened again - the drive would not get out of a cycle and was
> not spinning properly. Bring out the dock and liveCD (this time Knoppix).
> All good. This time however as I eagerly copied files to another drive (a
> USB powered lacie rugged thing) and left it overnight i woke up to an error.
> I was copying around 500GB in a few diffferent chunks. The first error it
> reported was I think error 15? mount structure needs cleaning...
> 

Logs? Kernel version? etc.

http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F

> I then tried with a Ubuntu liveCD - same error. This is maybe where I made a
> bit of an error of my own. In an attempt to shake it out of it's stupor I
> 'stupidly' plugged it into windows and opened up the disk utility (sorry I'm
> generally mac based) and deleted in total 5 partitions (3x8mb, 1x250odd mb &
> 1x600mbish partition) This left the partition that I assumed contained all
> my files: a 920GB partition. Tried to look at it again on Linux & (both
> Knoppix & Ubuntu) and the error message had changed slightly. It now reads:
> "Error mounting /dev/sdc2 at
> /media/ubuntu/e8b90eb2-8718-4964-939d-8a2b899b68bd: Command-line `mount -t
> "xfs" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdc2"
> "/media/ubuntu/e8b90eb2-8718-4964-939d-8a2b899b68bd"' exited with non-zero
> exit status 32: mount: Structure needs cleaning"
> 

To be clear, you've deleted partitions other than the partition of
interest? I suppose that shouldn't effect things either way, but I'm not
really sure what the disk utility might do. It might be worth checking
whether 'file -s <device>' still identifies the partition as an XFS
filesystem..?

Beyond that, I'd suggest to capture and post the logs of the failed
mount and perhaps the output of 'xfs_repair -n <dev>.' This will attempt
a dry-run (e.g., no modifications) check and repair of the filesystem.

Brian

> This drive has all my audio and video stored on it! Any help to move me
> toward a solution would be much appreciated!
> 
> Thanks for your time...
> 
> Tom 
> 
> 
> 
> --
> View this message in context: http://xfs.9218.n7.nabble.com/Mount-Structure-needs-cleaning-tp35026.html
> Sent from the Xfs - General mailing list archive at Nabble.com.
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

RE: Mount: Structure needs cleaning

[tom mason]

[-- Attachment #1.1: Type: text/plain, Size: 6063 bytes --]



> Date: Sun, 12 Oct 2014 10:20:08 -0400
> From: bfoster@redhat.com
> To: tom_in_canada@hotmail.com
> CC: xfs@oss.sgi.com
> Subject: Re: Mount: Structure needs cleaning
> 
> On Sun, Oct 12, 2014 at 01:43:28AM -0700, tommason wrote:
> > Hi,
> > 
> > First up - my knowledge of linux is pretty sparse - I've used it a few times
> > before, so please be gentle!
> > 
> > I've had a neil poulton network space for some time now - it freaked out a
> > while ago and I managed to rig it up to a Ubuntu liveCD via a SATA dock and
> > rescue the files.
> > 
> > This has now happened again - the drive would not get out of a cycle and was
> > not spinning properly. Bring out the dock and liveCD (this time Knoppix).
> > All good. This time however as I eagerly copied files to another drive (a
> > USB powered lacie rugged thing) and left it overnight i woke up to an error.
> > I was copying around 500GB in a few diffferent chunks. The first error it
> > reported was I think error 15? mount structure needs cleaning...

> Logs? Kernel version? etc.


Hey Brian,
Apologies! I'm pretty new to all this so you'll have to walk me through it if possible - how do I check the logs?

- Linux ubuntu 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
- xfs_repair version 3.1.9


> 
> http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
> 
> > I then tried with a Ubuntu liveCD - same error. This is maybe where I made a
> > bit of an error of my own. In an attempt to shake it out of it's stupor I
> > 'stupidly' plugged it into windows and opened up the disk utility (sorry I'm
> > generally mac based) and deleted in total 5 partitions (3x8mb, 1x250odd mb &
> > 1x600mbish partition) This left the partition that I assumed contained all
> > my files: a 920GB partition. Tried to look at it again on Linux & (both
> > Knoppix & Ubuntu) and the error message had changed slightly. It now reads:
> > "Error mounting /dev/sdc2 at
> > /media/ubuntu/e8b90eb2-8718-4964-939d-8a2b899b68bd: Command-line `mount -t
> > "xfs" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdc2"
> > "/media/ubuntu/e8b90eb2-8718-4964-939d-8a2b899b68bd"' exited with non-zero
> > exit status 32: mount: Structure needs cleaning"


> To be clear, you've deleted partitions other than the partition of
> interest? I suppose that shouldn't effect things either way, but I'm not
> really sure what the disk utility might do. It might be worth checking
> whether 'file -s <device>' still identifies the partition as an XFS
> filesystem..?


Yes it's a NAS drive and so I assume had some kind of proprietary OS on the other partitions (this is where i might have messed up by deleting?!) I'm pretty sure that the drive in bold below (sdc2) is the one I'm after which is xfs...

ubuntu@ubuntu:~$ sudo lsblk -o NAME,FSTYPE,SIZE,MOUNTPOINT,LABEL
NAME   FSTYPE     SIZE MOUNTPOINT LABEL
sda             596.2G            
├─sda1 vfat       200M            EFI
├─sda2 hfsplus  491.8G            Macintosh HD
├─sda3 hfsplus  619.9M            Recovery HD
└─sda4 ntfs     103.6G            
sdc             931.5G            
├─sdc1              1K            
└─sdc2 xfs      930.6G            
sr0    iso9660    981M /cdrom     Ubuntu 14.04.1 LTS amd64
loop0  squashfs 938.7M /rofs

& This:

ubuntu@ubuntu:~$ sudo fdisk -l

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 640.1 GB, 640135028736 bytes
255 heads, 63 sectors/track, 77825 cylinders, total 1250263728 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x34873486

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1      409639      204819+  ee  GPT
/dev/sda2          409640  1031659623   515624992   af  HFS / HFS+
/dev/sda3      1031659624  1032929167      634772   ab  Darwin boot
/dev/sda4   *  1032929280  1250263039   108666880    7  HPFS/NTFS/exFAT

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x1734c26c

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               2   976773167   488386583    b  W95 FAT32

Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xb06a2add

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1              63     2008124     1004031    5  Extended
/dev/sdc2         2008125  1953520064   975755970   83  Linux


> 
> Beyond that, I'd suggest to capture and post the logs of the failed
> mount and perhaps the output of 'xfs_repair -n <dev>.' This will attempt
> a dry-run (e.g., no modifications) check and repair of the filesystem.

Apologies again but you'd have to walk me through the process of exactly what to type in - as I say I'm really not very experienced with Linux/ubuntu & terminal!
Cheers!
Tom

> Brian
> 
> > This drive has all my audio and video stored on it! Any help to move me
> > toward a solution would be much appreciated!
> > 
> > Thanks for your time...
> > 
> > Tom 
> > 
> > 
> > 
> > --
> > View this message in context: http://xfs.9218.n7.nabble.com/Mount-Structure-needs-cleaning-tp35026.html
> > Sent from the Xfs - General mailing list archive at Nabble.com.
> > 
> > _______________________________________________
> > xfs mailing list
> > xfs@oss.sgi.com
> > http://oss.sgi.com/mailman/listinfo/xfs
 		 	   		  

[-- Attachment #1.2: Type: text/html, Size: 16490 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

RE: Mount: Structure needs cleaning

[tom mason]

[-- Attachment #1.1: Type: text/plain, Size: 6036 bytes --]

ok - so I worked out & tried the xfs_repair command:

root@ubuntu:~# xfs_repair -n /dev/sdc2
Phase 1 - find and verify superblock...
superblock read failed, offset 62448377856, size 131072, ag 2, rval -1

fatal error -- Input/output error






> Date: Sun, 12 Oct 2014 10:20:08 -0400
> From: bfoster@redhat.com
> To: tom_in_canada@hotmail.com
> CC: xfs@oss.sgi.com
> Subject: Re: Mount: Structure needs cleaning
> 
> On Sun, Oct 12, 2014 at 01:43:28AM -0700, tommason wrote:
> > Hi,
> > 
> > First up - my knowledge of linux is pretty sparse - I've used it a few times
> > before, so please be gentle!
> > 
> > I've had a neil poulton network space for some time now - it freaked out a
> > while ago and I managed to rig it up to a Ubuntu liveCD via a SATA dock and
> > rescue the files.
> > 
> > This has now happened again - the drive would not get out of a cycle and was
> > not spinning properly. Bring out the dock and liveCD (this time Knoppix).
> > All good. This time however as I eagerly copied files to another drive (a
> > USB powered lacie rugged thing) and left it overnight i woke up to an error.
> > I was copying around 500GB in a few diffferent chunks. The first error it
> > reported was I think error 15? mount structure needs cleaning...


> Logs? Kernel version? etc.

Hey Brian,
Apologies! I'm pretty new to all this so you'll have to walk me through it if possible - how do I check the logs?

- Linux ubuntu 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
- xfs_repair version 3.1.9


> 
> http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
> 
> > I then tried with a Ubuntu liveCD - same error. This is maybe where I made a
> > bit of an error of my own. In an attempt to shake it out of it's stupor I
> > 'stupidly' plugged it into windows and opened up the disk utility (sorry I'm
> > generally mac based) and deleted in total 5 partitions (3x8mb, 1x250odd mb &
> > 1x600mbish partition) This left the partition that I assumed contained all
> > my files: a 920GB partition. Tried to look at it again on Linux & (both
> > Knoppix & Ubuntu) and the error message had changed slightly. It now reads:
> > "Error mounting /dev/sdc2 at
> > /media/ubuntu/e8b90eb2-8718-4964-939d-8a2b899b68bd: Command-line `mount -t
> > "xfs" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdc2"
> > "/media/ubuntu/e8b90eb2-8718-4964-939d-8a2b899b68bd"' exited with non-zero
> > exit status 32: mount: Structure needs cleaning"


> To be clear, you've deleted partitions other than the partition of
> interest? I suppose that shouldn't effect things either way, but I'm not
> really sure what the disk utility might do. It might be worth checking
> whether 'file -s <device>' still identifies the partition as an XFS
> filesystem..?


Yes it's a NAS drive and so I assume had some kind of proprietary OS on the other partitions (this is where i might have messed up by deleting?!) I'm pretty sure that the drive in bold below (sdc2) is the one I'm after which is xfs...

ubuntu@ubuntu:~$ sudo lsblk -o NAME,FSTYPE,SIZE,MOUNTPOINT,LABEL
NAME   FSTYPE     SIZE MOUNTPOINT LABEL
sda             596.2G            
├─sda1 vfat       200M            EFI
├─sda2 hfsplus  491.8G            Macintosh HD
├─sda3 hfsplus  619.9M            Recovery HD
└─sda4 ntfs     103.6G            
sdc             931.5G            
├─sdc1              1K            
└─sdc2 xfs      930.6G            
sr0    iso9660    981M /cdrom     Ubuntu 14.04.1 LTS amd64
loop0  squashfs 938.7M /rofs

& This:

ubuntu@ubuntu:~$ sudo fdisk -l

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 640.1 GB, 640135028736 bytes
255 heads, 63 sectors/track, 77825 cylinders, total 1250263728 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x34873486

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1      409639      204819+  ee  GPT
/dev/sda2          409640  1031659623   515624992   af  HFS / HFS+
/dev/sda3      1031659624  1032929167      634772   ab  Darwin boot
/dev/sda4   *  1032929280  1250263039   108666880    7  HPFS/NTFS/exFAT

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x1734c26c

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               2   976773167   488386583    b  W95 FAT32

Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xb06a2add

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1              63     2008124     1004031    5  Extended
/dev/sdc2         2008125  1953520064   975755970   83  Linux


> 
> Beyond that, I'd suggest to capture and post the logs of the failed
> mount and perhaps the output of 'xfs_repair -n <dev>.' This will attempt
> a dry-run (e.g., no modifications) check and repair of the filesystem.

Apologies again but you'd have to walk me through the process of exactly what to type in - as I say I'm really not very experienced with Linux/ubuntu & terminal!
Cheers!
Tom

> Brian
> 
> > This drive has all my audio and video stored on it! Any help to move me
> > toward a solution would be much appreciated!
> > 
> > Thanks for your time...
> > 

> > xfs@oss.sgi.com
> > http://oss.sgi.com/mailman/listinfo/xfs
 		 	   		   		 	   		  

[-- Attachment #1.2: Type: text/html, Size: 16083 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

RE: Mount: Structure needs cleaning

[tom mason]

[-- Attachment #1.1: Type: text/plain, Size: 6264 bytes --]

and now xfs_check:

root@ubuntu:~# xfs_check /dev/sdc2
ERROR: The filesystem has valuable metadata changes in a log which needs to
be replayed.  Mount the filesystem to replay the log, and unmount it before
re-running xfs_check.  If you are unable to mount the filesystem, then use
the xfs_repair -L option to destroy the log and attempt a repair.
Note that destroying the log may cause corruption -- please attempt a mount
of the filesystem before doing this.


> Date: Sun, 12 Oct 2014 10:20:08 -0400
> From: bfoster@redhat.com
> To: tom_in_canada@hotmail.com
> CC: xfs@oss.sgi.com
> Subject: Re: Mount: Structure needs cleaning
> 
> On Sun, Oct 12, 2014 at 01:43:28AM -0700, tommason wrote:
> > Hi,
> > 
> > First up - my knowledge of linux is pretty sparse - I've used it a few times
> > before, so please be gentle!
> > 
> > I've had a neil poulton network space for some time now - it freaked out a
> > while ago and I managed to rig it up to a Ubuntu liveCD via a SATA dock and
> > rescue the files.
> > 
> > This has now happened again - the drive would not get out of a cycle and was
> > not spinning properly. Bring out the dock and liveCD (this time Knoppix).
> > All good. This time however as I eagerly copied files to another drive (a
> > USB powered lacie rugged thing) and left it overnight i woke up to an error.
> > I was copying around 500GB in a few diffferent chunks. The first error it
> > reported was I think error 15? mount structure needs cleaning...


> Logs? Kernel version? etc.

Hey Brian,
Apologies! I'm pretty new to all this so you'll have to walk me through it if possible - how do I check the logs?

- Linux ubuntu 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
- xfs_repair version 3.1.9


> 
> http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
> 
> > I then tried with a Ubuntu liveCD - same error. This is maybe where I made a
> > bit of an error of my own. In an attempt to shake it out of it's stupor I
> > 'stupidly' plugged it into windows and opened up the disk utility (sorry I'm
> > generally mac based) and deleted in total 5 partitions (3x8mb, 1x250odd mb &
> > 1x600mbish partition) This left the partition that I assumed contained all
> > my files: a 920GB partition. Tried to look at it again on Linux & (both
> > Knoppix & Ubuntu) and the error message had changed slightly. It now reads:
> > "Error mounting /dev/sdc2 at
> > /media/ubuntu/e8b90eb2-8718-4964-939d-8a2b899b68bd: Command-line `mount -t
> > "xfs" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdc2"
> > "/media/ubuntu/e8b90eb2-8718-4964-939d-8a2b899b68bd"' exited with non-zero
> > exit status 32: mount: Structure needs cleaning"


> To be clear, you've deleted partitions other than the partition of
> interest? I suppose that shouldn't effect things either way, but I'm not
> really sure what the disk utility might do. It might be worth checking
> whether 'file -s <device>' still identifies the partition as an XFS
> filesystem..?


Yes it's a NAS drive and so I assume had some kind of proprietary OS on the other partitions (this is where i might have messed up by deleting?!) I'm pretty sure that the drive in bold below (sdc2) is the one I'm after which is xfs...

ubuntu@ubuntu:~$ sudo lsblk -o NAME,FSTYPE,SIZE,MOUNTPOINT,LABEL
NAME   FSTYPE     SIZE MOUNTPOINT LABEL
sda             596.2G            
├─sda1 vfat       200M            EFI
├─sda2 hfsplus  491.8G            Macintosh HD
├─sda3 hfsplus  619.9M            Recovery HD
└─sda4 ntfs     103.6G            
sdc             931.5G            
├─sdc1              1K            
└─sdc2 xfs      930.6G            
sr0    iso9660    981M /cdrom     Ubuntu 14.04.1 LTS amd64
loop0  squashfs 938.7M /rofs

& This:

ubuntu@ubuntu:~$ sudo fdisk -l

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 640.1 GB, 640135028736 bytes
255 heads, 63 sectors/track, 77825 cylinders, total 1250263728 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x34873486

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1      409639      204819+  ee  GPT
/dev/sda2          409640  1031659623   515624992   af  HFS / HFS+
/dev/sda3      1031659624  1032929167      634772   ab  Darwin boot
/dev/sda4   *  1032929280  1250263039   108666880    7  HPFS/NTFS/exFAT

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x1734c26c

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               2   976773167   488386583    b  W95 FAT32

Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xb06a2add

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1              63     2008124     1004031    5  Extended
/dev/sdc2         2008125  1953520064   975755970   83  Linux


> 
> Beyond that, I'd suggest to capture and post the logs of the failed
> mount and perhaps the output of 'xfs_repair -n <dev>.' This will attempt
> a dry-run (e.g., no modifications) check and repair of the filesystem.

Apologies again but you'd have to walk me through the process of exactly what to type in - as I say I'm really not very experienced with Linux/ubuntu & terminal!
Cheers!
Tom

> Brian
> 
> > This drive has all my audio and video stored on it! Any help to move me
> > toward a solution would be much appreciated!
> > 
> > Thanks for your time...
> > 

> > xfs@oss.sgi.com
> > http://oss.sgi.com/mailman/listinfo/xfs
 		 	   		   		 	   		   		 	   		  

[-- Attachment #1.2: Type: text/html, Size: 16429 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: Mount: Structure needs cleaning

[Dave Chinner]

[ please don't top post. ]

On Sun, Oct 12, 2014 at 10:48:36PM +0000, tom mason wrote:
> > Date: Sun, 12 Oct 2014 10:20:08 -0400
> > From: bfoster@redhat.com
> > To: tom_in_canada@hotmail.com
> > CC: xfs@oss.sgi.com
> > Subject: Re: Mount: Structure needs cleaning
> > 
> > On Sun, Oct 12, 2014 at 01:43:28AM -0700, tommason wrote:
> > > Hi,
> > > 
> > > First up - my knowledge of linux is pretty sparse - I've used it a few times
> > > before, so please be gentle!
> > > 
> > > I've had a neil poulton network space for some time now - it freaked out a
> > > while ago and I managed to rig it up to a Ubuntu liveCD via a SATA dock and
> > > rescue the files.
> > > 
> > > This has now happened again - the drive would not get out of a cycle and was
> > > not spinning properly. Bring out the dock and liveCD (this time Knoppix).
> > > All good. This time however as I eagerly copied files to another drive (a
> > > USB powered lacie rugged thing) and left it overnight i woke up to an error.
> > > I was copying around 500GB in a few diffferent chunks. The first error it
> > > reported was I think error 15? mount structure needs cleaning...
> 
> 
> > Logs? Kernel version? etc.
> 
> Hey Brian,
> Apologies! I'm pretty new to all this so you'll have to walk me through it if possible - how do I check the logs?
> 
> - Linux ubuntu 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
> - xfs_repair version 3.1.9
>
> ok - so I worked out & tried the xfs_repair command:
> 
> root@ubuntu:~# xfs_repair -n /dev/sdc2
> Phase 1 - find and verify superblock...
> superblock read failed, offset 62448377856, size 131072, ag 2, rval -1
> 
> fatal error -- Input/output error

Which means the filesystem tried to read the offset at 62GB and the
underlying device failed it with EIO. That's not an XFS failure.
What error is there in dmesg when you run that xfs_repair command?

> > http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F

This asks you to post the contents of /proc/partitions, which is
what the kernel thinks are the partition sizes.

> Yes it's a NAS drive and so I assume had some kind of proprietary
> OS on the other partitions (this is where i might have messed up
> by deleting?!) I'm pretty sure that the drive in bold below (sdc2)
> is the one I'm after which is xfs...

Ummm, exactly what are you trying to do with this drive/filesystem?
What device did the drive come from in the first place?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: Mount: Structure needs cleaning

[Emmanuel Florac]

Le Sun, 12 Oct 2014 22:48:36 +0000
tom mason <tom_in_canada@hotmail.com> écrivait:

> superblock read failed, offset 62448377856, size 131072, ag 2, rval -1
> 
> fatal error -- Input/output error

You've got an hardware error here. Probably a bad disk drive. What does 

smartcl -A /dev/sdc

reports?

-- 
------------------------------------------------------------------------
Emmanuel Florac     |   Direction technique
                    |   Intellique
                    |	<eflorac@intellique.com>
                    |   +33 1 78 94 84 02
------------------------------------------------------------------------

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: Mount: Structure needs cleaning

[Tom Mason]

> On 13 Oct 2014, at 00:10, Dave Chinner <david@fromorbit.com> wrote:
> 
> [ please don't top post. ]
> 
> On Sun, Oct 12, 2014 at 10:48:36PM +0000, tom mason wrote:
>>> Date: Sun, 12 Oct 2014 10:20:08 -0400
>>> From: bfoster@redhat.com
>>> To: tom_in_canada@hotmail.com
>>> CC: xfs@oss.sgi.com
>>> Subject: Re: Mount: Structure needs cleaning
>>> 
>>>> On Sun, Oct 12, 2014 at 01:43:28AM -0700, tommason wrote:
>>>> Hi,
>>>> 
>>>> First up - my knowledge of linux is pretty sparse - I've used it a few times
>>>> before, so please be gentle!
>>>> 
>>>> I've had a neil poulton network space for some time now - it freaked out a
>>>> while ago and I managed to rig it up to a Ubuntu liveCD via a SATA dock and
>>>> rescue the files.
>>>> 
>>>> This has now happened again - the drive would not get out of a cycle and was
>>>> not spinning properly. Bring out the dock and liveCD (this time Knoppix).
>>>> All good. This time however as I eagerly copied files to another drive (a
>>>> USB powered lacie rugged thing) and left it overnight i woke up to an error.
>>>> I was copying around 500GB in a few diffferent chunks. The first error it
>>>> reported was I think error 15? mount structure needs cleaning...
>> 
>> 
>>> Logs? Kernel version? etc.
>> 
>> Hey Brian,
>> Apologies! I'm pretty new to all this so you'll have to walk me through it if possible - how do I check the logs?
>> 
>> - Linux ubuntu 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
>> - xfs_repair version 3.1.9
>> 
>> ok - so I worked out & tried the xfs_repair command:
>> 
>> root@ubuntu:~# xfs_repair -n /dev/sdc2
>> Phase 1 - find and verify superblock...
>> superblock read failed, offset 62448377856, size 131072, ag 2, rval -1
>> 
>> fatal error -- Input/output error
> 
> Which means the filesystem tried to read the offset at 62GB and the
> underlying device failed it with EIO. That's not an XFS failure.
> What error is there in dmesg when you run that xfs_repair command?

What's EIO?
'Error in dmesg' How would I report this info to you? 





> 
>>> http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
> 
> This asks you to post the contents of /proc/partitions, which is
> what the kernel thinks are the partition sizes.

How do I do this?


> 
>> Yes it's a NAS drive and so I assume had some kind of proprietary
>> OS on the other partitions (this is where i might have messed up
>> by deleting?!) I'm pretty sure that the drive in bold below (sdc2)
>> is the one I'm after which is xfs...
> 
> Ummm, exactly what are you trying to do with this drive/filesystem?
> What device did the drive come from in the first place?

It's a lacie 'Neil poulton' network space1 1tb NAS drive (see first paragraph of post) - it recently stopped working and was stuck in a 'spin cycle' - it contains my music and video backups. I'm trying to recover the files...

Cheers,

Tom



> 
> Cheers,
> 
> Dave.
> -- 
> Dave Chinner
> david@fromorbit.com
> 

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: Mount: Structure needs cleaning

[Emmanuel Florac]

Le Mon, 13 Oct 2014 11:05:49 +0100
Tom Mason <tom_mason@me.com> écrivait:

> > Which means the filesystem tried to read the offset at 62GB and the
> > underlying device failed it with EIO. That's not an XFS failure.
> > What error is there in dmesg when you run that xfs_repair command?  
> 
> What's EIO?
> 'Error in dmesg' How would I report this info to you? 

"Input/Output Error" . Run the "dmesg" command immediately after
this error, and see what it reports last (end of command output).

> > This asks you to post the contents of /proc/partitions, which is
> > what the kernel thinks are the partition sizes.  
> 
> How do I do this?

cat /proc/partitions

> >> Yes it's a NAS drive and so I assume had some kind of proprietary
> >> OS on the other partitions (this is where i might have messed up
> >> by deleting?!) I'm pretty sure that the drive in bold below (sdc2)
> >> is the one I'm after which is xfs...  
> > 
> > Ummm, exactly what are you trying to do with this drive/filesystem?
> > What device did the drive come from in the first place?  
> 
> It's a lacie 'Neil poulton' network space1 1tb NAS drive (see first
> paragraph of post) - it recently stopped working and was stuck in a
> 'spin cycle' - it contains my music and video backups. I'm trying to
> recover the files...

Most probably disk is badly damaged, dead or dying. It's advisable to
try to create an image of the disk on another one, and work for this
image, because this disk will probably die any time now. It's no use
trying to repair a filesystem on a bad drive, which is the cause of the
errors from the beginning. 

If all you care is to get your files back, just try to mount the volume
in read-only, non-recovery mode :

mount -o ro,norecovery /dev/sdc2 /tmp/mount

Then proceed by copying whatever you can get. Consider that any file
that gives an error is lost.

The other option is Kroll Ontrack or similar services, of course.

-- 
------------------------------------------------------------------------
Emmanuel Florac     |   Direction technique
                    |   Intellique
                    |	<eflorac@intellique.com>
                    |   +33 1 78 94 84 02
------------------------------------------------------------------------

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: Mount: Structure needs cleaning

[Tom Mason]

> On 13 Oct 2014, at 11:19, Emmanuel Florac <eflorac@intellique.com> wrote:
> 
> Le Mon, 13 Oct 2014 11:05:49 +0100
> Tom Mason <tom_mason@me.com> écrivait:
> 
>>> Which means the filesystem tried to read the offset at 62GB and the
>>> underlying device failed it with EIO. That's not an XFS failure.
>>> What error is there in dmesg when you run that xfs_repair command?  
>> 
>> What's EIO?
>> 'Error in dmesg' How would I report this info to you?
> 
> "Input/Output Error" . Run the "dmesg" command immediately after
> this error, and see what it reports last (end of command output).
> 
>>> This asks you to post the contents of /proc/partitions, which is
>>> what the kernel thinks are the partition sizes.  
>> 
>> How do I do this?
> 
> cat /proc/partitions
> 
>>>> Yes it's a NAS drive and so I assume had some kind of proprietary
>>>> OS on the other partitions (this is where i might have messed up
>>>> by deleting?!) I'm pretty sure that the drive in bold below (sdc2)
>>>> is the one I'm after which is xfs...  
>>> 
>>> Ummm, exactly what are you trying to do with this drive/filesystem?
>>> What device did the drive come from in the first place?  
>> 
>> It's a lacie 'Neil poulton' network space1 1tb NAS drive (see first
>> paragraph of post) - it recently stopped working and was stuck in a
>> 'spin cycle' - it contains my music and video backups. I'm trying to
>> recover the files...
> 
> Most probably disk is badly damaged, dead or dying. It's advisable to
> try to create an image of the disk on another one, and work for this
> image, because this disk will probably die any time now. It's no use
> trying to repair a filesystem on a bad drive, which is the cause of the
> errors from the beginning. 
> 
> If all you care is to get your files back, just try to mount the volume
> in read-only, non-recovery mode :
> 
> mount -o ro,norecovery /dev/sdc2 /tmp/mount
> 
> Then proceed by copying whatever you can get. Consider that any file
> that gives an error is lost.
> 
> The other option is Kroll Ontrack or similar services, of course.
> 
> Emmanuel Florac     

Thanks everyone - I'm away from the device at the moment so will report back when I get home, in about 8 hours or so..
Tom
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: Mount: Structure needs cleaning

[Tom Mason]

[-- Attachment #1.1: Type: text/plain, Size: 31552 bytes --]



On Oct 13, 2014, at 11:19 AM, Emmanuel Florac <eflorac@intellique.com> wrote:

> Le Mon, 13 Oct 2014 11:05:49 +0100
> Tom Mason <tom_mason@me.com    > écrivait:
>
>        >      > Which means the filesystem tried to read the offset at 62GB and the
>        >      > underlying device failed it with EIO. That's not an XFS failure.
>        >      > What error is there in dmesg when you run that xfs_repair command?
>        >
>        > What's EIO?
>        > 'Error in dmesg' How would I report this info to you?
 
r 1
[    6.829125] ehci-pci 0000:00:04.1: debug port 1
[    6.829162] ehci-pci 0000:00:04.1: cache line size of 256 is not supported
[    6.829185] ehci-pci 0000:00:04.1: irq 22, io mem 0xd0489200
[    6.840043] ehci-pci 0000:00:04.1: USB 2.0 started, EHCI 1.00
[    6.840112] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    6.840116] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    6.840119] usb usb1: Product: EHCI Host Controller
[    6.840122] usb usb1: Manufacturer: Linux 3.13.0-32-generic ehci_hcd
[    6.840125] usb usb1: SerialNumber: 0000:00:04.1
[    6.840295] hub 1-0:1.0: USB hub found
[    6.840307] hub 1-0:1.0: 7 ports detected
[    6.840791] ehci-pci 0000:00:06.1: EHCI Host Controller
[    6.840799] ehci-pci 0000:00:06.1: new USB bus registered, assigned bus number 2
[    6.840809] ehci-pci 0000:00:06.1: debug port 1
[    6.840837] ehci-pci 0000:00:06.1: cache line size of 256 is not supported
[    6.840855] ehci-pci 0000:00:06.1: irq 20, io mem 0xd0489100
[    6.852097] ehci-pci 0000:00:06.1: USB 2.0 started, EHCI 1.00
[    6.852153] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[    6.852156] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    6.852160] usb usb2: Product: EHCI Host Controller
[    6.852163] usb usb2: Manufacturer: Linux 3.13.0-32-generic ehci_hcd
[    6.852166] usb usb2: SerialNumber: 0000:00:06.1
[    6.852324] hub 2-0:1.0: USB hub found
[    6.852337] hub 2-0:1.0: 5 ports detected
[    6.852595] ehci-platform: EHCI generic platform driver
[    6.852609] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    6.852611] ohci-pci: OHCI PCI platform driver
[    6.852818] ohci-pci 0000:00:04.0: OHCI PCI host controller
[    6.852825] ohci-pci 0000:00:04.0: new USB bus registered, assigned bus number 3
[    6.852852] ohci-pci 0000:00:04.0: irq 23, io mem 0xd0488000
[    6.910128] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[    6.910132] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    6.910135] usb usb3: Product: OHCI PCI host controller
[    6.910138] usb usb3: Manufacturer: Linux 3.13.0-32-generic ohci_hcd
[    6.910141] usb usb3: SerialNumber: 0000:00:04.0
[    6.910291] hub 3-0:1.0: USB hub found
[    6.910304] hub 3-0:1.0: 7 ports detected
[    6.910784] ohci-pci 0000:00:06.0: OHCI PCI host controller
[    6.910792] ohci-pci 0000:00:06.0: new USB bus registered, assigned bus number 4
[    6.910817] ohci-pci 0000:00:06.0: irq 21, io mem 0xd0487000
[    6.966125] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
[    6.966130] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    6.966133] usb usb4: Product: OHCI PCI host controller
[    6.966136] usb usb4: Manufacturer: Linux 3.13.0-32-generic ohci_hcd
[    6.966139] usb usb4: SerialNumber: 0000:00:06.0
[    6.966289] hub 4-0:1.0: USB hub found
[    6.966302] hub 4-0:1.0: 5 ports detected
[    6.966553] ohci-platform: OHCI generic platform driver
[    6.966564] uhci_hcd: USB Universal Host Controller Interface driver
[    6.966638] i8042: PNP: No PS/2 controller found. Probing ports directly.
[    7.993878] i8042: No controller found
[    7.993976] mousedev: PS/2 mouse device common for all mice
[    7.994467] rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
[    7.994520] rtc_cmos 00:06: alarms up to one year, y3k, 242 bytes nvram, hpet irqs
[    7.994609] device-mapper: uevent: version 1.0.3
[    7.994707] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
[    7.994714] ledtrig-cpu: registered to indicate activity on CPUs
[    7.994853] TCP: cubic registered
[    7.994990] NET: Registered protocol family 10
[    7.995233] NET: Registered protocol family 17
[    7.995252] Key type dns_resolver registered
[    7.995588] Loading compiled-in X.509 certificates
[    7.997230] Loaded X.509 cert 'Magrathea: Glacier signing key: 5e3c0f9ca6e36543535fa2bb5b709e84f16da7c7'
[    7.997251] registered taskstats version 1
[    8.001292] Key type trusted registered
[    8.004490] Key type encrypted registered
[    8.007652] AppArmor: AppArmor sha1 policy hashing enabled
[    8.007656] IMA: No TPM chip found, activating TPM-bypass!
[    8.008268] regulator-dummy: disabling
[    8.008332]   Magic number: 2:86:43
[    8.008478] rtc_cmos 00:06: setting system clock to 2014-10-13 20:01:54 UTC (1413230514)
[    8.009069] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[    8.009072] EDD information not available.
[    8.009129] PM: Hibernation image not present or could not be loaded.
[    8.010552] Freeing unused kernel memory: 1336K (ffffffff81d1f000 - ffffffff81e6d000)
[    8.010554] Write protecting the kernel read-only data: 12288k
[    8.012782] Freeing unused kernel memory: 816K (ffff880001734000 - ffff880001800000)
[    8.014538] Freeing unused kernel memory: 696K (ffff880001b52000 - ffff880001c00000)
[    8.027129] systemd-udevd[100]: starting version 204
[    8.050650] forcedeth: Reverse Engineered nForce ethernet driver. Version 0.64.
[    8.050899] ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 16
[    8.060498] [drm] Initialized drm 1.1.0 20060810
[    8.088254] firewire_ohci 0000:04:00.0: irq 43 for MSI/MSI-X
[    8.090165] [drm] radeon kernel modesetting enabled.
[    8.090427] [drm] initializing kernel modesetting (RV770 0x1002:0x944A 0x106B:0x944A).
[    8.090442] [drm] register mmio base: 0xD0220000
[    8.090443] [drm] register mmio size: 65536
[    8.090492] radeon 0000:02:00.0: Invalid ROM contents
[    8.091227] ATOM BIOS: 113
[    8.091254] radeon 0000:02:00.0: VRAM: 512M 0x0000000000000000 - 0x000000001FFFFFFF (512M used)
[    8.091256] radeon 0000:02:00.0: GTT: 1024M 0x0000000020000000 - 0x000000005FFFFFFF
[    8.091258] [drm] Detected VRAM RAM=512M, BAR=256M
[    8.091259] [drm] RAM width 256bits DDR
[    8.091404] [TTM] Zone  kernel: Available graphics memory: 4076328 kiB
[    8.091405] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[    8.091406] [TTM] Initializing pool allocator
[    8.091411] [TTM] Initializing DMA pool allocator
[    8.091427] [drm] radeon: 512M of VRAM memory ready
[    8.091428] [drm] radeon: 1024M of GTT memory ready.
[    8.091441] [drm] Loading RV770 Microcode
[    8.091512] [drm] GART: num cpu pages 262144, num gpu pages 262144
[    8.094226] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0
[    8.111879] usb 1-4: new high-speed USB device number 2 using ehci-pci
[    8.111916] ssb: Found chip with id 0x4322, rev 0x01 and package 0x0A
[    8.111921] ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x17, vendor 0x4243)
[    8.111927] ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x10, vendor 0x4243)
[    8.111932] ssb: Core 2 found: PCI-E (cc 0x820, rev 0x0B, vendor 0x4243)
[    8.111937] ssb: Core 3 found: PCI (cc 0x804, rev 0x0E, vendor 0x4243)
[    8.111942] ssb: Core 4 found: USB 2.0 Device (cc 0x81A, rev 0x05, vendor 0x4243)
[    8.111947] ssb: Core 5 found: UNKNOWN (cc 0x8FF, rev 0x00, vendor 0x4243)
[    8.111953] ssb: Core 6 found: Internal Memory (cc 0x80E, rev 0x03, vendor 0x4243)
[    8.113736] [drm] PCIE GART of 1024M enabled (table at 0x0000000000040000).
[    8.113775] radeon 0000:02:00.0: WB enabled
[    8.113778] radeon 0000:02:00.0: fence driver on ring 0 use gpu addr 0x0000000020000c00 and cpu addr 0xffff88023352ec00
[    8.113780] radeon 0000:02:00.0: fence driver on ring 3 use gpu addr 0x0000000020000c0c and cpu addr 0xffff88023352ec0c
[    8.113783] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    8.113784] [drm] Driver supports precise vblank timestamp query.
[    8.113805] radeon 0000:02:00.0: irq 44 for MSI/MSI-X
[    8.113816] radeon 0000:02:00.0: radeon: using MSI.
[    8.113841] [drm] radeon: irq initialized.
[    8.129822] forcedeth 0000:00:0a.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:25:00:a5:98:42
[    8.129825] forcedeth 0000:00:0a.0: highdma csum pwrctl gbit lnktim msi desc-v3
[    8.144058] firewire_ohci 0000:04:00.0: added OHCI v1.10 device as card 0, 8 IR + 8 IT contexts, quirks 0x0
[    8.161628] [drm] ring test on 0 succeeded in 0 usecs
[    8.161806] [drm] ring test on 3 succeeded in 0 usecs
[    8.162282] [drm] Enabling audio 0 support
[    8.162342] [drm] ib test on ring 0 succeeded in 0 usecs
[    8.162880] [drm] ib test on ring 3 succeeded in 0 usecs
[    8.168632] ahci 0000:00:0b.0: version 3.0
[    8.169043] ACPI: PCI Interrupt Link [LSI0] enabled at IRQ 23
[    8.170020] ahci 0000:00:0b.0: irq 45 for MSI/MSI-X
[    8.170036] ahci 0000:00:0b.0: controller can't do PMP, turning off CAP_PMP
[    8.170104] ahci 0000:00:0b.0: AHCI 0001.0200 32 slots 6 ports 3 Gbps 0x3 impl IDE mode
[    8.170107] ahci 0000:00:0b.0: flags: 64bit ncq sntf pm led pio slum part boh
[    8.170957] scsi0 : ahci
[    8.171028] scsi1 : ahci
[    8.171081] scsi2 : ahci
[    8.171130] scsi3 : ahci
[    8.171180] scsi4 : ahci
[    8.171235] scsi5 : ahci
[    8.171268] ata1: SATA max UDMA/133 abar m8192@0xd0484000 port 0xd0484100 irq 45
[    8.171270] ata2: SATA max UDMA/133 abar m8192@0xd0484000 port 0xd0484180 irq 45
[    8.171271] ata3: DUMMY
[    8.171272] ata4: DUMMY
[    8.171273] ata5: DUMMY
[    8.171274] ata6: DUMMY
[    8.192095] [drm] radeon atom DIG backlight initialized
[    8.192099] [drm] Radeon Display Connectors
[    8.192101] [drm] Connector 0:
[    8.192103] [drm]   DP-1
[    8.192105] [drm]   HPD2
[    8.192108] [drm]   DDC: 0x7e60 0x7e60 0x7e64 0x7e64 0x7e68 0x7e68 0x7e6c 0x7e6c
[    8.192110] [drm]   Encoders:
[    8.192112] [drm]     DFP1: INTERNAL_UNIPHY
[    8.192114] [drm] Connector 1:
[    8.192116] [drm]   DP-2
[    8.192117] [drm]   HPD3
[    8.192120] [drm]   DDC: 0x7e20 0x7e20 0x7e24 0x7e24 0x7e28 0x7e28 0x7e2c 0x7e2c
[    8.192122] [drm]   Encoders:
[    8.192123] [drm]     DFP2: INTERNAL_UNIPHY
[    8.192125] [drm] Connector 2:
[    8.192127] [drm]   LVDS-1
[    8.192129] [drm]   Encoders:
[    8.192130] [drm]     LCD1: INTERNAL_KLDSCP_LVTMA
[    8.192132] [drm] Connector 3:
[    8.192134] [drm]   VGA-1
[    8.192137] [drm]   DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c
[    8.192138] [drm]   Encoders:
[    8.192140] [drm]     CRT1: INTERNAL_KLDSCP_DAC1
[    8.192279] [drm] Special thermal controller config
[    8.192290] [drm] radeon: power management initialized
[    8.220198] ssb: Sonics Silicon Backplane found on PCI device 0000:03:00.0
[    8.276286] usb 1-4: Duplicate descriptor for config 1 interface 1 altsetting 5, skipping
[    8.276291] usb 1-4: config 1 interface 1 has no altsetting 1
[    8.277975] usb 1-4: New USB device found, idVendor=05ac, idProduct=8502
[    8.277979] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    8.277982] usb 1-4: Product: Built-in iSight
[    8.277985] usb 1-4: Manufacturer: Apple Inc.
[    8.277988] usb 1-4: SerialNumber: 8J94412442CX3E00
[    8.488109] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    8.489125] ata1.00: ATA-8: Hitachi HDT721064SLA360, ST0KA36A, max UDMA/133
[    8.489129] ata1.00: 1250263728 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    8.490389] ata1.00: configured for UDMA/133
[    8.490581] scsi 0:0:0:0: Direct-Access     ATA      Hitachi HDT72106 ST0K PQ: 0 ANSI: 5
[    8.490699] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    8.490783] sd 0:0:0:0: [sda] 1250263728 512-byte logical blocks: (640 GB/596 GiB)
[    8.490898] sd 0:0:0:0: [sda] Write Protect is off
[    8.490901] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    8.490948] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    8.492063] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    8.496523] ata2.00: ATAPI: HL-DT-ST DVDRW  GA11N, KA16, max UDMA/133
[    8.502177] ata2.00: configured for UDMA/133
[    8.508246] scsi 1:0:0:0: CD-ROM            HL-DT-ST DVDRW  GA11N     KA16 PQ: 0 ANSI: 5
[    8.512429] sr0: scsi3-mmc drive: 31x/31x writer cd/rw xa/form2 cdda caddy
[    8.512432] cdrom: Uniform CD-ROM driver Revision: 3.20
[    8.512534] sr 1:0:0:0: Attached scsi CD-ROM sr0
[    8.512578] sr 1:0:0:0: Attached scsi generic sg1 type 5
[    8.555847]  sda: sda1 sda2 sda3 sda4
[    8.556239] sd 0:0:0:0: [sda] Attached SCSI disk
[    8.644196] firewire_core 0000:04:00.0: created device fw0: GUID 002500fffea59842, S800
[    8.704105] usb 2-4: new high-speed USB device number 3 using ehci-pci
[    8.844637] usb 2-4: New USB device found, idVendor=05ac, idProduct=1006
[    8.844641] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    8.844645] usb 2-4: Product: Keyboard Hub
[    8.844648] usb 2-4: Manufacturer: Apple, Inc.
[    8.844651] usb 2-4: SerialNumber: 000000000000
[    8.844900] hub 2-4:1.0: USB hub found
[    8.845009] hub 2-4:1.0: 3 ports detected
[    8.887236] [drm] fb mappable at 0xC0241000
[    8.887238] [drm] vram apper at 0xC0000000
[    8.887239] [drm] size 9216000
[    8.887240] [drm] fb depth is 24
[    8.887241] [drm]    pitch is 7680
[    8.887305] fbcon: radeondrmfb (fb0) is primary device
[    8.937101] Console: switching to colour frame buffer device 240x75
[    8.942022] radeon 0000:02:00.0: fb0: radeondrmfb frame buffer device
[    8.942024] radeon 0000:02:00.0: registered panic notifier
[    8.942033] [drm] Initialized radeon 2.36.0 20080528 for 0000:02:00.0 on minor 0
[    9.148130] usb 4-1: new full-speed USB device number 2 using ohci-pci
[    9.370182] usb 4-1: New USB device found, idVendor=0a5c, idProduct=4500
[    9.370187] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    9.370191] usb 4-1: Product: BRCM2046 Hub
[    9.370194] usb 4-1: Manufacturer: Apple Inc.
[    9.373223] hub 4-1:1.0: USB hub found
[    9.376193] hub 4-1:1.0: 3 ports detected
[    9.820112] usb 3-5: new low-speed USB device number 2 using ohci-pci
[   10.035180] usb 3-5: New USB device found, idVendor=05ac, idProduct=8242
[   10.035184] usb 3-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   10.035188] usb 3-5: Product: IR Receiver
[   10.035191] usb 3-5: Manufacturer: Apple Computer, Inc.
[   10.044975] hidraw: raw HID events driver (C) Jiri Kosina
[   10.052155] usbcore: registered new interface driver usbhid
[   10.052156] usbhid: USB HID core driver
[   10.112160] usb 2-4.2: new low-speed USB device number 4 using ehci-pci
[   10.211410] usb 2-4.2: New USB device found, idVendor=05ac, idProduct=0221
[   10.211414] usb 2-4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   10.211418] usb 2-4.2: Product: Apple Keyboard
[   10.211421] usb 2-4.2: Manufacturer: Apple, Inc
[   10.219118] input: Apple, Inc Apple Keyboard as /devices/pci0000:00/0000:00:06.1/usb2/2-4/2-4.2/2-4.2:1.0/input/input3
[   10.219184] apple 0003:05AC:0221.0002: input,hidraw0: USB HID v1.11 Keyboard [Apple, Inc Apple Keyboard] on usb-0000:00:06.1-4.2/input0
[   10.219906] input: Apple, Inc Apple Keyboard as /devices/pci0000:00/0000:00:06.1/usb2/2-4/2-4.2/2-4.2:1.1/input/input4
[   10.219967] apple 0003:05AC:0221.0003: input,hidraw1: USB HID v1.11 Device [Apple, Inc Apple Keyboard] on usb-0000:00:06.1-4.2/input1
[   10.288162] usb 2-4.3: new low-speed USB device number 5 using ehci-pci
[   10.386637] usb 2-4.3: New USB device found, idVendor=05ac, idProduct=0304
[   10.386642] usb 2-4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   10.386645] usb 2-4.3: Product: Apple Optical USB Mouse
[   10.386648] usb 2-4.3: Manufacturer: Mitsumi Electric
[   10.389628] input: Mitsumi Electric Apple Optical USB Mouse as /devices/pci0000:00/0000:00:06.1/usb2/2-4/2-4.3/2-4.3:1.0/input/input5
[   10.389708] apple 0003:05AC:0304.0004: input,hidraw2: USB HID v1.10 Mouse [Mitsumi Electric Apple Optical USB Mouse] on usb-0000:00:06.1-4.3/input0
[   10.466183] usb 4-1.1: new full-speed USB device number 3 using ohci-pci
[   10.588182] usb 4-1.1: New USB device found, idVendor=05ac, idProduct=8215
[   10.588187] usb 4-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   10.588190] usb 4-1.1: Product: Bluetooth USB Host Controller
[   10.588193] usb 4-1.1: Manufacturer: Apple Inc.
[   10.588196] usb 4-1.1: SerialNumber: 002500C0F736
[   10.665180] usb 4-1.2: new full-speed USB device number 4 using ohci-pci
[   10.776183] usb 4-1.2: New USB device found, idVendor=05ac, idProduct=820a
[   10.776188] usb 4-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[   10.788074] input: HID 05ac:820a as /devices/pci0000:00/0000:00:06.0/usb4/4-1/4-1.2/4-1.2:1.0/input/input6
[   10.788130] hid-generic 0003:05AC:820A.0005: input,hidraw3: USB HID v1.11 Keyboard [HID 05ac:820a] on usb-0000:00:06.0-1.2/input0
[   10.861178] usb 4-1.3: new full-speed USB device number 5 using ohci-pci
[   10.972182] usb 4-1.3: New USB device found, idVendor=05ac, idProduct=820b
[   10.972187] usb 4-1.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[   10.982514] input: HID 05ac:820b as /devices/pci0000:00/0000:00:06.0/usb4/4-1/4-1.3/4-1.3:1.0/input/input7
[   10.982589] hid-generic 0003:05AC:820B.0006: input,hidraw4: USB HID v1.11 Mouse [HID 05ac:820b] on usb-0000:00:06.0-1.3/input0
[   11.867826] random: nonblocking pool is initialized
[   16.829248] ISO 9660 Extensions: Microsoft Joliet Level 3
[   16.832917] ISO 9660 Extensions: RRIP_1991A
[   19.402642] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[   95.404256] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   98.480471] systemd-udevd[1054]: starting version 204
[  107.782107] lp: driver loaded but no devices found
[  108.557147] ppdev: user-space parallel port driver
[  111.968587] init: cups main process (1100) killed by HUP signal
[  111.968600] init: cups main process ended, respawning
[  111.975115] Bluetooth: Core ver 2.17
[  111.975128] NET: Registered protocol family 31
[  111.975129] Bluetooth: HCI device and connection manager initialized
[  111.975137] Bluetooth: HCI socket layer initialized
[  111.975139] Bluetooth: L2CAP socket layer initialized
[  111.975142] Bluetooth: SCO socket layer initialized
[  113.413518] Bluetooth: RFCOMM TTY layer initialized
[  113.413530] Bluetooth: RFCOMM socket layer initialized
[  113.413534] Bluetooth: RFCOMM ver 1.11
[  113.875800] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[  113.875803] Bluetooth: BNEP filters: protocol multicast
[  113.875812] Bluetooth: BNEP socket layer initialized
[  114.143675] i2c i2c-7: nForce2 SMBus adapter at 0x2140
[  114.143719] i2c i2c-8: nForce2 SMBus adapter at 0x2100
[  119.341861] device-mapper: multipath: version 1.6.0 loaded
[  122.364816] ACPI: PCI Interrupt Link [LAZA] enabled at IRQ 22
[  122.364826] hda_intel: Disabling MSI
[  122.364850] hda-intel 0000:00:08.0: Disabling 64bit DMA
[  122.369265] hda-intel 0000:00:08.0: Enable delay in RIRB handling
[  122.537244] cfg80211: Calling CRDA to update world regulatory domain
[  122.548169] input: Apple Computer, Inc. IR Receiver as /devices/pci0000:00/0000:00:04.0/usb3/3-5/3-5:1.0/input/input8
[  122.548267] appleir 0003:05AC:8242.0001: input,hiddev0,hidraw5: USB HID v1.11 Device [Apple Computer, Inc. IR Receiver] on usb-0000:00:04.0-5/input0
[  123.624345] usbcore: registered new interface driver btusb
[  123.641112] usb 4-1.2: USB disconnect, device number 4
[  123.788302] hda_codec: ALC889A: SKU not ready 0x400000f0
[  123.800111] usb 4-1.3: USB disconnect, device number 5
[  123.844020] autoconfig: line_outs=2 (0x1a/0x18/0x0/0x0/0x0) type:speaker
[  123.844023]    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[  123.844025]    hp_outs=1 (0x14/0x0/0x0/0x0/0x0)
[  123.844026]    mono: mono_out=0x0
[  123.844027]    dig-out=0x1e/0x0
[  123.844028]    inputs:
[  123.844029]      Mic=0x19
[  123.844030]      Line=0x15
[  123.844031]    dig-in=0x1f
[  123.844033] realtek: No valid SSID, checking pincfg 0x400000f0 for NID 0x1d
[  123.844034] realtek: Enable default setup for auto mode as fallback
[  124.645737] Linux video capture interface: v2.00
[  125.527345] init: failsafe main process (1316) killed by TERM signal
[  125.579476] input: HDA NVidia Headphone as /devices/pci0000:00/0000:00:08.0/sound/card0/input10
[  125.582542] input: HDA NVidia Line as /devices/pci0000:00/0000:00:08.0/sound/card0/input9
[  125.635895] ACPI: PCI Interrupt Link [Z004] enabled at IRQ 21
[  125.635914] hda-intel 0000:02:00.1: Handle VGA-switcheroo audio client
[  125.635915] hda-intel 0000:02:00.1: Using LPIB position fix
[  125.635959] snd_hda_intel 0000:02:00.1: irq 46 for MSI/MSI-X
[  125.649835] hda-intel 0000:02:00.1: Enable sync_write for stable communication
[  125.685886] applesmc: key=241 fan=3 temp=15 index=15 acc=0 lux=2 kbd=0
[  126.589401] HDMI ATI/AMD: no speaker allocation for ELD
[  126.589455] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:0c.0/0000:02:00.1/sound/card1/input11
[  127.755350] cfg80211: World regulatory domain updated:
[  127.755354] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[  127.755356] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[  127.755358] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[  127.755359] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[  127.755361] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[  127.755362] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[  127.908347] uvcvideo: Found UVC 1.00 device Built-in iSight (05ac:8502)
[  127.913856] input: Built-in iSight as /devices/pci0000:00/0000:00:04.1/usb1/1-4/1-4:1.0/input/input12
[  127.913952] usbcore: registered new interface driver uvcvideo
[  127.913953] USB Video Class driver (1.1.1)
[  129.566189] b43-phy0: Broadcom 4322 WLAN found (core revision 16)
[  129.608044] b43-phy0: Found PHY: Analog 8, Type 4 (N), Revision 4
[  129.632482] b43 ssb0:0: Direct firmware load failed with error -2
[  129.632485] b43 ssb0:0: Falling back to user helper
[  129.632529] Broadcom 43xx driver loaded [ Features: PNL ]
[  129.633372] b43 ssb0:0: Direct firmware load failed with error -2
[  129.633375] b43 ssb0:0: Falling back to user helper
[  129.634217] b43 ssb0:0: Direct firmware load failed with error -2
[  129.634220] b43 ssb0:0: Falling back to user helper
[  129.634711] b43 ssb0:0: Direct firmware load failed with error -2
[  129.634713] b43 ssb0:0: Falling back to user helper
[  129.635388] b43-phy0 ERROR: Firmware file "b43/ucode16_mimo.fw" not found
[  129.635391] b43-phy0 ERROR: Firmware file "b43-open/ucode16_mimo.fw" not found
[  129.635393] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
[  153.454844] init: alsa-restore main process (1570) terminated with status 99
[  159.859881] forcedeth 0000:00:0a.0: irq 47 for MSI/MSI-X
[  159.859908] forcedeth 0000:00:0a.0 eth0: MSI enabled
[  180.483909] init: plymouth-upstart-bridge main process ended, respawning
[  180.498245] init: plymouth-upstart-bridge main process ended, respawning
[  862.456063] usb 1-3: new high-speed USB device number 4 using ehci-pci
[  862.591595] usb 1-3: New USB device found, idVendor=1bcf, idProduct=0c31
[  862.591601] usb 1-3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[  862.591604] usb 1-3: Product: USB to Serial-ATA bridge
[  862.591608] usb 1-3: Manufacturer: Sunplus Innovation Technology.
[  862.591611] usb 1-3: SerialNumber: FAFFFFF0FDF13FF1BF901305
[  864.683460] usb-storage 1-3:1.0: USB Mass Storage device detected
[  864.683638] scsi6 : usb-storage 1-3:1.0
[  864.683708] usbcore: registered new interface driver usb-storage
[  865.690235] scsi 6:0:0:0: Direct-Access     SAMSUNG  HD103UJ               PQ: 0 ANSI: 4
[  865.690464] sd 6:0:0:0: Attached scsi generic sg2 type 0
[  865.694619] sd 6:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[  865.700970] sd 6:0:0:0: [sdb] Write Protect is off
[  865.700973] sd 6:0:0:0: [sdb] Mode Sense: 38 00 00 00
[  865.707350] sd 6:0:0:0: [sdb] No Caching mode page found
[  865.707352] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[  865.721592] sd 6:0:0:0: [sdb] No Caching mode page found
[  865.721595] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[  865.741343]  sdb: sdb1 < > sdb2
[  865.780852] sd 6:0:0:0: [sdb] No Caching mode page found
[  865.780855] sd 6:0:0:0: [sdb] Assuming drive cache: write through
[  865.780857] sd 6:0:0:0: [sdb] Attached SCSI disk
[  869.594066] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
[  869.609228] XFS (sdb2): Mounting Filesystem
[  869.687220] XFS (sdb2): Internal error xlog_clear_stale_blocks(2) at line 1368 of file /build/buildd/linux-3.13.0/fs/xfs/xfs_log_recover.c.  Caller 0xffffffffa07a8951
[  869.687226] CPU: 1 PID: 5635 Comm: mount Not tainted 3.13.0-32-generic #57-Ubuntu
[  869.687227] Hardware name: Apple Inc. iMac9,1/Mac-F2218FA9, BIOS     IM91.88Z.008D.B08.0904271717 04/27/09
[  869.687229]  00000000000045e1 ffff88021f8f5c38 ffffffff8171bcb4 ffff88020c7c7400
[  869.687232]  ffff88021f8f5c50 ffffffffa075753b ffffffffa07a8951 ffff88021f8f5c90
[  869.687234]  ffffffffa07a5cf3 ffffffffa07a538f ffff88020c7c7400 ffff880219400780
[  869.687236] Call Trace:
[  869.687243]  [<ffffffff8171bcb4>] dump_stack+0x45/0x56
[  869.687269]  [<ffffffffa075753b>] xfs_error_report+0x3b/0x40 [xfs]
[  869.687287]  [<ffffffffa07a8951>] ? xlog_find_tail+0x341/0x3d0 [xfs]
[  869.687302]  [<ffffffffa07a5cf3>] xlog_clear_stale_blocks+0x183/0x1c0 [xfs]
[  869.687318]  [<ffffffffa07a538f>] ? xlog_bread+0x3f/0x50 [xfs]
[  869.687334]  [<ffffffffa07a8951>] xlog_find_tail+0x341/0x3d0 [xfs]
[  869.687350]  [<ffffffffa07aa2be>] xlog_recover+0x1e/0xc0 [xfs]
[  869.687367]  [<ffffffffa07ae8ac>] xfs_log_mount+0x1bc/0x260 [xfs]
[  869.687380]  [<ffffffffa0766cca>] xfs_mountfs+0x3aa/0x700 [xfs]
[  869.687392]  [<ffffffffa076a142>] xfs_fs_fill_super+0x2b2/0x330 [xfs]
[  869.687396]  [<ffffffff811c0030>] mount_bdev+0x1b0/0x1f0
[  869.687409]  [<ffffffffa0769e90>] ? xfs_parseargs+0xbd0/0xbd0 [xfs]
[  869.687422]  [<ffffffffa0768185>] xfs_fs_mount+0x15/0x20 [xfs]
[  869.687425]  [<ffffffff811c0a29>] mount_fs+0x39/0x1b0
[  869.687428]  [<ffffffff8116f260>] ? __alloc_percpu+0x10/0x20
[  869.687431]  [<ffffffff811dbcd7>] vfs_kern_mount+0x67/0x110
[  869.687433]  [<ffffffff811de4ee>] do_mount+0x23e/0xad0
[  869.687435]  [<ffffffff8116a28b>] ? strndup_user+0x4b/0xf0
[  869.687437]  [<ffffffff811df073>] SyS_mount+0x83/0xc0
[  869.687440]  [<ffffffff8172c87f>] tracesys+0xe1/0xe6
[  869.687442] XFS (sdb2): failed to locate log tail
[  869.687444] XFS (sdb2): log mount/recovery failed: error 117
[  869.687486] XFS (sdb2): log mount failed
[ 1404.460745] sd 6:0:0:0: [sdb] Unhandled sense code
[ 1404.460751] sd 6:0:0:0: [sdb] 
[ 1404.460753] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1404.460756] sd 6:0:0:0: [sdb] 
[ 1404.460758] Sense Key : Medium Error [current]
[ 1404.460763] sd 6:0:0:0: [sdb] 
[ 1404.460766] Add. Sense: Unrecovered read error
[ 1404.460769] sd 6:0:0:0: [sdb] CDB:
[ 1404.460771] Read(10): 28 00 07 63 bf 8d 00 00 eb 00
[ 1404.460781] end_request: critical medium error, dev sdb, sector 123977613
[ 1489.507727] sd 6:0:0:0: [sdb] Unhandled sense code
[ 1489.507734] sd 6:0:0:0: [sdb] 
[ 1489.507736] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 1489.507739] sd 6:0:0:0: [sdb] 
[ 1489.507741] Sense Key : Medium Error [current]
[ 1489.507746] sd 6:0:0:0: [sdb] 
[ 1489.507749] Add. Sense: Unrecovered read error
[ 1489.507752] sd 6:0:0:0: [sdb] CDB:
[ 1489.507754] Read(10): 28 00 07 63 bf 8d 00 00 eb 00
[ 1489.507769] end_request: critical medium error, dev sdb, sector 123977613
root@ubuntu:~#


>
> "Input/Output Error" . Run the "dmesg" command immediately after
> this error, and see what it reports last (end of command output).
>
>        >      > This asks you to post the contents of /proc/partitions, which is
>        >      > what the kernel thinks are the partition sizes.
>        >
>        > How do I do this?
>
> cat /proc/partitions
 
root@ubuntu:~# cat /proc/partitions
major minor  #blocks  name

   7        0     961232 loop0
   8        0  625131864 sda
   8        1     204800 sda1
   8        2  515624992 sda2
   8        3     634772 sda3
   8        4  108666880 sda4
  11        0    1004544 sr0
   8       16  976762584 sdb
   8       17          1 sdb1
   8       18  975755970 sdb2
root@ubuntu:~#

Hi Emmanuel, so that should be what you asked for? I did a reset in terminal and tried the dmesg, so I hope this didn't wipe any data on the failed mount which I had completed before. I'm about to try mouning as read only - fingers crossed!
Cheers,
Tom

>
>        >      >    > Yes it's a NAS drive and so I assume had some kind of proprietary
>        >      >    > OS on the other partitions (this is where i might have messed up
>        >      >    > by deleting?!) I'm pretty sure that the drive in bold below (sdc2)
>        >      >    > is the one I'm after which is xfs...
>        >      >
>        >      > Ummm, exactly what are you trying to do with this drive/filesystem?
>        >      > What device did the drive come from in the first place?
>        >
>        > It's a lacie 'Neil poulton' network space1 1tb NAS drive (see first
>        > paragraph of post) - it recently stopped working and was stuck in a
>        > 'spin cycle' - it contains my music and video backups. I'm trying to
>        > recover the files...
>
> Most probably disk is badly damaged, dead or dying. It's advisable to
> try to create an image of the disk on another one, and work for this
> image, because this disk will probably die any time now. It's no use
> trying to repair a filesystem on a bad drive, which is the cause of the
> errors from the beginning.
>
> If all you care is to get your files back, just try to mount the volume
> in read-only, non-recovery mode :
>
> mount -o ro,norecovery /dev/sdc2 /tmp/mount
>
> Then proceed by copying whatever you can get. Consider that any file
> that gives an error is lost.
>
> The other option is Kroll Ontrack or similar services, of course.
>
> -- 
> ------------------------------------------------------------------------
> Emmanuel Florac | Direction technique
> | Intellique
> |      <eflorac@intellique.com        >
> | +33 1 78 94 84 02
> ------------------------------------------------------------------------

[-- Attachment #1.2.1: Type: text/html, Size: 57085 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: Mount: Structure needs cleaning

[Dave Chinner]

On Mon, Oct 13, 2014 at 08:33:57PM +0000, Tom Mason wrote:
> 
> 
> On Oct 13, 2014, at 11:19 AM, Emmanuel Florac <eflorac@intellique.com> wrote:
> 
> >Le Mon, 13 Oct 2014 11:05:49 +0100
> >Tom Mason <tom_mason@me.com    > écrivait:
> >
> >       >      > Which means the filesystem tried to read the offset at 62GB and the
> >       >      > underlying device failed it with EIO. That's not an XFS failure.
> >       >      > What error is there in dmesg when you run that xfs_repair command?
> >       >
> >       > What's EIO?
> >       > 'Error in dmesg' How would I report this info to you?
....
> [  862.456063] usb 1-3: new high-speed USB device number 4 using ehci-pci
> [  862.591595] usb 1-3: New USB device found, idVendor=1bcf, idProduct=0c31
> [  862.591601] usb 1-3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
> [  862.591604] usb 1-3: Product: USB to Serial-ATA bridge
> [  862.591608] usb 1-3: Manufacturer: Sunplus Innovation Technology.
> [  862.591611] usb 1-3: SerialNumber: FAFFFFF0FDF13FF1BF901305
> [  864.683460] usb-storage 1-3:1.0: USB Mass Storage device detected
> [  864.683638] scsi6 : usb-storage 1-3:1.0
> [  864.683708] usbcore: registered new interface driver usb-storage
> [  865.690235] scsi 6:0:0:0: Direct-Access     SAMSUNG  HD103UJ               PQ: 0 ANSI: 4
> [  865.690464] sd 6:0:0:0: Attached scsi generic sg2 type 0
> [  865.694619] sd 6:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
> [  865.700970] sd 6:0:0:0: [sdb] Write Protect is off
> [  865.700973] sd 6:0:0:0: [sdb] Mode Sense: 38 00 00 00
> [  865.707350] sd 6:0:0:0: [sdb] No Caching mode page found
> [  865.707352] sd 6:0:0:0: [sdb] Assuming drive cache: write through
> [  865.721592] sd 6:0:0:0: [sdb] No Caching mode page found
> [  865.721595] sd 6:0:0:0: [sdb] Assuming drive cache: write through
> [  865.741343]  sdb: sdb1 < > sdb2
> [  865.780852] sd 6:0:0:0: [sdb] No Caching mode page found
> [  865.780855] sd 6:0:0:0: [sdb] Assuming drive cache: write through
> [  865.780857] sd 6:0:0:0: [sdb] Attached SCSI disk

Device plugged in....

> [  869.594066] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
> [  869.609228] XFS (sdb2): Mounting Filesystem
> [  869.687220] XFS (sdb2): Internal error xlog_clear_stale_blocks(2) at line 1368 of file /build/buildd/linux-3.13.0/fs/xfs/xfs_log_recover.c.  Caller 0xffffffffa07a8951
.....
> [  869.687442] XFS (sdb2): failed to locate log tail
> [  869.687444] XFS (sdb2): log mount/recovery failed: error 117
> [  869.687486] XFS (sdb2): log mount failed

And that is XFS telling us that the log is corrupt and can't be
recovered.

> [ 1404.460745] sd 6:0:0:0: [sdb] Unhandled sense code
> [ 1404.460751] sd 6:0:0:0: [sdb] [ 1404.460753] Result:
> hostbyte=DID_OK driverbyte=DRIVER_SENSE
> [ 1404.460756] sd 6:0:0:0: [sdb] [ 1404.460758] Sense Key : Medium
> Error [current]
> [ 1404.460763] sd 6:0:0:0: [sdb] [ 1404.460766] Add. Sense:
> Unrecovered read error
> [ 1404.460769] sd 6:0:0:0: [sdb] CDB:
> [ 1404.460771] Read(10): 28 00 07 63 bf 8d 00 00 eb 00
> [ 1404.460781] end_request: critical medium error, dev sdb, sector 123977613
> [ 1489.507727] sd 6:0:0:0: [sdb] Unhandled sense code
> [ 1489.507734] sd 6:0:0:0: [sdb] [ 1489.507736] Result:
> hostbyte=DID_OK driverbyte=DRIVER_SENSE
> [ 1489.507739] sd 6:0:0:0: [sdb] [ 1489.507741] Sense Key : Medium
> Error [current]
> [ 1489.507746] sd 6:0:0:0: [sdb] [ 1489.507749] Add. Sense:
> Unrecovered read error
> [ 1489.507752] sd 6:0:0:0: [sdb] CDB:
> [ 1489.507754] Read(10): 28 00 07 63 bf 8d 00 00 eb 00
> [ 1489.507769] end_request: critical medium error, dev sdb, sector 123977613

And that is when you ran xfs_repair 10 minutes later? THose are IO
errors, and the "Unrecovered read error" and "critical medium error"
messages indicate that the drive has lost the data in those sectors
permanently. i.e. the disk has physically failed and it needs to be
replaced. As Emmanuel has already mentioned, the best you can
probably do at this point mount the filesystem "-o ro,norecover" and
copy everything you can off onto a new drive....

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: Mount: Structure needs cleaning

[Tom Mason]

> On 13 Oct 2014, at 23:09, Dave Chinner <david@fromorbit.com> wrote:
> 
>> On Mon, Oct 13, 2014 at 08:33:57PM +0000, Tom Mason wrote:
>> 
>> 
>>> On Oct 13, 2014, at 11:19 AM, Emmanuel Florac <eflorac@intellique.com> wrote:
>>> 
>>> Le Mon, 13 Oct 2014 11:05:49 +0100
>>> Tom Mason <tom_mason@me.com    > écrivait:
>>> 
>>>>> Which means the filesystem tried to read the offset at 62GB and the
>>>>> underlying device failed it with EIO. That's not an XFS failure.
>>>>> What error is there in dmesg when you run that xfs_repair command?
>>>> 
>>>> What's EIO?
>>>> 'Error in dmesg' How would I report this info to you?
> ....
>> [  862.456063] usb 1-3: new high-speed USB device number 4 using ehci-pci
>> [  862.591595] usb 1-3: New USB device found, idVendor=1bcf, idProduct=0c31
>> [  862.591601] usb 1-3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
>> [  862.591604] usb 1-3: Product: USB to Serial-ATA bridge
>> [  862.591608] usb 1-3: Manufacturer: Sunplus Innovation Technology.
>> [  862.591611] usb 1-3: SerialNumber: FAFFFFF0FDF13FF1BF901305
>> [  864.683460] usb-storage 1-3:1.0: USB Mass Storage device detected
>> [  864.683638] scsi6 : usb-storage 1-3:1.0
>> [  864.683708] usbcore: registered new interface driver usb-storage
>> [  865.690235] scsi 6:0:0:0: Direct-Access     SAMSUNG  HD103UJ               PQ: 0 ANSI: 4
>> [  865.690464] sd 6:0:0:0: Attached scsi generic sg2 type 0
>> [  865.694619] sd 6:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
>> [  865.700970] sd 6:0:0:0: [sdb] Write Protect is off
>> [  865.700973] sd 6:0:0:0: [sdb] Mode Sense: 38 00 00 00
>> [  865.707350] sd 6:0:0:0: [sdb] No Caching mode page found
>> [  865.707352] sd 6:0:0:0: [sdb] Assuming drive cache: write through
>> [  865.721592] sd 6:0:0:0: [sdb] No Caching mode page found
>> [  865.721595] sd 6:0:0:0: [sdb] Assuming drive cache: write through
>> [  865.741343]  sdb: sdb1 < > sdb2
>> [  865.780852] sd 6:0:0:0: [sdb] No Caching mode page found
>> [  865.780855] sd 6:0:0:0: [sdb] Assuming drive cache: write through
>> [  865.780857] sd 6:0:0:0: [sdb] Attached SCSI disk
> 
> Device plugged in....
> 
>> [  869.594066] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
>> [  869.609228] XFS (sdb2): Mounting Filesystem
>> [  869.687220] XFS (sdb2): Internal error xlog_clear_stale_blocks(2) at line 1368 of file /build/buildd/linux-3.13.0/fs/xfs/xfs_log_recover.c.  Caller 0xffffffffa07a8951
> .....
>> [  869.687442] XFS (sdb2): failed to locate log tail
>> [  869.687444] XFS (sdb2): log mount/recovery failed: error 117
>> [  869.687486] XFS (sdb2): log mount failed
> 
> And that is XFS telling us that the log is corrupt and can't be
> recovered.
> 
>> [ 1404.460745] sd 6:0:0:0: [sdb] Unhandled sense code
>> [ 1404.460751] sd 6:0:0:0: [sdb] [ 1404.460753] Result:
>> hostbyte=DID_OK driverbyte=DRIVER_SENSE
>> [ 1404.460756] sd 6:0:0:0: [sdb] [ 1404.460758] Sense Key : Medium
>> Error [current]
>> [ 1404.460763] sd 6:0:0:0: [sdb] [ 1404.460766] Add. Sense:
>> Unrecovered read error
>> [ 1404.460769] sd 6:0:0:0: [sdb] CDB:
>> [ 1404.460771] Read(10): 28 00 07 63 bf 8d 00 00 eb 00
>> [ 1404.460781] end_request: critical medium error, dev sdb, sector 123977613
>> [ 1489.507727] sd 6:0:0:0: [sdb] Unhandled sense code
>> [ 1489.507734] sd 6:0:0:0: [sdb] [ 1489.507736] Result:
>> hostbyte=DID_OK driverbyte=DRIVER_SENSE
>> [ 1489.507739] sd 6:0:0:0: [sdb] [ 1489.507741] Sense Key : Medium
>> Error [current]
>> [ 1489.507746] sd 6:0:0:0: [sdb] [ 1489.507749] Add. Sense:
>> Unrecovered read error
>> [ 1489.507752] sd 6:0:0:0: [sdb] CDB:
>> [ 1489.507754] Read(10): 28 00 07 63 bf 8d 00 00 eb 00
>> [ 1489.507769] end_request: critical medium error, dev sdb, sector 123977613
> 
> And that is when you ran xfs_repair 10 minutes later? THose are IO
> errors, and the "Unrecovered read error" and "critical medium error"
> messages indicate that the drive has lost the data in those sectors
> permanently. i.e. the disk has physically failed and it needs to be
> replaced. As Emmanuel has already mentioned, the best you can
> probably do at this point mount the filesystem "-o ro,norecover" and
> copy everything you can off onto a new drive....
> 
> Cheers,
> 
> Dave

Thanks guys - much appreciated, managed to mount the drive again and have saved some more files although I have lost a lot : ( 

Noob question: Could this have occurred due to me copying too many differing folders all 100gb+ when I first mounted the drive successfully in knoppix? Or was this drive just going to go anyway? 

Cheers!
Tom
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: Mount: Structure needs cleaning

[Tom Mason]

> On 13 Oct 2014, at 23:09, Dave Chinner <david@fromorbit.com> wrote:
> 
>> On Mon, Oct 13, 2014 at 08:33:57PM +0000, Tom Mason wrote:
>> 
>> 
>>> On Oct 13, 2014, at 11:19 AM, Emmanuel Florac <eflorac@intellique.com> wrote:
>>> 
>>> Le Mon, 13 Oct 2014 11:05:49 +0100
>>> Tom Mason <tom_mason@me.com    > écrivait:
>>> 
>>>>> Which means the filesystem tried to read the offset at 62GB and the
>>>>> underlying device failed it with EIO. That's not an XFS failure.
>>>>> What error is there in dmesg when you run that xfs_repair command?
>>>> 
>>>> What's EIO?
>>>> 'Error in dmesg' How would I report this info to you?
> ....
>> [  862.456063] usb 1-3: new high-speed USB device number 4 using ehci-pci
>> [  862.591595] usb 1-3: New USB device found, idVendor=1bcf, idProduct=0c31
>> [  862.591601] usb 1-3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
>> [  862.591604] usb 1-3: Product: USB to Serial-ATA bridge
>> [  862.591608] usb 1-3: Manufacturer: Sunplus Innovation Technology.
>> [  862.591611] usb 1-3: SerialNumber: FAFFFFF0FDF13FF1BF901305
>> [  864.683460] usb-storage 1-3:1.0: USB Mass Storage device detected
>> [  864.683638] scsi6 : usb-storage 1-3:1.0
>> [  864.683708] usbcore: registered new interface driver usb-storage
>> [  865.690235] scsi 6:0:0:0: Direct-Access     SAMSUNG  HD103UJ               PQ: 0 ANSI: 4
>> [  865.690464] sd 6:0:0:0: Attached scsi generic sg2 type 0
>> [  865.694619] sd 6:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
>> [  865.700970] sd 6:0:0:0: [sdb] Write Protect is off
>> [  865.700973] sd 6:0:0:0: [sdb] Mode Sense: 38 00 00 00
>> [  865.707350] sd 6:0:0:0: [sdb] No Caching mode page found
>> [  865.707352] sd 6:0:0:0: [sdb] Assuming drive cache: write through
>> [  865.721592] sd 6:0:0:0: [sdb] No Caching mode page found
>> [  865.721595] sd 6:0:0:0: [sdb] Assuming drive cache: write through
>> [  865.741343]  sdb: sdb1 < > sdb2
>> [  865.780852] sd 6:0:0:0: [sdb] No Caching mode page found
>> [  865.780855] sd 6:0:0:0: [sdb] Assuming drive cache: write through
>> [  865.780857] sd 6:0:0:0: [sdb] Attached SCSI disk
> 
> Device plugged in....
> 
>> [  869.594066] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
>> [  869.609228] XFS (sdb2): Mounting Filesystem
>> [  869.687220] XFS (sdb2): Internal error xlog_clear_stale_blocks(2) at line 1368 of file /build/buildd/linux-3.13.0/fs/xfs/xfs_log_recover.c.  Caller 0xffffffffa07a8951
> .....
>> [  869.687442] XFS (sdb2): failed to locate log tail
>> [  869.687444] XFS (sdb2): log mount/recovery failed: error 117
>> [  869.687486] XFS (sdb2): log mount failed
> 
> And that is XFS telling us that the log is corrupt and can't be
> recovered.
> 
>> [ 1404.460745] sd 6:0:0:0: [sdb] Unhandled sense code
>> [ 1404.460751] sd 6:0:0:0: [sdb] [ 1404.460753] Result:
>> hostbyte=DID_OK driverbyte=DRIVER_SENSE
>> [ 1404.460756] sd 6:0:0:0: [sdb] [ 1404.460758] Sense Key : Medium
>> Error [current]
>> [ 1404.460763] sd 6:0:0:0: [sdb] [ 1404.460766] Add. Sense:
>> Unrecovered read error
>> [ 1404.460769] sd 6:0:0:0: [sdb] CDB:
>> [ 1404.460771] Read(10): 28 00 07 63 bf 8d 00 00 eb 00
>> [ 1404.460781] end_request: critical medium error, dev sdb, sector 123977613
>> [ 1489.507727] sd 6:0:0:0: [sdb] Unhandled sense code
>> [ 1489.507734] sd 6:0:0:0: [sdb] [ 1489.507736] Result:
>> hostbyte=DID_OK driverbyte=DRIVER_SENSE
>> [ 1489.507739] sd 6:0:0:0: [sdb] [ 1489.507741] Sense Key : Medium
>> Error [current]
>> [ 1489.507746] sd 6:0:0:0: [sdb] [ 1489.507749] Add. Sense:
>> Unrecovered read error
>> [ 1489.507752] sd 6:0:0:0: [sdb] CDB:
>> [ 1489.507754] Read(10): 28 00 07 63 bf 8d 00 00 eb 00
>> [ 1489.507769] end_request: critical medium error, dev sdb, sector 123977613
> 
> And that is when you ran xfs_repair 10 minutes later? THose are IO
> errors, and the "Unrecovered read error" and "critical medium error"
> messages indicate that the drive has lost the data in those sectors
> permanently. i.e. the disk has physically failed and it needs to be
> replaced. As Emmanuel has already mentioned, the best you can
> probably do at this point mount the filesystem "-o ro,norecover" and
> copy everything you can off onto a new drive....
> 
> Cheers,
> 
> Dave.
> -- 
> Dave Chinner
> david@fromorbit.com
Btw - before I get rid of this old samsung 1tb drive, the folder's properties in the failed drive actually report a lot higher for file numbers and sizes than eventually get copied - it reports:
"Error while copying
There was an error getting information about the files in the folder 'xxxxx' no data available"
...is there a way around this or is this my lost data?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: Mount: Structure needs cleaning

[Dave Chinner]

On Mon, Oct 13, 2014 at 11:25:47PM +0100, Tom Mason wrote:
> Noob question: Could this have occurred due to me copying too many
> differing folders all 100gb+ when I first mounted the drive
> successfully in knoppix? Or was this drive just going to go
> anyway? 

The drive is dying - it's not related to anything you did.

-Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: Mount: Structure needs cleaning

[Dave Chinner]

On Mon, Oct 13, 2014 at 11:38:34PM +0100, Tom Mason wrote:
> Btw - before I get rid of this old samsung 1tb drive, the folder's
> properties in the failed drive actually report a lot higher for
> file numbers and sizes than eventually get copied - it reports:
> "Error while copying There was an error getting information about
> the files in the folder 'xxxxx' no data available" ...is there a
> way around this or is this my lost data?

You're now into disaster recovery territory. Use ddrescue to image
the filesystem, then something like photorec or some other data
recovery tool to scrape the image for intact files that otherwise
couldn't be pulled from the mounted filesystem.

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: Mount: Structure needs cleaning

[Emmanuel Florac]

Le Mon, 13 Oct 2014 23:38:34 +0100
Tom Mason <tom_mason@me.com> écrivait:

> Btw - before I get rid of this old samsung 1tb drive, the folder's
> properties in the failed drive actually report a lot higher for file
> numbers and sizes than eventually get copied - it reports: "Error
> while copying There was an error getting information about the files
> in the folder 'xxxxx' no data available" ...is there a way around
> this or is this my lost data?

The metadata information from the drive may be inaccurate because the
log is corrupted. Then some folder data may have been lost and prevent
you from recovering the files that are in some folders.

After you're done copying all files you can from the disk, you can try
to make a mirror image on another drive at least as big as this one,
and run xfs_repair on the image. After that you could eventually get
more data back (it depends upon the extent of the damage to the actual
data and file structure).

To copy the disk on another one, you can use ddrescue or dd with
"noerror" option.

-- 
------------------------------------------------------------------------
Emmanuel Florac     |   Direction technique
                    |   Intellique
                    |	<eflorac@intellique.com>
                    |   +33 1 78 94 84 02
------------------------------------------------------------------------

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: Mount: Structure needs cleaning

[Tom Mason]

> On 14 Oct 2014, at 11:55, Emmanuel Florac <eflorac@intellique.com> wrote:
> 
> Le Mon, 13 Oct 2014 23:38:34 +0100
> Tom Mason <tom_mason@me.com> écrivait:
> 
>> Btw - before I get rid of this old samsung 1tb drive, the folder's
>> properties in the failed drive actually report a lot higher for file
>> numbers and sizes than eventually get copied - it reports: "Error
>> while copying There was an error getting information about the files
>> in the folder 'xxxxx' no data available" ...is there a way around
>> this or is this my lost data?
> 
> The metadata information from the drive may be inaccurate because the
> log is corrupted. Then some folder data may have been lost and prevent
> you from recovering the files that are in some folders.
> 
> After you're done copying all files you can from the disk, you can try
> to make a mirror image on another drive at least as big as this one,
> and run xfs_repair on the image. After that you could eventually get
> more data back (it depends upon the extent of the damage to the actual
> data and file structure).
> 
> To copy the disk on another one, you can use ddrescue or dd with
> "noerror" option.
> -----------------------------------------
Thanks again!
Can I create an image on a new NAS drive such as a seagate 3tb 'Central network attached storage NAS' STCG3000200 without interfering with its capabilities as a NAS drive?
Tom
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: Mount: Structure needs cleaning

[Emmanuel Florac]

Le Tue, 14 Oct 2014 16:46:39 +0100
Tom Mason <tom_mason@me.com> écrivait:

> > To copy the disk on another one, you can use ddrescue or dd with
> > "noerror" option.
> > -----------------------------------------  
> Thanks again!
> Can I create an image on a new NAS drive such as a seagate 3tb
> 'Central network attached storage NAS' STCG3000200 without
> interfering with its capabilities as a NAS drive?

Yes of course, simply make a file image on the shared volume :


dd if=/dev/sdb2 noerror of=/mountpoint/mynas/disk1TB.img 

Then you can run xfs_repair on the image file:

xfs_repair -f /mountpoint/mynas/disk1TB.img

Or run photorec on it 

photorec /mountpoint/mynas/disk1TB.img


-- 
------------------------------------------------------------------------
Emmanuel Florac     |   Direction technique
                    |   Intellique
                    |	<eflorac@intellique.com>
                    |   +33 1 78 94 84 02
------------------------------------------------------------------------

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: Mount: Structure needs cleaning

[Tom Mason]

> On 14 Oct 2014, at 17:38, Emmanuel Florac <eflorac@intellique.com> wrote:
> 
> Le Tue, 14 Oct 2014 16:46:39 +0100
> Tom Mason <tom_mason@me.com> écrivait:
> 
>>> To copy the disk on another one, you can use ddrescue or dd with
>>> "noerror" option.
>>> -----------------------------------------  
>> Thanks again!
>> Can I create an image on a new NAS drive such as a seagate 3tb
>> 'Central network attached storage NAS' STCG3000200 without
>> interfering with its capabilities as a NAS drive?
> 
> Yes of course, simply make a file image on the shared volume :
> 
> 
> dd if=/dev/sdb2 noerror of=/mountpoint/mynas/disk1TB.img
> 
> Then you can run xfs_repair on the image file:
> 
> xfs_repair -f /mountpoint/mynas/disk1TB.img
> 
> Or run photorec on it 
> 
> photorec /mountpoint/mynas/disk1TB.img
> 
> 
Thanks Emmanuel! Much appreciated : ) I'll order a new NAS and might have some more questions when I get to work on it if thats ok?
Thanks again for all the help Dave/Brian/Emmanuel!
Tom
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: Mount: Structure needs cleaning

[Tom Mason]

> On 14 Oct 2014, at 17:38, Emmanuel Florac <eflorac@intellique.com> wrote:
> 
> Le Tue, 14 Oct 2014 16:46:39 +0100
> Tom Mason <tom_mason@me.com> écrivait:
> 
>>> To copy the disk on another one, you can use ddrescue or dd with
>>> "noerror" option.
>>> -----------------------------------------  
>> Thanks again!
>> Can I create an image on a new NAS drive such as a seagate 3tb
>> 'Central network attached storage NAS' STCG3000200 without
>> interfering with its capabilities as a NAS drive?
> 
> Yes of course, simply make a file image on the shared volume :
> 
> 
> dd if=/dev/sdb2 noerror of=/mountpoint/mynas/disk1TB.img
> 
> Then you can run xfs_repair on the image file:
> 
> xfs_repair -f /mountpoint/mynas/disk1TB.img
> 
> Or run photorec on it 
> 
> photorec /mountpoint/mynas/disk1TB.img
Hello again!
I have a new NAS Drive connected to my network, 3tb. How would I find this through my ubuntu livecd so that I can put an image of the broken disk on it? It shows up in nautilus with several server icons (three grey boxes stacked on top of one another)
-Seagate-41DA35
-SEAGATE-41DA35
-Seagate Central shared storage (Seagate-41DA35)
-SFTP file transfer on Seagate-41DA35
Cheers!
Tom
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs