This initially shows has being unable to access /var, /usr or /bin. Checking "cat /proc/mounts" shows the root mount / has been set to read only "ro". Sometimes I get a kernel panic. Powering down and checking with a recovery disk, using fsck shows that the "recovery journal contains a file with errors... "
I've check and double checked and done the following;
- Down loaded the Mint14 Mate 64bit version direct from the Linux-Mint website, checking the MD5Sum hash on download and following burning to a DVD.
The system is (and has been for ages) a dual boot to Win7, so the first 3 Fat and NTFS partitions remain untouched.
With gpared, deleted and realigned the 4 extended partion. Reestablished the virtual partitions sda5, sda6 for / (35GB) (one for mint and one for ubuntu) and 1000 GB for /home and 8GB for swap. All have about 1MB free space between.
Created ext4 fs and surface checked for bad blocks with the fsck -cc option.
And have tried installing Mint14Mate 64Bit in sda6 and sda5 with same results.
Googling - the symptoms seem similar to the kernel bug reported about Oct 24, 2012 where the journal system in ext4 and maybe in ext3 would not unload (clean) when there were USB drives or loop fs mounted and in use. I assume this has got to be addressed and patches rolled through...
Any guidance much appreciated!. Thanks.
Dtohjam, Perth Aust.
