Mailinglist Archive: opensuse-autoinstall (77 mails)

< Previous Next >
Re: [suse-autoinstall] SLES9 autoinstall hangs at creating initrd
  • From: Carl Pecinovsky <csky@xxxxxxxxxx>
  • Date: Tue, 5 Oct 2004 20:45:36 +0000 (UTC)
  • Message-id: <OF41C34C7B.E01D5975-ON86256F24.0071BD15-86256F24.0071C7E8@xxxxxxxxxx>
I don't see anything wrong with the directory structure, but you might want
to check the PDF against the instructions given in the the release notes
(CD1\docu\RELEASE-NOTES.en.html) under the section called "Setting up an
installation server for network installations". Also, you should post at
least the last part of the y2log.
-Carl


> I just cant get my network install to see the core distribution files.
> It installs the SLES Admin guide then goes to "Finishing Basic
Installation"
> and hangs at "Creating initrd..."
> I've followed http://yast2.suse.com/multiplesource/multiplesource.pdf
> as closely as possible.
>
> Here is my directory
>
> ls -ld *
> lrwxrwxrwx 1 root root 22 Oct 5 11:03 boot ->
> sles9-x86_64/CD1/boot/
> lrwxrwxrwx 1 root root 24 Oct 5 11:03 content ->
> sles9-x86_64/CD1/content
> lrwxrwxrwx 1 root root 28 Oct 5 11:04 control.xml
> -> sles9-x86_64/CD1/control.xml
> drwxr-xr-x 6 root root 4096 Oct 5 11:03 core9-x86_64
> lrwxrwxrwx 1 root root 25 Oct 5 11:04 media.1 ->
> sles9-x86_64/CD1/media.1/
> drwxr-xr-x 3 root root 4096 Oct 5 11:03 sles9-x86_64
> drwxr-xr-x 2 root root 4096 Oct 5 11:27 yast
>
> ls core9-x86_64/ sles9-x86_64/ yast/
> core9-x86_64/:
> CD1 CD2 CD3 CD4
>
> sles9-x86_64/:
> CD1
>
> yast/:
> instorder order
>
>
> cat yast/order
> /sles9-x86_64/CD1 /sles9-x86_64/CD1
> /core9-x86_64/CD1 /core9-x86_64/CD1
>
> cat yast/instorder
> /sles9-x86_64/CD1
> /core9-x86_64/CD1
>
> I can attach my y2log if anyone wants to see it.
>
>
> Thanks for any help
> Aaron
>
>
>
> On Mon, 4 Oct 2004, Durk S. wrote:
>
> > Okay peeps, as I already concluded earlier, my installation source
wasn't
> > completely okay. After some corrections, the AutoYaST install went like
it
> > should.
> >
> > Durk
> >
> >> Hey thanks!
> >>
> >> I've already found that PDF file, but this saves me a bit reading! ;-)
> >>
> >> Let's see if I can make a working network install this time. :-)
> >>
> >> Durk
> >>
> >>> Hi!
> >>>
> >>> Your source should look a bit different.
> >>>
> >>> From /usr/share/doc/packages/yast2-instserver/network-install.pdf:
> >>>
> >>> LINUX Enterprise Server 9 CD1 = SLES CD1
> >>>
> >>> LINUX Enterprise Server 9 CD2 = CORE CD1
> >>> LINUX Enterprise Server 9 CD3 = CORE CD2
> >>> LINUX Enterprise Server 9 CD4 = CORE CD3
> >>> LINUX Enterprise Server 9 CD5 = CORE CD4
> >>> LINUX Enterprise Server 9 CD6 = CORE CD5
> >>>
> >>> .
> >>> |-- sles9-i386
> >>> | |-- CD1
> >>> | |-- boot
> >>> | |-- docu
> >>> | |-- media.1
> >>> | |-- suse
> >>> | `-- yast
> >>> |-- core9-i386
> >>> | |-- CD1
> >>> | |-- CD2
> >>> | `-- CD3
> >>> |-- boot -> sles9-i386/CD1/boot
> >>> |-- media.1 -> sles9-i386/CD1/media.1
> >>> |-- content -> sles9-i386/CD1/content
> >>> |-- control.xml -> sles9-i386/CD1/control.xml
> >>> `-- yast SLES9 Network Install
> >>>
> >>> You have to set up a multisource installation as described in the
PDF.
> >>>
> >>> Best regards,
> >>> Andreas
> >>>
> >>> On Thu, 30 Sep 2004, Durk S. wrote:
> >>>
> >>>> Addition:
> >>>>
> >>>> I did a test with a floppy (for the profile) and SLES 9 CDs (as
> >>>> installation source)... This actually works! So there must be
> >>>> something wrong with my NFS installation source... or configuration
> >>>> to find that source.
> >>>>
> >>>> The structure of the source looks like this:
> >>>>
> >>>> sles9
> >>>> sles9/boot
> >>>> sles9/boot/root
> >>>> sles9/boot/directory.yast
> >>>> sles9/boot/README
> >>>> sles9/boot/modules1
> >>>> sles9/boot/modules2
> >>>> sles9/boot/modules3
> >>>> sles9/boot/modules4
> >>>> sles9/boot/modules5
> >>>> sles9/boot/LIESMICH
> >>>> sles9/boot/rescuefloppy
> >>>> sles9/boot/loader
> >>>> sles9/boot/loader/linux
> >>>> sles9/boot/loader/10240768.spl
> >>>> sles9/boot/loader/06400480.spl
> >>>> sles9/boot/loader/memtest
> >>>> sles9/boot/loader/message
> >>>> sles9/boot/loader/12801024.spl
> >>>> sles9/boot/loader/isolinux.bin
> >>>> sles9/boot/loader/isolinux.cfg
> >>>> sles9/boot/loader/initrd
> >>>> sles9/boot/loader/16001200.spl
> >>>> sles9/boot/loader/14001050.spl
> >>>> sles9/boot/loader/bootlogo
> >>>> sles9/boot/loader/08000600.spl
> >>>> sles9/boot/README.DOS
> >>>> sles9/boot/rescue
> >>>> sles9/boot/LIESMICH.DOS
> >>>> sles9/boot/bootdsk1
> >>>> sles9/boot/bootdsk2
> >>>> sles9/boot/bootdsk3
> >>>> sles9/boot/modules1.txt
> >>>> sles9/boot/modules2.txt
> >>>> sles9/boot/modules3.txt
> >>>> sles9/boot/modules4.txt
> >>>> sles9/boot/modules5.txt
> >>>> sles9/sles9-i386/CD1/... (contents of SLES 9 CD 1)
> >>>> sles9/sles9-i386/CD2/... (contents of SLES 9 CD 2)
> >>>> sles9/sles9-i386/CD3/... (contents of SLES 9 CD 3)
> >>>> sles9/sles9-i386/CD4/... (contents of SLES 9 CD 4)
> >>>> sles9/sles9-i386/CD5/... (contents of SLES 9 CD 5)
> >>>> sles9/sles9-i386/CD6/... (contents of SLES 9 CD 6)
> >>>> sles9/yast
> >>>> sles9/yast/order
> >>>> sles9/yast/instorder
> >>>> sles9/content
> >>>> sles9/media.1
> >>>> sles9/media.1/directory.yast
> >>>> sles9/media.1/media
> >>>> sles9/media.1/products
> >>>> sles9/media.1/info.txt
> >>>>
> >>>> I'm still figuring out this issue.
> >>>>
> >>>> Durk
> >>>>
> >>>>> Hi there,
> >>>>>
> >>>>> I've got exactly the same problem with a HP DL360 G3 using a
> >>>>> network AutoYaST2 install.
> >>>>>
> >>>>> The last lines of y2log:
> >>>>>
> >>>>> 2004-09-30 13:57:50 <1> linux(697) [YCP] Storage.ycp:1573
> >>>>> CheckForLvmRootFs root=$["detected_fs":`ext2,
> >>>>> "device":"/dev/cciss/c 0d0p7", "fs_options":$[], "fsid":131,
> >>>>> "mount":"/", "nr":7,
> >>>>> "region":[516, 16917], "type":`logical, "used_fs":`ext2, "uuid":"7f
> >>>>> ca98f4-1cf7-4862-81c0-93866245ea3d"]
> >>>>> dev=$["disk":"/dev/cciss/c0d0", "nr":7] 2004-09-30 13:57:50 <1>
> >>>>> linux(697) [YCP] Storage.ycp:1576 CheckForLvmRootFs ret=false
> >>>>> 2004-09-30 13:57:50 <1> linux(697) [YCP] Misc.ycp:146
> >>>>> WriteYaSTInf($["Keytable":"us.map.gz", "Language":"en_US",
> >>>>> "RebootMsg":" 0", "Root":"reboot"]) = Keytable: us.map.gz
> >>>>> Language: en_US
> >>>>> RebootMsg: 0
> >>>>> Root: reboot
> >>>>> 2004-09-30 13:57:50 <1> linux(697) [YCP] Bootloader.ycp:316 Writing
> >>>>> bootloader configuration
> >>>>> 2004-09-30 13:57:50 <3> linux(697) [libscr] Bootloader.ycp:361 No
> >>>>> SCR instance found
> >>>>> 2004-09-30 13:57:50 <1> linux(697) [YCP] Initrd.ycp:269
> >>>>> Initrd::Write called, changed: true, list: ["cciss"]
> >>>>> 2004-09-30 13:57:50 <3> linux(697) [libscr] Initrd.ycp:294 No SCR
> >>>>> instance found2004-09-30 13:57:50 <3> linux(697) [libscr]
> >>>>> Initrd.ycp:296 No SCR instance found2004-09-30 13:57:50 <1>
> >>>>> linux(697) [YCP] Initrd.ycp:304 Modules [] were added to initrd not
> >>>>> using Initrd module
> >>>>> 2004-09-30 13:57:50 <3> linux(697) [libscr] Initrd.ycp:313 No SCR
> >>>>> instance found2004-09-30 13:57:50 <1> linux(697) [YCP]
> >>>>> Initrd.ycp:316 Writing modules cciss 2004-09-30 13:57:50 <3>
> >>>>> linux(697) [libscr] Initrd.ycp:317 No SCR instance found2004-09-30
> >>>>> 13:57:50 <3> linux(697) [libscr] Initrd.ycp:318 No SCR instance
> >>>>> found2004-09-30 13:57:50 <3> linux(697) [libscr] Initrd.ycp:323 No
> >>>>> SCR instance found2004-09-30 13:57:50 <3> linux(697) [libscr]
> >>>>> Initrd.ycp:326 No SCR instance found2004-09-30 13:57:50 <3>
> >>>>> linux(736) [ui]
> >>>>> YUI_widgets.cc(createRichText):857 Invalid arguments for the Label
> >>>>> RichText: `RichText
> >>>>> (`opt (`plainText), nil)
> >>>>> 2004-09-30 13:57:50 <3> linux(736) [ui]
> >>>>> YUI_widgets.cc(widgetWithId):2426 No widget with `id( `ok_help )
> >>>>> 2004-09-30 13:57:50 <3> linux(736) [libycp] Initrd.ycp:254 No
> >>>>> widget with `id( `ok_help )
> >>>>>
> >>>>> I hope there's a solution.
> >>>>>
> >>>>> Durk
> >>>>>
> >>>>>> Date: Wed, 29 Sep 2004 10:01:15 +0200
> >>>>>> Message-ID:
> >>>>>>
<CD998562990BEA4D98E5EE624E492B3A5B163E@xxxxxxxxxxxxxxxxxxxxxxxxxx>
> >>>>>> From: <anders.g.karlsson@xxxxxx>
> >>>>>> Subject: [suse-autoinstall] SLES9 autoinstall hangs at creating
> >>>>>> initrd
> >>>>>>
> >>>>>>
> >>>>>> Hi,
> >>>>>>
> >>>>>> I've run into a problem when doing an autoinstall (SLES9) from a
> >>>>>> CD that I created using the YaST2 tools. Everything runs smooth up
> >>>>>> to the point where it is "Creating initrd...", at this point the
> >>>>>> installation just hangs. I'm trying to install on an HP DL380 G3
> >>>>>> with the cciss hardware raid driver. Anyone has the same
> >>>>>> experience?
> >>>>>>
> >>>>>> Regards,
> >>>>>> Anders
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> To unsubscribe, e-mail: suse-autoinstall-unsubscribe@xxxxxxxx For
> >>>>> additional commands, e-mail: suse-autoinstall-help@xxxxxxxx
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>
> >>> --
> >>> Andreas Vetter
> >>> Universitaet Wuerzburg, Theoretische Physik 1
> >>> Am Hubland, 97074 Wuerzburg, Deutschland / Germany
> >>>
> >>> --
> >>> To unsubscribe, e-mail: suse-autoinstall-unsubscribe@xxxxxxxx
> >>> For additional commands, e-mail: suse-autoinstall-help@xxxxxxxx
> >>
> >>
> >>
> >>
> >> --
> >> To unsubscribe, e-mail: suse-autoinstall-unsubscribe@xxxxxxxx
> >> For additional commands, e-mail: suse-autoinstall-help@xxxxxxxx
> >
> >
> >
> >
> >



< Previous Next >
List Navigation
Follow Ups