I have a dell studio 1536 my hard disk got corrupted a month ago and tried different software could not make it to work so, decided to buy another HD .
my new hard drive is (used) bought in ebay and SMART shows 100% health also tested on dell diagnosetic utility and all tests passed .
So, here comes my problem , the very first time when i poped (new/used) HD into the laptop and started, it showed me the above error ''no bootsector on internal hard drive'' and gave me 3 options F1 retry , F2 setup , F5 dell diganose utility. I ignored it as you all know a HD without system files, partion , or windows would do exactly the same , and i went ahead and somehow sorted windows vista to install . When setup expanded files, it restarted and when dell logo and flash screen passed where it was supposed to boot from C: it gave me this error again , but the vista disk was still there i thought let the cd take care of it as the HD may not have been used after couple formating and wiping. So thought it,s normal, all installation went normal finally restarted again with same error above .
Now if i put windows cd or whatever bootable madia i can get to my windows if i dont hit any key but first it will show the above error and then it will boot other media , even i can access to windows by pressing F1 ''retry'' after message appears and it will boot successfully fast and flawlessly but, windows cant find boot section by its own .
Installed vista and windows 7 four times but same symptoms
NOTE>>>> It will only occure when I enable AHCI mode , installed on ATA mode doesnt require me to do anything and will successfully go to boot from bios .
my bios setup is in correct order and
also reseted couple of times . reseated hard drive one time
also i installed sata drive driver
downloaded from dell site and loaded with usb everytime when i installed . So what could be the problem?
Am i missing something prior or after installation ?
I have completely lost my mind with this problem , tried 7hours of searching in forums nobody else has got same problem as mine , the error is same but symptoms are different