hal.dll issue with raid drive

V

Vie

I have a home built computer, 4 hard drives: 2 IDE storage drives designated
C and D, 2 SATA Raid 0 drives designated E. All of a sudden I started
getting the hal.dll message. I put in my XP disc and tried to use recovery
to access the raid drive but was unable to. Unable to make any progress I
wiped and reinstalled windows. Immediately I started having the problem.

Still not able to acess raid drive while in recovery mode.
 
P

Pegasus \(MVP\)

Vie said:
I have a home built computer, 4 hard drives: 2 IDE storage drives
designated
C and D, 2 SATA Raid 0 drives designated E. All of a sudden I started
getting the hal.dll message. I put in my XP disc and tried to use
recovery
to access the raid drive but was unable to. Unable to make any progress
I
wiped and reinstalled windows. Immediately I started having the problem.

Still not able to acess raid drive while in recovery mode.

Why would you run drive E: as a mirrored disk? Mirroring can keep your
system going when a disk fails (which is very rare these days) but it does
not protect you against data loss. Have you tried running the system with a
straight basic (not dynamic) disk?
 
B

Bob I

Pegasus said:
Why would you run drive E: as a mirrored disk? Mirroring can keep your
system going when a disk fails (which is very rare these days) but it does
not protect you against data loss. Have you tried running the system with a
straight basic (not dynamic) disk?

Nope, RAID 0 isn't mirrored that's RAID 1. User is truly stuffed until
he builds a recovery CD with RAID drivers. Perhaps he will give up on
the "speed" setup and go back to stable.
 
J

John John (MVP)

You need to use the F6 method to supply the RAID drivers on a floppy
diskette. Is the Windows installation on the RAID-0 array?

John
 
V

Vie

The windows installation is on the RAID array. I had already provided the
RAID drivers when installing and reinstalling XP. Initially it was working
fine accessing the C drive (boot files located on C drive) to boot the RAID
drive but just recently this issue came up. It will still boot up if I leave
the Windows CD in and just let it boot up on its own.
 
J

John John (MVP)

You will need to supply the drivers when you boot with the Windows XP
CD, without the drivers you will not be able to access the drive, the
Windows setup program will not see the drive nor will the Recovery
Console. You have to keep in mind that when you boot to the Recovery
Console or to the Windows setup program your are not booting or using
anything on the hard drive, all the files are loaded from the CD and the
RAID drivers are not on the CD, ergo you cannot see the drive when you
boot with the CD. You have to press the F6 key very early on when the
CD is booted and you *must* supply the drivers on a floppy diskette.

John
 
V

Vie

Oh yeah, I knew I was missing something with that. Ok so I'll stop being
semi retarded and try it. I went so far as to edit the boot.ini file. God
give me DOS 6.22 back so I can lie to my computer and tell Mystic Towers that
I do have a sound blaster 16
 
V

Vie

Well, trying to do bootcfg failed, but it did recognize the Windows
installation. I went back to looking at the boot.ini file cause something in
the back of my head just didn't sit right there. Initially it said:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(2)partition(1)\WINDOWS="Microsoft Windows XP Home
Edition" /noexecute=optin /fastdetect

Now, if multi is the number of extra OS installed, disk is the number of
hard drives, rdisk is the number of RAID drives, and partition is the number
of the partition on the drive in question (assuming it's not binary
countered), why would it look to 2 different locations for the operating
system. I changed it to read:


[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP Home
Edition" /noexecute=optin /fastdetect


Now it works fine. So if anyone else out there has a crazy setup like mine
and runs into this problem, here you go.
 
V

Vie

Oh, and to edit the boot.ini file, I had to do the following:

Start Menu > Run: command
C:
cd\ (if not already there)
attrib boot.ini -r -s -h
edit boot.ini
(after editing) attrib boot.ini +r +s +h

Vie said:
Well, trying to do bootcfg failed, but it did recognize the Windows
installation. I went back to looking at the boot.ini file cause something in
the back of my head just didn't sit right there. Initially it said:

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(2)partition(1)\WINDOWS="Microsoft Windows XP Home
Edition" /noexecute=optin /fastdetect

Now, if multi is the number of extra OS installed, disk is the number of
hard drives, rdisk is the number of RAID drives, and partition is the number
of the partition on the drive in question (assuming it's not binary
countered), why would it look to 2 different locations for the operating
system. I changed it to read:


[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP Home
Edition" /noexecute=optin /fastdetect


Now it works fine. So if anyone else out there has a crazy setup like mine
and runs into this problem, here you go.


John John (MVP) said:
You will need to supply the drivers when you boot with the Windows XP
CD, without the drivers you will not be able to access the drive, the
Windows setup program will not see the drive nor will the Recovery
Console. You have to keep in mind that when you boot to the Recovery
Console or to the Windows setup program your are not booting or using
anything on the hard drive, all the files are loaded from the CD and the
RAID drivers are not on the CD, ergo you cannot see the drive when you
boot with the CD. You have to press the F6 key very early on when the
CD is booted and you *must* supply the drivers on a floppy diskette.

John
 
J

John John (MVP)

Vie said:
Now, if multi is the number of extra OS installed, disk is the number of
hard drives, rdisk is the number of RAID drives, and partition is the number
of the partition on the drive in question (assuming it's not binary
countered), why would it look to 2 different locations for the operating
system.

Nice guess but that isn't how it works. Most users will use the MULTI()
Syntax to boot their pre-Vista Windows NT type computers, the syntax is:

Multi(W)disk(X)rdisk(Y)partition(Z)\%systemroot%

(In the earlier Microsoft documentation the Multi ARC path is explained
and documented as multi(X)disk(Y)rdisk(Z)partition(W)\<winnt_dir>, thus
the Multi syntax is often described as the MULTI(X) Syntax, (instead of
MULTI(W)), this is a purely cosmetic detail that is only relevant to the
explanation of the syntax).

The following is from various Microsoft sources:

The multi() syntax indicates to Windows NT that it should rely on the
system BIOS to load system files. This means that NTLDR, the boot loader
for x86-based computers, will be using interrupt (INT) 13 BIOS calls to
find and load Ntoskrnl.exe and any other files it needs to get the
system running.

In the multi(X)disk(Y)rdisk(Z)partition(W)\%systemroot% syntax:

The X, Y, Z, and W parameters have the following meaning:

* X is the ordinal number of the adapter and should always be 0
(see the text below for the reason).

* Y is always 0 (zero) if the ARC path starts with MULTI(), because
MULTI() invokes the INT 13 call as described above and therefore does
not need the DISK() parameter information.

* Z is the ordinal for the disk on the adapter and is usually a
number between 0 and 3.

* W is the partition number. All partitions receive a number except
for type 5 (MS-DOS Extended) and type 0 (unused) partitions, with
primary partitions being numbered first and then logical drives. NOTE:
The first valid number for W is 1, as opposed to X, Y, and Z which start
at 0 (zero).

Theoretically, this syntax could be used to start Windows NT on any
drive in the system. However, this would require that all drives are
correctly identified through the standard INT 13 interface; since
support for this varies from disk controller to disk controller and most
system BIOS only identify a single disk controller through INT 13, in
practice it is only safe to use this syntax to start Windows NT from the
first two drives connected to the primary disk controller, or the first
four drives in the case of a dual-channel EIDE controller.

In a pure IDE system, the MULTI() syntax will work for up to the four
drives maximum on the primary and secondary channels of a dual-channel
controller.

http://support.microsoft.com/kb/102873
http://www.microsoft.com/technet/pr...serv/reskit/prork/prbd_std_ccef.mspx?mfr=true
http://technet.microsoft.com/en-us/library/cc751045.aspx

John
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top