[lugm.org] kernel panic

Loganaden Velvindron gnukid1 at yahoo.co.uk
Thu Apr 22 17:11:56 UTC 2010


I'm not sure I can help here, but this may help.

It seems the journal has been corrupted.

According to this thread, 
http://www.linuxquestions.org/questions/linux-hardware-18/disable-journaling-on-ext3-266536/

It's possible to disable the journal (or at least mount it separately) 
from the partition itself, and recover the rest.

Another way might be to mount an ext3 as an ext2 partition.

The journal keeps a log of last activities, and it's very possible that you've lost
the last fs operations; some files may not have been altered properly.

Failing that, I'd advise going for commercial software such as:

http://www.datarecoverylinux.com/


//Logan
C-x-C-c




--- On Thu, 22/4/10, Belal Kadayer <abdelaziz at intnet.mu> wrote:

From: Belal Kadayer <abdelaziz at intnet.mu>
Subject: [lugm.org] kernel panic
To: "LUGM Discuss Mailing List" <discuss at lugm.org>
Date: Thursday, 22 April, 2010, 15:58



 
 


Hi guys,
 
Am having some problem fixing fs 
error 
Am using redhat enterprise edition 4 
with lvm 
The message am receiving at boot is 
 
JBD: io error reading journal 
superblock 
Ext3-fs: error loading 
journal 
Mount: error 22 mounting 
ext3 
Mount: error 2 mounting 
none 
Switch root: mount failed 
22 
Umount /initrd/dev failed: 
2 
  
  
I already try to fix with e2fsck 
with out success 
Am not able to mount the 
/dev/hda2  
  
Would appreciate if anyone can tell 
the proper way to recover my data 
  
Cheers 
Belal
-----Inline Attachment Follows-----

__________________________________________________________
Linux User Group of Mauritius (LUGM) Discuss mailing list
Website: http://lugm.org
Mailing list archive: http://lugm.org/pipermail/discuss_lugm.org/
Forum: http://lugm.org/forum/
IRC: #linux.mu on Freenode



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://discuss.lugm.org/pipermail/discuss_discuss.lugm.org/attachments/20100422/b7c78bd5/attachment.html>


More information about the Discuss mailing list