Hi, one problem solved, but partitioning still fails: Uwe Gansert wrote
On Monday 04 September 2006 12:45, Frank Steiner wrote:
I'm trying to install SuSE 10.1 on a system with one SCSI disk. I used a profile to keep all existing partitions:
what architecture do you use? On PPC for example, such a partition is added. On i586 it's not.
Architecture is i586 and it is added because YaST2 thinks that the bios of my host does not support lba, see my first mail:
Partitions.ycp: BootCycl lba_support false Partitions.ycp: BootCycl /proc/xen/capabilities $[] Partitions.ycp: BootCycl lba_support false autoinstall/autoaprt.ycp: boot added automagically...
I looked at Partitioning.ypc and it looks like the bios does not return the right value: list internal_bios = (list<map>) SCR::Read (.probe.bios); boolean lba = internal_bios[0, "lba_support"]:false; Due to the log file, lba obviously is set to false. I've no idea why that happens, the host is 2 years old and of course supports lba. Maybe it's because no IDE disk is in the system and the SCSI controller is not onboard, I don't know. Always worked fine with SuSE 9.0 and SLES9. I compared this to SLES9, and there the code was different. Especially one could set the "lba32" option for lilo and YaST2 would then set lba to true. In 10.1 the lba32-option is ignored, so it's once more that you are losing control and YaST2 just relies on auto-detection which fails. Just like with the insmod parameter... Anyway, what I did was: - patch the storage/src/modules/Partitions.ycp to global define integer BootCyl() ``{ + boot_cyl = 4*1024*1024*1024; if( boot_cyl == 0 ) so that boot_cyl is always large enough. Works here because all our hosts support lba32. - recompile yast2-storage package - put the compiled Partitions.ybc into the driverupdate file and installed my patched driverupdate Then AY works on the patched Partitions.ybc file and no /boot is created. However, the partitioning still fails. I've flipped the order for Partition 2 and 3 as you recommended (although I don't understand why this makes a difference when I use "partition_nr" for every partition), but now I end up with /dev/sda1 / ext3 /dev/sda2 swap swap /dev/sda3 extended partition /dev/sda5 /var ext3 /dev/sda6 /export reiserfs Although I specify four primary partitions (or does partition_nr not correspond to /dev/sda$partition_nr? Current profile is below. Do you have an idea what goes wrong here? 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> <partition_nr config:type="integer">1</partition_nr> <size>20gb</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <fstopt>defaults</fstopt> <mount>swap</mount> <partition_nr config:type="integer">2</partition_nr> <size>2gb</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <fstopt>defaults</fstopt> <mount>/var</mount> <partition_nr config:type="integer">3</partition_nr> <size>4gb</size> </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>defaults</fstopt> <mount>/export</mount> <partition_nr config:type="integer">4</partition_nr> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> -- 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. *