-
Notifications
You must be signed in to change notification settings - Fork 31
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
Segfault on CLR 36110 due to missing /dev/(root|boot) devices #248
Comments
It actually starts segfaulting from release 36080. I was bisecting it from 35000(default on AWS market) til latest in order to find last stable release. 35000 ok |
It seems that upgrade process from 36070 to 36080 removed /dev/root and more recent binaries cannot cope with it. I'm using AWS provided image so no extra /boot partition is needed hence creating /dev/root symlink was sufficient to mitigate the issue. From my perspective, it seems to be quite severe bc CL3 would be first choice for those who demand extra kick given by performance optimization and tuning kernel params is a common step to configure isolcpus, etc while this bug prevents CL3 from running at full potential. Thanks @MartB for workaround! |
Below you can find temporary solution which creates /dev/root at boot: [Service] [Install] /usr/sbin/cbm_fix: root_dev= exit 0 |
Describe the bug
Segmentation fault due to missing
/dev/(root|boot)
devices, not sure if intended, i would expect a tool like clr-boot-manager to still work in this case, neither do i know why its not created anymore. Would it not be better to fallback to/dev/disk/by-label/(root|boot)
if the /dev mapping isnt found?To Reproduce
Run clr-bootmanager update
To temporarily fix / workaround
Environment (please complete the following information):
Block Devices:
Additional context
dev_path=0x0 and the resulting PR=0x0
is the reason i guess, but i dont know how thats possible for the '/' lookup, as the blkid command works fine.The text was updated successfully, but these errors were encountered: