XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Sudden boot issues, emergency shell, root-lfgrma does not exist

    Scheduled Pinned Locked Moved Solved XCP-ng
    bootdracut
    2 Posts 1 Posters 32 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S Online
      seanmcg182
      last edited by seanmcg182

      Before today, I had XCP-NG 8.3 installed on the Metal of my server, and a LSI 3008 SAS Card going to a backplane, which was hidden in dom0 (Location 03:00.0, this is important), and passed through to a TrueNAS VM. No Issues, operated for years.

      Today, I installed a PCI to M.2 adapter, and to do so, I moved the LSI card to another slot, and put the M.2 adapter in the slot the LSI Card was in. Long story short, the new arrangement just made more sense to handle the bifurcation stuff needed.

      I booted XCP-NG, and TrueNAS reported that my Dataset was missing, but it saw the NVMe drive.
      Made sense once i checked a 'xe pci-list' , as the M.2 Adapter was now 03:00.0... Why it changed? don't know, I can't imagine that's an important detail.

      I saw the LSI 3008 card was on 01:00.0
      I pulled the usual xe pci-disable-dom0-access uuid=<pci uuid>
      Reboot the host.
      And it throws me into the Emergency Shell...

      After Google searching I find the google page about "Initrd is missing after an update"
      The weird part here is that the Emergency Shell is NOT reporting "/boot/initrd-4.19.0+1.img is missing"
      The Error I get is "Warning: /dev/disk/by-label/root-lfgrma does not exist"

      For thoroughness, I did load into the fallback kernel, and it loaded fine...
      Not sure where to go from here though.
      For testing purposes, I did attempt to Rebuild the initrd with 'dracut -f /boot/initrd-4.19.0+1.img 4.19.0+1' even though the error wasnt saying the img was the issue... but wanted to make sure
      A restart throws it back into the emergency shell.

      Any advice would be appreciated
      Any questions, I will gladly answer... I'm stumped

      S 1 Reply Last reply Reply Quote 0
      • S Online
        seanmcg182 @seanmcg182
        last edited by

        After a good sleep, I resolved half of my issue. I got my LSI Cards messed up, I accidentally hidan internal LSI3108 (Address 01:00.0) instead of the PCI Card LSI3008 (Address 05:00.0)...
        My Boot Drives run off of the internal card.

        From the fallback kernel, I was able to Modify /etc/grub-efi.cfg to remove the internal card form the hidden list.

        I now have a separate issue, but will make another post.

        1 Reply Last reply Reply Quote 0
        • S seanmcg182 marked this topic as a question
        • S seanmcg182 has marked this topic as solved

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        • First post
          Last post