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.
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.
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 am a newbie in Linux. So this is my story
I installed Ubuntu server 10.04lts. It worked great for many months, until today i decided to run fsck on the system partition and although it warned me, I kept pressing yes and now it will only boot into grub prompt.
So i read some article and tried grub reinstall.
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.
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).
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)
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 noticed that XFS does not implement a fsck at system boot and one of the reasons touted in that journaling file-systems help ensure the file-system is in a consistent state after an unclean shutdown; on the next boot the journal is replayed.
Is a fsck still needed after an unclean shutdown and why?
Email this page
