cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1108
Views
5
Helpful
8
Replies

WLSE recovery, appears to be hung at booting kernel

jduffek
Level 1
Level 1

For some reason our WLSE boxes got turned into ACS servers...so now we get to recover and set them up from scratch. I was not here for the intitial setup so this is my first time messing with them.

First I am using the 2.0 disk but I plan to upgrade to 2.91(or whatever) asap.

I boot the box from the CD. It loads some jpg file and vmlinux or whatever, uncompresses something, then says it is booting the kernel. Then it just sits. I think I have had that screen up for an hour and a half so I'm pretty sure it is dead. How long should that process take?

Is there some other way I should be going about this? Is the fact that win2k is installed on the box causing funkiness?

Any help would be appreciated.

Thanks,

Josh

8 Replies 8

sstudsdahl
Level 4
Level 4

Josh,

Do you have a console connected to the serial port on the front of the WLSE apliance? I suspect the recovery process is prompting for some input here. I've included a link with the steps for reimaging the WLSE unit.

http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cwparent/cw_1105/wlse/2_0/inst_gd/ig_adm.htm#20273

If it is not sitting at a prompt, you may see some additional output that may show what is going on.

Steve

rmushtaq
Level 8
Level 8

This is because you may be connected via the video port on the WLSE. Disconnect it and use the console cable provided with the WLSE to connect using Windows Hyperterminal application.

many thanks for the replies. it was hanging...and now i can see where by going in via console...here is part of the log:

--------------- ME1110 Maintenance Image -----------------

INIT: Entering runlevel: 1

bash: no job conEXT2-fs warning: checktime reached, running e2fsck is recommended

trol in this shell

CDROM is hde

Partitioning the drive: size = 39062500.

version: Error reading from flash

/ /

version: Error reading from flash

Error: Version infomation not found in flash.

bash: no job control in this shell

CDROM is hde

Partitioning the drive: size = 39062500.

version: Error reading from flash

/ /

mknod: `flash.dat': File exists

version: Error reading from flash

Error: Version infomation not found in flash.

bash: no job control in this shell

CDROM is hde

Partitioning the drive: size = 39062500.

version: Error reading from flash

/ /

mknod: `flash.dat': File exists

version: Error reading from flash

Error: Version infomation not found in flash.

bash: no job control in this shell

CDROM is hde

Partitioning the drive: size = 39062500.

version: Error reading from flash

/ /

mknod: `flash.dat': File exists

version: Error reading from flash

Error: Version infomation not found in flash.

bash: no job control in this shell

CDROM is hde

Partitioning the drive: size = 39062500.

version: Error reading from flash

/ /

mknod: `flash.dat': File exists

version: Error reading from flash

Error: Version infomation not found in flash.

bash: no job control in this shell

CDROM is hde

Partitioning the drive: size = 39062500.

version: Error reading from flash

/ /

mknod: `flash.dat': File exists

version: Error reading from flash

Error: Version infomation not found in flash.

bash: no job control in this shell

CDROM is hde

Partitioning the drive: size = 39062500.

version: Error reading from flash

/ /

mknod: `flash.dat': File exists

version: Error reading from flash

Error: Version infomation not found in flash.

bash: no job control in this shell

CDROM is hde

Partitioning the drive: size = 39062500.

version: Error reading from flash

/ /

mknod: `flash.dat': File exists

version: Error reading from flash

Error: Version infomation not found in flash.

bash: no job control in this shell

CDROM is hde

Partitioning the drive: size = 39062500.

version: Error reading from flash

/ /

mknod: `flash.dat': File exists

version: Error reading from flash

Error: Version infomation not found in flash.

bash: no job control in this shell

CDROM is hde

Partitioning the drive: size = 39062500.

version: Error reading from flash

/ /

mknod: `flash.dat': File exists

version: Error reading from flash

Error: Version infomation not found in flash.

INIT: Id "S0" respawning too fast: disabled for 5 minutes

INIT: no more processes left in this runlevel

-------------------------------------------

then it dies. i am going to try to download the 2.9 ISOs and try with them, maybe this 2.0 is just kinda bad...not sure.

does that log give any clues to the clueful?

thanks,

jd.

If this is a 1130 model, then use the 2.0 ISO files to make the CD and use it instead. 2.0 is too old

yes 1130. i hate to be a bbreaker but, saying 2.0 is too old doesn't really work for me. i used to be in tac and i know that using the newer software is better, but it's not like CDs have a shelf life.

i am, however, in the process of buring the 2.9iso and will try that, but i am planning for the worst and thinking that the fact that the non-expired-cd is not the problem...will find out in a few minutes though.

thanks for the replies.

ok things are a little different now...here is the bootup with the 2.9 CD:

--------------- ME1110 Maintenance Image -----------------

INIT: Entering runlevel: 1

bash: no job control in this shell

CDROM is hde

Partitioning the drive: size = 39062500.

version: Error reading from flash

Error: Version infomation not found in flash.

md: stopping all md devices.

flushing ide devices: hda hde

Restarting system.

------------------

since there is nothing on the HD im basically stuck...any ideas?

The message "Error: Version iniformation not found in flash." sounds like there may be a flash drive within the system. If your WLSE unit had Windows and ACS loaded on them, is it possible that the flash drive was formatted resulting in the required info being lost?

If this is the case, the only way you might be able to overcome this would be with an RMA. (I'm not sure if this will be the case or not, but that would be my guess.)

The only other thing I can think of would be to try going back to a much older version of the recovery CD, and try it. If it works, you should just need to do a lot of software upgrades to get up to the current version.

Steve

Thanks Steve!

I was afraid of something like that. I have a case open so I will get an RMA if i have to...argh.

Thanks Again,

Josh

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Review Cisco Networking products for a $25 gift card