Your message dated Wed, 8 Sep 2004 21:43:56 -0400
with message-id <[EMAIL PROTECTED]>
and subject line fixed
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; 31 Jul 2004 15:09:59 +0000
>From [EMAIL PROTECTED] Sat Jul 31 08:09:59 2004
Return-path: <[EMAIL PROTECTED]>
Received: from boy.univ.kiev.ua (mail.univ.kiev.ua) [193.125.78.122]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BqvUl-0003qv-00; Sat, 31 Jul 2004 08:09:59 -0700
Received: from intel4.icc.univ.kiev.ua (intel4.icc.univ.kiev.ua [10.25.0.243])
by mail.univ.kiev.ua (8.12.2/8.12.2) with ESMTP id i6VF9oHx089410;
Sat, 31 Jul 2004 18:09:51 +0300 (EEST)
Received: from eugen by intel4.icc.univ.kiev.ua with local (Exim 4.34)
id 1BqvUc-0000Kf-Ny; Sat, 31 Jul 2004 18:09:50 +0300
Date: Sat, 31 Jul 2004 18:09:50 +0300
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: installation-reports: failed, root on LVM
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.6+20040722i
From: Eugeniy Meshcheryakov <[EMAIL PROTECTED]>
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: built from svn, today
uname -a: i386
Date: <Date and time of the install>
Method: netboot
Machine: <Description of machine (eg, IBM Thinkpad R32)>
Processor:
Memory:
Root Device: LVM LV
Root Size/partition table: <Feel free to paste the full partition
table, with notes on which partitions are mounted where.>
Output of lspci:
Base System Installation Checklist:
Initial boot worked: [O]
Configure network HW: [O]
Config network: [O]
Detect CD: [ ]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives: [O]
Create file systems: [O]
Mount partitions: [O] see comments
Install base system: [O]
Install boot loader: [E] see comments
Reboot: [O]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Comments/Problems:
I tried to install Debian (testing) with root device on LVM.
Installation failed on boot loader installation step. First time d-i
offered to install grub. I returned to main menu to install lilo. lilo
installation failed. Problem is that root partition (VG vg01, LV
newroot) was mounted as /dev/mapper/vg01-newroot. LVM tools does not
understand logical volumes given in that format. Partition name should
be /dev/vg01/newroot (this file is really symlink to
/dev/mapper/vg01-newroot). d-i must not resolve such symlinks (resolved
name was also writen to /target/etc/fstab!).
After that I tryed to install d-i with low debconf priority. Before
bootloader installation step I unmounted /target and mounted it again
with command:
mount -t ext3 /dev/vg01/newroot /target
Then I choosed to install lilo (into MBR). There was no messages about failed
installation. Screen just blinked. After that main menu appeared with
header in English and menu entries in Ukrainian. Messages in other
dialogs was in English (all messages are translated in Ukrainian in
normal install!). After reboot my old grub bootloader appeared, so lilo
was not installed.
Next try... After lilo install i ran:
chroot /target /sbin/lilo (this code is in lilo-installer too)
Following messages appeared:
Warning: '/proc/partitions' does not exists, disc scan bypassed
Fatal: Sorry, don't know how to handle device 0xfe00
I did not seen such messages on any console before! I mounted
/target/proc and rerun this command. Some warings appeared, no error
messages. After reboot lilo loaded new Debian system.
---------------------------------------
Received: (at 262532-done) by bugs.debian.org; 9 Sep 2004 01:43:14 +0000
>From [EMAIL PROTECTED] Wed Sep 08 18:43:14 2004
Return-path: <[EMAIL PROTECTED]>
Received: from kitenet.net [64.62.161.42] (postfix)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1C5Dxy-0004E7-00; Wed, 08 Sep 2004 18:43:14 -0700
Received: from dragon.kitenet.net (unknown [66.168.94.144])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client CN "Joey Hess", Issuer "Joey Hess" (verified OK))
by kitenet.net (Postfix) with ESMTP id 524B11864F
for <[EMAIL PROTECTED]>; Thu, 9 Sep 2004 01:43:14 +0000 (GMT)
Received: by dragon.kitenet.net (Postfix, from userid 1000)
id AD3E66E2E9; Wed, 8 Sep 2004 21:43:56 -0400 (EDT)
Date: Wed, 8 Sep 2004 21:43:56 -0400
From: Joey Hess <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: fixed
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="GvXjxJ+pjyke8COw"
Content-Disposition: inline
User-Agent: Mutt/1.5.6+20040818i
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=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
--GvXjxJ+pjyke8COw
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
This is fixed.
--=20
see shy jo
--GvXjxJ+pjyke8COw
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFBP7Vbd8HHehbQuO8RAmo5AJ9xj7cvZYJ35l4aKRsu5Wcz4gI1RQCcDS38
XZt4YP1Asun+j05GP+cthmY=
=zNBh
-----END PGP SIGNATURE-----
--GvXjxJ+pjyke8COw--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
