On 7/15/25 1:22 AM, Samuel Sieb wrote:
On 7/13/25 1:31 PM, Robert McBroom via users wrote:
During boot I get the message
block nvme0n1: No UUID available providing old NGUID
When I try to mount the lvm I get the message
~# mount /dev/mapper/fedora /sd1
mount: /sd1: fsconfig system call faile
On 7/16/25 11:05 AM, Barry Scott wrote:
On 15 Jul 2025, at 05:51, Robert McBroom via users
wrote:
├─nvme0n1p5
│ LVM2_mem LVM2 001 v1gXoi-sKLO-fS0t-oKxo-en1J-7vOu-BH8Hal
└─nvme0n1p6
LVM2_mem LVM2 001 lQ45eA-ARYv-JiVX-JRjR-eyHl-NCXO-vkB2m0
Why are there two LVM2 partitions?
That is not
> On 15 Jul 2025, at 05:51, Robert McBroom via users
> wrote:
>
> ├─nvme0n1p5
> │ LVM2_mem LVM2 001
> v1gXoi-sKLO-fS0t-oKxo-en1J-7vOu-BH8Hal
> └─nvme0n1p6
> LVM2_mem LVM2 001
> lQ45eA-ARYv-JiVX-JRjR-eyHl-NCXO-vkB2m0
What does /etc/fstab look like?
See if "vgchange -ay" activates fedora, if so then rebuild the initramfs.
Use dracut to rebuild the initial ramdisk and see if that changes
anything something like;
dracut -f /boot/initramfs-$(uname -r).img $(uname -r)
You would need to manually substitute the kern
On 7/15/25 8:24 AM, Roger Heflin wrote:
On Mon, Jul 14, 2025 at 11:51 PM Robert McBroom via users
wrote:
and /dev/nvme0n1p6
while pasting got a line feed in the text
LVM2_mem LVM2 001
lQ45eA-ARYv-JiVX-JRjR-eyHl-NCXO-vkB2m0
~# lvmdiskscan -l
WARNING: only con
On Mon, Jul 14, 2025 at 11:51 PM Robert McBroom via users
wrote:
>
and /dev/nvme0n1p6
>
> LVM2_mem LVM2 001
> lQ45eA-ARYv-JiVX-JRjR-eyHl-NCXO-vkB2m0
>
> ~# lvmdiskscan -l
>
> WARNING: only considering LVM devices
> 0 LVM physical volume whole disks
>
> 0 LVM physic
On 7/13/25 1:31 PM, Robert McBroom via users wrote:
During boot I get the message
block nvme0n1: No UUID available providing old NGUID
When I try to mount the lvm I get the message
~# mount /dev/mapper/fedora /sd1
mount: /sd1: fsconfig system call failed: /dev/mapper/fedora Can't
lookup block
On 7/13/25 5:08 PM, Barry wrote:
On 13 Jul 2025, at 21:32, Robert McBroom via users
wrote:
During boot I get the message
block nvme0n1: No UUID available providing old NGUID
When I try to mount the lvm I get the message
~# mount /dev/mapper/fedora /sd1
mount: /sd1: fsconfig system ca
> On 13 Jul 2025, at 21:32, Robert McBroom via users
> wrote:
>
>
> During boot I get the message
>
> block nvme0n1: No UUID available providing old NGUID
>
> When I try to mount the lvm I get the message
>
> ~# mount /dev/mapper/fedora /sd1
> mount: /sd1: fsconfig system call failed: /de
During boot I get the message
block nvme0n1: No UUID available providing old NGUID
When I try to mount the lvm I get the message
~# mount /dev/mapper/fedora /sd1
mount: /sd1: fsconfig system call failed: /dev/mapper/fedora Can't
lookup blockdev.
dmesg(1) may have more information after
10 matches
Mail list logo
