В Mon, 20 Jul 2015 16:54:04 +0200
Jelle de Jong <jelledej...@powercraft.nl> пишет:

> On 20/07/15 16:29, Andrei Borzenkov wrote:
> > On Mon, Jul 20, 2015 at 5:14 PM, Jelle de Jong
> > <jelledej...@powercraft.nl> wrote:
> >>
> >> I simplified the config a bit for better debugging. It is one USB stick 
> >> now.
> >>
> >> /dev/sda is the debian system that I boot from and chroot and debootstrap.
> >>
> >> I do this process on the ML110G7, the resulting USB stick will boot on
> >> Z600 system but not on the sytem that I created it on the ML110G7.
> >>
> > 
> > Just to be sure - did you try to boot on ML110G7 or on Z600 first?
> > Just to exclude that booting once sets some flag on degraded MD raid
> > that GRUB does not like?
> > 
> >> I tested the same config without using mdadm and the sytem booted up
> >> just fine, so something goes wrong with mdadm grub and/or the machine.
> >>
> >> http://paste.debian.net/284148/
> >>
> > 
> > This looks pretty much fine as far as grub is concerned. Could you try
> > in grub command line
> > 
> > set debug=diskfilter
> > ls
> > 
> 
> I tried to boot in on the ML110G7 first and when it didn't work I put it
> in the Z600.
> 
> grub rescue> set debug=diskfilter
> grub rescue> ls
> (hd0) (hd0,msdos1) disk/diskfilter.c:135: Scanning for DISKFILTER
> devices on disk hd0
> disk/diskfilter.c:135: Scanning for DISKFILTER devices on disk hd0
> 

Yes, diskfilter debugging needs some love.

Do you know what superblock format is used? Could you dump superblock
using "mdadm --examine /dev/sdb1" (or whatever device is)?

If you have possibility to compile upstream grub, testing it would be
definitely helpful.

_______________________________________________
Help-grub mailing list
Help-grub@gnu.org
https://lists.gnu.org/mailman/listinfo/help-grub

Reply via email to