NetVanta 1531P flash error

[Anonymous]

Hi folks,

We have a Netvanta 1531P which is refusing to boot up:

Bootloader...

Starting logging: OK

Starting mdev...

Initializing random number generator... done.

Starting network...

Mounting sysconfig...

Mounting NONVOL...

UBIFS error (pid 445): ubifs_recover_log_leb: unrecoverable log corruption in LEB 5

mount: mounting ubi1:flash on /flash failed: Structure needs cleaning

loading modules...

DMA pool size: 8388608

Discovering devices...

AXI unit 0: Dev 0x8343, Rev 0x01, Chip BCM53343_A0, Driver BCM56150_A0

SOC unit 0 attached to PCI device BCM53343_A0

...done

Initializing unit 0...

Initializing ports...

LED: Loading 256 bytes into LED program memory

Heap size: 182829056

Initializing Driver factory -------------------------------------

dblk_area = 0xB6428000, phys_dblk_offset = 0x54028000

shm_size = 0x00400000

dblk_area = 0xB6428000

mblk_area = 0xB6618950

phys_dblk_offset = 0x54028000

AOS Init:

Switch (1700571F1)

Executing bootstrap...

ram: 259899392 bytes of RAM detected.

Serial Number: xxxxx

Bootstrap

  Version: R11.2.0

  Checksum: UNKNOWN

  Build Date: Tue Jun  3 15:51:48 CDT 2014

vfs: NONVOL: 0 total, 0 used.

vlan1: initializing...

msg from adtran_bcmsdk process:client sockets connected.

Attaching unit 0 to BCMX...success!

Register rx handler - BCM

Successful Packet RX registration

Switch hardware initialized!

vlan1: MAC address is 00:19:92:11:11:11

bootstrap: Checking boot configuration...

bootstrap: Boot configuration not found.

bootstrap: Upload a new image using the 'copy' command

           or specify the correct primary/backup images using the

           'boot system flash <filename> <backup_filename>' command.

bootstrap: Error in boot configuration!!!  Checking backup boot configuration.

bootstrap: Boot configuration not found.

bootstrap: Invalid boot configuration, entering bootstrap mode...

cli: starting command line interface...

cli: starting user interface

Press '?' for help.

bootstrap#dir

0 bytes used*, 0 available**, 0 total

NOTICE: On-the-fly file compression is in use on this file system.

*  Bytes used on disk (after file compression).

** Estimated bytes available. Actual may be greater due to file compression.

I did execute an erase file-system and rebooted, but still the same, I only have a 0 size filesystem.

Any idea how to proceed with this?

Do these units have soldered-on flash storage, or maybe standard CF cards?

Thanks and regards,

Tamas

[jayh]

You'll need to install the image via TFTP or XMODEM. TFTP is faster and more available on most operating systems. You'll need to download the latest software to your PC first. See this document starting on page 26. Upgrading Firmware in AOS

It's possible that the flash is defective (yes, it's soldered) but most likely the firmware just got corrupted and re-flashing will fix the issue. If you have enough flash memory to do so, load a second firmware image onto the flash, like one revision back, and save it as secondary. Then if there's an issue booting from the first image the unit will boot from the backup.

[Anonymous]

Thanks for the quick reply jayh!

No joy unfortunately:

bootstrap#dir

0 bytes used*, 0 available**, 0 total

NOTICE: On-the-fly file compression is in use on this file system.

*  Bytes used on disk (after file compression).

** Estimated bytes available. Actual may be greater due to file compression.

bootstrap#

bootstrap#copy tftp flash

Not enough space on flash to perform TFTP upload.

bootstrap#

bootstrap#erase file-system

This will erase all files in the file-system. Proceed? [y or n]y

File system erased.

bootstrap#dir

0 bytes used*, 0 available**, 0 total

NOTICE: On-the-fly file compression is in use on this file system.

*  Bytes used on disk (after file compression).

** Estimated bytes available. Actual may be greater due to file compression.

bootstrap#

bootstrap#copy tftp flash

Not enough space on flash to perform TFTP upload.

[Anonymous · Accepted solution]

In the meantime discovered a similar issue on another 1531P, serial number very close to the above one.

This one has some filesystem corruption and refuses to boot, tried multiple images, and also refuses to erase the filesystem:

bootstrap#copy tftp flash

Address of remote host?192.168.100.100

Source filename?NV1531A-R13-6-0.biz

Destination filename? [NV1531A-R13-6-0.biz]

Initiating TFTP transfer...

Received 20668616 bytes.

Transfer complete.

bootstrap#dir

        1175850 exception-report-19691231200051.tgz

        1180541 exception-report-19691231200056.tgz

        1181220 exception-report-19691231200115.tgz

        1195322 exception-report-19691231210016.tgz

       20670632 NV1531A-R13-5-3.biz

       20668616 NV1531A-R13-6-0.biz

46346240 bytes used*, 42434560 available**, 88780800 total

NOTICE: On-the-fly file compression is in use on this file system.

*  Bytes used on disk (after file compression).

** Estimated bytes available. Actual may be greater due to file compression.

bootstrap#boot NV1531A-R13-6-0.biz

bootstrap: Booting 'NONVOL:/NV1531A-R13-6-0.biz'

Verifying:....................... done.

Extracting: watchdog watchdog0: watchdog did not stop!

blockingCallBinary:1182: receiveTlv returned error.

connect: Connection refused

blockingCallBinary:1088: m_socketFd(-1) is not a valid File descriptor.

connect: Connection refused

blockingCallBinary:1088: m_socketFd(-1) is not a valid File descriptor.

connect: Connection refused

blockingCallBinary:1088: m_socketFd(-1) is not a valid File descriptor.

connect: Connection refused

blockingCallBinary:1088: m_socketFd(-1) is not a valid File descriptor.

connect: Connection refused

blockingCallBinary:1088: m_socketFd(-1) is not a valid File descriptor.

connect: Connection refused

blockingCallBinary:1088: m_socketFd(-1) is not a valid File descriptor.

connect: Connection refused

blockingCallBinary:1088: m_socketFd(-1) is not a valid File descriptor.

connect: Connection refused

blockingCallBinary:1088: m_socketFd(-1) is not a valid File descriptor.

connect: Connection refused

blockingCallBinary:1088: m_socketFd(-1) is not a valid File descriptor.

connect: Connection refused

blockingCallBinary:1088: m_socketFd(-1) is not a valid File descriptor.

connect: Connection refused

blockingCallBinary:1088: m_socketFd(-1) is not a valid File descriptor.

connect: Connection refused

blockingCallBinary:1088: m_socketFd(-1) is not a valid File descriptor.

connect: Connection refused

blockingCallBinary:Segmentation fault (core dumped)

1088: m_socketFd(-1) is not a valid File descriptor.

connect: Connection refused

blockingCallBinary:1088: m_socketFd(-1) is not a valid File descriptor.

connect: Connection refused

Rebooting...

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

bootstrap#

bootstrap#dir

        1175850 exception-report-19691231200051.tgz

        1180541 exception-report-19691231200056.tgz

        1181220 exception-report-19691231200115.tgz

        1195903 exception-report-19691231201533.tgz

        1195322 exception-report-19691231210016.tgz

       20670632 NV1531A-R13-5-3.biz

       20668616 NV1531A-R13-6-0.biz

47493120 bytes used*, 41287680 available**, 88780800 total

NOTICE: On-the-fly file compression is in use on this file system.

*  Bytes used on disk (after file compression).

** Estimated bytes available. Actual may be greater due to file compression.

bootstrap#

bootstrap#

bootstrap#erase file-system

This will erase all files in the file-system. Proceed? [y or n]y

File system erased.

bootstrap#dir

        1175850 exception-report-19691231200051.tgz

        1180541 exception-report-19691231200056.tgz

        1181220 exception-report-19691231200115.tgz

        1195903 exception-report-19691231201533.tgz

        1195322 exception-report-19691231210016.tgz

       20670632 NV1531A-R13-5-3.biz

       20668616 NV1531A-R13-6-0.biz

47493120 bytes used*, 41287680 available**, 88780800 total

NOTICE: On-the-fly file compression is in use on this file system.

*  Bytes used on disk (after file compression).

** Estimated bytes available. Actual may be greater due to file compression.

bootstrap#

[jpeloquin]

Ran into the same thing today. backed up config and erased config and firmware individually. erase file-system didn't appear to do anything, all files were still there when issuing a dir after erase file-system. Loaded a fresh copy of the last firmware the config was working on via xmodem. Still refuses to boot with similar behavior as above.