Am Donnerstag, 29. März 2012 schrieb David Banks: > On 29/03/12 12:57, Martin Steigerwald wrote: > >> However, when I boot this I get this error three times: > >> error: file not found. > > > > What is before the file not found? Does it give a hint as to which > > file it did not found? Or what it was trying to do before printing > > the error message? I suggest you to lookup whether GRUB 2 can run > > with more verbosity if not. > > Nothing -- 'error: file not found' is the first message. > > My Grub does not know about 'find', so I'll assume that 'search --file' > works the same for the following commands.
Ah, so grub2 has a different command > > In GRUB console what does > > > > find /boot > > grub> search --file /boot > error: no such device: /boot. Well its not a file, maybe searching for directories does not work. > > find /boot/vmlinuz-2.6.32-5-amd64 > > grub> search --file /boot/vmlinuz-2.6.32-5-amd64 > hd1,msdos1 > > > find /boot/initrd.img-2.6.32-5-amd64 > > grub> search --file /boot/initrd.img-2.6.32-5-amd64 > hd1,msdos1 Seems quite fine. > > find /etc/debian_version > > grub> search --file /etc/debian_version > hd0,msdos1 hd1,msdos1 hd0 is your kFreeBSD, hd1 the Linux, seems fine as well. > > find /boot/grub/core.img > > grub> search --file /boot/grub/core.img > hd1,msdos1 Thats strange. I thought GRUB was installed on the kFreeBSD hd0. > > find /boot/grub/ext2.mod > > grub> search --file /boot/grub/ext2.mod > hd1,msdos1 > > These last two are very confusing because the output should include > hd0,msdos1 -- the kFreeBSD partition -- I presume. No difference if I > run 'insmod ufs2' beforehand. Hmmm, exactly. > > On GRUB console does > > > > insmod ext2.mod > > > > work? > > This command gives an error, but "insmod ext2" is working. Hmmm, okay. I missed the detail that it needs it without the extension. > I was confused by the output above so I tried to boot kFreeBSD from the > GRUB console in the same way. It appears that GRUB cannot see any of > the files in the kFreeBSD partition when testing from the console. But > when I use the menuentry, KFreeBSD boots fine. I typed in the exact > commands from the kFreeBSD menuentry into the console: > > grub> insmod part_msdos > grub> insmod ufs2 > grub> set root='(hd0,msdos1)' > grub> search --no-floppy --fs-uuid --set=root 4f71fd5b806762cc > error: file not found. (repeat ~25 times) > error: no such device: 4f71fd5b806762cc. > grub> kfreebsd /boot/kfreebsd-8.2-1-amd64.gz > error: file not found. Strange. Could it be, that currently the GRUB from the Linux side is used? But even then, if it has a ufs module it should see the files from the UFS partition as well. If you have a GRML or other live cd available, I suggest you to install the grub from the kFreeBSD side again and move /boot/grub from the Linux side to /boot/grub-disabled in order to make sure, that GRUB 2 doesn´t get confused about two GRUB configuration. But thats just a rough bet. Otherwise for now I am out of ideas as well. -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201203291538.04969.mar...@lichtvoll.de
