Putting a Seagate U6 Model ST360020A HD as a slave

  • Thread starter Thread starter W. eWatson
  • Start date Start date
W

W. eWatson

I loaned a friend an old XP PC that has a master and slave drive. He
lives some distance from here. I'm pretty sure my drives are WD. He's
trying to replace my slave with a Seagate U6 Model ST360020A used as a
master on an old XP PC of his, but is running into problems. The Seagate
drive doesn't use jumpers as a slave. It just won't boot. It does boot
with the two WDs. Comments?
 
I loaned a friend an old XP PC that has a master and slave drive. He
lives some distance from here. I'm pretty sure my drives are WD. He's
trying to replace my slave with a Seagate U6 Model ST360020A used as a
master on an old XP PC of his, but is running into problems. The Seagate
drive doesn't use jumpers as a slave. It just won't boot. It does boot
with the two WDs. Comments?
Click to expand...

If you're going to use jumpers, both drives have to be jumpered
correctly.

If the ST360020A will be the Slave, remove all jumpers. (You already
know this, since you mentioned it above.) Also, be sure it's connected
to the Slave connector on the IDE cable. Speaking of the IDE cable, I
would use an 80-conductor cable rather than the older 40-conductor
type, although that shouldn't be a total barrier to operation.

Regarding the Master, then, be sure it's jumpered in a way that allows
the Slave to be present, and be sure the Master is connected to the
proper connector on the IDE cable. No hints on proper jumpering
because you didn't provide the model number.

Before trying to boot with the new configuration, and especially since
there's apparently a problem, be sure to enter the BIOS configuration
screen and make sure both drives are properly recognized, (make,
model, size, and master/slave status), before proceeding.

If all of that is good and the system won't boot, provide details on
exactly what happens. Boot progress, error messages, etc. There's a
slim possibility that the system's boot files are on the drive that
was removed, but you can see if that's the case by looking at Disk
Management. Not sure if you've already checked that.
 
If you're going to use jumpers, both drives have to be jumpered
correctly.

If the ST360020A will be the Slave, remove all jumpers. (You already
know this, since you mentioned it above.) Also, be sure it's connected
to the Slave connector on the IDE cable. Speaking of the IDE cable, I
would use an 80-conductor cable rather than the older 40-conductor
type, although that shouldn't be a total barrier to operation.

Regarding the Master, then, be sure it's jumpered in a way that allows
the Slave to be present, and be sure the Master is connected to the
proper connector on the IDE cable. No hints on proper jumpering
because you didn't provide the model number.

Before trying to boot with the new configuration, and especially since
there's apparently a problem, be sure to enter the BIOS configuration
screen and make sure both drives are properly recognized, (make,
model, size, and master/slave status), before proceeding.

If all of that is good and the system won't boot, provide details on
exactly what happens. Boot progress, error messages, etc. There's a
slim possibility that the system's boot files are on the drive that
was removed, but you can see if that's the case by looking at Disk
Management. Not sure if you've already checked that.
Click to expand...
Thanks for the tips, but the puzzle was solved. He had not taken the
jumper on the drive off.
 
Cool, thanks.
Click to expand...
Well, my friend returned to copy material off of the seagate onto a usb
thumb drive. He cannot see the drive when he is booted up. He can see
it in bios. What's missing?
 
Well, my friend returned to copy material off of the seagate onto a usb
thumb drive. He cannot see the drive when he is booted up. He can see
it in bios. What's missing?
Click to expand...

A drive letter?
 
Good. I love happy endings.
Click to expand...
There is no happy ending. The problem persists. There is no drive
letter. If one goes into Device Drivers, the Seagate is there. There
are three partitions on the primary C: drive. C:, D:, and E:. He has the
Seagate on the secondary drive, and it cannot be seen or accessed at all.
 
There is no happy ending. The problem persists. There is no drive
letter. If one goes into Device Drivers, the Seagate is there. There
are three partitions on the primary C: drive. C:, D:, and E:. He has the
Seagate on the secondary drive, and it cannot be seen or accessed at all.
Click to expand...

Disk Management is where you want to go, not Device Manager.

From Start->Run, type diskmgmt.msc and hit Enter.

Once in Disk management, verify that the drive is detected, and
detected properly, then right click on it and select "Change Drive
Letter and Paths". Click Add, select a letter, and OK your way out.
 
Disk Management is where you want to go, not Device Manager.

From Start->Run, type diskmgmt.msc and hit Enter.

Once in Disk management, verify that the drive is detected, and
detected properly, then right click on it and select "Change Drive
Letter and Paths". Click Add, select a letter, and OK your way out.
Click to expand...
We actually started down the disk mgmt. way, but couldn't see his
Seagate. There was a row labeled Disk 0: C: D: E:, and maybe another row
labeled G: H:. That left F: unaccounted for.

G and are the CD and DVD drives. C, D, and E are partitions of a WDC
drive. I sent him your instructions anyway, so we'll see what happens
eventually.
 
We actually started down the disk mgmt. way, but couldn't see his
Seagate. There was a row labeled Disk 0: C: D: E:, and maybe another row
labeled G: H:. That left F: unaccounted for.

G and are the CD and DVD drives. C, D, and E are partitions of a WDC
drive. I sent him your instructions anyway, so we'll see what happens
eventually.
Click to expand...


This drive needs to be formatted.
Thats the problem :-)
 
Back
Top