nexus booting error
Moderator: mike
-
- Posts: 8
- Joined: Fri Apr 28, 2017 3:31 am
Re: nexus booting error
Hello Guys,
I have the same issue after updating to the newest version of EVE. I had lab working for more than 2 weeks with 4 nexus devices running, 4 ASR's ( CSR's) 4 ASA's and multiple switches. Everything is working fine but nexus devices are not bootking up anymore. They are stuck in boot.
Boot Failed. EFI Floppy
Boot Failed. EFI Floppy 1
Boot Failed. EFI Hard Drive
Boot Failed. EFI Hard Drive 1
iPXE 1.0.0+ () -- Open Source Network Boot Firmware -- http://ipxe.org
Features: HTTP DNS TFTP EFI Menu
net0: 50:02:00:01:00:00 using 82540em on PCI00:03.0 (open)
[Link:up, TX:0 TXE:0 RX:2 RXE:0]
Configuring (net0 50:02:00:01:00:00)..........
I am using this NxOS version
boot nxos bootflash:/nxos.7.0.3.I6.1.bin
Please Help
Thanks
I have the same issue after updating to the newest version of EVE. I had lab working for more than 2 weeks with 4 nexus devices running, 4 ASR's ( CSR's) 4 ASA's and multiple switches. Everything is working fine but nexus devices are not bootking up anymore. They are stuck in boot.
Boot Failed. EFI Floppy
Boot Failed. EFI Floppy 1
Boot Failed. EFI Hard Drive
Boot Failed. EFI Hard Drive 1
iPXE 1.0.0+ () -- Open Source Network Boot Firmware -- http://ipxe.org
Features: HTTP DNS TFTP EFI Menu
net0: 50:02:00:01:00:00 using 82540em on PCI00:03.0 (open)
[Link:up, TX:0 TXE:0 RX:2 RXE:0]
Configuring (net0 50:02:00:01:00:00)..........
I am using this NxOS version
boot nxos bootflash:/nxos.7.0.3.I6.1.bin
Please Help
Thanks
-
- Posts: 5084
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: nexus booting error
inside of nexus image folder, rename file from hda.qcow2 to sataa.qcow2.
/opt/unetlab/addons/qemu/nxosv9k-7.0.3.I6.1/
filename inside must be
sataa.qcow2
then wipe your node, and start...
This update works only for v70.
sata hdd is used for faster NX boot.
UD
/opt/unetlab/addons/qemu/nxosv9k-7.0.3.I6.1/
filename inside must be
sataa.qcow2
then wipe your node, and start...
This update works only for v70.
sata hdd is used for faster NX boot.
UD
-
- Posts: 10
- Joined: Mon Jul 31, 2017 5:20 pm
Re: nexus booting error
i followed that way only and 9K is started booting also, but it stuck like below and rebooting after sometime.. repeating the same.
Code: Select all
loader > dir bootflash:
2 Setting listing for bootflash:
Number of devices detected by BIOS is 2
Number of devices detected by BIOS is 2
Number of devices detected by BIOS is 2
Going to print files for device bootflash: 1
.rpmstore
nxos.7.0.3.I5.2.bin
sysmgrLcore_0x101_event_manager_log.25504.tar.gz
Number of devices detected by BIOS is 2
Number of devices detected by BIOS is 2
Number of devices detected by BIOS is 2
Number of devices detected by BIOS is 2
Number of devices detected by BIOS is 2
Number of devices detected by BIOS is 2
Number of devices detected by BIOS is 2
Number of devices detected by BIOS is 2
Number of devices detected by BIOS is 2
Clearing listing for bootflash:. Ret 0
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 ksimg=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 2
NBI header
magic: 1b031336, len: 54, location: 94400000 (bx=0, ds=9440), exec addr: 92800000 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=nxos.7.0.3.I5.2.bin card_index=21099 dummy_sprom rw root=/dev/ram0 rdbase=0x8000000 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 length: 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 = 510
x86_64/loader/linux.c:133: physical_start = 0, physical_end = a0000
x86_64/loader/linux.c:146: trying to allocate 2 pages at 9e000
Trying to allocate 1309 pages for VMLINUZ
Allocated prot_mode_mem 0xbcdb3000 real_mode_mem 0x0009e000
[Linux-EFI, setup=0x1168, size=0x51d000]
segment header
length: 14, vendor: 15 flags: 0, loadaddr: a21000, image len: 2cd18000, memory length: 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: 1440
x86_64/loader/linux.c:603: desc = {type=7,ps=0x0,vs=0x0,sz=158,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0x100000,vs=0x0,sz=1824,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0x1000000,vs=0x0,sz=518909,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0x80000000,vs=0x0,sz=245760,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0xbc020000,vs=0x0,sz=3475,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0xbd34c000,vs=0x0,sz=117,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0xbd3c4000,vs=0x0,sz=1,attr=15}
x86_64/loader/linux.c:603: desc = {type=7,ps=0x100000000,vs=0x0,sz=1822720,attr=15}
Loading [56M/717M]
Boot Failed. EFI Floppy
Boot Failed. EFI Floppy 1
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(1,800,8000,c48fa7a2-22f0-4149-d4bc-1993e4cf76c1)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(2,8800,a3332,e717d076-a237-41f2-8081-f2c4fe637289)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(3,ac000,146666,79914cb2-73d2-4fb9-1999-b15f771375a6)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(4,1f2800,6b199c,5330e85f-6426-43dd-e986-056152ac5679)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(5,8a4800,146666,aa000172-ffda-4794-9d8e-444ba967be56)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(6,9eb000,146666,6fb3e8b7-501e-4b25-f791-787af6874f46)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(7,b31800,4c8000,a9c6e5c0-20cd-4bb0-5895-154fa6daee2d)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(1,800,8000,c48fa7a2-22f0-4149-d4bc-1993e4cf76c1)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(2,8800,a3332,e717d076-a237-41f2-8081-f2c4fe637289)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(3,ac000,146666,79914cb2-73d2-4fb9-1999-b15f771375a6)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(4,1f2800,6b199c,5330e85f-6426-43dd-e986-056152ac5679)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(5,8a4800,146666,aa000172-ffda-4794-9d8e-444ba967be56)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(6,9eb000,146666,6fb3e8b7-501e-4b25-f791-787af6874f46)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(7,b31800,4c8000,a9c6e5c0-20cd-4bb0-5895-154fa6daee2d)/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(1,1)/ATAPI(0,0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(1,800,8000,c48fa7a2-22f0-4149-d4bc-1993e4cf76c1)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(2,8800,a3332,e717d076-a237-41f2-8081-f2c4fe637289)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(3,ac000,146666,79914cb2-73d2-4fb9-1999-b15f771375a6)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(4,1f2800,6b199c,5330e85f-6426-43dd-e986-056152ac5679)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(5,8a4800,146666,aa000172-ffda-4794-9d8e-444ba967be56)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(6,9eb000,146666,6fb3e8b7-501e-4b25-f791-787af6874f46)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(0,0,0)/HD(7,b31800,4c8000,a9c6e5c0-20cd-4bb0-5895-154fa6daee2d)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(1,800,8000,c48fa7a2-22f0-4149-d4bc-1993e4cf76c1)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(2,8800,a3332,e717d076-a237-41f2-8081-f2c4fe637289)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(3,ac000,146666,79914cb2-73d2-4fb9-1999-b15f771375a6)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(4,1f2800,6b199c,5330e85f-6426-43dd-e986-056152ac5679)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(5,8a4800,146666,aa000172-ffda-4794-9d8e-444ba967be56)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(6,9eb000,146666,6fb3e8b7-501e-4b25-f791-787af6874f46)/EndEntire
/ACPI(a0341d0,0)/PCI(1,1)/ATAPI(1,0,0)/HD(7,b31800,4c8000,a9c6e5c0-20cd-4bb0-5895-154fa6daee2d)/EndEntire
/ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,0)/EndEntire
/ACPI(a0341d0,0)/PCI(0,1)/ACPI(60441d0,1)/EndEntire
Total memory is 0xa0000
Total memory is 0xbee3c000
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
Strlen bootflash: is 10
Device bootflash: is Drive 0x81 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 2
Failed. Trying to read config file from (hd0,5)
Filesystem type is ext2fs, partition type 0x83
Number of devices detected by BIOS is 2
Failed.
Loader Version 5.00.9
Entering interactive mode
-
- Posts: 5084
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: nexus booting error
Such behaviour is usually when you have not given to NX ensufficient resource to run.
It simply has no power run it
NX9K myst be min x4CPU and 8G RAM for single node
It simply has no power run it
NX9K myst be min x4CPU and 8G RAM for single node
-
- Posts: 8
- Joined: Fri Apr 28, 2017 3:31 am
Re: nexus booting error
I think I pressed the the right buttonUldis (UD) wrote: ↑Fri Aug 04, 2017 7:30 aminside of nexus image folder, rename file from hda.qcow2 to sataa.qcow2.
/opt/unetlab/addons/qemu/nxosv9k-7.0.3.I6.1/
filename inside must be
sataa.qcow2
then wipe your node, and start...
This update works only for v70.
sata hdd is used for faster NX boot.
UD
Thanks you so much for your answer UD.
I did change hda to sataa and fix the permissions. I wiped the node and this is the result I have right now:
Code: Select all
UEFI Interactive Shell v2.1
EDK II
UEFI v2.60 (EDK II, 0x00010000)
Mapping table
BLK2: Alias(s):
PciRoot(0x0)/Pci(0x1,0x1)/Ata(0x0)
BLK3: Alias(s):
PciRoot(0x0)/Pci(0xA,0x0)/Sata(0x0,0xFFFF,0x0)
BLK4: Alias(s):
PciRoot(0x0)/Pci(0xA,0x0)/Sata(0x0,0xFFFF,0x0)/HD(1,GPT,C48FA7A2-22F0-4149-BCD4-1993E4CF76C1,0x800,0x8000)
BLK5: Alias(s):
PciRoot(0x0)/Pci(0xA,0x0)/Sata(0x0,0xFFFF,0x0)/HD(2,GPT,E717D076-A237-41F2-8180-F2C4FE637289,0x8800,0xA3332)
BLK6: Alias(s):
PciRoot(0x0)/Pci(0xA,0x0)/Sata(0x0,0xFFFF,0x0)/HD(3,GPT,79914CB2-73D2-4FB9-9919-B15F771375A6,0xAC000,0x146666)
BLK7: Alias(s):
PciRoot(0x0)/Pci(0xA,0x0)/Sata(0x0,0xFFFF,0x0)/HD(4,GPT,5330E85F-6426-43DD-86E9-056152AC5679,0x1F2800,0x6B199C)
BLK8: Alias(s):
PciRoot(0x0)/Pci(0xA,0x0)/Sata(0x0,0xFFFF,0x0)/HD(5,GPT,AA000172-FFDA-4794-8E9D-444BA967BE56,0x8A4800,0x146666)
BLK9: Alias(s):
PciRoot(0x0)/Pci(0xA,0x0)/Sata(0x0,0xFFFF,0x0)/HD(6,GPT,6FB3E8B7-501E-4B25-91F7-787AF6874F46,0x9EB000,0x146666)
BLK10: Alias(s):
PciRoot(0x0)/Pci(0xA,0x0)/Sata(0x0,0xFFFF,0x0)/HD(7,GPT,A9C6E5C0-20CD-4BB0-9558-154FA6DAEE2D,0xB31800,0x4C8000)
BLK0: Alias(s):
PciRoot(0x0)/Pci(0x1,0x0)/Floppy(0x0)
BLK1: Alias(s):
PciRoot(0x0)/Pci(0x1,0x0)/Floppy(0x1)
Press ESC in 1 seconds to skip startup.nsh or any other key to continue.
Shell>
What should I do to start nexus again. I have 4 CPU per 9K with 12 G ram
Thanks
-
- Posts: 5084
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: nexus booting error
Look, so many annoying screens,
get me in skype: uldisd.poisonfish
Will chat online..
if you did changes you must wipe node before start again
get me in skype: uldisd.poisonfish
Will chat online..
if you did changes you must wipe node before start again
-
- Posts: 8
- Joined: Fri Apr 28, 2017 3:31 am
Re: nexus booting error
Thank you so much for your support UD. You are awesome
Now I am back again on my lab.
I will upload that lab as soon as I will be done with it
Thanks
Now I am back again on my lab.
I will upload that lab as soon as I will be done with it
Thanks
-
- Posts: 5084
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
-
- Posts: 10
- Joined: Mon Jul 31, 2017 5:20 pm
Re: nexus booting error
thanks .... below solution is working..
""inside of nexus image folder, rename file from hda.qcow2 to sataa.qcow2.
/opt/unetlab/addons/qemu/nxosv9k-7.0.3.I6.1/
filename inside must be
sataa.qcow2
""
""inside of nexus image folder, rename file from hda.qcow2 to sataa.qcow2.
/opt/unetlab/addons/qemu/nxosv9k-7.0.3.I6.1/
filename inside must be
sataa.qcow2
""