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] Sluggish response
No look for reallocated sector count or some such. The disk is supposed to say how many it's done and how many are left. There's a screenshot on a windows SMART program that shows it graphically: https://crystalmark.info/en/software/crystaldiskinfo/ Some info may be here https://www.smartmontools.org/wiki/BadBlockHowto One problem with smart disks these days is that many of them will do a read/write "scrub" on a failing sector dozens of times in an effort to "heal" it. Borrowing from the spinwrite marketing baloney from years past. If there's a series of bad sectors in a row the disk can take 30 minutes or more doing this before finally deciding to do an internal permanent re-map of the bad sectors or just failing entirely, whichever comes first. So you go to write a file and the machine takes forever because underneath it all the disk is hammering itself to death in a Hail Mary to save your data. SMART attributes appear to be vendor-defined so they are not all common in between disks. The disks also sometimes lie in saying how many reallocated sectors they have. Disks also love to lie like dogs on how many blocks and sectors and such they have. So the idea of a low level edit is out of the question. Some disks marketed to those cheap little NAS devices are labeled red and those will just error out on a sector fail for the bad sector. Most disks will NOT reallocate a bad sector unless you try writing to it. This can be a problem with filesystems that write to a sector by reading it first then writing it. If you suspect a disk, doing a dd if=/dev/zero of=/dev/disk0 or whatever your device is, over the entire disk, will sometimes force remaps on any bad sectors and the disks will return to normal speed. Ted -Original Message- From: PLUG On Behalf Of Dick Steffens Sent: Thursday, June 15, 2023 11:43 AM To: plug@pdxlinux.org Subject: Re: [PLUG] Sluggish response On 6/14/23 07:43, Tomas Kuchta wrote: > On Wed, Jun 14, 2023, 01:41 Ted Mittelstaedt wrote: > >> If it is a magnetic media drive that is older the drive could be >> suffering end stage sector failure where the bad sector table is >> filled up. I've seen it many times and it always makes the drive get >> very slow >> >> Ted. >> > Bad sectors should be evident in Smart tools. It might be good idea to > check it to prove/dis-proof disk issues. > > -T > rsteff@ENU-1:~$ sudo smartctl -H /dev/sdb smartctl 7.1 2019-12-30 > r5022 [x86_64-linux-5.4.0-150-generic] (local > build) > Copyright (C) 2002-19, Bruce Allen, Christian Franke, > www.smartmontools.org > > === START OF READ SMART DATA SECTION === SMART overall-health > self-assessment test result: PASSED I've run a few other smartctl options. I don't really know what I should specifically be looking for. One of the results said > Offline data collection status: (0x00) Offline data collection > activity > was never started. > Auto Offline Data Collection: Disabled. > Self-test execution status: ( 0) The previous self-test > routine completed > without error or no self-test has ever > been run. Is there something I should be running? -- Regards, Dick Steffens
Re: [PLUG] RESOLVED: VirtualBox export/import help needed -- Correction
I've been calling the virtual machine VMware. What I use is VirtualBox. Not sure if it really matters, but ... On 6/15/23 14:28, Dick Steffens wrote: On 6/15/23 14:16, Dick Steffens wrote: As part of solving my sluggish machine issue, I'm working on setting up my alternate desktop machine. I have installed VMware on it, and copied some .ova files. However, VMware doesn't like .ova files. It says it wants .ovf. On my other machine I try to export .ovf, but that doesn't seem to be available, only .ova. How can I get the import appliance to recognize the .ova file? Never mind. Most of the instructions I found don't mention double-clicking on the .ova file as a way to start the import process. That works. Sigh. I'll be sure to add this to my install log for the next time. -- Regards, Dick Steffens
[PLUG] RESOLVED: VirtualBox export/import help needed
On 6/15/23 14:16, Dick Steffens wrote: As part of solving my sluggish machine issue, I'm working on setting up my alternate desktop machine. I have installed VMware on it, and copied some .ova files. However, VMware doesn't like .ova files. It says it wants .ovf. On my other machine I try to export .ovf, but that doesn't seem to be available, only .ova. How can I get the import appliance to recognize the .ova file? Never mind. Most of the instructions I found don't mention double-clicking on the .ova file as a way to start the import process. That works. Sigh. I'll be sure to add this to my install log for the next time. -- Regards, Dick Steffens
[PLUG] VirtualBox export/import help needed
As part of solving my sluggish machine issue, I'm working on setting up my alternate desktop machine. I have installed VMware on it, and copied some .ova files. However, VMware doesn't like .ova files. It says it wants .ovf. On my other machine I try to export .ovf, but that doesn't seem to be available, only .ova. How can I get the import appliance to recognize the .ova file? -- Regards, Dick Steffens
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] Sluggish response
On 6/14/23 07:43, Tomas Kuchta wrote: On Wed, Jun 14, 2023, 01:41 Ted Mittelstaedt wrote: If it is a magnetic media drive that is older the drive could be suffering end stage sector failure where the bad sector table is filled up. I've seen it many times and it always makes the drive get very slow Ted. Bad sectors should be evident in Smart tools. It might be good idea to check it to prove/dis-proof disk issues. -T rsteff@ENU-1:~$ sudo smartctl -H /dev/sdb smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.0-150-generic] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED I've run a few other smartctl options. I don't really know what I should specifically be looking for. One of the results said Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Is there something I should be running? -- Regards, Dick Steffens
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
[PLUG] A hardware issue
Yesterday and today when I tried to log in my desktop server/workstation I couldn't: the monitor had no input from the desktop. Shutting down the computer and immediately starting it brought up the startup process and the system worked fine all day yesterday. Today's logs showed that the backups (run starting at 00:30) all successfully completed, but the rest of root's cron jobs (from 01:00 through 03:45) didn't. With the various hardware I've used running linux since 1997, and up 24/7, this has not before happened. I've no idea why the computer stops processing some time after the backups (the last started at 00:35) and 01:00. The desktop is still turned on but needs rebooting and I need to learn what's wrong so I can fix it. Help, please. Rich
