Data from Shuttle Columbia Survives Accident

Terry Olaes

I Used to be the [H] News Guy
2FA
Joined
Nov 27, 2006
Messages
4,646
Renowned data recovery engineer Jon Edwards has done it again. A hard drive recovered from the wreckage of the shuttle Columbia was salvaged by Edwards, even though the hard drive survived an explosion, re-entry burn, and a fall to the earth from thousands of feet. Amazing!

"When we got it, it was two hunks of metal stuck together. We couldn't even tell it was a hard drive. It was burned and the edges were melted," said Edwards, an engineer at Kroll Ontrack Inc., outside Minneapolis. "It looked pretty bad at first glance, but we always give it a shot."
 
That was on SciAm back on Monday. News travels slow. :p
 
I read this on CNN.com Technology yesterday and was about to submit it to [H] news. This feat is just beyond amazing, and scary at the same time! Those of you who are thinking about the hundred ways of destroying your data, don't bother, Jon Edwards most likely will find a way to retrieve it ;)
 
The biggest douche in the universe for the criminals :p. 'Tis pretty scary that something so far beyond repair could be recovered. I really doubt thought that this guy would be in any average Joe Blow criminal case - it would have to be pretty damn big to justify such an expenditure of time/money/effort.

340MB drive that ran on DOS.... NASA sure keeps up with the space age don't they?
 
They use what works for mission essentials, not necessarily the latest and greatest.
 
Edwards attributes that to a lucky twist: The computer was running an ancient operating system, DOS, which does not scatter data all over drives as other approaches do.

340MB drive that ran on DOS.... NASA sure keeps up with the space age don't they?

does that distrube you as much as it does me...

If i was microsoft or even apple.. I would feel a sharp slap for that one
 
NASA uses tried and true tech. This is especially important when its working one of the most complicated machines on the planet. No need to make it any more complicated than it is.

This being said, It pains me to think that technology hasn't progressed enough to produce a product that is more advanced and just as reliable (if not more) than an old 340MB drive running DOS. I am blown away that a 340MB drive is still in existence and functional. Average HD's now a day don't even being dropped...this one survived re-entry!!:D
 
Remember, the shuttle was designed in the 70's. The 8086 was upgrade hardware, probably from the late 80s/early 90s. Space rated hardware lags several years behind state of the art because ultimately the only way to prove the long term reliability of hardware is to actually spend a few years testing it. That means the hardware being targeted for development is several years old at the start of the very lengthy development path. The shuttle software team was the only group to qualify for a CMMI level 5 certification (bugfree software through massive documentation/testing processes) without having to improve their processes first. IIRC there're ~250k lines of code. The three releases of the software had a total of 2 bugs (one in each of the 1st two) between them. CMMI does work, but it's not fast.
 
This hard drive was not from Columbia's flight control systems, it was part of the CVX-2 experiment package (testing shear thinning of xenon gas) that Columbia was carrying when it was destroyed.

However, as was said upthread, something a lot of people forget is that hardware (and software) that is certified for spaceflight can take many years to be certified, because whatever is installed just has to work and return the astronauts safely, even with a major system failure. The shuttle's main flight control system is redundant to the extreme, because it has to fail safe to allow the crew to get home safe.

From Wikipedia:

Flight systems

Early shuttle missions took along the GRiD Compass, arguably one of the first laptop computers. The Compass sold poorly, as it cost at least $8000 (USD), but offered unmatched performance for its weight and size.[4] NASA was one of its main customers.[5]

The shuttle was one of the earliest craft to use a computerized fly-by-wire digital flight control system. This means no mechanical or hydraulic linkages connect the pilot's control stick to the control surfaces or reaction control system thrusters.

A primary concern with digital fly-by-wire systems is reliability. Much research went into the shuttle computer system. The shuttle uses five identical redundant IBM 32-bit general purpose computers (GPCs), model AP-101, constituting a type of embedded system. Four computers run specialized software called the Primary Avionics Software System (PASS). A fifth backup computer runs separate software called the Backup Flight System (BFS). Collectively they are called the Data Processing System (DPS).[6][7]

The design goal of the shuttle's DPS is fail operational/fail safe reliability. After a single failure, the shuttle can still continue the mission. After two failures, it can still land safely.

The four general-purpose computers operate essentially in lockstep, checking each other. If one computer fails, the three functioning computers "vote" it out of the system. This isolates it from vehicle control. If a second computer of the three remaining fails, the two functioning computers vote it out. In the rare case of two out of four computers simultaneously failing (a two-two split), one group is picked at random.

The Backup Flight System (BFS) is separately developed software running on the fifth computer, used only if the entire four-computer primary system fails. The BFS was created because although the four primary computers are hardware redundant, they all run the same software, so a generic software problem could crash all of them. Embedded system avionic software is developed under totally different conditions from public commercial software, the number of code lines is tiny compared to a public commercial software, changes are only made infrequently and with extensive testing, and many programming and test personnel work on the small amount of computer code. However in theory it can still fail, and the BFS exists for that contingency.

The software for the shuttle computers is written in a high-level language called HAL/S, somewhat similar to PL/I. It is specifically designed for a real time embedded system environment.

The IBM AP-101 computers originally had about 424 kilobytes of magnetic core memory each. The CPU could process about 400,000 instructions per second. They have no hard disk drive, and load software from magnetic tape cartridges.

In 1990, the original computers were replaced with an upgraded model AP-101S, which has about 2.5 times the memory capacity (about 1 megabyte) and three times the processor speed (about 1.2 million instructions per second). The memory was changed from magnetic core to semiconductor with battery backup.
Since the GPCs are based on the System/360 architecture, I don't think it'd run DOS.
 
does that distrube you as much as it does me...

If i was microsoft or even apple.. I would feel a sharp slap for that one


DOS is Microsoft.

You must be a young'in. DOS stands for Disk Operating System.

MS had numerous versions from 1.0 to 7.0. 6.22 was the last to be released by itself. After that, the Windows 98 had version 7.0 I believe.. and even Windows ME came with DOS even though you had to "hack" to be able to boot to DOS.

Yes, ther are a few other companies that made a "DOS" OS, but those were much less distributed.. things such as FreeDOS and Dr.DOS.
 
DOS is Microsoft.

You must be a young'in. DOS stands for Disk Operating System.

MS had numerous versions from 1.0 to 7.0. 6.22 was the last to be released by itself. After that, the Windows 98 had version 7.0 I believe.. and even Windows ME came with DOS even though you had to "hack" to be able to boot to DOS.

Yes, ther are a few other companies that made a "DOS" OS, but those were much less distributed.. things such as FreeDOS and Dr.DOS.

Not exactly correct regarding the owner of DOS. DOS is indeed Diskette Operating System, but Microsoft only owned MSDOS. IBM also had a diskette operating system known as PCDOS.

But you were correct saying there were other open source DOS's flying around out there.You can find a bunch at www.bootdisk.com

To those who regarded NASA as primitive running a DOS machine, I disagree. For mission critical purposes, you want to run as little as possible to reduce the chance of crashing the software.
 
You are correct.. I forgot about PCDOS.

I really would like then to clarify who's "DOS" they were running.
 
Bah, the guy fails. Only 1 for 3.
...he later had no success with two other drives found in Columbia's wreckage. Blasted by the unfathomable furnace of entry into the atmosphere, their metals had lost the ability to hold a magnetic charge.

:p
 
So much testing and redundancy, yet a small piece of foam brings down a multi billion dollar project.

I would say it was a management failure. They knew there was tile damage from the foam impacts, but instead of playing it safe, they tried to land anyways.

Same with the Challenger. Morton Thiokol engineers told NASA management it wasn't safe to fly, and they did anyways.
 
I would say it was a management failure. They knew there was tile damage from the foam impacts, but instead of playing it safe, they tried to land anyways.

Same with the Challenger. Morton Thiokol engineers told NASA management it wasn't safe to fly, and they did anyways.
After roughly a month of weather related delays they were given only a few hours to find a reason why it could NOT safely take off in weather 12F colder (20 vs 32F) than its minimum design launch temperature. Checking every single component in half a day was impossible.
 
After roughly a month of weather related delays they were given only a few hours to find a reason why it could NOT safely take off in weather 12F colder (20 vs 32F) than its minimum design launch temperature. Checking every single component in half a day was impossible.

Checking before the launch is not the point; The Engineers said "this is not safe, and here is why: (provided evidence of previous cold launches and damaged O-rings" It wasn't like they never asked, they just didn't listen.
 
Back
Top