Bug#275481: marked as done (Sarg Installation problem report)
Your message dated Wed, 08 Sep 2010 03:57:42 +0000
with message-id <E1OtBn4-00048Y-HT@ravel.debian.org>
and subject line Closing old installation report #275481
has caused the Debian Bug report #275481,
regarding Sarg Installation problem 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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact firstname.lastname@example.org
Debian Bug Tracking System
Contact email@example.com with problems
--- Begin Message ---
- To: firstname.lastname@example.org
- Subject: Sarg Installation problem report
- From: Jean-Christian de Rivaz <email@example.com>
- Date: Fri, 08 Oct 2004 14:39:08 +0200
- Message-id: <41668A6C.firstname.lastname@example.org>
md5sum boot.img sarge-i386-netinst.iso
uname -a: Linux talla 2.6.8-1-386 #1 Mon Sept 13 23:29:55 EDT 2004 i686
Date: 05 october 2004 about midnight
Method: Boot with USB Flash with boot.img and sarge-i386-netinst.iso on
it. Use SPB-Linux (http://www.8ung.at/spblinux/) boot sector and
syslinux (2.10-1) unstable.
Machine: MSI K7N2 Motherboard
Processor: AMD Athlon XP 3200+
Memory: 1G 400MHz
Root Device: /dev/md0
Root Size/partition table:
(note: Swap is first to increse the speed)
/dev/hda2 14.4G bootable
/dev/hdc2 14.4G bootable
/dev/md0 RAID1 of /dev/hda2 + /dev/hdc2
/dev/md1 RAID1 of /dev/hda1 + /dev/hdc1
/ ext3 on /dev/md0
/swap on /dev/md1
Output of lspci and lspci -n: Irrelevant, all cards work fine.
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot worked: [E]
Configure network HW: 
Config network: 
Detect CD: 
Load installer modules: 
Detect hard drives: 
Partition hard drives: 
Create file systems: 
Mount partitions: 
Install base system: 
Install boot loader: 
You can see the screenshot of the insall process on
http://www.eclis.ch/~jcdr/sarge/index.php . The install is in French,
but this don't hurt as the problem is in the boot process. This also
explain why this report is certainly full of english error. Sorry for that.
There is in fact 3 problems:
1) The boot.img.gz supplied don't boot, just hang the machine. The BIOS
correctly detect the bootsector on the first partition of the flash and
read it (the led blinks a half second) and then nothing. I zeroed the
first patition boot sector then write the SPB-Linux as the main boot
sector and I get a syslinux error while booting. Then I reformat the
partition, use the current syslinux from testing and add the other files
from boot.img.gz and the sarge-i386-netinst.iso. So it boot and startup
wonderfully. Conclusion: the USB boot image don't boot, but a modified
2) I choose to put the swap partion first on the disks because this
greatly increase the speed of the access time and the bandwidth (see all
hard disk review, the speed decrease as the data is near the end). So
the main partition is the second one and I add the boot flag on the
second partition of each disk of the RAID1. The installation go
wonderfully, including the GRUB install, but when I reboot I got a
"error 17: cannot mount selected partition". See
http://www.eclis.ch/~jcdr/sarge/index.php?boot/grub/PA040075.JPG I have
to correct the (hd0,0) to (hd0,1) to be able to boot. Of course I change
the values into the /boot/grub/menu.lst and make a grub-install.
Conclusion: the install process don't understand that the boot
partitions are the second one of each disk of the RAID1.
3) Since I make a RAID1 installation, I try to disconnect each disk to
test if I can still boot without one of the disk. All go well if I boot
only with the first disk (/dev/hda in the install process), but boot
failed with error "GRUB Hard Disk Error" if I boot only with the second
disk (/dev/hdc in the install process). See
I tryed several things based on finding on google, but almost all of
them failed too. Many people claim that setup (hd0,1) + setup (hd1,1)
work, but not for me. Finally I found this message
this is the solution that work for me. Now I can boot with only one of
the disks (and with to two of course). Conclusion: the GRUB
configuration don't allow safe RAID1 operation. This problem involve
maybe more that the installer to be resolved. GRUB obviously lack
documentation about the RAID1 support.
There also is many success:
1) The support for Swiss French is excellent (this is a rare keyboard).
2) The RAID1 partitionning work well and allow very precise setup. I
like it since it allway show clearely the state of the process. It's
only annoying that it require 58 screens to make a basic RAID1 setup!
But I agree that it's not easy to find a quicker way.
3) The package search and installation is a wonder dream. really I make
absolute nothing but wait a few minutes. Impressive good job!
4) This is my first GRUB install and I did't know it before as I used
LILO. I realise that GRUB is a good choice since it allow to adjust the
boot parameters when it fail. If I have the same problem with LILO I
will have to reboot the installer, but with GRUB I just edited a
parameter. GRUB just need RAID1 support as LILO have with it
I am open to make a new set of test if someone notify me of a new
version with fix on it. I use two old disk to test the install on what
is normaly a NFS worksation so it can't trash my datas. I know many
people interresting about installing a basic Debian Sarge web server
with the same RAID1 setup. I think it make sense to solve the problemes
I describs here.
Have a good day,
Jean-Christian de Rivaz
--- End Message ---
--- Begin Message ---
We are closing this installation report for one of the following
- it was reported with a pre-lenny version of Debian
- 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
Many thanks for your understanding and your help improving Debian,
past and present.
--- End Message ---