Installing from locally attached Raid?
Hi, is it possible to use a locally attached raid storage as installation source for autoyast? I.e., boot our NFS server (that usually serves the autoyast install repository via NFS to the clients) from a second dhcp/tftp server, but then let it mount it's raid locally and install from there. So sth. like "install=local://..." or whatever. Assuming the neccessary modules are preloaded. Is that possible? cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *
On Thursday 23 November 2006 16:28, Frank Steiner wrote:
So sth. like "install=local://..." or whatever. Assuming the neccessary modules are preloaded.
you can use install=hd:// -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany Business: http://www.suse.de/~ug now playing VNV Nation - standing (still)
Uwe Gansert wrote
On Thursday 23 November 2006 16:28, Frank Steiner wrote:
So sth. like "install=local://..." or whatever. Assuming the neccessary modules are preloaded.
you can use install=hd://
Ok! But how do I identify the hard disk afterwards? The device? The raid I want is a lvm volume, so could I use hd:///dev/mapper/raid-rpm/ or sth? Or is lvm to complicated in that early stage for AY? cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *
On Friday 24 November 2006 09:04, Frank Steiner wrote:
you can use install=hd://
Ok! But how do I identify the hard disk afterwards? The device? The raid I want is a lvm volume, so could I use hd:///dev/mapper/raid-rpm/ or sth? Or is lvm to complicated in that early stage for AY?
There are no lvm tools available at this stage. But you can add them, e.g., via a driver update and even trigger the lvm setup process there, so that you can indeed use hd:///dev/mapper/... -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany Business: http://www.suse.de/~ug now playing Diorama - Helmets Down
Uwe Gansert wrote
On Friday 24 November 2006 09:04, Frank Steiner wrote:
you can use install=hd:// Ok! But how do I identify the hard disk afterwards? The device? The raid I want is a lvm volume, so could I use hd:///dev/mapper/raid-rpm/ or sth? Or is lvm to complicated in that early stage for AY?
There are no lvm tools available at this stage. But you can add them, e.g., via a driver update and even trigger the lvm setup process there, so that you can indeed use hd:///dev/mapper/...
Sounds promising, I will try that! Thanks! -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *
Uwe Gansert wrote
On Friday 24 November 2006 09:04, Frank Steiner wrote:
you can use install=hd:// Ok! But how do I identify the hard disk afterwards? The device? The raid I want is a lvm volume, so could I use hd:///dev/mapper/raid-rpm/ or sth? Or is lvm to complicated in that early stage for AY?
There are no lvm tools available at this stage. But you can add them, e.g., via a driver update and even trigger the lvm setup process there, so that you can indeed use hd:///dev/mapper/...
Ehm, no, wait a sec... How can I add a driverupdate when the install repository is on the lvm volume? I would have to mount the lvm first to access the driverupdate file... Remember that I want to use install=hd:///dev/mapper/..., so I must get the lvm tools in before the install source should be mounted. Any change to activate a driverupdate before mounting the install source? I guess if I have to get all that into the initrd, it becomes complicated (all libraries needed for lvm tools etc., hacking the init script... :-() cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *
Frank Steiner wrote
Any change to activate a driverupdate before mounting the install source? I guess if I have to get all that into the initrd, it becomes complicated (all libraries needed for lvm tools etc., hacking the init script... :-()
I tried to put the driverupdate on a floppy and use driverupdate=1 on the boot prompt. My driverupdate file contains a file /linux/suse/i386-sles10/install/update.tar.gz which is just a tar.gz of all files and directories in the lvm2.rpm, plus a update.pre script, calling vgscan and vgchange. The driverupdate is indeed loaded from the floppy, but it doesn't unpack the update.tar.gz (I don't see any of the files when using the prompt at ALT+F9), nor does it execute the pre script. At console 3 I see sth. like Loading image /mounts/update/driverupdate dud 0: file:/linux/suse/i386-sles10 /download/image0 removed dud 0: Ok, that seems to have worked :-) Looking for a SuSE Linux Enterpriese Server 0 hard disk... and then it fails to mount /dev/mapper/.... Should it work like that, i.e., untar the update.tar.gz and execute the update.pre script *before* mounting the install source? Then I might just have sth. wrong in my driverupdate. Or can't it work like that? cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *
On Fri, 24 Nov 2006, Frank Steiner wrote:
Frank Steiner wrote
Any change to activate a driverupdate before mounting the install source? I guess if I have to get all that into the initrd, it becomes complicated (all libraries needed for lvm tools etc., hacking the init script... :-()
I tried to put the driverupdate on a floppy and use driverupdate=1 on the boot prompt. My driverupdate file contains a file /linux/suse/i386-sles10/install/update.tar.gz which is just a tar.gz of all files and directories in the lvm2.rpm, plus a update.pre script, calling vgscan and vgchange.
The driverupdate is indeed loaded from the floppy, but it doesn't unpack the update.tar.gz (I don't see any of the files when using the prompt at ALT+F9), nor does it execute the pre script.
update.tar.gz is unpacked only when the installation is about to start, which is too late for you. But you can slightly abuse the update process and do this: - add an UpdatePriority to dud.config, say: UpdatePriority: 555 - this ensures the local copy of the update files is created below /update/555/ - add a script, say 'install/foo' to your update - add an entry Exec: /update/555/install/foo to dud.config This will run your 'foo'-script the moment the update is read (and not later, when the installation is started). You can then use this script to create the environment you need, like copying lvm files and doing the lvm setup. BTW, if you can live with putting the driver update on CD, you can replace/add files to the initrd directly. Steffen -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
participants (3)
-
Frank Steiner -
Steffen Winterfeldt -
Uwe Gansert