Fibre Channel (SAN)

Reply
New Contributor
Posts: 4
Registered: ‎05-09-2008

Failed CF in SilkWorm 210E

Dear Brocade Users.

We have got a failed FabOS CompactFlash card in a SilkWorm 210E so that the switch would not boot into FabricOS.

The CompactFlash inside is an ordinary Toshiba 256 MB CF card with two

partitions of 128 MB each, where the second partition is a mirror copy

of the first. On the failed card the mirror copy is unreadable and the

first one is corrupted. Since the switch cannot boot we cannot upgrade

to a new firmware version.

What would be the suggested course of action to regain the switch? Is the image of the firmware available?

Thank you.

Dmitri

External Moderator
Posts: 4,974
Registered: ‎02-23-2004

Re: Failed CF in SilkWorm 210E

Dmitri,

i don't think that the CF is defective.

Please make follow:

Connect the switch trugh the Serial Console -> power on -> Press ESC beetwen 3 Second ->ESC stop the Boot Procedure.

You see a this time the EPROM Boot, select here the Option "printenv" and copy the Full and Exact Output here.

Whit a little luck is the Partition lost.

TechHelp24

TechHelp24
New Contributor
Posts: 4
Registered: ‎05-09-2008

Re: Failed CF in SilkWorm 210E

Hello,

here is the output from printenv.

First here is the console log prior to the boot interface prompt which says that POST completed with success.

Here is the actual output of printenv

And here is what I get when I try to boot. The output is rather verbose. The Fabric OS kernel loads but fails to mount the root partition.

So far so good, but here is where it fails.

Thank you.

External Moderator
Posts: 4,974
Registered: ‎02-23-2004

Re: Failed CF in SilkWorm 210E

Hi Dmitri,

both Partition are lost. Please Follow EXACT! this procedure.

Repeate the procedure, Power ON, Press ESC, select here -> 3) Enter command shell. you have here more command, here is the command "setenv"

edit the File listed below EXACT as despripted here at each line:

OSBooted=MEM()0xF0000000 OSLoadOptions=quiet;quiet OSLoader=MEM()0xF0000000;MEM()0xF0800000

you must repeated each lineby the command setenv

setenv OSBooted=MEM()0xF0000000

setenv OSLoadOptions=quiet;quiet

setenv OSLoader=MEM()0xF0000000;MEM()0xF0800000

after this line are edited, save the config with the command "saveenv" and execute the command "printenv" here must you see the new config.

boot the switch manually with the command:

boot MEM()0xF0000000 ( or by the second config 0xF0800000 )

Dmitri, whe cannot see in the Partition, ( in this config you can see, that the first Partition is MEM()0xF0000000, in this case the switch boot from this partition.

It is probable, that the boot partition, is the MEM 0800000, in this case you must edit this both line viceversa as follow:

setenv OSBooted=MEM()0xF0800000

setenv OSLoader=MEM()0xF0800000;MEM()0xF0000000

same procedure you must save the config "saveenv"

This must work.

Good luck, and please inform.

TechHelp24

TechHelp24
N/A
Posts: 1
Registered: ‎05-09-2008

Re: Failed CF in SilkWorm 210E

Hello, we followed the incstructions but no luck so far. Here is the console log.

1) Start system.

2) Recover password.

3) Enter command shell.

Option? 3

Boot PROM password has not been set.

printenv

AutoLoad=yes

BadRootDev=hda1;hda2

ENET_MAC=00051E020F24

InitTest=MEM()

LoadIdentifiers=Fabric Operating System;Fabric Operating System

OSLoader=ATA()0x25970;ATA()0x629d8

OSRootPartition=hda1;hda2

SkipWatchdog=yes

setenv OSBooted=MEM()0xF0000000

setenv OSLoadOptions=quiet;quiet

setenv OSLoader=MEM()0xF0000000;MEM()0xF0800000

saveenv

printenv

AutoLoad=yes

BadRootDev=hda1;hda2

ENET_MAC=00051E020F24

InitTest=MEM()

LoadIdentifiers=Fabric Operating System;Fabric Operating System

OSBooted=MEM()0xF0000000

OSLoadOptions=quiet;quiet

OSLoader=MEM()0xF0000000;MEM()0xF0800000

OSRootPartition=hda1;hda2

SkipWatchdog=yes

boot MEM()0xF0000000

Booting "Manually selected OS" image.

MEM()0xF0000000 has an invalid magic number (0x02FF02FF)

OSLoader contains no bootable devices.

The system is coming up, please wait...

Read board ID of 0x80 from addr 0x23

Read extended model ID of 0x19 from addr 0x22

Matched board/model ID to platform index 6

Read board ID of 0x80 from addr 0x23

Read extended model ID of 0x19 from addr 0x22

Matched board/model ID to platform index 6

Checking system RAM - press any key to stop test

Checking memory address: 00100000

System RAM test using Default POST RAM Test succeeded.

Press escape within 4 seconds to enter boot interface.

Booting "Fabric Operating System" image.

MEM()0xF0000000 has an invalid magic number (0xECECECEC)

Booting "Fabric Operating System" image.

MEM()0xF0800000 has an invalid magic number (0xECECECEC)

OSLoader contains no bootable devices.

External Moderator
Posts: 4,974
Registered: ‎02-23-2004

Re: Failed CF in SilkWorm 210E

Fomin,

are you the same user as "sinysee" ?

if no, do you have save the Old value before edit the EPROM with setenv ?

To you Problem, the MEM()0xF0000000 and MEM()0xF0800000 are the Standard Value, it is a First Time i see this Loader ATA= etc.....

Please edit now trough the command "setenv" with the Old Value follow Line:

OSLoader=ATA()0x25970;ATA()0x629d8

and

OSBooted=MEM()0xF0000000 ( replace here MEM()0xF0000000 ) with one of both ATA()0.....

TechHelp24

TechHelp24
New Contributor
Posts: 4
Registered: ‎05-09-2008

Re: Failed CF in SilkWorm 210E

Hello,

me and Fomin are talking of the same switch here. OSLoader=ATA() was the settings that were on the switch when we encountered the problem. It might be important that this is not the original 210E, but an OEMed version from Hewlett-Packard.

So far we could not recover the root partition as it is badly damaged: the root directory is missing and the kernel image could not be found among the recovered files. One option that we consider is to bootstrap Fabric OS using the firmware upgrade and a fresh CF card. It would've been much easier if we had a complete FabOS image, but this does not seem to be available.

Dmitri

New Contributor
Posts: 4
Registered: ‎05-09-2008

Re: Failed CF in SilkWorm 210E

Hello,

me and Fomin are talking of the same switch here.

OSLoader=ATA() was the settings that were on the switch when we encountered the problem.

It might be important that this is not the original 210E, but an OEMed version from Hewlett-Packard.

So far we could not recover the root partition as it is badly damaged:

the root directory is missing and the kernel image could not be found

among the recovered files. One option that we consider is to bootstrap

Fabric OS using the firmware upgrade and a fresh CF card. It would've

been much easier if we had a complete FabOS image, but this does not

seem to be available.

Dmitri

PS Sorry for multiple copies of this message.

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.