Debian User Forums

Posted: **2021-11-26 08:36**

It appears that the current 5.10 kernel has issues with NTFS file system:
- some errors are displayed in the logs (see below)
- the speed is about half compared with the same external HDD operating under Windows. Less than an issue, but this shows that there is room for improvements.
- higher CPU usage (about 15 - 20%) compared to Windows. Most likely is related with the point above.

First snippet:

kernel: usb 2-1.1: reset high-speed USB device number 39 using ehci-pci
kernel: sd 7:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=30s
kernel: sd 7:0:0:0: [sdd] tag#0 CDB: Read(16) 88 00 00 00 00 00 74 37 7c f0 00 00 00 10 00 00
kernel: blk_update_request: I/O error, dev sdd, sector 1949793520 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
kernel: usb 2-1.1: reset high-speed USB device number 39 using ehci-pci
kernel: sd 7:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=30s
kernel: sd 7:0:0:0: [sdd] tag#0 CDB: Read(16) 88 00 00 00 00 00 74 38 ca 00 00 00 00 f0 00 00
kernel: blk_update_request: I/O error, dev sdd, sector 1949878784 op 0x0:(READ) flags 0x84700 phys_seg 30 prio class 0
kernel: usb 2-1.1: reset high-speed USB device number 39 using ehci-pci
kernel: sd 7:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=30s
kernel: sd 7:0:0:0: [sdd] tag#0 CDB: Read(16) 88 00 00 00 00 00 74 3d c2 00 00 00 00 f0 00 00
kernel: blk_update_request: I/O error, dev sdd, sector 1950204416 op 0x0:(READ) flags 0x84700 phys_seg 30 prio class 0
kernel: usb 2-1.1: reset high-speed USB device number 39 using ehci-pci
kernel: sd 7:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=32s
kernel: sd 7:0:0:0: [sdd] tag#0 CDB: Read(16) 88 00 00 00 00 00 74 45 39 00 00 00 00 f0 00 00
kernel: blk_update_request: I/O error, dev sdd, sector 1950693632 op 0x0:(READ) flags 0x84700 phys_seg 18 prio class 0
kernel: usb 2-1.1: reset high-speed USB device number 39 using ehci-pci
kernel: sd 7:0:0:0: [sdd] tag#0 FAILED Result: hostbyte=DID_TIME_OUT driverbyte=DRIVER_OK cmd_age=30s
kernel: sd 7:0:0:0: [sdd] tag#0 CDB: Read(16) 88 00 00 00 00 00 74 49 eb 00 00 00 00 f0 00 00
kernel: blk_update_request: I/O error, dev sdd, sector 1951001344 op 0x0:(READ) flags 0x84700 phys_seg 30 prio class 0

In this case the disk activity simply "froze" for 30 seconds, then resumes and the cycle repeats.

Second snippet:

kernel: blk_update_request: I/O error, dev sdc, sector 1672718464 op 0x0:(READ) flags 0x80700 phys_seg 9 prio class 0
kernel: sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
kernel: sd 6:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current]
kernel: sd 6:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
kernel: sd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 63 b3 c0 80 00 01 00 00
kernel: blk_update_request: I/O error, dev sdc, sector 1672724608 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
kernel: sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
kernel: sd 6:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current]
kernel: sd 6:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
kernel: sd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 63 b4 41 80 00 01 00 00
kernel: blk_update_request: I/O error, dev sdc, sector 1672757632 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0
kernel: sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
kernel: sd 6:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current]
kernel: sd 6:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
kernel: sd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 63 b4 4f 80 00 01 00 00
kernel: blk_update_request: I/O error, dev sdc, sector 1672761216 op 0x0:(READ) flags 0x80700 phys_seg 8 prio class 0
kernel: sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
kernel: sd 6:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current]
kernel: sd 6:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
kernel: sd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 63 b4 b2 80 00 01 00 00
kernel: blk_update_request: I/O error, dev sdc, sector 1672786560 op 0x0:(READ) flags 0x80700 phys_seg 32 prio class 0
kernel: sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
kernel: sd 6:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current]
kernel: sd 6:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
kernel: sd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 63 b4 e6 80 00 01 00 00
kernel: blk_update_request: I/O error, dev sdc, sector 1672799872 op 0x0:(READ) flags 0x80700 phys_seg 28 prio class 0
kernel: sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
kernel: sd 6:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current]
kernel: sd 6:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
kernel: sd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 63 b5 20 80 00 01 00 00
kernel: blk_update_request: I/O error, dev sdc, sector 1672814720 op 0x0:(READ) flags 0x80700 phys_seg 9 prio class 0
kernel: sd 6:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=0s
kernel: sd 6:0:0:0: [sdc] tag#0 Sense Key : Not Ready [current]
kernel: sd 6:0:0:0: [sdc] tag#0 Add. Sense: No additional sense information
kernel: sd 6:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 63 b5 75 80 00 01 00 00
kernel: blk_update_request: I/O error, dev sdc, sector 1672836480 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0

Here there is a movie playing and the play stops or video/sound loose sync.

Using USB 2 or USB 3 ports doesn't change anything.

The problem is that there is no issue with the hard drive, I did a (surface) check on Windows and everything was ok. Under Windows everything works as expected, no error is displayed in the logs.
None of the drives show symptoms of a dying drive like vibrations, chirping sounds while operating.

If I remember correctly, I read that in kernel 5.12 there is a new NTFS driver.

Any observations, suggestions, tips will be highly appreciated.

Posted: **2021-11-27 21:05**

This seems to be a USB or drive issue.

FWIW, the old limited NTFS driver (ntfs) is disabled in Debian kernels and NTFS is handled in userspace with ntfs-3g. The new NTFS driver (ntfs3) was introduced in kernel 5.15, not 5.12.

Posted: **2021-11-30 09:31**

The external HDD drive works flawlessly under WIndows, so I would exclude it.
USB?... I don't know, the rest of devices work as expected, including the cases when a exFat external hard drive is used.
How can I investigate more?

As for the kernel currently I have 5.10.0-9-amd64 #1 SMP Debian 5.10.70-1 (2021-09-30)
When I connect the NTFS HDD there is no kernel module resembling ntfs, however package ntfs-3g (version 2017.3.23AR.3-4+deb11u1) is installed, so I take this as a confirmation of what you said.

Kernel 5.15 is label as experimental in Debian 11 and perhaps it will not reach stable branch too soon, maybe not in Debian 11.

Posted: **2022-01-26 08:09**

In the end it was a dying USB (actually eSATA) port that has 4.7 - 4-8 V at idle, more likely less when a HDD is attached.
Unfortunately 2 HDDs were affected permanently (bad sectors).

It can be closed now.

Posted: **2022-01-26 08:15**

Just to clarify some possible misunderstandings:

undesign wrote: ↑2021-11-30 09:31 Kernel 5.15 is label as experimental in Debian 11 and perhaps it will not reach stable branch too soon, maybe not in Debian 11.

Debian 11, as in the current Debian Stable, will never get a new kernel by default. The kernel may be available in backports and easy to install in Debian Stable, but that doesn't mean it will replace the current official kernel, i.e. 5.10.

Posted: **2022-01-26 12:53**

Thanks for the feedback. You can mark the thread as solved in the subject.

Debian User Forums

[SOLVED] Wrong / fake error messages when an external NTFS HDD is connected

[SOLVED] Wrong / fake error messages when an external NTFS HDD is connected

Re: Wrong / fake error messages when an external NTFS HDD is connected

Re: Wrong / fake error messages when an external NTFS HDD is connected

Re: Wrong / fake error messages when an external NTFS HDD is connected

Re: Wrong / fake error messages when an external NTFS HDD is connected

Re: Wrong / fake error messages when an external NTFS HDD is connected