[PATCH] aacraid: fails to initialize after a kexec operation

Vivek Goyal vgoyal at in.ibm.com
Tue Apr 24 05:01:55 EDT 2007

On Tue, Apr 24, 2007 at 02:14:44PM +0530, Vivek Goyal wrote:
> In second attempt, it mounted the file system but it found some issue
> with "resize" inode and asked me to run fsck manually. Which in turn 
> deleted whole lot of inodes.
> In third attemt it panics later when it finds ext3 to be corrupted.
> =========================================
> Creating block device nodes.
> Trying to resume from LABEL=SWAP-sda3
> No suspend signature on swap, not resuming.
> Creating root device.
> Mounting root filesystem.
> EXT3-fs: Magic mismatch, very weird !
> mount: error mouKernel panic - not syncing: Attempted to kill init!
> nting /dev/root
> =================================================== 

Hi Mark,

Interesting observation. After above message I rebooted my system
expecting ext3 is corrupted and I shall have to try to recover it
using fsck. Nothing of that sort happened. System just booted fine.

This leaves me wondering why does ext things that Magic number is a 
mismatch while booting using kexec. Is AACRAID returning the write bytes
from the disk after an reset?


More information about the kexec mailing list