On Wed, Aug 04, 2010 at 02:53:22PM +0100, Colin Watson wrote:
> > This behaviour seems to be a problem with grub-probe and its usage by the
> > default config scripts, because the simple most straightforward test fails
> > for one of the RAID devices:
> >
> > % sudo tune2fs -l /dev/md0 | grep UUID
> > Filesystem UUID: 18515dea-973e-473b-bddf-74d1cb58e15a
> > % sudo grub-probe --device /dev/md0 --target=fs_uuid
> > 7e6cdce7-8136-41f0-8a66-997b89ea00fe
> >
> > % sudo tune2fs -l /dev/md2 | grep UUID
> > Filesystem UUID: 222e0fc1-800d-4be4-89fa-96a876aca441
> > % sudo grub-probe --device /dev/md2 --target=fs_uuid
> > 222e0fc1-800d-4be4-89fa-96a876aca441
> >
> > What it thinks to be /dev/md0 isn't actually what the rest of the system
> > knows to be /dev/md0 (nor is it actually what grub sees as md0 on boot time,
> > as it happens).
>
> This all sounds awfully like the problems with array numbering which I
> fixed recently. Are you in a position to re-test with grub-pc
> 1.98+20100804-1 from unstable?
Sorry, no, in the meantime I had removed my extra i386 partition.
Feel free to close if you think it's fixed, it can always be reopened later.
--
2. That which causes joy or happiness.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
