nexus 9k keep going to loader

Before posting something, READ the changelog, WATCH the videos, howto and provide following:
Your install is: Bare metal, ESXi, what CPU model, RAM, HD, what EVE version you have, output of the uname -a and any other info that might help us faster.

Moderator: mike

Post Reply
ghostmm
Posts: 1
Joined: Sun May 06, 2018 6:16 pm

nexus 9k keep going to loader

Post by ghostmm » Wed May 09, 2018 5:04 pm

Hello,

The nexus 9k keep going to loader. I have laptop with 24 G RAM and quad cpu i7. I tried so many thing, repete the guide multiple time, use different image, increase RAM/CPU for VM but nothing work. Please see blow boot sequence which is look normal be at the end it's restart and goes to loader.



loader > boot nxos.7.0.3.I5.2.bin
Booting nxos.7.0.3.I5.2.bin
Trying diskboot
dev_str: bootflash: partition_str: 3 filename_str /nxos.7.0.3.I5.2.bin
command = root (hd0,3)
Filesystem type is ext2fs, partition type 0x83
Formed cmdline console=ttyS0,115200n8nn loader_ver="5.00.9" quiet debug
Formed cmdline console=ttyS0,115200n8nn loader_ver="5.00.9" quiet debug ksim g=nxos.7.0.3.I5.2.bin card_index=21099 dummy_sprom
Booting kickstart image: bootflash::3:/nxos.7.0.3.I5.2.bin....
Number of devices detected by BIOS is 1
NBI header
magic: 1b031336, len: 54, location: 94400000 (bx=0, ds=9440), exec addr: 9280000 0 16 16

segment header
length: 4, vendor: 11 flags: 0, loadaddr: 94000, image len: 200, memory length: 400
Reading data for kernel param. Len 512
Cmd line: console=ttyS0,115200n8nn loader_ver="5.00.9" quiet debug ksimg=nxo s.7.0.3.I5.2.bin card_index=21099 dummy_sprom rw root=/dev/ram0 rdbase=0x800000 0 ip=off ramdisk_size=131072 panic=5 quiet coredump_filter=0xb mtdparts=physmap- flash.0:256k(RR_LOG),512k(mtdoops),16M(plog),16M(trace) intel_idle.max_cstate=2 pcie_ports=native nopat slub_debug=- cpuidle.off=1

segment header
length: 4, vendor: 14 flags: 0, loadaddr: 100000, image len: 520e00, memory leng th: 800000
Loading kernel length 5377536
file_size 5377536 real_size 4456 prot_kernel_size 5361664 setupsects 30
x86_64/loader/linux.c:102: real_size = 2000, prot_size = 51d000, mmap_size = 6f0
x86_64/loader/linux.c:133: physical_start = 1000, physical_end = 9f000
x86_64/loader/linux.c:146: trying to allocate 2 pages at 9d000
Trying to allocate 1309 pages for VMLINUZ
Allocated prot_mode_mem 0xbd2d3000 real_mode_mem 0x0009d000
[Linux-EFI, setup=0x1168, size=0x51d000]

segment header
length: 14, vendor: 15 flags: 0, loadaddr: a21000, image len: 2cd18000, memory l ength: 10000000
Loading intird 751927296
x86_64/loader/linux.c:573: initrd_pages: 183576
x86_64/loader/linux.c:584: addr_min: 0x0 addr_max: 0x7ffff000 mmap_size: 1824
x86_64/loader/linux.c:603: desc = {type=7,ps=0x1000,vs=0x0,sz=156,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0x100000,vs=0x0,sz=1792,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0x808000,vs=0x0,sz=8,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0x818000,vs=0x0,sz=8,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0x1300000,vs=0x0,sz=518141,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0x80000000,vs=0x0,sz=245054,attr=15 }
x86_64/loader/linux.c:603: desc = {type=7,ps=0xbbd5e000,vs=0x0,sz=5493,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0xbd86c000,vs=0x0,sz=121,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0xbf8d5000,vs=0x0,sz=2,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0xbfd70000,vs=0x0,sz=16,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0x100000000,vs=0x0,sz=1310720,attr= 15}

Loading [717M/717M]
[Initrd, addr=0x52de5000, size=0x2cd18000]

segment header
length: 4, vendor: 16 flags: 4, loadaddr: 2500000, image len: 800, memory length : 800
Reading data for vendor seg. Length 2048
Leaving grub land

image length read 757307904

image hash: d974d4f1 de71969f 7b81ba39 a4111ee0
[ 104.584133] [1525884466] Error: Could not find mtd devices
Installing klm_card_index
done
INIT: version 2.88 booting
Installing ata_piix module ... done.
Unsquashing rootfs ...
Installing isan procfs ... done.
Installing SSE module with card index 21099 ... done.
Creating SSE device node 248 ... done.
Loading I2C driver ... done.
Installing CCTRL driver for card_type 29 on a VM without NEED_GEM ... done.
242.01: Interrupt throttling disabled. No cctrl irq detected.
Loading IGB driver ... done.
Not Micron SSD...

Checking all filesystems.Warning: switch is starting up with default configurati on

Installing SPROM driver ... IS_N9K done.
IS_SUP:; IS_SC:; IS_FC:; IS_LC:; IS_TOR:y done.
Installing pfmsvcs module with SPROM card index 21099 ... done.
Installing nvram module ... done.
Installing if_index module with port mode 6 ... done.
Installing RNI lcnd ... done
Installing LC netdev ... done
Installing psdev module ... done.
Installing veobc module ... done.
Inserting OBFL module ... done.
Making OBFL character devices
mounting plog for N9k!
Mounting OBFL pstore
Trying to mount cdrom...
Starting OpenBSD Secure Shell server: sshd ... done.
tune2fs 1.42.1 (17-Feb-2012)
Setting reserved blocks percentage to 0% (0 blocks)
Starting portmap daemon...
creating NFS state directory: done
starting 8 nfsd kernel threads: done
starting mountd: done
starting statd: done
Saving image for img-sync ...
Loading system software
Installing local RPMS
Patch Repository Setup completed successfully
Creating /dev/mcelog
Starting mcelog daemon
Overwriting dme stub lib
File /etc/shared/localtime does not exist.
INIT: Entering runlevel: 3
Running S93thirdparty-script...

Populating conf files for hybrid sysmgr ...
Starting hybrid sysmgr ...
inserting /isan/lib/modules/klm_cisco_nb.o ... done
2018 May 9 16:52:32 %$ VDC-1 %$ May 9 16:52:32 %KERN-0-SYSTEM_MSG: [ 104.584133] [1525884466] Error: Could not find mtd devices - kernel
2018 May 9 16:52:32 %$ VDC-1 %$ May 9 16:52:32 %KERN-2-SYSTEM_MSG: [ 251.094195] Initializing NVRAM Block 1 - kernel
2018 May 9 16:52:32 %$ VDC-1 %$ May 9 16:52:32 %KERN-2-SYSTEM_MSG: [ 251.094222] Initializing NVRAM Block 2 - kernel
2018 May 9 16:52:32 %$ VDC-1 %$ May 9 16:52:32 %KERN-2-SYSTEM_MSG: [ 251.094237] Initializing NVRAM Block 3 - kernel
2018 May 9 16:52:32 %$ VDC-1 %$ May 9 16:52:32 %KERN-2-SYSTEM_MSG: [ 251.094422] Initializing NVRAM Block 4 - kernel
2018 May 9 16:52:32 %$ VDC-1 %$ May 9 16:52:32 %KERN-2-SYSTEM_MSG: [ 251.095081] Initializing NVRAM Block 5 - kernel
2018 May 9 16:52:32 %$ VDC-1 %$ May 9 16:52:32 %KERN-2-SYSTEM_MSG: [ 251.095186] Initializing NVRAM Block 6 - kernel
2018 May 9 16:52:32 %$ VDC-1 %$ May 9 16:52:32 %KERN-2-SYSTEM_MSG: [ 251.095403] Initializing NVRAM Block 7 - kernel
2018 May 9 16:52:32 %$ VDC-1 %$ May 9 16:52:32 %KERN-2-SYSTEM_MSG: [ 251.095418] Initializing NVRAM Block 8 - kernel
2018 May 9 16:52:32 %$ VDC-1 %$ May 9 16:52:32 %KERN-2-SYSTEM_MSG: [ 251.095511] Initializing NVRAM Block 9 - kernel
2018 May 9 16:52:32 %$ VDC-1 %$ May 9 16:52:32 %KERN-2-SYSTEM_MSG: [ 251.095536] Initializing NVRAM Block 10 - kernel
2018 May 9 16:52:32 %$ VDC-1 %$ May 9 16:52:32 %KERN-2-SYSTEM_MSG: [ 251.095561] Initializing NVRAM Block 11 - kernel
2018 May 9 16:52:32 %$ VDC-1 %$ May 9 16:52:32 %KERN-2-SYSTEM_MSG: [ 251.095586] Initializing NVRAM Block 12 - kernel
2018 May 9 16:52:32 %$ VDC-1 %$ May 9 16:52:32 %KERN-2-SYSTEM_MSG: [ 251.095600] Initializing NVRAM Block 13 - kernel
2018 May 9 16:52:32 %$ VDC-1 %$ May 9 16:52:32 %KERN-2-SYSTEM_MSG: [ 251.095625] Initializing NVRAM Block 14 - kernel
2018 May 9 16:52:32 %$ VDC-1 %$ May 9 16:52:32 %KERN-2-SYSTEM_MSG: [ 251.095672] Initializing NVRAM Block 15 - kernel
2018 May 9 16:52:32 %$ VDC-1 %$ May 9 16:52:32 %KERN-2-SYSTEM_MSG: [ 251.095697] Initializing NVRAM Block 16 - kernel
2018 May 9 16:52:32 %$ VDC-1 %$ May 9 16:52:32 %KERN-2-SYSTEM_MSG: [ 251.095722] Initializing NVRAM Block 17 - kernel
2018 May 9 16:52:32 %$ VDC-1 %$ May 9 16:52:32 %KERN-2-SYSTEM_MSG: [ 251.096855] Initializing NVRAM Block 18 - kernel
2018 May 9 16:52:32 %$ VDC-1 %$ May 9 16:52:32 %KERN-2-SYSTEM_MSG: [ 251.096870] Initializing NVRAM Block 19 - kernel
2018 May 9 16:52:32 %$ VDC-1 %$ May 9 16:52:32 %KERN-2-SYSTEM_MSG: [ 251.097556] Initializing NVRAM Block 20 - kernel
2018 May 9 16:52:32 %$ VDC-1 %$ May 9 16:52:32 %KERN-2-SYSTEM_MSG: [ 251.097652] Initializing NVRAM Block 21 - kernel
2018 May 9 16:52:32 %$ VDC-1 %$ May 9 16:52:32 %KERN-2-SYSTEM_MSG: [ 251.097667] Initializing NVRAM Block 22 - kernel
2018 May 9 16:52:32 %$ VDC-1 %$ May 9 16:52:32 %KERN-2-SYSTEM_MSG: [ 251.098030] Initializing NVRAM Block 23 - kernel
2018 May 9 16:52:32 %$ VDC-1 %$ May 9 16:52:32 %KERN-2-SYSTEM_MSG: [ 251.438287] hwport mode=6 - kernel
2018 May 9 16:52:39 %$ VDC-1 %$ %USER-0-SYSTEM_MSG: before access to bkout_cfg - clis
System is coming up ... Please wait ...
System is coming up ... Please wait ...
2018 May 9 16:52:53 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: <<%USBHSD-2-MOUNT>> logflash: online - usbhsd
System is coming up ... Please wait ...
System is coming up ... Please wait ...
2018 May 9 16:53:13 %$ VDC-1 %$ %VMAN-2-INSTALL_STATE: Installing virtual service 'guestshell+'
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
2018 May 9 16:53:45 %$ VDC-1 %$ %SYSMGR-2-SIGKILL_FAILURE: Service "pixm_vl" failure to respond to SIGKILL causing supervisor to reset. Last heartbeat 60.07 secs ago.
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
System is coming up ... Please wait ...
[ 731.114060] [1525885096] Restarting system.

ramindia
Posts: 409
Joined: Sun Mar 19, 2017 10:27 pm

Re: nexus 9k keep going to loader

Post by ramindia » Sat May 12, 2018 6:26 am

Suggestion is :

When you see loader prompt

boot with your nxos image,

once it is booted, set the boot variable in config mode and save config and reboot.

R!

Uldis (UD)
Posts: 5080
Joined: Wed Mar 15, 2017 4:44 pm
Location: London
Contact:

Re: nexus 9k keep going to loader

Post by Uldis (UD) » Sat May 12, 2018 7:51 am

in our HOW to is is given what you should do after first time NX9K boot. !!!

http://www.eve-ng.net/documentation/how ... x9k-switch

UD

darko
Posts: 92
Joined: Tue Oct 24, 2017 2:42 pm

Re: nexus 9k keep going to loader

Post by darko » Wed May 01, 2019 1:52 pm

This is what I get when I power off a Nexus that I have used, and reboot it:

/ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/EndEntire
/ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(1,800,8000,3ff9057e-e931-40a4-4584-699cecf01024)/EndEntire
/ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(2,8800,5147a,2e0a36f7-721d-4179-309f-e94b9e859790)/EndEntire
/ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(3,5a000,a28f4,22a3a5ea-48a0-4521-f589-145002c2a32e)/EndEntire
/ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(4,fd000,355712,662fab65-a470-4a5d-70b5-0d1f79ca70ed)/EndEntire
/ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(5,452800,a28f4,5a07289e-1cb1-48b7-a687-d24fe98513b4)/EndEntire
/ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(6,4f5800,a28f4,3391772f-460b-4a4b-5f8d-d122b01ec587)/EndEntire
/ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(7,598800,261998,1ce2ee04-a294-47cf-7280-fc25766bcb63)/EndEntire
/ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,1)/EndEntire
/ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/EndEntire
/ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(1,800,8000,3ff9057e-e931-40a4-4584-699cecf01024)/EndEntire
/ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(2,8800,5147a,2e0a36f7-721d-4179-309f-e94b9e859790)/EndEntire
/ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(3,5a000,a28f4,22a3a5ea-48a0-4521-f589-145002c2a32e)/EndEntire
/ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(4,fd000,355712,662fab65-a470-4a5d-70b5-0d1f79ca70ed)/EndEntire
/ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(5,452800,a28f4,5a07289e-1cb1-48b7-a687-d24fe98513b4)/EndEntire
/ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(6,4f5800,a28f4,3391772f-460b-4a4b-5f8d-d122b01ec587)/EndEntire
/ACPI(a0341d0,0)/PCI(0,5)/SATA(0,ffff,0)/HD(7,598800,261998,1ce2ee04-a294-47cf-7280-fc25766bcb63)/EndEntire
/ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,1)/EndEntire
Total memory is 0x9f000
Total memory is 0x800000
Sysconf checksum failed. Using default values
WARNING: No BIOS Info found
Sysconf checksum failed. Using default values
serial --speed=115200 --word=8 --stop=1 --parity=no

success
Sysconf checksum failed. Using default values
Strlen bootflash: is 10
Device bootflash: is Drive 0x80 Partition 3
ATE0Q1&D2&C1S0=1
Trying to read config file /boot/grub/menu.lst.local from (hd0,4)
Filesystem type is ext2fs, partition type 0x83
Number of devices detected by BIOS is 1
Failed. Trying to read config file from (hd0,5)
Filesystem type is ext2fs, partition type 0x83
Number of devices detected by BIOS is 1
Failed.



Loader Version 5.00.9
Entering interactive mode

loader >


why is this happening and how can it be fixed?

Ho

Uldis (UD)
Posts: 5080
Joined: Wed Mar 15, 2017 4:44 pm
Location: London
Contact:

Re: nexus 9k keep going to loader

Post by Uldis (UD) » Wed May 01, 2019 9:36 pm

do not use version: nxosv9k-7.0.3.I7.5 !!!! it is very buggy !!

and use wipe node if image is changed.
then follow how to use nxos on frst boot.


rest are fine

NETPRAK2012
Posts: 2
Joined: Thu May 04, 2017 7:16 am

Re: nexus 9k keep going to loader

Post by NETPRAK2012 » Sun May 05, 2019 9:50 am

Hi UD,

My first node ( nxosv9k-7.0.3.I7.6) running without any issue, but when I add 2nd node it is keep on restarting and going to loader. Please let us know is there any issue with my desktop or image or CPU issue.

My Desktop details as below.

Intel Xeon R CPU L5520 @2.27GHz.

48 GB RAM

VMware Workstation 12.0

Win 10 Professional 64 bit

Uldis (UD)
Posts: 5080
Joined: Wed Mar 15, 2017 4:44 pm
Location: London
Contact:

Re: nexus 9k keep going to loader

Post by Uldis (UD) » Sun May 05, 2019 11:39 am

Your CPU does not hold another node may dear.
Your CPU has only 4 physical cores..

https://ark.intel.com/content/www/us/en ... l-qpi.html

No wonder, it cannot hold second one..
Did you read what is recommended CPU for NX9Kv image, Intel 26XXv3 !!!! Yours is 3 steps down..Sorry.
RAM is not player here.

Priorities for running images in EVE are:

1. Best CPU, as more cores you have, as better, as newer version CPU you have, as better. EPT feature is a must
2. Fast HDD, like SSD or SHDD (SHDD is similar as SSD but cheaper. It is hybrid hdd: sata+ssd)
3. and only then is RAM
your RAM is useless, if your CPU will not hold the nodeCPU requirements !


Uldis

Post Reply