[opensuse-autoinstall] Paritioning problems with parted / autoyast
Hello again, I have some problems with the partitioning system again (OpenSuse 11.3), maybe because I changed the filesystem sizes in my config for autoyast. Using my config on a existing system with the same patition sizes everything worked fine. After changing the sizes, I could not install the system any more. So I put a little (very basic) wipe-out script in my config, like this: <scripts> <pre-scripts config:type="list"> <script> <filename>wipe-sda.sh</filename> <interpreter>shell</interpreter> <location>http://192.168.0.101/autoyast/scripts/wipe-sda.sh</location> <source> <![CDATA[ #!/bin/bash dd if=/dev/zero of=/dev/sda ]]> </source> </script> </pre-scripts> </scripts> It takes a lot of time, but at the end the whole drive is erased. Now autoyast has problems creating the new partitions: Systemcodeerror: -1013 /usr/bin/parted -s '/dev/sda' mklabel msdos /usr/bin/parted libblkid.so.1 version `BLKID_2.17` not found (required by /usr/lib/libparted.so.0) Should I better create the partitions with a pre-script? ** Maybe some has a nice "wipe-out" and partition-creation script here on this list for me? I'm not a genius with scripting ;-) ** By the way: I also noticed that when booting & installing via tftpd my USB-keyboard and mouse are comletely "frozen". Booting from DVD and passing the autoyast.xml location etc. at the console works fine... Regards, Ivan -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Am 04.10.2010 16:58, schrieb Ivan De Masi:
Hello again,
I have some problems with the partitioning system again (OpenSuse 11.3), maybe because I changed the filesystem sizes in my config for autoyast.
... Hello, a little update: I tried partitioning by hand with parted/gparted on a test machine, like I want it to be done by autoyast. But autoyast still complains, that it can't read the partition table and I could use the partitions as they are, but can't do any changes like, format, resize, etc. Then it stops because it can't remove a partition: Errorcode: -1014 /usr/bin/parted -s '/dev/sda' rm 10 Don't know why it want's to remove that partition, because it's in my autoyast file. But that doesn't matter now, my whole installation is blocked at the moment. Still looking for a solution. Is it a bug and I need some driverupdate? Thanks! Regards, Ivan -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
on Monday 04 October 2010 Ivan De Masi wrote:
I have some problems with the partitioning system again (OpenSuse 11.3), maybe because I changed the filesystem sizes in my config for autoyast.
that should make no difference
Using my config on a existing system with the same patition sizes everything worked fine. After changing the sizes, I could not install the system any more.
why? what was the error?
So I put a little (very basic) wipe-out script in my config, like this:
<scripts> <pre-scripts config:type="list"> <script> <filename>wipe-sda.sh</filename> <interpreter>shell</interpreter> <location>http://192.168.0.101/autoyast/scripts/wipe-sda.sh</location> <source>
source and location together don't make sense
<![CDATA[ #!/bin/bash dd if=/dev/zero of=/dev/sda ]]>
better don't do that :) If you just want to erase the partition table, the first few blocks should be enough.
It takes a lot of time, but at the end the whole drive is erased.
Now autoyast has problems creating the new partitions:
Systemcodeerror: -1013
/usr/bin/parted -s '/dev/sda' mklabel msdos /usr/bin/parted libblkid.so.1 version `BLKID_2.17` not found (required by /usr/lib/libparted.so.0)
do you use a broken driverupdate? It looks like your installation system is totally broken. Do you use a wrong initrd? This error should appear in the y2log too. Does it appear with every parted call in the log?
Should I better create the partitions with a pre-script?
that should not be needed For me it looks like there is something broken in your setup
** Maybe some has a nice "wipe-out" and partition-creation script here on this list for me? I'm not a genius with scripting ;-) **
a simple wipe out would be a dd over the first few blocks, not over the whole disk :) But should not be needed here. We should find the reason for the problem and not start to shoot blindly on everything that moves ;)
By the way: I also noticed that when booting & installing via tftpd my USB-keyboard and mouse are comletely "frozen". Booting from DVD and passing the autoyast.xml location etc. at the console works fine...
-- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Am 05.10.2010 14:52, schrieb Uwe Gansert:
on Monday 04 October 2010 Ivan De Masi wrote:
I have some problems with the partitioning system again (OpenSuse 11.3), maybe because I changed the filesystem sizes in my config for autoyast.
that should make no difference
Using my config on a existing system with the same patition sizes everything worked fine. After changing the sizes, I could not install the system any more.
why? what was the error?
Hello Uwe, it's the error I posted below with gparted.
So I put a little (very basic) wipe-out script in my config, like this:
<scripts> <pre-scripts config:type="list"> <script> <filename>wipe-sda.sh</filename> <interpreter>shell</interpreter> <location>http://192.168.0.101/autoyast/scripts/wipe-sda.sh</location> <source>
source and location together don't make sense
<![CDATA[ #!/bin/bash dd if=/dev/zero of=/dev/sda ]]>
better don't do that :) If you just want to erase the partition table, the first few blocks should be enough.
OK, I'll do it that way: dd if=/dev/zero of=/dev/sda count=1 ;-)
It takes a lot of time, but at the end the whole drive is erased.
Now autoyast has problems creating the new partitions:
Systemcodeerror: -1013
/usr/bin/parted -s '/dev/sda' mklabel msdos /usr/bin/parted libblkid.so.1 version `BLKID_2.17` not found (required by /usr/lib/libparted.so.0)
do you use a broken driverupdate? It looks like your installation system is totally broken. Do you use a wrong initrd? This error should appear in the y2log too. Does it appear with every parted call in the log?
Unfortunately I can't read the log, because my keyboard is frozen. Next time I'll start with ssh=1. But I guess so :-( I worked long time with initrd and linux from a SLES 10 or 11 for my tftp boot I think and it worked fine. Problems startet with tests of autoinstallation 11.3. When I start the installation I have install=nfs://myserver/openSUSE_11.3_i568/ on the console. Maybe when I did some rsync update on that directory (I have mirrored there some repositorys like opensuse-mozilla and opensuse-openoffice too) something changed? Copying the original linux, initrd and pxelinux.0 files from openSUSE 11.3 DVD / installation to my tftp-boot directory brought me to a completely broken boot. Or do I need completely different initrd an linux files? At the moment I don't know where to continue any more :-( I can do some more tests tomorrow, today I writing this mail from home... Thanks! Regards, Ivan -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
on Wednesday 06 October 2010 Ivan De Masi wrote:
I worked long time with initrd and linux from a SLES 10 or 11 for my tftp boot I think and it worked fine. Problems startet with tests of autoinstallation 11.3. When I start the installation I have install=nfs://myserver/openSUSE_11.3_i568/ on the console. Maybe when I did some rsync update on that directory (I have mirrored there some repositorys like opensuse-mozilla and opensuse-openoffice too) something changed?
Copying the original linux, initrd and pxelinux.0 files from openSUSE 11.3 DVD / installation to my tftp-boot directory brought me to a completely broken boot.
To install an openSUSE 11.3, you should use kernel and initrd from /boot/x86_64/loader/ from the installation media. I can imagine that it works to install an openSUSE 11.1 with SLES11 components, because it's the same codebase but it's not recommended -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Am 07.10.2010 10:46, schrieb Uwe Gansert:
on Wednesday 06 October 2010 Ivan De Masi wrote:
I worked long time with initrd and linux from a SLES 10 or 11 for my tftp boot I think and it worked fine. Problems startet with tests of autoinstallation 11.3. When I start the installation I have install=nfs://myserver/openSUSE_11.3_i568/ on the console. Maybe when I did some rsync update on that directory (I have mirrored there some repositorys like opensuse-mozilla and opensuse-openoffice too) something changed?
Copying the original linux, initrd and pxelinux.0 files from openSUSE 11.3 DVD / installation to my tftp-boot directory brought me to a completely broken boot.
To install an openSUSE 11.3, you should use kernel and initrd from /boot/x86_64/loader/ from the installation media. I can imagine that it works to install an openSUSE 11.1 with SLES11 components, because it's the same codebase but it's not recommended
Yes, indeed! As I guessed yesterday after your good hint, my pxelinux.cfg/default pointed to the wrong kernel and initrd :-( So, now 11.3 boots like a charm - sorry for the confusion! Thanks again, Ivan -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
Am 05.10.2010 14:52, schrieb Uwe Gansert: ...
do you use a broken driverupdate? It looks like your installation system is totally broken. Do you use a wrong initrd? This error should appear in the y2log too. Does it appear with every parted call in the log?
Now thinking about that twice, maybe I really messed up the tftp-config / files. I'll check that tomorrow and report. Regards, Ivan -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
participants (2)
-
Ivan De Masi -
Uwe Gansert