Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Bad magic number in super-block

We have installed CS-MARS-100-K9 and on console we receive message:

Checking root filesystem

Fsck.ext3: Bad magic number in super-block while trying to open /dev/sda3

/dev/sda3:

The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains a ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:

      e2fsck –b 8193 <device>

Usage : checkdisk model

Fsck.ext3: Bad magic number in super-block /dev/sda3:

The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains a ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:

      e2fsck –b 8193 <device>

while trying to open /dev/sda3

*** An error occurred during the file system check.

*** Dropping you to a shell; the system will reboot

*** when you leave the shell

Give root password for maintenance

(or type Control-D to continue):

Do you have any ideas what to do?

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: Bad magic number in super-block

You can issue ctrl-d as indicated to continue on.  That may allo fsck to run and correct any issues.  If it does not, the next option is to re-image the CS-MARS and restore your data/configuration from archive.  If re-image does not correct the issue, you will need to open a service request with TAC so replacement can be verified.


Scott

2 REPLIES
Cisco Employee

Re: Bad magic number in super-block

You can issue ctrl-d as indicated to continue on.  That may allo fsck to run and correct any issues.  If it does not, the next option is to re-image the CS-MARS and restore your data/configuration from archive.  If re-image does not correct the issue, you will need to open a service request with TAC so replacement can be verified.


Scott

New Member

Re: Bad magic number in super-block

Thank you, Scott.

Ctrl-d not works in this case and Mars is always restarts.

We will re-image MARS appliance and we will keep you informed.

Best regards.

1322
Views
5
Helpful
2
Replies