Reset Port Error
So, I'm getting Reset Port Error upon boot up. I've looked around and am only getting hits for new motherboards or new hard drives or both.
I'm have the MB for almost a year, and the hard drives are much older. The hard drives are a Raid set up. They used to be my primary drive, but when I replaced the MB, I moved them to secondary and have a fresh drive as the primary.
Things were going great until we moved a couple of weeks ago. Then I started getting occasional Failed to Write errors on the hard drives. I understand tools are rather limited for testing Raid drives. But again, this is another problem that seems to exist mostly on new drives or new setups. The wires seem to be okay. Movers moved the system, so there was a chance things got bumped around. But I checked the cables and replugged them in, which didn't help immediately. It got working on one boot up, so I deleted a bunch of stuff since there was only 5GB free on a 700GB raid, and figured that might help. And a day later the problem was gone as if it had never been. Then started up again two days ago. I just rebooted, and it cleared up again, after running chkdsk, like nothing ever happened.
So, I've done no changes to the BIOS. I haven't been inside the guts of the system for almost a month now, so nothing has changed there. I haven't even done anything with any settings. Now can't get past this Reset Port Error. I'm prepared to get a new hard drive to replace the RAID (I'm so done with RAID set ups, so not worth the hassle), and I'm okay with wiping the hard drive if that helps check for errors - although if I can get past these errors, I'd rather do one last back up (I did a back up a few days ago, so I'm not too worried). But is there anything I missed? Something else I can check? What's the best array of solutions to pursue here?
Your best array of solutions is to not use any arrays at all :)
Your IT humor has gone over my head.
Tried googling as well, this was the only remotely helpful hit.
Hmm, that could be it or close to it. Though, I doubt a cable would have gone bad coincidentally with a move, so I suspect there's something wrong with the drive (or at least I prefer that over something wrong with the MB connector).
I got it working - or at least how it was before this morning. Which is, the RAID boot post reports an error, but it mounts and runs. I fiddled with the cables again to get it working (the motherboard connection might have been loose). And haven't gotten any write fails.
Whatever the problem is, I figured, fuck it, and bought a 1 TB drive to replace it. I'll reformat the raid drive and see which, if either, of the drives are salvagable after that.