Few more questions, I'm making some progress by using sfdisk in this case.  I 
need to get some machines imaged so I'm working around it.

Regarding the partitioning.  On the golden image, fstab looks like this:
/dev/sda2       /       xfs     defaults        1       1
/dev/sda1       /boot   ext2    defaults        1       2
/dev/sda3       swap    swap    defaults        0       0

And I notice that autoinstallscript.conf sets up swap to fill the rest of the 
disk with a fixed size / and /boot.  I want it to be a fixed /boot and swap and 
have / fill up the rest of the disk.  I modified autoinstallscript.conf to do 
this.  Is this because swap is on /dev/sda3?  I modified autoinstallscript.conf 
so that swap is on /dev/sda2 and / is on /dev/sda3.  Does the fstab order 
matter to si_prepareimage or does it instantiate by device number?

My modified autoinstallscript.conf looks like this now:

  <disk dev="/dev/sda" label_type="msdos" unit_of_measurement="MB">
    <!--
      This disk's output was brought to you by the partition tool "sfdisk",
      and by the numbers 4 and 5 and the letter Q.
    -->
    <part  num="1"  size="271"  p_type="primary"  p_name="-"  flags="boot" />
    <part  num="2"  size="16384"  p_type="primary"  p_name="-"  flags="-" />
    <part  num="3"  size="*"  p_type="primary"  p_name="-"  flags="-" />
  </disk>
  <fsinfo  line="10" real_dev="/dev/sda3" mp="/"  fs="xfs" options="defaults" 
dump="1" pass="1" />
  <fsinfo  line="20" real_dev="/dev/sda1" mp="/boot"  fs="ext2" 
options="defaults" dump="1" pass="2" />
  <fsinfo  line="30" real_dev="/dev/sda2" mp="swap"  fs="swap" 
options="defaults" dump="0" pass="0" />
  <fsinfo  line="40" real_dev="/dev/cdrom" mp="/mnt/cdrom"  fs="udf,iso9660" 
options="noauto,owner,kudzu,ro" dump="0" pass="0"  format="no" />
  <fsinfo  line="50" real_dev="none" mp="/dev/pts"  fs="devpts" 
options="gid=5,mode=620" dump="0" pass="0" />
  <fsinfo  line="60" real_dev="none" mp="/proc"  fs="proc" options="defaults" 
dump="0" pass="0" />
  <fsinfo  line="70" real_dev="none" mp="/dev/shm"  fs="tmpfs" 
options="defaults" dump="0" pass="0" />

having moved swap to /dev/sda2 and / to /dev/sda3.

Mitch

Mitch Sako wrote:
> It's stdout:
> 
> sh-2.05b# parted -s -- /dev/sda print 2>/dev/null
> Warning: Unable to align partition properly.  This probably means that 
> another partitioning tool generated an incorrect partition table, 
> because it didn't have the correct BIOS geometry.  It is safe to 
> ignore,but ignoring may cause (fixable) problems with some boot loaders.
> Disk geometry for /dev/sda: 0.000-69878.000 megabytes
> Disk label type: msdos
> Minor    Start       End     Type      Filesystem  Flags
> 1          0.000    284.195  primary   ext2        boot
> 2        284.195   2236.366  primary   linux-swap  3       2236.367  
> 69878.000  primary   xfs 
> Just to be sure....:
>       sh-2.05b# parted -s -- /dev/sda print 1>/dev/null
> sh-2.05b#
> Andrea Righi wrote:
> 
>> Right.. it's a common behaviour for a lot of distros... and what about
>> the output, is it printed to stdout or stderr?
>>
>> Cheers,
>> -Andrea
>>
>> Mitch Sako wrote:
>>
>>> I checked again.  The RH RPM is parted-1.6.3-29.5 if that makes any
>>> difference.  RH usually doesn't change the minor release number and just
>>> appends patches to it.
>>>
>>> Mitch
>>>
>>> Andrea Righi wrote:
>>>
>>>> Mitch Sako wrote:
>>>>
>>>>
>>>>> $ parted --version
>>>>> GNU Parted 1.6.3
>>>>
>>>>
>>>>
>>>> it's a very old version... have you tried to update it to a newer
>>>> release (at least 1.6.23)?
>>>>
>>>>
>>>>
>>>>> $ parted -s -- /dev/sda print
>>>>> Warning: Unable to align partition properly.  This probably means that
>>>>> another partitioning tool generated an incorrect partition table,
>>>>> because it didn't have the correct BIOS geometry.  It is safe to
>>>>> ignore,but ignoring may cause (fixable) problems with some boot 
>>>>> loaders.
>>>>> Disk geometry for /dev/sda: 0.000-76324.500 megabytes
>>>>> Disk label type: msdos
>>>>> Minor    Start       End     Type      Filesystem  Flags
>>>>> 1          0.000    271.074  primary   ext2        boot
>>>>> 2        271.075  53022.036  primary   xfs         3      53022.037 
>>>>> 76324.438  primary   linux-swap
>>>>>
>>>>
>>>>
>>>> Anyway, the output seems correct... can you check if it is printed to
>>>> stdout or stderr? for example what happens if you run:
>>>>
>>>> # parted -s -- /dev/sda print 2>/dev/null
>>>>
>>>> If the commands doesn't print anything we can fix it redirecting all to
>>>> stdout... let me know..
>>>>
>>>> Cheers,
>>>> -Andrea
>>>>
>>>>
>>>
>>>
>>
>>
> 
> 
> 


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sisuite-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sisuite-users

Reply via email to