You are not logged in.
I'm actually running the SystemRescue live ISO, which I hope is not an issue for this forum. If so, I'll ask elsewhere. Versions:
systemd: 256.5-1-arch
kernel: 6.6.47-1-lts
There's something weird going on with this system. I'm running the OS out of RAM, with no drives mounted. There is an unmounted drive in the system, and I over-write the start of this drive (including boot sector/partition tables/etc) with a new OS image (with LVM).
About 10 minutes after booting SystemRescue/Arch, I get to a point where the (unmounted) drive has been over-written, and I'm expecting to carry on with my bash script (which is running a 'dialog' menu/GUI). However, the message 'Started /usr/bin/lvm vgchange -aay --autoactivation event vg0' now pops up, messing up the menu. The script does various file redirections, and the message doesn't appear in the syslog.
It seems that systemd has been hanging around in the background, and now detects a new LVM drive, and starts autoactivation. Does this make any sense? There is no event that looks like hot-plugging a new drive. It looks very much like systemd has been scanning the drive, looking for changes.
If this is the problem, I'm hoping to fix it by starting the script with a 'vgchange --setautoactivation n', but I'd appreciate a sanity check first.
Update: adding 'vgchange --setautoactivation n' makes no difference to this.
Last edited by EML (2024-11-30 18:21:05)
Offline