Announcement

Collapse
No announcement yet.

Where are UUIDs stored?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    [RESOLVED] Where are UUIDs stored?

    Yesterday, I re-installed a fresh 24.04 system and configured stuff like firefox and libreoffice. This morning, I cannot boot it. It bombs with

    ALERT! UUID=668... does not exist.
    But when I boot another system and then mount the root partition for the defective system, blkid finds no partition with that UUID. In order to identify the problem, one lead seems to me to be what in the world that partition is, i.e., what /dev/sd-something it corresponds to. So how do I go about finding that?

    I plugged in and mounted the installation USB key, which came up as sde, but nothing shows up the UUID's for sde. Are they not stored somewhere on the partition? I certainly can't find it with gdisk.

    I have re-booted both those systems since installation and they worked fine. Mystery.
    Last edited by joneall; Oct 14, 2024, 04:18 AM.
    'I must have a prodigious quantity of mind; it takes me as much as a week sometimes to make it up.' Mark Twain

    #2
    I have discovered the file command and run 'sudo file -sL /dev/sd,,,,/ on all my partitions. No UUID=66...

    'I must have a prodigious quantity of mind; it takes me as much as a week sometimes to make it up.' Mark Twain

    Comment


      #3
      Strictly speaking, this query is resolved, since I found out how to find the UUID for a device /dev/sdx.
      'I must have a prodigious quantity of mind; it takes me as much as a week sometimes to make it up.' Mark Twain

      Comment


        #4
        use the command blkid

        But if , as a random, pulled-out-of-my-butt example: you have an old entry in your BIOS that points to an old partition for some reason, and your BIOS boot order is set to that stale entry
        I am assuming you see this error early on, and do not get to grub.

        If you moved or resized partitions since installing (not likely) that would obviously change that partition's UUID

        Comment


          #5
          But if , as a random, pulled-out-of-my-butt example: you have an old entry in your BIOS that points to an old partition for some reason, and your BIOS boot order is set to that stale entry
          I am assuming you see this error early on, and do not get to grub.
          Actually, it has displayed several screenfulls of boot log by then. In fact, syslog shows lines like this:

          Oct 14 15:14:03 jon-desktop 40grub2: debug: parsing: menuentry 'KDE neon 6.2 GNU/Linux, with Linux 6.8.0-45-generic (recovery mode) (on /dev/sdb2)' --class gnu-linux --class gnu --class os $menuentry_
          id_option 'osprober-gnulinux-/boot/vmlinuz-6.8.0-45-generic-root=UUID=668e8ec0-4a8c-4fec-87dd-4fb5468ab9ec ro recovery nomodeset dis_ucode_ldr-668e8ec0-4a8c-4fec-87dd-4fb5468ab9ec' {
          Oct 14 15:14:03 jon-desktop 40grub2: debug: parsing: linux /boot/vmlinuz-6.8.0-45-generic root=UUID=668e8ec0-4a8c-4fec-87dd-4fb5468ab9ec ro recovery nomodeset dis_ucode_ldr
          Whatever does that mean? What is this menuentry jazz? Looks like the grub cfg file is corrupted. Where do I find that and fix it?

          If you moved or resized partitions since installing (not likely) that would obviously change that partition's UUID
          Really? That surprises me. That would be a vote for using label rather than uuid or device name in fstab.
          Last edited by joneall; Oct 14, 2024, 09:11 AM.
          'I must have a prodigious quantity of mind; it takes me as much as a week sometimes to make it up.' Mark Twain

          Comment


            #6
            Originally posted by joneall View Post
            Really? That surprises me. That would be a vote for using label rather than uuid or device name in fstab.
            it doesn't normally, but it *can*, just more stuff I was throwing at the wall.

            Comment

            Working...
            X