Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: File System Error: BAD SUPERBLOCK AT BLOCK 16: NUMBER OF DIRECTORIES OUT OF RANGE
Operating Systems Solaris File System Error: BAD SUPERBLOCK AT BLOCK 16: NUMBER OF DIRECTORIES OUT OF RANGE Post 302943813 by Buddhike G on Wednesday 13th of May 2015 04:57:35 AM
Old 05-13-2015
File System Error: BAD SUPERBLOCK AT BLOCK 16: NUMBER OF DIRECTORIES OUT OF RANGE
Hi All,
we are having a file system error in one of our servers. The server failed to boot in usual user mode. Instead boot with single user mode and requesting to run a FSCK manually to repair the corrupted. see the below output.


Code:
Netra T2000, No Keyboard
Copyright 2008 Sun Microsystems, Inc.  All rights reserved.
OpenBoot 4.28.9, 8064 MB memory available, Serial #9dddddddae.
.
 
 
 
 
 
 
Boot device: /pci@780/pci@0/pci@9/scsi@0/disk@1,0:a  File and args:
SunOS Release 5.10 Version Generic_142900-03 64-bit
Copyright 1983-2009 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
Hostname: SVR
The / file system (/dev/md/rdsk/d0) is being checked.
 
 
WARNING - Unable to repair the / filesystem. Run fsck
manually (fsck -F ufs /dev/md/rdsk/d0).
 
 
May 12 17:21:42 svc.startd[7]: svc:/system/filesystem/usr:default: Method "/lib/svc/method/fs-usr" failed with exit status 95.
May 12 17:21:42 svc.startd[7]: system/filesystem/usr:default failed fatally: transitioned to maintenance (see 'svcs -xv' for details)
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run
 
 
Root password for system maintenance (control-d to bypass):
single-user privilege assigned to /dev/console.
Entering System Maintenance Mode
 
 
May 12 17:21:47 su: 'su root' succeeded for root on /dev/console
Sun Microsystems Inc.   SunOS 5.10      Generic January 2005
You have new mail.
Sourcing //.profile-EIS.....
root@SVR #
root@SVR #
root@SVR # fsck -F ufs /dev/md/rdsk/d0
** /dev/md/rdsk/d0
BAD SUPERBLOCK AT BLOCK 16: NUMBER OF DIRECTORIES OUT OF RANGE
 
 
LOOK FOR ALTERNATE SUPERBLOCKS WITH MKFS?
 
 
 
 
LOOK FOR ALTERNATE SUPERBLOCKS WITH NEWFS? Y
 
 
FOUND ALTERNATE SUPERBLOCK 32 WITH NEWFS
 
 
USE ALTERNATE SUPERBLOCK? y
 
 
FOUND ALTERNATE SUPERBLOCK AT 32 USING NEWFS
If filesystem was created with manually-specified geometry, using
auto-discovered superblock may result in irrecoverable damage to
filesystem and user data.
 
 
CANCEL FILESYSTEM CHECK? y
 
 
Please verify that the indicated block contains a proper
superblock for the filesystem (see fsdb(1M)).
root@SVR #



When we try to run the fsck it prompts to look for the superblocks using either MKFS or NEWFS, According to the oracle documentation, we need to select it correctly depending on the system. But we do not know from which command the file system is created. so with the warning given, we want get an advise on the best possible way to proceed for the file system repair.

Kindly advise on best possible way to proceed.


Thank You
Buddhike G
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Bad magic number in super-block

I am running mandrake 8.2 and when booting I get the message: e2fschk: Bad magic number in super-block while trying to open /dev/hda8. The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and really contains a valid an ext2 filesystem (and... (1 Reply)
Discussion started by: Jay
1 Replies

2. UNIX for Advanced & Expert Users

Bad Number Error

What is wrong with my syntax, I am getting bad number error. The following lines of code get the value from INI file but the variable is a combination of multiple variables. When compiling all together, I get a bad number error or changing the '((' with '{{' gets me bad substitution error. The... (2 Replies)
Discussion started by: moan71
2 Replies

3. HP-UX

BAD SUPER BLOCK - Run fsck with alternate super block number

Error received when I tried to restore a blank disk with an 'auto recovery' DDS tape via HP-UX recovery system 2.0 onto a 1Gb SCSI. I assumed it would do the setup, wrong. Could someone tell me the procedure to initial disk for recovering files using cpio. The system is a HP-UX 9.04 version on a... (1 Reply)
Discussion started by: admin wanabee
1 Replies

4. Shell Programming and Scripting

Error Message - ./dsp_svrconn.sh[41]: MBHD1: bad number

Hi Experts, I have a shell script in which I have the following if condition. if then CHLREP=`echo "$DSPLINE MCAUSER" | \ \opt\mqm\bin\runmqsc -e $QMGRNAME | \ "ALTER CHANNEL($CHANNEL) CHLTYPE(SVRCONN) MCAUSER('HAK')"` echo "$CHLREP" fi When I run this... (1 Reply)
Discussion started by: hkhan12
1 Replies

5. Filesystems, Disks and Memory

Bad Super Block: Magic Number Wrong

I had a power outage a day ago and when the power came back on my FreeBSD 4.6 webserver had problems. It said it was unable to mount /var and made me start in single user mode and said to run fsck MANUALY. So i did and this is now what i get. www# fsck /dev/ad0s1e ** /dev/ad0s1e BAD SUPER... (4 Replies)
Discussion started by: matthewbane
4 Replies

6. Filesystems, Disks and Memory

Bad super block: Magic number wrong

Whenever i run, # fsck -F ufs /dev/dsk/c0t0d0s7 The following error prompt out:- ** /dev/dsk/c0t0d0s7 BAD SUPER BLOCK: MAGIC NUMBER WRONG USE AN ALTERNATE SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; eg. fsck -o b=# where # is the alternate super block. SEE fsck_ufs(1M). ... (3 Replies)
Discussion started by: beginningDBA
3 Replies

7. Solaris

Bad File Number

System Solaris 8 When I open a CONSOLE window the following starts scrolling: "ServiceCommand: :write: Bad FIle Number" This will continue to scroll without stopping. However, you can type while it is scrolling and login into root and even conduct business within the CONSOLE window. The... (1 Reply)
Discussion started by: Kevin1166
1 Replies

8. Filesystems, Disks and Memory

Can't repair super block, bad magic number

Hello all, I have a hard drive that I can't repair. The drive is WD15EARS - Filesystem ext4 ( not 100% sure ) It's used in a Synology DS110j NAS. I try to run fsck -p /dev/sdb on the HD and I get this: Bad magic number in super-block while trying to open /dev/sdb /dev/sdb: The superblock... (4 Replies)
Discussion started by: dallasw1983
4 Replies

9. Solaris

Bad magic number error

So we have a new to us v240 server with no OS installed. It has an outdated version of OB and ALOM so before we install the OS we want to update both. We have a DVD with the latest OB patch burned on it. We do the boot cdrom command but receive the Bad Magic Number Error. Does an OS need to... (2 Replies)
Discussion started by: dunkpancakes
2 Replies

10. Red Hat

Linux bad superblock on /dev/mapper/VolGroup-lv_root

Hi Friends . my linux try to start very slowly after give it this error: mount: wrong fs type, bad option, bad superblock on /dev/mapper/VolGroup-lv_root, missing codepage or helper program, or other error in some cases useful info is found in syslog - try dmesg : tail or so Kernel panic... (3 Replies)
Discussion started by: blackjuan
3 Replies

LEARN ABOUT ULTRIX

systemd-fsck

SYSTEMD-FSCK@.SERVICE(8)				       systemd-fsck@.service					  SYSTEMD-FSCK@.SERVICE(8)

NAME

       systemd-fsck@.service, systemd-fsck-root.service, systemd-fsck - File system checker logic

SYNOPSIS

       systemd-fsck@.service

       systemd-fsck-root.service

       /lib/systemd/systemd-fsck

DESCRIPTION

       systemd-fsck@.service and systemd-fsck-root.service are services responsible for file system checks. They are instantiated for each device
       that is configured for file system checking.  systemd-fsck-root.service is responsible for file system checks on the root file system, but
       only if the root filesystem was not checked in the initramfs.  systemd-fsck@.service is used for all other file systems and for the root
       file system in the initramfs.

       These services are started at boot if passno in /etc/fstab for the file system is set to a value greater than zero. The file system check
       for root is performed before the other file systems. Other file systems may be checked in parallel, except when they are on the same
       rotating disk.

       systemd-fsck does not know any details about specific filesystems, and simply executes file system checkers specific to each filesystem
       type (/sbin/fsck.*). This helper will decide if the filesystem should actually be checked based on the time since last check, number of
       mounts, unclean unmount, etc.

       If a file system check fails for a service without nofail, emergency mode is activated, by isolating to emergency.target.

KERNEL COMMAND LINE

       systemd-fsck understands these kernel command line parameters:

       fsck.mode=
	   One of "auto", "force", "skip". Controls the mode of operation. The default is "auto", and ensures that file system checks are done
	   when the file system checker deems them necessary.  "force" unconditionally results in full file system checks.  "skip" skips any file
	   system checks.

       fsck.repair=
	   One of "preen", "yes", "no". Controls the mode of operation. The default is "preen", and will automatically repair problems that can be
	   safely fixed.  "yes" will answer yes to all questions by fsck and "no" will answer no to all questions.

SEE ALSO

       systemd(1), fsck(8), systemd-quotacheck.service(8), fsck.btrfs(8), fsck.cramfs(8), fsck.ext4(8), fsck.fat(8), fsck.hfsplus(8),
       fsck.minix(8), fsck.ntfs(8), fsck.xfs(8)

systemd 237														  SYSTEMD-FSCK@.SERVICE(8)
All times are GMT -4. The time now is 02:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy