Data Center (VDX)

  • 1.  VDX6740 Booting Problem

    Posted 08-09-2018 11:19
    I have a BR-VDX6740T and while it is booting gives the error below . What could e the source of problem?

    Thank you

    INIT: version 2.78 booting



    e2fsck 1.41.12 (17-May-2010)

    /dev/sda1: clean, 15806/122160 files, 183016/488281 blocks

    e2fsck 1.41.12 (17-May-2010)

    /dev/sda2: recovering journal



    /dev/sda2: clean, 6976/122160 files, 124698/488192 blocks



    Firmware Integrity Check is default off

    Bypassing firmware validation.

    mount: sysfs already mounted or /sys busy

    mount: according to mtab, none is already mounted on /sys

    mknod: /dev/fsl-hv: File exists

    Hostname is VDX-10

    INIT: Entering runlevel: 3

    FIPS-mode test application



    1. Non-Approved cryptographic operation test...

    a. Excluded algorithm (MD5)...successful

    b. Included algorithm (D-H)...successful

    2. Automatic power-up self test...successful

    3. AES-128,192,256 CBC encryption/decryption...successful

    4. RSA key generation and encryption/decryption...successful

    4.1. RSA 2048 with 'SHA256' testing...successful

    5. TDES-CBC encryption/decryption...successful

    6a. SHA-1 hash...successful

    6b. SHA-256 hash...successful

    6c. SHA-512 hash...successful

    6d. HMAC-SHA-1 hash...successful

    6e. HMAC-SHA-224 hash...successful

    6f. HMAC-SHA-256 hash...successful

    6g. HMAC-SHA-384 hash...successful

    6h. HMAC-SHA-512 hash...successful

    7. Non-Approved cryptographic operation test...

    a. Excluded algorithm (MD5)...Not executed

    b. Included algorithm (D-H)...successful as expected

    8. Zero-ization...Successful

    9. TLS KDF...successful

    10. SSH KDF...successful



    All tests completed with 0 errors

    Waiting to starting configuration management service

    Starting configuration management service

    [wmd_init]: chunk_size = 0xa00000

    [wmd_init]: Checksum does not match. current_cksum = 0x16c0388f stored_cksum = 0x8fd5a6c1

    [wmd_init]: FPGA version = 0x70007445

    [wmd_init]: reset_reason = 0x1

    [wmd_init]: updated reset_reason = 0x0



    Reset reason = 0x1

    wmem: b0004000:247439360

    tbuf: 8ff00000:536854528

    Found 1(threshold 5) abnormal reboots within 3000 seconds window(threshold)

    KernelSpace rastrace_register

    SWBD module launch ... Thu Aug 9 17:19:56 EEST 2018

    Castor: PCIe Err handler init plat_pci_init[636]

    bhpc_irq_init: Using default device map. Size 10



    pcie_event_isr: ###### virq 174 core 1 MCSR 0x0 MSR 0x10021002 count 1

    plat_pcie_error:Last addresses 0x0 0x0 0x0 0x0

    0x0 0x0 0x0 0x0

    0x0 0x0

    CPLD INIT DONE

    PCIe Event [unknown] slot 0 Source Bus 0 Dev 0 MM Parent Bus 0 Dev 0 Events: 1

    AQ1402: Loaded Platform 137

    MDIO Driver: Name [Freescale P4080DS MDIO Bus], Address [8acaa220]

    GPIO CCSR phys addr = 0xffe130000, virt addr = 0xd830a000

    cbr_rev_init: pci config word 0xc0220008 for Castors

    cbr_rev_init: prs_reg[0].ctrl=0x00000102

    cbr_rev_init: chip_rev detected=2

    Cobra rev B found

    Found Castor-T Type board Blade ID 145

    Info: panic dump has been initialized!

    Creating L3-L2 fifo Thu Aug 9 17:20:07 EEST 2018 ...

    Starting HASM ... Thu Aug 9 17:20:07 EEST 2018

    Exisitng reboot reason fsize = 5 rb=





    usb 1-1: device descriptor read/64, error -110

    usb 1-1: device descriptor read/64, error -110



    usb 1-1: device descriptor read/64, error -110

    usb 1-1: device descriptor read/64, error -110

    usb 1-1: device descriptor read/8, error -110

    usb 1-1: device descriptor read/8, error -110

    usb 1-1: device descriptor read/8, error -110

    usb 1-1: device descriptor read/8, error -110

    end_request: I/O error, dev sda, sector 65609

    EXT4-fs error (device sda1): ext4_find_entry: reading directory #7044 offset 0

    Aborting journal on device sda1-8.

    EXT4-fs (sda1): delayed block allocation failed for inode 7022 at logical offset 0 with max blocks 1 with error -30

    This should not happen!! Data will be lost

    EXT4-fs error (device sda1) in ext4_da_writepages: Journal has aborted

    EXT4-fs (sda1): previous I/O error to superblock detected

    EXT4-fs error (device sda1) in ext4_new_inode: Journal has aborted

    EXT4-fs error (device sda1) in ext4_reserve_inode_write: Journal has aborted

    EXT4-fs error (device sda1) in ext4_reserve_inode_write: Journal has aborted

    /etc/rc.d/rc3.d/S99sshd: /usr/sbin/sshd: Input/output error

    EXT4-fs error (device sda1) in ext4_da_write_begin: IO failure

    EXT4-fs error (device sda1): ext4_journal_start_sb: Detected aborted journal

    EXT4-fs (sda1): Remounting filesystem read-only

    EXT4-fs (sda1): ext4_da_writepages: jbd2_start: 1024 pages, ino 7022; err -30

    INIT: cannot execute "/sbin/getty"

    EXT4-fs (sda1): I/O error while writing superblock

    INIT: cannot execute "/sbin/getty"

    JBD2: I/O error detected when updating journal superblock for sda1-8.

    journal commit I/O error

    [store_cksum]: /var/wmd_cksum does not exists.

    Unable to handle kernel paging request for data at address 0xfffffff2

    Faulting instruction address: 0xc1502630

    Oops taken on: 2018-08-09 at 14:22:06

    Oops: Kernel access of bad area, sig: 11 [#1]

    PREEMPT SMP NR_CPUS=4 LTT NESTING LEVEL : 0

    SILKWORM PB HV

    NIP: c1502630 LR: c15026f8 CTR: 40577514

    REGS: 8520fc70 TRAP: 0300 Tainted: P (2.6.34.6)

    MSR: 10029002


  • 2.  RE: VDX6740 Booting Problem

    Posted 08-09-2018 12:02
    "Unable to handle kernel paging request for data at address 0xfffffff2Faulting instruction address: 0xc1502630

    Oops taken on: 2018-08-09 at 14:22:06

    Oops: Kernel access of bad area, sig: 11 [#1]"

    That could be hardware failure, we need to check core_files to be sure.

    Does it happen only once?

    it is better to open a case to TAC team



  • 3.  RE: VDX6740 Booting Problem

    Posted 08-09-2018 12:41
    what version you are running on the 6740



  • 4.  RE: VDX6740 Booting Problem

    Posted 08-10-2018 07:00
    please change the boot partition to SDA1