Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 25

Thread: new nvme and sata will not boot

  1. #11
    Join Date
    Jan 2011
    Location
    Retired in Bournemouth UK
    Beans
    385
    Distro
    Ubuntu Studio Development Release

    Re: new nvme and sata will not boot

    Quote Originally Posted by oldfred View Post
    To get around boot issue, boot live installer. Then post this in code tags, do not copy to another site.

    lsblk -o name,mountpoint,label,size,fstype,uuid,partuuid | egrep -v "^loop"

    How to use Code tags, # in advanced editor
    http://ubuntuforums.org/showthread.p...8#post12776168
    http://ubuntuforums.org/showthread.p...8#post12776168
    Oldfred-thanks for your reply, take me a while to get the info you want-now dinner's ready, the lovely Jane is not impressed.....
    Asus Z270i7 16gb rm 8tb GT1660 Haupp Quad tunr KDE Neon 20.04 Focal/Win 10 Be/FE mythtv 0.32Homerun dual netwk tunr 55¨ Smsng ES8000 Lap Smsng NP R580 i5 nvidia linux Ultimate/Win 10

  2. #12
    Join Date
    Jan 2011
    Location
    Retired in Bournemouth UK
    Beans
    385
    Distro
    Ubuntu Studio Development Release

    Re: new nvme and sata will not boot

    Quote Originally Posted by oldfred View Post
    To get around boot issue, boot live installer. Then post this in code tags, do not copy to another site.

    lsblk -o name,mountpoint,label,size,fstype,uuid,partuuid | egrep -v "^loop"

    How to use Code tags, # in advanced editor
    http://ubuntuforums.org/showthread.p...8#post12776168
    http://ubuntuforums.org/showthread.p...8#post12776168
    Oldfred-thanks for your help. sdg is the SDD, the sabrent nvme 2tb is not there for some reason???

    Code:
    kubuntu@kubuntu:~$ lsblk -o name,mountpoint,label,size,fstype,uuid,partuuid | egrep -v "^loop"
    NAME        MOUNTPOINT LABEL                 SIZE FSTYPE   UUID                                 PARTUUID
    sda                                          3.6T                                               
    └─sda1                 data                  3.6T ext4     b0171cc5-2137-4789-9359-ee7315ade770 26d3afe3-d442-4c36-867b-7e48cb5671fe
    sdb                                          4.5T                                               
    └─sdb1                 tv                    4.5T ntfs     6E66CE4866CE112F                     d9118715-a532-4b4f-8ba0-01fe09c65398
    sdg                                        238.5G                                               
    ├─sdg1                 SYSTEM                716M vfat     0FE6-9C83                            aee32a46-0ba7-44bf-9015-1c8a0ab01ee5
    ├─sdg2                                      80.9M vfat     D224-4637                            911ec5cd-151e-45b3-8668-49227963ae95
    ├─sdg3                 Windows              92.9G ntfs     94EA89EAEA89C946                     a1207cf5-2cb3-42cc-8d07-c29839f753d9
    ├─sdg4                                       540M ntfs     AE3A159F3A15659D                     1ce72b0e-9da1-4bf7-966e-ef36f3419eb4
    ├─sdg5                                      48.8G ext4     213fb185-2dc7-4eb2-ab58-fc2c36924d6f ebbbae4e-77b2-474d-9f2e-28f2869dfe2c
    ├─sdg6                                        84G ext4     7fff3192-2e26-4add-81d2-0ba7a8ee7601 606c2405-5ba0-42fa-bc4a-6b8cb77e8805
    └─sdg7                 Windows RE tools      5.9G ntfs     14448A2C448A10A2                     a15361d7-819e-4485-8f09-d9b978980046
    sdh                                         14.3G                                               
    ├─sdh1                 usbdata               1.1G ntfs     03479FBC56EAF4C5                     4b74152a-d56f-4c74-83a6-5615a32ae027
    ├─sdh2                                       977K                                               749d89df-8529-4d8b-89a0-0dfe16aeaf78
    ├─sdh3                 usbboot             244.1M vfat     4C2B-A37F                            273e49c9-e85a-43f4-a86e-47af010d77fb
    ├─sdh4      /cdrom     Kubuntu 21.04 amd64   2.8G iso9660  2021-04-20-11-02-45-00               0205fe1c-69b4-4964-8817-9743d5498080
    └─sdh5                 casper-rw            10.2G ext4     8f72e95b-5f21-447e-8565-7f867cac7ca8 65897d1f-8af5-4914-911f-93d1cae4dea4
    nvme0n1                                    238.5G                                               
    ├─nvme0n1p1            SYSTEM                716M vfat     CFCD-57FD                            aee32a46-0ba7-44bf-9015-1c8a0ab01ee5
    ├─nvme0n1p2                                 80.9M vfat     D224-4637                            911ec5cd-151e-45b3-8668-49227963ae95
    ├─nvme0n1p3            Windows              92.9G ntfs     94EA89EAEA89C946                     a1207cf5-2cb3-42cc-8d07-c29839f753d9
    ├─nvme0n1p4                                  540M ntfs     AE3A159F3A15659D                     1ce72b0e-9da1-4bf7-966e-ef36f3419eb4
    ├─nvme0n1p5                                 48.8G ext4     213fb185-2dc7-4eb2-ab58-fc2c36924d6f ebbbae4e-77b2-474d-9f2e-28f2869dfe2c
    ├─nvme0n1p6                                   84G ext4     7fff3192-2e26-4add-81d2-0ba7a8ee7601 606c2405-5ba0-42fa-bc4a-6b8cb77e8805
    └─nvme0n1p7            Windows RE tools      5.9G ntfs     14448A2C448A10A2                     a15361d7-819e-4485-8f09-d9b978980046
    kubuntu@kubuntu:~$
    Asus Z270i7 16gb rm 8tb GT1660 Haupp Quad tunr KDE Neon 20.04 Focal/Win 10 Be/FE mythtv 0.32Homerun dual netwk tunr 55¨ Smsng ES8000 Lap Smsng NP R580 i5 nvidia linux Ultimate/Win 10

  3. #13
    Join Date
    Apr 2008
    Location
    Southern California, USA
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: new nvme and sata will not boot

    Quote Originally Posted by vidtek View Post
    VMC I can't see what the set command says it scrolls to bottom too quickly
    type "pager=1", then you will get a page at a time.

  4. #14
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: new nvme and sata will not boot

    You show all partUUID or guid as duplicate between sdg & nvme0n1.
    And most of the UUIDs are the same.

    You cannot have any duplicates.
    UEFI used guid/partuuid to know which ESP to boot from. You see it in efibootmgr -v.
    And other partitions are mounted normally by UUID.
    Do not know how Windows works, but Windows will not boot from an external drive anyway, so does not matter to change its UUID, in case you want to mount it. You do have to make sure fast start up is off and Windows will keep turning it on with updates.

    I normally suggest a full install rather than a clone & then restore from your normal backup. That way, you know you have a good backup procedure since you still have older install to find any missing info.

    New install can take less time than trying to resolve these kinds of issues.
    I have new install down to about 10 minutes from previously downloaded ISO, booted into RAM using grub2's loopmount. About 90% of configuration is by my install scripts which do take a bit. Or in about an hour I have a fully working an mostly configured system.
    UEFI boot install & repair info - Regularly Updated :
    https://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

  5. #15
    Join Date
    Jan 2011
    Location
    Retired in Bournemouth UK
    Beans
    385
    Distro
    Ubuntu Studio Development Release

    Re: new nvme and sata will not boot

    Quote Originally Posted by oldfred View Post
    You show all partUUID or guid as duplicate between sdg & nvme0n1.
    And most of the UUIDs are the same.

    You cannot have any duplicates.
    UEFI used guid/partuuid to know which ESP to boot from. You see it in efibootmgr -v.
    And other partitions are mounted normally by UUID.
    Do not know how Windows works, but Windows will not boot from an external drive anyway, so does not matter to change its UUID, in case you want to mount it. You do have to make sure fast start up is off and Windows will keep turning it on with updates.

    I normally suggest a full install rather than a clone & then restore from your normal backup. That way, you know you have a good backup procedure since you still have older install to find any missing info.

    New install can take less time than trying to resolve these kinds of issues.
    I have new install down to about 10 minutes from previously downloaded ISO, booted into RAM using grub2's loopmount. About 90% of configuration is by my install scripts which do take a bit. Or in about an hour I have a fully working an mostly configured system.
    Oldfred- Thanks for your time and effort. I think I have not been clear in my intended use, I don't want to run both systems simultaneously. What I do want is to be able to choose whether to boot from the NVME or SDD drives at boot time. I can easily remove the SSD as it's in a quick caddy to boot from the NVME, but there seems no way to disable the NVME drive when I need to boot from the SSD.

    The reason all the UUID's of the partitions are identical is because I cloned the NVME drive from the SSD originally with clonezilla (only changing the main UUID later).

    If there is no way to readily disable the NVME drive at boot time I will just have to work round it. I suspect newer motherboards will have better options for handling the way M2 drives work and will have the capability I seek.

    The other alternative would be a PCI caddy for the NVME drive I suppose......running out of PCI lanes.

    I have my installs down to about 15mins too, but then there is mythtv install-the rest of the day for that!

    Cheers Tony.
    Asus Z270i7 16gb rm 8tb GT1660 Haupp Quad tunr KDE Neon 20.04 Focal/Win 10 Be/FE mythtv 0.32Homerun dual netwk tunr 55¨ Smsng ES8000 Lap Smsng NP R580 i5 nvidia linux Ultimate/Win 10

  6. #16
    Join Date
    Jan 2011
    Location
    Retired in Bournemouth UK
    Beans
    385
    Distro
    Ubuntu Studio Development Release

    Re: new nvme and sata will not boot

    Quote Originally Posted by VMC View Post
    type "pager=1", then you will get a page at a time.
    VMC--Here are the results: grub_set1.jpggrub_set2.jpg

    Cheers Tony
    Asus Z270i7 16gb rm 8tb GT1660 Haupp Quad tunr KDE Neon 20.04 Focal/Win 10 Be/FE mythtv 0.32Homerun dual netwk tunr 55¨ Smsng ES8000 Lap Smsng NP R580 i5 nvidia linux Ultimate/Win 10

  7. #17
    Join Date
    Jan 2011
    Location
    Retired in Bournemouth UK
    Beans
    385
    Distro
    Ubuntu Studio Development Release

    Re: new nvme and sata will not boot

    Oldfred- Incidentally I have managed to get windows 10 to boot from my turbo leopard dual cloning external USB3 dock from my SSD drive. That surely can be classed as an external drive?turbo_leopard.jpg

    Cheers Tony.
    Asus Z270i7 16gb rm 8tb GT1660 Haupp Quad tunr KDE Neon 20.04 Focal/Win 10 Be/FE mythtv 0.32Homerun dual netwk tunr 55¨ Smsng ES8000 Lap Smsng NP R580 i5 nvidia linux Ultimate/Win 10

  8. #18
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: new nvme and sata will not boot

    I know if directly to USB port, Windows knows.
    Perhaps your dock is not then seen as a USB port?

    Some UEFI have settings for drives. Its the same place as AHCI, RAID/Intel RST. It may have a "disabled" setting.
    Also if drive is removed, it may forget UEFI boot entry or change entry to some sort of default. Often then have to use efibootmgr to recreate entry or reinstall grub (which uses efibootmgr) to add/update entry. UEFI often auto finds Windows, but not other operating systems.
    Not sure with your ESP & duplicate UUIDs & GUIDs if it will work or you still need some changes.

    UEFI boots using GUID/partUUID to know which ESP. In ESP is a three line grub.cfg which has UUID of the install with the full grub.cfg for booting. It uses configfile to load another grub.cfg.
    UEFI boot install & repair info - Regularly Updated :
    https://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

  9. #19
    Join Date
    Jan 2011
    Location
    Retired in Bournemouth UK
    Beans
    385
    Distro
    Ubuntu Studio Development Release

    Re: new nvme and sata will not boot

    Quote Originally Posted by oldfred View Post
    I know if directly to USB port, Windows knows.
    Perhaps your dock is not then seen as a USB port?

    Some UEFI have settings for drives. Its the same place as AHCI, RAID/Intel RST. It may have a "disabled" setting.
    Also if drive is removed, it may forget UEFI boot entry or change entry to some sort of default. Often then have to use efibootmgr to recreate entry or reinstall grub (which uses efibootmgr) to add/update entry. UEFI often auto finds Windows, but not other operating systems.
    Not sure with your ESP & duplicate UUIDs & GUIDs if it will work or you still need some changes.

    UEFI boots using GUID/partUUID to know which ESP. In ESP is a three line grub.cfg which has UUID of the install with the full grub.cfg for booting. It uses configfile to load another grub.cfg.
    Sounds probable that is the main cause of not booting and going straight to the default (really helpful) grub command prompt.

    I do not have to re-install grub after this though-just removing the sata SDD lets mt boot normally from the nvme drive.

    OK so let me see if I follow you properly.

    You imply that if I could make changes to the grub.cfg file to point the EFI system to the correct system it may work?

    all I get now from the (really helpful) grub command prompt is you need to load a kernel first (paraphrasing).

    Right I'll give that a go and let you know how I get on.

    By the way, I'm not an orphan, there are many many posts on the various forums bemoaning the fact that people cannot disable their M2 nvme drives easily.

    Thanks again for your trouble oldfred!
    Asus Z270i7 16gb rm 8tb GT1660 Haupp Quad tunr KDE Neon 20.04 Focal/Win 10 Be/FE mythtv 0.32Homerun dual netwk tunr 55¨ Smsng ES8000 Lap Smsng NP R580 i5 nvidia linux Ultimate/Win 10

  10. #20
    Join Date
    Jan 2011
    Location
    Retired in Bournemouth UK
    Beans
    385
    Distro
    Ubuntu Studio Development Release

    Re: new nvme and sata will not boot

    I tried editing the grub.cfg file. (In the SSD drive only) I changed the partition UUID for a new random one using the tune2fs command thus:
    Code:
    tune2fs -U random /dev/sdg5
    The blkid command now shows a different UUID :
    Code:
    root@linuxmint:/home/tony# blkid
    /dev/nvme0n1p1: LABEL="SYSTEM" UUID="CFCD-57FD" TYPE="vfat" PARTUUID="aee32a46-0ba7-44bf-9015-1c8a0ab01ee5"
    /dev/nvme0n1p2: SEC_TYPE="msdos" UUID="D224-4637" TYPE="vfat" PARTUUID="911ec5cd-151e-45b3-8668-49227963ae95"
    /dev/nvme0n1p3: LABEL="Windows" UUID="94EA89EAEA89C946" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="a1207cf5-2cb3-42cc-8d07-c29839f753d9"
    /dev/nvme0n1p4: UUID="AE3A159F3A15659D" TYPE="ntfs" PARTUUID="1ce72b0e-9da1-4bf7-966e-ef36f3419eb4"
    /dev/nvme0n1p5: UUID="213fb185-2dc7-4eb2-ab58-fc2c36924d6f" TYPE="ext4" PARTLABEL="kubuntu20" PARTUUID="ebbbae4e-77b2-474d-9f2e-28f2869dfe2c"
    /dev/nvme0n1p6: UUID="7fff3192-2e26-4add-81d2-0ba7a8ee7601" TYPE="ext4" PARTUUID="606c2405-5ba0-42fa-bc4a-6b8cb77e8805"
    /dev/nvme0n1p7: LABEL="Windows RE tools" UUID="14448A2C448A10A2" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="a15361d7-819e-4485-8f09-d9b978980046"
    /dev/sdb1: LABEL="tv" UUID="6E66CE4866CE112F" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="d9118715-a532-4b4f-8ba0-01fe09c65398"
    /dev/sda1: LABEL="data" UUID="b0171cc5-2137-4789-9359-ee7315ade770" TYPE="ext4" PARTUUID="26d3afe3-d442-4c36-867b-7e48cb5671fe"
    /dev/loop0: TYPE="squashfs"
    /dev/loop1: TYPE="squashfs"
    /dev/loop2: TYPE="squashfs"
    /dev/loop3: TYPE="squashfs"
    /dev/loop4: TYPE="squashfs"
    /dev/loop5: TYPE="squashfs"
    /dev/loop6: TYPE="squashfs"
    /dev/loop7: TYPE="squashfs"
    /dev/loop8: TYPE="squashfs"
    /dev/loop9: TYPE="squashfs"
    /dev/loop10: TYPE="squashfs"
    /dev/loop11: TYPE="squashfs"
    /dev/sdg1: LABEL="SYSTEM" UUID="0FE6-9C83" TYPE="vfat" PARTUUID="aee32a46-0ba7-44bf-9015-1c8a0ab01ee5"
    /dev/sdg2: SEC_TYPE="msdos" UUID="D224-4637" TYPE="vfat" PARTUUID="911ec5cd-151e-45b3-8668-49227963ae95"
    /dev/sdg3: LABEL="Windows" UUID="94EA89EAEA89C946" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="a1207cf5-2cb3-42cc-8d07-c29839f753d9"
    /dev/sdg4: UUID="AE3A159F3A15659D" TYPE="ntfs" PARTUUID="1ce72b0e-9da1-4bf7-966e-ef36f3419eb4"
    /dev/sdg5: UUID="70afb10c-38bf-4edd-a070-24b1b3ddb1b5" TYPE="ext4" PARTLABEL="kubuntu20" PARTUUID="ebbbae4e-77b2-474d-9f2e-28f2869dfe2c"
    /dev/sdg6: UUID="7fff3192-2e26-4add-81d2-0ba7a8ee7601" TYPE="ext4" PARTUUID="606c2405-5ba0-42fa-bc4a-6b8cb77e8805"
    /dev/sdg7: LABEL="Windows RE tools" UUID="14448A2C448A10A2" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="a15361d7-819e-4485-8f09-d9b978980046"
    Then I edited the grub.cfg to reflect the changes, (with 67 results for the search and replace of the partition UUID).

    In the bios I selected to boot from the ssd drive

    No change, the really helpful grub screen appears as usual.

    Can you tell me why there seems to be 2 UUID's for the partition? as thus:
    Code:
    /dev/sdg5: UUID="70afb10c-38bf-4edd-a070-24b1b3ddb1b5" TYPE="ext4" PARTLABEL="kubuntu20" PARTUUID="ebbbae4e-77b2-474d-9f2e-28f2869dfe2c"
    The tune2fs command only changed the first bit........

    why are there two for each one? Why on earth do they have to make things so bloody complicated? GRRRRRRR!!!
    Last edited by vidtek; May 20th, 2021 at 10:52 AM. Reason: typo
    Asus Z270i7 16gb rm 8tb GT1660 Haupp Quad tunr KDE Neon 20.04 Focal/Win 10 Be/FE mythtv 0.32Homerun dual netwk tunr 55¨ Smsng ES8000 Lap Smsng NP R580 i5 nvidia linux Ultimate/Win 10

Page 2 of 3 FirstFirst 123 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •