Your message dated Sat, 30 Sep 2006 14:29:33 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Closing a januari 2005 boot failure.
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)
--- Begin Message ---
Package: installation-reports
Severity: important
-- System Information:
Debian Release: 3.1
APT prefers experimental
APT policy: (990, 'experimental'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.9-1-k7
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
INSTALL REPORT
Debian-installer-version:
http://gluck.debian.org/cdimage/testing/sarge_d-i/i386/20041226/sarge-i386-netinst.iso
uname -a: Linux space 2.6.9-1-k7 #1 Thu Nov 25 03:20:07 EST 2004 i686 GNU/Linux
Date: 20041227 0830 EST or 1330 GMT
Method: How did you install? Network Install
What did you install? Sarge
What did you boot off? sarge-i386-netinst.iso dated
2004-12-26
If network install, from where? ftp://ftp.us.debian.org
Proxied? No. Not inline nor traditional.
Machine: Soyo Dragon Ultra Platinum, KT600, VIA Chipset (Hand crafted machine)
Processor: AMD Athlon 3000XP+ Barton
Memory: 1.5GB (333MHz 3x512MB Non-ECC, Unbuffered)
Root Device: IDE Maxtor 6B200P0, /dev/hde2, 3903620 1024K blocks
Floppy Device: NONE
Root Size/partition table:
space:~# fdisk -l /dev/hde
Disk /dev/hde: 203.9 GB, 203928109056 bytes
255 heads, 63 sectors/track, 24792 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hde1 * 1 36 289138+ 83 Linux
/dev/hde2 37 522 3903795 83 Linux
/dev/hde3 523 765 1951897+ 82 Linux swap /
Solaris
/dev/hde4 766 24792 192996877+ f W95 Ext'd (LBA)
/dev/hde5 766 1738 7815591 83 Linux
/dev/hde6 1739 3683 15623181 83 Linux
/dev/hde7 3684 3805 979933+ 83 Linux
/dev/hde8 3806 24792 168578046 83 Linux
space:~# fdisk -l /dev/sda
Disk /dev/sda: 1199.9 GB, 1199956819968 bytes
255 heads, 63 sectors/track, 145886 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 145886 1171829294+ 83 Linux
space:~# fdisk -l /dev/sdb
Disk /dev/sdb: 1427.4 GB, 1427489423360 bytes
255 heads, 63 sectors/track, 173549 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 1 173549 1394032311 83 Linux
space:~# df -H (edited to exclude network and shm)
Filesystem Size Used Avail Use% Mounted on
/dev/hde2 4.0G 146M 3.9G 4% /
/dev/hde1 297M 47M 250M 16% /boot
/dev/sda1 1.2T 985G 216G 83% /exports/finish
/dev/sdb1 1.5T 992G 436G 70% /exports/scratch
/dev/hde8 173G 47M 173G 1% /home
/dev/hde7 1.1G 34M 970M 4% /tmp
/dev/hde5 8.1G 637M 7.4G 8% /usr
/dev/hde6 16G 351M 16G 3% /var
space:/boot/grub# cat /etc/fstab
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options>
<dump> <pass>
proc /proc proc defaults
0 0
/dev/hde2 / reiserfs defaults
0 1
/dev/hde1 /boot reiserfs notail
0 2
/dev/sda1 /exports/finish reiserfs defaults
0 2
/dev/sdb1 /exports/scratch xfs defaults
0 2
/dev/hde8 /home reiserfs defaults
0 2
/dev/hde7 /tmp reiserfs defaults
0 2
/dev/hde5 /usr reiserfs defaults
0 2
/dev/hde6 /var reiserfs defaults
0 2
/dev/hde3 none swap swap
0 0
/dev/hda /media/cdrom0 iso9660 ro,user,noauto
0 0
Output of lspci and lspci -n:
space:~# lspci
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400/KT600
AGP] Host Bridge
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT8235 PCI Bridge
0000:00:08.0 RAID bus controller: 3ware Inc 3ware Inc 3ware
7xxx/8xxx-series PATA/SATA-RAID (rev 01)
0000:00:0a.0 Ethernet controller: D-Link System Inc Gigabit Ethernet
Adapter (rev 11)
0000:00:0b.0 RAID bus controller: 3ware Inc 3ware Inc 3ware 9xxx-series
SATA-RAID
0000:00:0f.0 RAID bus controller: Triones Technologies, Inc.
HPT366/368/370/370A/372 (rev 05)
0000:00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
1.1 Controller (rev 80)
0000:00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
1.1 Controller (rev 80)
0000:00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
1.1 Controller (rev 80)
0000:00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
0000:00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
0000:00:11.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
0000:01:00.0 VGA compatible controller: nVidia Corporation NV18
[GeForce4 MX 4000 AGP 8x] (rev c1)
space:~# lspci -n
0000:00:00.0 0600: 1106:3189
0000:00:01.0 0604: 1106:b168
0000:00:08.0 0104: 13c1:1001 (rev 01)
0000:00:0a.0 0200: 1186:4c00 (rev 11)
0000:00:0b.0 0104: 13c1:1002
0000:00:0f.0 0104: 1103:0004 (rev 05)
0000:00:10.0 0c03: 1106:3038 (rev 80)
0000:00:10.1 0c03: 1106:3038 (rev 80)
0000:00:10.2 0c03: 1106:3038 (rev 80)
0000:00:10.3 0c03: 1106:3104 (rev 82)
0000:00:11.0 0601: 1106:3177
0000:00:11.1 0101: 1106:0571 (rev 06)
0000:01:00.0 0300: 10de:0185 (rev c1)
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
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 and O]
Reboot: [E]
Comments/Problems:
Install went as planned, until the Boot Loader install. LILO flat failed,
failed to install in either
MBR or /dev/hde1 to chain load. Grub at least suceeded there. But it too really
failed. As on the
reboot, it gets to stage1.5. Yes I tried most of the stage1_5 types for
different filesystems by
completely wiping the drives. I gave trying any others when I used ReiserFSv3.6.
Well the fist 300MB with dd if=/dev/zero of=/dev/hde bs=1048576 count=300
I am guessing this should really go against GRUB and/or LILO. They funny thing
is about the whole
thing is:
I created a Boot CD with grub to auto-load the system, so yet even
though it starts from the
CD, it actually boots from the hard drive.
Also rather head-scraztching, this motherboard and processor was a Fully
functional Sid machine before
the move to this machine. It had 250GB Maxtor Drives in it vs the 200GB now.
Same kernel and
everything.
Including these files:
a copy of the first 1024 bytes of /dev/hde
a copy of the first 1024 bytes of the CD (useless as it may be)
mbr-hde
Description: Binary data
mbr-cd
Description: Binary data
# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.
## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
default 0
## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 5
# Pretty colours
color cyan/blue white/blue
## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret
#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#
#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default optons below
## DO NOT UNCOMMENT THEM, Just edit them to your needs
## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specifiv kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
# kopt=root=/dev/hde2 ro vga=791
## default grub root device
## e.g. groot=(hd0,0)
# groot=(hd0,0)
## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true
## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false
## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(recovery mode) single
# altoptions=(recovery mode) single
## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all
## should update-grub create memtest86 boot option
## e.g. memtest86=true
## memtest86=false
# memtest86=true
## ## End Default Options ##
title Debian GNU/Linux, kernel 2.6.9-1-k7
root (hd0,0)
kernel /vmlinuz-2.6.9-1-k7 root=/dev/hde2 ro vga=791
initrd /initrd.img-2.6.9-1-k7
savedefault
boot
title Debian GNU/Linux, kernel 2.6.9-1-k7 (recovery mode)
root (hd0,0)
kernel /vmlinuz-2.6.9-1-k7 root=/dev/hde2 ro vga=791 single
initrd /initrd.img-2.6.9-1-k7
savedefault
boot
title Debian GNU/Linux, kernel 2.6.8-1-386
root (hd0,0)
kernel /vmlinuz-2.6.8-1-386 root=/dev/hde2 ro vga=791
initrd /initrd.img-2.6.8-1-386
savedefault
boot
title Debian GNU/Linux, kernel 2.6.8-1-386 (recovery mode)
root (hd0,0)
kernel /vmlinuz-2.6.8-1-386 root=/dev/hde2 ro vga=791 single
initrd /initrd.img-2.6.8-1-386
savedefault
boot
### END DEBIAN AUTOMAGIC KERNELS LIST
--- End Message ---
--- Begin Message ---
Hello,
Previous update to this bugreport was in januari 2005.
(see http://bugs.debian.org/288408 complete overview)
It was before the release of Debian 3.1, codenamed Sarge.
Meanwhile we are preparing for the release named Etch.
The boot failure is most likely being fixed.
If new versions might fail,
then report it by filing a new install report.
Cheers
Geert Stappers
--- End Message ---
