problem with MARS-55

[wei jin]

HI GUYS.

    recently i found my mars can not be accessible.i got some pictures and i hope someone can help me to Solve my problem.

     thx

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

============================================================================

==============================================================================

===============================================================================

/dev/sda8 contains a file system with errors, check forced  // i guess this disk partition has been destroyed.

is there any way to recover the system?

Looking forward to your answer

[wei jin]

now i can not login to the mars by the webui&cli 

even i can't test the system with icmp

[Dustin Ralich]

now i can not login to the mars by the webui&cli  
even i can't test the system with icmp

Right, because the boot-up is failing during filesystem check (network services have not yet been reached/brought online). That is expected in this situation (and not specific to MARS).

[Dustin Ralich]

In this situation, the only supported method to correct this would be to re-image the CS-MARS appliance (perform a clean software installation), which will result in the problem partition/filesystem being recreated (and also working copies of the OS and software being copied over). This also results in the existing config/data being lost, so once complete, you would restore your config/data from NFS/SFTP Data Archives (backups) if you had configured that prior to the failure, using the pnrestore command. Example:

pnrestore -m 4 -r 1 -p :/ -t

Full Command Reference can be found here.

I have encountered a few MARS users that have reported they have been able to boot-up the appliance using a Live Linux disc and perform filesystem repairs manually. That may or may not work for you, but it is definitely not supported by Cisco/TAC (so I would not advise that).

[wei jin]

hi dustin , thanks for your reply

now i just want to know is there any handbook can guide me to perform the "re-image" ,i want to repair it by myself if i could.

so could you tell me where i can find the latest soft image for the mars-55 and how to install it to the factory mode?

"/dev/sda8 contains a file system with errors, check forced "

when i  "re-image"  the mars , the problem partition/filesystem will start to repair itself ?

that is to say i have no need to replace the harddisk?

Looking forward to your answer

[Dustin Ralich · Accepted solution]

Hi Wei.

 hi dustin , thanks for your reply

You're welcome.

now i just want to know is there any handbook can guide me to perform the "re-image"

Certainly, check the Re-Imaging a Local Controller section of the Install and Upgrade Guide.

so could you tell me where i can find the latest soft image for the mars-55

The latest version is (as of this writing) 6.1.3 and the System Recovery .ISO image file for 6.1.3 (what you would burn to a DVD-R disc and use to re-image the appliance following the steps linked above), can be downloaded here.

But, keep in mind that if you have NFS/SFTP Data Archives (backups) to restore, then you must re-image to the exact same version of software that created the latest backups (i.e. whatever version was running on the MARS prior to this failure) in order to be able to restore them.

"/dev/sda8 contains a file system with errors, check forced " when i  "re-image"  the mars , the problem partition/filesystem will start to repair itself ? that is to say i have no need to replace the harddisk?

The re-image operation will result in the appliance's partitions/filesystems being recreated (and working copies of the OS and software being copied over). Think of it as performing a fdisk, format, and clean install of an Operating System on a workstation/server. This should resolve the fsck (filesystem check) error message you've encountered. There could be an underlying hardware/media problem that caused the filesystem problem, but since no such messages are shown, the first step would be to eliminate filesystem corruption (by re-imaging), and then once complete, if the problem immediately recurred, it's possible there is a hardware problem that warrants further investigation.