Bug#605759: [s390/hercules] disk partitioning failed: no /dev/dsda1
On Thu, Dec 16, 2010 at 05:37:55PM +0100, Ferenc Wagner wrote:
> Niko Tyni <ntyni@debian.org> writes:
>
> > Hercules s390 emulator installation failed at disk partitioning;
> > new partitions don't seem to show up in /dev.
> Thanks for the detailed but to-the-point report. This may be a kernel,
> a udev or a partman issue. Could you please try backing out of the
> partitioning menu to the main menu, start a shell in the installer
> environment with the appropriate menu item and do the partitioning
> yourself by fdasd or whatever's needed? Then please check if the new
> partitions show up in /proc/partitions and under /dev. This would help
> us narrowing down the case.
It works fine if I create the partition manually with fdasd.
Furthermore, if I try to create a partition first with the d-i interface
(getting the error) and then invoke fdasd and write out a trivial no-op
such as change the volume serial from LIN120 to LIN120, /dev/dasda1
appears.
It looks te me like the problem is that d-i does not manage to reread
the partition table.
I'm not sure if I understand the architecture correctly here, but
maybe the problem is this change in parted 2.3 ?
libparted: remove now-worse-than-useless _kernel_reread_part_table
Now that we're using BLKPG properly, there's no point in using the
less-functional BLKRRPART ioctl to make the kernel reread the partition
table.
More importantly, this function would fail when any partition is in
use, in spite of our having carefully vetted them via BLKPG ioctls.
I see fdasd (as of s390-tools 1.8.3-3) uses BLKRRPART and not BLKPG.
The timeline would also fit the successful reports #569209 and #575682.
I suppose I can try to hack parted to use BLKRRPART again and see if
that helps, but it's probably going to take a few days as I need to
get the emulator up and running first so I can rebuild the udeb.
--
Niko Tyni ntyni@debian.org
Reply to: