grub-install fails due to wrong target disk
hi i'm trying to install debian gnu/kfreebsd on a sun x4100 server with two sas controllers and an attached j4200 JBOD storage. the disk layout on the server is as following: 2x LSI SAS controllers: - SAS1064 (Bus 02, Dev 03, Fnc 00) - Phy 00: Hitachi 146G SAS Disk (boot drive) - Phy 01: Hitachi 146G SAS Disk - SAS1068 (Bus 02, Dev 01, Fnc 00) - Sun J4200 Storage Enclosure - 6x Hitachi 500G SATA Disk the debian installer sees the drives as such: /dev/da0 = disk01 of the j4200 enclosure /dev/da1 = disk02 of the j4200 enclosure /dev/da2 = disk03 of the j4200 enclosure /dev/da3 = disk04 of the j4200 enclosure /dev/da4 = disk05 of the j4200 enclosure /dev/da5 = disk06 of the j4200 enclosure /dev/da6 = internal disk 1 (boot drive) /dev/da7 = internal disk 2 i selected /dev/da6s1 as the zfs root partition. unfortunately, during grub2 installation, the installer tries to setup grub in /dev/da0 instead of /dev/da6, which fails. instead of grub-install --no-floppy --force "/dev/da0" it should use grub-install --no-floppy --force "/dev/da6" is there a way to run grub-install manually from a 2nd console during the installation, or any other way to get grub2 installed on /dev/da6? thanks, thomas -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4efbc58d.5020...@alternize.com
Re: grub-install fails due to wrong target disk
On 29/12/11 01:42, Thomas H. wrote: it should use grub-install --no-floppy --force "/dev/da6" is there a way to run grub-install manually from a 2nd console during the installation, or any other way to get grub2 installed on /dev/da6? Hi Thomas, If you Alt-F2/F3 into a spare console, I imagine you can do: chroot /target /bin/bash and then run the grub-install command manually. You should then Alt-F1 back into the installer menu and say 'Continue without a bootloader' as there are some other things it does before it finishes. thanks steven. the chrooting worked, but ultimatively resulted in a non-bootable system when doing update-grub and grub-install. i retried the installation, this time not allowing debian-installer to install grub in the MBR but rather setting the target to /dev/da6. this resulted in the following errors: grub-installer: info: Installing grub on '/dev/da6' grub-installer: info: grub-install supports --no-floppy grub-installer: info: Running chroot /target grub-install --no-floppy --force "/dev/da6" grub-installer: /usr/sbin/grub-stup: warn: grub-installer: Your core.img is unusually large. It won't fit in the embedding area. grub-installer: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged. grub-installer: /usr/sbin/grub-setup: error: grub-installer: cannot read '/grub/core.img' correctly grub-installer: error: Running 'grub-install --no-floppy --force "/dev/da6"' failed. i guess the disk partition layout is broken and will redo them now before giving it another try (i had to do the partitions in gparted as d-i failed partitioning the drive before...). some a grub bug-report comment [0] suggest that there should be at least 1M+ gap before the first partition when using MBR or have a dedicated 1M+ grub bios partition under GPT - which my drive currently hasn't. BTW, were you installing the Squeeze release (kfreebsd-8)? Or one of the Wheezy testing images (kfreebsd-9) from: http://www.debian.org/devel/debian-installer/ i used the squeeze release 6.0.3 kfreebsd-adm64 squeeze dvd release. i'll give the wheezy image a try if it still fails after repartitioning. another idea i had was to first try a normal amd64 debian to hopefully get grub2 installed correctly... regards, thomas [0] https://bugs.archlinux.org/task/24103#comment76579 -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4efcb281.3020...@alternize.com
Re: grub-install fails due to wrong target disk
i selected /dev/da6s1 as the zfs root partition. unfortunately, during grub2 installation, the installer tries to setup grub in /dev/da0 instead of /dev/da6, which fails. instead of grub-install --no-floppy --force "/dev/da0" it should use grub-install --no-floppy --force "/dev/da6" There's a debconf template in grub-pc package to ask user which disk(s) should GRUB be installed to. I think grub-installer should either offer the same functionality, or just rely on this template externally (if possible). Please could you file a bug on grub-installer? i think there are already bugs for different architecture with exactly the same problem, f.e. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610641 in the end i think it was my missunderstanding of d-i's message that it has found no other OS and would recommend installing grub in the MBR - which i always confirmed with [yes]. selecting [no] indeed gives me the option to manually specify the target drive (which ultimately also failed, but for different reasons). regards, thomas -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4efcb309.10...@alternize.com
