Sorry for bad english.
How to set systemd for automatically force fsck disks after crash (hard poweroff)?
When I used sysvinit (in Arch Linux) as /sbin/init I used the hack: in the rc.local I create /forcefsck file; in the rc.local.shutdown I remove it. At boot-up rc.sysinit enable force fsck if /forcefsck exists.
How to do same in systemd?
Possible Duplicate:
How do you get e2fsck to show progress information?
Is there a way to check the progress of fsck.ext3 under Ubuntu, if I'm logged in remotely?
Obviously the time taken depends on a lot of factors, but if fsck has to option of displaying a progress bar, it should be possible
EDIT:
Seems I didn't make the question clear enough.
I have a headless Ubuntu 12.04 server in a datacenter 1500 miles away. Twice now on reboot the system decided it had to fsck. Unfortunately Ubuntu ran fsck in interactive mode, so I had to ask someone at my datacenter to go over, plug in a console, and press the Y key.
From time to time it happens that I have a power failure and my computer shuts down uncleanly. Every time it happens, though, the next boot drops me into an emergency shell and tells me to run fsck manually.
This has happened more than once, and each time the system boots fine after running fsck. When I used Ubuntu I never had to run it manually.
Hi,
After some difficulties accessing to my NAS network in writing mode (1 TO, bought one year ago), I launched a fsck -yvf; now gparted tells me it gots no partition ...
I made a tesdisk /dev/sdb1> Proceed> Intel> Analyze> Quick search> Yes
After several hours the partition was not found.
Hi,
On 10.04.4 LTS.
My backup server was improperly shut down due to power failure. However, at that time, backups were turned off.
When turned back on, an automatic fsck was launched on a disk (first one since creation, ~300 days ago).
Hello,
I'm new to this forum. I have a Fedora server that acts as mail server.
Today morning i've found that the file system was in readonly mode, the hard disk was full at 27%... so I've rebooted it to run fsck to check filesystem integrity but... The server wont reboot. Now the server cannot boot, and show in the screen some code like this:
[<c054d880<] ?
fsck stands for "file system check" [1]. systemd will check all of your filesystems every time you boot [2]. systemd-fsck[145]: /dev/sda4: clean, 2977/296096 files, 85427/1217024 blocks
systemd-fsck[151]: /dev/sda1: clean, 345/26104 files, 34083/104388 blocks (check after next mount)These messages mean that there are no problems with your filesystems and they are "clean&
I have a relatively new install of Ubuntu 9.10. I have two hard drives /dev/sda1 & /dev/sdb1 both ext3. Today for the first time a filesystem check was run on /dev/sdb1 but it ran after boot instead of before. I thought filesystem checks had to run in read only mode, before the filesystem was mounted.