| Thread Previous • Date Previous • Date Next • Thread Next |
@Andrew you cannot add req4focal tags without agreement that we are
accepting these. I'm not sure if there are any actions on this bug
report.
Closing tasks, dropping req4focal tag, and setting z-systems as
incomplete.
** Tags removed: req4focal
** Changed in: curtin
Status: In Progress => Fix Released
** Changed in: ubuntu-z-systems
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of curtin
developers, which is subscribed to curtin.
https://bugs.launchpad.net/bugs/1870037
Title:
curtin fails when part of a VG is around
Status in curtin:
Fix Released
Status in subiquity:
Invalid
Status in Ubuntu on IBM z Systems:
Incomplete
Bug description:
On a LPAR installation with DASD disks, where two DASD disks where
activated, but where the installation should just be done on the
second, I came across the following issue:
At 'Guided storage configuration' by default the first disk is pre-
selected '0X260B':
================================================================================
Guided storage configuration [ Help ]
================================================================================
Configure a guided storage layout, or create a custom one:
(X) Use an entire disk
[ 0X260B local disk 6.877G v ]
[ ] Set up this disk as an LVM group
[ ] Encrypt the LVM group with LUKS
Passphrase:
Confirm passphrase:
( ) Custom storage layout
[ Done ]
[ Back ]
I then selected the second disk 'LX260C':
================================================================================
Guided storage configuration [ Help ]
================================================================================
Configure a guided storage layout, or create a custom one:
(X) Use an entire disk
[ LX260C local disk 6.877G v ]
[ ] Set up this disk as an LVM group
[ ] Encrypt the LVM group with LUKS
Passphrase:
Confirm passphrase:
( ) Custom storage layout
[ Done ]
[ Back ]
I get the following summary - separated by 'available devices' and 'unused devices':
================================================================================
Storage configuration [ Help ]
================================================================================
FILE SYSTEM SUMMARY ^
│
MOUNT POINT SIZE TYPE DEVICE TYPE │
[ / 6.875G new ext4 new partition of local disk > ] │
│
│
AVAILABLE DEVICES │
│
DEVICE TYPE SIZE │
[ 0X260B local disk 6.877G > ]│
partition 1 existing, already formatted as ext4, not 1.000G >
mounted
partition 2 existing, unused 5.876G >
[ Create software RAID (md) > ]
[ Create volume group (LVM) > ] v
[ Done ]
[ Reset ]
[ Back ]
================================================================================
Storage configuration [ Help ]
================================================================================
DEVICE TYPE SIZE ^
[ 0X260B local disk 6.877G > ]
partition 1 existing, already formatted as ext4, not 1.000G >
mounted
partition 2 existing, unused 5.876G >
[ Create software RAID (md) > ] │
[ Create volume group (LVM) > ] │
│
│
USED DEVICES │
│
DEVICE TYPE SIZE │
[ LX260C local disk 6.877G > ]│
partition 1 new, to be formatted as ext4, mounted at / 6.875G > │
v
[ Done ]
[ Reset ]
[ Back ]
After proceeding I later face this crash:
================================================================================
Storage configuration [ Help ]
================================================================================
DEVICE TYPE SIZE ^
[ 0X260B local disk 6.877G > ]
┌────────────────────── Confirm destructive action ──────────────────────┐
│ │
│ Selecting Continue below will begin the installation process and │
│ result in the loss of data on the disks selected to be formatted. │
│ │
│ You will not be able to return to this or a previous screen once the │
│ installation has started. │
│ │
│ Are you sure you want to continue? │
│ │
│ [ No ] │
│ [ Continue ] │
│ │
└────────────────────────────────────────────────────────────────────────┘
[ Reset ]
[ Back ]
================================================================================
Profile setup [ Help ]
================================================================================
Enter the username and password you will use to log in to the system. You
can configure SSH access on the next screen but a password is still needed
for sudo.
Your name: ubuntu
Your server's name: s1lp15
The name it uses when it talks to other computers.
Pick a username: ubuntu
Choose a password: ********
Confirm your password: ********
[ Done ]
================================================================================
An error occurred during installation [ Help ]
================================================================================
┌────────────────────────────────────────────────────────────────────────┐
│ │
│ Sorry, there was a problem completing the installation. │
│ │
│ [ View full report ] │
│ │
│ If you want to help improve the installer, you can send an error │
│ report. │
│ │
│ [ Send to Canonical ] │
│ │
│ Do you want to try starting the installation again? │
│ │
│ [ Restart the installer ] │
│ │
│ [ Close report ] │
│ │
└────────────────────────────────────────────────────────────────────────┘
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu21
Architecture: s390x
CasperVersion: 1.441
CrashDB: {'impl': 'launchpad', 'project': 'subiquity'}
CurrentDmesg:
[ 0.091308] Linux version 5.4.0-18-generic (buildd@bos02-s390x-009) (gcc ver
sion 9.2.1 20200306 (Ubuntu 9.2.1-31ubuntu3)) #22-Ubuntu SMP Sat Mar 7 18:05:50
UTC 2020 (Ubuntu 5.4.0-18.22-generic 5.4.24)
[ 0.091311] setup.6bac7a: Linux is running natively in 64-bit mode
[ 0.091342] setup.b050d0: The maximum memory size is 43008MB
[ 0.091359] numa.196305: NUMA mode: plain
[ 0.091399] cpu.33a262: 8 configured CPUs, 0 standby CPUs
[ 0.091410] cpu.643eaf: The CPU configuration topology of the machine is: 0
0 4 2 3 8 / 4
[ 0.091994] Write protected kernel read-only data: 11696k
[ 0.092302] Zone ranges:
[ 0.092303] DMA [mem 0x0000000000000000-0x000000007fffffff]
[ 0.092304] Normal [mem 0x0000000080000000-0x0000000a7fffffff]
[ 0.092305] Movable zone start for each node
[ 0.092306] Early memory node ranges
[ 0.092307] node 0: [mem 0x0000000000000000-0x00000007ffffffff]
[ 0.092406] Initmem setup node 0 [mem 0x0000000000000000-0x00000007ffffffff]/var/crash/1585726685.214678526.install_fail.crash
curtin.util.ProcessExecutionError: Unexpected error while running command.
Command: ['vgchange', '--activate=y']
Exit code: 5
Reason: -
Stdout: 0 logical volume(s) in volume group "s1lp15_vg" now active
Stderr: WARNING: Couldn't find device with uuid 4uOyAr-gwjV-Wx0F-BX2q-oxF4-IQH
s-9Ic6Xh.
WARNING: VG s1lp15_vg is missing PV 4uOyAr-gwjV-Wx0F-BX2q-oxF4-IQHs-9I
c6Xh (last written to /dev/dasda2).
Refusing activation of partial LV s1lp15_vg/s1lp15_lv. Use '--activat
ionmode partial' to override.
Unexpected error while running command.
Command: ['vgchange', '--activate=y']
Exit code: 5
Reason: -
Stdout: 0 logical volume(s) in volume group "s1lp15_vg" now active
Stderr: WARNING: Couldn't find device with uuid 4uOyAr-gwjV-Wx0F-BX2q-oxF4-IQH
s-9Ic6Xh.
WARNING: VG s1lp15_vg is missing PV 4uOyAr-gwjV-Wx0F-BX2q-oxF4-IQHs-9
Ic6Xh (last written to /dev/dasda2).
I only selected to reformat the entire disk, which seem to have happend, and afterwards the entire disk is used for the new installation.
I'm wondering about LVM and VG here, is using LVM always the default in case an installation is done on an entire disk? I don't think so ...
I've attached the full /var/log and /var/crash ...
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1870037/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
