Re: e2fsck malfunction?
On Thu, 2025-03-13 at 16:47 -0700, Dave Close wrote: > I have been trying to create an SDcard to use with an Raspberry > Pi. The card is created using the rpi-imager program on Fedora (41) > and that program reports the creation as successful. Later, after > mounting the ext4 partition on the card under Fedora and doing two or > three minutes of exploration, I encounter a bad block. So I unmount > the partition and use e2fsck to locate any bad blocks and mark them: > > e2fsck -y -c /dev/sdb2 > > But after that when I try to remount the partition, it seems that > e2fsck has destroyed the filesystem! If it failed during write, your e2fsck is just removing the bad sectors not magically repairing what ought to be there. You can only repair a filesystem if you can read failing data and replace it with undamaged data. And it sounds like the failures are in important places if that's happening. You could have a cascading failure (not just static errors, but increasing ones). Some cards can self-repair, so you mightn't notice problems until the failures become severe, and external repair attempts could fight with internal ones. A failing card is unreliable, it's not worth the grief. -- uname -rsvp Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. -- ___ 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: e2fsck malfunction?
I wrote: > Jeffrey Walton replied: >> Throw the old SDcard away, and use a new one. > > I intend to. But this isn't a problem with the card. Samuel Sieb answered: >Are you sure? It does sound likely. e2fsck doesn't write without warning. >I suggest testing it with the f3 tools. "e2fsck -c" said it didn't find any bad blocks. If it didn't find any, why would it modify the card at all? "e2fsck -y" (by itself) did not report any problem. I agree the card seems flaky and I've already ordered a replacement. But I remain concerned by the result of using -c; that doesn't seem related to the problems with the card since it claims not to have found any bad blocks. -- Dave Close, Compata, Irvine CA +1 714 434 7359 d...@compata.com dhcl...@alumni.caltech.edu "The mind is a wonderful thing. It starts working the minute you're born and never stops until you get up to speak in public." -Roscoe Drummond -- ___ 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: dnf downgrade dependencies
>On 3/13/25 10:20 PM, Dave Close wrote: >> I've decided I'm unhappy with one of the changes made by the most >> recent version of LibreOffice, 24.8, and I want to try going back to >> the previous version, 24.2, which is part of the FC40 repository. >> But I'm astounded by the result of the command below. (Without >> allowerasing the command won't do anything.) Samuel Sieb wrote: >libreoffice has many dependencies and if you downgrade those to what >that version needs, then you have to also downgrade all the packages >that depend on those dependencies. Well then, I suppose I could download the source package and try to build it on FC41... -- Dave Close, Compata, Irvine CA +1 714 434 7359 d...@compata.com dhcl...@alumni.caltech.edu "Paying attention to politicians can make you dumb." - Declan McCullagh -- ___ 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: Turning off current directory display in a terminal window
On Wed, 12 Mar 2025, Patrick O'Callaghan wrote: On Wed, 2025-03-12 at 15:39 -0700, Mike Wright wrote: On 3/12/25 15:03, Patrick O'Callaghan wrote: On Wed, 2025-03-12 at 15:29 -0400, Todd Zullinger wrote: That doesn't apply in Konsole for one. Don't know if it applies in other terminal emulators. You may be talking about different things. PS1 applies to the shell running in the terminal. It sounds like you're thinking of the terminal window's title, perhaps? I assumed that was what the OP was talking about. If he meant the Shell prompt, perhaps he was unfamiliar with the usual terminology. -- How might I turn off (or change) the display of the current path in a terminal window? For example I have one terminal window with: rgm@LX140e-3:~/data/htt/Projects/Critical/drafts/draft-ietf-drip-rid/dki-try2$ -- His plaint was that the prompt fills the line; he seeks a shorter prompt. My point was that the question is poorly phrased. It mentions "the No. It wasn't. display of the current path in the terminal window", when the actual issue has absolutely nothing to do with terminal windows. The exact same thing would happen in a virtual console or a glass teletype, since it's really about the Shell, not the particular display being used. My mistake for reading what the question said rather than what (in hindsight) it really meant. A careless reader might get ambiguity, but there was no reason to interpret OP's question as definitely being about the title at the top of the terminal window. OP complained that the directory name filled the line, not really a problem in the title. The line is also in the terminal window. Others had not problem understanding the question. A sensible definition of "terminal window" might exclude the frame generated by the window manager. In that case, there whould be no possible ambiguity. -- Michael henne...@mail.cs.ndsu.nodak.edu "SCSI is NOT magic. There are *fundamental technical reasons* why it is necessary to sacrifice a young goat to your SCSI chain now and then." -- John Woods-- ___ 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
dnf downgrade dependencies
I've decided I'm unhappy with one of the changes made by the most recent version of LibreOffice, 24.8, and I want to try going back to the previous version, 24.2, which is part of the FC40 repository. But I'm astounded by the result of the command below. (Without allowerasing the command won't do anything.) dnf downgrade --allowerasing --enable-repo=fedora40,updates40 \ libreoffice-24.2.2.1-3.fc40.x86_64 ... Transaction Summary: Installing:21 packages Upgrading: 8 packages Replacing: 1169 packages Removing: 13 packages Downgrading: 1161 packages This is effectively returning to FC40, not just downgrading a single package. Of course, I didn't follow through. But somehow DNF thinks the following packages are dependent on LibreOffice: mplayer, opencv, python3-crypt-r, tesseract-libs, x264, among others! And it thinks the removal of these packages requires downgrading others, including mod-perl! I suppose I can simply download the older LibreOffice packages and then use rpm to replace them. But there could be some authentic library dependencies. Is there a better solution? -- Dave Close, Compata, Irvine CA "He who thinks with difficulty d...@compata.com, +1 714 434 7359believes with alacrity." dhcl...@alumni.caltech.edu -- Ambrose Bierce -- ___ 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: dnf downgrade dependencies
On 13 Mar 2025 at 22:58, Dave Close wrote: To: users@lists.fedoraproject.org Subject:Re: dnf downgrade dependencies From: Dave Close Date sent: Thu, 13 Mar 2025 22:58:42 -0700 Send reply to: users@lists.fedoraproject.org > >On 3/13/25 10:20 PM, Dave Close wrote: > >> I've decided I'm unhappy with one of the changes made by the most > >> recent version of LibreOffice, 24.8, and I want to try going back to > >> the previous version, 24.2, which is part of the FC40 repository. > >> But I'm astounded by the result of the command below. (Without > >> allowerasing the command won't do anything.) > > Samuel Sieb wrote: > >libreoffice has many dependencies and if you downgrade those to what > >that version needs, then you have to also downgrade all the packages > >that depend on those dependencies. > > Well then, I suppose I could download the source package and try to > build it on FC41... Sent a longer reply to Dave Close. But you can have both the Fedora version of Libre Office and a Libre Office version at the same time. They can be installed at same time. On my Fedora 41 machine I have the two versions running. So, I'm doing the reverse of what he wants. I have the default 24.8.5.2 version of Fedora 41 and have the newer 25.2.1.2 version. Installing the LibreOffice version puts the files in /opt directory, while the Fedora version is in its location. Menu shows both. Just showing writer packages as example. libreoffice25.2-writer-25.2.1.2-2.x86_64 libreoffice-writer-24.8.5.2-1.fc41.x86_64 # which libreoffice /usr/bin/libreoffice # which libreoffice25.2 /usr/bin/libreoffice25.2 # ls -l /usr/bin/libreoffice25.2 /usr/bin/libreoffice25.2 -> /opt/libreoffice25.2/program/soffice So, except for doubling the space to have two versions for testing. Doesn't show any issues that I've seen? But limited testing. > -- > Dave Close, Compata, Irvine CA +1 714 434 7359 >d...@compata.com dhcl...@alumni.caltech.edu > "Paying attention to politicians can make you dumb." - Declan McCullagh > > > -- > ___ > 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 ++ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:mi...@guam.net mailto:msetze...@gmail.com mailto:msetze...@gmx.com Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ ++ -- ___ 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: dnf downgrade dependencies
On 3/13/25 10:20 PM, Dave Close wrote: I've decided I'm unhappy with one of the changes made by the most recent version of LibreOffice, 24.8, and I want to try going back to the previous version, 24.2, which is part of the FC40 repository. But I'm astounded by the result of the command below. (Without allowerasing the command won't do anything.) dnf downgrade --allowerasing --enable-repo=fedora40,updates40 \ libreoffice-24.2.2.1-3.fc40.x86_64 ... Transaction Summary: Installing:21 packages Upgrading: 8 packages Replacing: 1169 packages Removing: 13 packages Downgrading: 1161 packages This is effectively returning to FC40, not just downgrading a single package. Of course, I didn't follow through. But somehow DNF thinks the following packages are dependent on LibreOffice: mplayer, opencv, python3-crypt-r, tesseract-libs, x264, among others! And it thinks the removal of these packages requires downgrading others, including mod-perl! libreoffice has many dependencies and if you downgrade those to what that version needs, then you have to also downgrade all the packages that depend on those dependencies. I suppose I can simply download the older LibreOffice packages and then use rpm to replace them. But there could be some authentic library dependencies. Is there a better solution? You don't need to setup your own repo files for this. dnf --releasever=40 install --allowerasing libreoffice-24.2.2.1-3.fc40.x86_64 But that won't help you any. You can't do this. Here's a big clue when run without the --allowerasing: Problem: package libreoffice-pyuno-1:24.2.2.1-3.fc40.x86_64 from fedora requires python(abi) = 3.12, but none of the providers can be installed - package libreoffice-base-1:24.2.2.1-3.fc40.x86_64 from fedora requires libreoffice-pyuno(x86-64) = 1:24.2.2.1-3.fc40, but none of the providers can be installed - cannot install both python3-3.12.2-2.fc40.x86_64 from fedora and python3-3.13.2-1.fc41.x86_64 from @System - cannot install both python3-3.12.9-1.fc40.x86_64 from updates and python3-3.13.2-1.fc41.x86_64 from @System - package libreoffice-1:24.2.2.1-3.fc40.x86_64 from fedora requires libreoffice-base(x86-64) = 1:24.2.2.1-3.fc40, but none of the providers can be installed - installed package python3-google-re2-1:20240702-19.fc41.x86_64 requires python(abi) = 3.13, but none of the providers can be installed - conflicting requests - problem with installed package The first problem is that it requires Python 3.12. -- ___ 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: e2fsck malfunction?
On 3/13/25 10:05 PM, Dave Close wrote: I wrote: Jeffrey Walton replied: Throw the old SDcard away, and use a new one. I intend to. But this isn't a problem with the card. Samuel Sieb answered: Are you sure? It does sound likely. e2fsck doesn't write without warning. I suggest testing it with the f3 tools. "e2fsck -c" said it didn't find any bad blocks. If it didn't find any, why would it modify the card at all? "e2fsck -y" (by itself) did not report any problem. That's what I'm saying. It wouldn't have modified it at all. I agree the card seems flaky and I've already ordered a replacement. But I remain concerned by the result of using -c; that doesn't seem related to the problems with the card since it claims not to have found any bad blocks. Have you used this card before? Are you sure it's actually as large as it says it is? That's why I'm suggesting you test it with f3. -- ___ 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: Turning off current directory display in a terminal window
On Wed, Mar 12, 2025 at 3:38 PM Bob Marčan via users wrote: > > On Wed, 12 Mar 2025 12:09:21 -0400 > "Robert Moskowitz" wrote: > > > I don't want it permanent. this whole process is to deal with those > > specific times I am working on a project in a very deep directory. > > > > I have a dozen terminal windows open right now in 5 workspaces; it is > > only 2 that are on this project (working on the scripts for > > draft-ietf-drip-dki-05). Years ago I had the same issue (using zsh), so added a newline after the directory name. $PS1='$' $PS1='\n$' $ -- 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: Fresh install Fedora 41. Bootloader Problem. Camina Shell/Barry Scott/Samual Sieb/Jeffrey Walton/Tim. On Dell Inspiron 3721
On 13/3/25 19:11, Michael D. Setzer II via users wrote: On 13 Mar 2025 at 0:17, Samuel Sieb wrote: Date sent: Thu, 13 Mar 2025 00:17:44 -0700 Subject:Re: Fresh install Fedora 41. Bootloader Problem. Camina Shell/Barry Scott/Samual Sieb/Jeffrey Walton/Tim. On Dell Inspiron 3721 To: users@lists.fedoraproject.org From: Samuel Sieb Send reply to: Community support for Fedora users On 3/12/25 2:11 PM, Michael D. Setzer II via users wrote: Second, the latest released grub2 has an issue with windows ntfs regular partitions, and doesn't create grub menu entries. Works with UEFI windows thou. There is an updated version of grub2 in updates-testing repo, and atleast on my two notebooks that have windows 7, the grub2 in updates-testing, did get the boot menu to have the windows 7 boot option. Even if you get it to show on the menu, recent versions of windows will not successfully boot from grub. Don't know about recent version of windows. I only have machines with Fedora 41 only, and two notebooks with Fedora 41 and Windows 7. They boot the windows 7 fine using both the 42_custom I created or now with the newest grub2 updates. Don't have any machines with newer than windows 7. Do have two beelink mini machines, but they just have windows 11. So, perhaps you have more info than I do. I've had no issues booting Windows 7 through Windows 11 from grub menus via both Bios installs and UEFI installs on my home pc, but I have never installed bitlocker. regards, Steve -- ___ 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 ++ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:mi...@guam.net mailto:msetze...@gmail.com mailto:msetze...@gmx.com Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ ++ -- ___ 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: Fresh install Fedora 41. Bootloader Problem. Camina Shell/Barry Scott/Samual Sieb/Jeffrey Walton/Tim. On Dell Inspiron 3721.
On 13/3/25 18:16, Samuel Sieb wrote: On 3/12/25 2:20 PM, Stephen Morris wrote: In /etc/default/grub is the following line, that line causes grub to boot off, I think, the first entry in the grub menus and to not show the menus at all. If you change the entry to "false" instead of "true" and run grub2-mkconfig to get it to take effect without waiting for the next kernel update the menus will be displayed. You may want to change the GRUB_TIMEOUT entry to specify a time that is long enough to allow the menus to remain displayed so that you can make a selection if you want to. GRUB_ENABLE_BLSCFG=true No, that's not it. Don't change that setting. https://discussion.fedoraproject.org/t/how-to-disable-grub2-menu-auto-hide/76519/3 Sorry Samuel, you are right I was confusing the two. I think I set the autohide to off manually a long time ago, but I also have the above grub parameter set to false for another reason, which I've forgotten what it was. regards, Steve -- ___ 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: e2fsck malfunction?
On 3/13/25 4:47 PM, Dave Close wrote: I have been trying to create an SDcard to use with an Raspberry Pi. The card is created using the rpi-imager program on Fedora (41) and that program reports the creation as successful. Later, after mounting the ext4 partition on the card under Fedora and doing two or three minutes of exploration, I encounter a bad block. So I unmount the partition and use e2fsck to locate any bad blocks and mark them: e2fsck -y -c /dev/sdb2 Is there any output? Maybe don't use the `-y` option for now. -- ___ 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: e2fsck malfunction?
On Thu, Mar 13, 2025 at 7:48 PM Dave Close wrote: > > I have been trying to create an SDcard to use with an Raspberry > Pi. The card is created using the rpi-imager program on Fedora (41) > and that program reports the creation as successful. Later, after > mounting the ext4 partition on the card under Fedora and doing two or > three minutes of exploration, I encounter a bad block. So I unmount > the partition and use e2fsck to locate any bad blocks and mark them: > > e2fsck -y -c /dev/sdb2 > > But after that when I try to remount the partition, it seems that > e2fsck has destroyed the filesystem! > > # mount /dev/sdb2 /mnt > mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sdb2, > missing codepage or helper program, or other error. > dmesg(1) may have more information after failed mount system call. > > Checking dmesg, I see that the mount has tried several possible > filesystem types without success, including several lines like, > "EXT4-fs (sdb2): VFS: Can't find ext4 filesystem". Explicitly adding > "-t ext4" to the mount does not help. > > I've repeated this process, again getting success, including > verification, from rpi-imager. This time I omitted the -c from the > e2fsck command and was able to mount the partition after. > > So it appears that asking e2fsck to check for and mark bad blocks > causes it to destroy the superblock(s). Is there another explanation? Throw the old SDcard away, and use a new one. The old SDcard is clapped out. I used to do a lot of testing of C and C++ libraries on ARM SBCs, like BeagleBoards, BananaPi's, Raspberry Pi's and WandBoards. The low resources (like 512 MB or 1 GB or RAM) and C++ compiler ensured I needed a swap file to build the libraries. I used to go through SDcards like they were dirty underwear. Once I started seeing filesystem errors I threw away the old card and used a new card with the board. 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: e2fsck malfunction?
I wrote: >I have been trying to create an SDcard to use with an Raspberry >Pi. The card is created using the rpi-imager program on Fedora (41) >and that program reports the creation as successful. Later, after >mounting the ext4 partition on the card under Fedora and doing two or >three minutes of exploration, I encounter a bad block. So I unmount >the partition and use e2fsck to locate any bad blocks and mark them: > > e2fsck -y -c /dev/sdb2 Samuel Sieb replied: >Is there any output? Maybe don't use the `-y` option for now. The only output was a statement that no bad blocks were found. Jeffrey Walton replied: >Throw the old SDcard away, and use a new one. I intend to. But this isn't a problem with the card. -- Dave Close, Compata, Irvine CA +1 714 434 7359 d...@compata.com dhcl...@alumni.caltech.edu "Education is the kindling of a flame, not the filling of a vessel." -- Socrates -- ___ 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: e2fsck malfunction?
On 3/13/25 5:29 PM, Dave Close wrote: Jeffrey Walton replied: Throw the old SDcard away, and use a new one. I intend to. But this isn't a problem with the card. Are you sure? It does sound likely. e2fsck doesn't write without warning. I suggest testing it with the f3 tools. -- ___ 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: e2fsck malfunction?
On Thu, Mar 13, 2025 at 8:29 PM Dave Close wrote: > > I wrote: > >I have been trying to create an SDcard to use with an Raspberry > >Pi. The card is created using the rpi-imager program on Fedora (41) > >and that program reports the creation as successful. Later, after > >mounting the ext4 partition on the card under Fedora and doing two or > >three minutes of exploration, I encounter a bad block. So I unmount > >the partition and use e2fsck to locate any bad blocks and mark them: > > > > e2fsck -y -c /dev/sdb2 > > [...] > Jeffrey Walton replied: > >Throw the old SDcard away, and use a new one. > > I intend to. But this isn't a problem with the card. It sure sounds like it (to me): > Later, after mounting the ext4 partition on the card under Fedora and > doing two or three minutes of exploration, I encounter a bad block. 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
e2fsck malfunction?
I have been trying to create an SDcard to use with an Raspberry Pi. The card is created using the rpi-imager program on Fedora (41) and that program reports the creation as successful. Later, after mounting the ext4 partition on the card under Fedora and doing two or three minutes of exploration, I encounter a bad block. So I unmount the partition and use e2fsck to locate any bad blocks and mark them: e2fsck -y -c /dev/sdb2 But after that when I try to remount the partition, it seems that e2fsck has destroyed the filesystem! # mount /dev/sdb2 /mnt mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sdb2, missing codepage or helper program, or other error. dmesg(1) may have more information after failed mount system call. Checking dmesg, I see that the mount has tried several possible filesystem types without success, including several lines like, "EXT4-fs (sdb2): VFS: Can't find ext4 filesystem". Explicitly adding "-t ext4" to the mount does not help. I've repeated this process, again getting success, including verification, from rpi-imager. This time I omitted the -c from the e2fsck command and was able to mount the partition after. So it appears that asking e2fsck to check for and mark bad blocks causes it to destroy the superblock(s). Is there another explanation? -- Dave Close, Compata, Irvine CA +1 714 434 7359 d...@compata.com dhcl...@alumni.caltech.edu "Some ideas are so stupid that only intellectuals believe them." -- George Orwell -- ___ 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: Fresh install Fedora 41. Bootloader Problem. Camina Shell/Barry Scott/Samual Sieb/Jeffrey Walton/Tim. On Dell Inspiron 3721.
On 3/12/25 2:20 PM, Stephen Morris wrote: In /etc/default/grub is the following line, that line causes grub to boot off, I think, the first entry in the grub menus and to not show the menus at all. If you change the entry to "false" instead of "true" and run grub2-mkconfig to get it to take effect without waiting for the next kernel update the menus will be displayed. You may want to change the GRUB_TIMEOUT entry to specify a time that is long enough to allow the menus to remain displayed so that you can make a selection if you want to. GRUB_ENABLE_BLSCFG=true No, that's not it. Don't change that setting. https://discussion.fedoraproject.org/t/how-to-disable-grub2-menu-auto-hide/76519/3 -- ___ 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: Fresh install Fedora 41. Bootloader Problem. Camina Shell/Barry Scott/Samual Sieb/Jeffrey Walton/Tim. On Dell Inspiron 3721
On 3/12/25 2:11 PM, Michael D. Setzer II via users wrote: Second, the latest released grub2 has an issue with windows ntfs regular partitions, and doesn't create grub menu entries. Works with UEFI windows thou. There is an updated version of grub2 in updates-testing repo, and atleast on my two notebooks that have windows 7, the grub2 in updates-testing, did get the boot menu to have the windows 7 boot option. Even if you get it to show on the menu, recent versions of windows will not successfully boot from grub. -- ___ 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: Fresh install Fedora 41. Bootloader Problem. Camina Shell/Barry Scott/Samual Sieb/Jeffrey Walton/Tim. On Dell Inspiron 3721
On 13 Mar 2025 at 0:17, Samuel Sieb wrote: Date sent: Thu, 13 Mar 2025 00:17:44 -0700 Subject:Re: Fresh install Fedora 41. Bootloader Problem. Camina Shell/Barry Scott/Samual Sieb/Jeffrey Walton/Tim. On Dell Inspiron 3721 To: users@lists.fedoraproject.org From: Samuel Sieb Send reply to: Community support for Fedora users > On 3/12/25 2:11 PM, Michael D. Setzer II via users wrote: > > Second, the latest released grub2 has an issue with windows ntfs > > regular partitions, and doesn't create grub menu entries. Works > > with UEFI windows thou. > > > > There is an updated version of grub2 in updates-testing repo, and > > atleast on my two notebooks that have windows 7, the grub2 in > > updates-testing, did get the boot menu to have the windows 7 boot > > option. > > Even if you get it to show on the menu, recent versions of windows will > not successfully boot from grub. Don't know about recent version of windows. I only have machines with Fedora 41 only, and two notebooks with Fedora 41 and Windows 7. They boot the windows 7 fine using both the 42_custom I created or now with the newest grub2 updates. Don't have any machines with newer than windows 7. Do have two beelink mini machines, but they just have windows 11. So, perhaps you have more info than I do. > > -- > ___ > 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 ++ Michael D. Setzer II - Computer Science Instructor (Retired) mailto:mi...@guam.net mailto:msetze...@gmail.com mailto:msetze...@gmx.com Guam - Where America's Day Begins G4L Disk Imaging Project maintainer http://sourceforge.net/projects/g4l/ ++ -- ___ 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: Fresh install Fedora 41. Bootloader Problem. Camina Shell/Barry Scott/Samual Sieb/Jeffrey Walton/Tim. On Dell Inspiron 3721
> On 13 Mar 2025, at 07:18, Samuel Sieb wrote: > > Even if you get it to show on the menu, recent versions of windows will not > successfully boot from grub. True if you have bitlocker enabled in windows. But if you are not using bitlocker then grub can boot windows. I do this with my dual boot Windows 11 and Fedora system. Barry -- ___ 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: getting core dump with grub2-mkconfig on systems with windows7 partitions?? (No windows menu entry?)
Today's update (on F41) included a version of grub2 that fixed this issue. Thank you to all those who contributed to fixing it! ``` ... Upgrade grub2-common-1:2.12-20.fc41.noarch Dependency updates Upgrade grub2-tools-minimal-1:2.12-20.fc41.x86_64 Dependency updates Upgrade grub2-tools-extra-1:2.12-20.fc41.x86_64 Userupdates Upgrade grub2-tools-efi-1:2.12-20.fc41.x86_64 Userupdates Upgrade grub2-tools-1:2.12-20.fc41.x86_64 Dependency updates Upgrade grub2-efi-x64-modules-1:2.12-20.fc41.noarch Userupdates Upgrade grub2-efi-x64-1:2.12-20.fc41.x86_64 Userupdates ... ❯ sudo grub2-mkconfig -o /boot/grub2/grub.cfg Generating grub configuration file ... Found Windows Boot Manager on /dev/nvme2n1p1@/efi/Microsoft/Boot/bootmgfw.efi Adding boot menu entry for UEFI Firmware Settings ... Detecting snapshots ... Found snapshot: 2025-03-13 11:05:21 | .snapshots/950/snapshot | post | dnf upgrade Found snapshot: 2025-03-13 11:04:12 | .snapshots/949/snapshot | pre| dnf upgrade Found snapshot: 2025-03-13 11:00:00 | .snapshots/948/snapshot | single | timelin ``` -- ___ 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
