Rocky fails to boot with /dev/mapper/rl-home device timed out.

skalinkin commented 1 year ago

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

When filing a bug, please include the following headings if possible. Any example text in this template can be deleted.

Overview of the Issue

After building the project from here [https://github.com/skalinkin/packer-for-rocky-vagrant/tree/vb-7.0.8] with packer 1.9.1 and virtualbox-iso builder, Vagrant VM fails to load.

Reproduction Steps

On Windows machine check out [https://github.com/skalinkin/packer-for-rocky-vagrant/tree/vb-7.0.8] this, execute pack.bat After build finished run vagrant up

Packer version

1.9.1

Simplified Packer Template

https://github.com/skalinkin/packer-for-rocky-vagrant/blob/ad983192978461e06ac0c114f6cd981766691c95/rocky9.json

Operating system and Environment details

OS Name Microsoft Windows 10 Pro Version 10.0.19045 Build 19045 Processor Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz, 3600 Mhz, 8 Core(s), 16 Logical Processor(s)

Log Fragments and crash.log files

Set the env var PACKER_LOG=1 for maximum log detail.

skalinkin commented 1 year ago

What I found so far, is that kickstart autopart command will create separate partition for /home directory when disk has more then 50 Gigs. In my case I had 125 Gigs. And when packer packed the box and vagrant unpack it, some how that partition getting lost. This not existing device/disk/partition is causing the system fail to boot.

urog commented 1 year ago

There appears to be an issue with the vagrant post-processor. Using packer to produce the virtualbox ovf works fine: I am able to import that directly into Virtualbox and start the VM without any mounting issues. Furthermore, I am able to also manually create a vagrant export of the VM using vagrant package --base rocky9, and then use the resulting box in my Vagrantfile and it works fine.

Kadalia commented 11 months ago

Hello,

I confirm, Rocky 9.3 can be installed on TrueNas Scale 23.10.0.1 ONLY if you use a disk with capacity less than 50G. If the disk is larger ... you'll have the same error: /dev/mapper/rl-home can't be found. I understand that it appears to be an issue with vagrant ... but I do not understand if it's an issue with trueNas or with Rocky. (I can install Rocky in other VM or physical boxes with no issue)

I am new with TrueNas, but I have some IT knowledge but really not enough to dig into this problem. TrueNas Rocks !! So it has to be able to install Rocky ! :-)

BTW .. Spice ? Loses mouse and keyboard every 2 minutes, you have to refresh the browser ... boring

Thank-you

kt315ua commented 11 months ago

@skalinkin @Kadalia @urog We have faced with the same issue with LVM partitioning. In our case, it's Almalinux 9.3. We perform migration from Alma 8.6 to 9.3 and faced with identical issue. After investigation, we found that RedHat 9 has changes with LVM default configuration and got different LVM behavior. There were found next topics and solutions: https://serverfault.com/questions/1093110/linux-lvm-pvid-last-seen-on Screenshot_20231222_160542 Bug link - https://bugzilla.redhat.com/show_bug.cgi?id=1965941 Bug solution: Screenshot_20231222_160717

In our case, we perform double fix to be in safe :)

sed -i 's/# use_devicesfile = 1/use_devicesfile = 0/' /etc/lvm/lvm.conf
rm -vf /etc/lvm/devices/system.devices

Also, @skalinkin can you rename bug topic to next example: Rocky 9 and Almalinux 9 fails to boot with LVM volumes: /dev/mapper/rl-home device timed out And if solution works, put a mark in topic name (Resolved) Rocky 9 and Almalinux... It should help to others to find solution :) Thanks!

kt315ua commented 11 months ago

Also, about 50GB disk size... in my case, we don't use default kickstart, we use our custom kickstart and always use LVM. So, maybe default kickstart doesn't use installation with LVM volumes if disk is so small. Anyway, you can check it :) PS: Happy holidays!

Hkanfshujian commented 9 months ago

the same problem as me , when i remove /etc/lvm/devices/system.devices is ok

hashicorp / packer