On 03.01.2023 13:16, Alessandro Baggi wrote:
Hi Jack, I'm sorry to bother you during holidays.
I encountered a strange problem installing AlmaLinux 9.1 on a RAID1 (MDADM) with the current configuration:
- /boot/efi on md125 Note that any EFI modification by BIOS firmware (it can happen) or by EFI utilities (like firmware update, running memtest and saving report) will corrupt and degrade your raid. Moreover note that chainloading in grub does not work with virtual devices (like md raid).
by far the easiest and safest way is to have individual ESP partitions and let's say they are mounted to /boot/efi and /boot/efi2 just make a systemd unit with the form of: root@hal: ~ # cat /etc/systemd/system/esp_sync.service [Unit] Description=Sync ESP1 to ESP2 DefaultDependencies=no ConditionPathIsDirectory=/boot/efi/EFI/ ConditionPathIsDirectory=/boot/efi2/EFI/ After=final.target [Service] Type=oneshot ExecStart=/usr/bin/cp -af /boot/efi/EFI /boot/efi2/ [Install] WantedBy=multi-user.target (you could also use rsync if it's guaranteed to be present) and attach to this service a timer with [Timer] OnStartupSec=40 and/or a path unit with a specification like [Path] Unit=esp_sync.service PathModified=/boot/efi/EFI/almalinux also make sure that /boot/efi/EFI/almalinux/grub.cfg is a stub with a content like: [root@fst09 ~]# cat /boot/efi/EFI/almalinux/grub.cfg search --no-floppy --fs-uuid --set=dev f9c0f1b7-7f36-4b80-9563-6b2702b14c19 set prefix=($dev)/boot/grub2 export $prefix configfile $prefix/grub.cfg (you get the UUID from blkid output for the md device) this way, content of ESP is minimal and rarely changes AND you have a ESP fallback in the way of second ESP you can put ",nofail,errors=continue" for the mounting of ESP within system as ESP is not really needed for system running. HTH, Adrian
- swap on md126 - / on md127
disks are 2 SSD MLC Type.
After the installation, if I reboot the system I get:
"md: md125 stopped" (it is printed many times like in a loop)
alternated with:
"systemd-shutdown[1]: Not all MD devices stopped, 1 left Stopping MD Devices Stopping MD /dev/md125 (9:125)"
and the system hangs on this loop until I cut the power.
I encountered this issue on my Workstation with Asus Prime Z490-A / i9-10850k.
I tried with another workstation that runs on Asus Prime Z370-A / i7 8700K, to exclude bad SATA controller and bad cables.
Also on the second workstation the problem is found.
I tried to replicate this using 9.0 ISO. The problem does not occur until I update to 9.1
I tried also with 8.7. No problem here.
I tried also RockyLinux 9.1 and got the same problem but with different messages:
"block device autoconfig is deprecated and will removed"
alternated with:
"blkdev_get_no_open: 270 callbacks suppressed."
To stop the machine I need to cut the power.
I tried also Debian 11.5 without problems.
So seems that the problem is 9.1 related. Actually I can't test the same with RHEL 9.1 but probably the problem will occour also on RHEL 9.1
There is a way to fix this or I should wait an upgrade?
Thank you in advance. _______________________________________________ AlmaLinux Users mailing list -- users@lists.almalinux.org To unsubscribe send an email to users-leave@lists.almalinux.org
-- ---------------------------------------------- Adrian Sevcenco, Ph.D. | Institute of Space Science - ISS, Romania | adrian.sevcenco at {cern.ch,spacescience.ro} | ----------------------------------------------