| 1 |
Alan McKinnon wrote: |
| 2 |
> On Sunday 25 July 2010 06:57:43 KH wrote: |
| 3 |
> |
| 4 |
>>> You said you ran e2fsck and it was OK. What was the command? |
| 5 |
>>> |
| 6 |
>>> |
| 7 |
>>> |
| 8 |
>>> Normally with an e2fsck on a journalled fs, the app will replay the |
| 9 |
>>> journal and make a few minor checks. This takes about 4 seconds, not |
| 10 |
>>> the 40 minutes it takes to do a ful ext2 check. |
| 11 |
>>> |
| 12 |
>>> |
| 13 |
>>> |
| 14 |
>>> I think you might need to fsck without the journal. I know there's a way |
| 15 |
>>> to do this but a cursory glance at the man page didn't reveal it. Maybe |
| 16 |
>>> an ext user will chip in with the correct method |
| 17 |
>>> |
| 18 |
>>> |
| 19 |
>>> |
| 20 |
>>> |
| 21 |
>>> |
| 22 |
>> Hi, |
| 23 |
>> |
| 24 |
>> I ran on the two partitions e2fsck /dev/sde3 as well as fsck.ext3 |
| 25 |
>> /dev/sde3 . Yes, it only took some seconds. |
| 26 |
>> |
| 27 |
> It's been a long time since I used ext3 so some of this might be wrong. |
| 28 |
> |
| 29 |
> An fsck that takes a few seconds is using the journal, which might not uncover |
| 30 |
> deeper corruption. You should try disabling the journal (I couldn't find the |
| 31 |
> way to do that though), but this will also work: |
| 32 |
> |
| 33 |
> Boot of a LiveCD, mount your root partition somewhere using type "ext2" and |
| 34 |
> fsck it. This will invalidate the journal but that's OK, it gets recreated on |
| 35 |
> the next proper boot. Let the fsck finish - it will take a while on a large |
| 36 |
> fs. |
| 37 |
> |
| 38 |
> When done, reboot as normal and see if the machine boots up properly. |
| 39 |
> |
| 40 |
> |
| 41 |
> |
| 42 |
|
| 43 |
And I would stand guard to make sure housekeeping doesn't come around. |
| 44 |
;-) Cutting power during all this wold not be good. |
| 45 |
|
| 46 |
Dale |
| 47 |
|
| 48 |
:-) :-) |
Archives