Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

ntfs i/o errors

New to Debian (Or Linux in general)? Ask your questions here!
Post Reply
Message
Author
nuxnoob
Posts: 12
Joined: 2021-09-19 15:25

ntfs i/o errors

#1 Post by nuxnoob »

new install sees my 2nd drive a large ntfs, but when i try to copy a large file to it i get i/o errors
and cant write superblock.
i can write a copy of the large file to dame folder just fine.
tried unmount remount doesnt work. reboot to winpe to checkdisk ususally result no errors.
whe errors happen win chkdsk usually always fixes it.

User avatar
sunrat
Administrator
Administrator
Posts: 6382
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 115 times
Been thanked: 456 times

Re: ntfs i/o errors

#2 Post by sunrat »

What is "dame folder"?
Do you dual boot with Windows? Disable "Fast Startup" in Windows. It leaves NTFS drives in a kind of hibernation state which is read-only for Linux.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

nuxnoob
Posts: 12
Joined: 2021-09-19 15:25

Re: ntfs i/o errors

#3 Post by nuxnoob »

sorry that was "same" folder.

nuxnoob
Posts: 12
Joined: 2021-09-19 15:25

Re: ntfs i/o errors

#4 Post by nuxnoob »

no mostly just using winpe to do things i cant yet do in linux

nuxnoob
Posts: 12
Joined: 2021-09-19 15:25

Re: ntfs i/o errors

#5 Post by nuxnoob »

ntfs-3g: No device is specified.

ntfs-3g 2017.3.23AR.3 integrated FUSE 28 - Third Generation NTFS Driver
Configuration type 7, XATTRS are on, POSIX ACLS are on

nuxnoob
Posts: 12
Joined: 2021-09-19 15:25

Re: ntfs i/o errors

#6 Post by nuxnoob »

i dont think my winpe uses fast startup.

nuxnoob
Posts: 12
Joined: 2021-09-19 15:25

Re: ntfs i/o errors

#7 Post by nuxnoob »

i copied a small file fine. the error was occuring when i copies a 12G mkv movie file.
i was getting error "splicing".
then knocks the superblock.

User avatar
sunrat
Administrator
Administrator
Posts: 6382
Joined: 2006-08-29 09:12
Location: Melbourne, Australia
Has thanked: 115 times
Been thanked: 456 times

Re: ntfs i/o errors

#8 Post by sunrat »

Paste the exact error please. In CODE tags.
“ computer users can be divided into 2 categories:
Those who have lost data
...and those who have not lost data YET ”
Remember to BACKUP!

nuxnoob
Posts: 12
Joined: 2021-09-19 15:25

Re: ntfs i/o errors

#9 Post by nuxnoob »

ok i tried to reproduce it , couple times now no luck.
i suppose thats good news i sort of dont believe it.
have been quite and issue for a few days.
always repaired with winpe or not needed.

only thing i think could have changed would be if the full surface scan reset that bit.
i ran a 14 hour surface scan with a windows part app.
found no errors i assumed it was a read only event.

nuxnoob
Posts: 12
Joined: 2021-09-19 15:25

Re: ntfs i/o errors

#10 Post by nuxnoob »

seriously i dont understand what repaired the problem.

also is the ntfs3g saying i'm not using it?
and is it current?
i suppose i need to add it to the fstab.

seeker5528
Posts: 61
Joined: 2021-09-18 00:37
Been thanked: 2 times

Re: ntfs i/o errors

#11 Post by seeker5528 »

It doesn't look like there is a problem with ntfs-3g.

Superblocks are the areas of the filesystem where index type information is stored about the partition, the files and the free space. So the whole file could get written correctly, but if reading or writing the filesystem index information fails the copy fails.

I don't know what kind of scan on how big of a disk this was that it took 14 hours to scan, but it could have caused a bad sector to get mapped out. How many sectors have to get mapped out for the drive to start reporting it's self as failing seems to vary from drive to drive.

If you have GSmartControl installed you can use that to look at the SMART data. Or us the smartctl command in a terminal.

Code: Select all

smartctl --attributes /dev/sdX
I don't like seeing that any sectors have been mapped out, but I did have one hard drive that had 8 sectors that had been mapped out and lasted for another 3 or 4 years, before it got worse.

If there are a lot of pending sectors, that is a bad sign.

The Windows disk checking utilities are not that good at detecting/fixing some types of low level filesystem errors, so there is a possibility that some combination of things happened that corrected it or disk contents changed enough that the problem spot in the superblock did not have to be read or written to when the file copy succeded.

nuxnoob
Posts: 12
Joined: 2021-09-19 15:25

Re: ntfs i/o errors

#12 Post by nuxnoob »

5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0


seems maybe the fastboot flag was on for the month after i stopped using windows?
the surface scan turned that off then no?

seeker5528
Posts: 61
Joined: 2021-09-18 00:37
Been thanked: 2 times

Re: ntfs i/o errors

#13 Post by seeker5528 »

If you had 5 reallocated sectors I would guess the problem had to do with that.

When you use ntfs-3g from the command line to mount a Windows drive, it it recognizes the hibernation stuff is there it will fail to mount the partition with an error message telling you you need to boot into windows and disable that feature or mount the drive read only.

I would expect if it is in your fstab it would probably fail and leave an entry in a log file

Usually I would expect dmesg or systemlog which can be view as root.

Code: Select all

dmesg

or

journalctl --system
I don't have anything ntfs in my fstab at the moment to see how that would show up in the logs, but I would guess it would have mount or Mount or ntfs on the line so you could use the grep option of journalctl '-g' to cut down the output of that command.

Code: Select all

journalctl --system -g Mount
or search for ntfs and see if ntfs-3g is specifically included in the message.

I/O errors are typically hardware errors, so I don't think the fact that it is ntfs is really a factor. Low level corruption in the partition could also cause I/O errors but that is not so common. Splice errors when copying a file are more generic, but often they are a sign of a hardware issue, anything that causes a read or write failure could cause the splice error message.

I would keep an eye on the SMART data over the next few weeks, if any more sectors get remapped, I would plan on replacing the drive, I have seen too many drives that once the first few sectors fail they just continue to fail, sometimes rapidly.

nuxnoob
Posts: 12
Joined: 2021-09-19 15:25

Re: ntfs i/o errors

#14 Post by nuxnoob »

old topic this resolved itself when i moved the drive to another box.

Post Reply