![]() Nov 10 07:48:14 localhost.localdomain systemd-fsck: Pass 3: Checking directory connectivity Nov 10 07:48:14 localhost.localdomain systemd-fsck: Pass 2: Checking directory structure Nov 10 07:48:14 localhost.localdomain systemd-fsck: Root inode is not a directory. Nov 10 07:48:14 localhost.localdomain systemd-fsck: Pass 1: Checking inodes, blocks, and sizes Nov 10 07:48:14 localhost.localdomain systemd-fsck: Resize inode not valid. Nov 10 07:48:14 localhost.localdomain systemd-fsck: *** ext3 journal has been deleted - filesystem is now ext2 only *** ![]() Nov 10 07:48:14 localhost.localdomain systemd-fsck: Clear? yes Nov 10 07:48:14 localhost.localdomain systemd-fsck: Superblock has an invalid journal (inode 8). Consequently, we can observe how the repair process is carried out in the service logs: $ journalctl -u 10 07:48:14 localhost.localdomain systemd: Starting File System Check on /dev/sdb1. Occasionally, file system errors may occur. Nov 10 07:36:45 ubuntu-xenial systemd: Started File System Check on /dev/sdb1. For example, as a test case, we’ll have a service named corresponding to the mount point /dev/sdb1: $ journalctl -u 10 07:36:45 ubuntu-xenial systemd: Starting File System Check on /dev/sdb1. For the non-root filesystems, systemd will create a service for each file system according to the mount name defined in /etc/fstab.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |