Error/crash while trying to wipe disk during 23.04+ install

Bug #2016860 reported by Frank Heimes
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu on IBM z Systems
Fix Released
High
Frank Heimes
subiquity
Fix Released
High
Dan Bungert
subiquity (Ubuntu)
Fix Released
High
Unassigned

Bug Description

While testing the 23.04 RC image (timestamp April 15th)
and using
subiquity 23.04.1 4677
on z/VM (s390x) with a DASD FBA disk,
the installed crashed during installation with:

 devsync happy - path /dev/dasda now exists
 return volume path /dev/dasda
 Running command ['wipefs', '--all', '--force', '/dev/dasda'] with allowed retur
n codes [0] (capture=False)
 Wiping path: dev:/dev/dasda1 kname:dasda1 partnum:1
 Running command ['wipefs', '--all', '--force', '/dev/dasda1'] with allowed retu
rn codes [0] (capture=False)
 wipefs: error: /dev/dasda1: probing initialization failed: No such file or directory
 An error occured handling 'disk-dasda': ProcessExecutionError - Unexpected error while running command.
 Command: ['wipefs', '--all', '--force', '/dev/dasda1']
 Exit code: 1
 Reason: -
 Stdout: ''
 Stderr: ''
 finish: cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL: configuring disk: disk-dasda
 TIMED BLOCK_META: 17.898
 finish: cmd-install/stage-partitioning/builtin/cmd-block-meta: FAIL: curtin com
mand block-meta
 Traceback (most recent call last):
   File "/snap/subiquity/4677/lib/python3.10/site-packages/curtin/commands/main.py", line 202, in main
     ret = args.func(args)
   File "/snap/subiquity/4677/lib/python3.10/site-packages/curtin/log.py", line 97, in wrapper
     return log_time("TIMED %s: " % msg, func, *args, **kwargs)
   File "/snap/subiquity/4677/lib/python3.10/site-packages/curtin/log.py", line 79, in log_time
     return func(*args, **kwargs)
   File "/snap/subiquity/4677/lib/python3.10/site-packages/curtin/commands/block_meta.py", line 124, in block_meta
     return meta_custom(args)
   File "/snap/subiquity/4677/lib/python3.10/site-packages/curtin/commands/block_meta.py", line 2191, in meta_custom
     handler(command, storage_config_dict, context)
   File "/snap/subiquity/4677/lib/python3.10/site-packages/curtin/commands/block_meta.py", line 768, in disk_handler
     block.wipe_volume(disk, mode=info.get('wipe'))
   File "/snap/subiquity/4677/lib/python3.10/site-packages/curtin/block/__init__.py", line 1324, in wipe_volume
     quick_zero(path, partitions=True, exclusive=exclusive)
   File "/snap/subiquity/4677/lib/python3.10/site-packages/curtin/block/__init__.py", line 1233, in quick_zero
     quick_zero(pt, partitions=False)
   File "/snap/subiquity/4677/lib/python3.10/site-packages/curtin/block/__init__.py", line 1214, in quick_zero
     util.subp(['wipefs', '--all', '--force', path])
   File "/snap/subiquity/4677/lib/python3.10/site-packages/curtin/util.py", line 275, in subp
     return _subp(*args, **kwargs)
   File "/snap/subiquity/4677/lib/python3.10/site-packages/curtin/util.py", line 139, in _subp
     raise ProcessExecutionError(stdout=out, stderr=err,
 curtin.util.ProcessExecutionError: Unexpected error while running command.
 Command: ['wipefs', '--all', '--force', '/dev/dasda1']
 Exit code: 1
 Reason: -
 Stdout: ''
 Stderr: ''
 Unexpected error while running command.
 Command: ['wipefs', '--all', '--force', '/dev/dasda1']
 Exit code: 1
 Reason: -
 Stdout: ''

The DASD FBA disk exists:

root@ubuntu-server:/# lsdasd
Bus-ID Status Name Device Type BlkSz Size Blocks
================================================================================
0.0.0101 active dasda 94:0 FBA 512 16383MB 33554368
root@ubuntu-server:/# ls -l /dev/dasd*
crw------- 1 root root 10, 120 Apr 18 10:31 /dev/dasd_eer
brw-rw---- 1 root disk 94, 0 Apr 18 10:35 /dev/dasda
brw-rw---- 1 root disk 94, 1 Apr 18 10:35 /dev/dasda1
root@ubuntu-server:/#

But the installer seems to fail wiping it.

The full logs (var/crash and /var/log) are attached.

Related branches

Revision history for this message
Frank Heimes (fheimes) wrote :
Changed in subiquity (Ubuntu):
assignee: nobody → Dan Bungert (dbungert)
Changed in ubuntu-z-systems:
assignee: Dan Bungert (dbungert) → Frank Heimes (fheimes)
Changed in subiquity (Ubuntu):
importance: Undecided → High
Revision history for this message
Frank Heimes (fheimes) wrote (last edit ):

At the installer shell I manually wiped the disk myself with:
root@ubuntu-server:/# wipefs -a -f /dev/dasda1
root@ubuntu-server:/# wipefs -a -f /dev/dasda
and after restarting the installation from crash I was able to complete an installation w/o issues (using no LVM).

Then doing another install on the same system leaving the defaults for disk config (means using LVM) worked as well.

Another install (again on the same system using the defaults) completed again fine.

So somehow smells like an issue wiping out the disk if old LVM data was on the disk?!
(and with that it could be a duplicate of LP#1993633)

Revision history for this message
Frank Heimes (fheimes) wrote :

I think that this just happened to me on mantic, too.

Revision history for this message
Frank Heimes (fheimes) wrote :

I retried this again with the 23.10 ISO image and installer
and wasn't able to reproduce this anymore.
Neither with a manual install, not with an autoinstall (using a z/VM instance with FBA disks).

Dan Bungert (dbungert)
affects: subiquity (Ubuntu) → subiquity
Changed in subiquity:
status: New → Triaged
tags: added: rls-nn-incoming
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: New → Triaged
Revision history for this message
Frank Heimes (fheimes) wrote :

Just fyi (and cross-referencing), also happens on a L1-III aka z15 with NVMe disk attached:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2056207/comments/12

Revision history for this message
Dan Bungert (dbungert) wrote :

Removing the incoming tag after chat with Frank. We should attempt to fix this, but we are sticking with the "High" importance.

tags: removed: rls-nn-incoming
tags: added: foundations-todo
Dan Bungert (dbungert)
Changed in subiquity (Ubuntu):
status: New → Triaged
importance: Undecided → High
Dan Bungert (dbungert)
tags: added: fr-7062
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2016860

tags: added: iso-testing
Dan Bungert (dbungert)
summary: - Error/crash while trying to wipe disk during 23.04 install
+ Error/crash while trying to wipe disk during 23.04+ install
Revision history for this message
Frank Heimes (fheimes) wrote :

While testing with the today's ISO image (March 15th) I noticed that things have improved, especially on DASD/ECKD and FCP/SCSI systems.

Where I'm seeing that now mainly is on DASD/FBA systems, that are a bit special, anyway attaching the crash file and entire /var/log - just in case...

Frank Heimes (fheimes)
tags: added: installation
removed: installer
Dan Bungert (dbungert)
Changed in subiquity:
status: Triaged → In Progress
Frank Heimes (fheimes)
Changed in ubuntu-z-systems:
status: Triaged → In Progress
Revision history for this message
Dan Bungert (dbungert) wrote :

Frank - please find a test snap on channel edge/lp-2016860

Revision history for this message
Frank Heimes (fheimes) wrote :

Hi Dan, things look very promising, since I installed using edge/lp-2016860 on this ECKD FBA guest, where the situation was worst, and the install succeeded !

(Trying now on more and different systems and disk types ...)

Revision history for this message
Frank Heimes (fheimes) wrote :

I did more tests, on LPAR, z/VM, with FCP/SCSI, DASD/ECKD and have not faced this issue a single time (or any udev related issues).

So I would consider the installer "edge/lp-2016860" as fixed and working.
(I used the noble daily from today March 15th as base.)

Revision history for this message
Dan Bungert (dbungert) wrote :

This was merged to Subiquity and is present in current Noble ISO builds.

tags: removed: foundations-todo
Changed in subiquity:
status: In Progress → Fix Committed
Changed in subiquity (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Frank Heimes (fheimes) wrote :

Great, thx for the update Dan!

Changed in ubuntu-z-systems:
status: In Progress → Fix Committed
Revision history for this message
Frank Heimes (fheimes) wrote :

Based on the recent ISO, QA Tracker and installation tests around the 24.04 release,
this issues got solved and it did not happened anymore with recent images, hence I'm closing this LP bug.

Changed in ubuntu-z-systems:
status: Fix Committed → Fix Released
Changed in subiquity:
status: Fix Committed → Fix Released
Changed in subiquity (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.