Mount: Structure needs cleaning
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
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Quoted 9 lines · 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.
Quoted 7 lines
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
Quoted 4 lines
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 &
Quoted 9 lines
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/sdc2at /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
Quoted 9 lines
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
Quoted 8 lines
--
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
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Quoted 18 lines
Date: Sun, 12 Oct 2014 10:20:08 -0400
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: Mount: Structure needs cleaningQuoted 9 lines · 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.
Quoted 8 lines
Quoted 6 lines
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
Quoted 17 lines
http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
Quoted 4 lines
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 &
Quoted 8 lines
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/sdc2at /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"
Quoted 5 lines
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
Quoted 4 lines
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
Quoted 19 lines
Brian
Quoted 17 lines
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
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
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
Quoted 24 lines
Date: Sun, 12 Oct 2014 10:20:08 -0400
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: Mount: Structure needs cleaningQuoted 9 lines · 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.
Quoted 6 lines
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...
Quoted 1 line
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
Quoted 17 lines
http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
Quoted 4 lines
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 &
Quoted 8 lines
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/sdc2at /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"
Quoted 5 lines
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
Quoted 4 lines
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
Quoted 10 lines
Brian
Quoted 8 lines
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 mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
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.
Quoted 24 lines
Date: Sun, 12 Oct 2014 10:20:08 -0400
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: Mount: Structure needs cleaningQuoted 9 lines · 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.
Quoted 6 lines
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...
Quoted 1 line
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
Quoted 17 lines
http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
Quoted 4 lines
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 &
Quoted 8 lines
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/sdc2at /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"
Quoted 5 lines
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
Quoted 4 lines
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
Quoted 10 lines
Brian
Quoted 8 lines
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 mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
[ please don't top post. ]
Quoted 32 lines · tom mason
Quoted 24 lines
Date: Sun, 12 Oct 2014 10:20:08 -0400
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: Mount: Structure needs cleaningQuoted 9 lines · 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.
Quoted 6 lines
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...
Quoted 1 line
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_64x86_64x86_64GNU/Linux
-xfs_repairversion 3.1.9
Quoted 7 lines
ok - so I worked out & tried the
xfs_repaircommand:root@ubuntu:~# xfs_repair -n /dev/sdc2 Phase 1 - find and verify superblock... superblock read failed, offset 62448377856, size 131072, ag 2, rval -1fatal 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?
Quoted 1 line
This asks you to post the contents of /proc/partitions, which is what the kernel thinks are the partition sizes.
Quoted 4 lines
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.
Signature · 7 lines
Dave Chinner [email protected] _______________________________________________ xfs mailing list [email protected] http://oss.sgi.com/mailman/listinfo/xfs
Quoted 47 lines · Dave Chinner
[ please don't top post. ]
Quoted 38 lines · tom mason
Quoted 24 lines
Date: Sun, 12 Oct 2014 10:20:08 -0400
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: Mount: Structure needs cleaningQuoted 10 lines · 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.
Quoted 6 lines
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...
Quoted 1 line
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_64x86_64x86_64GNU/Linux
-xfs_repairversion 3.1.9ok - so I worked out & tried the
xfs_repaircommand:root@ubuntu:~# xfs_repair -n /dev/sdc2 Phase 1 - find and verify superblock... superblock read failed, offset 62448377856, size 131072, ag 2, rval -1
Quoted 5 lines
Quoted 1 line
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_repaircommand?
What's EIO?
'Error in dmesg' How would I report this info to you?
Quoted 5 lines
Quoted 2 lines
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?
Quoted 8 lines
Quoted 5 lines
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
Quoted 8 lines
Cheers,
Dave.
Signature · 2 lines
Dave Chinner [email protected]
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Le Mon, 13 Oct 2014 11:05:49 +0100
Tom Mason <[email protected]> écrivait:
Quoted 6 lines
Quoted 3 lines
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_repaircommand?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).
Quoted 4 lines
Quoted 2 lines
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
Quoted 5 lines
Quoted 5 lines
Quoted 4 lines
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...
Quoted 7 lines
Quoted 2 lines
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.
Signature · 11 lines
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <[email protected]>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfsQuoted 44 lines · Emmanuel Florac
Le Mon, 13 Oct 2014 11:05:49 +0100
Tom Mason <[email protected]> écrivait:Quoted 6 lines
Quoted 3 lines
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_repaircommand?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).
Quoted 4 lines
Quoted 2 lines
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/partitionsQuoted 5 lines
Quoted 5 lines
Quoted 4 lines
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...
Quoted 7 lines
Quoted 2 lines
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 :
Quoted 8 lines
mount -o ro,norecovery
/dev/sdc2/tmp/mountThen 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
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs
Le Sun, 12 Oct 2014 22:48:36 +0000
tom mason <[email protected]> écrivait:
Quoted 3 lines
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?
Signature · 11 lines
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <[email protected]>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
[email protected]
http://oss.sgi.com/mailman/listinfo/xfs