Linux - KernelThis forum is for all discussion relating to the Linux kernel.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Is this error produced after the device is successfully detected and mounted?
If not, it may not indicate a problem. If they are produced during normal reads, it could be a drive media problem. I don't know what information is on those sectors.
When you say the filesystem is normal, did you actually unmount the filesystem and run a scan, such as using the fsck.ext3 if ext3 is the filesystem?
Another potential problem is if you are using an external hub, such as the usb port on a keyboard and your computer usb port doesn't supply enough power for both the keyboard and the drive.
That helps, thanks, ...
The architecture of my target is NOT X86, and I have made many changes to USB drivers in Linux OS Kernel, in other words, I only ported Linux kernel source codes to current target.
As you know, there are many kinds of external USB devices in P.R.China, I have tested many of them, but only one can not pass my experiment, it always occur the above errors,
If it is only one device with the problem, you might try using Google, including the model of the drive in your search. Maybe this device isn't up to specs. Did you check the filesystem. That will be the easiest thing to try. Remember Occam's razor! (Although I tend to favor Alexander's solution of the Gordian knot.)
Sorry, I'm not that familiar with scsi drivers. If I were you I would first eliminate the filesystem as being the problem. Another possibility is a problem with the media. Pen drives have a limited number of writes. That is why you use the noatime option when mounting them. You also may want to use the flush option as well. An external usb hard drive, could be using a hard drive disk inside that simply is going bad.
If it is just one device model, and another device of the same model behaves the same way, it may be a defect in that model rather than a problem with your scsi driver. You will want to avoid using that model.