Re: Problem accessing lvm on nvme drive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 kernel versions if you are
building different kernels initramfs.

and reboot and see if that fixes it.

I have a machine with an nvme that from time to time does not get seen
at boot and fails to find root.  Booting back the old kernel and
rebuilding the intramfs fixes it. I have spent a few minutes examing
the working and non-working initramfs's and do not see what is missing
from the bad one.

On Tue, Jul 15, 2025 at 10:36 PM Robert McBroom via users
<users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
>
> On 7/15/25 8:24 AM, Roger Heflin wrote:
>
> On Mon, Jul 14, 2025 at 11:51 PM Robert McBroom via users
> <users@xxxxxxxxxxxxxxxxxxxxxxx> 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 considering LVM devices
>  0 LVM physical volume whole disks
>
>  0 LVM physical volumes
>
>
> pvs and vgs just return. on the system that sees the drives I get
>
> nvme0n1
> ├─nvme0n1p1
> ├─nvme0n1p2    ntfs                 Space            6C8EF2E161A652CA
> ├─nvme0n1p3    vfat        FAT32                     663E-94E3
> ├─nvme0n1p4    xfs                                   241ab641-a6b2-4979-9864-9d1d08db2d61
> ├─nvme0n1p5    LVM2_member LVM2 001                  v1gXoi-sKLO-fS0t-oKxo-en1J-7vOu-BH8Hal
> │ └─fedora_
> │              xfs                                   43c752f2-3963-4859-a4d6-8669482d51fb
> └─nvme0n1p6    LVM2_member LVM2 001                  lQ45eA-ARYv-JiVX-JRjR-eyHl-NCXO-vkB2m0
>   └─fedora_
>                xfs                                   43c752f2-3963-4859-a4d6-8669482d51fb
>
>
> --
>
> what does "cat /proc/cmdline" show?
>
>
>
>
>
>
>
> :~$ cat /proc/cmdline
>
> :~$ cat /proc/cmdline
> BOOT_IMAGE=/vmlinuz.alt root=/dev/sda6 ro rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-dr
> m.modeset=1 initcall_blacklist=simpledrm_platform_driver_init SYSFONT=latarcyrheb-sun16 LANG=en_US.UTF-8
>
> grep filter /etc/lvm/*.conf
>
> ~# grep filter /etc/lvm/*.conf
> /etc/lvm/lvm.conf:      # Configuration option devices/filter.
> /etc/lvm/lvm.conf:      # Run vgscan after changing the filter to regenerate the cache.
> /etc/lvm/lvm.conf:      # filter = [ "a|.*|" ]
> /etc/lvm/lvm.conf:      # filter = [ "r|/dev/cdrom|" ]
> /etc/lvm/lvm.conf:      # filter = [ "a|loop|", "r|.*|" ]
> /etc/lvm/lvm.conf:      # filter = [ "a|loop|", "r|/dev/hdc|", "a|/dev/ide|", "r|.*|" ]
> /etc/lvm/lvm.conf:      # filter = [ "a|^/dev/hda8$|", "r|.*|" ]
> /etc/lvm/lvm.conf:      # filter = [ "a|.*|" ]
> /etc/lvm/lvm.conf:      # Configuration option devices/global_filter.
> /etc/lvm/lvm.conf:      # Because devices/filter may be overridden from the command line, it is
> /etc/lvm/lvm.conf:      # not suitable for system-wide device filtering, e.g. udev.
> /etc/lvm/lvm.conf:      # Use global_filter to hide devices from these LVM system components.
> /etc/lvm/lvm.conf:      # The syntax is the same as devices/filter. Devices rejected by
> /etc/lvm/lvm.conf:      # global_filter are not opened by LVM.
> /etc/lvm/lvm.conf:      # global_filter = [ "a|.*|" ]
> /etc/lvm/lvm.conf:      # This is a quick way of filtering out block devices that are not
> /etc/lvm/lvm.conf:      # devices file or the filter. This option does not enable autoactivation
> /etc/lvm/lvm.conf:      # Configuration option activation/mlock_filter.
> /etc/lvm/lvm.conf:      # mlock_filter = [ "locale/locale-archive", "gconv/gconv-modules.cache" ]
>
> lvmdiskscan -d -v
>
> :~# lvmdiskscan -d -v
>  0 disks
>  0 partitions
>  0 LVM physical volume whole disks
>  0 LVM physical volumes
>
> --
> _______________________________________________
> 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
-- 
_______________________________________________
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



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux