Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Distribution: RH 6.2, Gen2, Knoppix,arch, bodhi, studio, suse, mint
Posts: 3,304
Rep:
I've seen several hard drives that the bios recognized, but you couldn't do anything else with. the best thing is just the boot floppy image you can download from the hard drive manufacturer. It will tell you if you drive is bad.
I've had a hard drive where the platters would stick to the heads. The bios would recognize it, but it wouldn't spin up. I had to spin it really hard in my hand to make the platters move, then put it back in the computer and it would work until it happened again. It's called stiction. http://www.webopedia.com/TERM/S/stiction.html
I've had a few drives from western digital and quantum that went, thunk, thunk, thunk, about 3 times a second forever until you turned it off. the bios would "see" the drive, but it wouldn't do anything.
Anyway, on an ide drive, the controller is on the bottom of the drive. That's what that circuit card is. You can easily have something physically wrong with the moving parts that the circuit card doesn't understand, or the circuit card can be damaged and the the moving parts not.
Distribution: RH 6.2, Gen2, Knoppix,arch, bodhi, studio, suse, mint
Posts: 3,304
Rep:
I think i just had a maxtor 20 gig die today. I put it in a new computer as a second drive for extra space this morning. I fdisked it, and formatted and mounted a filesystem on it this morning. Late this afternoon, i tried to access the drive, and the computer would just hang up for a minute or 2, and tell me it couldn't access the drive. I rebooted and saw the bios didn't detect the drive. I didn't really care, but it was messing up the first drive too. The case was behind another computer, and had been running at full load all day. It was super hot. I opened the case and the hard drives were really hot. After they cooled off while i added 2 fans to the case, i booted the machine, and the 20 gig maxtor would detect, but i couldn't access it. Like yours. Bios detects, but the computer cannot read or write anything to the drive.
With the 2 new fans, the computer is running almost 20 degrees cooler at full load. 131 down to 112.
the best thing is just the boot floppy image you can download from the hard drive manufacturer. It will tell you if you drive is bad.
I did try the MaxBlast 3 CD that came with the HDD and another one which I downloaded off their website. Both did not display the HDD.
Quote:
I've had a few drives from western digital and quantum that went, thunk, thunk, thunk, about 3 times a second forever until you turned it off. the bios would "see" the drive, but it wouldn't do anything.
I have a Maxtor 30gig 7200rpm (the current one). Anyways, I know what you are talking about with the repititious clunking noises. The BIOS does detect it but those are always near death. In my school, if they are found, I just put them in storage just in case some experiments are needed to be done.
Quote:
Anyway, on an ide drive, the controller is on the bottom of the drive. That's what that circuit card is. You can easily have something physically wrong with the moving parts that the circuit card doesn't understand, or the circuit card can be damaged and the the moving parts not.
I am very well aware of the integrated circuit and there has never been any damage to it. If taken out from the system, it was always held from the side and placed on an anti-static bags.
Quote:
I fdisked it, and formatted and mounted a filesystem on it this morning.
Ok, so it was working fine that morning.
AND:
Quote:
The case was behind another computer, and had been running at full load all day. It was super hot. I opened the case and the hard drives were really hot. After they cooled off while i added 2 fans to the case, i booted the machine, and the 20 gig maxtor would detect, but i couldn't access it.
So it was a cooling problem for you yet you still can't access the drive. Maybe something melted? And when you say it went down from 131 to 112, do you mean celsius or fahrenheit? The most highest my hdd had gotten was 47C at full load.
--Abid Kazmi
Last edited by securehack; 05-23-2005 at 10:30 AM.
OK, finally tried out the other Max software. It does not detect it nor can it do anything. Any suggestions or similar topics that can be found aside from this thread?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.