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