We're seeing this problem with certian ADS bitsyxb hardware that doesn't have a valid time until hwclock is run. Possible results range from fsck never running even after the max interval between checks has been reached, to it running at every single boot.
We've avoided this problem by adding a link to call hwclockfirst.sh before the fsck. -- see shy jo
signature.asc
Description: Digital signature
