| 1 |
On Saturday 24 July 2010 21:57:38 KH wrote: |
| 2 |
> Hi there, |
| 3 |
> |
| 4 |
> my server was running strait for 8 month now. I did updates regularly |
| 5 |
> but still used an 2.6.2x kernel. Never switched it of. Now someone from |
| 6 |
> houskeeping pulled the plug for the vacuum cleaner ... |
| 7 |
> |
| 8 |
> Anyway the box won't boot anymore. grub starts up. Kernel boots. Then |
| 9 |
> there is checking root file system (or something like that).The message |
| 10 |
> is that my ext2 file system can not be read. That I might want to try |
| 11 |
> the alternativ superblock by running #e2fsck -b 8193 <device> |
| 12 |
> |
| 13 |
> Well, I put the hdd in an external usb and conected it to my |
| 14 |
> workstation. As I thought hda3 (is /dev/sde3) is an ext3 filesystem. |
| 15 |
> Also badblocks and e2fsck did not show any problem with the hdd. |
| 16 |
> |
| 17 |
> /etc/fstab is corect (i hope), too. |
| 18 |
> |
| 19 |
> What am I missing? How can I get the server running, again? |
| 20 |
|
| 21 |
You said you ran e2fsck and it was OK. What was the command? |
| 22 |
|
| 23 |
Normally with an e2fsck on a journalled fs, the app will replay the journal |
| 24 |
and make a few minor checks. This takes about 4 seconds, not the 40 minutes it |
| 25 |
takes to do a ful ext2 check. |
| 26 |
|
| 27 |
I think you might need to fsck without the journal. I know there's a way to do |
| 28 |
this but a cursory glance at the man page didn't reveal it. Maybe an ext user |
| 29 |
will chip in with the correct method |
| 30 |
|
| 31 |
|
| 32 |
|
| 33 |
-- |
| 34 |
alan dot mckinnon at gmail dot com |
Archives