Re: Grub2 is not updated / grub2-probe: error: cannot find a device for / (is /dev mounted?)
I usually keep the old version. From time to time I do a diff check to see if there is something new and research the change. On Sat, May 4, 2024 at 8:06 PM Jeffrey Walton wrote: > > > On Sat, May 4, 2024 at 8:11 PM Javier Perez wrote: > >> Don' know. I have been dnf upgrading this system almost since Fedora was >> simple digits. .🤔 >> I am planning a new build for F40 and definitely clean install it. >> > > There are post-upgrade tasks that should be performed to keep the system > tidy. See < > https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/#sect-optional-post-upgrade-tasks > >. > > In particular, are you taking the maintainer's version of config files > during `rpmconf -a`? Or are you keeping old versions? > > Jeff > -- > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- -- /\_/\ |O O| pepeb...@gmail.com Javier Perez While the night runs toward the day... m m Pepebuho watches from his high perch. -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Grub2 is not updated / grub2-probe: error: cannot find a device for / (is /dev mounted?)
On Sat, May 4, 2024 at 8:11 PM Javier Perez wrote: > Don' know. I have been dnf upgrading this system almost since Fedora was > simple digits. .🤔 > I am planning a new build for F40 and definitely clean install it. > There are post-upgrade tasks that should be performed to keep the system tidy. See < https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/#sect-optional-post-upgrade-tasks >. In particular, are you taking the maintainer's version of config files during `rpmconf -a`? Or are you keeping old versions? Jeff -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Grub2 is not updated / grub2-probe: error: cannot find a device for / (is /dev mounted?)
Don' know. I have been dnf upgrading this system almost since Fedora was simple digits. .🤔 I am planning a new build for F40 and definitely clean install it. On Sat, May 4, 2024, 19:00 Samuel Sieb wrote: > On 5/4/24 1:26 AM, Javier Perez wrote: > > Ok, I think I solved it. > > I created the entry manually for Kernel 6.8.8 on grub.cfg and rebooted. > > Once in this kernel, I dnf reinstalled it and everything seems to have > > worked fine. > > dnf did not show any error and I had journalctl -f on another terminal > > and did not see any error either. > > I am going to chalk this one to some difference between Kernel 6.7 and > > 6.8. Weird. > > Did you somehow miss the change to BLS? The entries shouldn't be in > grub.cfg. They should be in /boot/loader/entries. > -- > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue > -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F40 Live image boot failure
On Sat, May 4, 2024 at 5:33 PM Patrick O'Callaghan wrote: > On Sat, 2024-05-04 at 14:53 -0400, Jeffrey Walton wrote: > > On Sat, May 4, 2024 at 7:30 AM George N. White III > > wrote: > > > > > [...] > > > > > > You should not be surprised by issues with recent kernels and > > > hardware > > > over a decade > > > old. > > > > > > > It may be worth pointing out that the kernel still supports the ISA > > bus, > > which is early IBM PC support. If the kernel supports a 40 year old > > bus, > > then a 10 year old video card should also be supported. It is > > probably more > > correct to say, the problem is with the driver, like no one has > > ported it > > to the latest kernel. > > "Support" isn't binary. I have a 10-year old MSI motherboard and get a > slew of ACPI errors every time I boot. They don't seem to affect > anything but they're there. I presume that a more modern mobo would > have fewer of these, if any. > I've seen the ACPI errors a lot in the past, too. I noticed they are not present in Fedora's 6.8 kernel. I guess that means the messages have been suppressed, or the kernel driver has been fixed. I also update my UEFI regularly, so it could be OEM bug fixes, too. Jeff -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Grub2 is not updated / grub2-probe: error: cannot find a device for / (is /dev mounted?)
On 5/4/24 1:26 AM, Javier Perez wrote: Ok, I think I solved it. I created the entry manually for Kernel 6.8.8 on grub.cfg and rebooted. Once in this kernel, I dnf reinstalled it and everything seems to have worked fine. dnf did not show any error and I had journalctl -f on another terminal and did not see any error either. I am going to chalk this one to some difference between Kernel 6.7 and 6.8. Weird. Did you somehow miss the change to BLS? The entries shouldn't be in grub.cfg. They should be in /boot/loader/entries. -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F40 Live image boot failure
On Sat, May 4, 2024 at 8:40 PM Tim via users wrote: > On Sat, 2024-05-04 at 22:32 +0100, Patrick O'Callaghan wrote: > > "Support" isn't binary. I have a 10-year old MSI motherboard and get a > > slew of ACPI errors every time I boot. They don't seem to affect > > anything but they're there. I presume that a more modern mobo would > > have fewer of these, if any. > > I have to wonder just how many things (motherboards, peripherals, > software, etc) were knowingly released full of bugs with either the > thought that they'd get around to fixing them with an update, or just > didn't give a damn. We've probably all had something that never worked > right, and was never going to. > My experience with early stuff released with bugs is that it was released after they got it to work on one system. Many issues were related to timing so stuff that worked initially would fail when moved to a newer, faster, machine. People were devising workarounds for buggy hardware. Some of those may have been adopted by distros, but are now being lost. -- George N. White III -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F40 Live image boot failure
On Sat, 2024-05-04 at 22:32 +0100, Patrick O'Callaghan wrote: > "Support" isn't binary. I have a 10-year old MSI motherboard and get a > slew of ACPI errors every time I boot. They don't seem to affect > anything but they're there. I presume that a more modern mobo would > have fewer of these, if any. I have to wonder just how many things (motherboards, peripherals, software, etc) were knowingly released full of bugs with either the thought that they'd get around to fixing them with an update, or just didn't give a damn. We've probably all had something that never worked right, and was never going to. -- NB: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the list. The following system info data is generated fresh for each post: uname -rsvp Linux 6.2.15-100.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Thu May 11 16:51:53 UTC 2023 x86_64 -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F40 Live image boot failure
On Sat, 2024-05-04 at 14:53 -0400, Jeffrey Walton wrote: > On Sat, May 4, 2024 at 7:30 AM George N. White III > wrote: > > > [...] > > > > You should not be surprised by issues with recent kernels and > > hardware > > over a decade > > old. > > > > It may be worth pointing out that the kernel still supports the ISA > bus, > which is early IBM PC support. If the kernel supports a 40 year old > bus, > then a 10 year old video card should also be supported. It is > probably more > correct to say, the problem is with the driver, like no one has > ported it > to the latest kernel. "Support" isn't binary. I have a 10-year old MSI motherboard and get a slew of ACPI errors every time I boot. They don't seem to affect anything but they're there. I presume that a more modern mobo would have fewer of these, if any. poc -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F40 Live image boot failure
On Sat, May 4, 2024 at 7:30 AM George N. White III wrote: > [...] > > You should not be surprised by issues with recent kernels and hardware > over a decade > old. > It may be worth pointing out that the kernel still supports the ISA bus, which is early IBM PC support. If the kernel supports a 40 year old bus, then a 10 year old video card should also be supported. It is probably more correct to say, the problem is with the driver, like no one has ported it to the latest kernel. Jeff -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: What is Castor ? Att.Jonathan Billings.
castor is someplace on your machine defined as the linux node's hostname. dhcp-client does deliver the defined hostname in the dhcp requests/responses to the router when it asks for the IP address. What does 'hostname' report? and 'hostnamectl' report as the hostname? On Sat, May 4, 2024 at 10:17 AM Ger van Dijck wrote: > > Hi, > > > A bit late Jonathan but here is my answer. > > > After upgrade to Fedora 40 all runs perfect , but the login prompt looks > as follows : > > > [root@castor GervanDijck] # > > > Suddenly the router a Fritz-Box 7490 detects the Name Castor with > IP192.168.178.29 (not connectebel) with a MAC number and the connection > is WLAN. > > > I just do not understand it : What does it represent ? > > > > > Ger van Dijck. > -- > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F40 Live image boot failure
On Sat, 2024-05-04 at 08:28 -0300, George N. White III wrote: > Over the years, linux has had workarounds for hardware > idiosyncrasies. I think some of those workarounds are being dropped > or lost as support for newer hardware is added with new and improved > code. > > You should not be surprised by issues with recent kernels and > hardware over a decade old. Especially considering what someone said on this list not long ago, saying how they thought everybody has beefy CPUs and graphics cards, to which I gave a one-word answer. It's no surprise that software developers might have the latest and greatest PC, but it's hardly representative of all users. Of course they can't have every piece of hardware to test against, but it's quite contemptuous to expect people to just spend more money on their PC. -- NB: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the list. The following system info data is generated fresh for each post: uname -rsvp Linux 6.2.15-100.fc36.x86_64 #1 SMP PREEMPT_DYNAMIC Thu May 11 16:51:53 UTC 2023 x86_64 -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
What is Castor ? Att.Jonathan Billings.
Hi, A bit late Jonathan but here is my answer. After upgrade to Fedora 40 all runs perfect , but the login prompt looks as follows : [root@castor GervanDijck] # Suddenly the router a Fritz-Box 7490 detects the Name Castor with IP192.168.178.29 (not connectebel) with a MAC number and the connection is WLAN. I just do not understand it : What does it represent ? Ger van Dijck. -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: How to increase size of /boot partition
On Fri, May 3, 2024 at 2:52 PM richard emberson wrote: > Just today I upgraded from 39 to 40 but there was an issue: > dnf told me I needed some 800k more space in my /boot partition to proceed. > I had two kernels in /boot so I dnf removed those associated with the older > of the two kernels. I then successfully upgraded. > [...] > I realize one way is to backup /home and then reinstall Fedora but 1) that seems like a lot of work and > 2) it would mean that the machine in question would then have to > use Wayland rather than Xorg. > Bots have taken over the internet, and contrary to "bot" wisdom, Fedora 40 still has Xorg. Systems upgraded over many years often have packages that not present in current F40. Resulting issues can be difficult to understand as few users will have those old packages. Doing a fresh install every few years keeps you closer to a configuration others have, so any issues you do encounter will probably affect others, but "all problems are shallow given enough eyes". A fresh install also gives you the option of moving to xfs or btrfs. -- George N. White III -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: F40 Live image boot failure
On Fri, May 3, 2024 at 10:05 PM Sam Varshavchik wrote: > It's something with that particular, older hardware, not the iso file. > > An old memory resurfaced: I dimly recalled having problems with using USB > storage devices on the two USB 3.0 ports on that laptop. This was back in > the days with iffy hardware support on Linux, so it was second nature for > me > to try the third, USB 2.0 port on back of the laptop, and they worked. > > So I tried the Live CD on the USB 2.0 port, and it booted. > > So, it's ten years later and Linux still has occasional hardware issues, > it > seems… Until the graphics card died a year ago, I was using a 2007 desktop. There were a couple times when newer kernels had simple mistakes that broke modules supporting old hardware. Others had already filed bug reports by the time I encountered issues, and fixes were not long in appearing. I recall seeing reports of bugs in early USB3 hardware. Over the years, linux has had workarounds for hardware idiosyncrasies. I think some of those workarounds are being dropped or lost as support for newer hardware is added with new and improved code. You should not be surprised by issues with recent kernels and hardware over a decade old. -- George N. White III -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Grub2 is not updated / grub2-probe: error: cannot find a device for / (is /dev mounted?)
Ok, I think I solved it. I created the entry manually for Kernel 6.8.8 on grub.cfg and rebooted. Once in this kernel, I dnf reinstalled it and everything seems to have worked fine. dnf did not show any error and I had journalctl -f on another terminal and did not see any error either. I am going to chalk this one to some difference between Kernel 6.7 and 6.8. Weird. On Sat, May 4, 2024 at 3:08 AM Javier Perez wrote: > Hi. > Since Kernel 6.8 it looks like grub.conf is not being updated. > The files are installed but grub.cfg is not updated. > > During installation I see this error: > > Running scriptlet: kernel-modules-core-6.8.8-200.fc39.x86_64 > > 49/49 > Running scriptlet: kernel-core-6.8.8-200.fc39.x86_64 > > 49/49 > /usr/sbin/grub2-probe: error: cannot find a device for / (is /dev > mounted?). > grub2-probe: error: cannot find a device for / (is /dev mounted?). > No path or device is specified. > Usage: grub2-probe [OPTION...] [OPTION]... [PATH|DEVICE] > Try 'grub2-probe --help' or 'grub2-probe --usage' for more information. > > Running scriptlet: kernel-modules-6.8.8-200.fc39.x86_64 > -- > If I manually add the entry to grub.cfg it appears and runs, but it is > weird that grub is not updating as it used to. > Currently I am using kernel 6.7.10 > This is my fstab > [root@pepewin ~]# cat /etc/fstab > # /etc/fstab > # Created by anaconda on Thu May 28 01:32:34 2015 > # > # Accessible filesystems, by reference, are maintained under '/dev/disk' > # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info > # > UUID=292bd418-8a67-4840-bf12-9478e961867d / btrfs > subvol=root 0 0 > UUID=fc7cfca3-47ee-4810-a8d0-5e1fee6d4ad0 /boot ext4 > defaults1 2 > UUID=6092-A870 /boot/efi vfat > umask=0077,shortname=winnt 0 0 > UUID=d091ba56-916e-468e-9880-9e9e6fec46da /home btrfs > subvol=home 0 0 > UUID=d091ba56-916e-468e-9880-9e9e6fec46da /varbtrfs > subvol=var 0 0 > #UUID=4823bca7-1f7a-4a3f-aa12-fcc03782fe7a swapswap > defaults0 0 > UUID=e713a195-a515-4f57-be8c-bf96f370a41e swapswap > defaults0 0 > -- > This is my lsblk > [root@pepewin ~]# lsblk -f > NAME FSTYPE FSVER LABELUUID > FSAVAIL FSUSE% MOUNTPOINTS > sda > > ├─sda1 ext2 1.03fe06597-c852-4d91-80d9-834351d59a81 > > ├─sda2 swap 1 b084858d-1ad6-4657-a14c-ae99503924d2 > > └─sda3 ext4 1.08136cc0b-298b-46a0-8693-8756a59fbb05 > > sdb > > ├─sdb1 ext2 1.04c212f1f-e567-4612-a9b1-edb18055af89 > > ├─sdb2 ext4 1.0 _Fedora-16-x86_6 7905aa06-92ff-49c2-a51f-ed9553340a1d > > ├─sdb3 swap 1 0f17d854-5f2f-4d57-ad13-c6afb7d933d7 > > ├─sdb4 > > ├─sdb5 ext4 1.048473866-4bda-46d0-87f6-9d10040825b2 > > ├─sdb6 ext4 1.0 /home7a089743-da14-4d09-ad56-38ee4ba69943 > > ├─sdb7 ext4 1.0c17f9aa7-d8dc-4e46-a9a9-590f53085fb6 > > └─sdb8 swap 1 d9c98608-6ef3-4ec2-a59c-963b76affeac > > sdc > > ├─sdc1 vfat FAT16 6092-A870 > 492.2M 1% /boot/efi > ├─sdc2 ext4 1.0fc7cfca3-47ee-4810-a8d0-5e1fee6d4ad0 > 103.1M72% /boot > ├─sdc3 btrfsFedora 292bd418-8a67-4840-bf12-9478e961867d > 19.3G69% / > └─sdc4 swap 1 swap2e713a195-a515-4f57-be8c-bf96f370a41e >[SWAP] > sdd > > ├─sdd1 swap 1 4823bca7-1f7a-4a3f-aa12-fcc03782fe7a > > └─sdd2 btrfsMy_Data d091ba56-916e-468e-9880-9e9e6fec46da > 633.6G66% /home > >/var > sde > > sdf > > sdg > > sdh > > sr0 > > zram0 >[SWAP] > [root@pepewin ~]# > > sda and sdb are just old drives I have left in place, sometimes I look up > info in there. > sdc and sdd are my regular system. > > I did not mind staying for a while in kernel 6.7.10 because I am using an > old nvidia driver (470) but it seems like they solve the problem with > kernel 6.8 already so I should be able to start using it normally > > I tried to google-fu the answer but I found a lot of references and > recipies in ubuntu, gentoo, archlinux that I am not sure if they are > applicable to my case. > > -- > /\_/\ > |O O| pepeb...@gmail.com > Javier Perez > While the night runs > toward the day... > m m Pepebuho watches > from his high perch. > -- -- /\_/\ |O O| pepeb...@gmail.com Javier Perez While the night runs toward the day... m m Pepebuho watches from his high perch. -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedo
Grub2 is not updated / grub2-probe: error: cannot find a device for / (is /dev mounted?)
Hi. Since Kernel 6.8 it looks like grub.conf is not being updated. The files are installed but grub.cfg is not updated. During installation I see this error: Running scriptlet: kernel-modules-core-6.8.8-200.fc39.x86_64 49/49 Running scriptlet: kernel-core-6.8.8-200.fc39.x86_64 49/49 /usr/sbin/grub2-probe: error: cannot find a device for / (is /dev mounted?). grub2-probe: error: cannot find a device for / (is /dev mounted?). No path or device is specified. Usage: grub2-probe [OPTION...] [OPTION]... [PATH|DEVICE] Try 'grub2-probe --help' or 'grub2-probe --usage' for more information. Running scriptlet: kernel-modules-6.8.8-200.fc39.x86_64 -- If I manually add the entry to grub.cfg it appears and runs, but it is weird that grub is not updating as it used to. Currently I am using kernel 6.7.10 This is my fstab [root@pepewin ~]# cat /etc/fstab # /etc/fstab # Created by anaconda on Thu May 28 01:32:34 2015 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # UUID=292bd418-8a67-4840-bf12-9478e961867d / btrfs subvol=root 0 0 UUID=fc7cfca3-47ee-4810-a8d0-5e1fee6d4ad0 /boot ext4 defaults1 2 UUID=6092-A870 /boot/efi vfat umask=0077,shortname=winnt 0 0 UUID=d091ba56-916e-468e-9880-9e9e6fec46da /home btrfs subvol=home 0 0 UUID=d091ba56-916e-468e-9880-9e9e6fec46da /varbtrfs subvol=var 0 0 #UUID=4823bca7-1f7a-4a3f-aa12-fcc03782fe7a swapswap defaults0 0 UUID=e713a195-a515-4f57-be8c-bf96f370a41e swapswap defaults0 0 -- This is my lsblk [root@pepewin ~]# lsblk -f NAME FSTYPE FSVER LABELUUID FSAVAIL FSUSE% MOUNTPOINTS sda ├─sda1 ext2 1.03fe06597-c852-4d91-80d9-834351d59a81 ├─sda2 swap 1 b084858d-1ad6-4657-a14c-ae99503924d2 └─sda3 ext4 1.08136cc0b-298b-46a0-8693-8756a59fbb05 sdb ├─sdb1 ext2 1.04c212f1f-e567-4612-a9b1-edb18055af89 ├─sdb2 ext4 1.0 _Fedora-16-x86_6 7905aa06-92ff-49c2-a51f-ed9553340a1d ├─sdb3 swap 1 0f17d854-5f2f-4d57-ad13-c6afb7d933d7 ├─sdb4 ├─sdb5 ext4 1.048473866-4bda-46d0-87f6-9d10040825b2 ├─sdb6 ext4 1.0 /home7a089743-da14-4d09-ad56-38ee4ba69943 ├─sdb7 ext4 1.0c17f9aa7-d8dc-4e46-a9a9-590f53085fb6 └─sdb8 swap 1 d9c98608-6ef3-4ec2-a59c-963b76affeac sdc ├─sdc1 vfat FAT16 6092-A870 492.2M 1% /boot/efi ├─sdc2 ext4 1.0fc7cfca3-47ee-4810-a8d0-5e1fee6d4ad0 103.1M72% /boot ├─sdc3 btrfsFedora 292bd418-8a67-4840-bf12-9478e961867d 19.3G69% / └─sdc4 swap 1 swap2e713a195-a515-4f57-be8c-bf96f370a41e [SWAP] sdd ├─sdd1 swap 1 4823bca7-1f7a-4a3f-aa12-fcc03782fe7a └─sdd2 btrfsMy_Data d091ba56-916e-468e-9880-9e9e6fec46da 633.6G66% /home /var sde sdf sdg sdh sr0 zram0 [SWAP] [root@pepewin ~]# sda and sdb are just old drives I have left in place, sometimes I look up info in there. sdc and sdd are my regular system. I did not mind staying for a while in kernel 6.7.10 because I am using an old nvidia driver (470) but it seems like they solve the problem with kernel 6.8 already so I should be able to start using it normally I tried to google-fu the answer but I found a lot of references and recipies in ubuntu, gentoo, archlinux that I am not sure if they are applicable to my case. -- /\_/\ |O O| pepeb...@gmail.com Javier Perez While the night runs toward the day... m m Pepebuho watches from his high perch. -- ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
