Leap 15.0 install failure with Crucial MX100 SSD

Greetings!
I’ve searched the forum for information, if I missed it I apologize.
I have successfully installed Leap 15.0 on a ‘rotating’ hard drive on another machine.
Now I am attempting to install to a Crucial MX100 SSD (128GB). It has a normal SATA connection (slightly used from an old XP machine) and it fails right after the licence page…“Configure iSCSI Disks”.
Clicking ‘Next’ it shows probing the hardware but breaks on Hard disks.
"ERROR
Internal error. Please report a bug with logs
Details:undefined method ‘auto?’ for #<Yast::ModeClass:0x000000000152c158>Did you mean ? auto
Caller: /mounts/YaST/lib/installation/clients/inst_system_analysis.rb:199:in’ActionHDDProbe’

Start the Ruby debugger now and debug the issue? (Experts only)"

Upon clicking ‘No’ and Next I get another error screen:

Calling the YaST module 'inst_system_analysis has failed.
More information can be found near the end of the ‘/var/log/YaST2/y2log’ file.

This is worth reporting a bug at http://bugzilla.suse.com/.
Please attach also all YaST logs stored in the ‘/var/log/YaST2/’ directory.
See http://en.opensuse.org/Bugs/YaST for more information about YaST logs.

I can’t seem to attach files of these two screen images.

And, of course I can not look at any logs, as the installation failed.

Any suggestions that might help me use the SSD?

Have fun,
Paxton
http://happyhome.org/web/suse/insterror1

Hi
I would boot the system and select the system BIOS and check it sees the drive. If it doesn’t check the SATA cable and power connections.

If it does see it, is this system UEFI or Legacy booting? Perhaps the SSD is set to gpt type (for UEFI), rather than dos (for Legacy).

Oh, did you check the download iso md5/sha256 sum to verify your download?

Else consider a live Tumbleweed desktop to check the system and disk, I normally do this to preconfigure the drive before install via gdisk/fdisk.

Once the license page has been reached, text vttys are available, Ctrl-Alt-F2 among others. From there one can, among other things, run save_y2logs, view logs, and copy logs and screenshots to floppy, USB, network share, or a mountable HD filesystem.

Thanks, Malcolm.
A little ‘red faced’ but problem solved. I think I did not have the SSD connected properly. Doing too many cable switches.

Maybe a “hard disk not found” messaged :slight_smile:

Paxton