You now remember SSHD hard disk drives
>>107570651So a regular hd with tons of cache?
>>107570651Can you ssh into them
>>107570651i still have a couple
>>107570651I now remember Intel's horrid attempts at SSD caches for HDDs.
>>107571244Don't they all have a cache? my wd gold 8TB has 256MB cache
>>107571345that's dram
>>107570651>Product warrant is void if [...] drive experiences shock in excess of 350GsIs there any scenario where someone looks at the remains of a drive that went through 350+ Gs and goes "Mhhhhm, yes, I'll ask for a replacement through my warranty"?
>>107571623Knocking two HDDs together with any amount of force is hundreds of GsDrops on hard surfaces are thousands of Gs
this is what I thought SSDs were when I first bought one and PCPartPicker didn't tell me that i was being rarted
>>107571650uh no
>>107571690Gs are acceleration, not how destroyed something is.
>>107571650>whoops I dropped my 1lb hard drive 3ft onto the floor>it lands with a force of 1000g's>i am instantly blinded and deafened by the sound >the shockwave throws me backwards and through the window>it punches straight through the floor >it strikes my downstairs neighbor, instantly killing him>keeps going until it reaches the basement >eventually stops after penetrating three feet of concrete >the rest of the building sways and then collapses >the support columns were all damaged by the initial shockwaveNow we finally know what happened to WTC 7.
>>107570651I bought a couple 500GB 2.5" models as a novelty, I wonder why they never took off.>>107571244Didn't RST require a program to be installed in Windows? It should have been implemented in BIOS.
>>1075729091000gs is the deceleration of the HDD from hitting the floorDoes nobody know what G forces actually are?
>>107572955I'm gonna blast your asshole with 1000g's of force from my cock
They made sense when SSDs were new because a proper SSD was thousands of dollars. You would put your things like apps etc on the ssd part and games on the HDD part. It was pre "everyone has 1TB nvme ssds minimum"
>>107573062nvm I'm mistaken, it was just a cache. I never actually had one I was too poor when they were around and had a traditional hdd
>>107573062>You would put your things like apps etc on the ssd part and games on the HDD part.I've never used a SSHD, but are you sure that's how they worked?I always assumed the OS sees it as a single standard HDD, and the SSD part just existed on the firmware level, being used as a fuckhuge cache.
>>107573082nvm didn't see this before posting >>107573175
>>107573175>>107573062Both existed at a pointWD had a proper HDD+SSD that where separate but required special drivers iircMost "Hybrid" HDDs did just use something like an 8gb/16gb cache.
>>107572955The whole fucking website is being filtered by a basic IQ test capcha. You should lower your expectations.
How did they work? I wasn't dumb enough to buy one of these and try them out.Was the SSD and HDD part exposed to the host as a single drive? Because I know for sure that you'd need SAS to have multiple devices over a single cable and good luck finding a consumer motherboard with a SAS controller.
I stopped buying Seagate after two of these died on me. Meanwhile I still have working 500GB WDs from 15 years ago.
>>107573268It was a fuckhuge cache, like >>107573175 said. At that scale, the controller is most likely to detect most OS files as the most accessed ones, so it would be mostly/entirely Windows/Linux
>>107570651Man I was hype for these, till I found that the WD Velociraptors were still faster than this.
>>107573268It's exactly like modern HDDs are right now with 256MB cache. But that's DRAM. Instead of using DRAM, you're using some of the first generation SSDs with terrible read and write speeds in place. So, sure you'd have a 10GB cache for burst speeds, but it was still pretty slow compared to DRAM burst speeds. The WD Velociraptors ironically were still faster than the SSHDs.
