[THIN] Re: inaccessible_boot_device
- From: "Columna, Melvin" <Melvin.Columna@xxxxxxxxx>
- To: "'thin@xxxxxxxxxxxxx'" <thin@xxxxxxxxxxxxx>
- Date: Thu, 24 Jul 2003 12:40:55 -0400
Same here... It will also happen to you if you install any OS based on the
NT Kernel (ie. XP) and having to load 3rd party SCSI/IDE controller drivers
(Promise, SIIG etc..)
-----Original Message-----
From: Kevin Hopley [mailto:khopley@xxxxxxxxxxx]
Sent: Thursday, July 24, 2003 11:49 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: inaccessible_boot_device
Matt
I've seen this on loads of machines with RAID controllers. I've always
resolved it using the old F6 button to manually install the raid controller
driver, during the initial file copy phase.
Kev
-----Original Message-----
From: Matt McComas [mailto:Matt.McComas@xxxxxxxxxxxxxx]
Sent: 24 July 2003 15:27
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] inaccessible_boot_device
BM__MailAutoSigI'm building a really old server for our MFXP lab - a Compaq
Proliant 3000 w/ dual 333 Mhz processors and about 512 MB of RAM.
The odd thing is that after getting through smart start, and the Windows
2000 install copy phase, I enter the text mode portion of setup when it says
"Starting Windows 2000" at the bottom of the blue screen, and then I get a
STOP "inaccessible_boot_device"
Sounds easy enough to troubleshoot-obviously the OS setup is having trouble
seeing the RAID controller...right? So, I researched on Compaq's site and
they suggest flashing BIOS, upgrading RAID controller firmware...
-I flashed BIOS w/ latest version
-I upgraded RAID controller firmware (Raid Controller is a Smart Array 2-DH)
-I even tried using an old version of Smart Start (4.8) instead of the most
recent (for G1 servers) ver. 5.5
Not sure what else to do, though I'm considering manually loading the
correct SCSI driver via a manual setup.
Any ideas?
MMM
Other related posts: