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.
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).
Hi all. I'm installing 12.1 ms5, and getting some strange problems with btrfs. My machine is a Dell D830 laptop. If I boot it is on mains power, the system enters maintance mode, with an error "fsck failed please repair manually" and no fsck.btrfs exists. If I boot on battery power, it boots correctly into the GUI.
i patiailly fixed the error doing a chroot from live cd then fsck from there everything works fine for aslong as the computer shuts down properly otherwise ill need to fsck from live cd again// some how the fsck done automatically after a couple of boot times dnt fix this :s
unable to repair the / filesystem. Run fsck manually (fsck -F ufs /dev/rdsk/c1t0d0s0)
--------------------------------------------------------------------------------
What can I fix this issue?
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 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.
When working remotely I set a server to force an fsck at boot time with the "sudo touch /forcefsck" command and rebooted.
After it restarted I checked in /var/log/fsck for the results of the disk check, but both checkfs and checkroot said "(Nothing has been logged yet.)
So where is it saving the results?
(I'll add that this was on an 11.10 server)
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?
Email this page
