fdisk -l

Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x197fb8ed

Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 206847 204800 100M 7 HPFS/NTFS/exFAT
/dev/sda2 206848 141195263 140988416 67.2G 7 HPFS/NTFS/exFAT
/dev/sda3 141195346 467910655 326715310 155.8G f W95 Ext'd (LBA)
/dev/sda4 470011904 488392703 18380800 8.8G 7 HPFS/NTFS/exFAT
/dev/sda5 141195348 188153279 46957932 22.4G 7 HPFS/NTFS/exFAT
/dev/sda6 188201538 262919789 74718252 35.6G 7 HPFS/NTFS/exFAT
/dev/sda7 262920192 267016191 4096000 2G 82 Linux swap / Solaris
/dev/sda8 385992704 455940095 69947392 33.4G 83 Linux
/dev/sda9 455954432 467910655 11956224 5.7G 83 Linux
/dev/sda10 267018240 385978367 118960128 56.7G 83 Linux

fsck -y /dev/sda1
fsck from util-linux 2.25.2
fsck -y /dev/sda2
fsck from util-linux 2.25.2
fsck -y /dev/sda5
fsck from util-linux 2.25.2
fsck -y /dev/sda6
fsck from util-linux 2.25.2
fsck -y /dev/sda7
fsck from util-linux 2.25.2
fsck -y /dev/sda8
fsck from util-linux 2.25.2
e2fsck 1.42.12 (29-Aug-2014)
/dev/sda8: clean, 144749/2187264 files, 1028435/8743424 blocks
fsck -y /dev/sda9
fsck from util-linux 2.25.2
e2fsck 1.42.12 (29-Aug-2014)

fsck -y /dev/sda10
fsck from util-linux 2.25.2
e2fsck 1.42.12 (29-Aug-2014)
/dev/sda10 is mounted.
e2fsck: Cannot continue, aborting.

How to check sda10 with command fsck? My debian8 was installed here.

Boot in single user - "rescue" or "failsafe" mode - then run fsck.

Other options:

fsck -n /dev/sd10
read-only, therefore safe, but might report errors because the filesystem is in an inconsistent state while mounted.

Some distros allow forcing fsck at boot time by creating the empty file /forcefsck, or perhaps other means.

Or use tune2fs to change the fsck interval and reboot.

1 members found this post helpful.

Could use a live Medium... or, trigger to run on boot?

http://www.ducea.com/2008/10/24/linu...e-next-reboot/
http://www.cyberciti.biz/faq/linux-f...boot-sequence/

Unfortunately the OP didn't mention the distribution, but likely at this point it's using systemD which ignores the traditional methods of forcing fsck at boot.

Instead with systemd, the OP must add

to the boot time command line.