Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Drive info:
(the following returned from smartctl -i)
Device: ATA Maxtor 6V200E0 Version: VA11
Serial number: V40AQBEG
Device type: disk
Size: 200GB
The disk in question (/dev/sdb) is a secondary, non-RAID harddrive that mounts as /home2 on my machine. The primary drive (with OS) is /dev/sda and is a Samsung 80GB SATA drive, recognized by the system as SATA0. Let me stress that I am NOT having any problems with /dev/sda... it is only /dev/sdb that keeps acting strange.
The problem:
After some heavy use, /dev/sdb (/home2) becomes inaccessible. Well, you can 'cd' to it, but that's about it. 'ls' returns nothing. This has happened twice and both times I have recovered it by performing the same method: crack the machine open and plug the drive into a different SATA port on the mo'board. Reboot, go into BIOS to enable SATA1, SATA2, or SATA3... whatever I happen to be using at the time. The machine boots fine and /dev/sdb mounts like normal. I can access everything just fine... for a while anyways. I ran fsck, e2fsck on /dev/sdb and it returned a 'clean' message. Okay, that's great. I backed up all of the data just in case.
The last time I cracked open the machine to switch SATA ports, I noticed that the drive in question was burning hot... I mean, really, really hot. It was far warmer than the primary drive. I know these things can get warm, but this guy was ridiculously hot.
I'm guessing that this is not a SATA controller problem, because I'm not having problems with /dev/sda. The temperature of the drive makes me think that it is possibly shutting down to prevent damage, but I'm not sure.
If you suspect a heat problem, you could use a household fan to see if it helps. Open the case, leave the door off, and point the fan toward the inside of the case. Then, attempt to duplicate the problem. If the fan helps, you might want to look at your cabling to see if you can improve air flow inside the case. Also, you may want to look at hard drive cooling systems. A simple heat sink may be enough to fix the problem. I'd like to tell you that hard drives shouldn't get that hot but in reality, they can.
First, I would try upgrading your kernel and seeing if the problem persists. SATA support in 2.6.9 was a pain in the BUTT for me even to get working correctly, let alone getting working well. Now, though, SATA support seems to be working quite nicely (2.6.17 here).
I'm not saying this is going to solve your problem necessarily, but regardless of whether or not you solve the problem you should still upgrade your kernel if you are using SATA drives.
Drive info:
(the following returned from smartctl -i)
Device: ATA Maxtor 6V200E0 Version: VA11
Serial number: V40AQBEG
Device type: disk
Size: 200GB
So what does smartctl --all /dev/sdb say the temperature is? For comparison my 7200 rpm Seagate Barracuda is currently running at 43 celsius with a worst temp of 55 celsius. And I ran it in a room without AC this summer, so if it's hotter than that I say just return it. Maxtor has a "no quibble" policy so they're not going to argue with you about it anyway.
Hey, thanks a bunch everyone. I am always so impressed by the response that I get to my posts.
Interestingly enough, I have set up about 10 identical systems over the past month and this is the first time I have had any disk problems. I suppose that I should thank my lucky stars that the failure/problem rate at this point is less than 3% (each system has at least three disks).
I'll checkout the Maxtor utilities and also see what smartctl has to say about temperatures etc. I'm just glad I was able to copy all of the data off before it went completely FUBAR. I feel that the overheating is just a symptom of a much larger problem with the disk. After all of the reading I have done lately about disk failures, it's amazing that they don't happen more often!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.