On 01.04.2011 16:43, Sean Porth wrote: > > > On 03/31/11 15:21, Vladimir 'Æ-coder/phcoder' Serbinenko wrote: > > On 09.02.2011 20:33, Sean Porth wrote: > >> I have the same exact issue. Upgrading to Debian squeeze. I even > upgraded the grub2 package to the Debian unstable version (1.99~rc1-2) > and same error. > >> > >> backup:/etc# grub-install /dev/md0 > >> /usr/sbin/grub-probe: error: no such disk. > >> Auto-detection of a filesystem of /dev/md0 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> > >> > >> backup:/etc# /usr/sbin/grub-probe > --device-map="/boot/grub/device.map" --target=fs -v /boot/grub > >> /usr/sbin/grub-probe: info: changing current directory to /dev. > >> /usr/sbin/grub-probe: info: changing current directory to disk. > >> /usr/sbin/grub-probe: info: changing current directory to by-uuid. > >> /usr/sbin/grub-probe: info: changing current directory to by-id. > >> /usr/sbin/grub-probe: info: changing current directory to block. > >> /usr/sbin/grub-probe: info: opening md0. > >> /usr/sbin/grub-probe: error: no such disk. > >> > >> > > Could you supply the output of following commands: > > cat /proc/mdstat > > grub-fstest -d all -c `ls /dev/sd?|wc -l` /dev/sd? ls -- -l > > as well as first and last 128K of every array member? > > backup:~# cat /proc/mdstat > Personalities : [linear] [raid1] > md1 : active raid1 sdb3[1] sda3[0] > 945513536 blocks [2/2] [UU] > > md0 : active raid1 sdb1[1] sda1[0] > 29294400 blocks [2/2] [UU] > > unused devices: <none> > > -- > > backup:/usr/src/grub-1.98# ./grub-fstest -d all -c `ls /dev/sd?|wc -l` > /dev/sd? ls -- -l > ls: cannot access /dev/sd?: No such file or directory > Invalid disk count. > Try `./grub-fstest --help' for more information. > > > I think the grub-fstest is showing the crux of the problem. After the > upgrade to squeeze I no longer have /dev/sda and /dev/sdb , all though > md seems to have no problem finding them. > Have you tried executing grub-mkdevicemap? Actually the normal way to launch grub-fstest is: ./grub-fstest -d all -c N <DEVICES> ls -- -l Where DEVICES is devices in the md array and N is the number of them. The part with sd? was just a quick hack to detect this things for error reporting. > > >> _______________________________________________ > >> Bug-grub mailing list > >> bug-g...@gnu.org > >> http://lists.gnu.org/mailman/listinfo/bug-grub > >> > >> > > >
-- Regards Vladimir 'φ-coder/phcoder' Serbinenko
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
