#367 Issue `closed`: ext3 module with distribution kernel¶

Labels: support / question

dwerner1 opened issue at 2014-02-18 12:45:¶

Hi,
I've been using rear for a couple of months with debian 7.0 and kernel 3.12-1-amd64. A week ago I had problems after a system update and found that rear cannot mount a partition due to lack of ext3 module. So I had to rebuild the system from scratch. Am I right that rear demands a custom build kernel in debian with ext3 fs support enabled?
Best regards
Dirk

gdha commented at 2014-02-18 15:25:¶

Normally ext3 or ext4 are built into the kernel. Please verify if it copies the kernel modules to the rear image. If not, you could add it to the MODULES_LOAD array.
Test, test and test your rear images on-front please (in a lab environment).

dwerner1 commented at 2014-02-18 15:38:¶

Many thanks gdha!

ext3 support is not integrated by default into current debian kernels

lsmod | grep ext
ext4 465607 5
crc16 12343 2 ext4,bluetooth
mbcache 13082 1 ext4
jbd2 82560 1 ext4

I had assumed that a module that is being integrated in the rear backup archive, has to be running on the machine, that is being backuped. I'll try your suggestion with the MODULES_LOAD parameter!

dwerner1 commented at 2014-03-20 06:59:¶

This was obviously no ext3 issue but I'm still stuck. Here's the log output of rear recover

2014-03-20 08:45:34 Including verify/NETFS/default/06_mount_NETFS_path.sh
mkdir: created directory '/tmp/rear.zpmFpyKbbWUshP0/outputfs'
2014-03-20 08:45:34 Mounting with 'mount -v -o rw,noatime /dev/disk/by-label/REAR-000 /tmp/rear.zpmFpyKbbWUshP0/outputfs'
mount: special device /dev/disk/by-label/REAR-000 does not exist
mount: you didn't specify a filesystem type for /dev/disk/by-label/REAR-000
       I will try all types mentioned in /etc/filesystems or /proc/filesystems
Trying ext3
2014-03-20 08:45:34 ERROR: Mount command 'mount -v -o rw,noatime /dev/disk/by-label/REAR-000 /tmp/rear.zpmFpyKbbWUshP0/outputfs' failed.
=== Stack trace ===
Trace 0: /bin/rear:249 main
Trace 1: /usr/share/rear/lib/recover-workflow.sh:27 WORKFLOW_recover
Trace 2: /usr/share/rear/lib/framework-functions.sh:79 SourceStage
Trace 3: /usr/share/rear/lib/framework-functions.sh:40 Source
Trace 4: /usr/share/rear/verify/NETFS/default/06_mount_NETFS_path.sh:11 source
Trace 5: /usr/share/rear/lib/global-functions.sh:150 mount_url
Trace 6: /usr/share/rear/lib/_input-output-functions.sh:131 StopIfError
Message: Mount command 'mount -v -o rw,noatime /dev/disk/by-label/REAR-000 /tmp/rear.zpmFpyKbbWUshP0/outputfs' failed.
===================
2014-03-20 08:45:34 Running exit tasks.
rmdir: removing directory, '/tmp/rear.zpmFpyKbbWUshP0/outputfs'
2014-03-20 08:45:34 Finished in 3 seconds
2014-03-20 08:45:34 Removing build area /tmp/rear.zpmFpyKbbWUshP0
rmdir: removing directory, '/tmp/rear.zpmFpyKbbWUshP0'
2014-03-20 08:45:34 End of program reached

Any idea? I'm using the following settings in default.conf

BACKUP=NETFS
OUTPUT=USB
OUTPUT_URL="usb:///dev/disk/by-label/REAR-000"

The usb disk has been formatted with rear format /dev/sdc

gdha commented at 2014-04-01 14:27:¶

@dwerner1 Could you try using OUTPUT_URL=usb:///dev/sdc1 instead? Also verify if udevd is running in rescue mode?

[Export of Github issue for rear/rear.]