Ubuntu 20.04 LTS has started to corrupt file systems on 3 different computers
 

These problems probably started within the last 2-3 weeks. They started off gently at first. The happen on Ubuntu 20.04 LTS.

I noticed fetcher errors where Yocto Bitbake downloads files and does a checksum comparison. I was seeing intermittent failures. The checksums didn't match. A second attempt would succeed.

Then I started seeing unexpected EOFs in C++ source files during compiles.

Then, when I open new terminal windows, the window opens but no shell appears to be running.

Then Ubuntu fails to shut down.

Then I got errors from rm -rf saying that I didn't have permissions to delete a subfolder. I did have permissions.

ls -l on the offending folder returned ': bad message'.

In the end I reformatted the disk.

I tried on another machine. A fresh install of Ubuntu over a Windows box. Same errors.

I tried crops on a Windows laptop. Same story.

Is anyone else having similar problems with the latest Ubuntu 20.04 LTS?

Don't run Ubuntu myself. Maybe next time comment out some sources lists when doing a upgrade and then maybe later check /var logs for error messages.

On my distro upgrade warns me if a server is offline and how long before it comes online again.

I don't do windows anymore either. Used to tune motorcycles with it but expenses would give the customer a heart attack. So I quit doing it.

Almost sounds like a hard drive failing. Or a corrupt ppa.

Might wanna post

while in ubuntu to give better details on your problem.
if nothing comes from that command. Look for it in synaptic or

This isn't an Ubuntu issue, it's a file system issue, but you did not give any information about the file system. Given 3 different systems, that points to really only 2 possible issues:

1. a corrupted ubuntu installation iso. Did you run the md5 hash test on the downloaded ubuntu installer?

2. you used btrfs, though even it is unlikely to fail on 3 different systems at the same time.

If you used a stable safe file system like ext4, then you can largely exclude the file system from suspicion.

Unfortunately if this was really on 3 different physical computers, you can also largely exclude RAM or Drive corruption, since the odds are just not in favor of such a conclusion, unless you don't have them attached to a UPS+surge protector and you had an electrical or weather/lightning event at that time.

You have to supply more information, ubuntu is just a set of packages with a kernel, it's the kernel / file system that will corrupt, so looking at ubuntu is a red herring.

Provide inxi -Faz

so we can see what you are doing, and so that actually relevant information is available for people who might be able to help you.

There's another possibility, since you seem to be trying the same tool on all systems, which is that the tool has a massive bug in it, any tool that can corrupt your file system even in theory should be dropped immediately until you determine the true cause of this event.

There's really no bigger bug or issue than file system corruption, and if it is in fact that tool, you neeed to post an issue report on their support/bug tracker right away, but you MUST supply real data, like inxi -Faz, or else nobody can help you.