Please do not cargo-cult stuff you found on the Internet, but try to understand what a command does before your enter it.
Your use of
sudo is unnecessary -- you are already logged in as the root user, and have full access.
The error message you were given indicates that the automatic file system check failed. With ext2, that happened often after a power outage, but with ext3 and ext4, one of which you are likely to be using if your system is newer than ten years, this generally does not happen unless there is faulty hardware involved.
The first command,
mount -o rw,remount / essentially tells the system "It is fine, there are no errors on this disk, and you can assume the file system to be consistent enough to write files." This is a bold statement, especially right after you received an error message stating that a file system check found problems that are so bad that the automated repairs would probably have to delete files in order to get the file system back into working shape.
The second command,
dpkg --configure -a then attempted to run the post-installation scripts for packages that are marked in the dpkg database as having their files unpacked, but the scripts not run yet. If this command attempted to do anything, this means that you will need to do that later on, but now is not the proper time. The dpkg tool exists all file systems to be mounted and error-free, you only have a root file system with errors, and all others are missing.
The way to resolve your situation is:
Go back to read-only mode using
mount -o ro,remount /. You do not want the kernel to change anything in the file system while the repair is under way.
Repair the root file system, using the fsck utility, which will then use the fsck.ext3 utility internally:
fsck -f /.
You can add the option
-C0 to get a progress indicator.
If you get messages about fsck being unable to read blocks because of I/O errors, you can interrupt with Ctrl-C and add the
-c option to scan for bad blocks beforehand. This will take ages, but the repair operation then does not attempt to rescue any files spread over defective sectors.
Most likely you will be asked if you agree to certain problems being fixed. Look up the error messages using your search engine of choice, there is ample documentation on the Internet. Most of these are about deleting files that are beyond repair, or moving them to the
After that is complete, you will most likely be asked to reboot, in capital letters. This is a good idea, just enter
sync first, give the disks a few seconds to write out the remaining data and then press Ctrl-Alt-Del. The reboot will be immediate, without unmounting file systems, but that is fine because the only file system mounted is read-only.
If after the reboot you are dropped back into the same prompt, another file system but the root file system is in need of repairs as well. Use the
fsck -A command to attempt an automated repair of all non-root file systems, and manually repair those that need it. This time around, you should not be asked to reboot, as this is only needed for file systems that are mounted while being checked.
So in fact I must have broken the installation process.
From within a chroot, I run
dpkg --configure -a as asked by
apt and I was finally able to boot after a reboot.
Everything seems fine at first sight but I think I am good for a complete reinstall nonetheless.
So this leads to the originial problem. Why couldn't I login after I started the upgrade process ??? This is why I rebooted inthe first place.
Nautilus bookmark settings
To manage bookmarks go to the Files menu in the panel to open the Bookmarks dialog. There we may enter a name and a path of a bookmark to appear in the Nautilus left side panel in the Bookmarks section:
Bookmark an opened directory
Alternatively open the directory you want to bookmark. Then click on the cogwheel top right to select "Bookmark this Location" or press Ctrl + D.
To remove a bookmark select "Remove"" from the right click context menu on the bookmark.
All our bookmarks will also be displayed as a quicklist:
Manual approach and removing default entries
Those bookmarks are stored in an editable file in
.config/gtk-3.0/bookmarkswhere we may manually (or programmatically) add and remove path entries which take effect immediately. The examples above resulted in the following file content: