Re: Factory CD boot problem

On Mon, Feb 23, 2015 at 2:10 AM, Andreas Färber <[email protected]> wrote:
> Am 23.02.2015 um 00:22 schrieb Dinar Valeev:
>> On Mon, Feb 23, 2015 at 12:01 AM, Andreas Färber <[email protected]> wrote:
>>> Am 22.02.2015 um 22:49 schrieb Dinar Valeev:
>>>> The yast issue has been fixed, it just needs to find its way to
>>>> Factory tree..
>>>
>>> So what exactly is it about?
>> http://bugzilla.opensuse.org/show_bug.cgi?id=917833
>
> OK. Neither that nor https://github.com/yast/yast-bootloader/pull/222
> really says what effect exactly this error has though? grub2 bootloader
> seemed installed okay.
This error can be workarounded by grub2-install /dev/sda1

Assuming your PReP partition is the first one.
>
> What I notice is that my disk partitioning is wrong. I had two old btrfs
> partitions; I overrode the default suggestion to take the whole disk and
> then edited the proposal to not create a separate xfs home partition
> (unchecked the option). What it did is it left the old home partition
> sda7 alone and installed the root into sda6. Is that related or a
> separate issue with yast2-partitioner?
>
> When I chroot into my sda6 via the installer rescue system option and
> run "yast bootloader", manually patched as in
> https://github.com/yast/yast-bootloader/commit/cbbe4229bd12c78f94efe058a3f6d67cb1b6bd91,
> then I get:
>
> Error
> Internal error. Please report a bug report with logs.
> Details: undefined method `first' for nil:NilClass
> Caller:  /usr/share/YaST2/modules/BootStorage.rb:422:in `detect_disks'
>
> I assume that is because Factory is still at 3.1.120? That particular
> file didn't change since then though:
> https://github.com/yast/yast-bootloader/commits/master/src/modules/BootStorage.rb
I wouldn't trust yast here :)
>
> Regards,
> Andreas
>
> --
> SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
> GF: Felix Imendörffer, Jane Smithard, Jennifer Guild, Dilip Upmanyu,
> Graham Norton; HRB 21284 (AG Nürnberg)
-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]