Determining the new ARC name

NTDEV
1

I have a disk which as survived intact through about three motherboard
upgrades over the years. (Amazingly enough.)

Now I install it on a new motherboard and get inaccessable boot device. Ok,
the new motherboard has a builtin raid and a lot of SATA ports that I’m not
using, so the arc boot path is probably no longer multi(0)etcetc but is
something else.

My usual method of ‘solving’ this is trial and error, but this time I
thought I try a more scientific approach. However, after a couple hours
fooling around, I probably would have been better off with trial and error.

I set up the kernel debugger and caught the inaccessible boot device trap.
I can see that it is trying to boot from
\ArcName\multi(0)disk(0)rdisk(0)partition(1).

Now, how do I find out the list of valid arc names on this system? The
ArcNames path in object manager is empty, the ?? path doesn’t seem to be
telling me much useful. I don’t seem to be having much luck in finding the
symbolic link names to the disk devices in any form I can seem to translate
back to arc names.

I’m sure this is simple, and I’m just looking in the wrong direction. What
should I be looking for?

Thanks
Loren

2

Are you trying to boot from the old disk on the new motherboard? That’s
pretty hit or miss.

Given that \ArcNames is empty the system probably isn’t finding your
disk, or the controller it’s attached to, or the controller requires a
non-standard driver (like a raid driver for the builtin RAID). The
system builds the path you list below from information captured by the
boot loader but then is unable to resolve it to an actual device.

It’s always better to just copy your configuration info and files off
the old machine, clean install on the new one and then reapply
everything.

You might have luck going into your bios and seeing if you can switch
off the “raidness” of your raid controller. Often times this switches
the machine back to having a standard IDE controller which the
critical-device-database can then configure in order to get you running
again.

-p

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Loren Wilton
Sent: Tuesday, September 06, 2005 12:09 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Determining the new ARC name

I have a disk which as survived intact through about three motherboard
upgrades over the years. (Amazingly enough.)

Now I install it on a new motherboard and get inaccessable boot device.
Ok, the new motherboard has a builtin raid and a lot of SATA ports that
I’m not using, so the arc boot path is probably no longer multi(0)etcetc
but is something else.

My usual method of ‘solving’ this is trial and error, but this time I
thought I try a more scientific approach. However, after a couple hours
fooling around, I probably would have been better off with trial and
error.

I set up the kernel debugger and caught the inaccessible boot device
trap.
I can see that it is trying to boot from
\ArcName\multi(0)disk(0)rdisk(0)partition(1).

Now, how do I find out the list of valid arc names on this system? The
ArcNames path in object manager is empty, the ?? path doesn’t seem to be
telling me much useful. I don’t seem to be having much luck in finding
the symbolic link names to the disk devices in any form I can seem to
translate back to arc names.

I’m sure this is simple, and I’m just looking in the wrong direction.
What should I be looking for?

Thanks
Loren

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@windows.microsoft.com
To unsubscribe send a blank email to xxxxx@lists.osr.com