Alcatel Unleashed

Posted: **08 Jul 2014 17:02**

I got an OmniSwitch 6855 that had newfs run on it, so I have been attempting to do a recovery via console. I went this route because the USB recovery option didn't work because I don't have a compatible drive.

I've successfully uploaded all my .img and .lsm files to the working directory. I tried booting from the working directory and still get this error:[/b]

Attempting to load from the WORKING directory...
Loading kernel from '/flash/working/K2Ios.img'...
Cannot find component(kernel.lnk) in package(/flash/working/K2Ios.img)!
Unable to load kernel image from file '/flash/working/K2Ios.img'.
Unable to boot from the WORKING software release.
Attempting to boot from the CERTIFIED software release.
Attempting to load from the CERTIFIED directory...
Loading kernel from '/flash/certified/K2Ios.img'...
Cannot find component(alcatelNetworking_kernel.lnk) in package(/flash/certified/
K2Ios.img)!
Cannot find component(kernel.lnk) in package(/flash/certified/K2Ios.img)!
Unable to load kernel image from file '/flash/certified/K2Ios.img'.
Unable to boot from the CERTIFIED software release.
[Miniboot]->USB Disaster Recovery Activated
0xedde250 (tBulkClnt): Bulk Device Not Supported!
sysUsbDisasterRecoveryTask: ERROR: /uflash not found

[Miniboot]->

Here is my working directory:

drw 4096 Jul 8 14:14 ./
drw 4096 Jul 8 14:30 ../
-rw 666 Jul 8 12:02 software3.lsm
-rw 3437 Jul 8 12:02 Kencrypt.img
-rw 624012 Jul 8 12:32 Ksecu.img
-rw 3573 Jul 8 12:48 K2Idiag.img
-rw 4488 Jul 8 12:53 K2Ios.img
-rw 3913 Jul 8 12:57 Kadvrout.img
-rw 6710 Jul 8 13:03 Kbase.img
-rw 5127 Jul 8 13:38 Keni.img

I don't think I missed any steps on the guide for how to do a recovery via console... can anyone offer any suggestions on what I can try next?

Posted: **09 Jul 2014 06:00**

Not sure whether the file sizes are correct, but Ksecu should not be the largest image.

I would try to test a couple of (older) USB drives on another switch.
With fat32 formated sticks with size between 256MB and 2Gb (giveaways..?) you should find one where
"usb enable" gives a successful output.
Also it is a way faster recovery than x/zmodem

Posted: **09 Jul 2014 16:47**

Thanks for bringing the file sizes to my attention... if those numbers are in bytes like the manual suggests, then I'm losing a huge chunk of the image files during the zmodem transfer process.

I'll try experimenting with a few different settings on the zmodem client for now because no one around here has any external storage smaller than 8gb, and creating a partition smaller than 2gb on several different large USB sticks didn't cut it. Maybe I can find a tiny old flash drive at the Goodwill computer store...

Posted: **16 Jul 2014 16:53**

I ended up finding a compatible USB stick so I performed the recovery that way. Unfortunately I never came to understand why the zmodem process didn't work for me.

Posted: **30 Oct 2014 10:36**

We are searching for a compatible usb-stick. Can you send me the name of your USB-Stick?

thanks a lot!

Posted: **31 Oct 2014 03:17**

I work successfull with transcend - but also a lot of other sticks works fine. Try any stick at an working Switch:
> usb enable
> ls /uflash
did you see the filesystem. Than all is fine.
regards
Silvio

Posted: **13 Nov 2014 16:11**

Thanks for your reply.

I'll try some transcend...do. you have a specifc Type of a model?

Posted: **19 Nov 2014 05:16**

just use different FAT16/FAT32 formated sticks on a working/lab Switch.
I had a 50% chance on Sticks which are below 2GB size (try some old marketing giveaways)

"usb enable"
should give you some output.

Code: Select all

Labswitch > usb enable 
Labswitch >  /uflash Bulk device is created
Node ID 0x2
  LUN #0
    Vendor Info            : G & T
    Product ID             : USB Flash Drive
    Product Revision       : 5.00
    Number of Blocks       : 2009088
    Bytes per Block        : 512
    Total Capacity         : 1028653056


WED NOV 19 11:14:59 : SYSTEM (75) alert message:
+++ USB Bulk Device mounted at 12 Mbps.

Labswitch > ls /uflash

Listing Directory /uflash:

drw     16384 Nov 26  2013 6850/
-rw         0 Oct 15  2012 aossignature 
drw     16384 Jun 13 14:58 ISSU/
-rw 211389068 Aug 21 18:46 Uos.img 
drw     16384 Oct 15  2012 6400/
drw     16384 Oct 15  2012 6250/
drw     16384 Oct 15  2012 6450/
drw     16384 Oct 15  2012 6900/
-rw    338672 Jun 12  2013 KFfpga.upgrade_kit 
-rw   1466107 Jun 12  2013 kfminiboot.bs 
-rw    539720 Jun 12  2013 KFU-BOOT.BIN

Alcatel Unleashed

AOS still fails to boot after recovery via console cable

AOS still fails to boot after recovery via console cable

Re: AOS still fails to boot after recovery via console cable

Re: AOS still fails to boot after recovery via console cable

Re: AOS still fails to boot after recovery via console cable

Re: AOS still fails to boot after recovery via console cable

Re: AOS still fails to boot after recovery via console cable

Re: AOS still fails to boot after recovery via console cable

Re: AOS still fails to boot after recovery via console cable