On Fri, 08 May 2015 16:51:20 -0400 The Wanderer <wande...@fastmail.fm> wrote:
> On 05/08/2015 at 04:34 PM, German wrote: > > > On Fri, 08 May 2015 16:27:22 -0400 The Wanderer > > <wande...@fastmail.fm> wrote: > > >> What leads you to conclude that the drive is OK and the filesystem > >> is what is bad? What errors are you seeing, in what situations? > > > > Error mounting /dev/sdc1 at /media/spore/FreeAgent GoFlex Drive: > > Command-line `mount -t "ntfs" -o > > "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177" > > "/dev/sdc1" "/media/spore/FreeAgent GoFlex Drive"' exited with > > non-zero exit status 13: ntfs_attr_pread_i: ntfs_pread failed: > > Input/output error Failed to read of MFT, mft=17625 count=1 br=-1: > > Input/output error Inode is corrupt (5): Input/output error Index > > root attribute missing in directory inode 5: Input/output error > > Failed to mount '/dev/sdc1': Input/output error > > "Input/output error" in this sort of context usually means that the > drive itself is failing, not the filesystem. (Or that something else > in the connection between the system and the drive is faulty; I've > seen it happen with bad SATA/IDE cables, and for that matter with > cables which were just loose.) > > Just to confirm, this happens on any mount attempt, correct? Yes, this happens on mount attempt. I still don't think that drive is failing and I think cables are ok too. It's happened when I was installing Lubuntu. During the install, install program obviously probed all available drives, and did something nasty to the drive. > > > NTFS is either inconsistent, or there is a hardware fault, or it's a > > SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on > > Windows then reboot into Windows twice. The usage of the /f > > parameter is very important! If the device is a SoftRAID/FakeRAID > > then first activate it and mount a different device under > > the /dev/mapper/ directory, (e.g. /dev/mapper/nvidia_eahaabcc1). > > Please see the 'dmraid' documentation for more details. > > If you have a suitable Windows system with which to try the suggested > 'chkdsk /f' and double reboot-into-Windows approach, you could do > that, but I wouldn't bet on it helping - and if the drive really is > failing, then trying to access the drive that way might make things > worse. > > I think it looks as if the drive really is failing, and the "separate, > larger drive" ddrescue/dd_rescue/myrescue approach is the right way to > go after all. > > (Also note that since the filesystem is on /dev/sdc1, you'll almost > certainly want to apply your ddrescue command to source that node, not > the higher-level /dev/sdc node. You _can_ recover the data from a copy > of /dev/sdc, but it's significantly less trivial.) > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150508165812.723cb...@asterius.asterius.net
