Drobo systems flag SMR disks as failed within hours of installing them. Drobo specifically say their systems don't support SMR disks, so not knowing the recording method is a real pain.
I've already had three Seagate drives returned to the supplier for a full refund because it was not disclosed they were SMR and they didn't function with the Drobo.
I wouldn't use SMR in ANY raid arrangement. Just not worth it.
So, as a follow-up, it appears all major disk vendors are now using SMR on their higher capacity budget drives with various levels of openness about it.
As far as I know WD are the only ones shipping NAS certified drives with SMR, which is REALLY shady.
Another problem with SMR is that some RAID systems can kill them in a matter of days. Read the fine print of your raid system's supported disks section to see if SMR is supported.
Drobo systems, for example, don't support SMR.
So, for example, recently we purchased three new Seagate 8TB Barracuda drives to add to our Drobo system. Within three days two of the drives had completely failed and the third was flashing up warning lights leading to an urgent purchase of non-Seagate drives to replace it.
Checking with Drobo and SMR drives aren't supported - are these SMR drives? I checked the online support sheet for the drive, no mention of SMR.
I emailed Seagate and they claim they don't even know!
"Thank you for contacting Seagate Support. "Typically"the new Barracuda over 8 TB uses SMR, we do not have access to this kind of information, so I can't confirm this."
But more digging revealed they are SMR.
https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.reddit.com%2Fr%2FDataH...
All three drives were returned to the dealer and a full refund received.
Since then I've been using Toshiba disks without any problems.
Guess I'd have to take the body out first.
Yes, I'm sure there's a public wifi just in reach called "NotMI5Honest" that he could use.
Perhaps it's time for Ecuador to start charging him rent.
The specific issue with the Lytro Illum is that it uses a ~40 megapixel traditional sensor to create an 0.4 megapixel "live" image - so even in the future if we were to get a camera that produced a more usable 8 megapixel live image it would need an 800 megapixels sensor to capture that 'live' data. Now, bear in mind the size of the lytro files would then be the size of the 800 megapixel image.
But it was a bit of a sham. Their '40 megaray' camera had an actual still image equivalent resolution of 0.4 megapixels (which they went to great lengths to hide) - so it was always a toy rather than a serious tool.
that's all!
That is true, but having both, I can assure you it's not the same.
And as for the smudges - strangely enough this happens on the iPad and iPhone and hasn't killed those products
I have to say that as a tablet it completely and utterly sucks. Windows simply does not translate to a tablet environment and, other than emergency use, I never use it without the keyboard.
However, with the keyboard and as a lightweight touchscreen laptop for travel, is is excellent. I use Mac for my desktop environment, but Apple have decided for what seems to be purely religious reasons not to put touch-screens into their laptop line, which for me is a dealbreaker. Using the mouse for 99% of the UI, but the finger on the screen to scroll and pinch-zoom when appropriate works really well for me, and when I'm doing presentations from my Surface Pro onto a projector being able to draw onto the screen with the pen is a major advantage.
I know for many of you a touchscreen in a laptop seems stupid, and you're perfectly entitled to that opinion. For me, it works, and it works better than the alternative (which is why my MacBook Pro is now hardly ever used.)
Perhaps before approving a story with a youtube link someone could actually check to make sure the video is available in a reasonable % of the world outside the USA?
This is unfortunately inevitable - newer OSs will cease supporting older hardware, forcing people to use old, insecure OSs because the newer versions simply can't work on it.
But this is still better (forcing obsolescence) than a world full of old, insecure devices. And these devices will still be useable, just not on a network.
Perhaps all OSs should have a kill date embedded after which they will fail to operate. Maybe nothing as drastic as the machine failing to start, but perhaps for example booting into the equivalent of safe mode with no networking, so that it's possible to move your data from the system but isn't really practical to use it.
Why? Because such a kill date would actually force people to think about upgrading rather just keeping running because they know they can.
It could be as simple to override as putting the clock back for those who want to play with older OSs on old hardware for fun, but that wouldn't be a practical solution for most of the lazy businesses who continue to use obsolete systems and not just put themselves at risk but, by becoming vectors for attacking others, affect us all.
And for at least a year before the kill date is activated the system wallpaper would be replaced with a timer counting down to the time the system needs to be replaced.
Citation:
jolyonr (2017) https://f6ffb3fa-34ce-43c1-939d-77e64deb3c0c.atarimworker.io/comments....
Beware of all enterprises that require new clothes, and not rather a new wearer of clothes. -- Henry David Thoreau
