"unmountable_boot_volume"

[Guest]

Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

I have an A7N8X-VM/400 here that is giving me the above message. I have
performed every sensible trick in the book, to no avail. I have Run the
Recovery Console tools, I have chkdsk'ed till my nose bled, I have changed
drives, I have disconnected everything on the drive bus but the one drive,
I have bought a new drive.I have re-jumpered drives.I have repartitioned.
I have changed drive cables. I have even considered blood sacrifices. To
no avail.

Does ANYONE have any suggestions or is this a MB with dead drive control
electronics? I hope it isn't, because that would mean that this is the
SECOND Asus MB to go naff in the drive controller section in less than a
month.

Oh, this started with no warning. Just turned the box on, one morning,
there the message was.

Next question: Is Asus getting sloppy in its QA? Two MBs bad in a month?
This don't look too good.

-skal

 

[Paul]

Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

In article <pan.2004.04.02.13.26.53.599831@notonuseneti.dont>, Skal Loret
<skal@notonuseneti.dont> wrote:

> I have an A7N8X-VM/400 here that is giving me the above message. I have
> performed every sensible trick in the book, to no avail. I have Run the
> Recovery Console tools, I have chkdsk'ed till my nose bled, I have changed
> drives, I have disconnected everything on the drive bus but the one drive,
> I have bought a new drive.I have re-jumpered drives.I have repartitioned.
> I have changed drive cables. I have even considered blood sacrifices. To
> no avail.
>
> Does ANYONE have any suggestions or is this a MB with dead drive control
> electronics? I hope it isn't, because that would mean that this is the
> SECOND Asus MB to go naff in the drive controller section in less than a
> month.
>
> Oh, this started with no warning. Just turned the box on, one morning,
> there the message was.
>
> Next question: Is Asus getting sloppy in its QA? Two MBs bad in a month?
> This don't look too good.
>
> -skal

Did it occur to you that your disk drive is killing motherboards ?
If I lost two motherboards, I'd be wondering what was up with the
drive. It could even be a bad cable. Make sure you mark the cable
and drive with a marker pen, so you can keep track of the
suspect components. (I've seen duff components get put back into
production systems, only to do more damage :-(

I don't know of an easy way to test drive electronics. At a minimum,
I'd need an oscilloscope to examine the signals on the cable, to see
if something isn't right. For now, I would "retire" the drive in
question, and RMA the motherboard.

You could pick up a second hand PCI IDE controller, and use
that to transfer the data from the suspect drive, to the new
one. There is no guarantee though, that the suspect drive won't
kill a channel on that PCI card too. Since cards like that have
two connectors, use a separate cable for the suspect drive and
the new drive, so the suspect doesn't damage the new one if they
share the same cable.

Also, are the power supply voltages good ? Have you checked the
power monitor page in the BIOS lately, to see if the supply
voltages are within 5% of their nominal values ? I don't know of
a damage mechanism related to the power supply, but maybe if you
see something weird there...

HTH,
Paul

 

[Paul]

Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

do you happen to have a ati videocard?

"Paul" <nospam@needed.com> wrote in message
news:nospam-0204041329480001@192.168.1.177...
> In article <pan.2004.04.02.13.26.53.599831@notonuseneti.dont>, Skal Loret
> <skal@notonuseneti.dont> wrote:
>
> > I have an A7N8X-VM/400 here that is giving me the above message. I have
> > performed every sensible trick in the book, to no avail. I have Run the
> > Recovery Console tools, I have chkdsk'ed till my nose bled, I have
changed
> > drives, I have disconnected everything on the drive bus but the one
drive,
> > I have bought a new drive.I have re-jumpered drives.I have
repartitioned.
> > I have changed drive cables. I have even considered blood sacrifices.
To
> > no avail.
> >
> > Does ANYONE have any suggestions or is this a MB with dead drive control
> > electronics? I hope it isn't, because that would mean that this is the
> > SECOND Asus MB to go naff in the drive controller section in less than a
> > month.
> >
> > Oh, this started with no warning. Just turned the box on, one morning,
> > there the message was.
> >
> > Next question: Is Asus getting sloppy in its QA? Two MBs bad in a month?
> > This don't look too good.
> >
> > -skal
>
> Did it occur to you that your disk drive is killing motherboards ?
> If I lost two motherboards, I'd be wondering what was up with the
> drive. It could even be a bad cable. Make sure you mark the cable
> and drive with a marker pen, so you can keep track of the
> suspect components. (I've seen duff components get put back into
> production systems, only to do more damage :-(
>
> I don't know of an easy way to test drive electronics. At a minimum,
> I'd need an oscilloscope to examine the signals on the cable, to see
> if something isn't right. For now, I would "retire" the drive in
> question, and RMA the motherboard.
>
> You could pick up a second hand PCI IDE controller, and use
> that to transfer the data from the suspect drive, to the new
> one. There is no guarantee though, that the suspect drive won't
> kill a channel on that PCI card too. Since cards like that have
> two connectors, use a separate cable for the suspect drive and
> the new drive, so the suspect doesn't damage the new one if they
> share the same cable.
>
> Also, are the power supply voltages good ? Have you checked the
> power monitor page in the BIOS lately, to see if the supply
> voltages are within 5% of their nominal values ? I don't know of
> a damage mechanism related to the power supply, but maybe if you
> see something weird there...
>
> HTH,
> Paul

 

[Guest]

Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

On Sat, 03 Apr 2004 22:11:01 -0500, Paul wrote:

> do you happen to have a ati videocard?

No sir. On-board Gforce 4 MX graphics.

-skal