regular filesystem checks not starting

[MadOp]

Hi,

It seems that whenever a routine filesystem check is executed at boot time in one of my systems it stays there with the "a FS check will ocurr, press C to cancel" but it doesn't start at all, so the OS is not booted unless I manually skip thet check.

Given that the system is scheduled for autostart when I am not at home (50% of the time) that leaves me with no remote access to my files.

Manual checks report no error AFAICT.

The system has Mint 9 Isadora LTS fluxbox edition 100% up to date.
The hard drive is an IDE one, with a mix of ext4, ext3 and Fat32 partitions.

Boot partition is the only one with ext4; I can't tell which one the system is trying to check when this happens, although I suspect it is the ext4 one.

Any ideas?
Thanks in advance!
MadOp.

[breaker]

Possibly imminent hardware failure, so back up your data. There are boot disks you can use to scan for disk errors such as MHDD or one from the drive manufacturer, just make sure you pick a non-destructive test. In the meanwhile you can adjust the disk checking frequency. I forget the command line for that, but there are commands you use to set those parameters on ext2, ext3, and ext4 volumes.

[MadOp]

I know it has been a lot of time since I asked, but I eventually found out it was caused by a partition getting around 90% filled.
It had nothing to do -at least in this case- with a faulty drive, but with a mount command at boot being issued before the disk checker released the partition.

Just FWIW.