Hmm, I had plugged the 240GB SSD into my top docking back on my Rosewill Blackhawk. When I first went into Disk Management, it asked me to initialize it, so I did.
I've had the drive just sitting there, plugged in, for the last few days, doing nothing.
I decided I wanted to benchmark the drive, so I went into Disk Management, and created a volume, with quick-format.
It was five minutes ago, and it still says "formatting". I thought I heard some sort of BIOS-like beep a minute ago though, and I'm not sure why. I'm also getting some strange pauses in my words appearing when I type this in my browser, and I don't have anything intensive going on in the background.
I'm not sure if Windows is TRIMming the entire 240GB during the quick format, or what's going on here, or if the SATA cable that is part of the SATA dock on my case doesn't handle 6Gbit/sec connections.
My internet radio keeps skipping now too.
Edit: I noticed clicking on "Hotswap!" doesn't show my 240GB anymore. Wierd. It's like the system lost connection with it.
Edit: If it won't format, I guess it's toast, right? Darn, brand-new drive too.
Edit: Opened HDTune free edition, started the "Error scan", it's been several minutes, and it still hasn't scanned a block yet.
Edit: So I followed this guide to Secure Erase the drive.
http://mackonsti.wordpress.com/2011/11/22/ssd-secure-erase-ata-command/
Booted to Linux, seemed to complete the commands just fine, and even created a FAT32 filesystem on the drive.
But I left the drive in when booting Windows 7, and then it hung at the "Starting Windows" logo, it just sat there.
So I hit reset, unplugged the drive, and am now booted to Windows 7.
Trying to figure this out. The drive seems to work in Linux, but not 7?
Fiddling with it some more, now it won't even detect in BIOS. Guess it's toast.
Edit: How I figured that out, was that I was going to boot off of a Win7 disc and install to the SSD, in case my current software environment was the problem. But when I went into the BIOS to set the boot order to the 240GB SSD, it was no longer showing up. I had noticed that on some of the prior reboots, it was hanging for a short while on the AHCI BIOS drive-detection screen, waiting for the Mushkin to show up.