|
|||||||||||
|
Bug#324446: marked as done (Failed while installing LILO because /boot was already mounted outside of the /target)
From: Debian Bug Tracking System <owner(at)bugs.debian.org>
Date: Sun Sep 30 2007 - 17:54:05 EDT
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) attached mail follows:
Package: debian-installer
When installing SID with a recent installer nightly, LILO failed to install:
Setting up lilo (22.6.1-6.2) ...
My partition scheme is as follows: hda1 primary ext2 /boot 41.13 MB hda2 primary ReiserFS / 15002.92 MB hda3 primary ReiserFS /home 23960.25 hda4 primary swap 1003.49 (Yeah, I'm sure that my partitioning scheme is poorly thought out.) I'll mention another problem for which I will not open a separate report as I believe that it is another facet of the fundamental problem: To fix this problem, I umounted /boot, chrooted to /target, mounted /boot, and tried again (if I am correctly remembering the order of events), this time getting a different error: 'Fatal: open /vmlinuz: No such file or directory'. I had to re-install (with dpkg) the kernel and try again before it finally worked. I am guessing that this is because the installer had installed the kernel to the /boot directory on the / partition rather than the /boot partition (in fact, I see it there now when I don't mount /boot). I suspect that this is important because it means that /target/boot needs to be mounted not only for the installation of LILO, but also for the installation of the kernel, if I understand correctly. I still have my installation logs if you need more from them. Much love, -- Miciah Masters attached mail follows:
Source: lilo-installer
Source-Version: 1.24
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.24.dsc
to pool/main/l/lilo-installer/lilo-installer_1.24.dsc
lilo-installer_1.24.tar.gz
to pool/main/l/lilo-installer/lilo-installer_1.24.tar.gz
lilo-installer_1.24_amd64.udeb
to pool/main/l/lilo-installer/lilo-installer_1.24_amd64.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 324446@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jérémy Bobbio <lunar@debian.org> (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 ftpmaster@debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Sun, 30 Sep 2007 23:33:03 +0200
Source: lilo-installer
Binary: lilo-installer
Architecture: source amd64
Version: 1.24
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team <debian-boot@lists.debian.org>
Changed-By: Jérémy Bobbio <lunar@debian.org>
Description:
lilo-installer - Install LILO on a hard disk (udeb)
Closes: 294881 322037 324446 341380 432314 441016
Changes:
lilo-installer (1.24) unstable; urgency=low
.
[ Jérémy Bobbio ]
This archive was generated by hypermail 2.1.8 : Sun Oct 07 2007 - 00:29:02 EDT |
||||||||||
|
|||||||||||