Re: PPC64 Image Installation Error
Hi Rick,
I partitioned the first disk (1 TB) in my machine like so:
#1 32 KB Apple Partition Map
#2 8 MB HFS NewWorld Boot Partition (mounted at /boot) - Designated to
Ubuntu Server 16.04, which used up 313 KB, leaving 7.32 MB unused.
#3 40 GB Ext4 System Partition (mounted at /) - Designated to Ubuntu
Server 16.04
#4 4.8 GB Swap Partition (4.5 GB installed) - Designated to Ubuntu
Server 16.04
#5 455 GB Ext4 Home Partition (mounted at /home) - Designated to Ubuntu
Server 16.04
#6 8 MB Ext2 Boot Partition (to be mounted at /boot) - Designated to
Debian 10, which the installer left with 298 KB used, leaving 7.34 MB
unused. (Which is why I didn't jump to it being a space issue.)
#7 40 GB Ext4 System Partition (to be mounted at /) - Designated to
Debian 10
#8 4.8 GB Swap Partition (ditto) - Designated to Debian 10
#9 455 GB Ext4 Home Partition (to be mounted at /home) - Designated to
Debian 10
This was actually also the first time I tried to dual-boot Linux
systems on PPC, so I now feel like I'm very obviously at fault for
this.
But we're always learning. I've been on this train for just under a
year and not only do I thank myself every day, I also learn something
new every day. Or at least, every other day, perhaps. Just as well.Thanks, all.
N
On Tue, 2019-01-29 at 03:41 -0800, Rick Thomas wrote:
>
> >
> > On Jan 28, 2019, at 11:19 PM, Noah Wolfe <n.wolfe4@outlook.com>
> > wrote:
> >
> > Hello.
> >
> > I'm running a Late 2005 Power Mac G5 (11,2), and although the
> > regular
> > powerpc installer images may be fixed from most problems at this
> > point
> > (going off of other people's posted experiences), the newest
> > netinstall
> > ppc64 images from 2019-01-27
> > (http://cdimage.debian.org/cdimage/ports/2
> > 019-01-27/) are still unable to install the linux-image-powerpc64
> > package during normal (non-expert) installation, and when the
> > installer
> > gives you the notification of this, it quits the rest of the
> > installation, leaving an incomplete base system.
> >
> > The notification window itself displays "Unable to install the
> > selected
> > kernel" in red text at the top, with the description "An error was
> > returned while trying to install the selected kernel into the
> > target
> > system." in regular black text. It specifies with "Kernel package:
> > 'linux-image-powerpc64'." below, and adds "Check /var/log/syslog or
> > see
> > virtual console 4 for the details." at the end. It is accompanied
> > by a
> > blue backdrop instead of the usual red.
> >
> > Upon further inspection into virtual console 4 (Ctrl+Alt+F4), the
> > last
> > remaining written installer activity is displayed, a particular
> > point
> > of interest after the usual "Unpacking linux-image-4.19.0-2-
> > powerpc64
> > (4.19.16-1) ...", being: "dpkg: error processing archive
> > /media/cdrom//pool-ppc64/main/l/linux/linux-image-4.19.0-2-
> > powerpc64_4.19.16-1_ppc64.deb (--unpack)", "Cannot copy extracted
> > data
> > for './boot/vmlinux-4.19.0-2-powerpc64' to '/boot/vmlinux-4.19.0-2-
> > powerpc64.dpkg-new': failed to write (No space left on device)",
> > "dpkg-
> > deb: error: paste subprocess was killed by signal (Broken pipe)",
> > "W:
> > Last kernel image has been removed, so removing the default
> > symlinks".
> >
> > It then goes on to normally select, prepare to unpack, and unpack
> > linux-image-powerpc64, only to stop with "Errors were encountered
> > while
> > processing: /media/cdrom//pool-ppc64/main/l/linux/linux-image-
> > 4.19.0-2-
> > powerpc64_4.19.16-1_ppc64.deb", "error: exiting on error base-
> > installer/kernel/failed-install", "WARNING **: Configuring
> > 'bootstrap-
> > base' failed with error code 30", "WARNING **: Menu item
> > 'bootstrap-
> > base' failed.", ending there.
> >
> > Debian 7.11, 8.11, and the May 2018 Sid netinstall cd, all install
> > onto
> > this machine (given the same partition tables) without a hitch,
> > along
> > with Ubuntu Server 16.04.5. Though admittedly they were all of
> > regular
> > powerpc decent and not ppc64 as seen here. I had also tried the
> > Debian
> > 9 installer port for ppc64
> > (http://cdimage.debian.org/cdimage/ports/9.0
> > /ppc64/iso-cd/) and got the same result displayed here, so it
> > appears
> > this may be a longstanding issue among the ppc64 builds, at least
> > from
> > my point of view.
> >
> > Putting that aside, maybe something was overlooked in the ppc64
> > images
> > specifically when building the new batches? To my knowledge, much
> > of it
> > should be synonymous with the regular powerpc builds, save for a
> > 64-bit
> > userspace over a 32-bit one, but of course, I'm not a developer.
> >
> > In any case, all is much appreciated.
> >
> > N
> Hi Noah,
>
> It sounds like you’re running out of free space in the partition that
> contains the /boot directory.
>
> Can you describe the steps you used to partition the disk? In
> particular, if you are re-using the /boot partition so as not to
> interfere with your existing installation, how much free space is
> there in it. E.g. on your existing (working) setup do
> df -HTP /boot
>
> hope it helps!
> Rick
>
Reply to: