Ntfs 3g Inode Is Corrupt Input Output Error
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack
Input/output Error Linux
Overflow the company Business Learn more about hiring developers or posting ads with us input/output error ubuntu Unix & Linux Questions Tags Users Badges Unanswered Ask Question _ Unix & Linux Stack Exchange is a question and answer site ubuntu input output error external hard drive for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted
Input Output Error External Hard Drive Linux
up and rise to the top ntfs-3g: Input/output error up vote 6 down vote favorite 4 For the past 3 days (after an update) my Debian Jessie refuses to mount NTFS disks. I reinstalled libfuse2 and ntfs-3g, yet I get the same Input/output error I tried the same disks under Windows 7 and OSX Mavericks (using ntfs-3g) and they work fine. I purged ntfs-3g and reinstalled, and still the same problem. The disks
Ntfs Is Either Inconsistent Or There Is A Hardware Fault Or It's A Softraid Fakeraid Hardware
will sometimes mount and sometimes won't mount. If they do mount, I am sometimes able to go into the mount directory, whereas some other times, I get a bash error Input/output error for the mount directory. The times I am able to go into the mount directory, when I try an ls -l, I see tons of question marks, instead of file/dir attributes. I have tried ntfsfix and chkdisk under windows, and they both reported no problems, it is only under this Jessie install that all of a sudden I can't mount them properly. dmesg has no usefull info other than the external disk being attached: [12816.210969] scsi 20:0:0:0: Direct-Access Seagate External SG16 PQ: 0 ANSI: 4 [12816.211825] sd 20:0:0:0: Attached scsi generic sg7 type 0 [12816.212542] sd 20:0:0:0: [sdg] 732566642 4096-byte logical blocks: (3.00 TB/2.72 TiB) [12816.213591] sd 20:0:0:0: [sdg] Write Protect is off [12816.213595] sd 20:0:0:0: [sdg] Mode Sense: bf 00 00 00 [12816.214782] sd 20:0:0:0: [sdg] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [12816.215561] sd 20:0:0:0: [sdg] 732566642 4096-byte logical blocks: (3.00 TB/2.72 TiB) [12816.242055] sdg: sdg1 sdg2 [12816.243244] sd 20:0:0:0: [sdg] 732566642 4096-byte logical blocks: (3.00 TB/2.72 TiB) [12816.246031] sd 20:0:0:0: [sdg] Attached SCSI disk parted /dev/sdg 'print' Model: Seagate External (scsi) Disk /dev/sdg: 3001GB Sector size (logical/physical): 4
only reason I wrote it is because it was something that happened to me now and again. But what about dual boots? What happens when your failed to read $mftmirr input/output error NTFS drive goes beserk, and you only have access to your Ubuntu install?
Ubuntu Input/output Error During Read On /dev/sda
Well, finally, I've come across a solution. Now, before we begin, this HowTo assumes that your Ubuntu install is volume is corrupt. you should run chkdsk. working as normal, and that the NTFS partition isn't essential to Ubuntu. It's also possible (though I've not yet tried) to follow this HowTo using Parted Magic. First, we need to find http://unix.stackexchange.com/questions/165057/ntfs-3g-input-output-error out what partition we are dealing with. To do this, open a terminal and type; sudo fdisk -l That'll give you something like this; Disk /dev/sdb: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: https://linuxexpresso.wordpress.com/2011/09/20/howto-fix-an-ntfs-partition-in-ubuntu/ 0x2709a320 Device Boot Start End Blocks Id System /dev/sdb1 * 1 19457 156288321 7 HPFS/NTFS /dev/sd1 is in this case the NTFS drive we'll be working with. Obviously change this to whatever yours is. If your partition isn't listed here, or appears to be the wrong size, you'll need to use TestDisk. Next, you need to install some software called "ntfsprogs". You can do this through Synaptic or on the command line using; sudo apt-get install ntfsprogs There's just one last step. sudo ntfsfix /dev/sdb1 With any luck, you should see the following; Mounting volume... OK Processing of $MFT and $MFTMirr completed successfully. NTFS volume version is 3.1. NTFS partition /dev/sdb1 was processed successfully. And that's it! Go try to mount you NTFS partition, and it should work again as normal. If not, feel free to leave a comment below. Share this:TwitterFacebookGoogleLike this:Like Loading... Related Filed under: Debian, HowTo, Operating Systems, Ubuntu |17Comments Tags: Debian, fix, HowTo, NTFS, partition, postaweek2011, Ubuntu 17 Responses to "HOWTO: Fix an NTFS partition inUbuntu" Feed for this Entry 1 Ron Bell on October 16, 2011 said: I have followed your instructions faithfully in
05:25 AMThis is bad. I think ntfs-36 is screwing up my files on my raid partition. I am getting lots http://forums.fedoraforum.org/archive/index.php/t-219006.html of errors in my log. I am posting this here, since it occured while I was testing the beta. This occurred on a RAID drive. Apr 5 18:47:36 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument Apr 5 18:47:36 LinPC ntfs-3g[1811]: Record 33556 has no FILE magic (0x0) Apr 5 18:47:36 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 output error size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument Apr 5 18:47:36 LinPC ntfs-3g[1811]: Record 34130 has no FILE magic (0x0) Apr 5 18:47:36 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument Apr 5 18:47:36 LinPC ntfs-3g[1811]: Record 39490 has no FILE magic (0x0) Apr 5 18:47:36 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 input output error usa_count: 65535: Invalid argument Apr 5 18:47:36 LinPC ntfs-3g[1811]: Record 39245 has no FILE magic (0x0) Apr 5 18:47:36 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument Apr 5 18:47:36 LinPC ntfs-3g[1811]: Record 39247 has no FILE magic (0x0) Apr 5 18:47:36 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument Apr 5 18:47:36 LinPC ntfs-3g[1811]: Record 39481 has no FILE magic (0x0) Apr 5 18:47:36 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0xd16be2be size: 4096 usa_ofs: 16261 usa_count: 9840: Invalid argument Apr 5 18:47:36 LinPC ntfs-3g[1811]: Actual VCN (0xfccfb1645c7c5118) of index buffer is different from expected VCN (0x0) in inode 0x8359. Apr 5 18:47:39 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument Apr 5 18:47:39 LinPC ntfs-3g[1811]: Record 39245 has no FILE magic (0x0) Apr 5 18:47:39 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument Apr 5 18:47:39 LinPC ntfs-3g[1811]: Record 39247 has no FILE magic (0x0) Apr 5 18:47:39 LinPC ntfs-3g[1811]: ntfs_mst_post_read_fixup: magic: 0x00000000 size: 1024 usa_ofs: 0 usa_count: 65535: Invalid argument