I’m on debian 11, this error doesn’t show up every time, but once it appear I need more that one reboot and it will fix automatically without doing nothing, don’t know the reason why (just read that can be kernel dependent). What I want to avoid is that maybe it’s just a warning of somethink that will cause a pc break in future (maybe hardware is starting working bad?) Do you have any sugggestion? Thanks

  • dafunkkk@lemmy.worldOP
    link
    fedilink
    arrow-up
    2
    ·
    11 months ago

    so can be bios dependent?..it’s possible to change from /dev/sdn to UUIDs…how? Thanks

    • vcmj@programming.dev
      link
      fedilink
      arrow-up
      0
      ·
      11 months ago

      Yes if you have multiple drives some buggy BIOS may not enumerate them in the same order every time. Most modern distros do UUIDs by default but when manually setting up a bootloader it is easy to succumb to such temptations to use the much simpler device paths as the UUIDs are a pain. If you’re not sure how to change the kernel parameters most likely you’re good on that front actually, its in your grub config as others have mentioned. I’ll leave this comment around in case some poor soul who did it manually comes across the thread.

    • vcmj@programming.dev
      link
      fedilink
      arrow-up
      0
      ·
      11 months ago

      Basically just look for things like root=/dev/sda2 in the kernel command line. You can get it at runtime by running “cat /proc/cmdline” having /dev/sda etc in your fstab might also be a problem

      • vcmj@programming.dev
        link
        fedilink
        arrow-up
        0
        ·
        11 months ago

        You can change those to /dev/disk/by-uuid/XYZ (“ls -an” that directory to see the symlinks to your current drives)