Your message dated Fri, 08 Jul 2005 09:33:41 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#281724: fixed in lilo-installer 1.11
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.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 17 Nov 2004 14:26:30 +0000
>From [EMAIL PROTECTED] Wed Nov 17 06:26:30 2004
Return-path: <[EMAIL PROTECTED]>
Received: from fm100.galaradio.com (mail.galaradio.com) [194.183.167.226]
by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
id 1CUQlO-00051x-00; Wed, 17 Nov 2004 06:26:28 -0800
Received: from zulu.gala ([10.0.0.14] helo=zulu)
by mail.galaradio.com with esmtp (Exim 3.35 (GalaradioMail))
id 1CUQlI-0008F8-00
for <[EMAIL PROTECTED]>; Wed, 17 Nov 2004 16:26:20 +0200
Received: from zulu by zulu with local (Exim 4.34)
id 1CUQnF-0005zV-3y
for [EMAIL PROTECTED]; Wed, 17 Nov 2004 16:28:21 +0200
Date: Wed, 17 Nov 2004 16:28:21 +0200
From: "Alexander A. Vlasov" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: problem with root on software raid
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=koi8-u
Content-Disposition: inline
User-Agent: Mutt/1.5.6+20040907i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Package: installation-reports
Debian-installer-version: pre-rc2
uname -a: various
Date: November 2004
Method: from CD (sarge-i386-businesscard)
Machine: various
Processor: various x86
Memory: various, 128M .. 1G
Root Device: software raid
Root Size/partition table: root on /dev/md0, consisting of a pair of
identical partitions on two disks. Tried both ide & scsi.
Output of lspci and lspci -n: various
Initial boot worked: [O]
Configure network HW: [O]
Config network: [O]
Detect CD: [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [O]
Create file systems: [O]
Mount partitions: [O]
Install base system: [O]
Install boot loader: [E]
Reboot: [O]
Comments/Problems:
Recently I installed sarge on a few machines (~5), and I used a software
raid as a root device. Installation progress was successfull until
bootloader has to be installed.
When I tried a "next step -- install bootloader", I got a choice: where
MBR should be placed. Menu consisted of three options: "/dev/md0: root
device", "/dev/md0: new debian partition" and "other: for experts".
I tried /dev/md0 (both of. They are the same, I suspect). I got a
pop-up, saying that /dev/md0 isn't active. (During partitioning. I
marked both partitions /dev/md0 consist of as "bootable"). Popup asked,
if I want to make /dev/md0 active. When I selected "yes", I got the
error message saying "An error occured during installing boot
loader", and I returned to previous menu. When I selected "no", I got a
message saying "error: lilo returns -1 as exit code", and again, I was
returned to previous menu.
So only way to install was select "do not make /dev/md0 active", get an
error (during this step, file /etc/lilo.conf on /target was created),
log in on second console, chroot to /target, manually edit
/etc/lilo.conf, appending 'raid-extra-boot=mbr-only', manually run lilo,
return to first console and select "continue without bootloader". After
this, everything is went OK. Reboot, base config and so on...
This bug/strange behavior is 100% reproduceable, I get it five times
during five installs.
--
WBR, Alexander A. Vlasov
Gala.Net System Administrator
+38(039)2476081
nic-hdl: ZULU-UANIC
---------------------------------------
Received: (at 281724-close) by bugs.debian.org; 8 Jul 2005 13:41:23 +0000
>From [EMAIL PROTECTED] Fri Jul 08 06:41:23 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Dqt6Z-0000gV-00; Fri, 08 Jul 2005 06:41:23 -0700
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1Dqsz7-0004M3-00; Fri, 08 Jul 2005 09:33:41 -0400
From: Joey Hess <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#281724: fixed in lilo-installer 1.11
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Fri, 08 Jul 2005 09:33:41 -0400
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
X-CrossAssassin-Score: 2
Source: lilo-installer
Source-Version: 1.11
We believe that the bug you reported is fixed in the latest version of
lilo-installer, which is due to be installed in the Debian FTP archive:
lilo-installer_1.11.dsc
to pool/main/l/lilo-installer/lilo-installer_1.11.dsc
lilo-installer_1.11.tar.gz
to pool/main/l/lilo-installer/lilo-installer_1.11.tar.gz
lilo-installer_1.11_i386.udeb
to pool/main/l/lilo-installer/lilo-installer_1.11_i386.udeb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Joey Hess <[EMAIL PROTECTED]> (supplier of updated lilo-installer package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Fri, 8 Jul 2005 15:02:06 +0300
Source: lilo-installer
Binary: lilo-installer
Architecture: source i386
Version: 1.11
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team <[email protected]>
Changed-By: Joey Hess <[EMAIL PROTECTED]>
Description:
lilo-installer - Install LILO on a hard disk (udeb)
Closes: 265900 281724
Changes:
lilo-installer (1.11) unstable; urgency=low
.
[ Joshua Kwan ]
* Add '-follow' to find arguments, or else nothing will be found when
$prefix == /dev/discs.
[ Colin Watson ]
* Make sure that the boot disk always has an active partition, unless
the user explicitly chose not to make the boot partition active (part
of Ubuntu bug #7906).
[ Matt Kraai ]
* Fix the spelling of "boot loader".
[ Joey Hess ]
* Patch from Eugeniy Meshcheryako to add raid-extra-boot=mbr-only
to lilo.conf for software raid (Closes: #281724) and to add a new, working
menu for raid (Closes: #265900)
.
* Updated translations:
- Arabic (ar.po) by Ossama M. Khayat
- Danish (da.po) by Claus Hindsgaul
- Greek, Modern (1453-) (el.po) by Greek Translation Team
- Spanish (es.po) by Javier Fernández-Sanguino Peña
- Basque (eu.po) by Piarres Beobide
- Hebrew (he.po) by Lior Kaplan
- Italian (it.po) by Giuseppe Sacco
- Lithuanian (lt.po) by KÄstutis BiliÅ«nas
- Portuguese (pt.po) by Miguel Figueiredo
- Portuguese (Brazil) (pt_BR.po) by André LuÃs Lopes
- Romanian (ro.po) by Eddy PetriÅor
- Russian (ru.po) by Yuri Kozlov
- Slovak (sk.po) by Peter Mann
- Ukrainian (uk.po) by Eugeniy Meshcheryakov
- Vietnamese (vi.po) by Clytie Siddall
- Simplified Chinese (zh_CN.po) by Carlos Z.F. Liu
Files:
c3ed517a20b7fcf9690c84823a7dff10 640 debian-installer standard
lilo-installer_1.11.dsc
fb233552a2448db42dc33d80d0e4c879 62620 debian-installer standard
lilo-installer_1.11.tar.gz
90a25b57b7a7d541e347880b1993718b 45412 debian-installer standard
lilo-installer_1.11_i386.udeb
package-type: udeb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCznxV2tp5zXiKP0wRAgPGAJ45p6X0u29Bc5pwPamb8hcVWyGVnwCgxS2n
aNUYEg0rDi//Wvf7wVGDcnM=
=Dmua
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
