Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Manual partitioning without wipe: deleting an existing partition crashes installer (wipefs runs on deleted partition path)

Aperta Adatta ai principianti
  • Qualcosa non va?
#4,849 1 commento 1 reazione 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@Kolgrim33 ci sta già lavorando.

Dal 25/10/2026.

  • #4853 di @Kolgrim33 — aperta

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
72/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
linux, python
Ambito
backend, operating-systems

Direzione di ricerca

Leggi archinstall/lib/disk/device_handler.py intorno a DeviceHandler.partition() e _setup_partition(), poi esamina i metodi di supporto dello stato di PartitionModification in archinstall/lib/models/device.py. Segui il percorso delle voci DELETE fino al ciclo di cancellazione delle firme e riproduci il problema con un disco non vuoto usando il partizionamento manuale senza cancellazione. Il lavoro è completato quando l’eliminazione di una partizione esistente non esegue più wipefs sul relativo percorso del dispositivo rimosso e l’installazione prosegue.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

ISO version

Not reproduced from a specific ISO — this bug was found by source analysis of master (commit 2c25540) and verified at component level (see evidence below). The affected code path exists in current master.

The installation log

No full install log available (static analysis). The failure point is deterministic, see "Root cause" below. The uncaught exception raised at that point is:

SysCallError: ['wipefs', '--all', '/dev/sdaX'] exited with abnormal exit code [1]:
wipefs: error: /dev/sdaX: probing initialization failed: No such file or directory

wipefs returning exit code 1 for a non-existent device node was verified locally:

$ wipefs --all /dev/sda99
wipefs: error: /dev/sda99: probing initialization failed: No such file or directory
$ echo $?
1
Summary

When installing onto a non-empty disk via manual partitioning without wiping the whole device, marking any existing partition for deletion crashes the installation with an uncaught SysCallError: the signature-wipe loop runs wipefs --all against the device path of the partition that was just deleted.

Steps to reproduce
  1. Start archinstall on a machine with a disk that already contains partitions (e.g. a previous installation).
  2. Disk setup → Manual Partitioning (do not wipe the whole disk).
  3. Select an existing partition → Delete partition.
  4. Proceed with the installation (creating new partitions in the freed space afterwards is optional — not required to trigger the bug).
Expected behavior

The partition marked as deleted is removed during DeviceHandler.partition() and the installation continues.

Actual behavior

The installation aborts with the uncaught SysCallError shown above as soon as partition() reaches the signature-wipe loop.

Root cause

Verified on master @ 2c25540:

  1. DeviceHandler.partition() collects every partition that is not EXIST — which also includes DELETE entries — into filtered_part (archinstall/lib/disk/device_handler.py:543):

    # don't touch existing partitions
filtered_part = [p for p in modification.partitions if not p.exists()]

    PartitionModification.exists() only checks status == ModificationStatus.EXIST (archinstall/lib/models/device.py:1028-1029).

  2. For a DELETE entry, _setup_partition() deletes the on-disk partition and returns early, leaving part_mod.dev_path pointing at the now-removed device node (archinstall/lib/disk/device_handler.py:349-361):

    if requires_delete and part_mod.status in [ModificationStatus.MODIFY, ModificationStatus.DELETE]:
    ...
    disk.deletePartition(part_info.partition)

if part_mod.status == ModificationStatus.DELETE:
    return

  3. After disk.commit() (device_handler.py:559) the kernel removes the /dev/sdaX node.

  4. The signature-wipe loop then iterates over the same filtered_part list and runs wipefs on the stale path of the deleted partition (device_handler.py:561-566):

    # Wipe filesystem/LVM signatures from newly created partitions
# to prevent "signature detected" errors
for part_mod in filtered_part:
    if part_mod.dev_path:
        debug(f'Wiping signatures from: {part_mod.dev_path}')
        SysCommand(f'wipefs --all {part_mod.dev_path}')

    Despite the comment, the list is not limited to newly created partitions. The if part_mod.dev_path: guard never filters DELETE entries out: __post_init__ requires a path for all is_exists_or_modify() entries, and that set includes DELETE (archinstall/lib/models/device.py:927-928, 1031-1036).

  5. SysCommandWorker.__exit__ raises SysCallError for any non-zero exit code (archinstall/lib/command.py:111-116) and the call site has no try/except → the installation crashes.

The path is fully reachable from the guided TUI: manual partitioning defaults to wipe=False (archinstall/lib/disk/disk_menu.py:355) and the "Delete partition" action sets status = ModificationStatus.DELETE (archinstall/lib/disk/partitioning_menu.py:355-362).

Suggested fix

Skip entries that were only deleted when wiping signatures:

for part_mod in filtered_part:
    if part_mod.status == ModificationStatus.DELETE or not part_mod.dev_path:
        continue
    debug(f'Wiping signatures from: {part_mod.dev_path}')
    SysCommand(f'wipefs --all {part_mod.dev_path}')

(or iterate over [p for p in filtered_part if p.is_create_or_modify()] instead).

Related observation (same scenario)

While repartitioning a non-empty disk, DeviceHandler.umount_all_existing() (device_handler.py:505-517) only unmounts filesystems and locks LUKS devices — it never calls swapoff (no swapoff call exists anywhere in the codebase). If an existing swap partition on the target disk is active, deleting that partition will make parted fail with "Device or resource busy".

Lingua principale
Python
Stelle
8.5k
Fork
785
Merge medio
15h 35m
PR unite (30g)
16

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di archlinux/archinstall

Tutte le issue di archlinux/archinstall

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.