Re: [sisuite-users] [Sisuite-devel] Net beta release v4.5.0-20170614git
Olivier - Thanks. Will wait for the new version and then try the OSCAR repository. David -Original Message- From: olivier.laha...@free.fr [mailto:olivier.laha...@free.fr] Sent: Thursday, June 29, 2017 3:07 AM To: sisuite-users@lists.sourceforge.net Cc: sisuite-de...@lists.sourceforge.net Subject: Re: [sisuite-users] [Sisuite-devel] Net beta release v4.5.0-20170614git David, After reading a bit closer your message you're trying to install systemimager using the rpm command that doesn't handle dependancies download. You need to use the "yum install" instead of "rpm -ivh" command. That should work. Please try again using yum. IMHO, it's a good idea to use the OSCAR repository: rpm -ivh http://svn.oscar.openclustergroup.org/repos/unstable/rhel-6-x86_64/oscar-release-6.1.2r11073-1.el6.noarch.rpm yum clean all; yum makecache yum install systemimager-x86_64boot-standard systemimager-x86_64initrd_template systemimager-server systemimager-common systemimager-client dracut-systemimager All dependancies should be downloaded. If there are still some deps missing, then try to add the EPEL repository (Extended Package for Enterprise Linux. It's a port of many fedora packages). => rpm -ivh http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm Optionally you can install flamethrower, bittorrent and bittorrent-gui packages using yum install but this deployment method is not yet tested. It may or may not work. Please wait until you see version v4.5.0-20170629git in OSCAR repository before trying again. (better version with many minor glitches fixes that I'll publish today). Cheers, - Mail original - > De: "Olivier Lahaye" <olivier.laha...@free.fr> > À: sisuite-users@lists.sourceforge.net > Cc: sisuite-de...@lists.sourceforge.net > Envoyé: Jeudi 29 Juin 2017 09:11:37 > Objet: Re: [Sisuite-devel] [sisuite-users] Net beta release > v4.5.0-20170614git > > Hi David, > > I'll check at work later but it looks like you didn't setup the epel > repo for rhel6/centos6. > Aside that I've built a new release with many cosmetic fixes. I'll > post it today with updated message regarding quick starting. > I'll cross check install on my centos6 physical hardware before > posting. > As Brian said, the real release will end up on systemimager repo. > Which will hosts non epel requirements like BitTorrent, flamethrower, > cx_Freeze and perl Tk-TextANSIColor packages if don't miss any other. > For the moment I'm using Oscar repo as it's easier for me (I'm using > oscar packager tool that does everything for me (build deps, creates > repo) for all distros) > > Envoyé de mon iPhone6+ > > > Le 28 juin 2017 à 18:01, David Livingstone <david.livingst...@cn.ca> > > a écrit : > > > > Olivier, > > > > Okay finally had a change to try and load below on rhel 6.4. From > > the http://svn.oscar.openclustergroup.org/repos/unstable/ link below > > I've gotten to the following : > > > > > > [root@scdev1 2017]# rpm -ivh --test > > systemimager-x86_64boot-standard-4.5.0-0.20170614git.el6.noarch.rpm > > systemimager-x86_64initrd_template-4.5.0-0.20170614git.el6.noarch.rp > > m systemimager-server-4.5.0-0.20170614git.el6.noarch.rpm > > systemimager-common-4.5.0-0.20170614git.el6.noarch.rpm > > systemimager-client-4.5.0-0.20170614git.el6.noarch.rpm > > dracut-systemimager-4.5.0-0.20170615git.el6.noarch.rpm > > perl-Tk-TextANSIColor-0.16-1.noarch.rpm > > systemconfigurator-2.2.12-3.el6.noarch.rpm > > error: Failed dependencies: > >xfsprogs is needed by > >systemimager-server-4.5.0-0.20170614git.el6.noarch > >btrfs-progs is needed by > >dracut-systemimager-4.5.0-0.20170615git.el6.noarch > >dracut-network is needed by > >dracut-systemimager-4.5.0-0.20170615git.el6.noarch > >plymouth-plugin-script is needed by > >dracut-systemimager-4.5.0-0.20170615git.el6.noarch > >xfsprogs is needed by > >dracut-systemimager-4.5.0-0.20170615git.el6.noarch > > [root@scdev1 2017]# > > > > Obviously I am missing some packages however nothing is obvious in > > the link above. > > > > Should I try the Easy install using OSCAR repositories for centos 6 > > ? > > > > Thanks > > David > > > > -Original Message- > > From: LAHAYE Olivier [mailto:olivier.lah...@cea.fr] > > Sent: Wednesday, June 14, 2017 10:25 AM > > To: sisuite-de...@lists.sourceforge.net; > > sisuite-users@lists.sourceforge.net > > Subject: [sisuite-users] Net beta release v4.5.0-20170614git > > > > > > New relase with Plymouth GUI (if "
Re: [sisuite-users] Net beta release v4.5.0-20170614git
Olivier, Okay finally had a change to try and load below on rhel 6.4. From the http://svn.oscar.openclustergroup.org/repos/unstable/ link below I've gotten to the following : [root@scdev1 2017]# rpm -ivh --test systemimager-x86_64boot-standard-4.5.0-0.20170614git.el6.noarch.rpm systemimager-x86_64initrd_template-4.5.0-0.20170614git.el6.noarch.rpm systemimager-server-4.5.0-0.20170614git.el6.noarch.rpm systemimager-common-4.5.0-0.20170614git.el6.noarch.rpm systemimager-client-4.5.0-0.20170614git.el6.noarch.rpm dracut-systemimager-4.5.0-0.20170615git.el6.noarch.rpm perl-Tk-TextANSIColor-0.16-1.noarch.rpm systemconfigurator-2.2.12-3.el6.noarch.rpm error: Failed dependencies: xfsprogs is needed by systemimager-server-4.5.0-0.20170614git.el6.noarch btrfs-progs is needed by dracut-systemimager-4.5.0-0.20170615git.el6.noarch dracut-network is needed by dracut-systemimager-4.5.0-0.20170615git.el6.noarch plymouth-plugin-script is needed by dracut-systemimager-4.5.0-0.20170615git.el6.noarch xfsprogs is needed by dracut-systemimager-4.5.0-0.20170615git.el6.noarch [root@scdev1 2017]# Obviously I am missing some packages however nothing is obvious in the link above. Should I try the Easy install using OSCAR repositories for centos 6 ? Thanks David -Original Message- From: LAHAYE Olivier [mailto:olivier.lah...@cea.fr] Sent: Wednesday, June 14, 2017 10:25 AM To: sisuite-de...@lists.sourceforge.net; sisuite-users@lists.sourceforge.net Subject: [sisuite-users] Net beta release v4.5.0-20170614git New relase with Plymouth GUI (if "splash" or "rhgb" keyword is present in PXE cmdline). What's new in this release: - New GUI dialogbox to display to request keypress when interactive shell is to be triggered (after install if requested or in case of failure. This leave time to read GUI previous messages) - If post install action is non interactive (reboot, poweroff, kexec, ..., the dialogbox will be displayed during 5 seconds and then action will be performed. - enhanced /lib/systemimager-lib.sh (new function to wait for a keypress in gui) - new screenshots Screenshots: - http://svn.oscar.openclustergroup.org/pkgs/downloads/sis_plymouth.png - http://svn.oscar.openclustergroup.org/pkgs/downloads/SIS_CO6.png - http://svn.oscar.openclustergroup.org/pkgs/downloads/sis_success_text.png - http://svn.oscar.openclustergroup.org/pkgs/downloads/sis_failure_text.png - http://svn.oscar.openclustergroup.org/pkgs/downloads/sis_SSH_text.png - http://svn.oscar.openclustergroup.org/pkgs/downloads/sis_SSH_plymouth.png - http://svn.oscar.openclustergroup.org/pkgs/downloads/sis_failure_plymouth.png - http://svn.oscar.openclustergroup.org/pkgs/downloads/sis_success_plymouth.png - http://svn.oscar.openclustergroup.org/pkgs/downloads/si_monitortk.png What works aside cool interface (text or GUI) - bootpackage creation works (si_mkbootpackage) - script creation works (si_mkautoinstallscript) - rsync deployment method works - SSH deployment method works (tested si_pushinstall) (both text anf GUI modes will display a banner asking for si_pushinstall if no ssh keys is available) - grub2 bootloader install works - si_monitortk works fine (see screenshot) Not tested but should work: - grub1 bootloader install (CentOS-6) TODO: - stop cleanly rsync and unmount disks if CTRL-ALT-DEL is pressed during imaging. - fix colormap bug on CENTOS-7 (drm driver bug) - test and eventually fix flamethrower deployment - test and eventually fix bittorrent deployment - update doc with all cmdline new parameters IMHO, this release is as stable as last stable release, though it is less tested so be careful. Source: http://svn.oscar.openclustergroup.org/pkgs/downloads/systemimager-4.5.0.tar.bz2 Repos for RHEL6, RHEL7 and FC25: http://svn.oscar.openclustergroup.org/repos/unstable/ Release number: v4.5.0-20170614git Usual notes: 1/ You must regenerate your install scripts E.g.: /usr/sbin/si_mkautoinstallscript --quiet --autodetect-disks --image oscarimage_sda --force --ip-assignment static --post-install cmdline (--post-install can be shell, reboot, poweroff, cmdline, kexec...) (shell drops a debug shell at the end so you can check what was done) cmdline parameter rd.sis.post-action=shell will drop a shell at the end of imaging. 2/ Easy install using OSCAR repositories - For easy install on CentOS-7: rpm -ivh http://svn.oscar.openclustergroup.org/repos/unstable/rhel-7-x86_64/oscar-release-6.1.2r0-1.el7.centos.noarch.rpm - For easy install on CentOS-6: rpm -ivh http://svn.oscar.openclustergroup.org/repos/unstable/rhel-6-x86_64/oscar-release-6.1.2r11073-1.el6.noarch.rpm - (Not yeat available for FC-25, you must create your repofile by hand or install CentOS-7 package and update /etc/yum.repos.d/oscar.repo) 3/ Note: to setup your PXE, most of relevant cmdline parameters can be found here: (/usr/lib/dracut/modules.d/51systemimager/module-install.sh or install on old
Re: [sisuite-users] Systemimager NG: Working alpha
Olivier - Thanks. Up to this point we are still using RHEL6 which as you know we have working from previous releases. When I attempt the new packages I will let all know. Thanks again David -Original Message- From: LAHAYE Olivier [mailto:olivier.lah...@cea.fr] Sent: Wednesday, April 12, 2017 10:50 AM To: sisuite-de...@lists.sourceforge.net; sisuite-users@lists.sourceforge.net Subject: Re: [sisuite-users] Systemimager NG: Working alpha David L, I reply in the list as this mail contains usefull information for every testers. Cool to here that systemimager is of any interest after such a long time without a working solution on modern distros. Be very carefull as I had difficulties to make RHEL-6 working until the imaging script works (dracut is v004 (we are at v044)) I'm using qemu and centos-6 fails to have a working network on my descktop, so I can't tell if it really works on this release of CentOS. - I end up to getting an IP (works) - Then I fail pingtests (normal on qemu with -net user (only the gateway is pingable and it works) - Then I try to rsync /scripts and it fails with no route to host (while there is a default route that itis correct and a correct IP and I can ping the gateway). Possible problem could be: lack of qemu support in rhel6 kernel Or it can also be a problem in systemimager that forgot to install a low level binary in the initrd and that ends up with a out of subject missleading error message. I hadn't yet the possibility to test on real hardware. but I'll do that soon. Also you must regenerate your imaging scripts as the structure has changed. The good news is that now, the header of the script reports the command line used to generate it. Also you must add the provided post installs scripts (grub setup and network setup). A bad trick could be to use the 86boot package from either rhel-7 or fedora. Those packages only contain matching kernel+initrd and it's a noarch package so even if it's ugly, I think it can work. (of course si_mkbootpackage will remain rhel-6 and generate rhel-6 based initrd, but if you're stuck it could be a viable alternative to use kernel+initrd from fc-25 boot package si_monitortk is able to report the imaging progress, but as I'm using NAT on my VMs I was unable to test if the remote console is working. I forgot to tell that IMAGING_SERVER can be specified on the kernel-cmdline For all possible parameters, have look here: https://github.com/finley/SystemImager/blob/initrd-from-imageserver-and-dont-package-initrd/lib/dracut/modules.d/39systemimager/parse-sis-options.sh (on rhel6, it's parse-sis-options-old.sh) You can also use most dracut.cmdline parameters (man dracut.cmdline) Cheers, Olivier. PS: Tis message should only be on the devel list, but as there is no working solution nowadays, it's good t know for non developpers that in case they really need a systemimager solution, this alpha release could help. >From now, I'll only post on devel for all messages relative to systemimager >devel. -- Olivier LAHAYE CEA -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] SystemImager NG: it works :-)
Olivier - Looks great ! Let me know when you have something to test - I'm still using RHEL 6. Thanks From: LAHAYE Olivier [mailto:olivier.lah...@cea.fr] Sent: Monday, January 26, 2015 4:06 AM To: sisuite-users@lists.sourceforge.net Subject: [sisuite-users] SystemImager NG: it works :-) Hi, I've finaly updated systemimager to work with host OS binaries instead of rebuilding everything. This means that now, the initrd template and the default initrd and kernel are generated using dracut and I only build 3 components: cx_freeze, udpcast and bittorrent client. All other binaries are taken from the host OS and are thus in sync with kernel and drivers (which was not the case in previous release were binaries expected to run with boel kernel 3.7.5 were built on a totaly different kernel and in some circumstance were crashing or failing to built. This is past. I've not yet pushed to git my changes, because I must do some more testing, but the most difficult things are fixed. things that still need to be addressed: - buzybox rpm not available on centos7: do we build it or used standard tools - need to fix list of binaries that we need - test. I hope to release a test rpm in less than 2 weeks, maybe this Friday if I have tilme. Best regards, Olivier. -- Olivier LAHAYE CEA DRT/LIST/DIR -- Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] RE : RE : support newer kernels in systemimager?
Olivier - Just getting back into this ... are these the latest ? Thanks From: LAHAYE Olivier [mailto:olivier.lah...@cea.fr] Sent: Friday, January 24, 2014 4:21 AM To: sisuite-users@lists.sourceforge.net Subject: [sisuite-users] RE : RE : support newer kernels in systemimager? Hi David, thanks a lot for your support :-) The latest beta packages are versionned with 4.3.0-0.16. This releases now builds with perl files installed in INSTALDIRS=vendor (no more use lib /usr/lib/systemimager needed). This version includes the si_monitortk thread warning fix. It is available here: http://svn.oscar.openclustergroup.org/repos/unstable/ The package has been built for rhel-6, debian-6, fedora-17 For the future, as I said, I'm looking forward for any info/doc/script on how to build such a thing: http://ftp.free.fr/mirrors/fedora.redhat.com/fedora/linux/releases/20/Fedora/x86_64/os/images/pxeboot/initrd.img Best regards, Olivier. -- Olivier LAHAYE CEA DRT/LIST/DIR De : David Livingstone [david.livingst...@cn.ca] Date d'envoi : jeudi 23 janvier 2014 21:24 À : sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net Objet : Re: [sisuite-users] RE : support newer kernels in systemimager? Olivier - 2. Definitely sounds like the way to go ... From: LAHAYE Olivier [mailto:olivier.lah...@cea.fr] Sent: Thursday, January 23, 2014 3:00 AM To: sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net Subject: [sisuite-users] RE : support newer kernels in systemimager? Hi, Sorry for not participating often here, I'm extremely buzy working on releasing a new stable OSCAR cluster release that will support many distros. Though, I'm still working on SystemImager. (just fixed si_monitortk thread warning) The current git should support kernels from 2.4 to 3.99 if it ever exists. We have built beta release here: http://svn.oscar.openclustergroup.org/repos/unstable/ For more info, here is my analysis of the current situation and what I'd like to achieve: Problem of the current release is that it fails to build template initrd and kernel on newer distros (like fedora-18+). The problem is that template initrd is based on udev when newer kernels needs latest udev version and build mechanism is not yet designed to build udev without systemd from systemd source tree. IMHO, the way to generate templates is not compatible anymore with the variety of distros and kernel version. rhel6 is using a 2.6, while other distros are using kernel 3.x Building latest kernel and lvm on an old system (rhel6) using installed system kernel includes leads to build failures or runtime crash. 2 solutions for the future: 1/ have different build tree for each distro with apropriate kernel = means old distro won't be supported on recent hardware . typically, our vanilla kernel-2.6 supports far less hardware that patched rhel-6 shipped kernel. = bad idea and very difficult to maintain. 2/ drop the idea to build our kernel and initrd from scratch and instead build the initrd using dracut. Big benefits: a/ we support the same hardware as the linux vendor. even with old kernel. b/ building the rpm is far more faster c/ far more stable. no more lvm built for kernel 3.10 using kernel 2.6 build host system includes. UYOK would still be possible for users having hardware that is not supported by their linux vendor, but for the majority of cases, the templates would be far sufficient. Unfortunately, I'm still searching a doc that tells how to build a non basic initrd. Our case is similar to http://ftp.free.fr/mirrors/fedora.redhat.com/fedora/linux/releases/20/Fedora/x86_64/os/images/pxeboot/initrd.img = If someone can point me to a page that explains how this image is built, that would be AWESOME. It uses systemd and udev for loading hardware drivers and minimal services like network and so. Basicaly it havs everything we need. Then we would just have to add needed binaries (lvm tools, ...) from installed system and (build)our specific stuffs like flamethrower client or bittorent client and replace stage2 loader with our rcS and voila! (cleaner, faster, higher ...;- ) Best regards. -- Olivier LAHAYE CEA DRT/LIST/DIR De : Jan Groenewald [j...@aims.ac.za] Date d'envoi : lundi 20 janvier 2014 07:38 À : sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net Objet : Re: [sisuite-users] support newer kernels in systemimager? Hi This file 0 root@muizenberg:/usr/lib/systemimager/perl/SystemImager#dpkg -S UseYourOwnKernel.pm systemimager-common: /usr/lib/systemimager/perl/SystemImager/UseYourOwnKernel.pm Checks the kernel version and throws an error for newer kernels. This patch allows me to use some 3.X kernels 1 root@muizenberg:/usr/lib/systemimager/perl/SystemImager#cat UseYourOwnKernel.pm.patch --- UseYourOwnKernel.pm.orig2012-05-30 17:05:54.899344781 +0200
Re: [sisuite-users] RE : RE : support newer kernels in systemimager?
Olivier - Thanks ! I will download and give it a try. Please keep me in the loop. BTW I am off to Red Hat Summit this year in San Francisco ... David From: LAHAYE Olivier [mailto:olivier.lah...@cea.fr] Sent: Friday, January 24, 2014 4:21 AM To: sisuite-users@lists.sourceforge.net Subject: [sisuite-users] RE : RE : support newer kernels in systemimager? Hi David, thanks a lot for your support :-) The latest beta packages are versionned with 4.3.0-0.16. This releases now builds with perl files installed in INSTALDIRS=vendor (no more use lib /usr/lib/systemimager needed). This version includes the si_monitortk thread warning fix. It is available here: http://svn.oscar.openclustergroup.org/repos/unstable/ The package has been built for rhel-6, debian-6, fedora-17 For the future, as I said, I'm looking forward for any info/doc/script on how to build such a thing: http://ftp.free.fr/mirrors/fedora.redhat.com/fedora/linux/releases/20/Fedora/x86_64/os/images/pxeboot/initrd.img Best regards, Olivier. -- Olivier LAHAYE CEA DRT/LIST/DIR De : David Livingstone [david.livingst...@cn.ca] Date d'envoi : jeudi 23 janvier 2014 21:24 À : sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net Objet : Re: [sisuite-users] RE : support newer kernels in systemimager? Olivier - 2. Definitely sounds like the way to go ... From: LAHAYE Olivier [mailto:olivier.lah...@cea.fr] Sent: Thursday, January 23, 2014 3:00 AM To: sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net Subject: [sisuite-users] RE : support newer kernels in systemimager? Hi, Sorry for not participating often here, I'm extremely buzy working on releasing a new stable OSCAR cluster release that will support many distros. Though, I'm still working on SystemImager. (just fixed si_monitortk thread warning) The current git should support kernels from 2.4 to 3.99 if it ever exists. We have built beta release here: http://svn.oscar.openclustergroup.org/repos/unstable/ For more info, here is my analysis of the current situation and what I'd like to achieve: Problem of the current release is that it fails to build template initrd and kernel on newer distros (like fedora-18+). The problem is that template initrd is based on udev when newer kernels needs latest udev version and build mechanism is not yet designed to build udev without systemd from systemd source tree. IMHO, the way to generate templates is not compatible anymore with the variety of distros and kernel version. rhel6 is using a 2.6, while other distros are using kernel 3.x Building latest kernel and lvm on an old system (rhel6) using installed system kernel includes leads to build failures or runtime crash. 2 solutions for the future: 1/ have different build tree for each distro with apropriate kernel = means old distro won't be supported on recent hardware . typically, our vanilla kernel-2.6 supports far less hardware that patched rhel-6 shipped kernel. = bad idea and very difficult to maintain. 2/ drop the idea to build our kernel and initrd from scratch and instead build the initrd using dracut. Big benefits: a/ we support the same hardware as the linux vendor. even with old kernel. b/ building the rpm is far more faster c/ far more stable. no more lvm built for kernel 3.10 using kernel 2.6 build host system includes. UYOK would still be possible for users having hardware that is not supported by their linux vendor, but for the majority of cases, the templates would be far sufficient. Unfortunately, I'm still searching a doc that tells how to build a non basic initrd. Our case is similar to http://ftp.free.fr/mirrors/fedora.redhat.com/fedora/linux/releases/20/Fedora/x86_64/os/images/pxeboot/initrd.img = If someone can point me to a page that explains how this image is built, that would be AWESOME. It uses systemd and udev for loading hardware drivers and minimal services like network and so. Basicaly it havs everything we need. Then we would just have to add needed binaries (lvm tools, ...) from installed system and (build)our specific stuffs like flamethrower client or bittorent client and replace stage2 loader with our rcS and voila! (cleaner, faster, higher ...;- ) Best regards. -- Olivier LAHAYE CEA DRT/LIST/DIR De : Jan Groenewald [j...@aims.ac.za] Date d'envoi : lundi 20 janvier 2014 07:38 À : sisuite-users@lists.sourceforge.netmailto:sisuite-users@lists.sourceforge.net Objet : Re: [sisuite-users] support newer kernels in systemimager? Hi This file 0 root@muizenberg:/usr/lib/systemimager/perl/SystemImager#dpkg -S UseYourOwnKernel.pm systemimager-common: /usr/lib/systemimager/perl/SystemImager/UseYourOwnKernel.pm Checks the kernel version and throws an error for newer kernels. This patch allows me to use some 3.X kernels 1 root@muizenberg:/usr/lib/systemimager/perl/SystemImager#cat UseYourOwnKernel.pm.patch
Re: [sisuite-users] beta7 bug fixed = beta8 WAS: systemimager 4.3.0-0.7 available for testing
Olivier,
Finally had a chance to test from a client running beta8 to a server
running beta8. Both client and server are running rhel 6.4 x86_64.
- I prepared the images as both uyok and without and both worked. No
problem with the getimage from the server.
- I then attempted to load the client with the image I had created. I
attempted this with both the standard kernel and the uyok.
Both worked up to the point in the script when lvcreate was executed. At
this point the load/system would hang(reset required).
See the log below. To restore I loaded from a server running a slightly
older version( systemimager-server-4.3.0-0.2.el6.noarch)
which did not have this problem.
Also note for reasons I have stated in the past I also modified
UseYourOwnKernel.pm as follows :
[root@wild1 130408]# diff
/usr/lib/systemimager/perl/SystemImager/UseYourOwnKernel.pm
UseYourOwnKernel.pm
152c152
$cmd = qq(rsync -a --exclude=build --exclude=source ) .
---
$cmd = qq(rsync -aL --exclude=build --exclude=source ) .
159c159
$cmd = qq(rsync -aR $module $staging_dir);
---
$cmd = qq(rsync -aLR $module $staging_dir);
222a223,233
#
# Copy /lib/firmware file to initrd
#
#
if (-d /lib/firmware) {
# copy firmware tree to new initrd.
$cmd = qq(rsync -aLR /lib/firmware $staging_dir);
!system( $cmd ) or die( Couldn't $cmd. );
}
Log of failed boot :
parted -s -- /dev/sda set 2 lvm on
logger: logger: parted /dev/sda set 2 lvm on
New partition table for /dev/sda:
parted -s -- /dev/sda print
Model: HP LOGICAL VOLUME (scsi)
Disk /dev/sda: 300GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End SizeType File system Flags
1 512B1000MB 1000MB primary boot
2 1000MB 300GB 299GB primary lvm
Load software RAID modules.
Load device mapper driver (for LVM).
Initializing partition /dev/sda2 for use by LVM.
pvcreate -M2 -ff -y /dev/sda2 || shellout
WARNING: Forcing physical volume creation on /dev/sda2 of volume group
rootvg
Physical volume /dev/sda2 successfully created
lvremove -f /dev/rootvg /dev/null 21 vgremove rootvg /dev/null 21
vgcreate -M2 -l 0 -p 0 -s 32768K rootvg /dev/sda2 || shellout
Volume group rootvg successfully created
lvcreate -L16777216K -n LogVol01 rootvg || shellout
David K Livingstone
CN Signals and Communications
10229 127 Avenue floor 2
Walker Operations East Building
Edmonton, AB, T5E 0B9
Ph : 780 472-3959 Fax : 780 472-3046
Email: david.livingst...@cn.ca
- Forwarded by David Livingstone/LIVING03/CNR/CA on 2013/04/17 15:14
-
From:
david.livingst...@cn.ca
To:
sisuite-users@lists.sourceforge.net
Date:
2013/04/10 15:56
Subject:
Re: [sisuite-users] beta7 bug fixed = beta8 WAS: systemimager 4.3.0-0.7
available for testing
Olivier,
Thanks. That does it. I still need to test loading the image. I will let
you know.
David
David K Livingstone
CN Signals and Communications
From:
LAHAYE Olivier olivier.lah...@cea.fr
To:
sisuite-users@lists.sourceforge.net
sisuite-users@lists.sourceforge.net
Date:
2013/04/08 06:37
Subject:
[sisuite-users] beta7 bug fixed = beta8 WAS: systemimager 4.3.0-0.7
available for testing
Hi,
The issue has been fixed.
I wonder how it could work on V0.2. There were 2 bugs:
One that I introduced when I wanted to match kernel 3.x kernels with x 2
But there was also a bug in initrd detection. the routine was unable to
check for initramfs files. If no initrd file was available, the error
should have triggered as well
Anyway,
It's hopefully fixed and should be available shortly for fedora, rhel-6
and debian-7-x86_64 soon here:
http://svn.oscar.openclustergroup.org/repos/unstable/
The source rpm (and tarball) will be available here soon as well:
http://svn.oscar.openclustergroup.org/pkgs/downloads/
--
Olivier LAHAYE
CEA DRT/LIST/DCSI/DIR
De : LAHAYE Olivier
Date d'envoi : lundi 8 avril 2013 09:24
À : sisuite-users@lists.sourceforge.net
Objet : RE : [sisuite-users] systemimager 4.3.0-0.7 available for testing
Hi,
Thanks a lot for this report, I'll try to understand the issue ASAP.
0.2 has the same code as 0.7 (differences are on the initrd and boot
packages which are very different).
Regards,
Olivier.
--
Olivier LAHAYE
CEA DRT/LIST/DCSI/DIR
De : david.livingst...@cn.ca [david.livingst...@cn.ca]
Date d'envoi : samedi 6 avril 2013 00:44
À : sisuite-users@lists.sourceforge.net
Objet : Re: [sisuite-users] systemimager 4.3.0-0.7 available for testing
Olivier,
I installed on a rhel 6.4 client and get the below error message when
attempting to prepare the client. If I install
4.3.0-0.2 this does not happen.
systemimager-common-4.3.0-0.7.el6.noarch
systemimager-x86_64initrd_template-4.3.0-0.7.el6.noarch
systemimager-client
Re: [sisuite-users] systemimager 4.3.0-0.7 available for testing
Olivier, I installed on a rhel 6.4 client and get the below error message when attempting to prepare the client. If I install 4.3.0-0.2 this does not happen. systemimager-common-4.3.0-0.7.el6.noarch systemimager-x86_64initrd_template-4.3.0-0.7.el6.noarch systemimager-client-4.3.0-0.7.el6.noarch - same error on vccs3 using --no-uyok and without - We get : - [root@mtl-vccs03d ~]# si_prepareclient --no-uyok --server 165.115.83.125 ... This client is ready to have its image retrieved. You must now run the si_getimage command on your imageserver. Automatically create configuration file for systemconfigurator: /etc/systemconfig/systemconfig.conf WARNING: unable to auto-detect kernel file! WARNING: coulnd't create file /etc/systemconfig/systemconfig.conf (needed by systemconfigurator) [root@mtl-vccs03d ~]# David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Walker Operations East Building Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3046 Email: david.livingst...@cn.ca - Forwarded by David Livingstone/LIVING03/CNR/CA on 2013/04/05 16:40 - From: David Livingstone/LIVING03/CNR/CA To: sisuite-users@lists.sourceforge.net Date: 2013/03/21 11:40 Subject: Re: [sisuite-users] systemimager 4.3.0-0.7 available for testing Olivier, Thanks ! I will download and test on rhel 6.x). BTW I am currently using your previous build(4.3.0-0.2 std kernel only) on rhel 6.x with the restrictions we have corresponded about. David David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Walker Operations East Building Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3046 Email: david.livingst...@cn.ca From: LAHAYE Olivier olivier.lah...@cea.fr To: sisuite-users@lists.sourceforge.net sisuite-users@lists.sourceforge.net Date: 2013/03/20 10:17 Subject: [sisuite-users] systemimager 4.3.0-0.7 available for testing Hi, I've uploaded the rpms for systemimager beta version V4.3.0 (beta7) I've built it for fedora-17 and centos-6.3 They are available here: http://olivier.lahaye1.free.fr/OSCAR/repos/unstable/ Note that you can install the oscar-release rpm which will setup the yum.repo.d/oscar.repo. Usage notes: - The pre install script required to modprobe disk controlers is not required anymore. (leave comments in it) - the post install scripts (si_scripts.tar.bz2) are usefull for grub setup (systemconfigurator not yet ported for new grub, grub2 and other bootloaders and Network manager) Just comment everything in the pre_install script. Firmwares available in the image are those that can be built from the kernel source tree. No external firmware is provided yet (need to check EULA). Please keep in mind that this is a testing release. If you have a systemimager that is in production, don't upgrade). Happy testing. -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] systemimager 4.3.0-0.7 available for testing
Olivier, Thanks ! I will download and test on rhel 6.x). BTW I am currently using your previous build(4.3.0-0.2 std kernel only) on rhel 6.x with the restrictions we have corresponded about. David David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Walker Operations East Building Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3046 Email: david.livingst...@cn.ca From: LAHAYE Olivier olivier.lah...@cea.fr To: sisuite-users@lists.sourceforge.net sisuite-users@lists.sourceforge.net Date: 2013/03/20 10:17 Subject: [sisuite-users] systemimager 4.3.0-0.7 available for testing Hi, I've uploaded the rpms for systemimager beta version V4.3.0 (beta7) I've built it for fedora-17 and centos-6.3 They are available here: http://olivier.lahaye1.free.fr/OSCAR/repos/unstable/ Note that you can install the oscar-release rpm which will setup the yum.repo.d/oscar.repo. Usage notes: - The pre install script required to modprobe disk controlers is not required anymore. (leave comments in it) - the post install scripts (si_scripts.tar.bz2) are usefull for grub setup (systemconfigurator not yet ported for new grub, grub2 and other bootloaders and Network manager) Just comment everything in the pre_install script. Firmwares available in the image are those that can be built from the kernel source tree. No external firmware is provided yet (need to check EULA). Please keep in mind that this is a testing release. If you have a systemimager that is in production, don't upgrade). Happy testing. -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[sisuite-users] systemimager-4.3.0-0.3 (kernel 3.7.2, hpsa, bnx2, ...) (For testing purpose).
Second attempt after the first one bounced due to size ... David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Walker Operations East Building Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3046 Email: david.livingst...@cn.ca - Forwarded by David Livingstone/LIVING03/CNR/CA on 2013/01/24 09:34 - From: David Livingstone/LIVING03/CNR/CA To: olivier.lah...@cea.fr Date: 2013/01/24 09:03 Subject: Fw: [sisuite-users] systemimager-4.3.0-0.3 (kernel 3.7.2, hpsa, bnx2, ...) (For testing purpose). Olivier, Just received a reply from the list saying the post exceeded the limit and it needs to be approved by the moderator ... In the meantime her is the post sent directly to you ! I was running out the door last night when I posted and forgot to answer your question : - I included the rsync -L option(as described below with a snippet from my original post) because unfortunately this is the default result when applying the HP spp(firmware and driver updates) to an HPserver. The first time an spp is applied to a server the HP updated driver is applied correctly to the /lib/modules/kernel tree. If you subsequently upgrade your kernel and then apply an spp again then the a link is made rather then the module being copied(as shown below). Yes I could fight HP/redhat on this however I don't have the time or energy ... - Needed modules(ie hpsa) as symbolic links under /lib/modules/(uname -r) ex [root@scdev ~]# ls -al /lib/modules/2.6.32-220.4.2.el6.i686/weak-updates/hpsa/hpsa.ko 0 lrwxrwxrwx 1 root root 50 Mar 5 04:05 /lib/modules/2.6.32-220.4.2.el6.i686/weak-updates/hpsa/hpsa.ko - /lib/modules/2.6.32-71.el6.i686/extra/hpsa/hpsa.ko [root@scdev ~]# This results in the modules not being copied correctly in the generated initrd. I resolved this by modifying the UseYourOwnKernel.pm rsync invocations to copy the resultant files(the L rather then the l option. I include the diff below. David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Walker Operations East Building Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3046 Email: david.livingst...@cn.ca - Forwarded by David Livingstone/LIVING03/CNR/CA on 2013/01/24 08:51 - From: David Livingstone/LIVING03/CNR/CA To: sisuite-users@lists.sourceforge.net Date: 2013/01/23 16:51 Subject: Re: [sisuite-users] systemimager-4.3.0-0.3 (kernel 3.7.2, hpsa, bnx2, ...) (For testing purpose). Olivier, I just attempted to load an x86_64 machine using your previous build with my changes applied as described in my email below. I haven't yet had a chance to look at your new build. - I attempted a boot using the standard kernel/initd and : - the dhclient DEVICE failed. Later in the shell with dhclient -v eth1) it turns out the interface was not up. After doing a ifconfig eth1 up the dhclinet eth1 is now is successful however now it attempts to write the lease into /var/db/dhclient.leases rather then the expected /var/state/dhcp/... Did you ever get a dhclient boot to work ? - also during booting requested firmware was hanging ie netxen_nic:...: firmware: requesting phanfw.bin See below with uyok. - I eventually tried setting all the IP parameters and IMAGESERVER in the pxelinux.cfg file which bypasses dhclient. At this point we now fail because there is no hpsa module loaded and no disks are visible. -The uyok load fails as once again numerous firmware files fail to load. This problem did not happen with my initial test setup using the 4.1.99.svn4556_bli-1 packages but does with 4.3.0-0.2.el6. In this case the firmware files are in the initrd however what appears to have changed is that the firmware loading code changed from a shell script (firmware.sh) to a binary. See https://bugzilla.redhat.com/show_bug.cgi?id=560031 The 4.1.99.svn4556_bli-1 package systemimager-i386initrd_template-4.1.99.svn4556_bli-1.noarch has : [root@nasedm udev]# pwd /usr/share/systemimager/boot/i386/standard/initrd_template/lib/udev [root@nasedm udev]# ls total 132 12 ata_id* 8 collect*12 edd_id* 12 path_id* 24 scsi_id* 12 vol_id* 4 write_net_rules* 8 cdrom_id* 12 create_floppy_devices* 4 firmware.sh* 4 rule_generator.functions 16 usb_id*4 write_cd_rules* [root@nasedm udev]# And the systemimager-x86_64initrd_template-4.3.0-0.2.el6.noarch has : [root@wild1 udev]# pwd /usr/share/systemimager/boot/x86_64/standard/initrd_template/lib/udev [root@wild1 udev]# ls total 356 24 ata_id*12 collect*20 edd_id*20 fstab_import* 36 path_id* 40 usb_id* 4 write_cd_rules* 36 cdrom_id* 44 create_floppy_devices* 44 firmware* 32 input_id* 32 scsi_id* 8 v4l_id* 4 write_net_rules* [root@wild1 udev]# The original firmware.sh is invoked in the /usr/share/systemimager/boot/i386/standard/initrd_template/etc/udev/rules.d/80
Re: [sisuite-users] RE : Which version ?
Olivier, Thanks. So far I have installed the rpm's on a dl380G7 with rhel6.3 x86_64 and both prepared the image(uyok) and retrieved from a similar server with the server packages loaded.Next step will be to test load the image on another server using both the standard and uyok ( I'm a little gun shy tryingto load back to the same server incase there are problems). I also re-applied the changes I've itemized below for the same reasons - btw the change below to rcS(start udev BEFORE load_my_modules) might address why you had similar problems ie needing the pre-install script to load the modules). - David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Walker Operations East Building Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3046 Email: david.livingst...@cn.ca From: LAHAYE Olivier olivier.lah...@cea.fr To: sisuite-users@lists.sourceforge.net sisuite-users@lists.sourceforge.net Date: 2013/01/07 02:05 Subject: [sisuite-users] RE : Which version ? Hi, You can try the 4.3.0-0.1svn version, it worked for me. You'll need pre and post-install scripts available here: http://olivier.lahaye1.free.fr/RPMS/extra/ Cheers, -- Olivier LAHAYE CEA DRT/LIST/DCSI/DIR De : david.livingst...@cn.ca [david.livingst...@cn.ca] Date d'envoi : mercredi 19 décembre 2012 00:09 À : sisuite-users@lists.sourceforge.net Objet : [sisuite-users] Which version ? I have been using a modified version of 4.1.99.svn4556_bli-1 to load my i386 rhel6.x servers as described below. I am now looking at imaging similar machines but now with the x86_64 version of rhel6.3 so I need like initrd_template( and boot_standard if it works) packages. What versions should I be trying ? http://olivier.lahaye1.free.fr/RPMS/noarch/ ?? Thanks David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Walker Operations East Building Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3046 Email: david.livingst...@cn.ca - Forwarded by David Livingstone/LIVING03/CNR/CA on 2012/12/18 16:00 - From: David Livingstone/LIVING03/CNR/CA To: sisuite-users@lists.sourceforge.net Date: 2012/03/29 09:41 Subject: Loading RHEL 6.2 using 4.1.99.svn4556_bli-1 Using systemimager 4.1.99.svn4556_bli-1(ext4 enabled version) I have successfully imaged a RHEL 6.2 image to HP DL380G7 hardware(p410 array controllers). I was considering using SALI however for RHEL6.x grub2 is not an issue and ext4 support is included in 4.1.99.svn4556_bli-1. The setup I was imaging is a Proliant DL380G7 server with two p410 controllers(p401i and p410) with raid1 for root/boot/swap on the p410i and raid5 for /data on the p410. The system is running the latest RHEL 6.2. The attempted to image the system in two ways: 1. standard kernel 2. uyok 1. standard kernel I eventually got this to work but only after major modifications to the install script and manually setting up grub. The major issue here is that the default kernel uses the cciss driver and device naming(ex /dev/cciss/c0d0p2) and the RHEL6.x uses the hpsa driver(scsi naming ex /dev/sda). See http://h2.www2.hp.com/bc/docs/support/SupportManual/c02677069/c02677069.pdf . In general RHEL 5.x and before uses the cciss driver and RHEL6.x uses the hpsa when possible. I presume the standard kernel could be built with the hpsa module and some version logic applied to resolve this. 2. uyok This worked successfully after making some changes to address : - Needed modules(ie hpsa) as symbolic links under /lib/modules/(uname -r) ex [root@scdev ~]# ls -al /lib/modules/2.6.32-220.4.2.el6.i686/weak-updates/hpsa/hpsa.ko 0 lrwxrwxrwx 1 root root 50 Mar 5 04:05 /lib/modules/2.6.32-220.4.2.el6.i686/weak-updates/hpsa/hpsa.ko - /lib/modules/2.6.32-71.el6.i686/extra/hpsa/hpsa.ko [root@scdev ~]# This results in the modules not being copied correctly in the generated initrd. I resolved this by modifying the UseYourOwnKernel.pm rsync invocations to copy the resultant files(the L rather then the l option. I include the diff below. - Numerous /lib/firmware files were missing in the initrd. By default the bnx2 nic driver(driver for the four nic's on the motherboard) as well as others in the RHEL6.2 kernel request firmware which is missing in the uyok initrd. I got this to work by : - modifying UseYourOwnKernel.pm to copy /lib/firmware to the initrd. Unfortunately this copies all of firmware as I couldn't figure out how to dynamically copy what was needed. - modified rcS under the std template to start udev BEFORE the modules are inserted. - rcS : start udev before loading modules. - under the std template : /usr/share/systemimager/boot/i386/standard/initrd_template/etc/init.d/rcS - The ramdisk_size must be set
[sisuite-users] Which version ?
I have been using a modified version of 4.1.99.svn4556_bli-1 to load my
i386 rhel6.x servers as
described below. I am now looking at imaging similar machines but now with
the x86_64 version
of rhel6.3 so I need like initrd_template( and boot_standard if it works)
packages.
What versions should I be trying ?
http://olivier.lahaye1.free.fr/RPMS/noarch/ ??
Thanks
David K Livingstone
CN Signals and Communications
10229 127 Avenue floor 2
Walker Operations East Building
Edmonton, AB, T5E 0B9
Ph : 780 472-3959 Fax : 780 472-3046
Email: david.livingst...@cn.ca
- Forwarded by David Livingstone/LIVING03/CNR/CA on 2012/12/18 16:00
-
From:
David Livingstone/LIVING03/CNR/CA
To:
sisuite-users@lists.sourceforge.net
Date:
2012/03/29 09:41
Subject:
Loading RHEL 6.2 using 4.1.99.svn4556_bli-1
Using systemimager 4.1.99.svn4556_bli-1(ext4 enabled version) I have
successfully imaged a
RHEL 6.2 image to HP DL380G7 hardware(p410 array controllers). I was
considering using SALI
however for RHEL6.x grub2 is not an issue and ext4 support is included in
4.1.99.svn4556_bli-1.
The setup I was imaging is a Proliant DL380G7 server with two p410
controllers(p401i and p410)
with raid1 for root/boot/swap on the p410i and raid5 for /data on the
p410. The system is running
the latest RHEL 6.2.
The attempted to image the system in two ways:
1. standard kernel
2. uyok
1. standard kernel
I eventually got this to work but only after major modifications to
the install script and manually
setting up grub. The major issue here is that the default kernel uses
the cciss driver and
device naming(ex /dev/cciss/c0d0p2) and the RHEL6.x uses the hpsa
driver(scsi naming ex /dev/sda).
See
http://h2.www2.hp.com/bc/docs/support/SupportManual/c02677069/c02677069.pdf
.
In general RHEL 5.x and before uses the cciss driver and RHEL6.x uses
the hpsa when possible.
I presume the standard kernel could be built with the hpsa module and
some version logic
applied to resolve this.
2. uyok
This worked successfully after making some changes to address :
- Needed modules(ie hpsa) as symbolic links under
/lib/modules/(uname -r)
ex
[root@scdev ~]# ls -al
/lib/modules/2.6.32-220.4.2.el6.i686/weak-updates/hpsa/hpsa.ko
0 lrwxrwxrwx 1 root root 50 Mar 5 04:05
/lib/modules/2.6.32-220.4.2.el6.i686/weak-updates/hpsa/hpsa.ko -
/lib/modules/2.6.32-71.el6.i686/extra/hpsa/hpsa.ko
[root@scdev ~]#
This results in the modules not being copied correctly in the
generated initrd.
I resolved this by modifying the UseYourOwnKernel.pm rsync
invocations
to copy the resultant files(the L rather then the l option. I
include the diff
below.
- Numerous /lib/firmware files were missing in the initrd. By default
the
bnx2 nic driver(driver for the four nic's on the motherboard) as
well as
others in the RHEL6.2 kernel request firmware which is missing in
the
uyok initrd. I got this to work by :
- modifying UseYourOwnKernel.pm to copy /lib/firmware to the
initrd.
Unfortunately this copies all of firmware as I couldn't figure
out how to
dynamically copy what was needed.
- modified rcS under the std template to start udev BEFORE the
modules
are inserted.
- rcS : start udev before loading modules.
- under the std template :
/usr/share/systemimager/boot/i386/standard/initrd_template/etc/init.d/rcS
- The ramdisk_size must be set high enough to accept the larger
initrd.
- I had to si_cpimage as part of testing and noted that for yuok the
kernel and initrd.img files are not copied. They had to be copied
manually.
Notes :
When creating the image initially I also had to change si_prepareclient
to use parted rather then sfdisk. I believe a bug
was submitted on this a long time ago which was never applied. parted
supports gpt
partitions and sfdisk does not.
[root@nasmtl sbin]# diff si_prepareclient
si_prepareclient.orig.4.1.99.svn4556_bli
969,971c969,971
#if($arch eq i386) {
#$preferred_tool = 'sfdisk';
#}
---
if($arch eq i386) {
$preferred_tool = 'sfdisk';
}
- Diff for UseYourOwnKernel.pm
[root@nasmtl SystemImager]# diff UseYourOwnKernel.pm
UseYourOwnKernel.pm.orig
152c152
$cmd = qq(rsync -aL --exclude=build --exclude=source ) .
---
$cmd = qq(rsync -a --exclude=build --exclude=source ) .
159c159
$cmd = qq(rsync -aLR $module $staging_dir);
---
$cmd = qq(rsync -aR $module $staging_dir);
223,225d222
#
# Copy /lib/firmware file to initrd
#
227,233d223
if (-d /lib/firmware) {
# copy entire firmware tree to new initrd.
$cmd = qq(rsync -aLR /lib/firmware $staging_dir);
!system( $cmd ) or die( Couldn't $cmd. );
}
- Diff for rcS :
[root
[sisuite-users] rhel6 - ext4 support
Is there a timeframe to have ext4 support ? Thanks David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Walker Operations East Building Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3046 Email: david.livingst...@cn.ca -- Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Saving image to USB Drive?
Bernard Li bern...@vanhpc.org wrote on 2009/07/09 15:36:21: Hi Jim: On Thu, Jul 9, 2009 at 1:10 PM, jimi o'beirnejimobei...@gmail.com wrote: Thank you. Unfortunately, I don't think moving my entire /var/lib dir to the external hard drive is an option I'd like to take on. Far too much other data within that directory. Seems a shame we can't just point SystemImager to whatever directory we want to save the image to. I was suggesting that you mount /var/lib/systemimager/images somewhere else, not the entire /var/lib directory. Alternatively, sounds like what MIke suggested is an easier way to get around your issue. I have /var/lib/systemimager as a symbolic link to my external array /data/systemimager. More; the system I am trying to image is a Dell XPS 710 Ubuntu Jaunty w/software RAID controlling 2x 500G drives which house the Ubuntu install. Additionally, it has 2x NVidia GeForce 8800's, another graphics accelerator card, Soundblaster 5.1 surround sound card, etc so this thing is a bear to have to reinstall with all the different config changes/edits I have to do to get everything running. Because of the NVidia software RAID, I have to use the alternate CD to install the OS, and that also means that all of the other clone/ghost software I have found does not support the software RAID. I can't even use a Live CD to do dd as it won't see the RAID drives. Quite the challenge. I haven't even found a truly decent backup program to handle imaging the system either. I'm just tired of having to rebuild this thing from scratch every time something goes awry. The last time a week ago was an update that toasted my video config and I couldn't get the custom xorg.conf to take so had to flatten it and rebuild again, (which I have done over the last 6 months no less than a dozen times!) Instead of using Nvidia's software raid, how about using md? Would that be possible? SystemImager in theory could setup software raid using md for you, however, I don't typically use si_getimage so I don't know how well it would detect your raid and put it in the autoinstallscript. Cheers, Bernard -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users-- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] SI, XEN, FC6 wheeee
Patch applied and yes this solves the problem. Have not yet had a chance
to image
to a client.
Thanks
David K Livingstone
CN Signals and Communications
10229 127 Avenue floor 2
Edmonton, AB, T5E 0B9
Ph : 780 472-3959 Fax : 780 472-3050
Email: [EMAIL PROTECTED]
Andrea Righi [EMAIL PROTECTED]
2008/02/20 07:39
Please respond to
[EMAIL PROTECTED]
To
[EMAIL PROTECTED], Tory M Blue [EMAIL PROTECTED]
cc
sisuite-users@lists.sourceforge.net
Subject
Re: [sisuite-users] SI, XEN, FC6 wh
Andrea Righi wrote:
Tory M Blue wrote:
note what it's in my grub.conf after the mess
# This file is generated by System Configurator. #
##
# The number of seconds to wait before booting.
timeout 5
# The default kernel image to boot.
default 0
# The splash image (this line will be empty if nothing was found)
splashimage=/grub/splash.xpm.gz
# kernel0
title fc6xen-virt_
root
kernel ro root=LABEL=/ ro root=LABEL=/ console=xvc0
initrd
We also need to patch UYOK stuff. See create_systemconfig_conf() in
sbin/si_prepareclient.
Tory, David,
could you check if the following patch fixes both your problems?
Thanks,
-Andrea
---
Index: lib/SystemImager/UseYourOwnKernel.pm
===
--- lib/SystemImager/UseYourOwnKernel.pm(revision 4390)
+++ lib/SystemImager/UseYourOwnKernel.pm(working copy)
@@ -345,18 +345,30 @@
#
# and not a directory
if( -d $file ) { return undef; }
+#
+# skip symlinks
+if( -l $file ) { return undef; }
+#
+# skip .bak files
+if( $file =~ /\.bak$/ ) { return undef; }
+#
+# eliminate vmlinux files on RH
+if( $file =~ m/^vmlinux$/ ) { return undef; }
+#
+# eliminate ramdisks
+if( $file =~ m/initrd/ ) { return undef; }
+#
+# eliminate memtest
+if( $file =~ m/^memtest/ ) { return undef; }
+#
+# eliminate message
+if( $file =~ m/^message/ ) { return undef; }
#
# Get output from file for elimination by identification tests
-my $cmd = file -b $file;
+my $cmd = file -bz $file;
open(INPUT,$cmd|) or die(Couldn't run $cmd to get INPUT);
my ($input) = (INPUT);
-#
-# eliminate vmlinux files on RH
-if( $input =~ m/ELF (32|64)-bit LSB executable,/ ) {
return undef; }
-#
-# eliminate compressed data (eg. ramdisk)
-if( $input =~ m/gzip compressed data,/ ) { return undef;
}
# eliminate cpio archives (eg. ramdisk)
if( $input =~ m/cpio archive/ ) { return undef; }
# eliminate cramfs files (eg. ramdisk)
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
sisuite-users mailing list
sisuite-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] [ RFC ] SystemImager 4.0.2 or not? (was: client netboot fails (rsync: failed to set times))
Andrea, I've read all the responses and there are merits to both 1 and 2 as well as Bernard Li's response. - My vote goes for 2. - should not have binaries availble which are broken and this will fix the current problem without introducing any other issues. - option 1 should be released a 4.0.1( ie pre release of 4.0.2) and tested. Thanks David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3050 Email: [EMAIL PROTECTED] Andrea Righi [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 2007/11/07 16:29 Please respond to [EMAIL PROTECTED]; Please respond to sisuite-users@lists.sourceforge.net To Brian Elliott Finley [EMAIL PROTECTED], Erich Focht [EMAIL PROTECTED], Bernard Li [EMAIL PROTECTED] cc sisuite-dev s [EMAIL PROTECTED], sisuite-users sisuite-users@lists.sourceforge.net Subject [sisuite-users] [ RFC ] SystemImager 4.0.2 or not? (was: client netboot fails (rsync: failed to set times)) Hi all, it seems that someone is agree with me and someone is not about the solution to add the pre-release of rsync (3.0.0pre4) into the stable branch of SystemImager and tag the new 4.0.2 stable ASAP (4.0.1, since .1 is odd, is reserved for development pre-releases). So, probably this is the first polling in these lists :-), don't know, but I would really like to know opinion of the community about this issue. The fact is that the current stable release of SystemImager 4.0.0 is not stable enough: there is a bug that occurs with rsync when it's built on a machine with a kernel = 2.6.22 (that's actually my build server) and the installing client uses a kernel 2.6.22: See http://www.systemimager.org:8000/trac.systemimager.org/ticket/6 for details, many thanks to Rochus Schmid for reporting this bug. The proposed solutions for now are: 1) use the pre-release of rsync that seems to fix the problem and tag SystemImager 4.0.2, leaving the 4.0.0 packages as they are, let me say that I would just proceed like the kernel guys do if there's a bug in the kernel (just leave all the previous released kernels forzen and available for download in any case, and always release new versions in case of errors/bugs) 2) remove the old 4.0.0 packages from SF.net (let me say close them to the users), rebuild all the packages in a build server with a kernel 2.6.22 and then release the new packages using the same version number: 4.0.0 3) rebuild the packages in a build server with a kernel 2.6.22 and changing the version number to 4.0.2, leaving 4.0.0 packages as they are on SF.net 4) other ideas are welcome... I vote for 1). -Andrea - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] [ RFC ] SystemImager 4.0.2 or not? (was: client netboot fails (rsync: failed to set times))
Of course I had already loaded 4.0.0 on my image server and as of today was looking at loading a machine(RH ES 4). I will download the pre-release packages and test. David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3050 Email: [EMAIL PROTECTED] Andrea Righi [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 2007/11/08 11:43 Please respond to [EMAIL PROTECTED]; Please respond to sisuite-users@lists.sourceforge.net To sisuite-users@lists.sourceforge.net cc Subject Re: [sisuite-users] [ RFC ] SystemImager 4.0.2 or not? (was: client netboot fails (rsync: failed to set times)) [EMAIL PROTECTED] wrote: Andrea, I've read all the responses and there are merits to both 1 and 2 as well as Bernard Li's response. - My vote goes for 2. - should not have binaries availble which are broken and this will fix the current problem without introducing any other issues. - option 1 should be released a 4.0.1( ie pre release of 4.0.2) and tested. Well... I've already tested it, but obviously tests are limited by my resources. I've reinstalled a i386 with Debian4, suse10, ubuntu 7.10 and a PS3 with ubuntu 7.10. I was able to reproduce the problem in the PS3 and rsync 3.0.0pre4 fixed it. I didn't see any other problem. I would like to remember that the pre-release packages with rsync 3.0.0pre4 (that I've used for my tests) are available here: http://download.systemimager.org/~arighi/systemimager/ As Bernard correctly said we need more tests. Volunteers are really welcome... ;-) -Andrea - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
[sisuite-users] No Logging
I am currently PXE booting HP Proliant servers with systemimager 3.9.6 and while the imaging is successful I have no logging on the server. The systemimager server is a HP Proliant DL380G4 running the latest RH ES 4. On the server I use si_mkdhcpserver I specified the log server and the port as shown in the dhcpd.conf file below : # log-servers option log-servers 192.168.81.35; # option-141 is the port number your log server uses option option-141 8181; On the server the the systemimager-server-monitord service is running - here is the ps trace : /usr/bin/perl -w /usr/sbin/si_monitor --log /var/log/systemimager/si_monitor.log --log_level 2 After a successful PXE boot/loading there is nothing in this file and by using netstat on the server I cannot see and connection to port 8181. From another machine I have connected to this port and I do get debug information in the log ie Fri Sep 28 09:11:19 2007: warning: bad request from 192.168.81.26 (mac address not specified)! Any help would be appreciated. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] No Logging
Bryan, Thanks for the information ... now I see that man si_monitor does give : Clients must have defined the MONITOR_SERVER (and optional MONITOR_PORT) as boot parameters to enable the monitoring feature. Is this documented anywhere else ? Thanks David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3050 Email: [EMAIL PROTECTED] Bryan Washer [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 2007/09/28 11:08 Please respond to sisuite-users@lists.sourceforge.net To sisuite-users@lists.sourceforge.net, [EMAIL PROTECTED] cc Subject Re: [sisuite-users] No Logging You need to edit the APPEND line in your boot file on the PXE server?.here is an example of one of mine? APPEND vga=extended initrd=i386_standard_initrd root=/dev/ram MONITOR_SERVER=192.168.118.244 MONITOR_CONSOLE=yes Notice the MONITOR_SERVER= and MONITOR_CONSOLE=yes MONITOR_SERVER=a.b.c.d is needed to active the monitoring of the installation And MONITOR_CONSOLE=yes is needed if you would like to be able to see a mirror of the console while the system in imaging. Hope this helps. Bryan Washer Sr. Systems Administrator Vitesse Semiconductor Corp From:[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, September 28, 2007 10:30 AM To: [EMAIL PROTECTED]; sisuite-users@lists.sourceforge.net Subject: [sisuite-users] No Logging I am currently PXE booting HP Proliant servers with systemimager 3.9.6 and while the imaging is successful I have no logging on the server. The systemimager server is a HP Proliant DL380G4 running the latest RH ES 4. On the server I use si_mkdhcpserver I specified the log server and the port as shown in the dhcpd.conf file below : # log-servers option log-servers 192.168.81.35; # option-141 is the port number your log server uses option option-141 8181; On the server the the systemimager-server-monitord service is running - here is the ps trace : /usr/bin/perl -w /usr/sbin/si_monitor --log /var/log/systemimager/si_monitor.log --log_level 2 After a successful PXE boot/loading there is nothing in this file and by using netstat on the server I cannot see and connection to port 8181. From another machine I have connected to this port and I do get debug information in the log ie Fri Sep 28 09:11:19 2007: warning: bad request from 192.168.81.26 (mac address not specified)! Any help would be appreciated. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] FATAL : Kernel too old
Andrea, Thanks for the reply. I used the standard image and this was successful. All our machines are HP Proliant DL/ML servers with Smart Array controllers(ie /dev/cciss). We currently have a mix of RHEL3/4 with the RHEL3 machines using the 2.4 kernel. [EMAIL PROTECTED] wrote: Andrea, Thanks for the reply. What options do I have ? - Try and boot using the standard(included) kernel ? For this you should try to install the systemimager-boot-standard-3.9.6 in your image server before, to have more chances for your hw to be properly recognized. After the install remember to update your kernel+initrd.img in your /tftpboot and restart the systemimager-bittorrent daemons (only if you're using the BT transport). A problem you can find with this approach is that in recent kernels the IDE disk naming schema has changed and all these devices are now mapped in /dev/sd* (look for hda - sda transition problem in google for details). So, if you're using an old kernel (actually 2.4 is old in any case), one or more IDE disks and you're not using UUIDs or LABELs in your autoinstallscript.conf probably you can find some problems during the first reboot. - Try an boot using a uyok from a similar machine using a 2.6 kernel. Will this work ? Yes, this is another valid solution, to try with a different boot package made with a 2.6 kernel. The hda - sda problem is still valid. - Build from source on the 2.4 machine. This looks like the cleanest solution. I have downloaded the 3.9.6 tar source however I'm not sure how to build the rpm's. I have looked at the online docs rpmbuild -ta tarball however after looking at the Makefile I see a rpm target which does a rpmbuild -tb. Also my machines are behind a firewall and can only connect to the internet via a proxy. This would be the cleanest solution, but one of the 2 solutions above is surely quicker. Wouldn't virtulization allow you to build both glibc versions on the same platform ? Yes, but since the build server is my laptop: 1) I don't have enough disk space free 2) probably the building process would require an entire night... :-) -Andrea - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] FATAL : Kernel too old
Andrea, Thanks for the reply. What options do I have ? - Try and boot using the standard(included) kernel ? - Try an boot using a uyok from a similar machine using a 2.6 kernel. Will this work ? - Build from source on the 2.4 machine. This looks like the cleanest solution. I have downloaded the 3.9.6 tar source however I'm not sure how to build the rpm's. I have looked at the online docs rpmbuild -ta tarball however after looking at the Makefile I see a rpm target which does a rpmbuild -tb. Also my machines are behind a firewall and can only connect to the internet via a proxy. Wouldn't virtulization allow you to build both glibc versions on the same platform ? Thanks David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3050 Email: [EMAIL PROTECTED] Andrea Righi [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 2007/09/14 02:31 Please respond to [EMAIL PROTECTED]; Please respond to sisuite-users@lists.sourceforge.net To [EMAIL PROTECTED] cc sisuite-users@lists.sourceforge.net Subject Re: [sisuite-users] FATAL : Kernel too old Andrea Righi wrote: [EMAIL PROTECTED] wrote: I just attempted to PXE boot a HP Proliant ML370 G2 with systemimager 3.9.6 and received the following kernel panic : Freeing unused kernel memory : 164k freed FATAL: Kernel too old Kernel panic : Attempting to kill init ! That's because the glibc into the initrd.img are build using the linux-2.6 headers (our build machine is a Ubuntu 7.04 host), that means your 2.4 kernel is not compatible. See also: http://www.busybox.net/lists/busybox/2005-January/013500.html To resolve you should build systemimager from source using your 2.4 machine, in order to have a compatible version of glibc in your initrd.img. For us this is a very difficult issue to resolve: first of all we should find 2 build machines for each arch (one with 2.4 kernel and another with a 2.6 kernel), and then we should build 2 different versions for each arch of the packages systemimager-initrd_template and systemimager-boot-standard... Added a comment in the troubleshooting guide: http://wiki.systemimager.org/index.php/Troubleshooting#FATAL:_Kernel_too_old For now this is the best we can do... -Andrea - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] SystemImager 3.8.0 (stable) is out!
Andrea, Are the pseudo filesystem exclusions for si_getimage going ahead and did they make it to 3.8.0 ? Checked the changelog and I don't see any mention of it. Thanks David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3050 Email: [EMAIL PROTECTED] Andrea Righi [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 2007/02/24 05:07 Please respond to [EMAIL PROTECTED]; Please respond to sisuite-users@lists.sourceforge.net To sisuite-users sisuite-users@lists.sourceforge.net, sisuite-dev sisuite-devel@lists.sourceforge.net cc Subject [sisuite-users] SystemImager 3.8.0 (stable) is out! Hi all, the new stable release is available: https://sourceforge.net/project/showfiles.php?group_id=259package_id=278release_id=488798 and here is the official announcement: http://sourceforge.net/forum/forum.php?forum_id=668989 Best regards, -Andrea - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Imaging issues with RH ES 4
Yes I have removed the /selinux/* from the image however I'm waiting for some new machines to try again. I agree that adding the patterns would be the fast solution.Of course the best solution would be to have mount/mtab show all mounts ... I could open a ticket with RH however I'm not sure I would get too far. Andrea Righi [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 2007/02/22 04:17 Please respond to [EMAIL PROTECTED]; Please respond to sisuite-users@lists.sourceforge.net To [EMAIL PROTECTED] cc sisuite-dev sisuite-devel@lists.sourceforge.net, sisuite-users@lists.sourceforge.net Subject Re: [sisuite-users] Imaging issues with RH ES 4 [EMAIL PROTECTED] wrote: Andrea, Find below the autoinstallscript.conf. What appears to have happended is that /selinux was imaged and then propagated to the new machine. By removing /selinux files, creating /.autorelabel and rebooting /selinux was properly mounted and 'fixfiles relabel' was run. Hi all, I think that we should add some common unwanted patters to the exclusions automatically made by systemimager during image retrieval by si_getimage. In some recent distributions some pseudo-filesystem are not reported with mount. On the other looking in /proc/mounts doesn't resolve, because there are also the filesystems mounted *under* others (usually rootfs, initramfs, etc). Here is a list of patterns that we could always exclude: # selinux stuff /selinux/* # eventfs in SuSE /lib/klibc/events/* # mounted media devices not reported by mount /media/* # NFS stuff /var/lib/nfs/* # LVM caches and backups (automatically re-created at the first boot) /etc/lvm/.cache /etc/lvm/backup/* /etc/lvm/archive/* What do you think? Do you know other patterns that should be automatically excluded? Regards, -Andrea PS for David: have you tried to remove /selinux/* from your image and try to repeat the installation? this is equivalent to run si_getimage with --exclude '/selinux/*'. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [sisuite-users] Imaging issues with RH ES 4
Andrea,
Find below the autoinstallscript.conf.
What appears to have happended is that /selinux was imaged and then
propagated to the
new machine. By removing /selinux files, creating /.autorelabel and
rebooting /selinux was
properly mounted and 'fixfiles relabel' was run.
As you can see below /selinux(selinuxfs) is not shown. The mount command
RHEL4 does
not show selinux however /proc/mounts does. rc.sysinit determines if
selinuxfs is mounted
as : selinuxfs=`awk '/ selinuxfs / { print $2 }' /proc/mounts` . I
checked si_prepareclient and
mount is used and not /proc/mounts. What is the best solution ?
- mount returns :
[EMAIL PROTECTED] etc]# which mount
/bin/mount
[EMAIL PROTECTED] etc]# /bin/mount
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
usbfs on /proc/bus/usb type usbfs (rw)
/dev/cciss/c0d0p1 on /boot type ext3 (rw)
none on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
[EMAIL PROTECTED] etc]#
- cat /proc/mounts returns :
[EMAIL PROTECTED] etc]# cat /proc/mounts
rootfs / rootfs rw 0 0
/proc /proc proc rw,nodiratime 0 0
none /dev tmpfs rw 0 0
/dev/root / ext3 rw 0 0
none /dev tmpfs rw 0 0
none /selinux selinuxfs rw 0 0
/proc /proc proc rw,nodiratime 0 0
/proc/bus/usb /proc/bus/usb usbfs rw 0 0
/sys /sys sysfs rw 0 0
none /dev/pts devpts rw 0 0
/dev/cciss/c0d0p1 /boot ext3 rw 0 0
none /dev/shm tmpfs rw 0 0
none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0
sunrpc /var/lib/nfs/rpc_pipefs rpc_pipefs rw 0 0
!--
autoinstallscript.conf
vi:set filetype=xml:
This file contains partition information about the disks on your golden
client. It is stored here in a generic format that is used by your
SystemImager server to create an autoinstall script for cloning this
system.
You can change the information in this file to affect how your target
machines are installed. See man autoinstallscript.conf for details.
--
config
disk dev=/dev/cciss/c0d0 label_type=msdos unit_of_measurement=MB
!--
This disk's output was brought to you by the partition tool sfdisk,
and by the numbers 4 and 5 and the letter Q.
--
part num=1 size=101 p_type=primary p_name=- flags=boot /
part num=2 size=* p_type=primary p_name=- flags=lvm
lvm_group=VolGroup00 /
/disk
lvm version=2
lvm_group name=VolGroup00 max_log_vols=0 max_phys_vols=0
phys_extent_size=32768K
lv name=LogVol00 size=28672K /
lv name=LogVol01 size=6094848K /
/lvm_group
/lvm
fsinfo line=10 comment=# This file is edited by fstab-sync - see 'man
fstab-sync' for details /
fsinfo line=20 real_dev=/dev/VolGroup00/LogVol00 mp=/ fs=ext3
options=defaults dump=1 pass=1 /
fsinfo line=30 real_dev=/dev/cciss/c0d0p1 mount_dev=LABEL=/boot
mp=/boot fs=ext3 options=defaults dump=1 pass=2 /
fsinfo line=40 real_dev=none mp=/dev/pts fs=devpts
options=gid=5,mode=620 dump=0 pass=0 /
fsinfo line=50 real_dev=none mp=/dev/shm fs=tmpfs
options=defaults dump=0 pass=0 /
fsinfo line=60 real_dev=none mp=/proc fs=proc
options=defaults dump=0 pass=0 /
fsinfo line=70 real_dev=none mp=/sys fs=sysfs
options=defaults dump=0 pass=0 /
fsinfo line=80 real_dev=/dev/VolGroup00/LogVol01 mp=swap fs=swap
options=defaults dump=0 pass=0 /
fsinfo line=90 real_dev=/dev/hda mp=/media/cdrecorder fs=auto
options=pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed
dump=0 pass=0 format=no /
fsinfo line=100 real_dev=/dev/fd0 mp=/media/floppy fs=auto
options=pamconsole,fscontext=system_u:object_r:removable_t,exec,noauto,managed
dump=0 pass=0 format=no /
boel devstyle=udev/
/config
David K Livingstone
CN Signals and Communications
10229 127 Avenue floor 2
Edmonton, AB, T5E 0B9
Ph : 780 472-3959 Fax : 780 472-3050
Email: [EMAIL PROTECTED]
Andrea Righi [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
2007/02/19 14:48
Please respond to
[EMAIL PROTECTED]; Please respond to
sisuite-users@lists.sourceforge.net
To
sisuite-users@lists.sourceforge.net
cc
Subject
Re: [sisuite-users] Imaging issues with RH ES 4
[EMAIL PROTECTED] wrote:
Using UYOK and 3.7.6 I successfully imaged and loaded a RHES 4
machine(DL380G4) without any major
issues. I did however run into pronlems when subsequently attemping to
install an rpm(see below for
error). I tracked the error to a getxattr call for security.selinux.
Disabling selinux avoids the problem
but doesn't correct it. I'm now guessing but does the fact that I imaged
and loaded the system
from a systemimager server running on RHES 3 without user_xattr on the
filesystem have
something to do with it ? Anyone else run into this ? Can I fix my
imaged system somehow ?
Are your filesystems mounted with user_xattr (or xattr) after the
imaging? what's the output of a simple mount? could you post also your
autoinstallscript.conf?
Regards,
-Andrea
[sisuite-users] Imaging issues with RH ES 4
Using UYOK and 3.7.6 I successfully imaged and loaded a RHES 4 machine(DL380G4) without any major issues. I did however run into pronlems when subsequently attemping to install an rpm(see below for error). I tracked the error to a getxattr call for security.selinux. Disabling selinux avoids the problem but doesn't correct it. I'm now guessing but does the fact that I imaged and loaded the system from a systemimager server running on RHES 3 without user_xattr on the filesystem have something to do with it ? Anyone else run into this ? Can I fix my imaged system somehow ? [EMAIL PROTECTED] nx]# rpm -ivh nxclient-2.1.0-11.i386.rpm Preparing...### [100%] error: %pre(nxclient-2.1.0-11.i386) scriptlet failed, exit status 255 error: install: %pre scriptlet failed (2), skipping nxclient-2.1.0-11 [EMAIL PROTECTED] nx]# David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3050 Email: [EMAIL PROTECTED] - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ sisuite-users mailing list sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] Newly imaged computer has file system damage
Remove the LABEL's from the fstab(ie hard code the devices for boot, home etc) and you should be okay. David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3050 Email: [EMAIL PROTECTED] Timothy J. Wielgos [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 2006/04/28 09:34 Please respond to sisuite-users To:sisuite-users@lists.sourceforge.net cc: Subject:[Sisuite-users] Newly imaged computer has file system damage Hey all-- I have been searching for two days now to find an answer to my problem, with little luck. Hopefully, someone on this list will know what's going on. I am running the latest sisuite, the server is running on Fedora Core 5. The golden client is a Red Hat AS3 Update 6 box. After I bring the image down on a box, the /etc/fstab looks like: LABEL=/ /ext3 defaults11 LABEL=/boot /boot ext3 defaults1 2 none /dev/ptsdevpts gid=5,mode=620 0 0 LABEL=/home /home ext3 defaults1 2 none /proc proc defaults00 none /dev/shmtmpfs defaults0 0 LABEL=/var /var ext3 defaults1 2 /dev/hda5swap swap defaults0 0 /dev/cdrom /mnt/cdrom udf,iso9660 noauto,owner,kudzu,ro 0 0 /dev/fd0/mnt/floppy auto noauto,owner,kudzu 00 And see the disk layout: [EMAIL PROTECTED] tmp]# fdisk -l /dev/hda Disk /dev/hda: 20.0 GB, 200 bytes 255 heads, 63 sectors/track, 2431 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot StartEnd Blocks Id System /dev/hda1 * 116 122070 83 Linux Partition 1 does not end on cylinder boundary. /dev/hda2 16514 3999023+ 83 Linux Partition 2 does not end on cylinder boundary. /dev/hda3 514 1011 3998047 83 Linux Partition 3 does not end on cylinder boundary. /dev/hda4 1011 2432 11412371 f Win95 Ext'd (LBA) /dev/hda5 1011 1136 1003905+ 83 Linux /dev/hda6 1136 2432 10408464+ 83 Linux The problem is, after I bring the image down on a new box, the file system will not mount as read-write. The first failure I see at boot time is a message: Remounting root filesystem in read-write mode: mount: no such partition found then the failures just cascade from there. Does anyone have any idea what might be going on? Thanks, Tim __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642 ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] livecd problems
Scott, I've run into the same problem with using a boot cd with 3.4.1 - Not sure if the code has changed since then but the only way I could get it to work was booting from cd and having the local.cfg file on a floppy. Obviously what you would like is to be able to have a local.cfg on the cd. David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3050 Email: [EMAIL PROTECTED] scott gamble [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 2006/04/12 04:04 Please respond to sisuite-users To:sisuite-users@lists.sourceforge.net cc: Subject:[Sisuite-users] livecd problems Hey All Is there a trick to building the boot cd using the si_mkautobootcd application? When booting from the livecd it runs through its checks fine and locates the DHCP server and pulls an address like its suppose to (DHCP is being handled by my IPCOP router) but then (me looking at the logs) it appears the LiveCD assumes the DHCP server is also the image server. In the instructions it recommends putting your image server on the same box as your dhcp server but it does not say its required to do so. The LiveCD does a ping verification against the dhcp server, says congrats you have network connectivity to the image server and tries to establish an rsync connection and - psht, craps out (because its trying to pull an image from the router/dhcp server and not the image server). DHCP is on .1 and the image server is on like .225 on a /24 so nowhere near each other. More reading shows that this might be tackled with the addition of a local.cfg file. But nowhere I could find where it specified where to actually put the local.cfg file so it will be included in a cd iso. Theres all kinds of instructions regarding doing this with a floppy - but nothing regarding a cd that I can find. I've also run prepareclient --server 192.168.1.225 on my Golden Client. Please oh please don't tell me I'm reduced to using a floppy. Most of my machines don't even have floppys any more - and I personally can't stand em. Thanks all for any help you can provide. Scott Gamble --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid=110944bid=241720dat=121642 ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] Smart Array 6i cciss not loading
Array 6i cciss not loading David, With your pings timing out... Are you running a Cisco switch by chance? If so, port fast is probably keeping the port from coming up in time for the ping to succeed. Something to check. As to your mount issue. When you said that you checked the /dev/cciss directory what did you see listed under the disc0 section? Was there only a /dev/cciss/disc0/disc? Or were there also part1 part2 and part3 block devices? Just curious, because there should be. I assume with only 3 parts you're just running a /boot, swap, and / configuration correct? This morning I was able to successfully clone a RHEL4 system with 3.5.1 using a fairly modified version of the image.master file (manually creating the block devices and commenting out some of the finish sections) Surprisingly enough grub-install never really completed properly but upon boot everything came up magically. I'm taking this as a saving grace and running with it. Tomorrow I'll be testing out a RHEL4 Update 1 system to see if it has any changes. Thanks, Seth On 9/12/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Seth/Peter/Anyone ! Unfortunately as you will note from muy first post I'm attempting to load RH EL 3 not 4 on the DL380 G4 so this will not solve my problem. I ran into problems when building 3.5.2 on RHEL3 and also when attempting to run si_prepareclient. I also have a installed base running off of 3.0.0 so I would like as little to change as possible. So back to trying to get 3.4.1 working on the DL380G4 ... I have attempted to force recognition of the driver by modifying the ./patches/linux.i386.config file such that CONFIG_BLK_CPQ_DA=y CONFIG_BLK_CPQ_CISS_DA=y I then remade all the packages(ie rpmbuild -ba /usr/src/redhat/SPECS/systemimager.spec). I then loaded the resultant boot pkg and made a bootable cd : - booting from the cd I eventually get the # prompt after the broadcast's fail(remmeber I normally use a local.cfg from floppy). - at this point /dev/cciss/disc0/disc ... exists however a parted still results in a No such device ... - I then attempted to boot again using the same cd but this time also included a floppy with a local.cfg on it(I had noted fromt he previous boot that the floppy is still referenced for local.cfg) - This time the local.cfg is read and the ping test is attempted to the image server. - the ping tests fails but on the subsequent rsync the script is received. - the script starts to runs and partially works : - old partition table via parted is displayed - new partitions are created(1-3 in my case) - mke2fs -f /dev/cciss/disc0/part3 || shellout works - tune2fs -L /dev/cciss/disc0/part3 works - mkdir -p /a/ || shellout works - mount /dev/cciss/disc0/part3 /a/ -t ext3 -o defaults || shellout FAILS -- I get failed: No such device - When I am in the shell after the failure I can manually run parted/mkde2fs/tune2fs successfully but the mount will always fail with No such device Ideas David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3050 Email: [EMAIL PROTECTED] - Forwarded by David Livingstone/LIVING03/CNR/CA on 2005/09/12 15:18 - Seth Haines [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 2005/09/08 12:15 Please respond to sisuite-users To: sisuite-users@lists.sourceforge.net cc: Subject:Re: [Sisuite-users] Smart Array 6i cciss not loading Some more info on this now: System Imager 3.5.1 uses the 2.6.10_boel_v3.5.2 Kernel. When it talks to the cciss device boel refers to the /dev as /dev/cciss/host0/target0/disc, where as the autoinstall script refers to the cciss device as /dev/cciss/disc0/disc, so no wonder I'm getting the error on boot saying that No such file or directory exists because the boel initrd cciss driver creates the wrong /dev structure! Also potentially of interest is the fact that the RedHat Enterprise Linux 4.0 cciss driver is around 250 kb give or take 10 kb, where as the boel is barely pushing 30 kb, something tells me that some features are going to be missing. The sad part is I've seen system imager work with a RHEL4 installation, but it was version 3.2.X, you just had to manually perform a grub-install off the recovery CD once the image had been put in place. Not exactly perfect. Here's the current thoughts: 1) I'm wondering whether or not it would be possible to get the make files for the boel kernel and build a new cciss driver based on the larger .c file that can be had from the RedHat installation (I'm thinking no, but it's a hope) I mean there has to be some way to get the /dev directory to populate with /dev/cciss/c0d0pX the way it should in order to match the volume labels and grub maps. 2) Editing the autoinstall script to switch all references from /dev/cciss/disc0/disc to /dev
Re: [Sisuite-users] Smart Array 6i cciss not loading
3.4.1 working on the DL380G4 ... I have attempted to force recognition of the driver by modifying the ./patches/linux.i386.config file such that CONFIG_BLK_CPQ_DA=y CONFIG_BLK_CPQ_CISS_DA=y I then remade all the packages(ie rpmbuild -ba /usr/src/redhat/SPECS/systemimager.spec). I then loaded the resultant boot pkg and made a bootable cd : - booting from the cd I eventually get the # prompt after the broadcast's fail(remmeber I normally use a local.cfg from floppy). - at this point /dev/cciss/disc0/disc ... exists however a parted still results in a No such device ... - I then attempted to boot again using the same cd but this time also included a floppy with a local.cfg on it(I had noted fromt he previous boot that the floppy is still referenced for local.cfg) - This time the local.cfg is read and the ping test is attempted to the image server. - the ping tests fails but on the subsequent rsync the script is received. - the script starts to runs and partially works : - old partition table via parted is displayed - new partitions are created(1-3 in my case) - mke2fs -f /dev/cciss/disc0/part3 || shellout works - tune2fs -L /dev/cciss/disc0/part3 works - mkdir -p /a/ || shellout works - mount /dev/cciss/disc0/part3 /a/ -t ext3 -o defaults || shellout FAILS -- I get failed: No such device - When I am in the shell after the failure I can manually run parted/mkde2fs/tune2fs successfully but the mount will always fail with No such device Ideas David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3050 Email: [EMAIL PROTECTED] - Forwarded by David Livingstone/LIVING03/CNR/CA on 2005/09/12 15:18 - Seth Haines [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 2005/09/08 12:15 Please respond to sisuite-users To: sisuite-users@lists.sourceforge.net cc: Subject:Re: [Sisuite-users] Smart Array 6i cciss not loading Some more info on this now: System Imager 3.5.1 uses the 2.6.10_boel_v3.5.2 Kernel. When it talks to the cciss device boel refers to the /dev as /dev/cciss/host0/target0/disc, where as the autoinstall script refers to the cciss device as /dev/cciss/disc0/disc, so no wonder I'm getting the error on boot saying that No such file or directory exists because the boel initrd cciss driver creates the wrong /dev structure! Also potentially of interest is the fact that the RedHat Enterprise Linux 4.0 cciss driver is around 250 kb give or take 10 kb, where as the boel is barely pushing 30 kb, something tells me that some features are going to be missing. The sad part is I've seen system imager work with a RHEL4 installation, but it was version 3.2.X, you just had to manually perform a grub-install off the recovery CD once the image had been put in place. Not exactly perfect. Here's the current thoughts: 1) I'm wondering whether or not it would be possible to get the make files for the boel kernel and build a new cciss driver based on the larger .c file that can be had from the RedHat installation (I'm thinking no, but it's a hope) I mean there has to be some way to get the /dev directory to populate with /dev/cciss/c0d0pX the way it should in order to match the volume labels and grub maps. 2) Editing the autoinstall script to switch all references from /dev/cciss/disc0/disc to /dev/cciss/host0/target0/disc. A find and replace may work, but then I'll probably be confronted with grub issues in the end. This however is an imperfect solution as changing an autoinstall script after every getimage would be a real pain! 3) Find another product... Ha. Doesn't HP have some Rapid Deployment package of some kind? Or is that just extremely similar to RedHat's kickstart? Thanks, Seth --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] Re: Smart Array 6i cciss not loading ([EMAIL PROTECTED])
Thanks Steve. Yes I should have also mentioned that I had also received a bunch(100s) of insmod : unresolved symbol n messages before the mke2fs. If I check in the install script there is a : modprobe ext2 modprobe ext3 To prove this I commented out these lines and attempted a boot from cd. Still bombs at the mount but no other messages. I then do a manual modprobe ext2/3 and yes lots of unresolved symbol messages and the mount still fails. As you suggest I can modify linux.i386.config however how do I boot the new kernel without making all the packages ? ie how can I just make the boot pkg ? Thanks David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3050 Email: [EMAIL PROTECTED] Steve Grandinetti [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 2005/09/12 19:21 Please respond to sisuite-users To:sisuite-users@lists.sourceforge.net cc: Subject:[Sisuite-users] Re: Smart Array 6i cciss not loading ([EMAIL PROTECTED]) Seth/Peter/Anyone ! Unfortunately as you will note from muy first post I'm attempting to load RH EL 3 not 4 on the DL380 G4 so this will not solve my problem. I ran into problems when building 3.5.2 on RHEL3 and also when attempting to run si_prepareclient. I also have a installed base running off of 3.0.0 so I would like as little to change as possible. So back to trying to get 3.4.1 working on the DL380G4 ... I have attempted to force recognition of the driver by modifying the ./patches/linux.i386.config file such that CONFIG_BLK_CPQ_DA=y CONFIG_BLK_CPQ_CISS_DA=y I then remade all the packages(ie rpmbuild -ba /usr/src/redhat/SPECS/systemimager.spec). I then loaded the resultant boot pkg and made a bootable cd : - booting from the cd I eventually get the # prompt after the broadcast's fail(remmeber I normally use a local.cfg from floppy). - at this point /dev/cciss/disc0/disc ... exists however a parted still results in a No such device ... - I then attempted to boot again using the same cd but this time also included a floppy with a local.cfg on it(I had noted fromt he previous boot that the floppy is still referenced for local.cfg) - This time the local.cfg is read and the ping test is attempted to the image server. - the ping tests fails but on the subsequent rsync the script is received. - the script starts to runs and partially works : - old partition table via parted is displayed - new partitions are created(1-3 in my case) - mke2fs -f /dev/cciss/disc0/part3 || shellout works - tune2fs -L /dev/cciss/disc0/part3 works - mkdir -p /a/ || shellout works - mount /dev/cciss/disc0/part3 /a/ -t ext3 -o defaults || shellout FAILS -- I get failed: No such device - When I am in the shell after the failure I can manually run parted/mkde2fs/tune2fs successfully but the mount will always fail with No such device Ideas I'm gonna guess that your ext3 filesystem module isn't being loaded automatically, just as your cciss driver wasn't being loaded automatically. In your 'linux.i386.config' file, is CONFIG_EXT3_FS=m? If so, try building that in statically (CONFIG_EXT3_FS=y), and then boot the new kernel (you shouldn't have to rebuild all the packages). See if that doesn't get you further. -Steve. --- SF.Net email is Sponsored by the Better Software Conference EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile Plan-Driven Development * Managing Projects Teams * Testing QA Security * Process Improvement Measurement * http://www.sqe.com/bsce5sf ___ Sisuite-users mailing list Sisuite-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] Smart Array 6i cciss not loading
Thanks Seth, See other post and yes I am connected to a Cisco switch - all my current installations also take numerous pings before connectivity. Also from your first post I am currently running psp-7.20(haven't yet upgraded to 7.3) which as you mentions replaces tg3 with bcm5700. This becomes a real pain because : - if you use redhat network to keep your servers up2date then anytime you change the kernel(or kudzu is run afterward) you have to re-install the support pack/reconfigure your network. I have tried to get Redhat to incorporate the HP enhancements( push them from rhn) to no avail. I even have a ticket opened with RH where they claim the bcm5700 driver is to blame and want me to test with the tg3 Ok rant over. David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3050 Email: [EMAIL PROTECTED] Seth Haines [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 2005/09/12 18:21 Please respond to sisuite-users To:sisuite-users@lists.sourceforge.net cc: Subject:Re: [Sisuite-users] Smart Array 6i cciss not loading David, With your pings timing out... Are you running a Cisco switch by chance? If so, port fast is probably keeping the port from coming up in time for the ping to succeed. Something to check. As to your mount issue. When you said that you checked the /dev/cciss directory what did you see listed under the disc0 section? Was there only a /dev/cciss/disc0/disc? Or were there also part1 part2 and part3 block devices? Just curious, because there should be. I assume with only 3 parts you're just running a /boot, swap, and / configuration correct? This morning I was able to successfully clone a RHEL4 system with 3.5.1 using a fairly modified version of the image.master file (manually creating the block devices and commenting out some of the finish sections) Surprisingly enough grub-install never really completed properly but upon boot everything came up magically. I'm taking this as a saving grace and running with it. Tomorrow I'll be testing out a RHEL4 Update 1 system to see if it has any changes. Thanks, Seth On 9/12/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Seth/Peter/Anyone ! Unfortunately as you will note from muy first post I'm attempting to load RH EL 3 not 4 on the DL380 G4 so this will not solve my problem. I ran into problems when building 3.5.2 on RHEL3 and also when attempting to run si_prepareclient. I also have a installed base running off of 3.0.0 so I would like as little to change as possible. So back to trying to get 3.4.1 working on the DL380G4 ... I have attempted to force recognition of the driver by modifying the ./patches/linux.i386.config file such that CONFIG_BLK_CPQ_DA=y CONFIG_BLK_CPQ_CISS_DA=y I then remade all the packages(ie rpmbuild -ba /usr/src/redhat/SPECS/systemimager.spec). I then loaded the resultant boot pkg and made a bootable cd : - booting from the cd I eventually get the # prompt after the broadcast's fail(remmeber I normally use a local.cfg from floppy). - at this point /dev/cciss/disc0/disc ... exists however a parted still results in a No such device ... - I then attempted to boot again using the same cd but this time also included a floppy with a local.cfg on it(I had noted fromt he previous boot that the floppy is still referenced for local.cfg) - This time the local.cfg is read and the ping test is attempted to the image server. - the ping tests fails but on the subsequent rsync the script is received. - the script starts to runs and partially works : - old partition table via parted is displayed - new partitions are created(1-3 in my case) - mke2fs -f /dev/cciss/disc0/part3 || shellout works - tune2fs -L /dev/cciss/disc0/part3 works - mkdir -p /a/ || shellout works - mount /dev/cciss/disc0/part3 /a/ -t ext3 -o defaults || shellout FAILS -- I get failed: No such device - When I am in the shell after the failure I can manually run parted/mkde2fs/tune2fs successfully but the mount will always fail with No such device Ideas David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3050 Email: [EMAIL PROTECTED] - Forwarded by David Livingstone/LIVING03/CNR/CA on 2005/09/12 15:18 - Seth Haines [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 2005/09/08 12:15 Please respond to sisuite-users To:sisuite-users@lists.sourceforge.net cc: Subject:Re: [Sisuite-users] Smart Array 6i cciss not loading Some more info on this now: System Imager 3.5.1 uses the 2.6.10_boel_v3.5.2 Kernel. When it talks to the cciss device boel refers to the /dev as /dev/cciss/host0/target0/disc, where as the autoinstall script refers to the cciss device as /dev/cciss/disc0/disc, so no wonder I'm getting the error on boot saying that No such file or directory exists
Re: [Sisuite-users] Smart Array 6i cciss not loading
Seth/Peter/Anyone ! Unfortunately as you will note from muy first post I'm attempting to load RH EL 3 not 4 on the DL380 G4 so this will not solve my problem. I ran into problems when building 3.5.2 on RHEL3 and also when attempting to run si_prepareclient. I also have a installed base running off of 3.0.0 so I would like as little to change as possible. So back to trying to get 3.4.1 working on the DL380G4 ... I have attempted to force recognition of the driver by modifying the ./patches/linux.i386.config file such that CONFIG_BLK_CPQ_DA=y CONFIG_BLK_CPQ_CISS_DA=y I then remade all the packages(ie rpmbuild -ba /usr/src/redhat/SPECS/systemimager.spec). I then loaded the resultant boot pkg and made a bootable cd : - booting from the cd I eventually get the # prompt after the broadcast's fail(remmeber I normally use a local.cfg from floppy). - at this point /dev/cciss/disc0/disc ... exists however a parted still results in a No such device ... - I then attempted to boot again using the same cd but this time also included a floppy with a local.cfg on it(I had noted fromt he previous boot that the floppy is still referenced for local.cfg) - This time the local.cfg is read and the ping test is attempted to the image server. - the ping tests fails but on the subsequent rsync the script is received. - the script starts to runs and partially works : - old partition table via parted is displayed - new partitions are created(1-3 in my case) - mke2fs -f /dev/cciss/disc0/part3 || shellout works - tune2fs -L /dev/cciss/disc0/part3 works - mkdir -p /a/ || shellout works - mount /dev/cciss/disc0/part3 /a/ -t ext3 -o defaults || shellout FAILS -- I get failed: No such device - When I am in the shell after the failure I can manually run parted/mkde2fs/tune2fs successfully but the mount will always fail with No such device Ideas David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3050 Email: [EMAIL PROTECTED] - Forwarded by David Livingstone/LIVING03/CNR/CA on 2005/09/12 15:18 - Seth Haines [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 2005/09/08 12:15 Please respond to sisuite-users To:sisuite-users@lists.sourceforge.net cc: Subject:Re: [Sisuite-users] Smart Array 6i cciss not loading Some more info on this now: System Imager 3.5.1 uses the 2.6.10_boel_v3.5.2 Kernel. When it talks to the cciss device boel refers to the /dev as /dev/cciss/host0/target0/disc, where as the autoinstall script refers to the cciss device as /dev/cciss/disc0/disc, so no wonder I'm getting the error on boot saying that No such file or directory exists because the boel initrd cciss driver creates the wrong /dev structure! Also potentially of interest is the fact that the RedHat Enterprise Linux 4.0 cciss driver is around 250 kb give or take 10 kb, where as the boel is barely pushing 30 kb, something tells me that some features are going to be missing. The sad part is I've seen system imager work with a RHEL4 installation, but it was version 3.2.X, you just had to manually perform a grub-install off the recovery CD once the image had been put in place. Not exactly perfect. Here's the current thoughts: 1) I'm wondering whether or not it would be possible to get the make files for the boel kernel and build a new cciss driver based on the larger .c file that can be had from the RedHat installation (I'm thinking no, but it's a hope) I mean there has to be some way to get the /dev directory to populate with /dev/cciss/c0d0pX the way it should in order to match the volume labels and grub maps. 2) Editing the autoinstall script to switch all references from /dev/cciss/disc0/disc to /dev/cciss/host0/target0/disc. A find and replace may work, but then I'll probably be confronted with grub issues in the end. This however is an imperfect solution as changing an autoinstall script after every getimage would be a real pain! 3) Find another product... Ha. Doesn't HP have some Rapid Deployment package of some kind? Or is that just extremely similar to RedHat's kickstart? Thanks, Seth On 9/8/05, Seth Haines [EMAIL PROTECTED] wrote: David, Where does the imaging process bomb? Is it when parted starts trying to create the partitions and format them? I'm running into the same problem with some DL380 G4's (RHEL4 Install). Partitioning /dev/cciss/disc0/disc... Old partition tabe for /dev/cciss/disc0/disc Error: Could not stat device /dev/cciss/disc0/disc. No such file or directory. parted -s -- /dev/cciss/disc0/disc Error: Could not stat device /dev/cciss/disc0/disc. No such file or directory. I remember seeing some traffic back in mid July from Mark Seger (HP SystemImager Guru) but I never really saw the outcome of the discussion. I'm starting to go through the archives now to see if there is anything I can find. Incidentally you should consider installing the HP
[Sisuite-users] Smart Array 6i cciss not loading
I curently run Systemimager 3.0.0 on numerous HP Proliant DL380 G3's witthout a problem. They use e1000 nic driver and cciss(Smart Array 5i) diriver when booting from floppy. I have loaded RH EL 3 with the latest updated. I recently acquired newer DL380 G4 servers(Smart Array 6i and tg3 nics) and I ran into numerous problems : 1. The 3.0.0 standard boot floppy does not recognize the Smart Array 6i and therefore no disks are available. 2. The nics are not recognized. I have tried the following : 1. Using Systemimager 3.4.1 - After much effort(another story) I finally generated a boot floppy from the std boot pkg however once again the Smart Array 6i(cciss) was not recognized. 2. Downloaded Ole Holm Nielsen's 3.5.2 rpm's(generate for RH 4.0 and posted to this list) and generated a bootable cd(no chance of floppy on this one:). Still no luck with with the cciss driver not loaded. The nic's however are recognized. So the immediate question is what do I have to do to get the Smart Array 6i recognized ? - I have subsequently loaded the machine via RH cd's(RH 3 upadte 5) and the array is working fine. Looked at the cciss code on RH 3 and the kernel source both cciss.c v 2.4.52.RH2 and the latest v2.4.54.RH all have the 6i updates. Other Questions : - I currently use local.cfg on my floppy boots : Can I use local.cfg on a bootable cd and if so how ? - Making a bootable floppy with 3.4.1 was a headace : - the si_mkautoinstalldiskette would exit with zero space on the floppy. No mention is made in the manual on this. I tried : 1. As per the suggestion in si_mkautoinstalldiskette(ie vi the code) I attemted to use /dev/fd0u1680 - This worked for si_mkautoinstalldiskette --floppy /dev/fd0u1680 however on subsequent boot the rc script which attempts to load local.cfg does so using /dev/fd0 and it fails. - si_mkautoinstalldiskette -out-file ddimage will also fail as it hardcodes to 1.44 MB and fails. 2. Took all the comments out of lcoal.cfg and syslinux.cfg and removed message.txt altogether. This then just fit on fd0. Thanks David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3050 Email: [EMAIL PROTECTED]
Re: [Sisuite-users] Smart Array 6i cciss not loading
Thanks for the reply Seth ... I was beginning to think there was no one on the list. The floppy/cd boots correctly and bombs exactly as you show below. - from the shell at that point a lsmod does not show cciss loaded. - /dev/cciss... does not exist. - I would attempt to load ccisss.o if I could find it - I presume it's in the initrd ? There was an item on May 2, 2005 Subject [Sisuite-users] Re: cciss disk problem DL360 where Steve Grandinetti responded : The device support for the SmartArray device wasn't loaded, either via the loadable module, or via static support in your kernel. By default, typically, the SmartArray support is via loadable module. There is a 'discover' task that runs as part of the BOEL env. startup, that identifies which h/w is present and loads the appropriate modules. If indeed your SmartArray support is dynamically loaded, it's possible that the 'discover' utility didn't identify the SmartArray devices. If you continue to have trouble in this area, you can statically build in the support by modifying the ./patches/linux.i386.config file, changing the following two config variables from CONFIG_BLK_CPQ_DA=m CONFIG_BLK_CPQ_CISS_DA=m to CONFIG_BLK_CPQ_DA=y CONFIG_BLK_CPQ_CISS_DA=y And rebuild the kernel. - The real issue is to have the new array detected correctly and the module loaded. In the meantime how does one rebuild the kernel ? Thanks David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3050 Email: [EMAIL PROTECTED] Seth Haines [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 2005/09/08 11:16 Please respond to sisuite-users To:sisuite-users@lists.sourceforge.net cc: Subject:Re: [Sisuite-users] Smart Array 6i cciss not loading David, Where does the imaging process bomb? Is it when parted starts trying to create the partitions and format them? I'm running into the same problem with some DL380 G4's (RHEL4 Install). Partitioning /dev/cciss/disc0/disc... Old partition tabe for /dev/cciss/disc0/disc Error: Could not stat device /dev/cciss/disc0/disc. No such file or directory. parted -s -- /dev/cciss/disc0/disc Error: Could not stat device /dev/cciss/disc0/disc. No such file or directory. I remember seeing some traffic back in mid July from Mark Seger (HP SystemImager Guru) but I never really saw the outcome of the discussion. I'm starting to go through the archives now to see if there is anything I can find. Incidentally you should consider installing the HP Proliant Support Pack 7.3, which replaces the tg3 nic card driver (that has potential to drop packets under heavy load) with the broadcom bcm5700. Thanks, Seth On 9/6/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I curently run Systemimager 3.0.0 on numerous HP Proliant DL380 G3's witthout a problem. They use e1000 nic driver and cciss(Smart Array 5i) diriver when booting from floppy. I have loaded RH EL 3 with the latest updated. I recently acquired newer DL380 G4 servers(Smart Array 6i and tg3 nics) and I ran into numerous problems : 1. The 3.0.0 standard boot floppy does not recognize the Smart Array 6i and therefore no disks are available. 2. The nics are not recognized. I have tried the following : 1. Using Systemimager 3.4.1 - After much effort(another story) I finally generated a boot floppy from the std boot pkg however once again the Smart Array 6i(cciss) was not recognized. 2. Downloaded Ole Holm Nielsen's 3.5.2 rpm's(generate for RH 4.0 and posted to this list) and generated a bootable cd(no chance of floppy on this one:). Still no luck with with the cciss driver not loaded. The nic's however are recognized. So the immediate question is what do I have to do to get the Smart Array 6i recognized ? - I have subsequently loaded the machine via RH cd's(RH 3 upadte 5) and the array is working fine. Looked at the cciss code on RH 3 and the kernel source both cciss.c v 2.4.52.RH2 and the latest v2.4.54.RH all have the 6i updates. Other Questions : - I currently use local.cfg on my floppy boots : Can I use local.cfg on a bootable cd and if so how ? - Making a bootable floppy with 3.4.1 was a headace : - the si_mkautoinstalldiskette would exit with zero space on the floppy. No mention is made in the manual on this. I tried : 1. As per the suggestion in si_mkautoinstalldiskette(ie vi the code) I attemted to use /dev/fd0u1680 - This worked for si_mkautoinstalldiskette --floppy /dev/fd0u1680 however on subsequent boot the rc script which attempts to load local.cfg does so using /dev/fd0 and it fails. - si_mkautoinstalldiskette -out-file ddimage will also fail as it hardcodes to 1.44 MB and fails. 2. Took all the comments out of lcoal.cfg and syslinux.cfg and removed message.txt altogether. This then just fit on fd0. Thanks David K Livingstone CN Signals and Communications
[Sisuite-users] Smart Array 6i cciss not loading
I curently run Systemimager 3.0.0 on numerous HP Proliant DL380 G3's witthout a problem. They use e1000 nic driver and cciss(Smart Array 5i) diriver when booting from floppy. I have loaded RH EL 3 with the latest updated. I recently acquired newer DL380 G4 servers(Smart Array 6i and tg3 nics) and I ran into numerous problems : 1. The 3.0.0 standard boot floppy does not recognize the Smart Array 6i and therefore no disks are available. 2. The nics are not recognized. I have tried the following : 1. Using Systemimager 3.4.1 - After much effort(another story) I finally generated a boot floppy from the std boot pkg however once again the Smart Array 6i(cciss) was not recognized. 2. Downloaded Ole Holm Nielsen's 3.5.2 rpm's(generate for RH 4.0 and posted to this list) and generated a bootable cd(no chance of floppy on this one:). Still no luck with with the cciss driver not loaded. The nic's however are recognized. So the immediate question is what do I have to do to get the Smart Array 6i recognized ? - I have subsequently loaded the machine via RH cd's(RH 3 upadte 5) and the array is working fine. Looked at the cciss code on RH 3 and the kernel source both cciss.c v 2.4.52.RH2 and the latest v2.4.54.RH all have the 6i updates. Other Questions : - I currently use local.cfg on my floppy boots : Can I use local.cfg on a bootable cd and if so how ? - Making a bootable floppy with 3.4.1 was a headace : - the si_mkautoinstalldiskette would exit with zero space on the floppy. No mention is made in the manual on this. I tried : 1. As per the suggestion in si_mkautoinstalldiskette(ie vi the code) I attemted to use /dev/fd0u1680 - This worked for si_mkautoinstalldiskette --floppy /dev/fd0u1680 however on subsequent boot the rc script which attempts to load local.cfg does so using /dev/fd0 and it fails. - si_mkautoinstalldiskette -out-file ddimage will also fail as it hardcodes to 1.44 MB and fails. 2. Took all the comments out of lcoal.cfg and syslinux.cfg and removed message.txt altogether. This then just fit on fd0. Thanks David K Livingstone CN Signals and Communications 10229 127 Avenue floor 2 Edmonton, AB, T5E 0B9 Ph : 780 472-3959 Fax : 780 472-3050 Email: [EMAIL PROTECTED]
