On 7/28/24 4:21 PM, Michael D. Setzer II via users wrote:
On 28 Jul 2024 at 18:19, Go Canes wrote:
From: Go Canes <letsgonhlcanes0@xxxxxxxxx>
Date sent: Sun, 28 Jul 2024 18:19:38 -0400
Subject: Re: NVMe questions
To: Community support for Fedora users
<users@xxxxxxxxxxxxxxxxxxxxxxx>
Send reply to: Community support for Fedora users
<users@xxxxxxxxxxxxxxxxxxxxxxx>
On Sun, Jul 28, 2024 at 5:42 PM Patrick O'Callaghan
<pocallaghan@xxxxxxxxx> wrote:
I tried disabling the SSD (in the bootable drives list). It made no
difference.
Check the blkids on all devices.
blkid
If you clone a disk in a raw mode, the blkid's are the same on both
devices, and since the boot process looks for the blkid to load, it
would be using the first device it sees.
In past, it use the /dev/sdx method so duplicate blkids would be ok,
but now it can be an issue. If you disconnect the SSD drive it
would probable work.
Option would be to either remove the SSD drive, or change the
blkids on it to be different than the nvme drive.
Would be interesting to see what blkid reports, but pretty sure it
would show same ids between SSD and nvme drives.
I've been maintainer of G4L disk imaging project since 2004, so
have seen this issue with cloning disks.
You're at the wrong level. This is before Fedora is booted, so all of
that is not relevant. He's trying to get the BIOS to boot from it.
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
