SSD Caching problems

[ubersonic]

RE your second pic, "volume_0000" is the only one showing as enabled/normal status/bootable/etc yet it shouldn't exist as its the left over space on the SSD but the RAID controller seems to be identifying it as part of a phantom stripe (RAID 0) array.

Is it possible to delete the RAID volume "volume_0000" without deleting the volumes "volume_0001" (the cache volume) or "RAID0" (the actual stripe) as that may be what's confusing the controller.

Any idea if you have the latest firmware for the SSD?

------

Didn't notice the last post, not sure what to suggest to that, you could try temporarily booting your system without the over clock as that can sometimes cause issues with software RAID, if you put the cache drive back in and have it as a normal disk instead of part of the array you could install Windows on that and then the Intel software which would presumably be able to error check the array.

 

[Sin_Chase]

Well that went well. All working lovely last night.

Woke up this morning to find a bunch of application exception errors for everything that was running in the background overlaying my lock screen. Entered my password and BSOD.

Windows now wont start, at all. Startup Repair doesnt fix it. I've removed the cache drive and disabled it in the Intel BIOS all to no avail.

Guess I'll whack a post up in the Windows forum..

What happens when you boot? BSOD (7b?), nothing at all?

If it's a 7B BSOD (INACCESIBLE BOOT DEVICE) I would boot your system in a bootable environment...BartPE for example.

You then want to load YOUR systems registry hive for editing.

Open a Registry Editor in the bootable environment. If it's the windows one you need to select HKEY_LOCAL_MACHINE so it is highlighted and do File > Load Hive...

Browse to your local C: drive (Not the bootable environment) Windows\System32\Config\

Select the file named SYSTEM and load it.

Assuming it loaded you will get a new expandable section in the tree view on the left for your systems registry hive.

Browse to the following 3 locations and change the 'Start' parameter value to 0 for each

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\msahci
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\iAStor
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\iAStorv
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\pciide

Left click your newly added SYSTEM hive in the tree view and do File > Unload Hive. If it asks if you want to commit any cyhanges or words to that effect say yes.

Exit Bootable Environment, try to boot.

Basically this tells Windows to load drivers for RAID, AHCI and IDE. It might get you in.

 

[Yamahahahahaha]

i wonder if theres a problem with the drive itself?

Not unheard of with SF-2281 based drives...
Is the firmware up to date?

Also what ubersonic said is sensible, avoid any overclocks until it's stable. When it breaks with an overclock, you'll know what the problem is.