-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Thomas, thanks for your message. I've attached the desired logs and control file to this mail. I've noticed during the successfull installation without SoftwareRAID today, that autoyast actually doesn't set bios_grub, it only creates the first partition with an offset of 1049kB in both cases. I've probably mixed it up with another installation. I've also performed an installation with SoftwareRAID and made a screenshot of a parted print after the first error message. I don't understand why the swap partition will be set up with boot and legacy_boot flags. Best regards, Lukas Puzik Am 16.09.2013 14:16, schrieb Thomas Fehr:
Hi,
On Mon, Sep 16, Lukas Puzik / myLoc managed IT AG wrote:
Hello!
I'm fighting for a week with autoyast and a SoftwareRAID partitoning on non-EFI servers with two 3-4 TB disks. I've figured out, that autoyast successfully applies my profile to the servers, as long as I don't set up a SoftwareRAID. Means, that autoyast creates automatically a bios_grub partition and installs GRUB2 correctly, the server is able to boot from a 2.7 TB root partiton. I don't need to do anything.
If possible, I would be interested to see complete content of /var/log/YaST2 and autoyast control file for both cases (the successful one without SoftwareRAID and the unsuccessful one with SoftwareRAID) see what is going on.
So far I cannot see how autoyast would automatically create a bios_grub partition. Since bios_grub stuff is fairly new it could very well be possible that there are bugs lurking in this area.
As soon as I'm using a SoftwareRAID partitioning, autoyast doesn't create the above mentioned bios_grub partition and bootlader instalation fails, the operating system isn't bootable. It's possible to workaround this issue by manually creating the bios_grub partiton in the partitioning context and to manually enabling bios_grub to this partiton with parted in postpartitioning-scripts, nevertheless GRUB2 will show the same error messages as before, which can't be timed out using error context. But, operating system will boot up correctly from a 2.7 TB md device.
...
As I need a fully unattended installation for a SoftwareRAID sceanrio, I'm hoping for a clean solution or a tip how to avoid bootloader context error messages, so no user interaction is needed. In fact other distributions like CentOS 6, Debian 7.0 and Ubuntu 12.04 don't show this issue, so I think, that this is a bug or limitation, not a general issue.
Tschuess, Thomas Fehr
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSNyQuAAoJEAQWnOsU6N73ODUH/R0a1ho2LjDX+Ow8fbFbpGtx I73tD5KyRhaZEJ+Z/Bs7vPwtSO7gphQOOOvgzoXzWLX1+CZZw98ajuzXPW8+Ow8k 1YUKFpdtjXeMHvFMPtUCyV4ov0S3+HoPmfsvK4/VmKdZiPWTCZuOj+LydGHv9Pbh gJWdhfuec+Es5f8FtBcHMZS9YmCMV8oOPGiibo00ArIiC5oAVWWKDYqRxtdboKpk u6PaQyK4Wh+XwPhTPMSTc971hIhtrL/HM78yc9G7xhkHhQ/x0eW0UGa7MTEWSHG/ GCiJDBrbIt5K3YO/pIHq5iOeeRCrZxijZFP5VogtDNNNJeA8n+EHmafv2xy5KF4= =zmsn -----END PGP SIGNATURE-----