Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

2/19/2008
08:02 PM
George V. Hulme
George V. Hulme
Commentary
50%
50%

When Good Intentioned Users Do Harm

Minneapolis-based data recovery and forensic software maker Kroll Ontrack published a list of what the company estimates to be some of most common mistakes end users make when trying to save data from a failing drive.

Minneapolis-based data recovery and forensic software maker Kroll Ontrack published a list of what the company estimates to be some of most common mistakes end users make when trying to save data from a failing drive.My big lesson came when, a number of years ago, I spilled 20 ounces of coffee dead center on a Dell ultraportable. In the moment of terror, I thought I saw a strange blue hue shoot from the dying machine. The screen went blank for a moment, then flashed white, beeped, and then never displayed anything ever again. This was not a good day, especially for a guy who earns his living on deadline.

Turns out, when I opened the case, the hard drive was soaked with coffee. And I mean dripping. I tried to revive the drive with one of the tactics Kroll lists as a no-no.

I know these lists are often self-serving, but this list has some truth to it. Kroll estimates that 30% of all drives that prove to be unrecoverable are the result of these types of errors:

1. The user decides they need to completely wipe their drive and restore their data using their backup because they've experienced a data loss situation. A complete reformat and reinstall is performed, only for the user to realize their backup a.) does not work, or b.) is not current. Because the original drive data was wiped, there is little hope of getting back the lost data the user was trying to locate in the first place. To avoid this error, individuals should test their backups by restoring their data to an alternate location before assuming the backup is sound.

2. When a nonworking drive no longer spins, the user attempts to buy a like drive and swap out what he/she believes to be the nonworking part with a part from the newly purchased drive. Because current hard drive parts contain drive-specific information, this act does not fix the drive malfunction since the new part isn't programmed to "talk" to the drive's original parts. In this situation, Kroll Ontrack recommends seeking recovery assistance from a reputable data recovery provider. 3. Similar to the situation listed above, the user believes the head of the drive is stuck because he/she doesn't hear the drive spinning. In an attempt to perform a "quick fix," the user removes the drive and bangs it against his/her desk, creating physical damage to the drive and potentially rendering some data unrecoverable because the head of the drive can actually scratch the platters when it is shaken or tapped. While there are many reasons (electronic failure, power outage, etc.) why a hard drive head stops working, it is certain that shaking the drive won't address any of these issues. 4. A hard drive is waterlogged in either a flood situation or because a glass of liquid was spilled on it. Referencing a common data recovery myth, the user attempts to remedy the situation by using a hair dryer, further damaging the drive. In water damage scenarios, it is recommended that the individual keep the drive in its wet state and send it in for recovery. This will maximize the chances of recovery success, as drying a drive adheres the liquid to the drive. 5. The user opts to utilize an operating system failure program such as CHKDSK, Mac Disk Utility, or FSCK in order to remedy what he/she believes to be an operating error. If the drive is physically damaged and the user runs the program, it will further damage the drive, making recovery more difficult than if the user simply turned off the computer and called an expert at the onset of the issue. In this case, the user should run the system failure program in "safe mode." Running the program in safe mode will allow the program to report on the condition of the system without actually attempting to fix it, thus enabling the user to determine how to proceed.

My favorite is banging the hard drive on one's desk. I've tried this with radios and TVs with much success (not against my desk, I just give them a whack from the side). But I've yet to slam a hard drive against my desk. I have, with some temporary success, extended the life of a desktop power-supply and fan by banging it on my workbench.

But it turns out, the biggest mistake I made was trying to dry my notebook hard drive with a hair dryer. Looks like all I did was fuse coffee particles to the drive.

I do backup now, automatically, every day. The automated backup routine kicks itself on about an hour before I reach my desk first thing in the morning. And that's about the same time I have my first cup of coffee.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Why Cyber-Risk Is a C-Suite Issue
Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Attackers' Costs Increasing as Businesses Focus on Security
Robert Lemos, Contributing Writer,  11/15/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19040
PUBLISHED: 2019-11-17
KairosDB through 1.2.2 has XSS in view.html because of showErrorMessage in js/graph.js, as demonstrated by view.html?q= with a '"sampling":{"value":"<script>' substring.
CVE-2019-19041
PUBLISHED: 2019-11-17
An issue was discovered in Xorux Lpar2RRD 6.11 and Stor2RRD 2.61, as distributed in Xorux 2.41. They do not correctly verify the integrity of an upgrade package before processing it. As a result, official upgrade packages can be modified to inject an arbitrary Bash script that will be executed by th...
CVE-2019-19012
PUBLISHED: 2019-11-17
An integer overflow in the search_in_range function in regexec.c in Oniguruma 6.x before 6.9.4_rc2 leads to an out-of-bounds read, in which the offset of this read is under the control of an attacker. (This only affects the 32-bit compiled version). Remote attackers can cause a denial-of-service or ...
CVE-2019-19022
PUBLISHED: 2019-11-17
iTerm2 through 3.3.6 has potentially insufficient documentation about the presence of search history in com.googlecode.iterm2.plist, which might allow remote attackers to obtain sensitive information, as demonstrated by searching for the NoSyncSearchHistory string in .plist files within public Git r...
CVE-2019-19035
PUBLISHED: 2019-11-17
jhead 3.03 is affected by: heap-based buffer over-read. The impact is: Denial of service. The component is: ReadJpegSections and process_SOFn in jpgfile.c. The attack vector is: Open a specially crafted JPEG file.