what's it doing?

[PB]

when I'm booting up, I get this message:

/dev/hda3 has reached maximal mount count, check forced

then it reads the harddrive for a while and gives me some stats about the drive and continues booting.

It's not really a problem, but I'm just curious as to what exactly its doing because it takes a long time. Does it have to do this on every boot? Is it part of the standard bootup procedure?

[Bradmont]

Originally posted by PB:
when I'm booting up, I get this message:

/dev/hda3 has reached maximal mount count, check forced

then it reads the harddrive for a while and gives me some stats about the drive and continues booting.

It's not really a problem, but I'm just curious as to what exactly its doing because it takes a long time. Does it have to do this on every boot? Is it part of the standard bootup procedure?
It's completely normal. What it means is that your partition(s) have been mounted a certain number of times whithout being checked, so the boot just verifies that there is nothing wrong with the partitions (eg, corrupted filesystems, etc). The x.x percent non-contiguous means that the drive is x.x % fragmented (what a defrag in windows reverses). Tho in Linux, you rarely (if ever) need to defrag.

[Derango]

Yep, thats normal...every once and awhile at least. If it starts every time you boot up, then you have a problem.