Comment 1 for bug 1868177

Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

The tracebacks look like this:

  File "/snap/subiquity/1561/lib/python3.6/site-packages/curtin/block/clear_holders.py", line 662, in clear_holders
    shutdown_function(dev_info['device'])
  File "/snap/subiquity/1561/lib/python3.6/site-packages/curtin/block/clear_holders.py", line 323, in wipe_superblock
    _wipe_superblock(mp_dev if mp_dev else blockdev)
  File "/snap/subiquity/1561/lib/python3.6/site-packages/curtin/block/clear_holders.py", line 371, in _wipe_superblock
    exclusive=exclusive, strict=strict)
  File "/snap/subiquity/1561/lib/python3.6/site-packages/curtin/block/__init__.py", line 1127, in wipe_volume
    quick_zero(path, partitions=False, exclusive=exclusive, strict=strict)
  File "/snap/subiquity/1561/lib/python3.6/site-packages/curtin/block/__init__.py", line 1041, in quick_zero
    exclusive=exclusive, strict=strict)
  File "/snap/subiquity/1561/lib/python3.6/site-packages/curtin/block/__init__.py", line 1084, in zero_file_at_offsets
    raise ValueError(m_short.format(**msg_vals))
ValueError: /dev/sda1 (size=524288): 1048576 bytes from 0 > size.

Looks like it's probably trying to wipe an extremely small partition? I guess subiquity could prevent people from trying to reuse those.