"Warren Crigger" <warren@leetnet.com> 17/05/2006 06:11:00 >>> Thanks for the reply. The hardware I'm installing on initially for test are Dell desktops: P4 ~2.4Ghz, 1 GB RAM, single 40GB drive. The 'repository' server is a PowerEdge 2650, 2 x ~3.2 Xeon, 8 GB, 4x73gb running Raid 5. I'll be asking for a second PowerEdge as a client for testing once I get
Some thoughts about the SLES reposirtoy 1) If you create a SLES9 SP3 repository for the installation server - actually the machine from where you create the repository - should be forhand updated to SP3 2) use the yast installation server menues to create the repository 3) The most important thing is that you use at least the SP3 boot CD. In our current enviroment we build the boot CD from the fresh created repository. Regarding dell Nowaday DELL machine have SATA drives. The SLES GM release does not supoort SATA afaik but at least SP2 does. To install from a SLES GM release you can switch in the DELL bios the SATA mode to combined meaning that ATA will be used. Problem with that: SLES GM will see hdX device but after installation you might have sdX devices. In this case grub will fail. So you are might back to point 3) above ;-) This way you will not have the trouble to boot from GM release but installing SP3 hth Hajo this working a little better. When I install SLES from CD media everything is fine, however, now we want to do this automated over the network. I used Yast-> Misc-> Installation Server to set up the repository of SLES inclusive of SP3 with no errors whatsoever. When I'm back at the office tomorrow I'll try to run the install again with a 100mb boot partition and see what happens. It's the better way to go, I agree, but that shouldn't really be the issue. Thanks for your help. _____ From: anoop kundathil [mailto:anoopbharathan@yahoo.com] Sent: Tuesday, May 16, 2006 11:41 PM To: warren@leetnet.com Subject: Re: [suse-autoinstall] SLES 9 SP3 Network Install Issue Hi, If the machine is hanging at GRUB stage2, then the system is not able to locate the GRUB stage2 loader which may be on your boot/root partition. Grub loads in two stages, stgae 1 and stage2. Stage1 is hardly 446 bytes and it is a pointer to the stage2 program.Stage2 is the actual boot loader and the size of the program is more than the size of an MBR (512 bytes) This is the reason why the program is loaded in two stages. You can create a seperate boot partition of ~100MB and try the installation. In most of the cases it is advisable to have a /boot partition for easy maintenance and sysadmin work. Also if you can provide more information of the hadware it will help. I have installed and tested Dell Poweredge systems with SLES9 SP3 and works fine for me Thanks Anoop warren@leetnet.com wrote: Firstly, sorry for the long email, I'd rather put more info than not enough ;-) I've been tasked with setting up Autoyast for my company's SLES 9.1 installs. I used yast2 to create the media directories (SLES & SP3) and decided to run some network (http) install tests first before doing the xml Autoyast stuff. I've tested this on two Dell desktops for test with the same result. Ultimately we will be installing on PowerEdges but I haven't been able to test that hardware yet and I doubt it will make a difference. What I'm doing: Booting to CD, choosing http silent install along with selecting local, packages, partitioning scheme (a temp partition with tmpfs and the remaining on / as reiserfs). I choose to let grub load from the MBR. The install over the network runs fine. However, when it completes and reboots the problem comes in: "GRUB Loading stage2.. GRUB Loading stage2.." And hangs. I've booted into rescue mode and viewed the Yast logs but nothing is sticking out at me: -in y2logRPM.log packages including kernel shows installed ok -in y2log there are a few errors, but i wouldn't consider any critical -y2loggrub: --------------------------------------- GNU GRUB version 0.94 (640K lower / 3072K upper memory) grub> root (hd0,1) Filesystem type is reiserfs, partition type 0x83 grub> install --stage2=/boot/grub/stage2 /boot/grub/stage1 (hd0) /boot/grub/stage2 0x8000 (hd0,1)/boot/grub/menu.lst grub> quit Root device: /dev/hda2 (mounted on / as reiserfs) Module list: reiserfs ---------------------------------------- -y2logmkinitrd: ---------------------------------------- Kernel image: /boot/vmlinuz-2.6.5-7.244-default Initrd image: /boot/initrd-2.6.5-7.244-default Shared libs: lib/ld-2.3.3.so lib/libblkid.so.1.0 lib/libc.so.6 lib/libselinux.so.1 lib/libuuid.so.1.2 Modules: kernel/fs/reiserfs/reiserfs.ko Including: udev You may now have to update your boot loader configuration. ------------------------------------------ The /boot/ directory seems normal to me: ------------------------------------------ -rw-r--r-- 1 root root 119140 Dec 12 19:58 Kerntypes-2.6.5-7.244-default -rw-r--r-- 1 root root 774348 Dec 12 19:44 System.map-2.6.5-7.244-default -rw-r--r-- 1 root root 512 May 12 11:56 backup_mbr lrwxrwxrwx 1 root root 1 May 16 14:21 boot -> . -rw-r--r-- 1 root root 5969920 May 16 14:03 boot.tar -rw-r--r-- 1 root root 57001 Dec 12 19:58 config-2.6.5-7.244-default drwxr-xr-x 2 root root 416 May 12 11:56 grub lrwxrwxrwx 1 root root 26 May 16 14:21 initrd -> initrd-2.6.5-7.244-default -rw-r--r-- 1 root root 1264374 May 12 11:56 initrd-2.6.5-7.244-default -rw-r--r-- 1 root root 82944 May 12 11:56 message -rw-r--r-- 1 root root 108897 Dec 12 20:02 symvers-2.6.5-7.244-i386-default.gz -rw-r--r-- 1 root root 1827091 Dec 12 19:58 vmlinux-2.6.5-7.244-default.gz lrwxrwxrwx 1 root root 27 May 16 14:21 vmlinuz -> vmlinuz-2.6.5-7.244-default -rw-r--r-- 1 root root 1544369 Dec 12 19:44 vmlinuz-2.6.5-7.244-default ---------------------------------------------- Any help would be greatly appreciated. Maybe it's something simple here, I am new to using SuSE distrubutions. Regards, Warren ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com _____ Talk is cheap. Use Yahoo! Messenger to make PC-to-Phone calls. Great <http://us.rd.yahoo.com/mail_us/taglines/postman7/*http://us.rd.yahoo.com/ev t=39666/*http://messenger.yahoo.com> rates starting at 1¢/min.