Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #175010
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: forcefsck inconsistency |
| Date | 2016-11-22 20:50 +0100 |
| Message-ID | <sGpeN-365-21@gated-at.bofh.it> (permalink) |
| References | <sGosq-2Ad-29@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Tue 22 Nov 2016 at 19:50:50 (+0100), Pierre Frenkiel wrote: > trying to force the exec of fsck at boot, I found in init.d/checkfs.sh: > > if [ -f /forcefsck ] || grep -q -s -w -i "forcefsck" /proc/cmdline > then > force="-f" > else > force="" > fi > > So, I typed "touch /forcefsck", and rebooted. > This gave me several strange (IMHO) things > > 1/ fsck was run on 3 of my 5 ext4 partitions > but not on / (which actually has fs_passno=1) > and not for the 5th partition ,/dev/sdg1, which has fs_passno=2. > I have in syslog: > > "EXT4-fs (sdg1): warning: maximal mount count reached, running e2fsck is recommended" > > 2/ I have in syslog: > > "systemd-fsck[2553]: Please pass 'fsck.mode=force' on the kernel > command line rather than creating /forcefsck on the root file system." > > Does that mean that the guys working on checkfs.sh and systemd-fsck don't > communicate? > Anyway, I also tried this method, which gave me the same results. > > A workaround would be to boot with a live cd, and run fsck manually, but is > there an easier solution? Some things got a bit out-of-date perhaps. What works is to edit the linux line in grub, adding forcefsck This gets processed by scripts in the initrd. Cheers, David.
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
forcefsck inconsistency Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2016-11-22 20:00 +0100
Re: forcefsck inconsistency David Wright <deblis@lionunicorn.co.uk> - 2016-11-22 20:50 +0100
Re: forcefsck inconsistency Pierre Frenkiel <pierre.frenkiel@gmx.com> - 2016-11-22 23:50 +0100
Re: forcefsck inconsistency David Wright <deblis@lionunicorn.co.uk> - 2016-11-23 20:10 +0100
Re: forcefsck inconsistency Pierre Frenkiel <pierre.frenkiel@gmx.com> - 2016-11-26 10:30 +0100
Re: forcefsck inconsistency Richard Hector <richard@walnut.gen.nz> - 2016-11-28 14:20 +0100
Re: forcefsck inconsistency Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2016-11-28 14:30 +0100
Re: forcefsck inconsistency Michael Biebl <biebl@debian.org> - 2016-11-28 14:50 +0100
Re: forcefsck inconsistency Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2016-11-28 15:20 +0100
Re: forcefsck inconsistency Michael Biebl <biebl@debian.org> - 2016-11-28 18:10 +0100
Re: forcefsck inconsistency Pierre Frenkiel <pierre.frenkiel@gmx.com> - 2016-11-28 20:00 +0100
Re: forcefsck inconsistency Michael Biebl <biebl@debian.org> - 2016-11-29 00:20 +0100
Re: forcefsck inconsistency Pierre Frenkiel <pierre.frenkiel@gmail.com> - 2016-11-29 08:50 +0100
Re: forcefsck inconsistency Michael Biebl <biebl@debian.org> - 2016-11-29 12:40 +0100
Re: forcefsck inconsistency Pierre Frenkiel <pierre.frenkiel@gmx.com> - 2016-11-29 13:50 +0100
csiph-web