good news adn bad news... The good news is this worked fine without yuok, which makes me wonder what was so different in this version that it could see the disks and the older, 3.8.1 couldn't - I'd think that's pretty basic stuff. Anyhow I'm not going to worry about it if you're not. I'm happy...
now the bad news - after my system rebooted it started to reimage again and si_netbootmond IS running. I then took a look in /var/log/messages and saw the following: Dec 19 11:12:09 cag-dl380-01 kernel: application bug: rsync(17523) has SIGCHLD set to SIG_IGN but calls wait(). Dec 19 11:12:09 cag-dl380-01 kernel: (see the NOTES section of 'man 2 wait'). Workaround activated. so I'm guessing the successful termination message netbootmond is looking for isn't there! In any event I did escape out of the network boot when the system tried to come back up and it did boot successfully so we in fact have installed a good image, but this also means it's going to always try to install a new image unless I clean up the problem with rsync. Has anyone seen this before? Might it be possible for the installation script to write its own message into the messages file rather than rely on rsync? Just a thought... As another comment, I'm using a pretty old system for imaging - don't laugh, but it's RH9 and has been working just fine for SI and I guess we've been do dependent on SI we've been afraid to upgrade it. -mark. Andrea Righi wrote: > Mark Seger wrote: > >> I should probably know better but I don't, even though I've been using >> SystemImager for a very long time and now I'm faced with a kernel that >> can't see my hard drive and so need to get UYOK working. The >> documentation implied that it just worked yet SI insists on loading >> BusyBox. Is there some manual step I need to do in which to tell the it >> to load MY kernel and initrd instead of BusyBox? >> -mark >> > > Mark, > > probably you misunderstand something... UYOK is a kernel, BusyBox is a > set of unix utilities in userspace. Both the standard BOEL and UYOK > kernels use BusyBox to create a UNIX environment into the initrd.img, so > in practice you must always see the BusyBox shell. > > But let's focus on the real problem: you don't see your /dev/sda. Do you > know which particular disk controller is installed in your client? > > Anyway, I would suggest to try also the BOEL kernel from SI 4.0.2 and > re-create the autoinstall script with --autodetect-disks. > > -Andrea > ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ sisuite-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-devel
