[Bug 1410573] Re: Expert mode installation fails with error
Mauricio Faria de Oliveira
mauricfo at linux.vnet.ibm.com
Mon Jan 26 12:19:56 UTC 2015
Here's the installer screens confirming patch [1] (in comment #10) fixes
the issue on ppc64el:
Running Vivid installer, with priority=low.
Go through Partition Disks -> Guided - use entire disk -> (select disk) -> Separate /home, /usr, /var, and /tmp partitions
Before patch:
-------------------
- / is ~300 MB
- /usr is 6.0 GB
┌────────────────────────┤ [!!] Partition disks ├─────────────────────────┐
│ │
│ This is an overview of your currently configured partitions and mount │
│ points. Select a partition to modify its settings (file system, mount │
│ point, etc.), a free space to create partitions, or a device to │
│ initialize its partition table. │
│ │
│ SCSI1 (0,0,0) (sda) - 137.4 GB QEMU QEMU HARDDISK │
│ > 1.0 MB FREE SPACE ▒ │
│ > #1 7.3 MB K ▒ │
│ > #2 299.9 MB f ext4 / │
│ > #3 6.0 GB f ext4 /usr ▒ │
│ > #4 3.0 GB f ext4 /var ▒ │
│ > #5 12.5 GB f swap swap ▒ │
│ > #6 399.5 MB f ext4 /tmp ▒ │
│ > #7 115.2 GB f ext4 /home ▒ │
│ > 1.0 MB FREE SPACE │
│ │
│ <Go Back> │
│ │
└─────────────────────────────────────────────────────────────────────────┘
After patch:
-----------------
- applied manually (nano /lib/partman/recipes-ppc64el/80multi), slight change due to 280/300 numbers.
- / is 5.0 GB
- /usr is gone
- /home accomodated the remaining 1.3 GB (previously 6.0 /usr + 0.3 / = 6.3 GB, now / is 5.0 GB. Difference is 1.3 GB)
┌────────────────────────┤ [!!] Partition disks ├─────────────────────────┐
│ │
│ This is an overview of your currently configured partitions and mount │
│ points. Select a partition to modify its settings (file system, mount │
│ point, etc.), a free space to create partitions, or a device to │
│ initialize its partition table. │
│ │
│ SCSI1 (0,0,0) (sda) - 137.4 GB QEMU QEMU HARDDISK │
│ > 1.0 MB FREE SPACE ▒ │
│ > #1 7.3 MB K ▒ │
│ > #2 5.0 GB f ext4 / │
│ > #3 3.0 GB f ext4 /var ▒ │
│ > #4 12.5 GB f swap swap ▒ │
│ > #5 399.5 MB f ext4 /tmp ▒ │
│ > #6 116.5 GB f ext4 /home ▒ │
│ > 1.0 MB FREE SPACE ▒ │
│ │
│ │
│ <Go Back> │
│ │
└─────────────────────────────────────────────────────────────────────────┘
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debian-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1410573
Title:
Expert mode installation fails with error
Status in debian-installer package in Ubuntu:
Triaged
Status in debian-installer source package in Vivid:
Triaged
Bug description:
1) Start 15.04 installation (as a Power KBM guest) using daily ISO (Jan 11)
2) Append priority=low option during installation
3) On partitioning disk panel select - Separate /home, /usr, /var, and /tmp partitions - option
4) Continue with the installation.
Installation fails with following message :
Configuring linux-image-3.18.0-8-generic
Unable to install the selected kernel
An error was returned while trying to install the kernel into the
target system.
Kernel package: 'linux-generic'.
Check /var/log/syslog or see virtual console 4 for the details.
<Continue>
I have attached following files captured after the failure.
hardware-summary lsb-release status partman
syslog
> Hi Sachin,
>
> It seems that we ran out of space on / while unpacking the kernel modules:
>
> an 12 08:30:55 in-target: Preparing to unpack
> .../linux-image-extra-3.18.0-8-generic_3.18.0-8.9_ppc64el.deb ...
> Jan 12 08:30:55 in-target: Unpacking linux-image-extra-3.18.0-8-generic
> (3.18.0-8.9) ...
> Jan 12 08:31:14 in-target: dpkg: error processing archive
> /media/cdrom//pool/main/l/linux/linux-image-extra-3.18.0-8-generic_3.18.0-8.
> 9_ppc64el.deb (--unpack):
> Jan 12 08:31:14 in-target: cannot copy extracted data for
> './lib/modules/3.18.0-8-generic/kernel/drivers/scsi/ips.ko' to
> '/lib/modules/3.18.0-8-generic/kernel/drivers/scsi/ips.ko.dpkg-new': failed
> to write (No space left on device)
> Jan 12 08:31:14 in-target: dpkg-deb: error: subprocess paste was killed by
> signal (Broken pipe)
>
> hardware-summary shows /dev/vda2 is fairly small. Was that intentional?
>
> df: Filesystem 1K-blocks Used Available Use% Mounted on
> df: none 836160 2496 833664 0% /run
> df: devtmpfs 4139712 0 4139712 0% /dev
> df: /dev/sr0 573810 573810 0 100% /cdrom
> df: /dev/vda2 275395 181991 74665 71% /target
> df: /dev/vda7 63427476 53064 60129408 0% /target/home
> df: /dev/vda6 369639 2062 343974 1% /target/tmp
> df: /dev/vda3 5636212 250392 5076472 5% /target/usr
> df: /dev/vda4 2818080 23964 2631252 1% /target/var
> df: /dev/sr0 573810 573810 0 100%
> /target/media/cdrom
Nope. The partitions and their size was suggested by the installer.
These are the default suggested values.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1410573/+subscriptions
More information about the foundations-bugs
mailing list