Worst Computer Disaster You Have Caused or Experienced

I once tried to change hard drives while the computer was on. I got a spark and smoke but the HD was fine, just had to replace the power supply.

Many years ago when Macs only had SCSI connectors in them I had a drive I needed some data off of. I don't know why, but if it was plugged into the bus at boot time the computer wouldn't boot.

Then I had a brilliant idea, plug the drive into the bus after boot. This actually worked. If you have any idea how touchy SCSI is (especially then) this is totally amazing.

More so by the fact I did it 3 more times.
 
Wow, I will work to prevent any of those horrific incidents that "numb" a person from happening to me.

I get numb just thinking I may have said the wrong thing to someone. I couldn't handle multimillion dollar profit losses that are my fault.

Worst I've done is attempt to resize an existing partition to take over space that once belonged to a linux partition. Unfortunatly I hadn't bothered to spare a few extra megs of space (which this drive apparently needs) and thus ruined a perfectly good partition table. After managing to fix the partition table, I decided to do something else, forget what, and destroyed the boot record on the drive. A full reinstall of the system later, I found out all I had to do to restore the boot record was some minor thing.
 
I changed the driver on a printer on our Windows NT 4 print server. It blue screened so bad it had to be rebuild from the ground up. We don't backup print servers. 300 people, no printing.

I hold the record for the fastest take down, rebuild of a server at our company.
 
Minor issue, didn't even break the computer, but I once dumped a computer off a cart onto a concrete sidewalk. Funny bit is I bent the frame of the computer. It had this just barely perceptible lean to the left, you'd look at it and know something was wrong but not quite what it was.
 
One long weekend I couldn't be bothered going in to the office to change the backup tapes, so the normal weekly full backup didn't run. That same weekend, three - count them, three - drives failed, including both sides of a mirror, taking out our largest database. (About 150GB, which was enormous at the time.)

Turned out that the guy responsible for running the previous full backup hadn't done it either.

I had to reconstruct the data by re-processing two weeks worth of input files - and the company couldn't send out any bills until I finished. I stayed awake for 54 hours straight. Actually, I think I fell asleep in my chair a couple of times, but I was working most of that time.

At the end, it reconciled to the cent.
 
Then I had a brilliant idea, plug the drive into the bus after boot. This actually worked. If you have any idea how touchy SCSI is (especially then) this is totally amazing.

How on earth did you pull that one off? You should have been able to find the drive pretty easily by running SCSI Probe, but just plugging it in and having it work is amazing. Was the info on a SyQuest, perchance? That's another technology I'm not missing.

Oh, the bad old days, eh? Thank Ed for USB and FireWire...
 
I've detailed my own recent problem with wiping out my hard drive elsewhere. However, the worst work-related error was typing M-ACCT instead of M-ACCOUNT in a COBOL program (both were legitimate fields, but stats were only collected from one). Not discovered until six months later when the stats for the project were collected. Of course no backups had been made of the original data (that part was not my fault). This started a whole line of unfortunate incidents that ultimately led to another job that worked out quite well.


Some might say that things started to go wrong the moment you accepted a job writing COBOL. ;)
 
How on earth did you pull that one off? You should have been able to find the drive pretty easily by running SCSI Probe, but just plugging it in and having it work is amazing. Was the info on a SyQuest, perchance? That's another technology I'm not missing.

Oh, the bad old days, eh? Thank Ed for USB and FireWire...

The problem is I couldn't boot as long is it was plugged in, it screwed up the startup sequence some how. I think it had to do with the spin up time of the drive taking too long.

Not sure why it worked, it was the only device on this particular chain and was properly terminated. I was very careful to plug it in with one push, all pins made contact at the same time.
 
I came into work one day at 8am, before we had a dedicated server room, and was met by a guy saying he had come in at 6am but couldn't access his data. He'd gone to our area and smelled something funny.

Our area smelled strongly of burnt insulation. Turns out the server had caught on fire, there weren't any flammables around it so it had gone out.

Fortunately the backup for the night had finished, and the tape drive was a serperate peripheral so the tapes were still good.

When we asked why the guy hadn't paged us (this was before cellphones were affordable) he said he didn't want to wake us.
 
The problem is I couldn't boot as long is it was plugged in, it screwed up the startup sequence some how. I think it had to do with the spin up time of the drive taking too long.

Not sure why it worked, it was the only device on this particular chain and was properly terminated. I was very careful to plug it in with one push, all pins made contact at the same time.
Followed, I presume, by the usual SCSI stuff of writing the runes, lighting the candles and sacrificing the chicken. I miss those days.
 
How on earth did you pull that one off? You should have been able to find the drive pretty easily by running SCSI Probe, but just plugging it in and having it work is amazing.

Oh for goodness sake.

Done that hundreds of times on VMS machines.

Even had a system disk that was starting to go flaky. Whipped it out of the running system, took it over to another machine, changed its address jumper, made a block-for-block copy to a spare disk, took the copy back to the original system, plugged it back in.

The system continued to run throughout the whole episode.

VMS, when only the very best is good enough.

VMS, when downtime is not an option.
 
Was installing a Netblazer terminal server (we were an ISP) and forgot the the unit had shipped stright from America, so I neglected to switch the little voltage selector at the rear from 110V to 220V.

About 30 minutes after install there was an almight bang and the power to the ISP main node went down........
 
... I killed a man...



...don't like to talk about it...
 
We had just spent 3 months performing 42 separate month end processes as part of a data migration. Then someone truncated all the tables.

Given the volumes of data involved c700Gb, no-one had been doing backups.

Second time around it didn't take 3 months
 
Waaay back in my mainframe days, waaay back (early 80's) when I was a lowly computer operator for a small insurance company, I was the first to enter our air conditioned mainframe computer room (normally kept very cold) in the morning only to discover that the large air conditioner (located in the computer room, where it should not have been) we depended on for cooling had failed. Not only had it failed, but the high temp cutoff that should have tripped a breaker had not tripped. I had not experienced such heat since my first summer job working in a kiln at a local sewer pipe factory - I was in an instant sweat. All computers were still running! I instantly brought down all programs and the mainframe in an orderly fashion. Later, I pulled one of the floor squares covering our elevated floor to find all our heavy duty cabling, including power cables and junction boxes, immersed in several inches of water! Yikes! After the air conditioner was repaired and after pumping the water out as best we could, and cooling and drying the room and floor with all the industrial fans we could find, we started up our mainframe, fully expecting everything to go up in smoke. But we came up and were running just like nothing happened. Nothing was lost but time and nothing was harmed. No hard drives were affected. And kept on using the same air conditioner until we switched to pcs and servers.
 
I got home from work approx 1 hr ago (its 11:30pm) as my idiot work colleague decided to rectify a problem with some printing by CDS'ing (turning off) half our ancient mainframes comms lines. That would have been OK, but he neglected to tell it they were back, before he left at 2pm! He also forgot to tell me, any other staff or any customers. SO 2:05pm comes and the phone calls start. Only way to get it back was to reIPL the system, but then it wouldn't come back up, hence me being in work until 10:30pm. He is dead man come monday!

Thank jebus I work with servers now, couldn't remember half the instructions for mainframes!
 
... I killed a man...



...don't like to talk about it...

I really don't mean to pry, but, are you serious? If this is true, you need not say any more. I just want to know if this is a joke or not.

All I can say is, if you want huge pressure, take a programming job involving a system that directly involves someone's life.
 
All I can say is, if you want huge pressure, take a programming job involving a system that directly involves someone's life.
Years ago I read an article about some firmware in a device which automatically dispensed drugs into a patient's IV.

There was a bug in the firmware which occasionally caused the device to dispense all of the drug at once, which, depending on the drug involved, could (and did) kill patients.

No way in hell would I write software for an app like that.
 

Back
Top Bottom