Tue Nov 3 10:50:01 GMT 2009
Content-Type: text/html; charset=ISO-8859-1
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<body bgcolor="#ffffff" text="#000000">
Robin Darlington wrote:
cite="mid:375efd030911050838h1de1e59el5e625e08920f27c at mail.gmail.com"
<div>I am running a fresh install of Ubuntu Studio Karmic and I have
now experienced filesystem errors twice.</div>
<div>The first time I put my computer to sleep and upon waking up it
would not accept my password (not due to keyboard layout : i checked by
typing it in username field) so I restarted and then I had to run fsck
manually to fix the Filesystem errors. The seccond time I was trying to
install some software in the terminal via sudo apt-get and the sudo was
just getting ignored. So i restarted and once again had to run fsck in
order for my system to boot. I installed with a ext4 filesystem.</div>
<div>Does anyone have any ideas what is going on here? and how to fix
<div>Has this happened to anybody else? Could it be to do with the
fact that I am using to <a moz-do-not-send="true"
href="http://ubuntu-tweak.com/">tweak ubuntu</a> to install third
party software (Opera, VirtualBox, Code Blocks etc.) ?</div>
<div>Thank you for your time,</div>
Here is a bugg comment:<br>
<span class="bz_comment_head"><i>Comment <a name="c6"
<span class="vcard"> <a class="fn email"
href="mailto:bug-track at fisher-privat.net">Alexey Fisher</a> </span>
2009-10-10 16:48:58</i> <span class="comment_rule">-------</span> </span>
<pre class="bz_comment_text">Ok, i think i know now how it's happed. I nneded some time to play to reproduce
it. There is _no_difference_ if you just boot 2.6.32 kernel run fsck and then
boot 2.6.31 kernel and run fsck again - nothing will happen.
here is the way i reproduced it:
1. crash (reset or poweroff) 2.6.32-rc3 kernel,
2. start again in 2.6.32-rc3
3. run fsck it well looks clean.. but some progrums will lost it setting.
4. reboot and start with 2.6.31 kernel
5. run fsck and this will find that ext4 is brocken.
6. after fsck fix it.. many fils will be lost.
More information about the Ubuntu-Studio-users