Issue 2: Can't resolve "unknown device" for 1 standard SATA drive

[thomnet]

Issue 2: Can't resolve "unknown device" for 1 standard SATA drive

I have a customized Asus M4A875-M system with:

- Phenom quad core 9750 CPU @ 2.4GHz
- 16GB RAM
- BluRay & DVD R/W optical drives (2)
- 500W Antec power supply
- 4 disks:
= drive 0 - Vertex2 80GB SSD 2.5"
= drive 1 - Toshiba 680GB 2.5"
= drive 2 - White Label 1TB 3.5"
= drive 3 - Seagate 1TB ST31000528AS (just upgraded drive firmware to CC49 from CC45)
-Multiboot:
= Windows 7 Ultimate
= OpenSUSE tumbleweed linux
= Linux Mint 17.2
= Windows 10
= Windows 7 Home Premium
= OpenSUSE v12.2

My boot loader is grub2 with a nice custom boot menu using

.

The issue is the Seagate drive is listed as an "unknown device" under Windows 7 Ultimate OS (along with 3 other volumes) despite the fact it works OK when I boot Windows 7 Home Premium. Haven't gotten Windows 10 to boot yet, so don't know about that, but its just fine under all of the Linux OSs too.

I have all of these backed up using Macrium on a 3TB external USB also.

All of the UUIDs for each disk and partition (volume) are unique as reported by gparted under Linux. Having an issue with Windows 10, but I'm saving that for a separate thread.

The Seagate was showing up OK before the FW and RAM update. I may have confused the Win 7 Ultimate OS when I had to remove the CMOS battery to reset mobo, and I forget to switch the SATA ports to AHCI mode. Win 7 Ult. booted up, but many volumes weren't recognized. When I discovered and fixed the mode 4 items shown as "unknown", starting with the Seagate drive explicitly labeled and 3 other drives, presumable the other NTFS partitions on that same drive.

For a map of the partitions on all of the drives see my Issue 3: Can't boot Windows 10 on multiboot system thread.

 

[ComputerGeek]

You still have this problem? Zip the file C:\Windows\inf\setupapi.dev.log and attach to next post

/* EDIT */
And while you're at it... you say it works under your other OS? Why don't you zip and attach the C:\Windows\inf\setupapi.dev.log file under that installation too

 

[thomnet]

I've had a devil of a time with these enhancements.

> The drive with my Windows Home Premium crashed (new drive should arrive this week)
> Weird problem where my USB keyboard and mouse die as Windows boots (fine on all other Op Sys & BIOS setup)
> When I hide updates under Windows Updates they won't stay hidden
> I have 3 "Storage volumes" that show up under unknown devices in Device Manager (may be due to disabling USB 2.0 support)

Before the drive crashed I was able to get the files you asked for. The version for the Ultimate OS I'm using is several days old however, not sure how to update it. When this file was created there may not have been an issue. I notice that the 70GB volume with Windows 10 is listed as a "Recovery partition" for some reason, don't know why.

 

[ComputerGeek]

The issue is the Seagate drive is listed as an "unknown device" under Windows 7 Ultimate OS (along with 3 other volumes) despite the fact it works OK when I boot Windows 7 Home Premium.

1. I was looking for your case of: 'Seagate drive showing up as "unknown". There's no evidence in the logs provided that problem still exists
2. You also said "along with 3 other volumes". What do you mean? Are these volumes on the Seagate? If seagate disk shows as "unknown" then, yes, of course, all volumes on that drive won't appear either

I don't know about your other issues but I'm seeing 3 hard drives detected and installed on under both HomePremium and Ultimate logs you gave me
> a Seagate ST31000528AS 1TB (Disk 0 in your snapshot?)
> a Toshiba MK6465GSXN 640GB (Disk 1?)
> OCZ Vertex 2 SSD (I'd guess is Disk 2)

You can delete the current log files. And if an internal disk shows up as "unknown" again provide the new logfile. Otherwise, sorry, can't answer any of your questions. Reinstalls may be a good idea if things continue to be so flaky