I speak from experience on this one: run fsck on an unmounted root partition. You must boot the system from a cdrom (or dvd) with:
and then run fsck.
If you run fsck on a mounted root partition you WILL corrupt it beyond repair. Your only option will be to reinstall the OS or try a restore from a backup.
Once in a while, I would think it advisable to run fsck -y to check the disk.
Should I sign in as su or sudo?
What is the difference and which is preferred?
Thank you in Advance! (4 Replies)
If a file is compressed, how can i uncompress on the fly using pipes(handling this in the shell script depending on the command line arguments passed to the script)
ex: ex_pr.sh -d disable -f ex_pr_1212.log.Z (6 Replies)
OS: Solaris 5.8
Everytime I run fsck -y I get: FILE SYSTEM STATE IN SUPERBLOCK IS WRONG; FIX? yes
Do I need to run fsck with the backup superblock option or is there
some other option I should use. I have tried the format->analyze->read
option but that does not report any corrupt blocks.... (5 Replies)
I want to use fsck to check and repair my linux system. When I use this command, what do I need to pay attention to or what should I do to make job running successfully. Thanks for your inputs for a newbie. (3 Replies)
i have couple of my assignment questions
What command results in adding today's date and time to the file yesterday.txt
What command results in creation of a new file named yesterday.txt that contains yesterday's date but no time (3 Replies)
Hello...
Im trying to use "- " as field separator...
I used awk -F"- " '{print $3}' input_file ... but it's not working, it assumes that the field separator is "-" and not "- " ...
Any ideas ?? :(
Thanks (6 Replies)
i want to know what does it mean by doing a consistentcy check fsck on a disk and why journaling filesystems dont need to do it
and what is meant by disk is in a consistent state when writing because entries are recorded in a journal and then to the metadata and then removed from journal (1 Reply)
What can I fix this issue? I have ran below commands but everything is same.:confused:
WARNING: Last shutdown is later than time on time-of-day chip: check date.
The / file system (/dev/rdsk/c1t0d0s0) is being checked
WARNING - unable to repair the / filesystem. Run fsck manually (fsck -F... (4 Replies)
hello guys!! need 1 favour from u all..
Can u jst tell me the answers for these ques??
1. ls - l _____ : command to return all files that end with single digit and those with TXT extension
2. ls -l report* _______ : command to return all files that start with the word RPT except those with LOG... (1 Reply)
Discussion started by: Gan_7
1 Replies
LEARN ABOUT POSIX
systemd-fsck
SYSTEMD-FSCK@.SERVICE(8) systemd-fsck@.service SYSTEMD-FSCK@.SERVICE(8)NAME
systemd-fsck@.service, systemd-fsck-root.service, systemd-fsck - File system checker logic
SYNOPSIS
systemd-fsck@.service
systemd-fsck-root.service
/lib/systemd/systemd-fsck
DESCRIPTION
systemd-fsck@.service and systemd-fsck-root.service are services responsible for file system checks. They are instantiated for each device
that is configured for file system checking. systemd-fsck-root.service is responsible for file system checks on the root file system, but
only if the root filesystem was not checked in the initramfs. systemd-fsck@.service is used for all other file systems and for the root
file system in the initramfs.
These services are started at boot if passno in /etc/fstab for the file system is set to a value greater than zero. The file system check
for root is performed before the other file systems. Other file systems may be checked in parallel, except when they are on the same
rotating disk.
systemd-fsck does not know any details about specific filesystems, and simply executes file system checkers specific to each filesystem
type (/sbin/fsck.*). This helper will decide if the filesystem should actually be checked based on the time since last check, number of
mounts, unclean unmount, etc.
If a file system check fails for a service without nofail, emergency mode is activated, by isolating to emergency.target.
KERNEL COMMAND LINE
systemd-fsck understands these kernel command line parameters:
fsck.mode=
One of "auto", "force", "skip". Controls the mode of operation. The default is "auto", and ensures that file system checks are done
when the file system checker deems them necessary. "force" unconditionally results in full file system checks. "skip" skips any file
system checks.
fsck.repair=
One of "preen", "yes", "no". Controls the mode of operation. The default is "preen", and will automatically repair problems that can be
safely fixed. "yes" will answer yes to all questions by fsck and "no" will answer no to all questions.
SEE ALSO systemd(1), fsck(8), systemd-quotacheck.service(8), fsck.btrfs(8), fsck.cramfs(8), fsck.ext4(8), fsck.fat(8), fsck.hfsplus(8),
fsck.minix(8), fsck.ntfs(8), fsck.xfs(8)systemd 237 SYSTEMD-FSCK@.SERVICE(8)