IÂ´m trying to do an unattendet autoyast install on SLES 11 SP3 with a harddisk layout that looks as follows:
/dev/sda1 /boot ext3
/dev/sdb complete disk without making a partition /dev/sdb1 in volume group vg0
/dev/sdc complete disk without making a partition /dev/sdb1 in volume group vg1
/dev/vg0/lv_root /root xfs
/dev/vg0/lvxxxxx … …
/dev/vg1/lv_userdata /userdata xfs
Unfortunately the installation stops with the error: “Bei der folgenden Aktion ist ein Fehler aufgetreten: Volumegroup vg0 (0 B) wird aus erstellt.
“Volumegroup vg0 (0 B) will be created from . Systemerror -4004”
Is it possible to do this setup with autoyast. I can make the setup interactive with these settings. The server works fine.
Cloning this fresh server and deploying the created autoinst.xml results in the above error.
this response is pure guesswork, but: I’m pretty sure someone simply made partitioning an implicit requirement.
So in the end, even if it is a waste of a number of blocks, I recommend to create that single partition covering (almost) the whole disk, even if it seems a waste of space. If for nothing else, be motivated by the poor admin soul following you and scratching his/her head, trying to grasp what had happened that the partition table got lost on those two disks
BTW: Things get worse when you use USB devices - there are different OS assumptions about different types of “USB media” (including making assumptions based on the “removable media” flag). You may end up partitioning a device just for good measure, but the next system you plug the device (or i.e. CF card) into won’t work, because it assumes the FS is using the complete device…
I’m trying to accomplish the same as Alexander but get obviously the same error.
Also did a manual install with the option to create an autoinst.xml file. In this manual install i could use /dev/sdb as PV and did not need to create a partition, but the generated xml file is not working (and indeed makes no sense when I try to analyze it)
If people think that disks have to be partioned, well then IMHO they should not be working in a operating system company.
There is even a similar post from jan 2012 (https://forums.suse.com/archive/index.php/t-39.html). So had hoped that novell had fixed or changed it by now, but I’m afraid not
these forums are run by users for users, there’s no official SUSE/Novell participation and this is not the way to report bugs. Have you opened a service request? Then I’d like to have a peek at what the “officials” are saying on the subject…
I don’t have created a service request (yet), since I need the future now. So the request might still be an action to do.
For those interested, I have created some config which gets the job done. It’s odne via the postpartitioning-scripts. I have first tried every option to do it via the pre-scripts but it failed every time somewhere.
So the approach is to have the partitioning done by autoyast (but then it uses lvm on a partition) and after the partition is done, to backup some files, destroy the lvm config of yast and rebuild the lvm on top of sdb. Code snipptes from the xml file are below:
disk layout for yast:
and the postpartitioning-scripts part: (I know there is some funny looking code in it but this is because our xml files are generated from an internal cmdb tool, so because of that some dirty hacks were needed :-))
See the partitioning xml code in my previous post, that works if it’s fine with you to get your PV on a partition instead of the whole disk.
If you need the PV to cover the whole disk without partition, then it’s not possible unless you use the postpartitioning-scripts.
Can you post your partitioning xml?