[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#505964: marked as done (Package: installation-reports)



Your message dated Mon, 10 Jan 2011 21:19:18 +0000
with message-id <1294694358.2490.4.camel@eeepc.Belkin>
and subject line 
has caused the Debian Bug report #505964,
regarding Package: installation-reports
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.)


-- 
505964: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505964
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports

Boot method: CD
Image version: http://cdimage.debian.org/cdimage/lenny_di_rc1/amd64/iso-cd/debian-testing-amd64-netinst.iso
Date: 2008-11-17

Machine: Fujitsu Siemens Primergy RX300 S4
Processor: Intel(R) Xeon(R) CPU   E5440 @ 2.83GHz
Memory: 32 GB
Partitions: 
  Disk /dev/sda: 1462.6 GB, 1462637690880 bytes
  255 heads, 63 sectors/track, 177822 cylinders
  Units = cylinders of 16065 * 512 = 8225280 bytes
  Disk identifier: 0x0005eaf8
   
     Device Boot      Start         End      Blocks   Id  System
  /dev/sda1   *           1          31      248976   83  Linux
  /dev/sda2              32      177822  1428106207+  8e  Linux LVM
   
 
  Filesystem    Type   1K-blocks      Used Available Use% Mounted on
  /dev/mapper/voyager-root
                ext3      959512    134272    776500  15% /
  tmpfs        tmpfs    16511824         0  16511824   0% /lib/init/rw
  udev         tmpfs       10240        76     10164   1% /dev
  tmpfs        tmpfs    16511824         0  16511824   0% /dev/shm
  /dev/mapper/voyager-tmp
                ext3      376807     10287    347064   3% /tmp
  /dev/mapper/voyager-usr
                ext3     4805760    327452   4234188   8% /usr
  /dev/mapper/voyager-var
                 xfs   195214204    143812 195070392   1% /var


Output of lspci -knn (or lspci -nn):
  00:00.0 Host bridge [0600]: Intel Corporation 5000P Chipset Memory Controller Hub [8086:25d8] (rev 92)
  00:02.0 PCI bridge [0604]: Intel Corporation 5000 Series Chipset PCI Express x8 Port 2-3 [8086:25f7] (rev 92)
  	Kernel driver in use: pcieport-driver
  	Kernel modules: shpchp
  00:03.0 PCI bridge [0604]: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 [8086:25e3] (rev 92)
  	Kernel driver in use: pcieport-driver
  	Kernel modules: shpchp
  00:04.0 PCI bridge [0604]: Intel Corporation 5000 Series Chipset PCI Express x4 Port 4 [8086:25e4] (rev 92)
  	Kernel driver in use: pcieport-driver
  	Kernel modules: shpchp
  00:05.0 PCI bridge [0604]: Intel Corporation 5000 Series Chipset PCI Express x4 Port 5 [8086:25e5] (rev 92)
  	Kernel driver in use: pcieport-driver
  	Kernel modules: shpchp
  00:06.0 PCI bridge [0604]: Intel Corporation 5000 Series Chipset PCI Express x8 Port 6-7 [8086:25f9] (rev 92)
  	Kernel driver in use: pcieport-driver
  	Kernel modules: shpchp
  00:07.0 PCI bridge [0604]: Intel Corporation 5000 Series Chipset PCI Express x4 Port 7 [8086:25e7] (rev 92)
  	Kernel driver in use: pcieport-driver
  	Kernel modules: shpchp
  00:10.0 Host bridge [0600]: Intel Corporation 5000 Series Chipset FSB Registers [8086:25f0] (rev 92)
  	Kernel driver in use: i5000_edac
  	Kernel modules: i5000_edac
  00:10.1 Host bridge [0600]: Intel Corporation 5000 Series Chipset FSB Registers [8086:25f0] (rev 92)
  	Kernel modules: i5000_edac
  00:10.2 Host bridge [0600]: Intel Corporation 5000 Series Chipset FSB Registers [8086:25f0] (rev 92)
  	Kernel modules: i5000_edac
  00:11.0 Host bridge [0600]: Intel Corporation 5000 Series Chipset Reserved Registers [8086:25f1] (rev 92)
  00:13.0 Host bridge [0600]: Intel Corporation 5000 Series Chipset Reserved Registers [8086:25f3] (rev 92)
  00:15.0 Host bridge [0600]: Intel Corporation 5000 Series Chipset FBD Registers [8086:25f5] (rev 92)
  00:16.0 Host bridge [0600]: Intel Corporation 5000 Series Chipset FBD Registers [8086:25f6] (rev 92)
  00:1c.0 PCI bridge [0604]: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 1 [8086:2690] (rev 09)
  	Kernel driver in use: pcieport-driver
  	Kernel modules: shpchp
  00:1c.1 PCI bridge [0604]: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 2 [8086:2692] (rev 09)
  	Kernel driver in use: pcieport-driver
  	Kernel modules: shpchp
  00:1c.2 PCI bridge [0604]: Intel Corporation 631xESB/632xESB/3100 Chipset PCI Express Root Port 3 [8086:2694] (rev 09)
  	Kernel driver in use: pcieport-driver
  	Kernel modules: shpchp
  00:1d.0 USB Controller [0c03]: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #1 [8086:2688] (rev 09)
  	Kernel driver in use: uhci_hcd
  	Kernel modules: uhci-hcd
  00:1d.1 USB Controller [0c03]: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #2 [8086:2689] (rev 09)
  	Kernel driver in use: uhci_hcd
  	Kernel modules: uhci-hcd
  00:1d.2 USB Controller [0c03]: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #3 [8086:268a] (rev 09)
  	Kernel driver in use: uhci_hcd
  	Kernel modules: uhci-hcd
  00:1d.3 USB Controller [0c03]: Intel Corporation 631xESB/632xESB/3100 Chipset UHCI USB Controller #4 [8086:268b] (rev 09)
  	Kernel driver in use: uhci_hcd
  	Kernel modules: uhci-hcd
  00:1d.7 USB Controller [0c03]: Intel Corporation 631xESB/632xESB/3100 Chipset EHCI USB2 Controller [8086:268c] (rev 09)
  	Kernel driver in use: ehci_hcd
  	Kernel modules: ehci-hcd
  00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev d9)
  00:1f.0 ISA bridge [0601]: Intel Corporation 631xESB/632xESB/3100 Chipset LPC Interface Controller [8086:2670] (rev 09)
  	Kernel modules: intel-rng, iTCO_wdt
  00:1f.2 IDE interface [0101]: Intel Corporation 631xESB/632xESB/3100 Chipset SATA IDE Controller [8086:2680] (rev 09)
  	Kernel driver in use: ata_piix
  	Kernel modules: ata_generic, ata_piix, ide-pci-generic
  00:1f.3 SMBus [0c05]: Intel Corporation 631xESB/632xESB/3100 Chipset SMBus Controller [8086:269b] (rev 09)
  	Kernel driver in use: i801_smbus
  	Kernel modules: i2c-i801
  01:00.0 PCI bridge [0604]: Intel Corporation 6311ESB/6321ESB PCI Express Upstream Port [8086:3500] (rev 01)
  	Kernel driver in use: pcieport-driver
  	Kernel modules: shpchp
  01:00.3 PCI bridge [0604]: Intel Corporation 6311ESB/6321ESB PCI Express to PCI-X Bridge [8086:350c] (rev 01)
  	Kernel modules: shpchp
  02:00.0 PCI bridge [0604]: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E1 [8086:3510] (rev 01)
  	Kernel driver in use: pcieport-driver
  	Kernel modules: shpchp
  02:01.0 PCI bridge [0604]: Intel Corporation 6311ESB/6321ESB PCI Express Downstream Port E2 [8086:3514] (rev 01)
  	Kernel driver in use: pcieport-driver
  	Kernel modules: shpchp
  08:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID SAS 1078 [1000:0060] (rev 04)
  	Kernel driver in use: megaraid_sas
  	Kernel modules: megaraid_sas
  0b:00.0 VGA compatible controller [0300]: Matrox Graphics, Inc. MGA G200e [Pilot] ServerEngines (SEP1) [102b:0522] (rev 02)
  0c:00.0 PCI bridge [0604]: Broadcom EPB PCI-Express to PCI-X Bridge [1166:0103] (rev c3)
  	Kernel modules: shpchp
  0d:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet [14e4:164c] (rev 12)
  	Kernel driver in use: bnx2
  	Kernel modules: bnx2
  0e:00.0 PCI bridge [0604]: Broadcom EPB PCI-Express to PCI-X Bridge [1166:0103] (rev c3)
  	Kernel modules: shpchp
  0f:00.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet [14e4:164c] (rev 12)
  	Kernel driver in use: bnx2
  	Kernel modules: bnx2
  
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:           [O]
Detect network card:    [O]
Configure network:      [O]
Detect CD:              [O]
Load installer modules: [O]
Detect hard drives:     [O]
Partition hard drives:  [O]
Install base system:    [O]
Clock/timezone setup:   [O]
User/password setup:    [O]
Install tasks:          [ ]
Install boot loader:    [E]
Overall install:        [E]

Comments/Problems:
The system cannot mount the root file system after install and 
boots into busybox.

<snip type="boot message">
Loading, please wait...
   5 logical volume(s) in volume group "voyager" now active
xinit: name_to_dev_t(/dev/mapper/voyager-swap_1) = dm-1(254,1)
xinit: trying to resume from /dev/mapper/voyager-swap_1)
xinit: No resume image, doing normal boot...
mount: mounting /dev/root on /root failed: No such device
mount: mounting /dev on /root/dev failed: No such file or directory
mount: mounting /sys on /root/sys failed: No such file or directory
mount: mounting /proc on /root/proc failed: No such file or directory
Target filesystem doesn't have /sbin/init.
No init found. Try passing init= bootarg.
</snip>

I had to explicitely specify the root partition at the 
lilo prompt:
  Linux root=/dev/mapper/voyager-root
to boot into the system.

Running lilo (on an unmodified /etc/lilo.conf) makes the system bootable without the need
to specify the root partition (or anything else) at the lilo prompt.

<snip file="/etc/lilo.conf>
# Automatically added by lilo postinst script
large-memory

# /etc/lilo.conf - See: `lilo(8)' and `lilo.conf(5)',
# ---------------       `install-mbr(8)', `/usr/share/doc/lilo/',
#                       and `/usr/share/doc/mbr/'.

# +---------------------------------------------------------------+
# |                        !! Reminder !!                         |
# |                                                               |
# | Don't forget to run `lilo' after you make changes to this     |
# | conffile, `/boot/bootmess.txt' (if you have created it), or   |
# | install a new kernel.  The computer will most likely fail to  |
# | boot if a kernel-image post-install script or you don't       |
# | remember to run `lilo'.                                       |
# |                                                               |
# +---------------------------------------------------------------+

# Specifies the boot device.  This is where Lilo installs its boot
# block.  It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/sda

# Specifies the device that should be mounted as root. (`/')
#
root=/dev/mapper/voyager-root

# This option may be needed for some software RAID installs.
#
# raid-extra-boot=mbr-only

# Enable map compaction:
# Tries to merge read requests for adjacent sectors into a single
# read request. This drastically reduces load time and keeps the
# map smaller.  Using `compact' is especially recommended when
# booting from a floppy disk.  It is disabled here by default
# because it doesn't always work.
#
# compact

# Installs the specified file as the new boot sector
# You have the choice between: text, bmp, and menu
# Look in lilo.conf(5) manpage for details
#
#install=menu

# Specifies the location of the map file
#
map=/boot/map

# You can set a password here, and uncomment the `restricted' lines
# in the image definitions below to make it so that a password must
# be typed to boot anything but a default configuration.  If a
# command line is given, other than one specified by an `append'
# statement in `lilo.conf', the password will be required, but a
# standard default boot will not require one.
#
# This will, for instance, prevent anyone with access to the
# console from booting with something like `Linux init=/bin/sh',
# and thus becoming `root' without proper authorization.
#
# Note that if you really need this type of security, you will
# likely also want to use `install-mbr' to reconfigure the MBR
# program, as well as set up your BIOS to disallow booting from
# removable disk or CD-ROM, then put a password on getting into the
# BIOS configuration as well.  Please RTFM `install-mbr(8)'.
#
# password=tatercounter2000

# Specifies the number of deciseconds (0.1 seconds) LILO should
# wait before booting the first image.
#
delay=20

# You can put a customized boot message up if you like.  If you use
# `prompt', and this computer may need to reboot unattended, you
# must specify a `timeout', or it will sit there forever waiting
# for a keypress.  `single-key' goes with the `alias' lines in the
# `image' configurations below.  eg: You can press `1' to boot
# `Linux', `2' to boot `LinuxOLD', if you uncomment the `alias'.
#
# message=/boot/bootmess.txt
#	prompt
#	delay=100
#	timeout=100

# Specifies the VGA text mode at boot time. (normal, extended, ask, <mode>)
#
# vga=ask
# vga=9
#


# Kernel command line options that apply to all installed images go
# here.  See: The `boot-prompt-HOWTO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""
 
# If you used a serial console to install Debian, this option should be
# enabled by default.
# serial=

#
# Boot up Linux by default.
#
default=Linux

image=/vmlinuz
	label=Linux
	read-only
#	restricted
#	alias=1
    append="quiet"
	initrd=/initrd.img

image=/vmlinuz.old
	label=LinuxOLD
	read-only
	optional
#	restricted
#	alias=2
    append="quiet"
	initrd=/initrd.img.old


# If you have another OS on this machine to boot, you can uncomment the
# following lines, changing the device name on the `other' line to
# where your other OS' partition is.
#
# other=/dev/hda4
#	label=HURD
#	restricted
#	alias=3
</snip>



--- End Message ---
--- Begin Message ---
Thanks for your report.
Closing as it's an installation report.
Feel free to test and report against the current debian installer
release (Squeeze Beta2).

-- 
Melhores cumprimentos/Best regards,

Miguel Figueiredo
http://www.DebianPT.org



--- End Message ---

Reply to: