[redsniper]

No no, I mean the BIOS isn't detecting it anymore. It worked once but now I'm back where I started and I can't even begin to explain why.

[redsniper]

I just flashed my BIOS; still no luck.
EDIT: Windows is going crazy with 'found new hardware.' It says it found my CD/DVD drive (which was working fine already), and it's finding all kinds of IDE stuff (which must have been working already since it can boot from this old HD). I guess since the BIOS got updated it's re-detecting everything. Didn't mention SATA anywhere though. Bummer.

[Scuddie]

Go into BIOS setup and enable reset configuration data (not load defaults), and make sure Plug-and-Play OS is set to NO.  Now try again.

EDIT: SATA isn't recognized under Windows, it's recognised as a SCSI device.

[redsniper]

What do you mean 'reset configuration data'? All I can find is 'Load Setup Defaults'

[Scuddie]

Reset configuration data is typically under PnP/PCI Configurations submenu.  However, if you have a stripped down BIOS with only one or two screens of options (which Asus is notorious for), then good luck finding it.  If all else fails, then go ahead and load setup defaults.

Anyway, if you want your BIOS to detect and configure your controllers, then it's best to disable the PnP OS feature...  Otherwise it won't do it!

[Descenterace]

Originally posted by Bobboau
you'r useing windows, right?
the thing about windows you have to remember is that it's fueled by the purest most vile, dark evil ever to blight the universe.
this sort of **** happens.

Mostly true, but in this case the kernel is the only factor in the equation and the WinXP kernel is actually pretty damned good, comparable in many ways to UNIX.

They just ruined it by putting a whole load of cosmetic bull**** on top of it.

Besides, this sounds to me like a faulty mainboard or disk. I've had problems before where a disk wasn't detected on the first bootup after pressing the power button, but on subsequent resets would work fine. That fault was typically due to either a fault in a disk's onboard controller or a bus misconfiguration. Since SATA doesn't use Master/Slave designations for drives, I doubt it's the latter in this case.

Hang on... jumpers? On a SATA disk? They don't need jumpers.

[WMCoolmon]

Originally posted by Descenterace
Hang on... jumpers? On a SATA disk? They don't need jumpers.

Yes, maybe he mistook a PATA drive for a SATA one. "Why won't this damned connector go in!?!?!?"

[redsniper]

Look, this is definitely a SATA drive and it definitely has a jumper on it too. Like I said earlier, the one time it was detected I was able to browse the disk just fine so I don't think anything is seriously wrong with it. I know it's not impossible for this mobo to detect this HD since it's done it twice, I just need to find out how to make it happen consistently.

[WMCoolmon]

*Hands redsniper an is_sarcasm() function. *

[redsniper]

is_grumpy_that_comp_isn't_working(redsniper)

[Descenterace]

Considered removing the jumper? You never know: it might solve the problem. Anything's worth a try.

Just remember where it was so you can replace it afterward...

[redsniper]

I changed the SATA cable just for kicks then reset the BIOS settings to default. No detect. I then put all the settings back the way I had them including activating the RAID controller. Detected!:cool: It still isn't getting detected all the time, but when it isn't detected I can go into the BIOS, disable the RAID controller, go into the BIOS again, turn the controller back on, and then it will be detected. Now obviously I don't want to do this every day but for now it will work since I'm just trying to get my files backed up before I reinstall Windows.
Now then, I've backed up almost everything I want but there's one hitch. I've got a folder where my downloaded anime, music, pictures and other junk go. At some point in time I did something to limit access to this folder (not a password) all it says when I try to open it is '*folder path* is not accessible Acces Denied'. So I need to know how I can hack around this and get my stuff. I've already tried the Recovery Console on the Windows cd and that'll only let my access the WINDOWS folder.
Help please.

[redsniper]

Alright, the SATA drive is still only being detected intermittently. When it isn't detected I can restart the comp several times and eventually it will detect it again. Now then, I've found a trick for getting around the security on the one folder. By booting from the Win2k floppies I can then go into the Win2k recovery console which gives me full access to the main HD. Unfortunately, I'm not very familiar with DOS environments. I can browse through the various folders easily enough but I don't know how to copy files from one drive to another (and yes I tried 'copy source [destination]'). I also got my hands on a knoppix .iso which I'll try to figure out this evening.

[redsniper]

Maybe it's just my imagination but it seems like this SATA disk is getting detected less and less frequently. I had to restart the comp probably about 10 times before it was detected. It would be impractical to keep this up, there's got to be a way to fix this and I just replaced a mobo so I don't want to have to replace one again. Anyway, I'm gonna see if I can get anywhere with knoppix. Wish me luck, I guess.
EDIT: Knoppix is hardcore!

[redsniper]

Okay, why can't I copy any files from one hard drive to another in Knoppix? Does it matter that some are NTFS?

[Scuddie]

Have you done a dd?  You shouldn't be copying individual files anyhow.

[redsniper]

What's a dd? and why shouldn't I be copying files? How else am I gonna get them off the SATA disk and backed up?
EDIT: found out how to make HD's writable in knoppix.

[Admiral LSD]

dd is a Unix program that does sector-level operations on disks. If you're not familiar with it then it's not something you want to be messing around with as it can severely **** up your disks.

[redsniper]

w00t w00t! I got all the stuff backed up that I want to back up thanks to Knoppix. With that out of the way we're back to the problem of the BIOS more often than not failing to detect the SATA HD. There doesn't seem to be anything that correlates to whether it gets detected or not. It even got detected once when the RAID controller was off.

[redsniper]

ARR!