Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsThe LSI 9207-8e is a popular external SAS HBA for connecting JBOD enclosures, but it was designed primarily for reliable host bus adapter operation rather than consumer-style disk power management. In Windows, that often means disk idle timers and spindown requests do not consistently reach individual SATA drives behind the controller, even when the operating system power plan appears to be configured correctly.
The usual fix is not a special “spindown firmware” so much as using the correct IT-mode firmware, matching it with a compatible Windows driver, and avoiding controller or enclosure behavior that masks drive-level power commands. For many users, reflashing the 9207-8e to stable LSI/Broadcom IT firmware and validating with Windows power settings, driver checks, and real disk idle testing is the path that resolves the issue.
As an Amazon Associate I earn from qualifying purchases.
Understanding the LSI 9207-8e and Windows Spindown Problem
The LSI 9207-8e is a PCIe SAS host bus adapter based on the SAS2308 controller. In typical home-lab and storage-server use, it is connected to external SAS expanders, JBOD shelves, or breakout cables that expose individual SATA or SAS disks to Windows. When flashed in IT mode, the card is intended to behave like a transparent HBA rather than a RAID controller, which makes it popular for Storage Spaces, StableBit DrivePool, ZFS-on-Windows experiments, and direct disk management. However, “transparent” does not always mean that every power-management command from Windows reaches the drive exactly as it would on a motherboard SATA port.
The spindown issue usually appears when Windows is configured to turn off hard disks after a set idle period, but disks attached behind the 9207-8e continue spinning indefinitely. In some systems, a few drives may spin down while others do not; in others, Windows reports no obvious error, yet the drives never enter standby. The confusing part is that the same disks may spin down correctly when connected to onboard SATA, while the HBA path prevents or interferes with the standby transition.
#1 Best Overall
- Chipset: LSI SAS2308.
- Firmware (FW) version: P20 (20.00.07.00) IT Mode.
- Interface: 2 * SFF-8087 internal, PCI-e 3.0 x8.
- Package: controller card, full-height bracket, low-profile bracket.
Standard LSI firmware for the 9207-8e was designed primarily for enterprise SAS environments where constant disk availability is favored over aggressive desktop-style power saving. As a result, the controller firmware and Windows driver stack may not reliably pass ATA standby, idle, or power condition commands through to SATA disks, especially when those disks are reached through SAS-to-SATA translation or an expander. The operating system can request spindown, but the command may be filtered, translated inconsistently, or overridden by periodic activity from the controller, driver, enclosure services, SMART polling, or other monitoring tools.
Common symptoms in Windows
- Windows power plan is set to turn off hard disks, but HBA-attached drives stay spinning.
- Drives spin down on motherboard SATA ports but not when connected to the LSI 9207-8e.
- SMART tools can read drive health, yet standby commands fail or immediately wake the disk.
- Event Viewer shows no clear storage error even though the power setting is ignored.
- External SAS shelves show constant activity or periodic polling that prevents idle time.
The solved path in this class of problem is generally not a special “Windows spindown firmware” made specifically for desktop power saving. The successful configuration is normally a properly cross-flashed or reflashed IT-mode firmware package for the SAS2308 controller, combined with a compatible Windows driver and reduced background polling. IT mode removes RAID abstraction and gives Windows the best chance of addressing each physical disk directly. IR mode, vendor-customized firmware, or mismatched firmware and driver combinations can add another layer that makes standby behavior less predictable.
Even with correct IT-mode firmware, Windows disk spindown depends on the full path: the Microsoft or Broadcom/LSI driver, the HBA firmware revision, the enclosure or expander, the disk model, and any software that touches the disks. Backup agents, SMART dashboards, indexing, antivirus scans, Storage Spaces maintenance, and temperature polling can reset the idle timer before the disk ever reaches standby. For validation, the useful test is not just checking the Windows power-plan setting; it is confirming that a standby command reaches the target disk, that the drive reports a standby state afterward, and that it remains asleep until intentionally accessed.
Recommended Free Tools
IT Mode vs IR Mode Firmware Behavior
The LSI 9207-8e is based on the SAS2308 controller, and it is normally used as a host bus adapter rather than as a hardware RAID card. The firmware personality matters because Windows does not talk to the attached disks in quite the same way under each mode. In IT mode, the card presents physical drives more directly to the operating system, which is the preferred setup for Storage Spaces, DrivePool, ZFS-on-Windows experiments, SnapRAID, StableBit Scanner, and other software-managed storage layouts. In IR mode, the controller adds RAID-oriented behavior between Windows and the disks, even if the drives are configured as single-disk volumes or simple pass-through targets.
For disk spindown, that distinction is critical. Windows power management generally relies on the storage stack being able to send idle, standby, and related ATA/SCSI translation commands down to the drive. With an HBA in IT mode, those commands have a better chance of reaching the disk because the firmware is not trying to manage virtual disks, RAID metadata, or controller-level policy. With IR firmware, the controller may abstract the drive behind a al device. That abstraction can block, alter, or ignore some power-management commands, especially when the driver and firmware decide that the disk should remain ready for array availability or command responsiveness.
How the two modes usually differ
| Firmware mode | How disks are exposed | Effect on Windows spindown |
|---|---|---|
| IT mode | Physical disks are exposed with minimal controller intervention | Best chance for standby and idle commands to pass through |
| IR mode | Disks may be handled as RAID-capable or logical devices | Power commands are more likely to be filtered or ignored |
The firmware path that most consistently solves the 9207-8e spindown problem is to run the card in pure IT mode, typically using the LSI/Broadcom SAS2308 IT firmware branch, with no RAID BIOS features required unless the machine must boot from a device behind the card. Many users choose the later P20 IT firmware package for the SAS2308 family, while also pairing it with a Windows driver that behaves well with pass-through commands. The firmware alone is not always the entire fix, but IR-to-IT conversion removes the largest source of command interception.
A clean IT-mode configuration also means avoiding controller-created arrays, foreign RAID metadata, and mixed-mode configurations left over from previous use. If the card was bought second-hand, it may have vendor-branded firmware from Dell, IBM, HP, Fujitsu, or another OEM. Those builds can work well for normal disk access but still behave differently around power management. Reflashing to a standard LSI SAS2308 IT image, then confirming the controller reports itself as an HBA rather than a RAID adapter, is the usual baseline before troubleshooting Windows settings.
- Use IT firmware when the goal is direct disk visibility and Windows-controlled idle timers.
- Avoid IR firmware when relying on Windows to spin down individual disks in an external SAS enclosure.
- Remove old RAID metadata from disks if they were previously attached to a RAID controller.
- Check the driver stack after flashing, since Windows may keep using an older LSI or inbox driver.
In the solved configuration, the practical change was not finding a special “spindown firmware” for the 9207-8e, but moving to the right operating mode: standard SAS2308 IT-mode firmware, matched with a Windows driver and power plan that allow standby commands to reach the drives. Once the controller stopped presenting storage through the IR layer, Windows disk idle timers and manual standby tests became meaningful, and the attached drives could be validated individually rather than treated as controller-managed RAID members.
Firmware Versions Known to Work Best
For the LSI 9207-8e, the firmware path that most consistently resolves Windows disk spindown pass-through issues is plain LSI/Broadcom IT-mode firmware, not vendor-customized RAID firmware and not IR mode. The 9207-8e is based on the SAS2308 controller, and the commonly successful target is the final mature SAS2308 IT package, usually referred to as P20 IT firmware. In practical terms, that means firmware in the 20.00.07.00 family, paired with a matching or compatible Windows driver.
Rank #2
- 8 internal 6 Gb/s SATA + SAS ports
- Low-profile form-factor design
- Supports up to 256 SAS or SATA end devices
- Supports SSDs, HDDs, and tape devices
- Fusion-Mpt 2.0 Architecture Can Achieve More Than 700,000 I/Os Per Second
The reason this version is commonly preferred is not that it adds a special Windows “spindown feature,” but that it presents disks as direct-attached SCSI devices with the least controller-side policy interference. Earlier releases may work, but they have more variation in enclosure behavior, SATA translation, and standby command handling. OEM firmware from Dell, IBM/Lenovo, HP, Fujitsu, or other rebadged cards can also behave differently because it may include board-specific defaults, RAID-oriented settings, or altered identification strings that affect which Windows driver binds to the adapter.
Recommended firmware/configuration target
- Controller: LSI SAS9207-8e / SAS2308-based HBA.
- Mode: IT mode, not IR mode.
- Firmware branch: P20 IT, preferably 20.00.07.00.
- BIOS/UEFI ROM: optional; omit it if the card is not used for booting.
- Driver pairing: use a stable LSI/Broadcom storport driver or the Windows inbox driver if it behaves better on that system.
In the solved configuration, reflashing the adapter to standard LSI P20 IT firmware was the decisive change. Once the card was no longer running RAID-style firmware or OEM-customized firmware, Windows power management and tools capable of sending SCSI START STOP UNIT or ATA standby-equivalent commands had a clear pass-through path to the drives. This allowed the operating system or disk utility to request standby without the HBA immediately masking, rejecting, or reversing the command.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →There are still limits. Even with P20 IT firmware, spindown is not guaranteed in every enclosure. SAS expanders, USB-to-SAS bridges, disk shelves, SATA interposers, and some backplanes can block or reinterpret power-management commands. Some enterprise disks also ignore ordinary standby timers, while others wake quickly because Windows, antivirus software, SMART polling, indexing, Storage Spaces, or monitoring tools touch the volume. The firmware only removes a major controller-side obstacle; it does not force every downstream device to honor standby.
| Firmware/configuration | Expected spindown behavior in Windows |
|---|---|
| LSI P20 IT firmware, non-boot HBA, direct disks | Best chance of reliable pass-through and idle standby behavior |
| Older LSI IT firmware | May work, but behavior can vary by driver, disk, and enclosure |
| IR firmware | Less suitable because the controller may manage disks through RAID-oriented abstraction |
| OEM-customized firmware | Unpredictable; may bind different drivers or apply vendor-specific defaults |
After moving to P20 IT firmware, validation should be done from Windows rather than assumed from the flash result. Confirm that Device Manager shows the expected LSI/Broadcom SAS2308 HBA, check the loaded driver version, set a short disk idle timeout, and use a tool that can report whether each physical disk reaches standby. Then watch for unwanted wakeups from SMART polling, Explorer access, backup agents, or enclosure management. If the disks spin down only after the firmware change and remain down when the system is idle, the firmware and driver path is working as intended.
Windows Drivers, Power Settings, and Pass-Through Commands
After the LSI 9207-8e is running IT-mode firmware, the next barrier is Windows itself. The controller may expose each attached SAS or SATA disk as an individual device, but Windows still depends on the miniport driver to carry storage commands from the operating system down to the drive. Disk idle timers, standby requests, SMART queries, and START STOP UNIT commands all have to survive that path. With some LSI/Broadcom driver combinations, normal reads and writes work perfectly while power-management commands are ignored, translated inconsistently, or never sent to the physical disk.
For many 9207-8e installations, the most reliable path has been to use IT-mode firmware together with the Microsoft in-box driver or a known stable LSI/Broadcom storport driver rather than mixing old firmware with a much newer driver package. The card commonly appears in Device Manager as an LSI or Avago SAS2308-based HBA. If the driver stack is mismatched, Windows may show all disks correctly but fail to honor configured idle timeouts. In practice, solving spindown often means treating firmware and driver as a pair: flash the HBA to a clean IT-mode release known to behave well, then test both the Microsoft driver and the vendor driver instead of assuming the newest package is always better.
Windows settings that affect standby
The relevant Windows setting is found under Power Options, in the advanced settings for the active power plan: Hard disk > Turn off hard disk after. Set a short interval for testing, such as 5 or 10 minutes, and make sure the machine is not running a workload that continuously touches the disks. Indexing, antivirus scans, SMART polling tools, media libraries, backup agents, and storage dashboards can all reset the idle timer. A disk that never reaches the Windows idle threshold will not be asked to enter standby, even if the HBA and firmware are capable of passing the command.
- Use an IT-mode HBA firmware rather than RAID/IR mode for direct disk exposure.
- Check Device Manager for the active SAS controller driver and version.
- Test the Microsoft in-box driver if the vendor driver does not allow standby.
- Disable or lengthen polling intervals in SMART and monitoring utilities during testing.
- Set a short Windows hard-disk idle timeout only while validating behavior.
The actual command path matters. Windows can request a disk standby state through its storage stack, and tools such as smartctl or vendor utilities can issue direct commands for testing. On a properly behaving 9207-8e in IT mode, the HBA should allow commands such as disk standby, wake, identify, and SMART reads to reach the target drive. If SMART works but standby does not, that points toward a power-management handling issue rather than a general pass-through failure. If neither SMART nor standby reaches the disk, the problem is more likely the driver, cabling topology, expander behavior, or the way the device is being presented to Windows.
Validation should be done with observation rather than assumptions. After changing firmware or drivers, reboot, confirm the controller and disks are detected cleanly, set the Windows disk idle timeout, then leave the system untouched. A spun-down disk will usually show a delayed first access while it spins back up, and some drives expose their power state through SMART data. Event Viewer, Resource Monitor, and tools such as Process Monitor can help identify background processes that keep opening the volume. In the solved configuration, the working combination was not a special Windows-only firmware that added spindown support, but a clean IT-mode firmware path with a compatible Windows driver and a power plan that allowed the disks to become idle long enough for standby commands to be passed through.
Rank #3
Flashing or Reflashing the LSI 9207-8e Safely
For the LSI 9207-8e, the firmware path that most consistently resolves Windows spindown pass-through issues is a clean flash to LSI/Broadcom SAS2308 IT-mode firmware, typically the P20 package, paired with the matching Windows driver. The card should appear as a simple SAS HBA, not as a RAID controller. This is the configuration that gives Windows and disk utilities the best chance of sending standby, idle, and inquiry commands directly to the attached SATA or SAS disks without IR firmware intercepting or abstracting them.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Before flashing, record the card’s SAS address. It is usually printed on a sticker on the adapter and can also be read with the flashing utility before erasing the card. Losing this address can cause duplicate SAS identifiers or discovery problems, especially in systems with mulle HBAs or expanders. Also disconnect data disks during the flash if practical. The firmware operation targets the controller, but removing storage from the equation reduces the chance of selecting the wrong device or interrupting active I/O.
Safe flashing checklist
- Confirm the chipset: the LSI 9207-8e is based on the SAS2308 controller, so use SAS2308 firmware, not SAS2008 or SAS3008 packages.
- Use IT-mode firmware: select the 9207-8e IT firmware image, commonly named similar to 9207-8e.bin, from the correct Broadcom/LSI P20 package.
- Use the right utility: use sas2flash for SAS2308 cards. On some systems, the UEFI version works more reliably than the DOS version.
- Save the SAS address: write it down before erasing the controller firmware or NVRAM.
- Flash the BIOS only if needed: the option ROM is not required for Windows data disks unless booting from drives behind the HBA.
- Reboot after flashing: power-cycle the system fully so the controller initializes with the new firmware.
A typical reflash sequence is to first list the adapters, verify the controller is the expected SAS2308 card, erase the existing firmware region, flash the IT firmware image, and then restore or confirm the SAS address. If the card already has a working IT firmware but spindown still fails, a full erase and reflash can still help by removing older NVRAM settings or vendor-customized firmware remnants. Cross-flashed OEM cards, such as Dell or IBM variants, may need extra care because their subsystem IDs and existing firmware layouts can differ from a retail LSI 9207-8e.
After the flash, Windows Device Manager should no longer present the controller as a RAID device. It should load an LSI/Broadcom SAS2 HBA driver, often under a name such as LSI Adapter, SAS2 2308 Mustang or a similar SAS2 controller entry. At that point, install or select a stable driver version known to behave well with your Windows release. Newer is not always better for power behavior; the goal is consistent pass-through, reliable disk enumeration, and no periodic polling that immediately wakes disks after they enter standby.
Once the controller is reflashed, reconnect the disks and validate one enclosure or drive group at a time. Check that each disk exposes its real model and serial number in Windows tools, then test standby with a utility that can send ATA standby commands through the HBA. Also set a Windows disk idle timeout and watch whether the disks remain spun down for more than a few seconds. If the drives immediately wake, the remaining cause is often software polling, enclosure behavior, SMART monitoring intervals, or a driver mismatch rather than the 9207-8e firmware itself.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Verifying Disk Spindown After the Firmware Change
After reflashing the LSI 9207-8e to a known-good IT-mode firmware, the remaining task is to confirm that Windows can actually idle the attached disks and that the HBA is no longer blocking or constantly resetting the power-management state. The most useful test is not whether Windows shows the drives, but whether each physical disk behind the SAS2308 controller enters standby after the configured idle timeout and wakes cleanly when accessed.
Begin by confirming that the card is running the expected firmware and driver combination. In Device Manager, the controller should appear as an LSI/Broadcom SAS2 HBA rather than a RAID adapter, with no virtual disks exposed by the controller. Tools such as sas2flash can confirm the firmware package and mode, while Windows Device Manager can confirm the loaded driver version. A working setup is typically an IT-mode P20 firmware path paired with a stable Windows LSI/Broadcom SAS2 driver, rather than an IR-mode firmware or a generic storage stack that hides too much device behavior.
Next, configure a short test timeout in Windows. Open Control Panel → Power Options → Change plan settings → Change advanced power settings, then set Hard disk → Turn off hard disk after to a low value such as 3 to 5 minutes for testing. Avoid running indexing, backup, SMART polling, media scanning, or monitoring tools during the first validation pass, because even a small read request can wake a disk or prevent it from sleeping. If you use StableBit Scanner, Hard Disk Sentinel, smartmontools, storage dashboards, or enclosure monitoring utilities, temporarily disable background polling.
Practical validation steps
- Reboot after the firmware and driver change so the HBA, disks, and Windows storage stack start from a clean state.
- Confirm all attached drives are visible in Disk Management and that no rescan, rebuild, or filesystem check is running.
- Set the Windows disk idle timeout to a short interval for testing.
- Leave the system completely idle for longer than the configured timeout.
- Check whether the disks have spun down by listening for motor noise reduction, observing enclosure LEDs if supported, or using a tool that can query standby state without waking the drive.
- Access a folder or run a directory listing on the target disk and confirm that the drive spins up again without errors, disconnects, or controller resets.
For a more precise check, use a utility capable of issuing an ATA or SCSI standby query through the HBA. Some SMART tools wake disks simply by querying them, so results can be misleading. The best validation is a combination of idle behavior, event logs, and controlled wake testing. In Event Viewer → Windows Logs → System, look for disk, storport, or LSI_SAS2 warnings during spin down and wake up. A successful configuration should not produce surprise removals, bus resets, timeout errors, or repeated device reinitialization messages.
Rank #4
- Designed for LSI 9207 & 9300-8i compatibility; built with SAS3008 controller. Operates in IT Mode to enable direct disk passthrough functionality.
- Firmware: IT Mode (Non-RAID). Supports transfer speeds up to 12Gb/s for SAS and 6Gb/s for SATA. Ideal for JBOD setups and software-managed storage.
- Equipped with PCIe 3.0 x8 interface and dual SFF-8643 internal ports. Supports up to 8 drives directly, with expansion capability via SAS expanders.
- Suitable for ZFS, TrueNAS, FreeNAS, unRAID, Proxmox, ESXi, and NAS environments. Ideal for home labs, server builds, and disk passthrough applications.
- Package includes 1 HBA card and 2 SFF-8643 to SFF-8482 SAS cables. Included cables support SAS drives only. SATA drives require separate SFF-8643 to SATA breakout cables.
If the disks still do not sleep, test with only one directly attached drive and no expander or enclosure services in the path. SAS expanders, USB-to-SAS bridges, enclosure management, and aggressive SMART polling can all change the result. Also verify that the drives themselves support standby and that their own firmware does not ignore idle timers. Once a single bare drive spins down correctly, add the enclosure, expander, and monitoring software back one at a time. The solved path is usually confirmed when the 9207-8e is on IT-mode firmware, Windows is using a compatible SAS2 driver, power settings are enabled, and no background process keeps touching the disks.
Frequently Asked Questions
Can the LSI 9207-8e pass Windows disk spindown commands to attached drives?
It can, but not reliably with every firmware and driver combination. The LSI 9207-8e is based on the SAS2308 chipset, and standard firmware often keeps disks visible as SAS/SCSI devices rather than exposing full ATA power-management behavior to Windows. The working path is usually IT-mode firmware with a compatible Windows driver and power settings that allow idle disks to be spun down.
Should I use IT mode or IR mode firmware if I want disk spindown in Windows?
Use IT mode. IR mode adds RAID-layer behavior that can interfere with direct pass-through of disk commands, including ATA power-management commands used for standby and spindown. IT mode presents the controller as a host bus adapter and gives Windows and storage tools the best chance of sending commands directly to each drive.
Which firmware version is best for the LSI 9207-8e spindown issue?
The commonly successful configuration is LSI/Broadcom SAS2308 IT-mode firmware, typically from the P20 firmware family, flashed cleanly without RAID BIOS if boot support is not needed. Some users find that reflashing from OEM or IR firmware to clean LSI IT firmware resolves inconsistent standby behavior. The exact result can still depend on the enclosure, expander, drive model, and Windows driver version.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Do I also need to change the Windows driver or power settings?
Yes, firmware alone may not be enough. Use a stable LSI/Broadcom-compatible Windows driver for the SAS2308 controller, then confirm that the Windows power plan has “Turn off hard disk after” set to a realistic idle time. Also check that background services, SMART polling tools, indexing, backup software, or monitoring utilities are not waking the disks immediately after they enter standby.
How can I confirm that spindown is actually working after reflashing?
Set a short disk idle timeout in Windows, stop any software that frequently polls the disks, and wait longer than the configured timeout. Then check drive state with a tool that can query standby status without waking the disk, or listen and watch enclosure activity LEDs carefully. A real validation should include confirming that the disks spin back up only when accessed, not every few minutes due to polling or controller activity.
Bottom Line
Standard LSI 9207-8e IT-mode firmware is excellent for direct disk access, but it does not reliably translate or honor Windows idle spindown behavior on every drive/enclosure combination. In many cases, the limiting factor is the LSI/Broadcom driver and SAS HBA power-management model rather than a simple firmware switch.
The practical fix was to use the right IT-mode firmware and driver combination, then validate spindown from Windows with tools such as Power Options, Event Viewer, SMART/drive state checks, and real idle testing. If spindown still does not pass through, the next step is to test alternate approved driver versions, confirm enclosure/expander behavior, or use a controller/enclosure path known to expose disk power management correctly.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
