Your message dated Wed, 08 Sep 2010 03:57:48 +0000
with message-id <e1otbna-0004k2...@ravel.debian.org>
and subject line Closing old installation report #283011
has caused the Debian Bug report #283011,
regarding Sarge Installer does not install GRUB into MBR on Software RAID
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 ow...@bugs.debian.org
immediately.)
--
283011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=283011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Debian-installer-version: 20041124
http://cdimage.debian.org/pub/cdimage-testing/daily/i386/20041124/
uname -a: Linux server 2.4.27-1-386 #1 Fri Sep 3 06:24:46 UTC 2004 i686
GNU/Linux
Date: 25.11.2004 22:30 GMT+1 (Berlin/Germany)
Method: Installation with Sarge Net Install CD Image (107 MB). Boot with
Net Install CD.
Machine: 2U Server (noname, custom)
Processor: Intel P3 1130 MHz (Single CPU)
Memory: 512 MB
Root Device: 2 IDE WD 80 GB (WD Caviar WD800), connected to a Promise
FastTrack 100 RAID Controller as Master, each disk on a single IDE port
(without slave devices).
Root Size/partition table:
----------------------------------------------------------------------
Partition Table for /dev/hde
---Starting--- ----Ending---- Start Number of
# Flags Head Sect Cyl ID Head Sect Cyl Sector Sectors
-- ----- ---- ---- ---- ---- ---- ---- ---- ----------- -----------
1 0x80 1 1 0 0xFD 15 63 1023 63 154296513
2 0x00 15 63 1023 0xFD 15 63 1023 154296576 2004912
3 0x00 0 0 0 0x00 0 0 0 0 0
4 0x00 0 0 0 0x00 0 0 0 0 0
----------------------------------------------------------------------
----------------------------------------------------------------------
Partition Table for /dev/hdg
---Starting--- ----Ending---- Start Number of
# Flags Head Sect Cyl ID Head Sect Cyl Sector Sectors
-- ----- ---- ---- ---- ---- ---- ---- ---- ----------- -----------
1 0x80 1 1 0 0xFD 15 63 1023 63 154296513
2 0x00 15 63 1023 0xFD 15 63 1023 154296576 2004912
3 0x00 0 0 0 0x00 0 0 0 0 0
4 0x00 0 0 0 0x00 0 0 0 0 0
----------------------------------------------------------------------
--- /etc/mtab --------------------------------------------------------
/dev/md0 / ext3 rw,errors=remount-ro 0 0
proc /proc proc rw 0 0
devpts /dev/pts devpts rw,gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs rw 0 0
usbfs /proc/bus/usb usbfs rw 0 0
----------------------------------------------------------------------
--- /etc/fstab -------------------------------------------------------
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/md0 / ext3 defaults,errors=remount-ro 0 1
/dev/md1 none swap sw 0 0
/dev/hdb /media/cdrom0 iso9660 ro,user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
----------------------------------------------------------------------
Output of lspci:
----------------------------------------------------------------------
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo
PRO133x] (rev c4)
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo
MVP3/Pro133x AGP]
0000:00:06.0 VGA compatible controller: ATI Technologies Inc Rage XL
(rev 27)
0000:00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super
South] (rev 40)
0000:00:07.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
0000:00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
1.1 Controller (rev 1a)
0000:00:07.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB
1.1 Controller (rev 1a)
0000:00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI]
(rev 40)
0000:00:0c.0 RAID bus controller: Promise Technology, Inc. PDC20267
(FastTrak100/Ultra100) (rev 02)
0000:00:0d.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro
100] (rev 08)
0000:00:0e.0 Ethernet controller: Intel Corp. 82557/8/9 [Ethernet Pro
100] (rev 08)
----------------------------------------------------------------------
Output of lspci -n:
----------------------------------------------------------------------
0000:00:00.0 0600: 1106:0691 (rev c4)
0000:00:01.0 0604: 1106:8598
0000:00:06.0 0300: 1002:4752 (rev 27)
0000:00:07.0 0601: 1106:0686 (rev 40)
0000:00:07.1 0101: 1106:0571 (rev 06)
0000:00:07.2 0c03: 1106:3038 (rev 1a)
0000:00:07.3 0c03: 1106:3038 (rev 1a)
0000:00:07.4 0680: 1106:3057 (rev 40)
0000:00:0c.0 0104: 105a:4d30 (rev 02)
0000:00:0d.0 0200: 8086:1229 (rev 08)
0000:00:0e.0 0200: 8086:1229 (rev 08)
----------------------------------------------------------------------
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]
Reboot: [E]
Comments/Problems:
First some data:
--- /boot/grub/menu.lst ---------------------------------------------
# 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/md0 ro
## 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
## ## End Default Options ##
title Debian GNU/Linux, kernel 2.4.27-1-386
root (hd0,0)
kernel /boot/vmlinuz-2.4.27-1-386 root=/dev/md0 ro
initrd /boot/initrd.img-2.4.27-1-386
savedefault
boot
title Debian GNU/Linux, kernel 2.4.27-1-386 (recovery mode)
root (hd0,0)
kernel /boot/vmlinuz-2.4.27-1-386 root=/dev/md0 ro single
initrd /boot/initrd.img-2.4.27-1-386
savedefault
boot
### END DEBIAN AUTOMAGIC KERNELS LIST
# This is a divider, added to separate the menu items below from the Debian
# ones.
title Other operating systems:
root
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/hde1.
title Debian GNU/Linux (3.1) (on /dev/hde1)
root (hd0,0)
kernel /boot/vmlinuz-2.4.27-1-386 root=/dev/hde1
initrd /boot/initrd.img-2.4.27-1-386
savedefault
boot
# This entry automatically added by the Debian installer for an existing
# linux installation on /dev/hdg1.
title Debian GNU/Linux (3.1) (on /dev/hdg1)
root (hd1,0)
kernel /boot/vmlinuz-2.4.27-1-386 root=/dev/hdg1
initrd /boot/initrd.img-2.4.27-1-386
savedefault
boot
---------------------------------------------------------------------
--- /boot/grub/devices.map-------------------------------------------
(hd0) /dev/hde
(hd1) /dev/hdg
---------------------------------------------------------------------
--- /etc/mdadm.conf -------------------------------------------------
DEVICE partitions
ARRAY /dev/md1 level=raid1 num-devices=2
UUID=62dc0ea5:1bd176c2:d26037de:27fb37c9
devices=/dev/hde2,/dev/hdg2
ARRAY /dev/md0 level=raid1 num-devices=2
UUID=8ca3b15a:c4d6f2d9:2873467f:d4a99bbf
devices=/dev/hde1,/dev/hdg1
----------------------------------------------------------------------
--- cat /proc/mdstat -------------------------------------------------
Personalities : [raid1]
read_ahead 1024 sectors
md1 : active raid1 ide/host2/bus0/target0/lun0/part2[0]
ide/host2/bus1/target0/lun0/part2[1]
1002368 blocks [2/2] [UU]
md0 : active raid1 ide/host2/bus0/target0/lun0/part1[0]
ide/host2/bus1/target0/lun0/part1[1]
77148160 blocks [2/2] [UU]
unused devices: <none>
----------------------------------------------------------------------
So i have tow Software RAID devices: /dev/md0 (first partition of
/dev/hde and first partition of /dev/hdg) and /dev/md1 (second partition
of /dev/hde and second partition of /dev/hdg). On md0 is my ext3 root fs
and on md1 the swap fs. The installation with the installer was fine,
however after the *first* reboot (the Debian base system was not yet
installed) nothing happens! There was no grub menu or something (also no
grub shell). The system hangs, no error messages, no output. However the
floppy led was on ...
So i used a minimal grub installation on a floppy disk and was able to
boot the new Sarge install with that disk. I supplied the same
information to the floppy disk grub shell as in /boot/grub/menu.lst on
the Sarge install (i looked at that file right after my "grub on a
floppy disk boot"). So what? Yes ... same information in that file,
however no booting of the system ... but boot process runs fine with
grub on a floppy ... so i believe the grub was *not installed* in the
MBR of my both IDE disks (arranged as Software RAID /dev/md0 and
/dev/md1). After i installed grub in the MBR of both disks manual, the
system was able to boot *without* the "grub on a floppy disk boot" trick
... with grub boot menu and all that! I used following commands to
install grub in the MBR of both disks (that's the part the Installer
should have done, i think ...):
--- in the MBR of /dev/hde -------------------------------------------
root# grub
grub> root (hd0,0)
grub> setup (hd0)
grub> quit
----------------------------------------------------------------------
--- in the MBR of /dev/hdg -------------------------------------------
root# grub
grub> root (hd1,0)
grub> setup (hd1)
grub> quit
----------------------------------------------------------------------
Okay, that's all. I hope the information is helping.
PLEASE keep going the good work and PLEASE take Sarge to stable!
Greetings,
Andreas
--- End Message ---
--- Begin Message ---
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 ---
