data loss
Latest
An enterprise SSD flaw will brick hardware after exactly 40,000 hours
Hewlett Packard Enterprise (HPE) has warned that certain SSD drives could fail catastrophically if buyers don't take action soon. Due to a firmware bug, the products in question will be bricked exactly 40,000 hours (four years, 206 days and 16 hours) after the SSD has entered service. "After the SSD failure occurs, neither the SSD nor the data can be recovered," the company warned in a customer service bulletin.
US Court: Code isn't property, therefore it can't be stolen
New York's Second Circuit Court of Appeals has decided that computer code cannot be stolen after acquitting former Goldman Sachs programmer Sergey Aleynikov. He'd been charged with property theft and economic espionage which carried an eight year prison sentence, but left court a free man after serving just a year of his term. The case hinged upon the definition of both property and economic espionage, and the court found that code, being an intangible, couldn't be property that's capable of being stolen within the definition of the statute -- affirming a state of affairs that's been in place since the British case of Oxford v Moss from 1979. Just as a warning: the Judges advised Congress to amend the relevant legislation in order to prevent thefts of this nature in the future, so we'd hold back on any big data-heists you've got planned.
iPhoto '11 updated, still not up to par
It's a shame -- iPhoto is likely the most heavily used of all the iLife applications. There are simply more people taking digital pictures than there are using GarageBand or iMovie. iWeb, left languishing by Apple with few updates and no new features, has probably forced people to look elsewhere for quick and easy web publishing. iDVD appears to be on life support too, which brings iPhoto to the fore of media sharing on the Mac. When iPhoto '11 was released last month, it immediately caused problems for a large number of users. Photo libraries were corrupted, and there was even data loss for a significant group. Apple responded with iPhoto 9.0.1. That update appeared to stop the library corruption, but didn't fix a lot of the other complaints aggravated iPhoto users had, such as a loss of photo calendars, a change in how photos are emailed, and general instability and slowness. Yesterday, iPhoto users received an update to version 9.1. Apple said it "improves overall stability and addresses a few minor issues." This is the way Apple details bug fixes, and sadly, you often don't know what is fixed, and are left experimenting to see if the software works again. It's a maddening way to deal with people who purchased the software, but there it is. Apple 'thinks different'. iPhoto calendars are back, but a subset of users is still struggling with iPhoto even after this latest update. It's clear that the original release simply wasn't tested very well since there have been two bug fix updates in a very short period. How is iPhoto going for you? We know it is working well for a number of users, but scanning the support boards reveals all is not completely well. Please share your experiences and recommendations to Apple in our comments.
Palm and Sprint issue statement acknowledging Profile backup issue
Even in a world full of racket, it seems that the squeaky wheel still gets the grease. In yet another blow to this whole "cloud" agenda, a vocal segment of Palm users began to notice that information transferred from their online Palm Profile was only a fraction of what it should have been. Today, both Palm and Sprint have issued a joint statement acknowledging the issue and promising to work much, much harder in order to avoid having something like this ruin your life once again. To quote: "We are seeing a small number of customers who have experienced issues transferring their Palm Profile information to another Palm webOS device. Palm and Sprint are working closely together to support these customers to successfully transfer their information to the new device." Between this mess and the T-Mobile fiasco, we're pretty certain we're being forced to stay on the manual backup bandwagon for the foreseeable future. [Thanks, Mike]
Dear Aunt TUAW: Recovering iPhone data and media
Dear Aunt TUAW, I'm from the Philippines and I would just like to ask for your help. I don't know if the news had reached you guys but there had been some massive flood lately in our country brought about by super typhoons storming over our land. Anyway, I own an iPhone and thank God I brought it with me when the flash flood came which sadly destroyed my PC and laptop. Now I have a new desktop which leads me to my problem. I'm afraid to install iTunes in it because if ever I'd sync my phone with the new desktop, I'm pretty sure all my iPod files will be gone. Are there any work around for it (so that I can still save my files on my phone)? Will jailbreaking help (as a last resort)? Thanks and more power! =) Best regards, Rand B. Read on for Auntie's answer...
T-Mobile posts Sidekick contact recovery instructions
That Microsoft / T-Mobile tag team has been doing a pretty decent job of cleaning up the disaster area left by the Sidekick data loss, and now the first item on the recovery menu is ready for collection. Sidekick users can hit up the My T-Mobile webpage to download their contacts and then restore them either to their Sidekick or whatever device they've replaced it with. Extensive how-to instructions are available at the read link, which also furnishes us with the reassurance that "Microsoft/Danger continues its efforts to recover pictures, calendar entries and to-do lists, which may be available in the future."[Thanks, Abe G.]
T-Mobile 'considering additional measures' to compensate Sidekick owners
The official line is still that T-Mobile customers affected by Sidekick amnesia will be given a months' credit on their data plan, but that may not be the end of it (and considering the magnitude of the issue for affected folks, we'd certainly hope not). At this point, they're leaving the door open to more by saying that they're "considering additional measures" to help soothe the souls of those who lost contacts, notes, schedules, apps, and everything else, but exactly what those "measures" are remains to be seen. Free phones? Free service? A gift certificate to a day spa? The full (albeit brief) remarks can be found after the break.
Siege jeopardy in Darkfall
Nobody likes server crashes. They always seem to come at the most inopportune times. However, there is no greater inopportune time than during a city siege in Darkfall.Sadly, an ill-timed server crash right after a city siege finalized in Darkfall. This lead to data not being properly saved inside all of the systems, putting the siege result into jeopardy.Tasos Flambouras, Darkfall's producer, took a moment to relate the announcement to the community, and outline that the siege results will be corrected during the server maintenance. As a result, the city ownership will be finalized during the maintenance, and the game will move forward from that point.For Tasos's full remarks, check out his post on the official Darkfall forums.[Via MMORPG.com]
Alaska Department of Revenue vaporizes $38 billion account
The Last Frontier is no stranger to computer failure on a noteworthy scale, but the latest mishap far exceeds the severity of yet another e-voting failure. A quick-fingered technician at the Alaska Department of Revenue reformatted a hard drive while handling "routine maintenance work" that contained an account worth $38 billion -- yeah, with a B. To make matters exponentially worse, he / she also deleted the backup drive for reasons unbeknownst to mere men, and we can probably assume that at least a few individuals in the department suffered a near-heart attack when they found the backup tapes completely unreadable. The only remaining proof of the oil-funded account was in 300 boxes of paperwork, which had to be digitized yet again by staff members working incredibly long hours completing work that had just been done a few months earlier. Incredibly, no one was reportedly punished for the incident, and while the recovery efforts were actually finished in just six painstaking weeks, the damage inflicted by a few careless keystrokes totaled $220,700 in excess labor costs. Ouch.[Via Fark]
Ontrack reveals RAID data recovery secrets
Kroll Ontrack, purveyors of data recovery, give a glimmer of hope to those with wrecked RAIDs in Tom's Hardware Guide's 7-page explanation detailing their step-by-step process, including preventative measures, proper handling tips, different types and levels of damage, and an overview of various Ontrack recovery methods.They stress the obvious solution to make a habit of defragging and backing up your data, however if it weren't for the irresponsible / lazy demographic, Ontrack would be counting their food stamps. They also encourage potential data-loss victims to stay calm, as freak-out sessions oftentimes yield impulsive and regretful decisions for data that might be recoverable. "In 2005, Kroll Ontrack processed 50,000 recovery cases. Ontrack was able to complete 40% of incoming orders successfully right away. The remaining 60% had to be taken to the clean room, where 75% of data recoveries were successful." The stats sound promising if you're in need of a serious data resurrection, and as long as you're willing to cough up a good chunk of your savings. [Via Slashdot]
TextEdit data loss concerns
Over at MacOSXHints, Rob G. has posted a must-read article about possible data loss from TextEdit's Save dialog. The problem stems from TextEdit's (and Cocoa's) willingness to overwrite entire folders with text files. This data security hole seems to occur because "bundle" style files (which are actually folders and not single files) are considered on-par with flat files in OS X. TextEdit does not seem to check to ensure that the folder being replaced is actually a bundle and not, say, your entire home directory. It's an important article to read and a bug that you need to be aware of.
