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

Bug#405579: marked as done (PowerPC, prep-flavor: manual partitioning error)

Your message dated Thu, 11 Jan 2007 19:44:43 +0100
with message-id <200701111944.44000.elendil@planet.nl>
and subject line Bug#405579: PowerPC, prep-flavor: manual partitioning error
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: partman-base
Version: 100

During an installation of:


on an Motorola Powerstack II:

ut@pleddis:~$ cat /proc/cpuinfo 
processor       : 0
cpu             : 604r
clock           : ???
revision        : 49.2 (pvr 0009 3102)
bogomips        : 299.00
machine         : PReP Utah (Powerstack II Pro4000)
l2 cache        : 512KiB, parity disabled SRAM:synchronous, pipelined, no parity

I had a very strange problem during partitioning. I am just guessing that
the culprit is in partman-base, it could be inside partman-prep as well,
as it has to do with the prep-boot partition.

Anyway, here the full story:

Initial boot of the prep boot CD-ROM image (vmlinuz-prep.initrd) over TFTP,
then continued the install from the CD-ROM. Yes, this may seem strange,
but I have a slow network connection. Graphical console was attached,
no additional parameters were set during boot. English as installation
language, german keyboard layout, manual network configuration.

Nothing special on the initial partioner screen, only some garbled
characters shown at the end of the partition description.

I had a non-working partition layout on my installation target disk (9 GB
SCSI, sda), the prep-boot partition was too small. I deleted all
partitions on the disk. So far, so good.

As soon as I created a fresh prep-boot partition, an alert box popped
up with only question marks and "go back" and "continue" buttons.
After choosing "continue", only the disk itself is shown in the menu
(which is OK), but I was not able to create any partitions on it, nor
do anything useful. It looked like the partitioner restarted
itself, switching to another virtual console only cluttered that console
as well. This is reproducible, but prevents looking at log files at
that point. Choosing "back", I was able to look at the partman log file,
I think the relevant lines are (by hand - I was not able to mount NFS

/lib/partman/update.d/50filesystems : IN : CHANGE_FILE_SYSTEM =dev=scsi=host0=bus0=target0=lun0=disc 32256-98703359 prep
parted_server: opening outfifo
parted_server: command_change_file_system(32256-98703359,prep)
parted_server: partition_with_id(32256-98703359)
parted_server: Filesystem + not found, let's see if it is a flag
parted_server: Bad file system or flag type: +
parted_server: line 1616. CRITICAL ERROR!!! EXITING

If you like to have the full log, I can reproduce the bug, but you have to
tell me how I get it off the machine at this point.

As soon as I used guided partitioning/use full disk/all on one partition,
the created partition layout was fine and the install onto it was successful.

I would rate this bug at least as annoying, as it prevents manual
partitioning from scratch.

Dipl. Inf. Ulrich Teichert|e-mail: Ulrich.Teichert@gmx.de
Stormweg 24               |listening to: Cauchemar (Opération S)
24539 Neumuenster, Germany|Good Looks, Big Deal (Sweatmaster)

--- End Message ---
--- Begin Message ---
Version: 101

On Thursday 11 January 2007 18:44, Ulrich Teichert wrote:
> And this bug is definitely squashed. I've deleted all partitions and
> was able to create different ones, installed on them and all was as it
> should be. AFAIK, we did not even introduce new bugs with the patch ;-)


> This report can be closed, as far as I'm concerned,

Done. Thanks for your excellent work in tracing and testing this.

Feel like having a go at #392764? ;-)

Attachment: pgpE8WZCqjUzy.pgp
Description: PGP signature

--- End Message ---

Reply to: