09-08-2006
Best bet is to upgrade your OS while you're at it.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
working with FreeBSD 4.5
trying to mount my floppy like i did in red hat
like $mount /dev/fd0 /mnt/floppy
but i get the answer :incorrect super block
i thought maybe it needs format: $fdformat /dev/rfd0.1440
still doesn't work and the man pages and the site of FreeBSD don't really help me :(... (2 Replies)
Discussion started by: termiEEE
2 Replies
2. UNIX for Dummies Questions & Answers
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
3. Filesystems, Disks and Memory
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
4. Solaris
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)
Discussion started by: simquest
1 Replies
5. Solaris
Greetings:
I am trying to re-install my system with the Solaris 9 CD.
I typed boot cdrom from the OBP, the system restarted and started saying Failed To Read Super Block, and then proceeds to the screen where I was initially before I decided to re-install the OS.
My system was working... (4 Replies)
Discussion started by: ogfunsho
4 Replies
6. UNIX for Dummies Questions & Answers
Greetings:
I am trying to re-install my system with the Solaris 9 CD.
I typed boot cdrom from the OBP, the system restarted and started saying Failed To Read Super Block, and then proceeds to the screen where I was initially before I decided to re-install the OS.
My system was working... (0 Replies)
Discussion started by: ogfunsho
0 Replies
7. Filesystems, Disks and Memory
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
8. UNIX for Advanced & Expert Users
Hello All,
I am working on UNIX like environment. This environment is ported from UNIX. Here when we need to build product set, we need to run some script with super user privledge (which we normal user dont have)
Is there any way (some C program or some script) through which any normal... (2 Replies)
Discussion started by: joshi123
2 Replies
9. Filesystems, Disks and Memory
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
10. Solaris
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.
Netra T2000, No Keyboard
Copyright 2008 Sun Microsystems,... (5 Replies)
Discussion started by: Buddhike G
5 Replies
LEARN ABOUT OPENSOLARIS
fsck.minix
FSCK.MINIX(8) System Administration FSCK.MINIX(8)
NAME
fsck.minix - check consistency of Minix filesystem
SYNOPSIS
fsck.minix [options] device
DESCRIPTION
fsck.minix performs a consistency check for the Linux MINIX filesystem.
The program assumes the filesystem is quiescent. fsck.minix should not be used on a mounted device unless you can be sure nobody is writ-
ing to it. Remember that the kernel can write to device when it searches for files.
The device name will usually have the following form:
/dev/hda[1-63] IDE disk 1
/dev/hdb[1-63] IDE disk 2
/dev/sda[1-15] SCSI disk 1
/dev/sdb[1-15] SCSI disk 2
If the filesystem was changed, i.e., repaired, then fsck.minix will print "FILE SYSTEM HAS CHANGED" and will sync(2) three times before
exiting. There is no need to reboot after check.
WARNING
fsck.minix should not be used on a mounted filesystem. Using fsck.minix on a mounted filesystem is very dangerous, due to the possibility
that deleted files are still in use, and can seriously damage a perfectly good filesystem! If you absolutely have to run fsck.minix on a
mounted filesystem, such as the root filesystem, make sure nothing is writing to the disk, and that no files are "zombies" waiting for
deletion.
OPTIONS
-l, --list
List all filenames.
-r, --repair
Perform interactive repairs.
-a, --auto
Perform automatic repairs. This option implies --repair and serves to answer all of the questions asked with the default. Note
that this can be extremely dangerous in the case of extensive filesystem damage.
-v, --verbose
Be verbose.
-s, --super
Output super-block information.
-m, --uncleared
Activate MINIX-like "mode not cleared" warnings.
-f, --force
Force a filesystem check even if the filesystem was marked as valid. Marking is done by the kernel when the filesystem is
unmounted.
-V, --version
Display version information and exit.
-h, --help
Display help text and exit.
DIAGNOSTICS
There are numerous diagnostic messages. The ones mentioned here are the most commonly seen in normal usage.
If the device does not exist, fsck.minix will print "unable to read super block". If the device exists, but is not a MINIX filesystem,
fsck.minix will print "bad magic number in super-block".
EXIT CODES
The exit code returned by fsck.minix is the sum of the following:
0 No errors
3 Filesystem errors corrected, system should be rebooted if filesystem was mounted
4 Filesystem errors left uncorrected
7 Combination of exit codes 3 and 4
8 Operational error
16 Usage or syntax error
AUTHORS
Linus Torvalds <torvalds@cs.helsinki.fi>
Error code values by Rik Faith <faith@cs.unc.edu>
Added support for filesystem valid flag: Dr. Wettstein <greg%wind.uucp@plains.nodak.edu>.
Check to prevent fsck of mounted filesystem added by Daniel Quinlan <quinlan@yggdrasil.com>.
Minix v2 fs support by Andreas Schwab <schwab@issan.informatik.uni-dortmund.de>, updated by Nicolai Langfeldt <janl@math.uio.no>.
Portability patch by Russell King <rmk@ecs.soton.ac.uk>.
SEE ALSO
fsck(8), fsck.ext2(8), mkfs(8), mkfs.ext2(8), mkfs.minix(8), reboot(8)
AVAILABILITY
The fsck.minix command is part of the util-linux package and is available from Linux Kernel Archive <https://www.kernel.org/pub/linux/utils
/util-linux/>.
util-linux June 2015 FSCK.MINIX(8)