Hi,
I'm trying to install SuSE 10.1 on a system with one SCSI disk. I used
a profile to keep all existing partitions:
/dev/sda1 / ext3
/dev/sda2 swap swap
/dev/sda3 /var ext3
/dev/sda4 /export reiserfs
The profile worked with SLES9, now fails with 10.1. While debugging
I tried the same profile but toll AY to create all 4 partitions,
just to see what comes out of it. Amazingly, AY creates this
partitioning scheme:
/dev/sda1 / ext3
/dev/sda2 /var ext3
/dev/sda3 extended partition
/dev/sda5 swap swap
/dev/sda6 /export reiserfs
/dev/sda7 /boot ext2
A complete mess, of course (note that also swap and /var are swapped
with the partition no.). Looking at y2log I find this:
Partitions.ycp: BootCycl lba_support false
Partitions.ycp: BootCycl /proc/xen/capabilities $[]
Partitions.ycp: BootCycl lba_support false
autoinstall/autoaprt.ycp: boot added automagically...
So it looks like AY thinks that I need a special boot partition, which
is nosense, of course. What can I do? Is this some known bug, or do
I need to send the full y2log? The partitioning profile is below...
cu,
Frank
<partitioning config:type="list">
<drive>
<device>/dev/sda</device>
<partitions config:type="list">
<partition>
<create config:type="boolean">true</create>
<filesystem config:type="symbol">ext3</filesystem>
<format config:type="boolean">true</format>
<fstopt>defaults</fstopt>
<mount>/</mount>