Re: [PLUG] A hardware issue [UPDATE 2]
On Thu, Jun 15, 2023 at 4:01 PM Rich Shepard wrote: > On Thu, 15 Jun 2023, Michael Ewan wrote: > > > sudo umount /boot/efi > > sudo fsck /dev/sda1 > > sudo mount /boot/efi > > Logged in as root: > # umount /boot/efi > # fsck /dev/sda1 > fsck from util-linux 2.27.1 > fsc.fat 3.0.28 (2015-05-16) > 0x41: Dirty bit is set. Fs was not properly unmounted and some data may be > corrupt. > 1) Remove dirty bit > 2) No action > ? > # mount /dev/sda1 > > What's a dirty bit? It literally says right there "Fs [filesystem] was not properly unmounted [because you power cycled it, rather than reboot] and some data may be corrupt [although it won't be, because you weren't writing anything to the filesystem when you powercycled it, but the OS doesn't know that, it just noticed that the dirty bit was still set because you had not unmounted it cleanly]" > How do I remove it? > Press '1' at the prompt, like the rudimentary menu suggests. Or, alternatively (after unmounting) auto-repair with: fsck.vfat -y /dev/sda1 There is a manual page for fsck.vfat on most systems: man fsck.vfat -- Russell Senior russ...@personaltelco.net
Re: [PLUG] A hardware issue [UPDATE 2]
On Thu, 15 Jun 2023, Michael Ewan wrote: sudo umount /boot/efi sudo fsck /dev/sda1 sudo mount /boot/efi Logged in as root: # umount /boot/efi # fsck /dev/sda1 fsck from util-linux 2.27.1 fsc.fat 3.0.28 (2015-05-16) 0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt. 1) Remove dirty bit 2) No action ? # mount /dev/sda1 What's a dirty bit? How do I remove it? Both umount and mount seemed to work okay since the mount command shows /dev/sda1 on /boot/efi type vfat (rw) Rich
Re: [PLUG] A hardware issue [UPDATE]
On Thu, 15 Jun 2023, Russell Senior wrote: Does it still boot despite the warning? If so, after booting, you ought to be able to unmount /boot and do the fsck. Russell, Yes, it does. Later today I'll umount /boot, run fsck, and remount it. Thanks, Rich
Re: [PLUG] A hardware issue [UPDATE]
On Thu, 15 Jun 2023, Paul Heinlein wrote: For a vfat filesystem, I cannot imagine that the version difference will have any adverse impact. Paul, Makes sense to me. Thanks again, Rich
Re: [PLUG] A hardware issue [UPDATE]
Does it still boot despite the warning? If so, after booting, you ought to be able to unmount /boot and do the fsck. On Thu, Jun 15, 2023, 09:32 Rich Shepard wrote: > On Thu, 15 Jun 2023, Rich Shepard wrote: > > > The desktop is still turned on but needs rebooting and I need to learn > > what's wrong so I can fix it. > > UPDATE: > > /var/log/syslog tells me: > Jun 15 05:35:10 salmo kernel: [ 36.853148] FAT-fs (sda1): Volume was not > properly unmounted. Some > data may be corrupt. Please run fsck. > > /dev/sda1 is /boot/efi type vfat (rw) > > How do I fsck the /boot partition? > > Rich >
Re: [PLUG] A hardware issue [UPDATE]
On Thu, 15 Jun 2023, Rich Shepard wrote: On Thu, 15 Jun 2023, Paul Heinlein wrote: I usually rely on a live CD (or a modern equivalent on a USB stick) to fsck the /boot partition. Paul, I have a Slackware64-15.0 installation on a USB drive. But the desktop's running -14.2. For a vfat filesystem, I cannot imagine that the version difference will have any adverse impact. -- Paul Heinlein heinl...@madboa.com 45°22'48" N, 122°35'36" W
Re: [PLUG] A hardware issue [UPDATE]
On Thu, 15 Jun 2023, Paul Heinlein wrote: I usually rely on a live CD (or a modern equivalent on a USB stick) to fsck the /boot partition. Paul, I have a Slackware64-15.0 installation on a USB drive. But the desktop's running -14.2. Thanks, Rich
Re: [PLUG] A hardware issue [UPDATE]
On Thu, 15 Jun 2023, Michael Ewan wrote: Most times to repair a system partition, you will need to boot from a USB stick, then run fsck on the damaged partition. You can simply check the condition with 'sudo fsck /dev/sda1'. On my Linux Mint box I was able to umount, fsck, and mount the /boot/efi. In your case it would be sudo umount /boot/efi sudo fsck /dev/sda1 sudo mount /boot/efi Thanks, Michael. I've run fsck on non-boot partitions by unmounting/remounting but not before on the /boot partition. Regards, Rich
Re: [PLUG] A hardware issue [UPDATE]
Most times to repair a system partition, you will need to boot from a USB stick, then run fsck on the damaged partition. You can simply check the condition with 'sudo fsck /dev/sda1'. On my Linux Mint box I was able to umount, fsck, and mount the /boot/efi. In your case it would be sudo umount /boot/efi sudo fsck /dev/sda1 sudo mount /boot/efi On Thu, Jun 15, 2023 at 9:34 AM Rich Shepard wrote: > On Thu, 15 Jun 2023, Rich Shepard wrote: > > > /dev/sda1 is /boot/efi type vfat (rw) > > This is a separate SSD and the /boot partition is the only content. > > Rich >
Re: [PLUG] A hardware issue [UPDATE]
On Thu, 15 Jun 2023, Rich Shepard wrote: /var/log/syslog tells me: Jun 15 05:35:10 salmo kernel: [ 36.853148] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. /dev/sda1 is /boot/efi type vfat (rw) How do I fsck the /boot partition? I doubt this is the underlying problem, and may be a symptom of the deeper issue, but in general ... I usually rely on a live CD (or a modern equivalent on a USB stick) to fsck the /boot partition. -- Paul Heinlein heinl...@madboa.com 45°22'48" N, 122°35'36" W
Re: [PLUG] A hardware issue [UPDATE]
On Thu, 15 Jun 2023, Rich Shepard wrote: /dev/sda1 is /boot/efi type vfat (rw) This is a separate SSD and the /boot partition is the only content. Rich
Re: [PLUG] A hardware issue [UPDATE]
On Thu, 15 Jun 2023, Rich Shepard wrote: The desktop is still turned on but needs rebooting and I need to learn what's wrong so I can fix it. UPDATE: /var/log/syslog tells me: Jun 15 05:35:10 salmo kernel: [ 36.853148] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. /dev/sda1 is /boot/efi type vfat (rw) How do I fsck the /boot partition? Rich
