Bug#327287: marked as done (Cannot boot Sarge boot disk on Proliant 1500)
Your message dated Wed, 08 Sep 2010 03:58:04 +0000
with message-id <E1OtBnQ-0004qc-2a@ravel.debian.org>
and subject line Closing old installation report #327287
has caused the Debian Bug report #327287,
regarding Cannot boot Sarge boot disk on Proliant 1500
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
327287: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=327287
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: debian-31r0a-i386-netinst.iso
Version: 31r0a
When I try to install the latest stable version of Debian (Sarge) on my
Compaq Proliant 1500 server (dual Pentium 166 mHz processors, 256 MB
RAM, several SCSI drives), it fails. I gave the boot command line:
expert26 mem=255M sym53c8xx=safe:y . The boot process proceeds till I
get the message: "Kernel panic: VFS: Unable to mount root fs on
unknown_block(0,0)". I also tried booting with linux26, expert, and
linux. I tried giving the memory parameters as "mem=exactmap mem=640K@0
mem=255M@1M" (this did not even get to the point of extracting the
initrd.gz file). I also tried with and without the sym53c8xx=safe:y
parameter.
I have had this problem with all Debian-based distributions for some
time now. I was able to install an earlier version of Sarge (unstable)
before by rebuilding the initrd file to include the sym53c8xx,
sym53c8xx_2 and NCR53c8xx drivers in the modules directory. I also
recompiled the kernel to include these drivers and then rebuilt the boot
ISO to use these. I suspect the problem is that the proper driver for
my NCR SCSI card is no longer included. I'm not sure if my rebuilding
the kernel to include these drivers fixed the problem, or the rebuilding
of the initrd.
Since this problem seems to be getting perpetuated, I thought I'd check
with you to see if it could be repaired so that others won't have this
problem. Also, if you have a workaround to help me install this, I'd
appreciate it.
Thanks very much.
Vic
Walker
--
****************************************************************************
Vic Walker R.Ph., B.C.P.P.
Internet Address(es):
vwalker@pharmdata.net or vwalker@dhs.ca.gov
Printed with 100% recycled electrons.
--- End Message ---
--- Begin Message ---
We are closing this installation report for one of the following
reasons:
- it was reported with a pre-lenny version of Debian
Installer.
- indications in the installation report give the feeling that
the reported problem waslying in another software, unrelated to
D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful
The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet.
In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.
You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the "daily builds section", then choose to
install "squeeze" when prompted.
If some problems are found, please report them with a new bug sent
against installation-reports.
Many thanks for your understanding and your help improving Debian,
past and present.
--- End Message ---
Reply to: