hitachi 5k320-160 with model hts543216L9a300 160 GB problem

[sdthgi]

hello dear friend .
i have a acer extensa 420 labtop.
my probelm is that everytime i press power button in laptop the windows does not start and error tell me No Bootable device -- Insert boot disk and press any key . and when is press control + alt+delete . windows comming up and everything is ok.
my problem only this that i have to the restart the computer to start windows . and if i turn off the computer and press power on computer and go to setup my hard disk model does not show. and if i press conrol +alt+delete in bios it show my hard disk model number and my problem will be solved .
please tell me why i need to restart my computer everythime to my windows will be ok.
for this probelm.
i fdisk my harddisk .with acronis . with paragon and with ....
install new windows.
repair mbr .
update the bios of labtop.
. i changed my hardisk to new one and my problem with solved . please help me . i know the problem is my hardisk and need to update the firmware . but i can`t find the firmware in everywhere.
my hardisk model is :hitachi 5k320-160 with model hts543216L9a300 160 GB.
i`m so appreciated.

[labtech]

Not so sure the problem is the hard disk. More tests are necessary.

Test the hard disk on another machine with MHDD to confirm intermittent failure.

[Vulcan]

@sdthgi,

i know the problem is my hardisk

Based on your story, I agree (although as labtech said, further tests may help to confiirm the situation; a slow spin-up problem would fit with your description).

and need to update the firmware

No, you don't "need" to do that. You have not diagnosed a firmware problem and IMHO your description does not fit with a firmware problem anyway, so you are wasting your time looking in that area.

[warnerr]

Suugest you turn it on and go to Bios. I am intrested if it has correctly identified itself at that point without reboot. If yes as a longshot try moving the boot order.

[sdthgi]

thank you for your respone .i checked my harddisk with mhdd and it finished without warning . please help what can i do?

[labtech]

thank you for your respone .i checked my harddisk with mhdd and it finished without warning . please help what can i do?

So as anticipated the hard disk is fine.

Have warranty on your laptop?

[Vulcan]

@labtech,

So as anticipated the hard disk is fine.

Although the OP's latest comment is ambiguous (I can think of at least 5 possible interpretations, of what he might be describing), I respectfully disagree that the conclusion can be that the (original) disk is OK. Note that the OP has already said:

i changed my hardisk to new one and my problem with solved

so IMHO that is clear evidence that the disk is at least part (and I suspect all) of the problem.

The original test results from the OP describing when the disk is, and is not, reported by the BIOS still fit my hypothesis of a disk which is slow to spin-up (or slow to come ready for any other reason) and that it needs extra time to do so (hence why a failed boot, which takes time, followed by ctrl+alt+del then allows the disk to be used, as described by the OP). I've seen this behaviour several times before... A disk with this type of problem can still test OK with MHDD, due to the extra time needed to boot MHDD which can then allow the disk enough time to become ready.

In a proper bench test setup, with controlled power to the disk, then we could test how long it takes for the drive to become ready and see if this is abnormal - but in a laptop like the OP, and trying to work remotely, I don't see an easy way to do that. The SMART data spin-up time attribute may give a clue for some types of problem, but it would not necessarily be conclusive.

Perhaps you are finding more info in the OP's description than me, but my view is still that the specific type of disk problem that I described, fits with the OP's results so far.

@sdthgi,

I am not perfect but as you can read above, I have a different opinion of the situation from labtech, based on my interpretation of your story. It would be require you to perform more tests to attempt to prove (or disprove) my hypothesis, and also require very clear and unambiguous updates from you. The problem is that since we don't know your skills, available equipment, attitude to risk, and other limits, we might waste our time describing tests for you to perform which you cannot do, since we cannot see your situation remotely.

Instead, one common technical approach (but perhaps not the easist method for you!) is for you to put your original hard disk into another laptop of the same make, model and preferably BIOS revision as yours. Does the original problem (e.g. PC fails to boot first time, but does boot after ctrl+alt+del - and/or disk not recognised in BIOS setup after power-on, but is then recognised after ctrl+alt+del) then show in that different laptop? If so, then you have proved that this is a disk problem, because the problem would have moved with the disk into that different laptop.

However, it may be difficult or impossible for you to find and borrow another laptop of the same type, for this test. Note: Using another laptop with different make / model / BIOS than your laptop might produce unexpected results, if that different laptop has a different BIOS timeout for a disk to become ready. However, if you only have access to a completely different laptop, the result of doing the "BIOS check" test in that completely different might still confirm my hypothesis.

Other possible plans would, as I said before, require your time and effort to perform tests, and require you to clearly provide unambiguous updates in English. I am already seeing some communication problems, and that always makes remote diagnosis much, much more difficult. It is your decision how much effort you want to put into your investigation.

If you have already decided that this is a disk problem (as you said originally, and based on your story, then I agree with you), and since this is not a disk firmware problem, then what help are you now requesting from readers here?

[SAjunky]

In some BIOS setup you can add delay to the hard disk. If such option is not present, changing quick boot to slow, or select full memory tests can increase time before hard drive is checked.
However as Vulcan pointed out, slower than usual come to ready state is a sign for hardware malfunction and shouldn't be ignored.
I would reseat connector to the hard drive first. Also cleaning PCB contacts might help.

[labtech]

Vulcan is right, it is not 100% cristal clear yet.

I just solely posted opinion based on what the OP mentioned.
For me, just one test would not be enough, but again it is up to the individual and time & resources they want to invest.