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.
My first plan of action was to unmount the drive (which contains an ext3 filesystem) and run:
fsck -y /dev/hdb1
it ran and corrected some errors and ended.
I remounted the drive and have tried to pull all important data from it...in the midst of this, I was watching the logs for more errors and sure enough, the same ones as lited above re-surfaced.
I un-mounted the drive again and ran: fsck -y /dev/hdb1 and it returned that the disk was clean!?!?
I am also getting I/O errors from this disk (which, by the way is a brand new WD 200GB / 7200RPM / 8mb cache disk) which look like:
[root@bono data]# cp: reading `<FILE>': Input/output error
I think the inevitable is replacing this disk, but its brand new...how often do brand new (within 2 weeks of purchase) drives fail? Anomaly here? Can anyone offer an alternate plan of action to check whether this disk is indeed failing???
Yep. Try like kilgoretrout said, but I just had one bite the dust instantly, spewing Seek/Error messages like that.
Basically, disks fail in one of two ways - almost immediately or after years. It's not *common* for them to fail in a matter of days/weeks but more common than to fail after a year or so. It's not extraordinary. If you're under warranty and have your data backed up, you're in good shape. Or you can be like I was.