03-28-2014
The system at reboot will have done so (fsck that is ) ... If you have looked at the syslogs, you may have seen messages about abrupt shutdown and so expected flags on the filesystems arent so the system will do an fsck...
A quick check would be to look if you have anything in the lost+found directories of each filesystem, nothing = you are OK
That said UPS are cheap now and if you are runing servers, its far from being silly to invest in such device...
This User Gave Thanks to vbe For This Post:
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi, dear Experts !
I need some help, again.
Earlier in my work I experienced that one script included in '/etc/dt/config/Xstartup' file caused some serious troubles. But this is another story.
The point here is: I changed the script so that it worked again.
But... After restart of... (3 Replies)
Discussion started by: DGoubine
3 Replies
2. UNIX for Dummies Questions & Answers
How do I configure my workstation (Solaris 9) to restart and perform any check disk automatically if there is a power failure?
Thanks. (1 Reply)
Discussion started by: here2learn
1 Replies
3. Solaris
Hi all,
I have a server SUN FUJITSU in solaris 10 ; result of uname -a is :
SunOS MOBD1 5.10 Generic_118833-03 sun4us sparc FJSV,GPUZC-M
I have configured the eeprom to auto-boot as usual and this automatic reboot does not work in case of power failure. I must type "boot" on the prompt "ok"... (5 Replies)
Discussion started by: aribault
5 Replies
4. Shell Programming and Scripting
hi,
I have 100 files say File1.mp3, File2.mp3 .......file100.mp3
i found that File1.mp3 to File50.mp3 are damaged.
I want to delete the damaged files from the directory using sed with regex how can i do this.
thanks (5 Replies)
Discussion started by: pchangba
5 Replies
5. SCO
After System power get failed
File system is not getting mounted in read- write mode (1 Reply)
Discussion started by: gtkpmbpl
1 Replies
6. UNIX for Dummies Questions & Answers
hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless. (11 Replies)
Discussion started by: fredthayer
11 Replies
7. Solaris
SUNW, Sun Fire V240 Spare
Sun OS Release 5.9
After a power failure
we try to start the server
We have the following messages:
Thanks for your assistance (7 Replies)
Discussion started by: doudou2012
7 Replies
8. Shell Programming and Scripting
I want to transfer all details of sftp connection into a log file and spawn sftp $PCMSu@$FTP_LOC >> log_file is not working for me. Please suggest how to send the data to a log file that has all information if sftp connection is successful or not?
Script that I am using:
#!/usr/bin/expect... (7 Replies)
Discussion started by: Geeta Yadav
7 Replies
LEARN ABOUT XFREE86
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)