On Mon, 2024-07-29 at 08:34 -0400, Go Canes wrote:
> Note the quotes have been re-ordered for clarity
>
> On Mon, Jul 29, 2024 at 6:32 AM Patrick O'Callaghan
> wrote:
>
> > # efibootmgr
> > BootCurrent: 0001
> [...]
> > Boot0001* Fedora HD(1,GPT,8a303a03-0b91-453a-8555-
> > f9627c261f65,0
Note the quotes have been re-ordered for clarity
On Mon, Jul 29, 2024 at 6:32 AM Patrick O'Callaghan
wrote:
> # efibootmgr
> BootCurrent: 0001
[...]
> Boot0001* Fedora
> HD(1,GPT,8a303a03-0b91-453a-8555-f9627c261f65,0x800,0x12c000)/\EFI\fedora\shimx64.efi424f
> # blkid
[...]
> /dev/
On Mon, 2024-07-29 at 09:21 +1000, Michael D. Setzer II via users
wrote:
> 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.
>
I didn't clone it in raw mode, and t
On Fri, 2024-07-26 at 23:02 +0100, Patrick O'Callaghan wrote:
> I've cloned my existing SSD onto a new NVMe drive, copying EFI
> (vfat),
> /boot (ext4) and root+/home (BTRFS with /home subvolume) partitions
> and
> editing /etc/fstab appropriately.
>
> However I have a couple of questions:
>
> 1)
On 28 Jul 2024 at 21:57, Samuel Sieb wrote:
Date sent: Sun, 28 Jul 2024 21:57:04 -0700
Subject:Re: NVMe questions
To: Community support for Fedora users
From: Samuel Sieb
Send reply to: Community support for Fedora
On 7/28/24 7:00 PM, Michael D. Setzer II wrote:
On 28 Jul 2024 at 17:54, Samuel Sieb wrote:
Date sent: Sun, 28 Jul 2024 17:54:13 -0700
Subject:Re: NVMe questions
To: users@lists.fedoraproject.org
From: Samuel Sieb
Send reply to
On 28 Jul 2024 at 17:54, Samuel Sieb wrote:
Date sent: Sun, 28 Jul 2024 17:54:13 -0700
Subject:Re: NVMe questions
To: users@lists.fedoraproject.org
From: Samuel Sieb
Send reply to: Community support for Fedora users
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
Date sent: Sun, 28 Jul 2024 18:19:38 -0400
Subject:Re: NVMe questions
To: Community support for Fedora users
On 28 Jul 2024 at 18:19, Go Canes wrote:
From: Go Canes
Date sent: Sun, 28 Jul 2024 18:19:38 -0400
Subject:Re: NVMe questions
To: Community support for Fedora users
Send reply to: Community support for Fedora users
On Sun, Jul 28, 2024 at 5:42 PM Patrick O'Callaghan
wrote:
> I tried disabling the SSD (in the bootable drives list). It made no
> difference.
Just to be clear - did you disable the drive or just remove it from
the bootable list? What we want to do here is prevent the BIOS from
reading from the
On Sat, 2024-07-27 at 20:04 -0400, Go Canes wrote:
> On Sat, Jul 27, 2024 at 4:36 PM Patrick O'Callaghan
> wrote:
> > However none of the UUIDs seen by efibootmgr correspond to anything
> > on
> > any of the drives.
>
> Re-read my reply. Both of the efibootmgr variables *do* correspond
> to
> ex
On Sat, 2024-07-27 at 19:40 -0600, Gabriel Ramirez wrote:
> If you give the FAT file system a volume name (i.e. file system label),
> be sure to name it something other than EFI. That can trigger a bug in
> some firmwares (due to the volume name matching the EFI directory name)
> that will cause
On 7/27/24 03:35, Patrick O'Callaghan wrote:
Model: WD_BLACK SN770 2TB (nvme)
Disk /dev/nvme0n1: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End SizeFile system NameFlags
1 1049kB 269MB 268MB fat32EFI msft
On Sat, Jul 27, 2024 at 4:36 PM Patrick O'Callaghan
wrote:
> However none of the UUIDs seen by efibootmgr correspond to anything on
> any of the drives.
Re-read my reply. Both of the efibootmgr variables *do* correspond to
existing UUIDs.
> > Can you disable the SSD in "BIOS"?
> Yes, but the NV
On Sat, 2024-07-27 at 15:47 -0400, Go Canes wrote:
> What I'm not sure of is the "1" in "HD(1,GPT,[...]" - I am thinking
> it
> refers to the first "hard disk", which if I am right, means at least
> one of them is pointing to the correct uuid, but on the wrong disk.
>
However none of the UUIDs se
I think quoting levels are getting messed up
> $ efibootmgr
> BootCurrent: 0001
> Timeout: 1 seconds
> BootOrder: 0001,0002
> Boot0001* Fedora
> HD(1,GPT,8a303a03-0b91-453a-8555-f9627c261f65,0x800,0x12c000)/\EFI\fedora\shimx64.efi424f
> Boot0002* Fedora
> HD(1,GPT,e7207d2d-
On Sat, 2024-07-27 at 15:17 +0200, Lukas Middendorf wrote:
> On 27/07/2024 14:56, Patrick O'Callaghan wrote:
> > On Fri, 2024-07-26 at 19:00 -0400, Go Canes wrote:
> > > - EFI needs a variable that points to the desired disk and the
> > > desired
> > > partition on that disk
> > > - the UUID from t
On Sat, Jul 27, 2024 at 8:57 AM Patrick O'Callaghan
wrote:
[...]
> None of those numbers correspond to any of my UUIDs:
[followed by lsblk -fs]
Use "blkid" - it will show the UUID of the device and the PARTUUID of
the partition for all your disks.
--
_
On 27/07/2024 14:56, Patrick O'Callaghan wrote:
On Fri, 2024-07-26 at 19:00 -0400, Go Canes wrote:
- EFI needs a variable that points to the desired disk and the
desired
partition on that disk
- the UUID from the EFI variable needs to match the PARTUUID for the
EFI partition on the desired disk
On Fri, 2024-07-26 at 19:00 -0400, Go Canes wrote:
> - EFI needs a variable that points to the desired disk and the
> desired
> partition on that disk
> - the UUID from the EFI variable needs to match the PARTUUID for the
> EFI partition on the desired disk
> - the directory from the EFI var shou
On Sat, 2024-07-27 at 11:59 +0200, Lukas Middendorf wrote:
> On 27/07/2024 11:35, Patrick O'Callaghan wrote:
> > Model: WD_BLACK SN770 2TB (nvme)
> > Disk /dev/nvme0n1: 2000GB
> > Sector size (logical/physical): 512B/512B
> > Partition Table: gpt
> > Disk Flags:
> >
> > Number Start End Siz
On 27/07/2024 11:35, Patrick O'Callaghan wrote:
Model: WD_BLACK SN770 2TB (nvme)
Disk /dev/nvme0n1: 2000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End SizeFile system NameFlags
1 1049kB 269MB 268MB fat32EFI m
On Fri, 2024-07-26 at 18:33 -0400, Felix Miata wrote:
> Patrick O'Callaghan composed on 2024-07-26 23:02 (UTC+0100):
>
> > I ran dracut with the
> > UUID of the appropriate root NVMe partition but it made no
> > difference.
> > What am I missing here?
>
> What did you do to ensure NVME support is
On Fri, 2024-07-26 at 17:32 -0500, Richard Shaw wrote:
> Try posting the output of "sudo parted --list", for my nvme boot
> drive it
> looks like this:
>
> Model: Samsung SSD 970 EVO Plus 500GB (nvme)
> Disk /dev/nvme1n1: 500GB
> Sector size (logical/physical): 512B/512B
> Partition Table: gpt
> D
On Fri, 2024-07-26 at 15:17 -0700, Mike Wright wrote:
> On 7/26/24 15:02, Patrick O'Callaghan wrote:
> > I've cloned my existing SSD onto a new NVMe drive, copying EFI
> > (vfat),
> > /boot (ext4) and root+/home (BTRFS with /home subvolume) partitions
> > and
> > editing /etc/fstab appropriately.
>
On Fri, Jul 26, 2024 at 6:03 PM Patrick O'Callaghan
wrote:
>
> I've cloned my existing SSD onto a new NVMe drive, copying EFI (vfat),
> /boot (ext4) and root+/home (BTRFS with /home subvolume) partitions and
> editing /etc/fstab appropriately.
>
> However I have a couple of questions:
>
> 1) I'm p
Try posting the output of "sudo parted --list", for my nvme boot drive it
looks like this:
Model: Samsung SSD 970 EVO Plus 500GB (nvme)
Disk /dev/nvme1n1: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End SizeFile system Name
Patrick O'Callaghan composed on 2024-07-26 23:02 (UTC+0100):
> I ran dracut with the
> UUID of the appropriate root NVMe partition but it made no difference.
> What am I missing here?
What did you do to ensure NVME support is included in the new initramfs?
--
Evolution as taught in public school
Once upon a time, Mike Wright said:
> Which tool did you use to partition the drive? For UEFI I believe
> you have to use gparted or gfdisk.
That's not true, I think most if not all of the commonly-used tools can
partition a drive compatible with UEFI. The partition table needs to be
GPT, and s
On 7/26/24 15:02, Patrick O'Callaghan wrote:
I've cloned my existing SSD onto a new NVMe drive, copying EFI (vfat),
/boot (ext4) and root+/home (BTRFS with /home subvolume) partitions and
editing /etc/fstab appropriately.
However I have a couple of questions:
1) I'm puzzled that the NVMe drive
I've cloned my existing SSD onto a new NVMe drive, copying EFI (vfat),
/boot (ext4) and root+/home (BTRFS with /home subvolume) partitions and
editing /etc/fstab appropriately.
However I have a couple of questions:
1) I'm puzzled that the NVMe drive (a 2TB WD Black) doesn't appear as
bootable in
31 matches
Mail list logo
