-
-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
First boot after installing never finishes ("A start job is running for Monitoring of LVM2 mirrors, ...") #7335
Comments
I wonder: Could I enable core dumps easily in the system, and would it be helpful to have the actual core dump? Or have a different lvm to replace the one that is failing? |
can you provide how you do custom partition ? |
Basically I was following https://www.qubes-os.org/doc/custom-install/ with the exception that I skipped partitioning as the correct partitions did exist already. So I started from creating a new LUKS device on an existing partition. |
Mostly it because you have wrong partition / bad lvm config, maybe try zero disk first, then follow the guide again. |
I'm unsure whether speculation is the best way to solve the issue: I can boot Windows 10 without a problem, I can boot Linux (openSUSE Laap 15.3) without a problem, I can boot Tails without a problem, I can boot Qubes OS 4.0 without a problem. |
Here are some details:
Partition1 and 2 are the relevant ones:
The corresponding command line from GRUB is:
|
Running Qubes OS 4.0, my four IRST disks look like this:
And here are the details:
|
While no fixed installation medium is available, I'd suggest to add something helpful to https://www.qubes-os.org/doc/installation-troubleshooting/ |
try with single disk first : cryptsetup -c aes-xts-plain64 -h sha512 -s 512 luksFormat /dev/sda2 https://forum.qubes-os.org/t/4-1-installer-lvm-partitioning-hard-to-customize-missing-space/6155/5 |
Is #7335 (comment) suggesting to unplug all the other disks? |
Would it be possible to get a backtrace from the core dump? |
By default the segfault does not create a core dump. I'm not deep enough into it: |
I’m not sure, but it is probably in some documentation. |
@sjvudp can you try |
no just create partition like that, and follow above command. additional storage could be added after install or you could reinstall again and add some device in volume group. |
That did it! However, even after having installed all updates, I need that parameter on every boot! |
There is also some strange effect when shutting down: it waits for some LVM deactivation for a rather long time, delaying the shutdown or reboot. |
When running a debug shell on tty9 during boot via "systemd.debug_shell=1", I realized that a "vgchange --monitor y" seems to hang. However when I enter that command manually, I get a syntax error (it wants a VG name). When I use "vgchange --monitor y qubes_dom0", the command exits very soon. |
Also having this problem from an in place upgrade to 4.1 from 4.0. Everything seemed to go fine (except for debian qubes) - first boot after upgrade goes into infinite wait for lvm2. Unfortunately grub appears not to be working correctly and I cannot use the workaround mentioned above. |
Well, if you cannot do it interactively, you could do it the hard way: Boot some rescue system, mount the |
Well, let me update that the issue still exists on a new installation (and new partitioning) of Qubes OS 4.2.2 (same fix still works, however). The problem occurs after switching root and luksOpen the PV. |
How to file a helpful issue
Qubes OS release
4.1.0
Brief summary
Booted installer, perpared the disks, ran installation.
All fine without any error.
Then on boot from harddisk nothing happens, i.e. initrd never "switches root"
Steps to reproduce
Expected behavior
Installation continues
Actual behavior
Boot never finishes (see attached screen photo).
Examining the journal of the failed boots, I found this:
That segfault doesn't look good!
The last things that seem to happen on boot are:
A key indicator might be "kernel: md124: p1" that could mean mdadm was built without IRST support:
Usually there are four md-devices (two per IRST RAID: one real RAID and one pseudo RAID (IRST)). Maybe LVM chokes on the pseudo RAID.
Additional info (that might be important)
The system has two IRST software RAID1 (one for Windows, one for Linux, but none for Qubes OS (that is on a different non-RAID disk)
The text was updated successfully, but these errors were encountered: