RE: [suse-autoinstall] Problems with <use> and <partition_type>
Hi, I found that if I made my partitions sections look like the following, it would grab the first disk (be it /dev/sda or /dev/hda) and autopartition it. See if it works for you: <partitioning config:type="list"> <drive> <use>all</use> </drive> </partitioning> Christopher R. Slater ITO Specialist MSDD/SSO Hewlett Packard Company, Roseville Site (916) tn785-1802 http://ecardfile.com/id/chris_slater -----Original Message----- From: Fermín Galán [mailto:fermin.galan@agora-2000.com] Sent: Friday, October 03, 2003 5:37 AM To: suse-autoinstall@suse.com Subject: [suse-autoinstall] Problems with <use> and <partition_type> Hello everyone. I'm trying to configure a control file that destroy the existing primary partition hda1 and install SuSE freed with the deletion. To do that, I use <use>1</use> in the control file, but it doesn't seem to work. However <use>5,6,7</use> works, I guest it is due to 1 is a primary partition and 5,6,7 are logical units. It seems like autoyast has problems deleting a primary partition. Or not? Although I destroy the partition previously to the installation (with fdisk, for example) I also have problems with <partition_type>primary</partition_type>. It only seems to work when there is no other partitions in the disk. For example, if an extended partition previously exists, the partitions specified in the control file aren't created. Is possible to install SuSE in primary partitions when a extended partition already exist? How? I'm using SuSE 8.1, autoyast2-installation-2.6.42. Will the problem be fixed using a recent patched version? Is the problem fixed in SuSE 8.2? Any help to solve these problems is welcome. Thanks in advance! --------- Fermín -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com
I found that if I made my partitions sections look like the following, it would grab the first disk (be it /dev/sda or /dev/hda) and autopartition it. See if it works for you:
<partitioning config:type="list"> <drive> <use>all</use> </drive> </partitioning>
This solution destroys all partitions, but I only want to delete /dev/hda1 and preserve the others. For example, if I have: /dev/hda1 whatever /dev/hda5 data /dev/hda6 more data I want to get after installation: /dev/hda1 boot /dev/hda2 swap /dev/hda3 root partition /dev/hda5 data (preserved) /dev/hda6 more data (preserved) But your example leads to: /dev/hda5 boot /dev/hda6 swap /dev/hda7 more data -------- Fermín
Fermín Galán wrote:
I found that if I made my partitions sections look like the following, it would grab the first disk (be it /dev/sda or /dev/hda) and autopartition it. See if it works for you:
<partitioning config:type="list"> <drive> <use>all</use> </drive> </partitioning>
This solution destroys all partitions, but I only want to delete /dev/hda1 and preserve the others. For example, if I have:
/dev/hda1 whatever /dev/hda5 data /dev/hda6 more data
I want to get after installation:
/dev/hda1 boot /dev/hda2 swap /dev/hda3 root partition /dev/hda5 data (preserved) /dev/hda6 more data (preserved)
This will never work for the simple reason that the extended partition has to be destroyed in order to be able to add additional primary partitions.
But your example leads to:
/dev/hda5 boot /dev/hda6 swap /dev/hda7 more data
Manipulating partitions at the beginning of the device is still not supported unfortunatly. You can only manipulate partitions at the end. Anas
-------- Fermín
Manipulating partitions at the beginning of the device is still not supported unfortunatly. You can only manipulate partitions at the end.
What do you exactly mean with *manipulate partitions*? Only to create partitions or also to format already created partitions? Is possible to have the partition plan already done (not only desired partitions created, but also formatted) before run autoinstaller and just tell in the XML the target partitions for the installation (the autoinstaller wouldn't need to manipulate anything, just install)? ------ Fermín
Fermín Galán wrote:
I found that if I made my partitions sections look like the following, it would grab the first disk (be it /dev/sda or /dev/hda) and autopartition it. See if it works for you:
<partitioning config:type="list"> <drive> <use>all</use> </drive> </partitioning>
This solution destroys all partitions, but I only want to delete /dev/hda1 and preserve the others. For example, if I have:
/dev/hda1 whatever /dev/hda5 data /dev/hda6 more data
I want to get after installation:
/dev/hda1 boot /dev/hda2 swap /dev/hda3 root partition /dev/hda5 data (preserved) /dev/hda6 more data (preserved)
This will never work for the simple reason that the extended partition has to be destroyed in order to be able to add additional primary partitions.
But your example leads to:
/dev/hda5 boot /dev/hda6 swap /dev/hda7 more data
Manipulating partitions at the beginning of the device is still not supported unfortunatly. You can only manipulate partitions at the end. Anas
-------- Fermín
participants (3)
-
Anas Nashif -
Fermín Galán -
SLATER,CHRIS (HP-Roseville,ex1)