Mount usb drive with mount -a fails after f10 upgrade

Joe W. Byers ecjbosu at aol.com
Wed Jan 7 17:57:44 UTC 2009


Jeff Spaleta <jspaleta <at> gmail.com> writes:

> 
Pruned!
> So you were getting an EL5 failure at boot, you were probably using a
> custom script to run mount commands "later on"  Again I'm not in a
> position to try to diagnose your EL5 behavior.
> 
> The point is simply this.... the information from tune2fs associated
> with the max mount count looks odd to me.  What's also problematic in
> your tune2fs output is the fact that the Filesystem state is listed as
> unclean.
> 
> If I were you I would set the max mount count to 0 or -1 turning off
> the max mount count check using tune2fs -c.  I would then  run
> fsck.ext2 again and use the -f to force the check,  run tune2fs -l and
> see if the Filesystem state changes from "not clean" to "clean"
> 
> -jef
> 


I set the max count to 99 this morning.  When I get home I will 
rerun the e2fsck. 

Yes my upgrade path is strange and I am not sure at all how EL 
handled this.  I
may have had a mount script that no longer runs.  I will have to 
look around.

Thank you very much for the input.

Joe





More information about the fedora-list mailing list