Package: installation-reports
Debian-installer-version: http://cdimage.debian.org/pub/cdimage-testing/daily/i386/current/sarge-i386-netinst.iso 29-Oct-2004 23:34 uname -a: The system was not able to boot. Date: Sat Oct 30 17:57:29 CEST 2004 Method: How did you install?. What did you boot off?. http://cdimage.debian.org/pub/cdimage-testing/daily/i386/current/sarge-i386-netinst.iso Proxied?. No. Machine: clone PC Processor: AMD XP 3000+ Memory: 1G Root Device: 2 IDE HD, Name of device? /dev/md1 Root Size/partition table: [knoppix]# fdisk /dev/hda The number of cylinders for this disk is set to 19457. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK) Command (m for help): p Disk /dev/hda: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 1 249 2000061 fd Linux raid autodetect /dev/hda2 * 250 19457 154288260 fd Linux raid autodetect Command (m for help): q # fdisk /dev/hdc The number of cylinders for this disk is set to 19457. There is nothing wrong with that, but this is larger than 1024, and could in certain setups cause problems with: 1) software that runs at boot time (e.g., old versions of LILO) 2) booting and partitioning software from other OSs (e.g., DOS FDISK, OS/2 FDISK) Command (m for help): p Disk /dev/hdc: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hdc1 1 249 2000061 fd Linux raid autodetect /dev/hdc2 * 250 19457 154288260 fd Linux raid autodetect Command (m for help): q # RAID1 device #0 RAID1 device #1 partition #1 of RAID1 device #0 as swap partition #1 of RAID1 device #1 as ext3 hda1 & hdc1 is configured as md0 swap hda2 & hdc2 is configured as md1 ext3 mount on / Output of lspci and lspci -n: [knoppix]# lspci -n 0000:00:00.0 0600: 10de:01e0 (rev c1) 0000:00:00.1 0500: 10de:01eb (rev c1) 0000:00:00.2 0500: 10de:01ee (rev c1) 0000:00:00.3 0500: 10de:01ed (rev c1) 0000:00:00.4 0500: 10de:01ec (rev c1) 0000:00:00.5 0500: 10de:01ef (rev c1) 0000:00:01.0 0601: 10de:0060 (rev a4) 0000:00:01.1 0c05: 10de:0064 (rev a2) 0000:00:02.0 0c03: 10de:0067 (rev a4) 0000:00:02.1 0c03: 10de:0067 (rev a4) 0000:00:02.2 0c03: 10de:0068 (rev a4) 0000:00:04.0 0200: 10de:0066 (rev a1) 0000:00:05.0 0401: 10de:006b (rev a2) 0000:00:06.0 0401: 10de:006a (rev a1) 0000:00:08.0 0604: 10de:006c (rev a3) 0000:00:09.0 0101: 10de:0065 (rev a2) 0000:00:0d.0 0c00: 10de:006e (rev a3) 0000:00:1e.0 0604: 10de:01e8 (rev c1) 0000:01:04.0 0200: 11ab:4320 (rev 13) 0000:01:09.0 0200: 10b7:9200 (rev 78) 0000:01:0b.0 0104: 1095:3112 (rev 02) 0000:03:00.0 0300: 10de:0185 (rev a4) # 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: [O] Reboot: [O] Comments/Problems: <Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install.> -*- Though the installation process does not report any trouble and the system reboots, after the reboot the system does not boot. I do not get any GRUB feedback or prompt. This is the output of the last steps: Installing GRUB boot loader reboot ... PCI device listing ... Bus No. Device No. ... . . . Verifying DMI Pool Data .......... Boot from CD : As you can read, the system does not boot from the hard disk MBR. There is not hardware problem due to I have plugged another previously installed HD and it boot without any problem. The same problem was raised using pre-rc2. I have tried the daily build following the advice which #debian-boot gave me, in order to send this bug report. Note that RedHat Advanced Server 3.0 reports that "The GRUB boot loader will be installed on /dev/md1 and it offers "Change boot loader" button ( GRUB, LILO, do not install boot loader ), but note it does not offer change the /dev/md1 target device. Unfortunately I have not been able to finish the RedHat installation due to the second installation CD was broken. Any workaround so I can finish the installation of Debian GNU/Linux sarge over RAID1?. I have got a shell but I do not find grub-install to do it by hand. I suppose the problem is related to a wrong device target, at the time of the grub-install command. I think it is using hd0 as target instead of /dev/md1 It would be cool offer the posibility to choose LILO besides GRUB as RedHat does. Note I am thinking about use this reference to the installation process: http://juerd.nl/site.plp/debianraid?display=print but I do not want to compile the kernel, to use the debian security update service. Regards, Davi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
