From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1KRY4I-0000F8-Mx for mharc-grub-devel@gnu.org; Fri, 08 Aug 2008 15:56:10 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KRY4G-0000Eh-UU for grub-devel@gnu.org; Fri, 08 Aug 2008 15:56:08 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KRY4E-0000EE-L5 for grub-devel@gnu.org; Fri, 08 Aug 2008 15:56:07 -0400 Received: from [199.232.76.173] (port=55189 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KRY4E-0000EB-DY for grub-devel@gnu.org; Fri, 08 Aug 2008 15:56:06 -0400 Received: from smtp-vbr6.xs4all.nl ([194.109.24.26]:4665) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KRY4E-0008Cs-AT for grub-devel@gnu.org; Fri, 08 Aug 2008 15:56:06 -0400 Received: from [192.168.1.2] (sander-marechal.xs4all.nl [82.95.221.82]) (authenticated bits=0) by smtp-vbr6.xs4all.nl (8.13.8/8.13.8) with ESMTP id m78Ju5Dq036737 for ; Fri, 8 Aug 2008 21:56:05 +0200 (CEST) (envelope-from s.marechal@jejik.com) Message-ID: <489CA4D4.4080108@jejik.com> Date: Fri, 08 Aug 2008 21:56:04 +0200 From: Sander Marechal User-Agent: Icedove 1.5.0.14eol (X11/20080724) MIME-Version: 1.0 To: grub-devel@gnu.org X-Enigmail-Version: 0.94.4.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by XS4ALL Virus Scanner X-detected-kernel: by monty-python.gnu.org: FreeBSD 4.6-4.9 Subject: Problem booting grub2: can't find fd1 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Aug 2008 19:56:09 -0000 Hello, I have a brand new server: A Dell PowerEdge T105 Quad Core AMD64. I installed it with Debian Lenny, which installed Lilo as a bootloader. I installed grub2 manually: grub-install /dev/sda update-grub When I boot I get dropped into a rescue shell because grub can't find fd1. The output of `ls`: (linuxvg-boot) (linuxvg-root) (linuxvg-swap) (hd0) (hd0,1) (hd0,2) (hd0,3) (fd0) (fd1) Thing is, my server has no floppy drive. It has one had disk containing two small Dell partitions and a big partition that is the PV for my LVM volume group "linuxvg". And it contains a DVD-ROM drive. No floppy drive. I even disabled the floppy controller in the BIOS. I am able to boot Debian by entering the boot commands manually: > insmod linux > linux (linuxvg-boot)/vmlinuz-2.6.25-2-amd64 root=/dev/mapper/linuxvg-root ro > initrd (linuxvg-boot)/initrd.img-2-6-25-2-amd64 > boot What can I do to fix this issue? Yesterday on #grub marco_g suggested that I try grub-legacy to see it it has the same fd1 problem. I can't install grub-legacy because it does not support having /boot on LVM, so I will need to test grub-legacy with a rescue image. Unfortunately I don't have a floppy drive so I can't try the grub legacy disk image supplied by the grub-disk package. I do have grub-rescue-cd but that's grub2, not grub-legacy. Does anyone have a grub-legacy rescue CD iso I can use to see if grub-legacy has the same problem as grub2? Kind regards, -- Sander Marechal