Bugzilla – Bug 1213420
[ALP][Agama][Installer][Build1.50] Error performing the following action: Deleting vfat on /dev/sda1
Last modified: 2023-10-27 13:40:23 UTC
Created attachment 868277 [details] alp_server_installation_error ##### Summary: Do ALP Server installation with https://download.opensuse.org/repositories/systemsmanagement:/Agama:/Staging/images/iso/agama-live.aarch64-2.2.0-ALP-Build1.50.iso. After installation starts, partitioning always report: There was an error performing the following action: Deleting vfat on on /dev/sda1 (128.0 MiB). Continue installation with this error will not cause any trouble. Installation can finish as normal and system can boot up. Please refer to screenshot alp_server_installation_error. This error only occurs to ALP Server installation. ALP Micro has no such issue. ##### Steps to reproduce: 1. Load installation iso media into cd-rom and boot from cd-rom 2. Boot from installation entry 3. Wait for installation environment ready and login to https://host-to-install:9090 4. Select ALP Server, config user password/public ssh key and start installation 5. Partitioning report error: There was an error performing the following action: Deleting vfat on on /dev/sda1 (128.0 MiB). 6. Ignore error and continue installation 7. Installation finishes, reboot and system boots up ##### Expected result: No error reported during installtion ##### Actual result: After installation starts, partitioning always report: There was an error performing the following action: Deleting vfat on on /dev/sda1 (128.0 MiB). ##### Reproducibility 100% ##### Software Environment: agama-live.aarch64-2.2.0-ALP-Build1.50.iso ALP Server ##### Hardware Environment: Huawei XA320 V2 Kunpeng 920-4826 ##### Logs: 1. Screenshot alp_server_installation_error 2. yast_logs saved from options menu in agama installer
Created attachment 868278 [details] yast_logs
libstorage tries to remove the vfat on /dev/sda1 but wipefs complains that /dev/sda1 does not exist. It looks like a race condition: Removing /dev/sda2 triggers udev to regenerate the device node /dev/sda1. Adding another 'udevadm settle' should resolve the problem.
PR: https://github.com/openSUSE/libstorage-ng/pull/939
There is another issue reported before "continue installation": Probing file system with UUID ce91cb20-f08b-4a6f-96f9-af477d23db00 failed command '/bin/mount --read-only '/dev/sda2' '/tmp/libstorage-gYHKhM/tmp-mount-mZ5OqK' -o subvol=/' failed: stderr: mount: /tmp/libstorage-gYHKhM/tmp-mount-mZ5OqK: can't read superblock on /dev/sda2. dmesg(1) may have more information after failed mount system call. exit code: 32 But this error does not always present. Can not be reproduced every time. Please also refer to attached screenshots: alp_server_storage_error_01 alp_server_storage_error_02
Created attachment 868304 [details] alp_server_storage_error_01
Created attachment 868305 [details] alp_server_storage_error_02
Then please provide the complete YaST logs (using save_y2logs) for that problem. Best in another bug report.
(In reply to Arvin Schnell from comment #7) > Then please provide the complete YaST logs (using save_y2logs) for that > problem. Best in another bug report. Opened new bug https://bugzilla.suse.com/show_bug.cgi?id=1213460
SR: https://build.suse.de/request/show/303394
It is fixed already.