Primocahe: L1
2048GB <--- cool DDR8, get back to the future
1. you really have a hardware-raid or FW-raid chip on your motherboard that just "look" like a hardware raid for a simple mind? ah ok i see it is a hardware controller indeed, sry - but "good", why you want a raid and cache? any realistic use case that needs that hardly? <-- these hint is for the others, chances with software or mobo-raid are nearly zeroed.
2. what do you mean with defer-write of the raid? a raid doesn't defer writes externally as far as i know, everything happens internally, it reports a usual sata-drive externally, but raids are not supported in fance/primo-cache, so that might me the simple cause or the HW-raid FW having some incompatibilities in properly reporting a usual normal drive externally or interpreting usual normal drive commands externally.
(( 3. What do you mean with a "shut" command. "shut down"? or "shut up"?
only a joke ))
The raid controller will try to flush data earlier to hard drive and sent a shut command to the computer.
(( Caution: I have a poo without having anything eaten ....
only a joke ))
((
http://www.youtube.com/watch?v=HQoRXhS7vlU just to get you in the right mood
))
the answer is not a mystery to see here:
In your case to BIOS and OS the truely HW-raid controller should report as a disk without a special disk driver. (C:\Windows\system32\driver\disk.sys)
How is the Raid-controller able to want to flush the data to the disk before primocache passed it on to the controller!?
Anything you write in the OS is intercepted by primocache for defer-write... nothing reaches the controller/disks before that. FIrstly when primocache flushes cache that data is passed on to the raid. So what you say cannot be true! the raid is unable to try to defer anthing to the disks it doesnt even know of. Think about it again! YOu write everything to primocache... no more the raid, and when primocache flushes then firstly the raid is accessed for write.
The more likely is that a systray or service application or simply the special raid-driver of your raid-controller tries to send internal commands... but that drive is "primocache" on top what puts any internal-raid command at high risk, and by that additionally anything the raid-controller sends without a reason to emulate a standard drive to the os, cannot be properly interpreted by the OS because it only listens to "primocache" for that drive... primocache cannot listen or send to propriety third party layers, what the raids-controller sends is invalid for a direct write - it communicates through primocache!!! A non-standard management command lands in the cache for at least 10 seconds, while that management app trys to read that "result" immediately after - which demand is passed on immediately to the raid (1st read) Tadaaa, and thats why romex doesnt support these, because primocache isnt able to provide a layer for any raid out there to directly pass on or receive internal raid-driver that "make up" a standard-drive
A raid-controller must be standalone, by that means flawlessly work with your individual sata-controller driver like any other drive without any special necccessities, in special software-layers, that is the only way a software like "primocache" might work....might, because the programm actually is without any warrant in general... not saying it not working wonderful with many standard-drive. no issue here, less known.
Sad to see such great hardware in hands of - sry to say it - newbies (no offense) that warn people with half knowledge in bold-letters
.
*// Just found these according to the LSI shut downs with cache-solutions:
http://alturl.com/nuzrk - SaxGuy explains it very well *// just for relaxing a bit, bro, you are demanding impossible actually.
PS Im not an employee