Author Topic: I think I just lost my main OS drive... (And now my car died...) (Read 3513 times)

The_Ed · « **on:** Sat, 31 August 2013, 22:07:19 »

My computer just locked up, so I restarted it.

1 long, 2 short beeps. Code FF. ****... (Code FF means either "Fully Functional" or "Fully ****ed" in the IT world. Look it up if you don't believe me.)

Well at least I can boot into this 3 year old Win7 install on this other drive. And I can still see my main drive and contents. Maybe it's JUST the OS, or more likely the boot sector because the screen never even came on to show the bios post.

Looks like I'll be putting in that spare hard-drive I have and... It's at Dad's isn't it... Of course it is because I need it...

****...

EDIT: Interesting... This install was back when I would delete all traces of porn after viewing instead of putting it in folders or making links.

tp4tissue · « **Reply #1 on:** Sat, 31 August 2013, 22:57:03 »

probably you antivirus.

see if you can boot safe mode and uninstall it.

i had a time where the antivirus caused memory errors on boot. and it kept crashing.

The_Ed · « **Reply #2 on:** Sat, 31 August 2013, 23:05:02 »

It has the beeps and code FF before it even posts, so I doubt it's antivirus. Now if it started to boot and then crashed I would accept that as a possibility.

Turkishrambo · « **Reply #3 on:** Sat, 31 August 2013, 23:08:58 »

That sucks. How about taking out the drive and see if it posts? iff no change, put it back in and try 1 stick of memory and test each one

Photoelectric · « **Reply #4 on:** Sat, 31 August 2013, 23:09:17 »

I don't know the post codes that well, but is it certain that the drive is the culprit? Could it be another component having gone bad? If yes, Id try to boot with the bare minimum of parts plugged in, and 1 stick of RAM.

The_Ed · « **Reply #5 on:** Sat, 31 August 2013, 23:43:37 »

Quote from: Turkishrambo on Sat, 31 August 2013, 23:08:58

That sucks. How about taking out the drive and see if it posts? iff no change, put it back in and try 1 stick of memory and test each one

Quote from: Photoelectric on Sat, 31 August 2013, 23:09:17

I don't know the post codes that well, but is it certain that the drive is the culprit? Could it be another component having gone bad? If yes, Id try to boot with the bare minimum of parts plugged in, and 1 stick of RAM.

If you read my OP:

Quote from: The_Ed on Sat, 31 August 2013, 22:07:19

Well at least I can boot into this 3 year old Win7 install on this other drive. And I can still see my main drive and contents. Maybe it's JUST the OS, or more likely the boot sector because the screen never even came on to show the bios post.

It is that hard drive as I can boot to another I have in the same system.

Photoelectric · « **Reply #6 on:** Sun, 01 September 2013, 07:53:51 »

The BIOS should be stored locally on the motherboard, no? You should be able to get into the BIOS before you even have Anything on Any storage drive. I wonder if your PSU is somehow at fault instead. You can boot when you unplug the OS drive from the motherboard AND from the PSU? Or just from the motherboard?

tp4tissue · « **Reply #7 on:** Sun, 01 September 2013, 08:13:08 »

hmmmm..... it could be anyyyything....

uzoc · « **Reply #8 on:** Sun, 01 September 2013, 08:36:23 »

Don't guess, check the Bios code meaning online.
For example: http://www.computerhope.com/beep.htm

The_Ed · « **Reply #9 on:** Sun, 01 September 2013, 14:47:23 »

You guys do realize I'm an IT guy right? As I said before, I simply booted to a different drive in the same system. No changes were made to anything because with my BIOS if there is a failed boot it reverts to other settings. For example - If I overclock too high and it crashes it'll boot to safe clock settings so I can change the overclock to a safer level. When I get the beeps and code FF I just press reset and it boots to the next drive in the boot order (with my overclock intact). It's really an awesome BIOS. IF it isn't my main drive, then it is the SATA port that it is connected to.

When I get my spare drive from my Dad's I'll make a fresh install (I'm overdue anyway) and back up my files from that main drive (Yes I do it manually, I hate backup utilities). Then I'll run some diagnostics to see if I am correct that it's the boot sector, or possibly the SATA port (though this is very unlikely as I can still access my files, but who knows). If it's the boot sector I'll just repair it and be able to boot into it like always. But if it's the SATA port I should be able to just switch to another port and change the boot order in the BIOS.

TLDR: The only thing that's different between not working and working is the choice of drive to boot, thus all other hardware besides my main drive and the SATA port it's connected to is ruled out. And it IS hardware related because it doesn't even POST, and that rules out software.

damorgue · « **Reply #10 on:** Sun, 01 September 2013, 14:55:27 »

I found MHDD to be very useful when a drive head crashed into one of the disks in my OS drive a few years back. Just mentioning it in case you haven't heard of it.

Edit: It is pretty versatile. It can keep the SATA controller from starting and allow you to investigate it a bit if it the problems lies there for instance.

Photoelectric · « **Reply #11 on:** Sun, 01 September 2013, 14:56:39 »

I was just saying that it's odd that it wouldn't post because of the drive. POST is usually done within the motherboard. You can get into the BIOS without ANY drives connected. So the fact that it doesn't post when that drive is connected is definitely odd--I don't see how it would be boot sector related. But you're an IT guy, so I guess you should know the answer already

The_Ed · « **Reply #12 on:** Sun, 01 September 2013, 15:05:04 »

SMART says the drive looks fine, only the power-on hours count is a little low (meaning I have had my drive powered-on for a lot more than the average person). My BIOS is *different* as I explained, so the normal rules don't apply.

The_Ed · « **Reply #13 on:** Thu, 05 September 2013, 15:15:29 »

I forgot to grab my spare drive when I was over at my Dad's on Monday. To make matters MUCH worse my car just died yesterday... (I ain't gonna spend $2-5K to replace the engine) ****...

thebeargentile · « **Reply #14 on:** Thu, 05 September 2013, 15:20:57 »

Quote from: Photoelectric on Sun, 01 September 2013, 14:56:39

I was just saying that it's odd that it wouldn't post because of the drive. POST is usually done within the motherboard. You can get into the BIOS without ANY drives connected. So the fact that it doesn't post when that drive is connected is definitely odd--I don't see how it would be boot sector related. But you're an IT guy, so I guess you should know the answer already

It is uncommon, but definitely happens. Had an 80GB Intel X-25M go bad on me, and the exact same thing happened to me that happened to OP-- system wouldn't post... thought for sure it was bad RAM or MoBo, then I randomly unplugged the X-25's SATA connection, and it started to work again. Threw in another drive, it booted fine... put back in the X-25, no post again. Something about the HDD was making the system fail the self test such that it would't progress past POST.

thadood · « **Reply #15 on:** Thu, 05 September 2013, 15:29:06 »

I had my work PC's SSD die out on me last week. It just dropped off the face of the BIOS. No amount of SATA cable port/cable swaps worked. The system literally can't detect it. So, I booted into a GParted livedisc and mounted my SSD in a USB drive dock to see if I can save anything. All my files are there! So, it gets detected over USB but not SATA. I dd'd to a larger, mechanical HDD.. booted right up. Wut.

Computers are weird, man.

vun · « **Reply #16 on:** Thu, 05 September 2013, 15:30:27 »

This thread is scaring me, tempted to buy a bunch of backup drives in case anything happens now.

The_Ed · « **Reply #17 on:** Thu, 05 September 2013, 15:40:11 »

Quote from: vun on Thu, 05 September 2013, 15:30:27

This thread is scaring me, tempted to buy a bunch of backup drives in case anything happens now.

Or you could buy a bunch of matched drives and make a RAID 5, which is probably what I'm gonna do for my next build. RAID 5 is the best of both worlds, but do I want to do it from the motherboard or a dedicated card... Hmmm... (Yes, I know a dedicated card is the 'proper' way, but they just cost so much.)

thebeargentile · « **Reply #18 on:** Thu, 05 September 2013, 15:43:40 »

I picked up a Synology Disk Station last year, and haven't looked back. Those things are awesome.

I have a love hate relationship with SSDs... I love the speed, but I have had three quality SSDs fail on my in the past two years, vs. only one platter drive in the past 10... I know it's just bad luck, but it's just something about the finality of a SSD failure. If your HDD fails, there's a good chance that you'll be able to recover SOMETHING off of it... all three of my SSD failures were just instabricks... couldn't get anything off of them. But yeah, definitely backup your back ups. Loosing data is no fun.

The_Ed · « **Reply #19 on:** Thu, 05 September 2013, 17:01:20 »

I remember with the whole R00TW0RM fiasco I used this pic a few times. Hopefully there are proper backups (that aren't attached!) of GH nowadays.

The SSD failure rate kinda scares me as well. That's why I wouldn't keep my data on an SSD if I get one for my next build, just the OS and programs/videogames.

microsoft windows · « **Reply #20 on:** Thu, 05 September 2013, 17:13:53 »

WHAT HAPPENED TO YOUR CAR?

The_Ed · « **Reply #21 on:** Thu, 05 September 2013, 17:24:34 »

I didn't write down the list, but it's done for... It was engine AND suspension stuff though. I just got my stuff out of it less than an hour ago, and I probably won't ever see it again.

tp4tissue · « **Reply #22 on:** Thu, 05 September 2013, 17:29:01 »

in my experience, when all your tech starts to break down at the same time...

It's cuz you haven't updated in too long...

MKULTRA · « **Reply #23 on:** Thu, 05 September 2013, 17:31:09 »

Welp you should prolly go beg CC for some stuff and have a sale! Seems like the popular thing to do.

The_Ed · « **Reply #24 on:** Thu, 05 September 2013, 17:33:29 »

A partial hard drive failure has nothing to do with updates, and neither does my car dying.

I've never owned a CC, and probably never will seeing as I'd never pay money for one of those things. I've also never had an auction.

MKULTRA · « **Reply #25 on:** Thu, 05 September 2013, 17:35:56 »

Quote from: The_Ed on Thu, 05 September 2013, 17:33:29

I've never owned a CC, and probably never will seeing as I'd never pay money for one of those things. I've also never had an auction.

I was being sarcastic haha.

Btw what brand drive was it?

The_Ed · « **Reply #26 on:** Thu, 05 September 2013, 17:41:22 »

A 2002 Saturn L200?

MKULTRA · « **Reply #27 on:** Thu, 05 September 2013, 17:47:59 »

Quote from: The_Ed on Thu, 05 September 2013, 17:41:22

A 2002 Saturn L200?

The hard drive

The_Ed · « **Reply #28 on:** Thu, 05 September 2013, 17:55:58 »

Quote from: MKULTRA on Thu, 05 September 2013, 17:47:59

Quote from: The_Ed on Thu, 05 September 2013, 17:41:22
A 2002 Saturn L200?
The hard drive

...Western Digital Caviar Black SATA III 7200RPM 1TB 64MB cache

After I get the files off of it I'll do some thorough testing. If it fails the tests it is still within the 5 year warranty, so I should be able to get a replacement.

News:

Author Topic: I think I just lost my main OS drive... (And now my car died...) (Read 3513 times)