Error with partition proposal

English Install/Boot/Login
1

Hello to everybody.
I’m trying to install OpenSUSE LEAP 15 (but the same applied to the latest Tumbleweed) on an HP Elitedesk 800 G1 SFF.
The installation process goes fine up to the point where Yast should suggest a partitioning scheme. I get these three error in sequence:

The first is about an internal error in devicegraph.rb at line 153
http://susepaste.org/view/raw/7059130

The second tells me that “YaST module inst_disk_proposal has failed”. It suggests to check /var/log/YaST2/y2log but I have no idea how to get there during installation.
http://susepaste.org/view/raw/96344673

The third says that “inst_complex_welcome has failed”
http://susepaste.org/view/raw/15241385
I searched the internet about these errors but without success.
Through the limited BIOS interface of the machine I started the installation in UEFI and then in BIOS mode, but both led to the same error.
Do you have any advice?

Thanks in advance

2

I have not seen that particular error.

To report the bug:

CTRL-ALT-F2 will get you a command line as root.

Then the command

save_y2logs

will save the logs to a file (and tell you the name of the file)

From there, you need to copy that file to somewhere that stays around. I usually mount one of my partitions that I know is safe. Or I plug in a flash drive and mount that. If you need more hints on mounting something, then ask in a follow up reply.

3

Hi Miaguleti!

At first, excuse my English.

I had the same problem with installation. In my case the reason was in mount points to NTFS partitions. So I booted to the old system, unmount all partitions except root ("/") and “/home” and then started installation again. Error disappear and system was installed well.

4

Thanks for answering. Actually I’m starting from a blank (not new) disk, no previous installation on this one.
I’ll try to recollect the logs.

Thanks

5

Ok I managed to recover the logs file.
Upon a quick scan, it looks like the proposal is actually created, but then there is an error calling a “tostring”.
Here is an excerpt for the curious:

2018-07-09 08:32:19 <1> install(3647) [Ruby] y2storage/dump_manager.rb:264 Dumping Devicegraph to 02-proposed
2018-07-09 08:32:19 <1> install(3647) [Ruby] clients/inst_disk_proposal.rb:62 BEGIN of inst_disk_proposal
...]
2018-07-09 08:32:19 <3> install(3647) [libstorage] MdContainerImpl.cc:56 THROW:     invalid md-level for MdContainer
2018-07-09 08:32:19 <2> install(3647) [Ruby] yast/builtins.rb:586 tostring builtin called on wrong type Class
2018-07-09 08:32:19 <3> install(3647) [Ruby] yast/wfm.rb:253 Client /mounts/mp_0001/usr/share/YaST2/clients/inst_disk_proposal.rb failed with 'Storage::Exception' (Storage::Exception).
Backtrace:
/mounts/mp_0001/usr/share/YaST2/lib/y2storage/devicegraph.rb:153:in `initialize'
/mounts/mp_0001/usr/share/YaST2/lib/y2storage/devicegraph.rb:153:in `new'
/mounts/mp_0001/usr/share/YaST2/lib/y2storage/devicegraph.rb:153:in `actiongraph'
/mounts/mp_0001/usr/share/YaST2/lib/y2storage/dialogs/proposal.rb:54:in `initialize'
/mounts/mp_0001/usr/share/YaST2/lib/y2storage/clients/inst_disk_proposal.rb:65:in `new'
/mounts/mp_0001/usr/share/YaST2/lib/y2storage/clients/inst_disk_proposal.rb:65:in `run'
/mounts/mp_0001/usr/share/YaST2/clients/inst_disk_proposal.rb:25:in `&lt;top (required)&gt;'
/mounts/mp_0001/usr/lib64/ruby/vendor_ruby/2.5.0/yast/wfm.rb:313:in `eval'
/mounts/mp_0001/usr/lib64/ruby/vendor_ruby/2.5.0/yast/wfm.rb:313:in `run_client'
/mounts/mp_0001/usr/lib64/ruby/vendor_ruby/2.5.0/yast/wfm.rb:206:in `call_builtin'
/mounts/mp_0001/usr/lib64/ruby/vendor_ruby/2.5.0/yast/wfm.rb:206:in `call_builtin_wrapper'
/mounts/mp_0001/usr/lib64/ruby/vendor_ruby/2.5.0/yast/wfm.rb:195:in `CallFunction'
/mounts/mp_0001/usr/share/YaST2/modules/ProductControl.rb:1355:in `RunFrom'
/mounts/mp_0001/usr/share/YaST2/lib/installation/clients/inst_complex_welcome.rb:109:in `merge_and_run_workflow'
/mounts/mp_0001/usr/share/YaST2/lib/installation/clients/inst_complex_welcome.rb:73:in `block in main'
/mounts/mp_0001/usr/share/YaST2/lib/installation/clients/inst_complex_welcome.rb:65:in `loop'
/mounts/mp_0001/usr/share/YaST2/lib/installation/clients/inst_complex_welcome.rb:65:in `main'
/mounts/mp_0001/usr/share/YaST2/clients/inst_complex_welcome.rb:2:in `<top (required)>'
/mounts/mp_0001/usr/lib64/ruby/vendor_ruby/2.5.0/yast/wfm.rb:313:in `eval'
/mounts/mp_0001/usr/lib64/ruby/vendor_ruby/2.5.0/yast/wfm.rb:313:in `run_client'
/mounts/mp_0001/usr/lib64/ruby/vendor_ruby/2.5.0/yast/wfm.rb:206:in `call_builtin'
/mounts/mp_0001/usr/lib64/ruby/vendor_ruby/2.5.0/yast/wfm.rb:206:in `call_builtin_wrapper'
/mounts/mp_0001/usr/lib64/ruby/vendor_ruby/2.5.0/yast/wfm.rb:195:in `CallFunction'
/mounts/mp_0001/usr/share/YaST2/modules/ProductControl.rb:1355:in `RunFrom'
/mounts/mp_0001/usr/share/YaST2/modules/ProductControl.rb:1542:in `Run'
/mounts/mp_0001/usr/share/YaST2/lib/installation/clients/inst_worker_initial.rb:106:in `main'
/mounts/mp_0001/usr/share/YaST2/clients/inst_worker_initial.rb:2:in `&lt;top (required)&gt;'
/mounts/mp_0001/usr/lib64/ruby/vendor_ruby/2.5.0/yast/wfm.rb:313:in `eval'
/mounts/mp_0001/usr/lib64/ruby/vendor_ruby/2.5.0/yast/wfm.rb:313:in `run_client'
/mounts/mp_0001/usr/lib64/ruby/vendor_ruby/2.5.0/yast/wfm.rb:206:in `call_builtin'
/mounts/mp_0001/usr/lib64/ruby/vendor_ruby/2.5.0/yast/wfm.rb:206:in `call_builtin_wrapper'
/mounts/mp_0001/usr/lib64/ruby/vendor_ruby/2.5.0/yast/wfm.rb:195:in `CallFunction'
/mounts/mp_0001/usr/share/YaST2/lib/installation/clients/installation.rb:81:in `main'
/mounts/mp_0001/usr/share/YaST2/clients/installation.rb:2:in `<top (required)>'
/mounts/mp_0001/usr/lib64/ruby/vendor_ruby/2.5.0/yast/wfm.rb:313:in `eval'
/mounts/mp_0001/usr/lib64/ruby/vendor_ruby/2.5.0/yast/wfm.rb:313:in `run_client'
/mounts/mp_0001/usr/lib64/ruby/vendor_ruby/2.5.0/yast/wfm.rb:206:in `call_builtin'
/mounts/mp_0001/usr/lib64/ruby/vendor_ruby/2.5.0/yast/wfm.rb:206:in `call_builtin_wrapper'
/mounts/mp_0001/usr/lib64/ruby/vendor_ruby/2.5.0/yast/wfm.rb:195:in `CallFunction'
/usr/lib/YaST2/bin/y2start:58:in `<main>'

I’ll report this as a bug.
Meanwhile I’m trying with another disk or another machine.

Thanks

6

Bug reported