[atomic-wg] Issue #443: Boot from ISO stuck at Reached target Basic System

[Rares Vernica]

rares reported a new issue against the project: `atomic-wg` that you are following:
``
I got `Fedora-Atomic-ostree-x86_64-27-20180314.0.iso` on a USB stick. When booting from
USB, I get as far as:
~~~~
...
[ OK ] Reached target paths.
[ OK ] Reached target Basic System.
_
~~~~
Than it get stack there forever.

On the same hardware, I was able to boot and install previous versions of the ISO.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/443

[Dusty Mabe]

dustymabe added a new comment to an issue you are following:
``
hi. Thanks for the report!

Can you answer a few questions?

- How did you place the `Fedora-Atomic-ostree-x86_64-27-20180314.0.iso` onto the USB
stick?
- What were the previous versions that worked for you?
- Do you know if your system is using EFI or booting using legacy mode? 
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/443

[Rares Vernica]

rares added a new comment to an issue you are following:
``
To answer you questions:

* `dd bs=4M if=Fedora-Atomic-ostree-x86_64-27-20180314.0.iso of=/dev/sdb`
* Actually, after checking it, the one that worked was
`CentOS-Atomic-Host-7-Installer.iso`, downloaded on 11/3/2017
* I believe it is legacy. There is no option to disable EFI, so that makes me think there
is no EFI

A few more notes:

* The workstation has LSI MPT SAS BIOS, but the adapter is disabled from its BIOS
configuration utility
* Regarding the BIOS storage settings, I tried `SATA Emulation`: 
    * `IDE`
    * `RAID+AHCI` with `GEN1/1.5Gbps` and `GEN2/3.0Gbps`
* I also pulled the HDDs out and tried to boot without them on
* When it starts up there are a few (probably unrelated errors) like:
    * `ACPI Error: [CAPD] Namespace lookup failure...`
    * `ACPI Error: Method parse/execution failed...`
    * `dracut-pre-udev[618]: rpc.idmapd: conf_reinit: oone ... failed`

``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/443

[Rares Vernica]

rares added a new comment to an issue you are following:
``
I think I found the cause and a workaround. If I go to `Troubleshooting` in the boot menu
and select `Install ... in basic graphics mode`, it moves past that step and successfully
loads the installer.

CentOS Atomic also has the same problem, it just gets stuck at a different step.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/443

[Dusty Mabe]

dustymabe added a new comment to an issue you are following:
``
>  I think I found the cause and a workaround. If I go to
> Troubleshooting in the boot menu and select Install ... in basic graphics mode, it moves
> past that step and successfully loads the installer.
>  
odd. so do we think this is a graphics driver issue? 

>  CentOS Atomic also has the same problem, it just gets stuck at a
> different step. 
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/443