#444 Issue `closed`: rear rescue ISO image kernel panic¶

Labels: support / question

kamensa opened issue at 2014-07-29 10:09:¶

Hi All,

I have installed REAR on RHEL 6.5 - 2.6.32-431.el6.x86_64, physical box and RHEL 5.10 - 2.6.18-371.el5 i686 - VM on VirtualBox. REAR versions which I have used are rear-1.16.1-1.el5 and rear-1.15-9.el6.noarch. The backup process completes without any issues. I'm using NFS share for backup and iso files but when I try to boot from rescue image I get kernel panic. The same result on physical box and VM. Could you tell me how to attached my local.conf, site.conf and rear log file here? Basically I have copied default.conf into /etc/site.conf and changed the following:

BACKUP=NETFS
OUTPUT=ISO
BACKUP_URL=nfs://camstore3a/vol/camreardr_nfs
OUTPUT_URL=nfs://camstore3a/vol/camreardr_nfs
EXCLUDE_MOUNTPOINTS=("Data dirs")

The /etc/rear/local.conf contains: OUTPUT=ISO

The /etc/rear/os.conf contains:
OS_VENDOR=RedHatEnterpriseServer
OS_VERSION=6

Here are the kernel panic snapshots:

physical_box

vm_box

gdha commented at 2014-07-29 14:11:¶

which fs type are you using? ext3 perhaps. it might be the the ext3 kernel module is not loaded during the initrd phase...

kamensa commented at 2014-07-30 06:50:¶

How could I fix this? I mean how could I force rear mkbackup or rear mkrescue to include this module. I have used rear couple of years before and I haven't had such issues. It's very strange to have issues with ext3 fs.

gdha commented at 2014-07-30 09:05:¶

See the issues #326 and #367 for some background details. You could start with lsmod | grep ext on your running system (and on the system booted with recovery image)