Checking The File System

[anonprivate]

After having had some problems with the kwalletmanager and having uninstalled this utility, I think it might be a good idea to check my file system.

Before the check, I would just like to ask if I am using the correct code. I would like to check the file system on the hard disk and am thinking of using the following command:

fsck -V /dev/sda1

My aim is to check, report, and, if necessary, repair.

Thanks

[sithlord48]

your filesystem will automaticly be checked every N boots (i think by default N is 30 or so) . looking at the help for fsck you can see the various options i think you want to use -v -p. you cant check filesystems that are mounted (this is why it happens at boot time for partitions in fstab)

➜  ~  fsck --help         
fsck from util-linux 2.25.1
fsck.ext4: invalid option -- 'h'
Usage: fsck.ext4 [-panyrcdfvtDFV] [-b superblock] [-B blocksize]
                [-I inode_buffer_blocks] [-P process_inode_size]
                [-l|-L bad_blocks_file] [-C fd] [-j external_journal]
                [-E extended-options] device

Emergency help:
 -p                   Automatic repair (no questions)
 -n                   Make no changes to the filesystem
 -y                   Assume "yes" to all questions
 -c                   Check for bad blocks and add them to the badblock list
 -f                   Force checking even if filesystem is marked clean
 -v                   Be verbose
 -b superblock        Use alternative superblock
 -B blocksize         Force blocksize when looking for superblock
 -j external_journal  Set location of the external journal
 -l bad_blocks_file   Add to badblocks list
 -L bad_blocks_file   Set badblocks list

[anonprivate]

Thank you for responding.

I assume that the path '/dev/sda1' is correct.

A couple of questions.

What will happen if I 'unmount' the file system (if this is the correct terminology). I would like to check all file systems?

You say there is an automatic file system check at 'N' boot-ups. I haven't noticed any messages to this effect. Can I gain more information?

Best wishes.

A

[Rog132]

fsck & documents

Ubuntu community

Ubuntu Community Help Wiki: https://help.ubuntu.com/community
--> Drives And Partitions: https://help.ubuntu.com/community/DrivesAndPartitions
----> Testing Storage Media: https://help.ubuntu.com/community/TestingStorageMedia
--> Trouble Shooting Guide: https://help.ubuntu.com/community/TroubleShootingGuide
----> Filesystem Troubleshooting: https://help.ubuntu.com/community/Fi...roubleshooting

Fstab (fsck order): https://help.ubuntu.com/community/Fstab


AskUbuntu

Where are fsck results logged at boot time, after /forcefsck?: http://askubuntu.com/questions/11290...fter-forcefsck

Note ! Does not log fsck invocations in /var/log/fsck/: https://bugs.launchpad.net/ubuntu/+s...ll/+bug/513644
--> You could look the: /var/log/upstart/mountall.log

How do I find out if there will be a fsck during the next boot?: http://askubuntu.com/questions/26141...-the-next-boot


I would...

I would start the computer from the Kubuntu installation CD / USB stick and run the fsck from there.

[oshunluvr]

I don't have much to add as Rog usually covers everything.

I believe another way to force a filesystem check of your mounted filesystem is to simply set it to do so and reboot. What used to work was

sudo touch /forcefsck

and reboot. I haven't tried that in years so I don't know if it's still valid. Likely, it's mentioned in one of the threads Rog linked to.

I do have a couple points:
#1: You should mention what filesystem you are using when asking these sort of questions. I suppose most will assume you're using the default these days - ext4 - but not everyone does.
#2: I wonder why you think removing a package or two requires a files system check? Of course - you should be as diligent with your filesystem as you feel the need, but I guess I want to point out that ext4 is not NTFS and isn't likely to become damaged or fragmented by normal operations. I can't think of anything kwalletmanager would do at the filesystem level to cause problems.

[Rod J]

It should be noted that automatic fsck on ext4 file systems is no longer performed at boot time since Kubuntu 12.04. We discussed this some time ago on this forum: https://www.kubuntuforums.net/showth...sck-at-boot-up

Although, after a lot of googling I still can't find a direct reference to the actual change of policy on this.

[anonprivate]

I don't have much to add as Rog usually covers everything.

I believe another way to force a filesystem check of your mounted filesystem is to simply set it to do so and reboot. What used to work was

sudo touch /forcefsck

and reboot. I haven't tried that in years so I don't know if it's still valid. Likely, it's mentioned in one of the threads Rog linked to.

I do have a couple points:
#1: You should mention what filesystem you are using when asking these sort of questions. I suppose most will assume you're using the default these days - ext4 - but not everyone does.
#2: I wonder why you think removing a package or two requires a files system check? Of course - you should be as diligent with your filesystem as you feel the need, but I guess I want to point out that ext4 is not NTFS and isn't likely to become damaged or fragmented by normal operations. I can't think of anything kwalletmanager would do at the filesystem level to cause problems.

Yes, The system is ext4. Why is it called ext4?

I wanted to check the file system because the walletmanager worked well, and then started giving odd messages that related to a path that was not correct. I get many update messages and and update, I assumed that one of these may have caused the problem. I could not think of anything else.

Just to be on the safe side, I though it wise to check the validity of the files system.

Best wishes.

A

[oshunluvr]

http://en.wikipedia.org/wiki/Extended_file_system

EXTended file system, 4th version.