Topic: Connecting a hard disk drive in slave only mode leads to system halt (Read 2710 times)

toasty0 · « **on:** August 30, 2005, 06:40:10 pm »

Connecting a hard disk drive in slave only mode leads to system halt during resume from standby

Tus-XC · « **Reply #1 on:** August 30, 2005, 08:55:48 pm »

which is why on ide drives i use cable select...

E_Look · « **Reply #2 on:** August 30, 2005, 10:13:04 pm »

Interesting, guys. Cable select doesn't always work for some motherboards. What is in the Master position on your IDE cable, Toasty? Sometimes, if I hook a Zip drive or CDROM first, things don't work out. It's best usually to have a HD as master, unless you slave HDD is slave to another HDD.

toasty0 · « **Reply #3 on:** August 31, 2005, 01:06:00 am »

I always run master/slave, master/slave. I never run clable select either.

The article is for those who wish to make their primary OS HDD run from the slave HDD (for whatever reason that I haven't figure out yet)

SkyFlyer · « **Reply #4 on:** August 31, 2005, 03:02:32 am »

Quote

(for whatever reason that I haven't figure out yet)

Simple... Primary os on a small slave HDD.

Applications (games etc) on a large master HDD.

E_Look · « **Reply #5 on:** August 31, 2005, 11:04:40 am »

Sheesh, Sky, you can switch the two HDs around and no mas problemo. Besides, what advantage is there in making the game disk the master? I think the boot disk should be the master and the one holding the OS executables. Even if there is no system halt issue, it ought to be faster!

Bonk · « **Reply #6 on:** August 31, 2005, 11:12:38 am »

I agree, the larger disk should be the primary and hold the OS. Data on secondary disk.

I never did see the point of installing apps to a secondary drive, as when the OS goes from the primary so do all the app dlls and registrations, you have to reinstall the apps anyway. I just keep dumb data on secondary disks or partitons and install apps to the same disk as the OS.

Never did use standby, just don't trust it, so I always jumper my drives as master and slave, seems the logical thing to do. Standby and advanced power management have only caused problems in my experience... spin the hard disks up and leave them up thank you very much! (easier on them in the long haul) Windows has a habit of going to standby when the system is not really idle (still downloading or aquiring data... whcih of course requires a hard disk that is still working...unless working in ram alone...)

E_Look · « **Reply #7 on:** August 31, 2005, 11:25:01 am »

Yeah, but spinning them all the time will wear them down faster, though admittedly, by that time, one is usually into a new computer already...

... in the times I need my home computer at intermittent times, I leave it on and have HD power down kick in after like two hours of nonuse or so. Usually, though, I just shut the system down until I need it again, though the drawback of that is the restarting of the HDs and increased powerspiking to the PSU, shortening the service life of both.

But I have to watch my power costs these days very carefully.

Bonk · « **Reply #8 on:** August 31, 2005, 11:39:41 am »

Quote from: E_Look NCC-9091 on August 31, 2005, 11:25:01 am

Yeah, but spinning them all the time will wear them down faster, though admittedly, by that time, one is usually into a new computer already...

Pretty sure that constant power cycling is much harder on the disks than running them continuously. Hardware MTBF stats often include power cycling conditionals that supercede the actual time in use. This is true for more than just disks in my observations but particulary applies to components with moving parts. (Though it holds for CRT monitors as well)

E_Look · « **Reply #9 on:** August 31, 2005, 02:44:14 pm »

You do have a strong point there... for me it'll be easier in late autumn or winter, as my socket 754 Athlon 64 chip can be used to heat a large city apartment. This summer, wow, I can definitely feel the computer's effect on the room's temperature.

In another room where my kids have their computers, it gets downright hot at times and they're just socket A Athlon XPs!

Bonk · « **Reply #10 on:** August 31, 2005, 02:50:40 pm »

Hehe, I used to use my old Nokia 17" CRT to heat my room in winter. It did a very good job!

NJAntman · « **Reply #11 on:** August 31, 2005, 04:38:55 pm »

Dang, now I'm confused. This could explain why my setup never completes a restart, always turns off instead.

It's hooked up "master" not CS on the newer HDD (wich has the XP OS) and "slave" on the older data HDD (since the older is a WD 60GB with only "Single or Master" / "Master w Slave" / "Slave" settings.

So if I set the the OS containing newer HDD from "Master" to "CS" I should now be able to do a restart all the way through, right?

Unless of course I have a MB that isn't CS happy. How would I see that in the BIOS settings?

Tus-XC · « **Reply #12 on:** September 01, 2005, 11:43:16 am »

the master/slave will always work as long as xp is on the master. I use CS as 1) most hd are defaulted to it on purchase and 2) most modern MBs support it. however i will say that SATA is much better

E_Look · « **Reply #13 on:** September 01, 2005, 04:38:59 pm »

Quote from: Tus on September 01, 2005, 11:43:16 am

... however i will say that SATA is much better

I'll second that! Never mind fast, setup was easy!

prometheus · « **Reply #14 on:** September 07, 2005, 11:13:25 am »

I just lost an HD the other day... I heard that tell tale metallic ping coming from inside the box, thought nothing of it and heard it again and hour later... So I immediately started copying my data like crazy onto other disks, and down it went... thankfully I had the foresight to archive my digital photo collection onto another disk...

News: