Archived from groups: comp.sys.laptops (More info?)
I have a problem with a computer which doesn't recognise its hard disc.
It behaves exactly as if the hard disc was missing or completely
unreadable, and asks for a boot device. Microsoft's FDISK does not see
the drive. When removed, the drive can be read perfectly by another
computer; if a new, known good, drive is fitted in the faulty machine,
FDISK does not recognise it. The machine works fine when booted from CD-
ROM, although the bad drive is not seen by any program.
If this is a known problem, what is the usual cause, please?
Archived from groups: comp.sys.laptops (More info?)
On Wed, 02 Mar 2005 11:05:31 -0800, <a$-b$1@ms3.org.uk> wrote:
> I have a problem with a computer which doesn't recognise its hard disc.
> It behaves exactly as if the hard disc was missing or completely
> unreadable, and asks for a boot device. Microsoft's FDISK does not see
> the drive. When removed, the drive can be read perfectly by another
> computer; if a new, known good, drive is fitted in the faulty machine,
> FDISK does not recognise it. The machine works fine when booted from CD-
> ROM, although the bad drive is not seen by any program.
>
> If this is a known problem, what is the usual cause, please?
>
> (The machine is a Toshiba Satellite 1410)
Sounds like a bad HD controller (motherboard in this case) or defective
cable
Archived from groups: comp.sys.laptops (More info?)
a$-b$1@ms3.org.uk wrote:
: I have a problem with a computer which doesn't recognise its hard disc.
: It behaves exactly as if the hard disc was missing or completely
: unreadable, and asks for a boot device. Microsoft's FDISK does not see
: the drive. When removed, the drive can be read perfectly by another
: computer; if a new, known good, drive is fitted in the faulty machine,
: FDISK does not recognise it. The machine works fine when booted from CD-
: ROM, although the bad drive is not seen by any program.
How did this happen? Have you used this computer until now and this
problem just started? Or did you inherit the computer and it has
never worked?
If the computer is new to you, I would check the BIOS and make sure
the hard disk controller is enabled. If so, as the other person said,
it could be the cable or the internal HDD controller.
Andrew
--
----> Portland, Oregon, USA <----
*******************************************************************
----> http://www.bizave.com <---- Photo Albums and Portland Info
----> To Email me remove "MYSHOES" from email address
*******************************************************************
Archived from groups: comp.sys.laptops (More info?)
I asked:
> : I have a problem with a computer which doesn't recognise its hard disc.
> : It behaves exactly as if the hard disc was missing or completely
> : unreadable
Andrew wrote:
> How did this happen? Have you used this computer until now and this
> problem just started?
Thanks to all who responded. The computer just stopped booting. I had
checked the BIOS settings in case they had become corrupted (everything
OK). So it's almost certainly the cable (faulty or just not connected
properly) or the (out-of-warranty) motherboard.
Archived from groups: comp.sys.laptops (More info?)
Sounds like you either have a configuration problem or a bad IDE port.
a$-b$1@ms3.org.uk wrote:
> I have a problem with a computer which doesn't recognise its hard disc.
> It behaves exactly as if the hard disc was missing or completely
> unreadable, and asks for a boot device. Microsoft's FDISK does not see
> the drive. When removed, the drive can be read perfectly by another
> computer; if a new, known good, drive is fitted in the faulty machine,
> FDISK does not recognise it. The machine works fine when booted from CD-
> ROM, although the bad drive is not seen by any program.
>
> If this is a known problem, what is the usual cause, please?
>
> (The machine is a Toshiba Satellite 1410)
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.