I have just *mostly* finished a system rebuild and while going through and checking to be sure that TRIM was working on my second SSD, I found out that it is not. TRIM is working fine on the primary SSD. I then prepared to do (yet another) backup of the system onto the standard HD on the system in preparation for some playing around with configurations, etc., and noticed that the second SSD isn't being included in the backup set.
I had LOTS of fun with this system getting the SSD's to read, and resolving all the weird driver issues, and now I'm sitting here stuck with no clue what to do. At this point if I simply yank the second SSD out of the machine I think everything will be working perfectly. But I’d rather not do that, because that would be giving up. LOL.
System Info follows:
[EDIT] [Windows 7 Ultimate]
Mainboard: ASROCK Z68 Extreme 4 / 8GB / i7-2700 @3.5GHz
SSDs are both Kingston Hyper X 3K 120GB models - The drives are NOT configured in RAID. I have one I use for the operating system, and another I will use for games. Both are configured to allow Windows to use them for virtual memory.
Standard HD is a 2TB Seagate something or another that used to be my main drive.
The SSD's are located in SATA3 0 and SATA3 1 ports. The front case I/O panel, HD, and a DVD burner are on three of the other [EDIT] [NON-Marvell] SATA ports.
BIOS is the most updated BIOS available from ASROCK.
System Drivers are up to date per DriverNavigator with the exception of some strange Matrox PCI driver which cannot possibly have anything to do with my machine, as the GPU is a GTX560. Intel Smart Connect and Intel Display Audio drivers are not loaded into the machine at all, and are disabled in BIOS.
Kingston website provided tools detect both drives fine. The operating system detects them fine for reading and writing.
Nothing on this machine is overclocked. It’s all factory spec. CPU, RAM, GPU. Air cooled. Power is from an 850W Thermaltake that is roughly 1 year old. System is fed by a voltage regulating UPS, which is in turn protected by a high capacity surge suppressor with power conditioning.
As I mentioned above I thought all was well, but decided that just detecting if the TRIM service was running wasn't enough, I wanted to TEST it. So I did, using TRIMcheck. The SATA3 0 acting as the boot drive tests perfectly. The SATA3 1 supplemental drive will not TRIM at all. I have even gone as far as rebooting, and just checked again after roughly 1 hour total time has passed, about 50 minutes of which was uptime on the machine, and it still has not trimmed the drive.
Everything is talking. The Device Manager seems relatively content.
The only thing that pops into my head as a possibility is formatting? I did reformat both of the drives at one point to recover from a lovely blunder involving the wrong drivers for ASROCK mainboard hardware. Then when reinstalling the OS, after yet another driver issue (I'm NOT a fan of Asrock's driver documentation for this mobo) I am confident that Windows reformatted the C: drive again.
So before going into deep dive land, can someone verify if the format of an SSD can impact its ability to be trimmed, while not impacting its ability to read/write? Are some formats not supported by Windows Backup for SSD’s?
As I click to activate this post, I am starting yet another backup, in preparation for whatever mad !science! is proposed here.
[EDIT] [Changed post type from discussion to question]
[EDIT] [Performed a chkdsk / reboot and checked event viewer logs. Both drives are NTFS 4096, and neither drive generated errors during the chkdsk, so it doesn't seem to be a format-related issue? At this point I'm completely confused.]
[EDIT] [Noticed that all three of my hard drives are being picked up as USB devices that can be removed. I dug into that a bit in Google, and it seems to be considered a cosmetic issue by most responders, but could it be related?] If the drives are all being seen on the USB bus, maybe only one of the drives gets the TRIM commands from the operating system?]
[EDIT] [Fixed the weird USB borked recognition issue by defining the SATA ports 0-5 on my machine as non-removable media in the registry. No change to TRIM function on either drive. C: still trims fine. E: fails to trim.]
I had LOTS of fun with this system getting the SSD's to read, and resolving all the weird driver issues, and now I'm sitting here stuck with no clue what to do. At this point if I simply yank the second SSD out of the machine I think everything will be working perfectly. But I’d rather not do that, because that would be giving up. LOL.
System Info follows:
[EDIT] [Windows 7 Ultimate]
Mainboard: ASROCK Z68 Extreme 4 / 8GB / i7-2700 @3.5GHz
SSDs are both Kingston Hyper X 3K 120GB models - The drives are NOT configured in RAID. I have one I use for the operating system, and another I will use for games. Both are configured to allow Windows to use them for virtual memory.
Standard HD is a 2TB Seagate something or another that used to be my main drive.
The SSD's are located in SATA3 0 and SATA3 1 ports. The front case I/O panel, HD, and a DVD burner are on three of the other [EDIT] [NON-Marvell] SATA ports.
BIOS is the most updated BIOS available from ASROCK.
System Drivers are up to date per DriverNavigator with the exception of some strange Matrox PCI driver which cannot possibly have anything to do with my machine, as the GPU is a GTX560. Intel Smart Connect and Intel Display Audio drivers are not loaded into the machine at all, and are disabled in BIOS.
Kingston website provided tools detect both drives fine. The operating system detects them fine for reading and writing.
Nothing on this machine is overclocked. It’s all factory spec. CPU, RAM, GPU. Air cooled. Power is from an 850W Thermaltake that is roughly 1 year old. System is fed by a voltage regulating UPS, which is in turn protected by a high capacity surge suppressor with power conditioning.
As I mentioned above I thought all was well, but decided that just detecting if the TRIM service was running wasn't enough, I wanted to TEST it. So I did, using TRIMcheck. The SATA3 0 acting as the boot drive tests perfectly. The SATA3 1 supplemental drive will not TRIM at all. I have even gone as far as rebooting, and just checked again after roughly 1 hour total time has passed, about 50 minutes of which was uptime on the machine, and it still has not trimmed the drive.
Everything is talking. The Device Manager seems relatively content.
The only thing that pops into my head as a possibility is formatting? I did reformat both of the drives at one point to recover from a lovely blunder involving the wrong drivers for ASROCK mainboard hardware. Then when reinstalling the OS, after yet another driver issue (I'm NOT a fan of Asrock's driver documentation for this mobo) I am confident that Windows reformatted the C: drive again.
So before going into deep dive land, can someone verify if the format of an SSD can impact its ability to be trimmed, while not impacting its ability to read/write? Are some formats not supported by Windows Backup for SSD’s?
As I click to activate this post, I am starting yet another backup, in preparation for whatever mad !science! is proposed here.
[EDIT] [Changed post type from discussion to question]
[EDIT] [Performed a chkdsk / reboot and checked event viewer logs. Both drives are NTFS 4096, and neither drive generated errors during the chkdsk, so it doesn't seem to be a format-related issue? At this point I'm completely confused.]
[EDIT] [Noticed that all three of my hard drives are being picked up as USB devices that can be removed. I dug into that a bit in Google, and it seems to be considered a cosmetic issue by most responders, but could it be related?] If the drives are all being seen on the USB bus, maybe only one of the drives gets the TRIM commands from the operating system?]
[EDIT] [Fixed the weird USB borked recognition issue by defining the SATA ports 0-5 on my machine as non-removable media in the registry. No change to TRIM function on either drive. C: still trims fine. E: fails to trim.]
Facebook
Twitter
Instagram