Today this problem reappeared. I directly restarted my system with the systemrescuecd to run e2fsck. No problems at all. So there is no corrupt superblock... And since it is not occurring with kernel 2.6.26-1, I believe it has something to do with kernel 2.6.26-2. I just can't see any pattern in the appearance of the problem.
Greets Steven -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
