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:
Next I get the superblocks with mkfs -n /dev/sdb
It outputs 18 blocks, tried them all with fsck -b and all returned this error:
Now I believe the HD has a ext4 fs, I couldn't find any info from the disk it self, but read it from the Synology website.
The OS I'm using is CentOS 5.7 and Ubuntu server 10.04. I also have Windows 7 & XP and Mac 10.6.8 to use as well.
I noticed that CentOS fsck goes up to fsck.ext3 and Ubuntu goes up to fsck.ext4, but both produced the same result.
Well, I'm at a loss here... Any help will be greatly appreciated.
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)
Hi,
when installing a piece of third part software I get the error "Bad magic number" at one point when it tries to use libraries from the bea tuxedo server. Am I correct that this means that the software is expecting 32bit while I'm on 64bit? Is there a way around it or can it only be solved... (5 Replies)
Dear All,
i have a SCSI hard disk drive i'm installing on it solaris 5 and the workstation is sun sparc, i made an image of this H.D using Norton Ghost 6, so i took off the SCSI H.D from the sun workstation and put it on a Compaq server then i booted the server from the Norton Ghost floppy disk... (0 Replies)
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)
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)
I want mount a disk. I have this error. I'm trying to correct with the superblock but i have the same error. Look my procedure.
bash-2.03# fsck -F ufs /dev/rdsk/c0t1d0s0
Alternate super block location: 9423392.
** /dev/rdsk/c0t1d0s0
BAD SUPER BLOCK: MAGIC NUMBER WRONG
USE AN ALTERNATE... (1 Reply)
Hello All,
(RHEL4)
Few weeks ago I had posted a message in this forum about the problem I had when I replaced my two scsi disks and tried rebuild raid1 array.
I somehow managed to up the system with working raid1 array.
But the main problem persisted..
i.e when I reboot the system, mounting... (0 Replies)
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)
I'll keep it fairly straight forward. I work with a Solaris server and magically today it decided to take a dump on me. At first it give a long list of files that couldn't be acessed before terminating the boot process and returning to the 'ok' prompt. Booting in single-user mode allowed me to run... (4 Replies)
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
LEARN ABOUT DEBIAN
fsck.ocfs2
fsck.ocfs2(8) OCFS2 Manual Pages fsck.ocfs2(8)NAME
fsck.ocfs2 - Check an OCFS2 file system.
SYNOPSIS
fsck.ocfs2 [ -pafFGnuvVy ] [ -b superblock block ] [ -B block size ] device
DESCRIPTION
fsck.ocfs2 is used to check an OCFS2 file system.
device is the file where the file system is stored (e.g. /dev/sda1). It will almost always be a device file but a regular file will work
as well.
OPTIONS -a This option does the same thing as the -p option. It is provided for backwards compatibility only: it is suggested that people use
the -p option whenever possible.
-b superblock block
Normally, fsck.ocfs2 will read the superblock from the first block of the device. This option specifies an alternate block that the
superblock should be read from. (Use -r instead of this option.)
-B blocksize
The block size, specified in bytes, can range from 512 to 4096. A value of 0, the default, is used to indicate that the blocksize
should be automatically detected.
-D Optimize directories in filesystem. This option causes fsck.ocfs2 to coalesce the directory entries in order to improve the filesys-
tem performance.
-f Force checking even if the file system is clean.
-F By default fsck.ocfs2 will check with the cluster services to ensure that the volume is not in-use (mounted) on any node in the
cluster before proceeding. -F skips this check and should only be used when it can be guaranteed that the volume is not mounted on
any node in the cluster. WARNING: If the cluster check is disabled and the volume is mounted on one or more nodes, file system cor-
ruption is very likely. If unsure, do not use this option.
-G Usually fsck.ocfs2 will silently assume inodes whose generation number does not match the generation number of the super block are
unused inodes. This option causes fsck.ocfs2 to ask the user if these inodes should in fact be marked unused.
-n Give the 'no' answer to all questions that fsck will ask. This guarantees that the file system will not be modified and the device
will be opened read-only. The output of fsck.ocfs2 with this option can be redirected to produce a record of a file system's
faults.
-p Automatically repair ("preen") the file system. This option will cause fsck.ocfs2 to automatically fix any problem that can be
safely corrected without human intervention. If there are problems that require intervention, the descriptions will be printed and
fsck.ocfs2 will exit with the value 4 logically or'd into the exit code. (See the EXIT CODE section.) This option is normally used
by the system's boot scripts.
-r backup-number
mkfs.ocfs2 makes upto 6 backup copies of the superblock at offsets 1G, 4G, 16G, 64G, 256G and 1T depending on the size of the vol-
ume. Use this option to specify the backup, 1 thru 6, to use to recover the superblock.
-y Give the 'yes' answer to all questions that fsck will ask. This will repair all faults that fsck.ocfs2 finds but will not give the
operator a chance to intervene if fsck.ocfs2 decides that it wants to drastically repair the file system.
-v This option causes fsck.ocfs2 to produce a very large amount of debugging output.
-V Print version information and exit.
EXIT CODE
The exit code returned by fsck.ocfs2 is the sum of the following conditions:
0 - No errors
1 - File system errors corrected
2 - File system errors corrected, system should
be rebooted
4 - File system errors left uncorrected
8 - Operational error
16 - Usage or syntax error
32 - fsck.ocfs2 canceled by user request
128 - Shared library error
SEE ALSO mkfs.ocfs2(8)debugfs.ocfs2(8)tunefs.ocfs2(8)mounted.ocfs2(8)ocfs2console(8)o2cb(7)AUTHORS
Oracle Corporation. This man page entry derives some text, especially the exit code summary, from e2fsck(8) by Theodore Y. Ts'o
<tytso@mit.edu>.
COPYRIGHT
Copyright (C) 2004, 2010 Oracle. All rights reserved.
Version 1.6.4 September 2010 fsck.ocfs2(8)