Skip to main content

Alma Elevate Boot Issue

Comments

16 comments

  • cPRex Jurassic Moderator
    Hey there! We did some testing on DNSOnly as part of this post, and it worked normally in our testing environment. It sounds like this specific issue is a problem with your system not properly detecting the kernel on the machine after the reboots, so I can't say for sure what would cause that.
    0
  • dstana
    Ok, I guess I'll do some more fooling around with it. Is 4.10.0-477.21.1.e18._8.x86_64 the correct kernel expected to be installed during the elevate process? Also, is there a mechanism in the elevate script to pause before the reboot to stage 4? This would give me a chance to see what's going on before diving in, or snapshot it at that point as well so I can try a few different things if needed.
    0
  • cPRex Jurassic Moderator
    That does seem like the correct kernel version, yes -
    0
  • dstana
    That does seem like the correct kernel version, yes -
    0
  • cPRex Jurassic Moderator
    That isn't an option - the whole process is automated.
    0
  • dstana
    That isn't an option - the whole process is automated.

    I just looked in the code for the script, I'm seeing a function in there called "request_manual_reboots", is there some reason I can't use that?
    0
  • cPRex Jurassic Moderator
    Better question - why would a manual reboot help the process? If it can't find the kernel, it's still going to fail. But no, ELevate needs to be left alone and is 100% automated.
    0
  • dstana
    Better question - why would a manual reboot help the process? If it can't find the kernel, it's still going to fail. But no, ELevate needs to be left alone and is 100% automated.

    Well before it does that reboot I can see what kernel was installed. Because the one it's looking for and the link you sent for the Alma kernel don't match up.
    0
  • cPRex Jurassic Moderator
    Could you submit a ticket to our team so we can take a look?
    0
  • dstana
    I'm not sure what there is to look at, after running the script the instance isn't accessible.
    0
  • dstana
    Well I found the --manual-reboots flag squirreled away in the docs, so I'm giving that a try. Not sure what the big deal is with trying that.
    0
  • cPRex Jurassic Moderator
    With that particular instance, there wouldn't be anything to look at, that's true. But, if you can reproduce this problem in your particular environment, we may be able to work with the host to improve that process.
    0
  • dstana
    Well, not sure what happened with that goofy kernel issue. But after a couple of other issues, I've successfully moved to Alma. The first one was done with --manual-reboot and I confirmed the correct kernels were installed before moving on to that last boot.
    0
  • cPRex Jurassic Moderator
    Nice!
    0
  • Paolo Toniolo

    Hi, when elevate process is locked to "Unmounting ..rpc_pipefs" (that retry infinite)
    is it possible force reboot? Will elevate process continue or will lock again at the same point?

    0
  • cPRex Jurassic Moderator

    Paolo Toniolo - I spoke with the ELevate team just now and we don't have any records of that exact error message.  Could you provide the full error, or create a ticket so this can be examined?

    0

Please sign in to leave a comment.