Bug#497110: boot loader installation failed when dmraid=true
(No need to CC me on replies.)
On Saturday 30 August 2008, Giuseppe Iuculano wrote:
> Frans Pop ha scritto:
> > First thing that needs to be determined is what exactly has changed
> > to add this "p". Is it a change in dmraid, or in libparted, or
> > elsewhere? When we know that we can check where changes are needed.
> > Do you have any idea yourself where this "p" comes from?
>
> I don't know where this "p" comes from,
Well, I assume that the "p" stands for "partition". It is a somewhat
common separator. The question is why it is showing up suddenly now and
what is responsible for adding it.
> this is an ls -la after partitions (from network shell installer)
[...]
> But in the next reboot , from network shell installer:
What exactly do you mean by "network shell installer"? That is not really
a meaningfull term for us. If this is some Debian Installer image, then
please specify exactly what image you were using (full URL of the image
you downloaded is good).
I guess the two boots were with the exact same version of the installer
and the same boot options? If that is the case then something is really
broken.
Exactly at what point of the installation did you do the 'ls -la'? Was
this before or after partitioning? The best point to do it would be after
hardware (disk) detection, but before partitioning.
Obviously we cannot really support something that is so unpredictable.
From the info so far I would say that the problem is either in dmraid or
maybe in the device-mapper (either user space or kernel).
I suggest that you try to determine what causes the difference by saving
and carefully comparing the output of dmesg, various dmraid commands,
maybe info available in /proc/, the output of fdisk -l for the underlying
real devices, etc.
What is also suspicious is the missing partition 2, which I suspect is an
extended partition.
Reply to: