From: tommason <tom_in_canada@hotmail.com>
To: xfs@oss.sgi.com
Subject: Mount: Structure needs cleaning
Date: Sun, 12 Oct 2014 01:43:28 -0700 (MST) [thread overview]
Message-ID: <1413103408756-35026.post@n7.nabble.com> (raw)
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
next reply other threads:[~2014-10-12 8:45 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-12 8:43 tommason [this message]
2014-10-12 14:20 ` Mount: Structure needs cleaning Brian Foster
2014-10-12 22:39 ` tom mason
2014-10-12 22:48 ` tom mason
2014-10-12 22:51 ` tom mason
2014-10-12 23:10 ` Dave Chinner
2014-10-13 10:05 ` Tom Mason
2014-10-13 10:19 ` Emmanuel Florac
2014-10-13 10:40 ` Tom Mason
2014-10-13 9:26 ` Emmanuel Florac
-- strict thread matches above, loose matches on Subject: below --
2014-10-13 20:33 Tom Mason
2014-10-13 22:09 ` Dave Chinner
2014-10-13 22:25 ` Tom Mason
2014-10-13 23:44 ` Dave Chinner
2014-10-13 22:38 ` Tom Mason
2014-10-13 23:47 ` Dave Chinner
2014-10-14 10:55 ` Emmanuel Florac
2014-10-14 15:46 ` Tom Mason
2014-10-14 16:38 ` Emmanuel Florac
2014-10-14 16:43 ` Tom Mason
2014-10-21 20:44 ` Tom Mason
2012-02-26 3:15 mount: " MikeJeezy
2012-02-26 4:35 ` Stan Hoeppner
2012-02-26 7:22 ` MikeJeezy
2012-02-26 17:07 ` Stan Hoeppner
2012-02-27 0:49 ` Dave Chinner
2012-02-27 3:11 ` MikeJeezy
2012-02-27 6:28 ` Stan Hoeppner
2012-02-27 18:32 ` MikeJeezy
2012-02-28 1:48 ` Dave Chinner
2012-02-28 9:14 ` Brian Candler
2012-02-29 3:50 ` Dave Chinner
2012-02-29 7:40 ` Brian Candler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1413103408756-35026.post@n7.nabble.com \
--to=tom_in_canada@hotmail.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox