Cornelius,<div><br></div><div>Most likely it is the hard drive itself, though it could be a BIOS issue (in times past you wouldn't be able to boot if your CMOS battery failed because the drive parameters stored in the BIOS were lost, but that was resolved many years ago with PNP by having the BIOS poll the drive for the parameters), since that is the moving part and those are what generally fail. If you suspect the controller, you could shuck out the drive and put it in an external USB enclosure and test on another machine to verify that it is not anything else with this laptop that is causing you grief.</div>
<div><br></div><div>Assuming it is the hard drive, it **should** be a SATA drive, but if much more than 4 or 5 years old, it could be an IDE drive. If SATA, you can get a new 500GB drive from NewEgg for ~ $100 to $120, or a 320GB for pretty much the same price, if you prefer. Your timing is bad on this as hard drives have gone up considerably in price since the flood in Thailand, but still 500GB 2.5" drive for less than $150 delivered isn't bad compared to what you would have paid for one that size just 2-3 years ago.</div>
<div><br></div><div>Someone posted about 7.2K 5 year warranty drives and yes, those are pretty much gone away. You only get the 5 year warranty on Enterprise Class Drives and "you gets what you pays for", as they say. But honestly folks, how can you expect the corporapist drive manufacturers to stay in business while selling a 3TB hard drive for ~ $150 retail (prior to the flood) and cover it for 5 or even 3 years. We all know that drives are generally MUCH more reliable than they were back in the MFM and RLL days not to mention BIGGER, FASTER and CHEAPER. So go cry in your beer if you can't find a 5 yr warranty drive for less than $300 now after the flood. But it is still pretty damn cheap for what you get with a 1 year warranty even after the flood.</div>
<div><br></div><div>BTW for you Seagate lovers/haters among us, they just recently agreed to buy the Samsung HDD business. I don't think the deal has closed yet, but probably won't be wrong. My guess is that Samsung didn't have good contracts for the parts that are in shortage since the flood and they are going to concentrate on SSDs, but I didn't actually read anything on that.</div>
<div><br></div><div>Regards,</div><div>Greg Clifton<br><br><div class="gmail_quote">On Tue, Jan 24, 2012 at 10:57 PM, Ron Frazier <span dir="ltr"><<a href="mailto:atllinuxenthinfo@c3energy.com">atllinuxenthinfo@c3energy.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Cornelis,<br>
<br>
Just to clarify a bit. I didn't realize an external drive was under<br>
consideration. I guess I didn't read your post fully.<br>
<br>
Regarding the internal drive. If it is mechanically damaged, or has a<br>
bad controller, etc., no software will fix it. However, computers often<br>
fail to boot because some data that they're trying to read during boot<br>
is corrupted. If a critical file has been deleted or something,<br>
Spinrite wouldn't be able to fix that. However, in many cases, the<br>
files are there, but parts of the sector have been corrupted where the<br>
data is stored. The computer usually tries to read a whole sector at a<br>
time and gives up rather easily if it can't read it. If Spinrite<br>
recovered damaged sectors enough so that the OS can read them, it is<br>
possible that the part of the sector that was damaged was not a critical<br>
boot file, but that the sector contained a critical boot file. Once the<br>
sector became unreadable, for whatever reason, that critical file<br>
couldn't be read either. If you fix the sector enough to be readable<br>
again, then that critical file might be readable. I hope that makes any<br>
sense whatsoever. In any case, it is entirely possible that Spinrite<br>
could restore the machine's ability to boot, and it often does, but is<br>
not guaranteed to do so, depending on the nature of the failure.<br>
<br>
Now, I should point out that Spinrite must be booted from a floppy disk<br>
or a CD. So, since you don't have a floppy, you'd probably have to boot<br>
from CD. You could boot from a floppy attached to USB, but we haven't<br>
established that you can boot from USB. More on that later. There is<br>
sometimes a setting in the BIOS that tells if you can boot from CD.<br>
Sometimes the machine will boot from a CD automatically. Sometimes you<br>
have to press a key to boot the cd or get a menu from which to boot the<br>
CD. You may have already mastered this problem, since you mentioned the<br>
SUSE installer.<br>
<br>
In any case, if you can boot from CD, you can use something such as<br>
Spinrite, or tools on The Ultimate Boot CD, or even a Linux Install Disc<br>
to run diagnostics and tests on the hard drive in the computer, even if<br>
that hard drive cannot be booted on its own.<br>
<br>
Now, I should mention that you would have to create said CD's on a<br>
computer that is bootable and working, or you'd have to order them by<br>
mail, if that's an option. If you burn your own CD's, be aware that<br>
really old machines, like my Win98 one (now running Lubuntu but<br>
decommissioned for being too slow), don't always like to read homemade<br>
CD's. Use a quality brand of blank disk to burn to improve your odds.<br>
<br>
As for a USB drive, if the computer is pre 2000 vintage, it may not be<br>
able to boot from USB. I have an old Win98 laptop that falls into that<br>
category. It also has USB 1 rather than USB 2. USB 1 is MUCH MUCH<br>
slower. Look in the BIOS for anything that mentions USB or USB<br>
emulation or USB booting and turn it on. Then, look for stuff that<br>
relates to the boot order. If you want, and if the option is there, you<br>
can set the system to boot first from the USB port, then the internal<br>
hard drive. So, if the system has this capability and if a USB drive is<br>
plugged in that's bootable, the system can boot from it. I keep my<br>
systems set to boot from internal HDD, then CD, then USB. If the<br>
internal drive is functioning, it will boot from that. If the internal<br>
HDD is not working, and a bootable CD is in the drive, it will boot from<br>
that. If the internal HDD is not working, and there is no CD in the<br>
drive, and a bootable USB device exists, it will boot from that. Any<br>
time I want, I can press the special key, which varies by computer, and<br>
get a menu and force a boot from any device.<br>
<br>
In general, booting from USB, even if you can, is a bad idea unless you<br>
have a special reason like testing, etc. The USB port is going to be<br>
much slower than the internal HDD interface. If your PC has USB 1,<br>
don't even think about it. However, as someone else mentioned, if you<br>
have access to eSata or USB 3, then booting an external drive becomes a<br>
lot more practical, other than the fact you have to attach it to boot.<br>
<br>
Regarding the BIOS. You MIGHT be able to boot a Live Linux Install<br>
disc, access the internet, and get a more recent BIOS patch. Installing<br>
it may be a problem, since the files are usually an executable that has<br>
to run from DOS or Windows. Some BIOS's have a deal where you can<br>
access the patch file from within the BIOS and it will do the upgrade.<br>
But, the patch file has to be stored somewhere, which needs a functional<br>
hard drive. You would have to research the particular procedure for<br>
your computer. Make sure you've got all the bases covered if you<br>
attempt this. Usually, if you start a BIOS upgrade and it fails in the<br>
middle, there is a good likelihood it will "brick" the computer and make<br>
it unusable.<br>
<br>
Hope this helps.<br>
<br>
Sincerely,<br>
<br>
Ron<br>
<div class="im HOEnZb"><br>
<br>
On 1/24/2012 8:05 PM, Cornelis van Dijk wrote:<br>
> Thank you all for the quick reply.<br>
><br>
> I should have mentioned that the drive does not want to boot anymore,<br>
> it just hangs with an idiot message about a wireless (RealTek) gadget<br>
> which needs its cables checked. As far as I know there is no such<br>
> thing on this laptop.<br>
><br>
> The BIOS still sees the drive but not the USB external Seagate. The<br>
> install program of suse 11.2 *does* see the external drive and I guess<br>
> I could install the OS on that, but would it boot?<br>
> Is there a way to force the BIOS to recognize the external drive? I<br>
> can find no mention of the USB drive anywhere in the BIOS (it mentions<br>
> a floppy, but this laptop does not even have a floppy!) Upgrading the<br>
> BIOS is probably also out of the question because of the boot problem.<br>
> It is a Phoenix BIOS from 1999.<br>
><br>
> It is kind of hard to see how programs like Spinrite would help if I<br>
> am not able to boot. Sorry for the incomplete information. Good to<br>
> know anyway.<br>
><br>
> Also good to know that these thing are user serviceable. It is a<br>
> Fujitsu drive. I guess I have to open the thing up. (A year ago I<br>
> succesfully mucked around inside my Sony Viao, disconnected a faulty<br>
> ventilator fan; thing does not seem to mind.)<br>
><br>
> Thanks again and any further help will be appreciated,<br>
><br>
> Cor van Dijk<br>
><br>
><br>
<br>
</div><div class="im HOEnZb">--<br>
<br>
(PS - If you email me and don't get a quick response, you might want to<br>
call on the phone. I get about 300 emails per day from alternate energy<br>
mailing lists and such. I don't always see new messages very quickly.)<br>
<br>
Ron Frazier<br>
<br>
<a href="tel:770-205-9422" value="+17702059422">770-205-9422</a> (O) Leave a message.<br>
linuxdude AT <a href="http://c3energy.com" target="_blank">c3energy.com</a><br>
<br>
</div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</div></div></blockquote></div><br></div>