Questions[disk-check](ubuntu)

When using the ISO for Ubuntu 20.04, checking the SHA256SUM (from here - https://releases.ubuntu.com/20.04/SHA256SUMS), and creating a bootable USB, the following message appears briefly at the end of the media check during boot.

Check finished: errors found in 1 files! You might encounter errors.

I tried creating the bootable USB with 3 different thumbdrives (2 different brands), and using either the Startup Disk Creator or Disks and the error does not go away.

Could the ISO be corrupted ? (and the checksum be calculated on the corrupted iso).

edit: a comment requested further clarification on that latest part - The check during boot appears to be checking individual files (in the ISO) while the checksum verfied after downloading (and prior to creating the bootable USB) is for the ISO. The creation of the ISO and the calculation of its digest, and the check mechanisms for individual files in the ISO can be distinct processes, which would allow the creation of a corrupted ISO if being built from at least one corrupted subpart (file).

Yesterday I got a pop up on my Ubuntu installation running 19.10 saying that 20.04 is available. I figure I'd give the upgrade a try, hoping it wouldn't take too long. The upgrade completed, and my computer restarted, at which point a filesystem check seems to have started. I let it run overnight, and at this point it's been going for around 12 hours.

At some point I tried cancelling it because it said "Press ctrl+c to cancel all file system checks in progress" on the screen. However after unplugging my external monitor I just see a spinner, the Lenovo logo and a Ubuntu logo.

My question: do these checks usually take this long? is it safe to try and stop it? I'm dual booting with Windows 10 if that makes a difference.

I had some bad blocks within my hard drive lately but I was able to repair them . I'm trying to install Ubuntu on my Hard drive ( which is empty ) but I don't get the Grub Interface thing , it automatically runs ' check disk for defects ' . How can I prevent this program to start at startup ?

I encounter a problem on booting process. It seems like a disk checking, cleaning etc., but on every boot is just too annoying.

Here is the image I shot at the booting process:

I remember yesterday I did something to Ubuntu with the purpose to repair wake up problem after suspend (though unsuccessful), what I did is:

In a terminal run sudoedit /etc/pm/sleep.d/fglrx-fix and paste in the following script. Afterwards make it executable by running sudo chmod u+x /etc/pm/sleep.d/fglrx-fix

Script:

#!/bin/bash
#Script kills autofs when going into standby to eliminate issues with it
case $1 in

suspend)
#suspending to RAM
    chvt 1
    echo "Going to sleep"
    sleep 1
;;
resume)
#resume from suspend 
    echo "try to resume"
    sleep 1
    chvt 7
;;       
esac    

After that I tested suspend Ubuntu but Ubuntu failed to wake up. Then I wanted to make the above file not executable by using chmod -R -x /etc/pm/sleep.d/fglrx-fix, but I was told I don't have permission to do it. Then I cut off all the text in the above file and saved.

That is what I did. How should I do now so that it won't check the disk every time the system boots. It is really very annoying. Thanks a lot for your help.

PS: 1. Should I delete the file fglrx-fix? If yes, how? 2. I forget to say that the checking time is about 1 min. , not a very long time, but still strange and annoying. 3. Should I stop force check?

PS2: 21.11.2015 removed the file fglrx-fix, but the problem is still there. Pls help!

PS3: I searched the file fsck, this is the result:

When I try to do a ntfsck to a NTFS partition I get this:

sudo ntfsck /dev/sdb1
Unsupported: replay_log()
Volume is dirty.
Unsupported: check_volume()
Checking 161792 MFT records.
Unsupported cases found.

How can I clean a "dirty" NTFS volume without having to actually use windows chkdsk tool in the NTFS volume.

I also did a ntfsfix and it said that everything was OK but it actually was not.

I also get the same "Dirty" error when trying to check the filesystem using the Disk Utility:

I am starting to think I need some powerful soap.