File System Check software?

[GregM]

Busybox came up this morning and after searching around on the net I found the commands for fixing the problem (I think).
I am wondering if there is some software that I can run once in a while that can check out my drive and fix/correct any problems that might be brewing.

Is there some thing like Gparted that I can run and have it check everything?

What is recommended?

Thanks
Greg

[Snowhog]

Busybox came up this morning and after searching around on the net I found the commands for fixing the problem (I think).

What was the problem, and what commands did you find/run that ‘fixed’ the ‘problem’?

[GregM]

I ran fsck /dev/sda3 -y
and was able to boot after that.

[claydoh]

Gparted, or KDE Partition Manager can do this (via fsck, actually)
The problem can be doing so on a running mounted file system. You can use a live USB to do this, in this case, as the computer's drives can be unmounted if necessary.


You can also use the recovery menu to run an fsck, it is an option in its menu.
This IIRC may mount it in read-only mode, which at least can show problems. I has been a while since I used recovery mode for this.

[GregM]

When I try to run KDE Partition Manager it starts, but just there and hangs up?

[claydoh]

Check that the password box isn't hidden under the main window. I see that happen a lot.
Or if it is misbehaving for some reason, just use Gparted, I believe it will have the same option for this, though it will likely be in a different spot.

[GregM]

It was behind the KDE Partition Manager.

[oshunluvr]

I believe if you have the partition in question set to do a filesystem check in fstab, you can set an interval using tune2fs:

sudo tune2fs -c 10 /dev/sda1

-c being the count so in this example every 10th boot would run fsck. A value of -1 would mean no automatic fsck. so this turns it off:

sudo tune2fs -c -1 /dev/sda1


Setting the file system check marker in fstab is the last number in the fstab line:

UUID=<UUID HERE> / ext4 default,auto 0 1

The default is 1 for / and 2 for /home

The numbers reflect the order is which fsck is run. 0 meaning "never."

From the fstab manpage:

The sixth field (fs_passno).
This field is used by the fsck(8) program to determine the order
in which filesystem checks are done at reboot time. The root
filesystem should be specified with a fs_passno of 1, and other
filesystems should have a fs_passno of 2. Filesystems within a
drive will be checked sequentially, but filesystems on different
drives will be checked at the same time to utilize parallelism
available in the hardware. If the sixth field is not present or
zero, a value of zero is returned and fsck will assume that the
filesystem does not need to be checked.

All this only for EXT filesystems

[oshunluvr]

Another option would be to write a script and set it as a cronjob like weekly or monthly

[GregM]

Looks like I did it (I think)
Downloaded 22.04.2 and after a bit of reading I burned it to a USB drive.
Booted off the USB drive and started KDE Partition Manager.
Had it check my main drive and it zipped right through it checked it and said everything is fine. Whether or not it actually did anything I do not know. It ran pretty quick.

I'm going to save the install on the USB drive in case I need to do this again.

Thanks Boys.

[claydoh]

I'm going to save the install on the USB drive in case I need to do this again.

Good idea I have one on a usb key on my keychain

[vanadiumboy]

I once used this command

sudo badblocks -nvs /dev/sdb (The n means non-destructive mode)
^^^^^This would check the drive "sdb" in non-destructive read–write mode and display progress by writing out the block numbers as they are checked.
It displays progress by writing out the block numbers as they are checked (-s = show, -v = verbose).

There is also Smartmontools
You can install on Kubuntu by opening Discover and search for Smartmontools

Example:
sudo smartctl -a /dev/sda
lists various information.

[GregM]

Thank you
I'll check it out.

[GregM]

Also
I had to figure out about making a USB bootable drive and finally found this article and followed it.
I used a 8gb "thumb drive".

https://ubuntu.com/tutorials/create-...ntu#1-overview

[jlittle]

...making a USB bootable drive ...tutorial...

That's an old approach. Using Ventoy is much simpler after you've got it set up, and, space permitting, you can have several isos on the same drive. Also, it's handy on a key chain because one can use the USB for other purposes, like storing files, space permitting.