Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
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.
I have just upgraded my machine to an ASUS A8V sck 939 and amd64 3500+ but seem to be having some 'issues' with my (admittedly old) SATA disk.
I run ubuntu breezy (64 bit) from a regular maxtor 40Gb drive and use another 160Gb SATA drive for storing my mp3s. Recently, however, access to the larger drive has been pretty temperamental, causing amarok and nautilus (or, indeed, any other program trying to access it) to freeze up and crash.
When I go for reboot, I'm frequently confronted with 'Buffer I/O errors on device sda*, logical block ****', with the * after the 'sda' varying across all partitions and the **** varying across several, sequential, values. Furthermore, within the past hour or two of trying to backup some of the data, I'm encountering the same messages at start-up, with no obvious end in sight.
I've tried telling my fstab not to mount the partitions automatically so that i can try and format them but this makes no difference - the errors come up whether it's automounting or not.
Is this a sign of hardware failiure or is there a way to solve the problem?
To try and diagnose further, i've hooked up the SATA drive to an external usb caddy. Here's the dmesg:
[ 1151.694291] usb-storage: device found at 7
[ 1151.694294] usb-storage: waiting for device to settle before scanning
[ 1188.318824] usb 5-2: reset high speed USB device using ehci_hcd and address 7
[ 1201.991209] scsi: Device offlined - not ready after error recovery: host 10 channel 0 id 0 lun 0
[ 1201.995435] usb-storage: device scan complete
[ 1329.684490] usb 5-2: USB disconnect, address 7
[ 1333.965117] usb 5-2: new high speed USB device using ehci_hcd and address 8
[ 1334.000861] scsi11 : SCSI emulation for USB Mass Storage devices
[ 1334.001525] usb-storage: device found at 8
[ 1334.001528] usb-storage: waiting for device to settle before scanning
[ 1370.626090] usb 5-2: reset high speed USB device using ehci_hcd and address 8
[ 1384.298202] scsi: Device offlined - not ready after error recovery: host 11 channel 0 id 0 lun 0
[ 1384.298460] usb-storage: device scan complete
Go to the hard drive manufacturer's website and download their hard drive diagnostic utilities. They are usually in the form of a bootable iso or floppy image. Then run the dignostic utilities on the drive. That's usually the best way to test a hard drive.