Hi.
I managed to temporary solve it by booting in rescue mode on the newly
imaged servers, erasing the initrd and regenerating it (so it would reuse
the systemworks controller).
Okay, can you have a look at the contents of your boel_binaries.tar.gz
> and see if there are symlinks to non-existing files?
> B
>
boel_binaries is standard systemimager file, and doesn't come from the
custom initrd? AFAIK it shouldn't contain any dead symlinks?
>> the log of when you generate the UYOK initrd -- perhaps something went
> >> wrong there and it wasn't caught.
> >
> > How can I produce such log?
>
> How did you generate the UYOK kernel/initrd? Re-run that same command
> and post the output. Better yet, if that command provides a --verbose
> mode, do that.
>
I will do it on the next imaging batch, and then post here the results.
>
> So 4.1.6?
Yes.
Regards.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
