[SOLVED] Old drive shows up in bios, but nowhere else

Dec 27, 2019
1
0
10
0
Howdy all. It finally happened: I hit a snag I couldn't solve myself.

Last night my PC gave me a BSOD with a kernel error. Not entirely unexpected as it's been having problems lately. I rebooted only for it to fail to find boot media. No problem - just a loose SATA cable.

Then the oddness starts. My windows 7 install (yes, I'm a dinosaur - ironically one that was about to swap over to 10 on an SSD for new years!) is now locked in a classpnp.sys loop. Also not a big problem except I don't have windows 7 restoration media or know what happened to my auth key, which makes downloading an iso a little tricky to say the least. So, I decided to soldier on and installed windows 10 clean onto the new SSD, planning to crack into the old HDD and salvage data or resolve the classpnp.sys corruption the old fashioned way. All good there.

Then comes the oddness. The drive doesn't show up in Windows 10. As far as it's concerned, it doesn't exist. I try doing the same thing with an ubuntu flash I have lying around: Same problem. The disk still shows in bios and boots far enough to get locked into its classpnp.sys loop, but won't show for any other system.

Anyone have any thoughts on how to resolve this one? My last backup was a couple of weeks ago.
 

Mr.Spock

Prominent
Dec 8, 2019
549
57
590
40
I've hit that before, in the old days before AHCI, the SATA ports did IDE so that may be causing the hiccup.
So that old system probably had the option to toggle between the two.

Howdy all. It finally happened: I hit a snag I couldn't solve myself.

Last night my PC gave me a BSOD with a kernel error. Not entirely unexpected as it's been having problems lately. I rebooted only for it to fail to find boot media. No problem - just a loose SATA cable.

Then the oddness starts. My windows 7 install (yes, I'm a dinosaur - ironically one that was about to swap over to 10 on an SSD for new years!) is now locked in a classpnp.sys loop. Also not a big problem except I don't have windows 7 restoration media or know what happened to my auth key, which makes downloading an iso a little tricky to say the least. So, I decided to soldier on and installed windows 10 clean onto the new SSD, planning to crack into the old HDD and salvage data or resolve the classpnp.sys corruption the old fashioned way. All good there.

Then comes the oddness. The drive doesn't show up in Windows 10. As far as it's concerned, it doesn't exist. I try doing the same thing with an ubuntu flash I have lying around: Same problem. The disk still shows in bios and boots far enough to get locked into its classpnp.sys loop, but won't show for any other system.

Anyone have any thoughts on how to resolve this one? My last backup was a couple of weeks ago.
 

Mr.Spock

Prominent
Dec 8, 2019
549
57
590
40
I've hit that before, in the old days before AHCI, the SATA ports did IDE so that may be causing the hiccup.
So that old system probably had the option to toggle between the two.

Howdy all. It finally happened: I hit a snag I couldn't solve myself.

Last night my PC gave me a BSOD with a kernel error. Not entirely unexpected as it's been having problems lately. I rebooted only for it to fail to find boot media. No problem - just a loose SATA cable.

Then the oddness starts. My windows 7 install (yes, I'm a dinosaur - ironically one that was about to swap over to 10 on an SSD for new years!) is now locked in a classpnp.sys loop. Also not a big problem except I don't have windows 7 restoration media or know what happened to my auth key, which makes downloading an iso a little tricky to say the least. So, I decided to soldier on and installed windows 10 clean onto the new SSD, planning to crack into the old HDD and salvage data or resolve the classpnp.sys corruption the old fashioned way. All good there.

Then comes the oddness. The drive doesn't show up in Windows 10. As far as it's concerned, it doesn't exist. I try doing the same thing with an ubuntu flash I have lying around: Same problem. The disk still shows in bios and boots far enough to get locked into its classpnp.sys loop, but won't show for any other system.

Anyone have any thoughts on how to resolve this one? My last backup was a couple of weeks ago.
 

ASK THE COMMUNITY

TRENDING THREADS