I haven't used my computer in a couple of weeks; been away. When I got back and booted up, most of my partitions needed to be scanned for apparently not having been scanned in 203 days.

While the partitions are being scanned I notice that the occasional error pops up so when I finish booting I try running "df -hT" to see if any of my partition weren't able to mount. The error message I get is "df: cannot read table of mounted filesystems."

However, I can browse through my file system and read files on my different partitions just fine.

What I also can't do is connect to the internet... Even though I'm connected as we speak on the same computer (running Windows XP).

Does anyone have any idea what's going on? I have multiple hard drives running on the computer: 250GB disk (with Windows), 320GB disk (Linux boot, swap, root, etc + storage), 500GB disk (storage) and a 640GB disk (storage).

I really doubt that they're all fucked up at the same time... What do you guys think? Any ideas?

Thanks for reading.

hi

its quite possible that the 203 days is correct and your system has a very long scan delay.

I have a ext3 system and mine is set to check after 30 cold boots or every 7 days....which suits me.

more mission critical people may prefer shorter delays.

2) assuming you have ext2 or 3 you can use a live cd to change your scan delays. ...target partition is left unmounted

man tune2fs ...will give you the options but I think you may like to look at example
tune2fs -c 30 -i 7 d /dev/sda1

3) while in live mode force a check now...again I assume you are ext2/3

man e2fsck will give you options but I like -f first and follow the prompts

Hi. Thanks for the reply.

Actually, only my boot partition is ext2/3. Others are either ReiserFS or XFS... Problem is, I don't remember which one's are what. I remember the bigger ones (storage) being XFS but with out "df" I don't remember the /dev/sd* of those partitions...

they have their own progs...so check your distro /etc/fstab to see which one is which and a good live cd should be able to re-configure your delay before filesystem checks