[Rear-users] Problem with SLES 10 recover on HP BL460C G6

Dag Wieers dag at wieers.com
Fri Jan 6 00:15:58 CET 2012


On Wed, 4 Jan 2012, danny.petterson at accenture.com wrote:

> I do have some errors during the backup, like these:
>
> strip: /tmp/rear.14089/rootfs/bin/ldd: File format not recognized
> strip: /tmp/rear.14089/rootfs/bin/fsck.xfs: File format not recognized
> strip: /tmp/rear.14089/rootfs/bin/xfs_admin: File format not recognized
> strip: /tmp/rear.14089/rootfs/bin/egrep: File format not recognized
> strip: /tmp/rear.14089/rootfs/bin/fgrep: File format not recognized
> strip: /tmp/rear.14089/rootfs/bin/hpacucli: File format not recognized
> strip: /tmp/rear.14089/rootfs/bin/path_id: File format not recognized
> strip: /tmp/rear.14089/rootfs/bin/rear: File format not recognized
>
> Cannot determine dependencies of module unix. Is modules.dep up to date?
> Cannot determine dependencies of module hpilo. Is modules.dep up to date?
> 2012-01-04 15:55:30 Copying kernel modules
> cp: cannot stat `/hwcrypto=0': No such file or directory
> cp: cannot stat `/led=1': No such file or directory
> cp: cannot stat `/associate=0': No such file or directory
> cp: cannot stat `/hwcrypto=0': No such file or directory
> cp: cannot stat `/led=1': No such file or directory
> cp: cannot stat `/associate=0': No such file or directory
>
> 012-01-04 15:55:32 Including build/GNU/Linux/60_verify_and_adjust_udev.sh
> 2012-01-04 15:55:32 WARNING: unmatched external call to 'ipw3945d.sh' in etc/udev/rules.d/31-network.rules:16
> 2012-01-04 15:55:32 WARNING: unmatched external call to 'ipw3945d.sh' in etc/udev/rules.d/31-network.rules:17
> 2012-01-04 15:55:32 WARNING: unmatched external call to '/sbin/ifdown' in etc/udev/rules.d/31-network.rules:27
> 2012-01-04 15:55:32 WARNING: unmatched external call to '/sbin/fxload' in etc/udev/rules.d/40-alsa.rules:9
> 2012-01-04 15:55:32 WARNING: unmatched external call to '/sbin/fxload' in etc/udev/rules.d/40-alsa.rules:10
> 2012-01-04 15:55:32 WARNING: unmatched external call to '/sbin/fxload' in etc/udev/rules.d/40-alsa.rules:11
> 2012-01-04 15:55:32 WARNING: unmatched external call to '/sbin/startproc' in etc/udev/rules.d/40-alsa.rules:12
> 2012-01-04 15:55:32 WARNING: unmatched external call to '/sbin/startproc' in etc/udev/rules.d/40-alsa.rules:13
> 2012-01-04 15:55:32 WARNING: unmatched external call to '/usr/sbin/alsactl' in etc/udev/rules.d/40-alsa.rules:14
> 2012-01-04 15:55:32 WARNING: unmatched external call to '/etc/alsa.d/udev-soundfont' in etc/udev/rules.d/40-alsa.rules:1
> 5
> 2012-01-04 15:55:32 WARNING: unmatched external call to '/sbin/kpartx_id' in etc/udev/rules.d/71-multipath.rules:14
> 2012-01-04 15:55:32 WARNING: unmatched external call to '/sbin/kpartx_delete' in etc/udev/rules.d/71-multipath.rules:34
> 2012-01-04 15:55:32 WARNING: unmatched external call to '/sbin/mdadm' in etc/udev/rules.d/73-mdadm.rules:2
> 2012-01-04 15:55:32 WARNING: unmatched external call to '/sbin/mdadm' in etc/udev/rules.d/73-mdadm.rules:4
> 2012-01-04 15:55:32 WARNING: unmatched external call to '/sbin/hwup' in etc/udev/rules.d/80-sysconfig.rules:4
> 2012-01-04 15:55:32 WARNING: unmatched external call to '/sbin/hwup' in etc/udev/rules.d/80-sysconfig.rules:5
> 2012-01-04 15:55:32 WARNING: unmatched external call to '/sbin/hwup' in etc/udev/rules.d/80-sysconfig.rules:6
> 2012-01-04 15:55:32 WARNING: unmatched external call to '/sbin/hwdown' in etc/udev/rules.d/80-sysconfig.rules:7
> 2012-01-04 15:55:32 WARNING: unmatched external call to '/sbin/hwup' in etc/udev/rules.d/80-sysconfig.rules:8
>
> tar: /boot/: file is on a different filesystem; not dumped
> tar: /proc/: file is on a different filesystem; not dumped
> tar: /sys/: file is on a different filesystem; not dumped
> tar: /dev/: file is on a different filesystem; not dumped
> tar: /var/lib/dhcp/dev/log: socket ignored
> tar: /var/lib/ntp/proc/: file is on a different filesystem; not dumped
>
> Any help would be appreciated.

Just a heads-up.

Most (if not all) of the above errors are not related to your network 
problems, but I do sympathize with the fact that we shouldn't have any of 
these in the default output. (Not sure why /sbin/ifdown is missing on 
SLES and what some of these other binaries are)

The errors we generate ourselves should probably be surpressed unless 
verbose/debug output is being used.

The errors generated by other tools (e.g. tar) is out of our direct 
control. If we would surpress the output, real problems may go unnoticed. 
For example, the tar output is correct, when we tar each file-system (in 
a single run), it excludes the other filesystems while recursing. This is 
exactly what we want, but may look erroneous just by looking at the logs 
:-(

This issue should be listed as one of the (known) issues and prioritized 
in the TODO list.

Kind regards,
-- 
-- dag wieers, dag at wieers.com, http://dag.wieers.com/
-- dagit linux solutions, info at dagit.net, http://dagit.net/

[Any errors in spelling, tact or fact are transmission errors]




More information about the rear-users mailing list