Your message dated Wed, 08 Sep 2010 03:58:20 +0000 with message-id <E1OtBng-0005OS-8U@ravel.debian.org> and subject line Closing old installation report #397133 has caused the Debian Bug report #397133, regarding boot problem after installation 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.) -- 397133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=397133 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: <submit@bugs.debian.org>
- Subject: boot problem after installation
- From: "Igor Hoveijn" <ihoveijn@zonnet.nl>
- Date: Sun, 5 Nov 2006 13:34:49 +0100
- Message-id: <000801c700d6$da068450$8a866391@laptopigor>
Package: installation-reports
Boot method: DVD
Image version: from DVD1: "Debian 3.1r3 Released 31 August 2006", kernel-image-2.4.27-2-386, purchased on november 2, 2006, from "delinuxspecialist.nl"
Date: november 4, 2006
Machine: HP Compaq nx9110
Processor: Pentium 4 2.8GHz
Memory: 704 MB
Partitions:according to debian-installer:ide1 master (hda) - 40.0 GB HITACHI_DK23FA-40
#1 primary 5.2 GB ntfs
#4 primary 23.7 GB fat32
#2 primary 10.6 GB ext3 /
#5 logical 493.5 MB swap swapcontents of /target/etc/fstab:proc /proc proc defaults 0 0
/dev/hda2 / ext3 defaults,errors=remount-ro 0 1
/dev/hda5 none swap rw 0 0
/dev/hdc /media/cdrom0 iso9660 ro,user,noauto 0 0Output of lspci and lspci -n: I am unable to run lspciBase System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [-] = didn't try itInitial boot worked: [E]
Configure network HW: [-]
Config network: [-]
Detect CD: [0]
Load installer modules: [0]
Detect hard drives: [0]
Partition hard drives: [0]
Create file systems: [0]
Mount partitions: [0]
Install base system: [0]
Install boot loader: [0] (grub)
Reboot: [-]Comments/Problems:After installing base system, first boot into new system fails, messages:pivot_root: no such file or directory
/sbin/init: 432 cannot open dev/console
kernel panic: Attempted to kill init!boot commands from the grub menu:root (hd0,1)
kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/hda2 ro
initrd /boot/initrd.img-2.4.27-2-386
savedefault
boot
Dear N,I am having a boot problem during installation. Please see below for
details. If you need other details or specifications please let me
know. Any help will be greatly appreciated.Yours,Igor Hoveijn
Problem: Unable to boot into system after installation of base systemError message: kernel panic: Attempted to kill init!History:Initial system with four partitions, first two windows partitions then
two linux partitions containing other linux distribution.Obtained Debian linux on two DVD. Boot system from DVD1, deleted two
linux partitons and used debian-installer to automatically partition
the free space. Further with debian installation, no problems. After
installation of grub the installer suggests to boot the new system for
the first time, which results in a kernel panic.Searched the web for 'attempted to kill init' etc. Can't use the hints
because I can't get to the file system. I don't have a rescue CD,
didn't get the chance to make one. Had to copy the partition table
from screen. Please see below for contents of /target/etc/fstab. Also
/target/dev exists and /target/dev/console. At least just before I
said OK to try the first boot.It seems that I'm stuck here.
--- End Message ---
--- Begin Message ---
- To: 397133-done@bugs.debian.org
- Subject: Closing old installation report #397133
- From: Christian Perrier <bubulle@debian.org>
- Date: Wed, 08 Sep 2010 03:58:20 +0000
- Message-id: <E1OtBng-0005OS-8U@ravel.debian.org>
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 ---