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

danny.petterson at accenture.com danny.petterson at accenture.com
Wed Jan 4 22:50:45 CET 2012

Hi again!

Thanks a lot for your mail.

It did get rid of the /sbin/hwup-problem – however the NIC’s/NIC-bond’s are not working, which makes the rescue impossible – which I don’t get as it is the exact same box where the backup was done.

Sorry – Im sure I miss something very simple here…

Greetings from

Danny Petterson

"Shadows and Dust"

From: Schlomo Schapiro [mailto:schlomo at schapiro.org]
Sent: 4. januar 2012 20:06
To: Discussions about Relax & Recover
Subject: Re: [Rear-users] Problem with SLES 10 recover on HP BL460C G6

On 4 January 2012 16:43, Jeroen Hoekx <jeroen.hoekx at hamok.be<mailto:jeroen.hoekx at hamok.be>> wrote:
udevd-event[xxxx]: run_program: exec of program ‘/sbin/hwup’ failed

I thought that I put in some code to filter out (e.g. replace with /bin/true or with a symlink) some well-known problematic udev helpers, one of them was hwup on SUSE.

The hwup script does some magic foo to load drivers and bind them to the "right" instance of a multi-instance hardware unit (e.g. multiple NICs, SCSI cards etc.) and won't work in the rescue system anyway.

Try adding the following line to build/GNU/Linux/00_create_symlinks.sh:

ln -sf $v true $ROOTFS_DIR/sbin/hwup >&2 # SUSE with udev needs this

and let us know if it works. I don't know where my stuff got lost, probably during the migration away from having symlinks in our source tree.


Subject to local law, communications with Accenture and its affiliates including telephone calls and emails (including content), may be monitored by our systems for the purposes of security and the assessment of internal compliance with Accenture policy.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://pikachu.3ti.be/pipermail/rear-users/attachments/20120104/03a17070/attachment.html 

More information about the rear-users mailing list