search

azuer88 / grub-mkconfig_lib-patch

a simple patch to make update-grub in ubuntu use partition labels instead of UUID
GNU Lesser General Public License v3.0
6 stars 2 forks source link

No such device ... #1

Open minzak opened 5 years ago

minzak commented 5 years ago

If drive has bad label - it is no boot.

/dev/nvme0n1: PTUUID="37ffe190" PTTYPE="dos"
/dev/nvme0n1p1: LABEL="nvme" UUID="ef6cb666-a5da-403b-861f-6764cd63e6d8" TYPE="ext4" PARTUUID="37ffe190-01"
/dev/sda1: LABEL="deb" UUID="2b02c1c8-bb51-4a01-bd33-1bf5488d96d4" TYPE="ext4" PARTUUID="c0b59f34-01"
/dev/sda2: LABEL="WIN" UUID="37A1257E0D53D5D8" TYPE="ntfs" PARTUUID="c0b59f34-02"
/dev/sda3: LABEL="DATA" UUID="103897063896E9CC" TYPE="ntfs" PARTUUID="c0b59f34-03"
/dev/sdb1: LABEL="data1" UUID="c41c8b64-9136-4bc6-8d82-d3df91625739" TYPE="ext4" PARTLABEL="data1" PARTUUID="e85ba40e-14d4-4996-b828-37df3d72a01b"
/dev/sdc1: LABEL="data2" UUID="aef00e48-6366-4032-803d-1187e38ecdfb" TYPE="ext4" PARTLABEL="data2" PARTUUID="fdf5d568-6e21-484b-8bd1-6dd6d001d4af"
/dev/sdd1: LABEL="data3" UUID="0a5c4324-441d-4129-9f1a-f6edb4edd532" TYPE="ext4" PARTLABEL="data3" PARTUUID="399e8d9a-66e1-44ac-8067-2c801a7fc2da"

I think it because UUID is not equal to PARTUUID.

How about made with DEVICE, not LABEL? Here we can see all targets - https://www.gnu.org/software/grub/manual/grub/html_node/Invoking-grub_002dprobe.html

and use /dev/sda1 - is the best way.

for example made worked like this: grub-probe --target=drive --device /dev/sda1

azuer88 commented 5 years ago

The original mkconfig uses DEVICE. I needed to use LABEL, because I connect different devices, but using same label.

On Mon, May 13, 2019 at 4:24 AM Olexandr Minzak notifications@github.com wrote:

If drive has bad label - it is no boot.

How about made with DEVICE, not LABEL? Here we can see all targets - https://www.gnu.org/software/grub/manual/grub/html_node/Invoking-grub_002dprobe.html

and use /dev/sda1 - is the best way.

for example made worked like this: grub-probe --target=drive --device /dev/sda1

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/azuer88/grub-mkconfig_lib-patch/issues/1, or mute the thread https://github.com/notifications/unsubscribe-auth/AAEXAE6S6YW7OZUTZIDURPTPVB4IRANCNFSM4HMLFF7Q .

--

The most exciting phrase to hear in science - the one that heralds new discoveries - is not "Eureka!" but "That's funny...".

I f you give someone a program, you will frustrate them for a day; if you teach them how to program, you will frustrate them for a lifetime. - Anonymous

If writing good code requires very little comments, then writing really excellent code requires no comments at all!- Ken Thompson

Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. - Rick Cook

minzak commented 5 years ago

The original mkconfig uses DEVICE.

No, by default use UUID, and i got error during boot "not found device <UUID)> Press any...."

And i even use in grub this option "GRUB_DISABLE_LINUX_UUID=true" But in grub.cfg i see like this:

        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root  2080bb0b-8161-48b3-ae64-a66338daa0ec
        else

Just fully not understand how to correctly use not UUID, Because in my case even LABEL not works! I have message "not found device <LABEL)> Press any...." I guess with DEVICE like /dev/... i eliminate my issues.

azuer88 commented 5 years ago

My bad. You are correct.

Look at the output of sudo blkid and use the LABEL= value.

On Tue, May 14, 2019 at 4:59 PM Olexandr Minzak notifications@github.com wrote:

The original mkconfig uses DEVICE.

No, by default use UUID, and i got error during boot "not found device <UUID)> Press any...."

And i even use in grub this option "GRUB_DISABLE_LINUX_UUID=true" But in grub.cfg i see like this:

  if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root  2080bb0b-8161-48b3-ae64-a66338daa0ec
  else

Just fully not understand how to correctly use not UUID, Because in my case even LABEL not works! I have message "not found device <LABEL)> Press any...." I guess with DEVICE like /dev/... i eliminate my issues.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/azuer88/grub-mkconfig_lib-patch/issues/1?email_source=notifications&email_token=AAEXAE3PVORI7FXZ6J7EJBLPVJ5QLA5CNFSM4HMLFF72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVK2F4Y#issuecomment-492151539, or mute the thread https://github.com/notifications/unsubscribe-auth/AAEXAEY5UD45UYM73IEQMNTPVJ5QLANCNFSM4HMLFF7Q .

--

The most exciting phrase to hear in science - the one that heralds new discoveries - is not "Eureka!" but "That's funny...".

I f you give someone a program, you will frustrate them for a day; if you teach them how to program, you will frustrate them for a lifetime. - Anonymous

If writing good code requires very little comments, then writing really excellent code requires no comments at all!- Ken Thompson

Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. - Rick Cook