Nice… Hopefully the non-AV variants will appear soon.
The conspiracy theorist in me says they might be “squeezing” some extra storage space by repurposing some/all error-check space as data since it’s an AV drive… But of course it’d be a miracle to squeeze an entire 50% more storage out, heh.
ooh ooh - i really want to buy some just to rip the SATA drives out of the box!
hopefully this is a sign of an impending SAT drive release!
Side note: Seagate’s GoFlex is simple, but brilliant, especially for the non-tech-savvy. The NTFS driver for Mac OS is a nice touch too.
@ bhiga mainly but i’m sure others will be tempted, i definitely wouldnt buy a 3tb goflex and chuck it in drobo
its a 5 platter, 7200 rpm drive - 14.3W under load![hr]
and wow, does it get hot:
Thanks for the warning. I’m forbidden to buy any more hard drives for a while so… I’ll be good to go for the 4TB cycle.
haha, my bf just moved in and bought his huge dvd collection, which i am busy ripping so i think i’ll have to buy my 10th 2tb drive now…
Are our Drobos able to understand GPT, and thus use >2TB drives?
i can only assume that since windows/mac sees drobo disks as totally unformatted then they dont use GPT or MBR on their discs, so your questions doesnt really make sense.
Well, my understanding is that the partition that the OS sees is a virtual partion laying on top of all the drives in the Drobo. The virtual machine that resides between the the virtual partition and the actual drives, must rely on some sort of partitioning scheme to put data on them, right?
correct, but however drobo formats those drives, its not MBR or GPT otherwise windows/OSX would be able to recognise the partitioning - even if it only saw them as “unrecognised” (which it can and does do where it can see the partition but cant recognise the format)
it would look something like this if they used MBR or GPT
Intersting. Thank you.
I haven’t yet hooked up and looked at a drive outside of the drobo.
Yup, the filesystem is handled by the connected client’s OS.
Drobo itself is a block-level device so it just treats the disks as a bunch of blocks, unless you’re talking about FS or DroboShare, but in those cases the embedded Linux is the client OS that’s then sharing the disk contents.
Interesting stuff. Thanks for the info.
I knew the file system was handled by the client OS, but I didn’t realize the Drobo’s management was block level. I figured it had it’s own partition structure underneatht eh virtual layer, but I guess a block managed system DOES make more sense now that I think about it