Bug#684293: root cause of mount hang in installer [kernel bug]
On Thu 09 Aug 2012 at 13:29:20 +0100, Brian Potkin wrote:
> Either before or just after selecting a language and configuring the
> keyboard I executed 'mountmedia' and 'mountmedia driver'. Everything
> seems to go well, with extended partitions being detected and attempted
> to be mounted.
>
> After selecting cdrom-detect mountmedia stops at the first extended
> partition it finds. This does not happen with the alpha-1 image and I
> have no explanation why detecting and mounting the CD-ROM should trigger
> this behaviour.
To follow up on this:
The two lines in mountmedia
mount $1 -tauto $MNT || true
and
mount $1 -tauto $MNT
can be altered to look explicitly for vfat partitions with -tvfat.
Detection and loading of missing firmware then takes place as we would
expect. I offer this as an observation, not as a solution, because I'm
unsure how it would affect d-i as a whole.
After detecting and mounting the CD-ROM the iso9660 filesystem is shown
in /proc/filesystems and my thinking is that this may be the cause of
the present problem. The installation proceeds as usual if, after
loading the installer components. /cdrom is unmounted and the isofs
module unloaded from the kernel.
When mountmedia hangs it appears to be because -tauto tests for an
iso9660 filesystem first and fails with an extended partition. The lsmod
output shows two processes using the isofs module. I assume mountmedia
cannot go on to look for other partition types until the second process
has completed.
Reply to: