Windows – Hard drive recognized in BIOS, but not device/disk management

device managerhard drivewindows 7

I installed windows 7 x64 a day or two ago, after install I could use the HDD fine. Today I noticed it wasn't showing up in my computer, so I restarted my computer, but it still was not showing, I checked disk management, only my main OS drive there, checked Device manager, only my main drive is shown, but when I checked by BIOS both were shown.

I scanned for hardware changes, it showed up but as I tried to access it, it would "load" for a few minutes then I would get an error

"J:\ is not accessible. The specified network resource or device is no longer available."

I tried running a CHKDSK, but it just returned an error saying

"Cannot open volume for direct access."

I've tried Googling, but haven't found anyone with the same problem. Please, does anyone know how I can fix this?

P.S It worked fine in Vista x64

EDIT: I went back into the BIOS and the BIOS only recognizes it when i set SATA 1-4 to ACPI, but when I do these I can't boot into windows because I get an error "NTLDR is missing." I can only boot when all SATA ports are set to IDE.

Best Answer

If it reports in the BIOS, but not in the OS, it's likely that the driver being used by the OS is not compatible with the drive. It's possible that one drive is compatible with AHCI and the other with legacy IDE. When you enalbe AHCI, windows ignores the IDE drive (prob your boot drive), you are essentially trying to boot form your '2nd' drive (no os/boot loader). When you enable IDE, you can boot from the IDE drive, but Windows will ignore the AHCI drive.

Go to the m-board or PC manufacturer and see if there is an updated chipset or hard drive controller driver specifically for Win7x64. Also install firmware updates for the board.

Lastly, if you want to quickly see if you can mount the drive, bypassing the mboard controller, get a usb connector (external drive enclosure) for your 2nd drive. Boot to win7, attach your the drive via usb, and if the drive is good, the virtual usb drive controller should recognize it.

Related Question