Hi.
I would check your initrd.img and maybe make a new one pre-loading or with
raid5.
How such image could be prepared?
I posted my autoinstall in the original post, here it is again:
config
disk dev=/dev/sda label_type=msdos unit_of_measurement=MB
!--
This disk's output was
Seth Haines wrote:
Andrea,
This was on a 3.8.1 based server.
This bug has been fixed in 4.0.0.
Look at the diff below. In particular these two lines should resolve
your problem:
+ $cmd =~ s//\\/g;
+ $cmd = \$cmd\;
Maybe you should consider to move to 4.0.2 or if you don't
Hi Jesus,
comments below.
Jesus Sanchez wrote:
I've got some good news. At least now the cloned system boots. There
was something related with the modules and therefore with the initrd file.
I was using UYOK and not BOEL, sorry, but I tried to add some extra
modules in the file
hi to all
new to the list.. i recently installed and used the systemimager distro
all works fine, except when using the bittorrent deployment method,
i got this error
$: /etc/init.d/systemimager-server-bittorrent start
Starting SystemImager's BitTorrent Transport:
OK, I managed to solve it.
There were two issues:
1) The master looked for raid5.ko module, while I had raid456.ko. Changing
the master script took care of this.
2) The mdadm --create failed due to specified --chunk 256 parameter, with
the following errors:
invalid sb on partition
error
hi to all
new to the list.. i recently installed and used the systemimager distro
all works fine, except when using the bittorrent deployment method,
i got this error
$: /etc/init.d/systemimager-server-bittorrent start
Starting SystemImager's BitTorrent Transport:
Maurice Libes wrote:
hi to all
Maurice
# Tracker log file.
BT_TRACKER_LOG=/var/log/systemimager/bittorrent-tracker.log
# Interface used to seed files with bittorrent.
BT_INTERFACES=eth0
BT_INTERFACE will do the trick (so remove the trailing s_ ;-)
--
--
DongInn Kim wrote:
Hi Erich,
Thank you.
Basically, I got this question when I looked for some instructions about
updating kernel on the OSCAR cluster in the OSCAR admin manual.
http://svn.oscar.openclustergroup.org/trac/oscar/wiki/AdminGuide/Commands#ManagingRepositories
As you can see
Bas van der Vlies a écrit :
# Interface used to seed files with bittorrent.
BT_INTERFACES=eth0
BT_INTERFACE will do the trick (so remove the trailing s_ ;-)
i removed the trailing S (shame on me) but it's the same error, so
the error didnt'come from this line
Maurice Libes wrote:
Bas van der Vlies a écrit :
# Interface used to seed files with bittorrent.
BT_INTERFACES=eth0
BT_INTERFACE will do the trick (so remove the trailing s_ ;-)
i removed the trailing S (shame on me) but it's the same error, so
the error didnt'come from
Stas Oskin wrote:
OK, I managed to solve it.
There were two issues:
1) The master looked for raid5.ko module, while I had raid456.ko.
Changing the master script took care of this.
2) The mdadm --create failed due to specified --chunk 256 parameter,
with the following errors:
invalid sb
Hi.
The strange thing with chunk, is that the partitions already contain SB -
does the partitioning process creates it? The mdadm apparently tries to
import it, and then fails.
About UYOK, I followed Quick Start HOWTO, and part of it is the following
command:
si_prepareclient --server
12 matches
Mail list logo
