[opensuse-autoinstall] SoftwareRAID on GPT disks
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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.
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.
I've attached my example partitioning with static 1MB bios_grub
partition, 32GB swap, 1GB /boot, and max root partition:
<partitioning config:type="list">
<drive>
<device>/dev/sda</device>
<initialize config:type="boolean">true</initialize>
<partitions config:type="list">
<partition>
<create config:type="boolean">true</create>
<format config:type="boolean">false</format>
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 -- Thomas Fehr, SuSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Tel: +49-911-74053-0, Fax: +49-911-74053-482, Email: fehr@suse.de GPG public key available. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
-----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-----
On Mon, Sep 16, Lukas Puzik / myLoc managed IT AG wrote:
-----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.
Thanks for the log files.
I just talked to the bootloader maintainer and the support for
grub2 in this scenario is not fully implemented in openSuSE 12.3.
According to bootloader maintainer the setting of bios_grub
flag is not really needed. He suggests to use grub instead of
grub2, where everything is quite new and not yet really stable.
For grub you need one partition for /boot, swap and raid as
currently.
The autoyast.xml should contain a bootloader section like:
<bootloader>
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.
They are not created by yast2-storage but probably by bootloader itself. Maybe they are not reset, so they stay set in spite of a partition now used for swap instead of for booting. No idea if this is harmful you could try to reset them manually. Tschuess, Thomas Fehr -- Thomas Fehr, SuSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Tel: +49-911-74053-0, Fax: +49-911-74053-482, Email: fehr@suse.de GPG public key available. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Thomas! Thanks for your help, it works fine for all cases. Didn't expected, that this would be the solution. Best regards, Lukas Puzik Am 17.09.2013 14:11, schrieb Thomas Fehr:
On Mon, Sep 16, Lukas Puzik / myLoc managed IT AG wrote:
-----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.
Thanks for the log files.
I just talked to the bootloader maintainer and the support for grub2 in this scenario is not fully implemented in openSuSE 12.3. According to bootloader maintainer the setting of bios_grub flag is not really needed. He suggests to use grub instead of grub2, where everything is quite new and not yet really stable. For grub you need one partition for /boot, swap and raid as currently.
The autoyast.xml should contain a bootloader section like:
<bootloader>
grub </bootloader>to make it use grub instead of grub2.
If this does not work, just create a bug report at https://bugzilla.novell.com/ with full content of /var/log/YaST2 and autoyast xml file attached and assign it to me.
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.
They are not created by yast2-storage but probably by bootloader itself. Maybe they are not reset, so they stay set in spite of a partition now used for swap instead of for booting. No idea if this is harmful you could try to reset them manually.
Tschuess, Thomas Fehr
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSOIV/AAoJEAQWnOsU6N73ICAIAMIyQ8vY6nJlf2goFvrg+7tF P5dgon58PQSn65C7G6joyjvbi4Xk+0Rk6Bu9U41jrvMB106pnrhS1hFUsH6h1ra8 Gk+pdip2RgIX7qnOwUl26ywgMmVWVP0zWmhY0GWH9dPCJutxXqMrZ58uwg+qAVJN i2Q/auYNwOWQok4+DztGSpxT/WuNhe4dsy4aJdzFIrwNyzfE7YouWHNLQD5GBINX kVS1b7TKE4E5+D8w73Sn+E76uGcESVSNGrZTm6tThzrjw7Do0cDTuu7sItI6l6o2 Q3q5Xt5N/++mWa5110SI/eL8dwnQASuyevtwy+E30yVQYK7N3dWEqdHP5HZAG8k= =RU57 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
participants (2)
-
Lukas Puzik / myLoc managed IT AG -
Thomas Fehr