Techies: Wouldn't happen to have this Gigabyte AMD AM2 mobo would ya?

[Gremlin]

I'm hunting for a Gigabyte AMD AM2 M59SLI-S5 motherboard. Part code is GA-M59SLI-S5. Purchase if I have to, but ideally borrow one for a couple of days.

I think mine has shat itself on the pci-e slots, or it could be something else (minimal hardware plugged in, cmos reset etc, and I get nothing display wise). Basically, I can't get it working at the mo, and don't hear any beeps if I start it up without ram (which means either a, this motherboard happens to not do that - it is model specific, or b, its toast).

The bad part is that a lot of data is caught up in a raid 10 across 4x 1tb drives, utilising the fantastic nvidia raid (sarcasm is the lowest form of wit, I know) and ummmm I haven't backed it up, as it wasn't CRUCIAL, but very handy to have :whistle:

Worst case scenario, I think I can read the raid on another machine, but I would like to take the easier route first.

btw... If anyone is after an amd am2 socket cpu cooler, or x2 6400+ cpu, they will be for sale shortly... I have had it with amd. :angry2:

[PirateJafa]

If it is hardware RAID you should be able to read it on another machine. Just swap the drives and PCI RAID card across.

[BadCompany]

If it is hardware RAID you should be able to read it on another machine. Just swap the drives and PCI RAID card across.

If its nvidia raid its not hardware raid. And either way the array should be stored in the MBR or something, so you should be able to recompile it on another machine.

Gremlin, you shouldn't need the same motherboard. Just befriend someone who has an AM2 system and start swapping out parts until you find the problem. Have you tried popping the graphics card out and seeing if you get the same results? Do the same with the CPU.


-Bad.

[Gremlin]

If its nvidia raid its not hardware raid. And either way the array should be stored in the MBR or something, so you should be able to recompile it on another machine.
Yep, nvidia raid is software raid, as badcompany says, and onboard, so no swapping of pci card :rolleyes: Only issue with MBR, is that it had dual raids, 1x raid 1 for the primary (with OS etc) and being raid 1, can plug the drive in easy as, as the drives are identical, and 1x raid 10 for secondary raid, which is the one I want the data off, as being raid 10, its stored the data across 2 drives, then mirrored.

Haven't gotten to the point of swapping out equipment like the cpu, as its a pain in the ass, and I had other things to do. It was running dual gfx cards, and tested one at a time, without success, also removed 6 of the 7 hdd along with other peripherals.

*sigh* I despise troubleshooting

[Gremlin]

May as well provide an update...

Did some part replacing, gave up, RMA'd the motherboard almost 2 weeks ago. Collected it yesterday, and they told me it had been replaced. I even gave them a nice long description of the fault, what I had tried, the test result they stated: "Did not post" :clap:

Anyway, picked up the mobo late yesterday afternoon (weds). Spent about 2 hours putting the computer back together into the early morning. Start her up, and we have action, post etc. :banana: Straight into the BIOS to set it up etc. A little bit suspicious about what board it was, as it was slightly dusty, so suspect it is mine, fixed (no probs with that, if its been fixed, odds are, its better than a new one).

While in the BIOS, I realise its too old for the CPU I am running, so quickly flash that. Reboot.

No post... :angry2:

I would like to commend myself for not screaming in rage/frustration... would have woken a lot of people. I now get to visit them again, and politely explain I would like it actually fixed... :crybaby:

side note... without display, you can't even go back, and it has a dual bios which obviously isn't kicking in either *sigh*

[captain_andrey]

Pull out the CMOS battery and leave it out for about 10 secs. Put it back and give it another go.

[Gremlin]

Pull out the CMOS battery and leave it out for about 10 secs. Put it back and give it another go.
Thats what killed it properly the first time... as in, it was having issues booting, cleared cmos/removed battery, and then I got nothing...