I have been given a 80GB drive, as above, and for a short while worked fine.

The drive is now not recognised at POST and also the master drive is not

being recognised as well, the Samsung drive being the slave. I have tried

the HDD diag util from samsung but even that wont recognise the drive. Is

this drive now defunct and why is the master not being recognised? This has

not happened before when I have had a drive fail.

LeeG wrote:

> I have been given a 80GB drive, as above, and for a short while

> worked fine. The drive is now not recognised at POST and also the

> master drive is not being recognised as well, the Samsung drive being

> the slave. I have tried the HDD diag util from samsung but even that

> wont recognise the drive. Is this drive now defunct and why is the

> master not being recognised? This has not happened before when I

> have had a drive fail.

 

Disconnect the Samsung. Does the master then work?

Yes. Everything is detected and operates normally without the samsung

connected.

 

"Keith" wrote:

> LeeG wrote:

> > I have been given a 80GB drive, as above, and for a short while

> > worked fine. The drive is now not recognised at POST and also the

> > master drive is not being recognised as well, the Samsung drive being

> > the slave. I have tried the HDD diag util from samsung but even that

> > wont recognise the drive. Is this drive now defunct and why is the

> > master not being recognised? This has not happened before when I

> > have had a drive fail.

>

> Disconnect the Samsung. Does the master then work?

>

>

>

>> LeeG wrote:

>> > I have been given a 80GB drive, as above, and for a short while

>> > worked fine. The drive is now not recognised at POST and also the

>> > master drive is not being recognised as well, the Samsung drive being

>> > the slave. I have tried the HDD diag util from samsung but even that

>> > wont recognise the drive. Is this drive now defunct and why is the

>> > master not being recognised? This has not happened before when I

>> > have had a drive fail.

 

> "Keith" wrote:

>> Disconnect the Samsung. Does the master then work?

 

 

 

"LeeG" <lee.gorton(removethis)@hotmail.co.uk> wrote in message

news:006554CA-AD21-4F8F-8884-28895DC70610@microsoft.com...

> Yes. Everything is detected and operates normally without the samsung

> connected.

 

 

LeeG:

We are assuming that you've properly connected/configured the device and

that its power connection & IDE data cable are non-defective.

 

It certainly sounds like you're dealing with a dead HDD. You could try

installing it in another machine as kind of a last-resort diagnostic but

from the way you've described the situation it sounds like the disk is

kaput. I'm sure you're aware that particular Samsung is fairly "old in the

tooth", yes?

 

Also, if you haven't done so already, try connecting the drive to another

IDE channel - try both the Master/Slave configurations. You could even try

(as a test) installing it as Primary Master (I'm assuming it does not

contain a bootable OS) and installing your boot drive as either a Slave on

the Primary IDE channel or as Master on the Secondary IDE channel. Just to

see what happens in those situations.

 

Anyway, it won't be the first time a non-defective completely functional

boot drive refuses to boot with a defective secondary HDD installed in the

machine. We've experienced this many times. It's not as unusual as you may

think. We've even come across similar types of non-booting situations where

there was no problem with the boot drive per se but where the defective

device was an optical drive or even a USB external HDD.

Anna

Thank you for your reply. I have tried the different combinations you have

suggested and it refuses to work. I will be refiling the drive in the bin I

think.

 

 

"Anna" wrote:

>

> >> LeeG wrote:

> >> > I have been given a 80GB drive, as above, and for a short while

> >> > worked fine. The drive is now not recognised at POST and also the

> >> > master drive is not being recognised as well, the Samsung drive being

> >> > the slave. I have tried the HDD diag util from samsung but even that

> >> > wont recognise the drive. Is this drive now defunct and why is the

> >> > master not being recognised? This has not happened before when I

> >> > have had a drive fail.

>

>

> > "Keith" wrote:

> >> Disconnect the Samsung. Does the master then work?

>

>

>

> "LeeG" <lee.gorton(removethis)@hotmail.co.uk> wrote in message

> news:006554CA-AD21-4F8F-8884-28895DC70610@microsoft.com...

> > Yes. Everything is detected and operates normally without the samsung

> > connected.

>

>

> LeeG:

> We are assuming that you've properly connected/configured the device and

> that its power connection & IDE data cable are non-defective.

>

> It certainly sounds like you're dealing with a dead HDD. You could try

> installing it in another machine as kind of a last-resort diagnostic but

> from the way you've described the situation it sounds like the disk is

> kaput. I'm sure you're aware that particular Samsung is fairly "old in the

> tooth", yes?

>

> Also, if you haven't done so already, try connecting the drive to another

> IDE channel - try both the Master/Slave configurations. You could even try

> (as a test) installing it as Primary Master (I'm assuming it does not

> contain a bootable OS) and installing your boot drive as either a Slave on

> the Primary IDE channel or as Master on the Secondary IDE channel. Just to

> see what happens in those situations.

>

> Anyway, it won't be the first time a non-defective completely functional

> boot drive refuses to boot with a defective secondary HDD installed in the

> machine. We've experienced this many times. It's not as unusual as you may

> think. We've even come across similar types of non-booting situations where

> there was no problem with the boot drive per se but where the defective

> device was an optical drive or even a USB external HDD.

> Anna

>

>

>