[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#791794: UUID not found for root



On Thu, Jul 16, 2015 at 10:05:48AM -0400, Martin Michlmayr wrote:
> * Peter Nagel <Peter.Nagel@kit.edu> [2015-07-08 15:12]:
> > The problem seems to appear only when jessie is installed to RAID (e.g.
> > RAID1)!
> > Error message:
> > flash-kernel-installer does not find UUID (see the two lines of syslog
> > below):
> >   in-target: UUID eeb34bbe-375a-4dc1-939d-f56b801a4c75 doesn't exist in
> > /dev/disk/by-uuid in-target:
> >   Warning: root device
> > /dev/disk/by-uuid/eeb34bbe-375a-4dc1-939d-f56b801a4c75 does not exist
> 
> I received several reports about this recently.  I'm surprised because
> this used to work just fine.
> 
> I didn't have time to investigate, but I noticed the following partman
> errors in the syslog of those affected.  Colin, do you know what this
> is about?
> 
> Jul  1 10:22:40 partman: mke2fs 1.42.12 (29-Aug-2014)
> Jul  1 10:22:45 kernel: [ 8083.996693] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: errors=remount-ro
> Jul  1 10:22:47 apt-install: Queueing package e2fsprogs for later installation
> Jul  1 10:22:47 main-menu[1537]: (process:5300): /lib/partman/choose_partition/60partition_tree/do_option: 
> Jul  1 10:22:47 main-menu[1537]: (process:5300): line 88: 
> Jul  1 10:22:47 main-menu[1537]: (process:5300): /lib/partman/active_partition/copy/choices: not found

The "copy" operation was removed from partman because parted 3 no longer
supports filesystem operations.  However, I can't find any references to
it in partman code any more.  Is this perhaps coming from a preseeded
partman recipe or something?  Do you have a more complete syslog,
preferably with DEBCONF_DEBUG=developer?

> On a related note, flash-kernel waits for user input when the UUID of
> root is not found, which makes sense in an installed system, but not
> in d-i -- for the user, d-i will just hang with no obvious error.  Is
> there a good way to solve this?  In particular, is there a way for a
> postinst in /target to detect that it's run from within d-i?  KiBi
> doesn't know a way.  I guess a debconf prompt is the way to go?

I think trying to add debconf prompting to an initramfs hook would
probably be unwise.  flash-kernel already seems to check for
DEBIAN_FRONTEND=noninteractive, so you could just set that in
flash-kernel-installer.postinst when calling flash-kernel.

Cheers,

-- 
Colin Watson                                       [cjwatson@debian.org]


Reply to: