Kernel Panic after power failure

2013-10-21 Thread Henrique C. S. Junior 

After a power failure in my building, my SL 6.4 (x86_64) is experiencing a 
kernel panic in the first stages of booting.
Error messages suggests that a serious problem occurred with my Ext4 filesystem 
in /dev/mapper/VolGroup-lv_root.
Here are the error messages aftes the kernel panic:

ata3.00: status: { DRDY ERR }
ata3.00: error: { UNC }
ata3.00: exception Emask 0xoSAct 0x0 SErr 0x0 action 0x0
ata3.00: BMDMA stat 0x25
ata3.00: failed command: READ DMA
ata3.00: cmd c8/00:00:c0:86:14/00:00:00:00:00/e3 tag 0 dm 131072 in
 res 51/40:cf:e8:86:14/00:00:00:00:00/e3 Emask 0x9 (media error)

ata3.00: status: { DRDY ERR }
ata3.00: error: { UNC }
JBD: Failed to read block at offset 6886
EXT4-fs (dm-0): error
 loading journal
mount: wrong fs type, bad option, bad superblock on 
/dev/mapper/VolGroup-lv_root,
   missing codepage or helper program, or other error
   In some cases useful info is found in syslog - try
dmesg | tail or so

Rescue disk says that I don't have any Linux partitions and I need to rescue, 
at least, two MySQL databases in this server.
Can someone, please, provide some help with this case?
 
---
Henrique C. S. Junior
http://about.me/henriquejunior
Química Industrial - UFRRJ
Prefeitura Muncipal de Paracambi
Centro de Processamento de Dados

Re: Kernel Panic after power failure

2013-10-21 Thread John Lauro 
Is it a SSD? A lot of SSD (especially consumer grade) lie about writes 
completing and cause nasty problems when the power goes out... 

Try mounting it with ro,noload. 

- Original Message -

 From: Henrique C. S. Junior henrique...@gmail.com
 To: Scientific Linux Users scientific-linux-users@fnal.gov
 Sent: Monday, October 21, 2013 8:52:52 AM
 Subject: Kernel Panic after power failure

 After a power failure in my building, my SL 6.4 (x86_64) is
 experiencing a kernel panic in the first stages of booting.
 Error messages suggests that a serious problem occurred with my Ext4
 filesystem in /dev/mapper/VolGroup-lv_root.
 Here are the error messages aftes the kernel panic:

 ata3.00: status: { DRDY ERR }
 ata3.00: error: { UNC }
 ata3.00: exception Emask 0xoSAct 0x0 SErr 0x0 action 0x0
 ata3.00: BMDMA stat 0x25
 ata3.00: failed command: READ DMA
 ata3.00: cmd c8/00:00:c0:86:14/00:00:00:00:00/e3 tag 0 dm 131072 in
 res 51/40:cf:e8:86:14/00:00:00:00:00/e3 Emask 0x9 (media error)

 ata3.00: status: { DRDY ERR }
 ata3.00: error: { UNC }
 JBD: Failed to read block at offset 6886
 EXT4-fs (dm-0): error loading journal
 mount: wrong fs type, bad option, bad superblock on
 /dev/mapper/VolGroup-lv_root,
 missing codepage or helper program, or other error
 In some cases useful info is found in syslog - try
 dmesg | tail or so

 Rescue disk says that I don't have any Linux partitions and I need
 to rescue, at least, two MySQL databases in this server.
 Can someone, please, provide some help with this case?

 ---
 Henrique C. S. Junior
 http://about.me/henriquejunior
 Química Industrial - UFRRJ
 Prefeitura Muncipal de Paracambi
 Centro de Processamento de Dados

Re: Kernel Panic after power failure

2013-10-21 Thread Henrique Junior 
I was able to fix the issue using the steps provided here:
http://pissedoffadmins.com/os/mount-unknown-filesystem-type-lvm2_member.html

Thank you for your help, guys.


2013/10/21 Henrique C. S. Junior henrique...@gmail.com

 Hi,
 It is an HDD failure. I have already tried e2fsck -b 8193 with no luck...

 ---
 Henrique C. S. Junior
 http://about.me/henriquejunior
 Química Industrial - UFRRJ
 Prefeitura Muncipal de Paracambi
 Centro de Processamento de Dados


   On Monday, October 21, 2013 11:33 AM, Henrique Castro 
 henrique...@yahoo.com wrote:

  Hi,
 It is an HDD failure. I have already tried e2fsck -b 8193 with no luck...

 ---
 Henrique C. S. Junior
 http://about.me/henriquejunior
 Química Industrial - UFRRJ
 Prefeitura Muncipal de Paracambi
 Centro de Processamento de Dados


   On Monday, October 21, 2013 11:23 AM, Oleg Sadov sa...@linux-ink.ru
 wrote:

 Seems like HDD failure. Try to read this disk in another computer. If
 superblock is damaged -- you may try to recover form backup superblock
 (e2fsck -b).

 21/10/2013 05:52 -0700, Henrique C. S. Junior wrote:
  After a power failure in my building, my SL 6.4 (x86_64) is
  experiencing a kernel panic in the first stages of booting.
  Error messages suggests that a serious problem occurred with my Ext4
  filesystem in /dev/mapper/VolGroup-lv_root.
  Here are the error messages aftes the kernel panic:
 
  ata3.00: status: { DRDY ERR }
  ata3.00: error: { UNC }
  ata3.00: exception Emask 0xoSAct 0x0 SErr 0x0 action 0x0
  ata3.00: BMDMA stat 0x25
  ata3.00: failed command: READ DMA
  ata3.00: cmd c8/00:00:c0:86:14/00:00:00:00:00/e3 tag 0 dm 131072 in
   res 51/40:cf:e8:86:14/00:00:00:00:00/e3 Emask 0x9 (media
  error)
 
  ata3.00: status: { DRDY ERR }
  ata3.00: error: { UNC }
  JBD: Failed to read block at offset 6886
  EXT4-fs (dm-0): error loading journal
  mount: wrong fs type, bad option, bad superblock
  on /dev/mapper/VolGroup-lv_root,
 missing codepage or helper program, or other error
 In some cases useful info is found in syslog - try
  dmesg | tail or so
 
  Rescue disk says that I don't have any Linux partitions and I need
  to rescue, at least, two MySQL databases in this server.
  Can someone, please, provide some help with this case?
 
  ---
  Henrique C. S. Junior
  http://about.me/henriquejunior
  Química Industrial - UFRRJ
  Prefeitura Muncipal de Paracambi
  Centro de Processamento de Dados
 







-- 
Henrique LonelySpooky Junior
http://about.me/henriquejunior