Re: During reinstallation I'm told that setup can't find the hard drive/mass storage device - whY?

I'll move the "Gb NIC1" item up in the boot sequence. Odd thing is that
that list is handled by BIOS; I can't alter what's on it without actually
install physical devices. The Hard-Disk Drive Sequence is also
handled/populated by the BIOS.
I thought it odd, too, that the RAID device wasn't listed on the boot
sequence; I can only guess that the Gb NIC1 item is a part of it.

Mike

"Jim Behning" <jimbehning@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:gka7i2de4kjnaqrdp6dd1dag8ph3lsir3c@xxxxxxxxxx
If it is booting off the PERC then you need that driver with F6. The
29160 is ancient and the drivers on the OS setup should work. Besides
that the tape drive is probably hooked up to the 29160. I have seen
the message that the OS install has a newer driver than what is on
your floppy. Sometimes the newer driver has not worked but the floppy
did.

On an Intel server board the raid should be up high in the boot
sequence. I do not see any Perc listed in your boot sequence. I
thought Dell was just Intel with a Dell logo on it.

On Wed, 4 Oct 2006 06:36:48 -0500, "Mike Webb"
<mike_webb@xxxxxxxxxxxxxxxxx> wrote:

In answer to both of you, I have the following:

Adaptec SCSI Card 29160 Ultra160 SCSI
driver: adpu160m.sys ver. 6.4.630.100
DELL PERC 4e/Di RAID Controller
driver: mraid35x.sys

Server: DELL Power Edge 2800, BIOS ver. A05

Boot Sequence (from BIOS)
1. Diskette Drive A:
2. IDE CD-ROM Device
3. Hard Drive C:
4. Embedded Gb NIC1 IBA GE Slot 0B38 v1226

Hard-Disk Drive Sequence (from BIOS)
1. System BIOS boot devices
2. Embedded PERC 4e/Di Adapter(bus 02 dev 0E)

I've got both drivers on diskette now. I'm assuming that I need to use
both
from F6 during the Setup phase?

Mike

<mike_webb@xxxxxxxxxxxxxxxxx> wrote in message
news:1159889681.364263.41770@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks for the question; I'll check the boot sequence and report back.

Mike

Steve wrote:
As Charlie suggests we'd need to know the specific Adaptec SCSI RAID
card
you're using, but I do know that Windows 2003 has native support for
the
older 2100S series. Also is booting from the RAID controller enabled in
your
BIOS? If not I don't think the Windows install routine will see it
either.

"Charlie Russel - MVP" <charlie@xxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:A97605A0-028A-49BD-89D3-04ED6ACFA43F@xxxxxxxxxxxxxxxx
You have two choices when running an installation. If you run the
installation from within an existing Windows installation, as an in
place
upgrade, you can generally avoid having to have a floppy disk with
the
necessary drivers on it. However, it what you're trying to do is do a
fresh install, you need to either use a type of disk controller that
has
built in drivers in Server 2003, or you need to provide the drivers
on
a
floppy drive. When you first boot off the CD to install SBS you'll
see
"Press F6 to specify additional mass storage, etc." at the bottom of
the
screen. Press F6 and you'll eventually get prompted to provide the
floppy.
At this point you have to provide the _correct_ drivers for your disk
controller. If you have multiple controllers, the critical one is the
one
that has your boot drive attached to it.

Without more details as to your specific hardware and what drives are
attached to which controllers, I can't be more specific.

--
Charlie.
http://msmvps.com/xperts64


"Mike Webb" <mike_webb@xxxxxxxxxxxxxxxxx> wrote in message
news:esmFOsm5GHA.3920@xxxxxxxxxxxxxxxxxxxxxxx
Running SBS 2003 Premium.
==================
For necessary reasons, I need to reinstall SBS. My problem is right
from
the get-go after setup gets down loading files and drivers to start,
it
tells me it can't detect a hard-drive/mass storage device. That
puzzled
me as it shows up fine during boot-up. After cycling through a
reboot
a
few times, it hit me that I have a SCSI RAID device. So I dug out
the
3.25 in floppy (ADAPTEC Family Manager Set v4.0a Utility Disk) and
plopped it in the drive and went to the setup. I selected the SCSI
drive
from the list presented, and then setup told me that the file
already
in
windows was newer than what was on the diskette, and asked me
whether
to
replace or keep the file. I chose to keep the newest file. It then
went
to the next window to tell me it still couldn't find the
hard-drive/mass
storage device.
Very frustrating!
Can someone please tell me how to convince setup that there IS a
hard-drive/mass storage device?
--
Mike Webb
Platte River Whooping Crane Maintenance Trust, Inc.
a 501 (c)(3) non-profit org.
Wood River, NE






.

Relevant Pages

  • Re: CD-Rom not recognized in: BIOS or Device Mgr. or my computer
    ... see if their is any mention of needing drivers to access the CD ... This is either a BIOS problem, ... I changed the boot order and enabled the CD-Rom in the BIOS and it would ...
    (microsoft.public.windowsxp.hardware)
  • Re: BIOS and basic hardware drivers
    ... If I try to boot the debian cd ... installation disk without offering any alternative boot method in BIOS, ... drivers that enables the system to function prior to boot. ...
    (comp.os.linux.hardware)
  • Re: external eSata enclosure drive recognition?
    ... Probes by the BIOS, to the configuration space of the SIL3132, will ... If the above BIOS chip, has INT 0x13 code present, then that storage card ... SIL3132 cannot be used to boot the computer. ... that a lot of drivers run their initialization code, ...
    (microsoft.public.windowsxp.hardware)
  • Re: XP Home install doesnt complete
    ... You may have to use the floppy disk with the SATA drivers during the 2nd ... boot in the system install sequence, as well as during the first part. ... >>> I've read something about xp not recognising SATA drives and at the F6 ...
    (microsoft.public.windowsxp.general)
  • Re: BIOS and basic hardware drivers
    ... If I try to boot the debian cd ... installation disk without offering any alternative boot method in BIOS, ... drivers that enables the system to function prior to boot. ...
    (comp.os.linux.hardware)