Your message dated Sat, 3 Aug 2019 12:09:05 +0300
with message-id <20190803090905.tz5sc46phrf2j55x@localhost>
and subject line Re: Bug#414455: palo-installer: cannot handle /boot on raid1
has caused the Debian Bug report #414455,
regarding palo-installer: cannot handle /boot on raid1
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
414455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=414455
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: palo-installer
Version: 0.0.8

Just to do something different I tried putting the boot partition on 
raid1. That turned out to be a very bad idea as either palo or 
palo-installer did not have a clue how to deal with that.

The syslog showed:
palo version 1.14 kyle@duet Sat Apr  8 16:08:23 EDT 2006
ELF64 executable
Your media does not contain a partition table.  Use 'fdisk' or
a similar utility to create one.  Be certain to create a partition
of type F0 to hold the boot loader, possibly a kernel image, and
possibly a ramdisk image.  5-6Mbytes is probably a good size
Configuring 'palo-installer' failed with error code 2

Obviously I _did_ create a palo partition. the problem was more that 
palo.conf was broken. After manually changing /target/boot to a regular 
partition, editing palo.conf and running palo in a chroot on /target was 
I able to get past this.

Attachment: pgpLKyapWVgaW.pgp
Description: PGP signature


--- End Message ---
--- Begin Message ---
On Lu, 12 mar 07, 00:22:29, Frans Pop wrote:
> Package: palo-installer
> Version: 0.0.8

This package appears to have been removed from Debian long time ago, 
closing.

Kind regards,
Andrei
-- 
Looking after bugs reported against inexistent or removed packages

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to