Ubuntu :: Mount Fails Because Of Unexpected Inconsistency?Oct 15, 2010
We are testing Ubuntu as the base for our products, we create custom Karmic installations (debootstrap + some extra packages) and then deploy our software, these systems can start in two different modes: "normal" and "read-only". We must say the system works quite well, but after some time, several systems are showing a common error: they don't start or fail showing an unexpected inconsistency for one of the partitions (every system has one hard disk with four partitions), the message refers to an unexpected inconsistency. When this error appears, a recovery console is started and I can run fsck and answer "yes" to its recommendations, after this the system runs again without errors. The problem is that this error can appear again at a random time and we need to avoid this "manual fixing" process, I've searched the web and found some references to a bug? in an early Karmic version: [URL]
Besides ALSA 1.0.23, we use only standard Karmic tools (all from the official repositories), we are running the latest kernel update available for Karmic, and don't know whether this inconsistency is caused by our software or by the system itself, or maybe because of incorrect shutdown?
At the moment, I'm setting a new test system using Lucid. Does anybody know if this is a "common" error in Karmic?