[Starlingx-discuss] StarlingX ISO Image from Cengn Mirror not working on Artesyn/MaxCore

Penney, Don Don.Penney at windriver.com
Mon Jan 14 15:05:15 UTC 2019


Hi Marcel,

When you're at the boot option you want to choose from the installer menu, hit <tab> to edit the boot command-line and modify the boot_device and rootfs_device parameters from the default sda to the correct device name (ie. nvme0n1).

Cheers,
Don.


-----Original Message-----
From: Marcel Schaible [mailto:marcel at schaible-consulting.de] 
Sent: Monday, January 14, 2019 10:00 AM
To: Little, Scott; Penney, Don; starlingx-discuss at lists.starlingx.io
Subject: Re: [Starlingx-discuss] StarlingX ISO Image from Cengn Mirror not working on Artesyn/MaxCore

Hi,

the image lloks better. At least I am getting now the installer screen.

Now I am getting the following error:

<--- snipp --->
anaconda 21.48.22.121-1 for CentOS 7 started.
 * installation log files are stored in /tmp during the installation
 * shell is available on TTY2
 * when reporting a bug add logs from /tmp as separate text/plain attachments
02:17:51 Running pre-installation scripts

There was an error running the kickstart script at line 256.  This is a fatal error and installation will be aborted.  The details of this error are:

Installation failed.

ERROR: Specified installation (sda) or boot (sda) device is a USB drive.
<--- snipp --->


Question: How can I confugure the installation/root device? I my case I have 2 1TB nvme flash drives.

Thanks for your help in advance

Marcel
> Scott Little <scott.little at windriver.com> hat am 9. Januar 2019 um 21:54 geschrieben:
> 
> 
> Fix as of this image ...
> 
> http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190109T162801Z/outputs/iso/bootimage.iso 
> <http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/20190109T162801Z/outputs/iso/bootimage.iso>
> 
> 
> On 2019-01-09 11:08 a.m., Penney, Don wrote:
> > I just checked the latest CENGN ISO, and it's still using the unmodified installer image. See attached email thread.
> >
> > Scott, any update on this issue?
> >
> > -----Original Message-----
> > From: Marcel Schaible [mailto:marcel at schaible-consulting.de]
> > Sent: Wednesday, January 09, 2019 10:24 AM
> > To: starlingx-discuss at lists.starlingx.io
> > Subject: [Starlingx-discuss] StarlingX ISO Image from Cengn Mirror not working on Artesyn/MaxCore
> >
> > Hi,
> >
> > I am trying to give the above mentioned ISO image a try on our ArteSyn/MaxCore box without success.
> >
> > After starting the installation I'll get the following message:
> >
> > [   18.503656] localhost iscsid[643]: iSCSI daemon with pid=644 started!
> > [   18.503816] localhost iscsid[643]: can't open InitiatorName configuration file /etc/iscsi/initiatorname.iscsi
> > [   18.503949] localhost iscsid[643]: Warning: InitiatorName file /etc/iscsi/initiatorname.iscsi does not exist or does not contain a properly formatted InitiatorName. If using software iscsi (iscsi_tcp or ib_iser) or partial offload (bnx2i or cxgbi iscsi), you may not be able to log into or
> > [   18.504121] localhost iscsid[643]: can't open InitiatorAlias configuration file /etc/iscsi/initiatorname.iscsi
> > [   18.504254] localhost iscsid[643]: can't open iscsid.safe_logout configuration file /etc/iscsi/iscsid.conf
> > [   21.185105] localhost kernel: scsi 0:0:0:0: Direct-Access     Generic  Ultra HS-COMBO   1.98 PQ: 0 ANSI: 0
> > [   21.204488] localhost kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk
> > [   18.665925] localhost multipathd[636]: sda: add path (uevent)
> > [   18.667242] localhost multipathd[636]: sda: failed to get path uid
> > [   18.667399] localhost multipathd[636]: uevent trigger error
> > [   21.930592] localhost kernel: scsi 1:0:0:0: Direct-Access     TrekStor TrekStor USB CS       PQ: 0 ANSI: 0 CCS
> > [   21.940187] localhost kernel: scsi 1:0:0:0: alua: supports implicit and explicit TPGS
> > [   21.947210] localhost kernel: scsi 1:0:0:0: alua: No target port descriptors found
> > [   21.953921] localhost kernel: scsi 1:0:0:0: alua: not attached
> > [   21.959034] localhost kernel: sd 1:0:0:0: [sdb] 15257600 512-byte logical blocks: (7.81 GB/7.27 GiB)
> > [   21.968220] localhost kernel: sd 1:0:0:0: [sdb] Write Protect is off
> > [   21.973575] localhost kernel: sd 1:0:0:0: [sdb] Mode Sense: 43 00 00 00
> > [   21.974314] localhost kernel: sd 1:0:0:0: [sdb] No Caching mode page found
> > [   21.980260] localhost kernel: sd 1:0:0:0: [sdb] Assuming drive cache: write through
> > [   21.990203] localhost kernel:  sdb: sdb1
> > [   21.994973] localhost kernel: sd 1:0:0:0: [sdb] Attached SCSI removable disk
> > [   19.533105] localhost multipathd[636]: sdb: add path (uevent)
> > [   63.961502] localhost kernel: random: crng init done
> > [  142.536373] localhost dracut-initqueue[646]: Warning: dracut-initqueue timeout - starting timeout scripts
> > ...
> > [  203.386668] localhost dracut-initqueue[646]: Warning: Could not boot.
> > [  204.505706] localhost systemd[1]: Received SIGRTMIN+20 from PID 625 (plymouthd).
> > [  204.505980] localhost dracut-initqueue[646]: Warning: /dev/root does not exist
> > [  204.514883] localhost systemd[1]: Starting Dracut Emergency Shell...
> > [  204.532145] localhost systemd[1]: Received SIGRTMIN+21 from PID 625 (plymouthd).
> >
> > I suspect that the installer is not finding the disk, which is in our case nvme0n1 and nvme1n1 flash storage.
> >
> > Any idea or hint is welcome!
> >
> > Thanks
> >
> > Marcel
> >
> > _______________________________________________
> > Starlingx-discuss mailing list
> > Starlingx-discuss at lists.starlingx.io
> > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
> 
>


More information about the Starlingx-discuss mailing list