0

I want to find out what the most noisy component of my computer is, and though it could be the hard drives (since lowering the PWM of the fans and pump only helps a little). So I thought I could just turn off the drives (RAID 1) for a short time and see (hear) if there's a big difference in noise levels.

But it turns out there doesn't seem to be any possibility to turn off the system hard drive, or at least I couldn't find one after a lot of searching. Does anyone know how I could achieve this? Or how I could do something similar at least?

PS: Maybe there exists a program that can delay writes to the system drive by a few minutes (writing them to RAM or such), so that it will spin down automatically?

7
  • If you turn off your system drive the OS kernel would crash. Why don't you boot to a non-mechanical system drive. You can then not mount the system drive on the mechanical drive, thus allowing you to perform your test, if you so desire. A non-mechanical drive makes no noise.
    – Ramhound
    Nov 30, 2015 at 18:14
  • @Ramhound: That's not entirely true – a HDD can still spin down and become quiet while remaining connected to the bus. The "Power" control panel has had a spindown timeout ever since Windows 98. Nov 30, 2015 at 18:15
  • @grawity - The actual system drive though? Sure it can spin down while in low power modes, and non-system drives, can be low powered green devices and be spundown.
    – Ramhound
    Nov 30, 2015 at 18:19
  • @Ramhound: Yes, the actual system drive. (Most people didn't have more than one drive back then. Most laptops still don't.) A system can work from the memory cache for a while – especially if it's just sitting idle at the desktop. And since the drive is still online, it can be spun up on demand again. Nov 30, 2015 at 18:20
  • Maybe a more "physical" solution: amazon.com/…
    – Eddie Dunn
    Nov 30, 2015 at 18:22

1 Answer 1

1

hdparm -y should put a drive in standby mode.

Now HDparm is a tool which is usually shipped with Linux, but there are ports of it for windows.

None of these claim to work with windows 10, though I strongly suspect that the latter one will work. I would love some feedback on that.

3
  • 1
    I just get HDIO_DRIVE_CMD(identify) failed: Function not implemented (or the same with HDIO_GET_IDENTITY), probably because of the RAID (the drives aren't listed in the BIOS SATA list either).
    – Njol
    Nov 30, 2015 at 19:35
  • Ack. I did not consider fake RAID (IRST). I assumed normal software RAID. That leaves only two choices I know off: Disconnect one drive amd boot with a degraded array (assume powering down two drives would cause twice an as big reduction). Or programming the drives themselves to spin down regarless of OS (hdparm -S somelowvaluehere). Though to configure the drives you would need to boot without the RAID else you get the same error with -S as with -y
    – Hennes
    Nov 30, 2015 at 20:00
  • I'm not sure why I didn't think of this earlier, but disabling RAID in the BIOS allowed me to use hdparm to spin the drives down. I bought an SSD in the meantime though so not sure if it would have worked as well if I actually booted from one of those HDDs.
    – Njol
    Feb 7, 2016 at 18:21

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .