9.5

Table Of Contents

31 Paragon NTFS&HFS+ for Linux 9.5

7.11 Hardware issues

Sometimes storage issues are caused by a faulty hardware. Hardware issues can be classiﬁed by

their place of origin:

1. storage device (HDD, SSD, USB ﬂash drive, SD card, etc.)

2. target platform (hardware board which utilizes the UFSD driver)

3. data medium (e.g. USB cable)

Often this kind of issues can be identiﬁed based on the system log output (e.g. dmesg). The basic

principle is to look for an error messages from the underlying subsystem on top of which the UFSD

driver operates (e.g. USB controller). Some examples:

» usb

: USB disconnect, device number

***

(in case the USB device was not actually disconnected)

» end_request: I/O error, dev sdX, sector

***

» Buffer I/O error on device sdX, logical block

***

» mmcblk

: error -110 transferring data, sector

***

» sd

: [sdX] Unhandled error code

» sd

: [sdX] Spinning up disk........not responding...

» sd

: [sdX] Device not ready

» xhci_hcd

: WARN: Stalled endpoint

Identiﬁcation of the faulty hardware cannot be done solely on the UFSD driver messages because the

driver operates on a higher level than HW drivers. Still UFSD messages can be helpful for obtaining

a general picture of the issue. Here are some typical messages in case of hardware issues:

» ufsd: failed to read block 0xNNNN

» ufsd: failed to map block 0xNNNN

» ufsd: failed to write block 0xNNNN

» ufsd: bio read I/O error

A hardware problem cannot be solved at the ﬁle system driver level. Thereby that kind of issues

is out of the Paragon’s scope of responsibility. The best solution is to contact the faulty hardware’s

manufacturer technical support. One should contact us only if the hardware fault is followed by a

system hang or kernel panic caused by the UFSD driver.