fsck on non-existent UUID on every boot

I’ve got a problem with XUbuntu 19.04. On every boot, it runs a file system check that times out after 1:30 (killed by systemd) before the boot process continues.

It all started after I installed Debian 10.0 alongside (removed after only one attempt to boot, as it didn’t recognize my video).

The tricky part:

The UUID that it’s trying to check does not exist.

So I can’t simply do a fsck on that drive once it’s finished booting. There is no “trigger file” for “all” file system checks at the root.

I cannot do “tune2fs -l <…>” or “tune2fs -c” on the drive because the drive (the UUID) does not exist.

I already restored the partition to an image from before the issues began – and the file system checks continued. So it seems to be the partitions (why and how and what’s changed?) and not Ubuntu, but… I also have Fedora installed on this computer and it boots without any strange file system checks just fine.

I also tried rebooting into single user mode – the drive’s UUID does not exist there either.

A photo of the file system check: https://imgur.com/BMc76bU

How can I troubleshoot this? Obviously, I’d like the system to stop trying to fsck a non-existent drive.

The root filesystem on /dev/sda3 requires a manual fsck

When I turn on my computer, it sends me directly to the GRUB menu. When I select Ubuntu, it sends me to a black screen. When I select Advanced Options, it sends me to a series of commands where I get an error: enter image description here / dev / sda3: Unexpected Inconsistency; RUN fsck MANUALLY (i.e., without -a or -p options) fsck exited status code 4 The root filesystem on / dev / sda3 requires a manual fsck BusyBox v1.27.2 (Ubuntu 1: 1.27.2-2ubntu3) built-in shell (ash) Enter ‘help’ for a list of built-in commands.

my system ka s asking me for user name when booting. fsck is done. the problem arisen when shutdown was not proper. how do i log in into my computer

I can’t access the terminal or the other resources in system.

Only thing is to press the power button and reach the login window again

Usernames such as HP, root and my name was given in upper and lower case letters

How to force Google Compute Engine ubuntu instance to do fsck?

I have an instance in Google Compute Engine (cloud server) running ubuntu 16.04.

I noticed filesystem corruption on the root filesystem as follows:

==>ls -l data/vocabulary/ ls: cannot access 'data/vocabulary/Makefile': Permission denied ls: cannot access 'data/vocabulary/vocab-count.txt': Permission denied ls: cannot access 'data/vocabulary/vocab-random-access.db': Permission denied ls: cannot access 'data/vocabulary/vocab-list.txt': Permission denied ls: cannot access 'data/vocabulary/vocab.db': Permission denied ls: cannot access 'data/vocabulary/CVS': Permission denied total 0 d????????? ? ? ? ?            ? CVS -????????? ? ? ? ?            ? Makefile -????????? ? ? ? ?            ? vocab-count.txt -????????? ? ? ? ?            ? vocab-list.txt -????????? ? ? ? ?            ? vocab-random-access.db -????????? ? ? ? ?            ? vocab.db 

However, my attempts to “force fsck” and reboot were unsuccessful. I would touch file “/forcefsck” and reboot but fsck just simply would not occur.

I also tried to set the fsck remaining count and that also does not seem to be effective.

What should I do to proceed with fsck?

If file system is dirty, can I safely delete files in .Trashes folder of an external HDD to speed up fsck?

I got a brand new HDD, formatted in exFAT, I was moving folders to it and it happened that something got corrupted when I opened more threads to copy files there.

I know the directory that faulted (it got stucked, maybe for hundred thousands files in it). I tried to remove it (was moved on .Trash folder on mac).

But could not erase files. So I unplugged the HDD, thinking no process was running.

Now:

sudo fsck_exfat -q /dev/disk1s2 

reports file system dirty

sudo fsck_exfat -gd /dev/disk1s2 

I see that it goes through the long list of files listed in the ./Thrashes/

folder of the external HDD

I wonder if I could do:

rm -r ./Thrashes/* 

to remove all files in thrash, and run again fsck to make the process faster.

Or is it better to avoid and let fsck complete, since file system is dirty ?

I also occasionally see lines:

Read      offset = 0x000005200000  length = 0x040000 

Does it mean is an error, or simply an information ?

this is the log I got:

sudo fsck_exfat -gd /dev/disk1s2 Opening /dev/rdisk1s2 (S,"Checking volume.",0) (S,"Checking main boot region.",0) 7813556224 total sectors; 512 bytes per sector FAT starts at sector 32768; size 131072 sectors 15260532 clusters starting at sector 163840; 262144 bytes per cluster Root directory starts at cluster 11 Read      offset = 0x000001000000  length = 0x001000 (S,"Checking system files.",0) Read      offset = 0x000005240000  length = 0x040000 (S,"Volume name is %1$  @.",1) luigi4T Found active bitmap; first cluster 2, length 1907567 (S,"Checking upper case translation table.",0) Read      offset = 0x000005200000  length = 0x040000 Found upcase table; starting cluster 10, length 5836 (S,"Checking file system hierarchy.",0) Directory / File      /._.Trashes Directory /.Trashes Directory /.fseventsd Directory /.Spotlight-V100 Directory /.TemporaryItems Directory /20190318 BackUp File      /.com.apple.timemachine.donotpresent File      /._.com.apple.timemachine.donotpresent File      /._.TemporaryItems File      /.apdisk File      /._.apdisk Read      offset = 0x000005280000  length = 0x040000 Directory /.Trashes/501 File      /.Trashes/._501 Read      offset = 0x000005300000  length = 0x040000 File      /.fseventsd/fseventsd-uuid File      /.fseventsd/0000000002073ca7 File      /.fseventsd/0000000002089d5c ... # files I'd like to remove from Thrashes folder, *before* running a files system check again ... File      /.Trashes/501/WatchDiscovery 10.01.36 AM/backup Jan 21, 2012/Posters_cleaned/mm2219_9_Assassinio_per_cause_naturali.jpg File      /.Trashes/501/WatchDiscovery 10.01.36 AM/backup Jan 21, 2012/Posters_cleaned/mm2219_imm_Assassinio_per_cause_naturali.jpg File      /.Trashes/501/WatchDiscovery 10.01.36 AM/backup Jan 21, 2012/Posters_cleaned/mm221_0_Accordi_sul_palcoscenico.jpg File      /.Trashes/501/WatchDiscovery 10.01.36 AM/backup Jan 21, 2012/Posters_cleaned/mm221_10_Accordi_sul_palcoscenico.jpg File      /.Trashes/501/WatchDiscovery 10.01.36 AM/backup Jan 21, 2012/Posters_cleaned/mm221_1_Accordi_sul_palcoscenico.jpg File      /.Trashes/501/WatchDiscovery 10.01.36 AM/backup Jan 21, 2012/Posters_cleaned/mm221_2_Accordi_sul_palcoscenico.jpg File      /.Trashes/501/WatchDiscovery 10.01.36 AM/backup Jan 21, 2012/Posters_cleaned/mm221_3_Accordi_sul_palcoscenico.jpg File      /.Trashes/501/WatchDiscovery 10.01.36 AM/backup Jan 21, 2012/Posters_cleaned/mm221_4_Accordi_sul_palcoscenico.jpg 

…. ….


If matters, mac OS version 1.9.5

File system error on external hard drive and ntfsfix, fsck and chkdsk are of no use, what now?

I messed up the file system of my external hard drive somehow (most likely through the Boot-repair live usb in an attempt to reinstall GRUB after a Windows reinstall). Ntfsfix, fsck and chkdsk are all of no use, here are the error messages they displayed:

ntfsfix:

Mounting volume... ntfs_mst_post_read_fixup_warn: magic: 0x24738cd6  size: 1024   usa_ofs: 8316  usa_count: 45321: Invalid argument Record 0 has no FILE magic (0x24738cd6) Failed to load $  MFT: Input/output error FAILED Attempting to correct errors... ntfs_mst_post_read_fixup_warn: magic: 0x24738cd6  size: 1024   usa_ofs: 8316  usa_count: 45321: Invalid argument Record 0 has no FILE magic (0x24738cd6) Failed to load $  MFT: Input/output error FAILED Failed to startup volume: Input/output error Checking for self-located MFT segment... ntfs_mst_post_read_fixup_warn: magic: 0x24738cd6  size: 1024   usa_ofs: 8316  usa_count: 45321: Invalid argument OK Unrecoverable error Volume is corrupt. You should run chkdsk. 

fsck:

% sudo fsck /dev/sdb1  fsck from util-linux 2.32 e2fsck 1.44.4 (18-Aug-2018) ext2fs_open2: Bad magic number in super-block fsck.ext2: Superblock invalid, trying backup blocks... fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb1  The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem.  If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:     e2fsck -b 8193 <device>  or     e2fsck -b 32768 <device>  Found a atari partition table in /dev/sdb1 

chkdsk:

View post on imgur.com

What shall I do now to get the data back? If it’s testdisk, how exactly can I use it?

Every startup i need to manually run fsck /dev/mapper/ubuntu–vg-root

Hi every day when I start my ubuntu 18.04, then it’s not starting and gives a below error.

(initramfs) exit /dev/mapper/ubuntu--vg-root contains a file system with errors, check forced. Inodes that were part of a corrupted orphan linked list found.  /dev/mapper/ubuntu-vg-root: UNEXPECTED INCONSISTENCY; Run fsck MANUALLY.     (i.e., without -a or -p options)  fsck exited with status code 4. The root file system on /dev/mapper/ubuntu--vg-root requires manual fsck 

When I run command fsck /dev/mapper/ubuntu--vg-root

it solves error but again the next day when I start up my system it shows same error again and needs to run the command again.