Univention Bugzilla – Bug 24648
Erzeugung eines fehlerhaften Installationsprofils
Last modified: 2013-11-19 06:42:26 CET
Created attachment 3812 [details] installation_profile Wird ein System profilbasiert mit UCS 3.0-0 installiert, taucht die Megabyteangabe anschließend im fertig installierten System doppelt auf: root@mas76:~# grep ^dev_ /etc/univention/installation_profile dev_1='PHY /dev/sda3 0 1 none 1908MM 23000MM lvm' dev_0='PHY /dev/sda2 0 1 linux-swap 320MM 1908MM ' dev_3='PHY /dev/sda1 0 1 ext3 1MM 320MM /boot boot' dev_2='LVM /dev/vg_ucs/rootfs LVMLV 1 ext4 0MM 20092MM / None'
Installiert mit folgendem Profil: domainname='new.test' auto_reboot='no' bootloader_record='/dev/vda' ldap_base='dc=new,dc=test' auto_join='false' timezone='Europe/Berlin' cdrom_device='nfs:10.200.7.150:/var/lib/univention-repository/' locales='de_DE.UTF-8:UTF-8' eth0_type='dhcp' hostname='mymem' fqdn='mymem.new.test' use_efi='no' keymap='de-latin1' partitiontable_type='GPT' locale_default='de_DE.UTF-8:UTF-8' dev_4='PHY /dev/vda2 0 1 ext4 24M 536M /boot none' dev_2='PHY /dev/vda4 0 1 none 2555M 20352M None lvm' dev_1='PHY /dev/vda3 0 1 linux-swap 536M 2555M None linux-swap' dev_0='PHY /dev/vda1 0 0 none 16M 24M None bios_grub' dev_3='LVM /dev/vg_ucs/rootfs LVMLV 0 ext4 0M 17792M / none' system_role='memberserver' bootloader_record="/dev/vda" disks="/dev/vda" part_delete="all" lvm_delete="/dev/vg_ucs/*" Dann bekomme ich folgendes in /etc/univention/installation_profile: dev_4='PHY /dev/vda2 0 1 ext4 24MiB 536MiB /boot none' dev_1='PHY /dev/vda3 0 1 linux-swap 536MiB 2555MiB None linux-swap' dev_0='PHY /dev/vda1 0 0 none 16MiB 24MiB None bios_grub' dev_3='LVM /dev/vg_ucs/rootfs LVMLV 0 ext4 0MiB 17792MiB / none' dev_2='PHY /dev/vda4 0 1 none 2555MiB 20352MiB None lvm'
A installation with this "MiB" profile also works.
Created attachment 5386 [details] Traceback
If I try to install with the current Univention Net Installer and the profile from Comment 1 I get the traceback from the attached screenshot.
(In reply to Moritz Muehlenhoff from comment #4) > If I try to install with the current Univention Net Installer and the > profile from Comment 1 I get the traceback from the attached screenshot. Looks like no partitiontable is present on the disk. The following line within the profile seems to be missing: create_partitiontable="/dev/vda"
(In reply to Sönke Schwardt-Krummrich from comment #5) > (In reply to Moritz Muehlenhoff from comment #4) > > If I try to install with the current Univention Net Installer and the > > profile from Comment 1 I get the traceback from the attached screenshot. > > Looks like no partitiontable is present on the disk. > The following line within the profile seems to be missing: > > create_partitiontable="/dev/vda" If I add this, the installation completes, but the installed system fails to boot once installed, see screenshot.
Created attachment 5387 [details] Systems fails to boot after PXE installation
Just test if portioning options in the installation profile for a profile based installation is correct. -> dev_1='PHY /dev/sda3 0 1 none 1908MM 23000MM lvm' -> WRONG (MM) -> dev_4='PHY /dev/vda2 0 1 ext4 24MiB 536MiB /boot none' -> CORRECT (MiB) -> dev_4='PHY /dev/vda2 0 1 ext4 24M 536M /boot none' -> CORRECT (M)
I made a profile-based installation and the partition info was generated correctly: root@basesystem:~# grep ^dev /etc/univention/installation_profile dev_4='PHY /dev/sda2 0 0 ext4 24MiB 536MiB /boot none' dev_1='PHY /dev/sda3 0 0 linux-swap 536MiB 8402MiB None linux-swap' dev_0='PHY /dev/sda1 0 0 none 16MiB 24MiB None bios_grub' dev_3='LVM /dev/vg_ucs/rootfs LVMLV 0 ext4 0MiB 144204MiB / none' dev_2='PHY /dev/sda4 0 0 none 8403MiB 152499MiB None lvm'
UCS 3.2 has been released: http://docs.univention.de/release-notes-3.2-en.html http://docs.univention.de/release-notes-3.2-de.html If this error occurs again, please use "Clone This Bug".