Bug#57094: marked as done (cannot boot from compaq SmartArray 221 with frozen boot-floppies 2.2.5)
Your message dated 15 Mar 2000 03:04:14 -0500
with message-id <oa3dpsfym9.fsf@arroz.fake>
and subject line bugs fixed in previous upload
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Darren Benham
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 5 Feb 2000 15:45:47 +0000
Received: (qmail 11682 invoked from network); 5 Feb 2000 15:45:46 -0000
Received: from godzilla.contigo.com (209.75.193.5)
by master.debian.org with SMTP; 5 Feb 2000 15:45:46 -0000
Received: (from lmoore@localhost)
by godzilla.contigo.com (8.9.3/8.9.3/Debian 8.9.3-6) id HAA10058;
Sat, 5 Feb 2000 07:45:45 -0800
Sender: lmoore@contigo.com
To: submit@bugs.debian.org
Subject: cannot boot from compaq SmartArray 221 with frozen boot-floppies 2.2.5
X-Now-Playing: republica / republica / ready to go-us mix
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
From: lantz moore <lmoore@contigo.com>
Date: 05 Feb 2000 07:45:45 -0800
Message-ID: <86og9vk5zq.fsf@godzilla.contigo.com>
Lines: 18
User-Agent: Gnus/5.07008 (Pterodactyl Gnus v0.80) XEmacs/20.4 (Emerald)
Package: boot-floppies
Version: 2.2.5
hi. i'm attempting to install frozen on a compaq proliant 1600 with a
SmartArray 221 controller providing a raid5 boot device. i'm using the
'compact' flavor of boot disks.
everything goes smoothly up until the first reboot. that is, i can see
the raid controller, partition the disk, and install/configure the base
system. i made the drive bootable and a boot floppy. when i attempt to
boot from the raid, i never receive a lilo prompt. when i attempt to boot
from the boot (or rescue) disk, i receive a VFS kernel panic about not
being able to mount the device at 00:00. during the boot process (from
the boot disk) the kernel *does* see the SmartArray and the partitions.
--
lantz moore, contigo software lmoore@contigo.com
---------------------------------------
Received: (at 57094-done) by bugs.debian.org; 15 Mar 2000 07:22:16 +0000
Received: (qmail 4963 invoked from network); 15 Mar 2000 07:22:14 -0000
Received: from 216-164-253-50.s50.tnt6.nyw.ny.dialup.rcn.com (HELO arroz.fake) (@216.164.253.50)
by master.debian.org with SMTP; 15 Mar 2000 07:22:14 -0000
Received: by arroz.fake (Postfix, from userid 421)
id E39DF93858; Wed, 15 Mar 2000 03:04:14 -0500 (EST)
Sender: apharris@arroz.fake
To: 36412-done@bugs.debian.org, 38144-done@bugs.debian.org,
48637-done@bugs.debian.org, 50014-done@bugs.debian.org,
53113-done@bugs.debian.org, 54130-done@bugs.debian.org,
56600-done@bugs.debian.org, 56960-done@bugs.debian.org,
57094-done@bugs.debian.org, 57110-done@bugs.debian.org,
57114-done@bugs.debian.org, 57119-done@bugs.debian.org,
57344-done@bugs.debian.org, 57364-done@bugs.debian.org,
57366-done@bugs.debian.org, 57372-done@bugs.debian.org,
57672-done@bugs.debian.org, 57736-done@bugs.debian.org,
57738-done@bugs.debian.org, 57783-done@bugs.debian.org,
58006-done@bugs.debian.org, 58009-done@bugs.debian.org,
58387-done@bugs.debian.org, 59156-done@bugs.debian.org,
59187-done@bugs.debian.org
Subject: bugs fixed in previous upload
From: Adam Di Carlo <adam@onshore.com>
Date: 15 Mar 2000 03:04:14 -0500
Message-ID: <oa3dpsfym9.fsf@arroz.fake>
Lines: 11
User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.5
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
We believe the bug you reported has been fixed as of the Potato boot flopppies,
version 2.2.8. Please let us know if not.
Remember that often bugs are filed against boot-floppies, when the should
be filed against modconf, base-config, kernel-image-2.2.14, or other
related packages. Please do you best to track down which package is the
culprit when creating bugs.
--
.....Adam Di Carlo....adam@onShore.com.....<URL:http://www.onShore.com/>
Reply to: