Hey all,
My attempts to get my system working are progressing well, but I've got a couple of questions I need to finish the job.
I decided to make this a new thread that I hope can help me understand the system issues and what to do the next time.
The previous posters helped me get this far and I am grateful for everyone's help.
Hopefully, I can get this issue fixed and what to do the next time.
It will help me to better understand how my system works and to make it better.
What does "FILE SYSTEM WAS MODIFIED" mean in my situation and how do I get it taken care of?
Code:
Deleted inode 35409210 has zero dtime. Fix<y>? yes
Pass 1E: Optimizing extent trees
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda5: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda5: 259707/39043072 files (1.5% non-contiguous), 7676803/156151296 blocks
Is there a way to find out how the file system was modified and what it means?
don't know much - it might be good to know more.[/code]
Sorry about the underline. I tried to get rid of it using the options shown, but that didn't work. [/code]
This is what the fsck showed initially.
Fsck found some issues with my system. It also looks like most of them were fixed.
Thanks
https://ubuntuforums.org/showthread.php?t=2464806
My system is an AMD 9850
650 HDD - with one 650GB HDD partition
And another partition with 535.8 MB
The Disks & Storage test. It shows The HDD partition 15.7 GB is being used (With some contents unreadable)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Code:
I did the first fsck with a mounted partition. I did not realize that the partition was supposed to be unmounted. After I unmounted the partition, I did the recommended fsck, this what it returned this information:
this is a mouse the kept freezing, then releasing, etc. but then locked up to the point of having to reboot to make it work. This problem led me to attempt a fix using FSCK. But I didn't read the part where I was supposed to do this from root w/o mounted file systems. I tried that twice and it then came back with "error code 2."
I tried to run fsck again, but then the system came back with the BusyBox v1.30.1 Initramfs errors. I read as much as I could on how to proceed, but didn't see any solution that I thought fit my situation.
Finally, I rebooted with the 20.04 live disk and to "Try Ubuntu" That brought up 2 partitions - one empty and the other with the file systems I had been using.
I checked on my documents - which seemed OK, but I'm not sure I still had all of them.
I don't recall exactly what I did then, but there was a banner showing
Circle X Access with sys/device/software/subsystem/uevent denied
I hit OK and the banner closed
In the second partition (supposedly empty) There was a file labeled
"Ubiquity Desktop"name:~desktop/ubiquity.desktop
2[read only] /run/network manager/devices
Code:
Failed to start shuts down pre-installed sys cleanly
SystemCTL i status Casper.service for detail
OK Reached Target Final step/finished powered-off
OK Finished reached target power off
[!!!!!!] Failed Execute shutdown binary [40985.213694] blk_update_request] I/O Error
Earlier today the screen was frozen and I did a soft reboot and got
Begin: running/scripts/local-premount ... done
Begin: Will now check root file system ... fsck from util-linux 2.34 [/usr/sbin/fsck.ext4 (1) --/dev/sda5] fsck,ext4 -a -C0 /dev/sda5 /dev/sda5 contains a file system with errors, check forced
[ 10.326632] random: crng init done ==== \54.4% /dev/sda5:
Inode 35401772 extent tree (at level 1) could be shorter. IGNORED. /dev/sda5: Inodeds that were part of a corrupted orphan linked list found.
/dev/sda5: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY (I.E., WITHOUT -A OR -P OPTIONS
fsck exited with status code 4 done.
FAILURE: file system check of the root filesystem failed
the root filesystem on /dev/sda5 requires a manual fsck
Code:
$ sudo fsck /dev/sda5
fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-2020)
/dev/sda5 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Inode 35401772 extent tree (at level 1) could be shorter. Optimize<y>? yes
Inodes that were part of a corrupted orphan linked list found. Fix<y>? yes
The worrisome item is:
dev/sda5: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda5: 259707/39043072 files (1.5% non-contiguous), 7676803/156151296 blocks
Bookmarks