Solved Win7 on Adata SSD can't see the D: drive

[loninappleton]

I have an Adata SU650 with Win7 installed. This SSD performs normally as the boot drive. But it cannot see an old WD 320 on D: which I have now tested as recognized but on a different motherboard. That should be of no consequence for a data drive but the old WD320 is likely bootable. I have not tried the WD boot capabilities-- just seeing if it works.

Do SSD's have to be refreshed with the format program? Or might I just run Win7 Repair disk on the WD?


The SSD boot drive is ok except for this issue. I don't want to lose the data on that. What I see on screen is: When the SSD has the WD 320 attached, Win7 begins to start and then freezes at the whirlygig circles while booting.


It looks like this Win7 is trying to find something but cannot. As a data drive, those booting on different motherboard issues should not come up. Or do they? Perhaps if I did the routine where it shows all the startup processes.

I tried the test on more than one old drive I have which have been unused for a while.

 

[Megahertz07]

Is the WD 320 recognized by BIOS?
If you have cloned the WD 320 onto the SSD, you have to set the SSD with the proper ID.
Detach the WD 320, boot from an win 7 installation drive and do a boot repair.
Attach the WD 320, boot from the SSD and look for it on Disk manager and explorer.
On Disk manager see if it has an letter assigned to it.

 

[loninappleton]

Yes Adata is recognized by BIOS.


I will try the bootrec commands as you suggest in the order you show and report back.

 

[Sunnysky]

I have an Adata SU650 with Win7 installed. This SSD performs normally as the boot drive. But it cannot see an old WD 320 on D: which I have now tested as recognized but on a different motherboard. That should be of no consequence for a data drive but the old WD320 is likely bootable. I have not tried the WD boot capabilities-- just seeing if it works.


I tried the test on more than one old drive I have which have been unused for a while.

Does Diskmgnt see anything?


Run> compmgmt.msc {enter}


> storage > disk Management

 

[loninappleton]

Thanks for the tip. I'm not familiar with that command.

I have not done the other bootrec procedure mentioned earlier yet.

To be clear, the Adata can see some HDs or DVD connected last time I had
checked that. It works fine on programs.

To run the compmgmnt is it in Disk management as Go > storage > disk management > compmgmnt

No, I don't see it in that path. That opens window showing HD's attached. Is it run from the high level CMD?

compmgmnt is not searchable. You have be more specific.

And does the questionable D: need to connected? I see this as a problem in getting the D: recognized.

I'm going to try one other thing too: just reinstall a scratch Win7 to see of the HD in question
accepts that as a new install.

 

[Megahertz07]

To open disk manager without opening computer management execute C:\Windows\System32\diskmgmt.msc:

If Bios recognize the WD 320, it should also be under disk manager. Sometimes it does but doesn't have a letter assigned to it.

You can also use diskpart commands
diskpart
List disk
list volume
exit

 

[SIW2]

compmgmnt ???

compmgmt.msc there is no n

others are

diskmgmt.msc

services.msc

 

[loninappleton]

I think I will look for a different way to do this. I'm not getting the point or what is accomplished.
Surely there is an executable _by now_ for Ol' Win7.

 

[loninappleton]

Something is hosed. I am going to mark this as solved from a bad disk.


I ran the repair cd and that did a repair cycle with the usual failed result from that
procedure no matter the problem. the I ran the bootrec commands from the

repair disk.


All that didn't get me anything.


Last and finallY I attempted to run Win7 install to match up with the motherboard.
That stalled out at the Win7 logo screen. A few "throbs" and then it stopped and my

DVD drive went into iactive mode as it would from no CPU activity.


"It's dead , Jim" as Dr. McCoy would have it.


So that goes bacxk on the pile fro the recycle shop. I have no other clues:
why it would partially work but no further is beyond me.


So mark solved.


I will ask afresh if I'm using something from the active pile.


This all started trying to test a Low Level Format program which I've used regularly.
That was the first failed run on the object HD we were calling D: and not the Adata.

 

[loninappleton]

Thanks for that. Once done it presents the screen I've seen many times for doing HD formatting.
I didn't know there was anything to look for in there. And indeed I saw nothing but the drive info as
'healthy' . It looked like the usual hatched NTFS OK HD entry. What was I supposed to see?

The HD has to be malfunctioning with that frozen Win7 screen. The other problem was trying to
perform a Low Level Format using the HDD Guru Low Level Format tool. I had just purchased the
upgrade after long-time use to see the speed improvement. They have a lock on it until the $3.00
was paid. I had used it as freeware for years.