On 26.02.2011 05:54, Dererk wrote: > Package: grub2 > Version: 1.99~rc1-3 > Severity: important > Usertags: kfreebsd > > Could you come to freenode #grub ? I would like to make a series of tests and it will be faster over IRC. > Hi there. > > I've been using grub2 on my kfreebsd machines for some time now with no > issues at all, but since two or three weeks I started getting this very > exact error on both i386 and amd64 machines, one performing grub package > upgrades. Unfortunately one of them went down unexpectedly and caused me > to loose the capability to boot since I get grub entering rescue mode > without being able to perform any task other than getting "error: > unknown filesystem." > > I'm using regular UFS on the root partition which holds the /boot too, > _no zfs_ on any of them. > > > This is the log I get from the other running machine which stills live: > > root <at> ananke[~]# dpkg-reconfigure -plow grub-pc > camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed > cam_lookup_pass: No such file or directory > cam_lookup_pass: either the pass driver isn't in your kernel > cam_lookup_pass: or ad0 doesn't exist > camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed > cam_lookup_pass: No such file or directory > cam_lookup_pass: either the pass driver isn't in your kernel > cam_lookup_pass: or ad0 doesn't exist > camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed > cam_lookup_pass: No such file or directory > cam_lookup_pass: either the pass driver isn't in your kernel > cam_lookup_pass: or ad0 doesn't exist > camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed > cam_lookup_pass: No such file or directory > cam_lookup_pass: either the pass driver isn't in your kernel > cam_lookup_pass: or ad0 doesn't exist > Configuring grub-pc > ------------------- > > The grub-pc package is being upgraded. This menu allows you to select > which devices you'd like grub-install to be automatically run for, if any. > > Running grub-install automatically is recommended in most situations, to > prevent the installed GRUB core image from getting out of sync with GRUB > modules or grub.cfg. > > If you're unsure which drive is designated as boot drive by your BIOS, > it is often a good idea to install GRUB to all of them. > > Note: it is possible to install GRUB to partition boot records as well, > and some appropriate partitions are offered here. However, this forces > GRUB to use the blocklist mechanism, which makes > it less reliable, and therefore is not recommended. > > 1. /dev/ad0 (??? MB; ???) 2. /dev/ad0s1a (??? MB; ???) 3. none of > the above > > (Enter the items you want to select, separated by spaces.) > > GRUB install devices: 1 2 > > > /usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/ad0s1a. > Check your device.map. > Auto-detection of a filesystem of /dev/ad0s1a failed. > Please report this together with the output of "/usr/sbin/grub-probe > --device-map="/boot/grub/device.map" --target=fs -v /boot/grub" to > <bug-g...@gnu.org> > /usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/ad0s1a. > Check your device.map. > Auto-detection of a filesystem of /dev/ad0s1a failed. > Please report this together with the output of "/usr/sbin/grub-probe > --device-map="/boot/grub/device.map" --target=fs -v /boot/grub" to > <bug-g...@gnu.org> > GRUB failed to install to the following devices: > > /dev/ad0 /dev/ad0s1a > > Do you want to continue anyway? If you do, your computer may not start > up properly. > > Writing GRUB to boot device failed - continue? y > > > root <at> ananke[~]# > > root <at> ananke[~]# /usr/sbin/grub-probe > --device-map="/boot/grub/device.map" --target=fs -v /boot/grub > /usr/sbin/grub-probe: info: the size of hd0 is 8388608. > /usr/sbin/grub-probe: info: the size of hd0 is 8388608. > /usr/sbin/grub-probe: info: scanning hd0 for LVM. > /usr/sbin/grub-probe: info: the size of hd0 is 8388608. > /usr/sbin/grub-probe: info: no LVM signature found > . > /usr/sbin/grub-probe: info: the size of hd0 is 8388608. > /usr/sbin/grub-probe: info: the size of hd0 is 8388608. > /usr/sbin/grub-probe: info: the size of hd0 is 8388608. > /usr/sbin/grub-probe: info: the size of hd0 is 8388608. > /usr/sbin/grub-probe: info: the size of hd0 is 8388608. > /usr/sbin/grub-probe: info: the size of hd0 is 8388608. > /usr/sbin/grub-probe: info: the size of hd0 is 8388608. > /usr/sbin/grub-probe: info: the size of hd0 is 8388608. > /usr/sbin/grub-probe: info: the size of hd0 is 8388608. > /usr/sbin/grub-probe: info: the size of hd0 is 8388608. > /usr/sbin/grub-probe: info: the size of hd0 is 8388608. > /usr/sbin/grub-probe: info: the size of hd0 is 8388608. > /usr/sbin/grub-probe: info: the size of hd0 is 8388608. > /usr/sbin/grub-probe: info: the size of hd0 is 8388608. > /usr/sbin/grub-probe: info: the size of hd0 is 8388608. > /usr/sbin/grub-probe: info: scanning hd0 for LVM. > /usr/sbin/grub-probe: info: the size of hd0 is 8388608. > /usr/sbin/grub-probe: info: no LVM signature found > . > /usr/sbin/grub-probe: info: the size of hd0 is 8388608. > /usr/sbin/grub-probe: info: scanning hd0,msdos1,bsd2 for LVM. > /usr/sbin/grub-probe: info: the size of hd0 is 8388608. > /usr/sbin/grub-probe: info: no LVM signature found > . > /usr/sbin/grub-probe: info: scanning hd0,msdos1,bsd1 for LVM. > /usr/sbin/grub-probe: info: the size of hd0 is 8388608. > /usr/sbin/grub-probe: info: no LVM signature found > . > /usr/sbin/grub-probe: info: scanning hd0,msdos1 for LVM. > /usr/sbin/grub-probe: info: the size of hd0 is 8388608. > /usr/sbin/grub-probe: info: no LVM signature found > . > /usr/sbin/grub-probe: info: changing current directory to /dev. > /usr/sbin/grub-probe: info: changing current directory to fd. > /usr/sbin/grub-probe: info: changing current directory to led. > /usr/sbin/grub-probe: info: changing current directory to usb. > /usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/ad0s1a. > Check your device.map. > > root <at> ananke[~]# cat /boot/grub/device.map > (hd0) /dev/ad0 > > root <at> ananke[~]# df > Filesystem 1K-blocks Used Available Use% Mounted on > /dev/ad0s1a 3567918 461166 2821320 15% / > devfs 1 1 0 100% /dev > linprocfs 4 4 0 100% /proc > /sys 4 4 0 100% /sys > fdescfs 1 1 0 100% /dev/fd > tmpfs 629024 4 629020 1% /lib/init/rw > > > Please do let me know about any possible information I can provide you > with to solve this issue, which is quite important as it's highly likely > to render many systems unbootable. > > > Thanks in advance. > > > Cheers, > > Dererk > > > > > _______________________________________________ > Pkg-grub-devel mailing list > pkg-grub-de...@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pkg-grub-devel
-- Regards Vladimir 'φ-coder/phcoder' Serbinenko
signature.asc
Description: OpenPGP digital signature