Bad magic number in super-block

Answered Question
Jul 6th, 2010
User Badges:

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?

Correct Answer by Scott Fringer about 6 years 8 months ago

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

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
Correct Answer
Scott Fringer Tue, 07/06/2010 - 08:21
User Badges:
  • Cisco Employee,

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

vaba Tue, 07/06/2010 - 23:22
User Badges:

/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin-top:0cm; mso-para-margin-right:0cm; mso-para-margin-bottom:10.0pt; mso-para-margin-left:0cm; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;}

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.

Actions

This Discussion