T60P will not detect SSD in main!?

[gmgfarrand]

Ok,

I am using an OCZ 64GB Core SSD and it will NOT detect in the main HD slot, but if I put it in the ultrabay, it detects it and boots fine.

If I use a "normal" HD it boots from main.

Any ideas?

[AvalonXIII]

Ok,

I am using an OCZ 64GB Core SSD and it will NOT detect in the main HD slot, but if I put it in the ultrabay, it detects it and boots fine.

If I use a "normal" HD it boots from main.

Any ideas?

Have you tried formatting the SSD with NTFS file system yet? Is the drive initialized yet?

[gmgfarrand]

It's been cloned.
It's already NTFS, and it boots in the media bay.

When its in the main bay, it gives an initialization error.

[AvalonXIII]

It's been cloned.
It's already NTFS, and it boots in the media bay.

When its in the main bay, it gives an initialization error.

I think you get initialization error because you haven't initialized the drive yet.
DO this: Put your SSD in the ultrabay, then boot into windows and format it. If the drive doesn't appear in My Computer, then initialize the drive in Disk Management.

[deforest]

When you performed the clone to the ssd, was it in located in the main bay? I understand sometimes if you clone to a drive that is in the media or external bay that sometimes the clone works, but that the drive geometery isn't correct for the main bay, so it will boot off the media or externally, but not of the main bay.

[gmgfarrand]

hmmm...
Nope, the drive was in an external enclosure.

I might have to try it again.

Even though I am not going to do it, putting the drive in the media bay, formatting it, and initializing will NOT change the issue.

[deforest]

I'm trying to understand because you say one the one hand drive isn't recognized, and on the other you get an initialization error

If you go into bios and use the hard drive disk utility, and run that, is the drive recognized and pass the test? If so, then the hard drive as a device is being recognized.

But now if you try to boot, and the drive gives an error, the initialization error, then that is another problem, which I believe is due to the cloning process.

See http://forum.thinkpads.com/viewtopic.php?t=45638, section 11

a. (Note: Why are we swapping the drives BEFORE cloning? Apparently, the IBM motherboard codes data onto its hard drives in a configuation that NO OTHER laptop manufacturer uses. IBM apparently uses a proprietary "240-head" configuration for data on the hard drive, whereas virtually every other PC manufacturer uses 255 heads of data. I don't know the correct terminology, but the drive encoding is somehow proprietary to IBM (wonderful, no?). (I have also read that this sometimes occurs on HP and Compaq laptops, too?!) Thinkpad running Windows XP is using NTFS, but it just somehow configures data in a slightly proprietary way. So...this means that in order to ensure that your cloned drive will work in a Thinkpad, the destination drive must be cloned while plugged into the Thinkpad motherboard itself.)

[obarriel]

I use a low end g.skill 64gb SSD as a main in my T60P without any problem.

[AvalonXIII]

hmmm...
Nope, the drive was in an external enclosure.

I might have to try it again.

Even though I am not going to do it, putting the drive in the media bay, formatting it, and initializing will NOT change the issue.

How do you know that it won't change the issue if you're not going to do it

[gmgfarrand]

Because its a BIOS issue...
It worked fine, then I replaces it with a normal HD, then a few months later installed a "modified" bios to allow me to install a non-IBM WLAN card.
Then the SSD would not work in the MAIN bay.

Wiping the partition/reformatting will not take care of it the issue.

[dsvochak]

Because its a BIOS issue...

It sounds more like a modified BIOS issue.