10-01-2002
Quote:
Originally posted by Kelam_Magnus
Try 16, I believe there is an extra one there.
Um, no there's not. We need to remember that the various versions of unix do have some differences. On his system, that "newfs -N" did not actually modify the disk, but it did produce a list of alternate superblocks for him. His first was at 32.
I do agree that having come this far I would certainly try a few more superblocks, just to explore the depth of the disaster if nothing else. But on the other hand, I would not trust a filesystem after a disaster that was so severe that two superblocks were trashed.
10 More Discussions You Might Find Interesting
1. 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
2. UNIX for Advanced & Expert Users
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)
Discussion started by: rein
5 Replies
3. Filesystems, Disks and Memory
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)
Discussion started by: wesweshahaha
0 Replies
4. HP-UX
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
5. 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
6. Solaris
/pci@if,0/pci@1,1/ide@3/dad@0,0 corrupt label wrong magic number
can u plz suggustion me (6 Replies)
Discussion started by: tirupathi
6 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. Solaris
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)
Discussion started by: Aon
4 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
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 NETBSD
tunefs
TUNEFS(8) BSD System Manager's Manual TUNEFS(8)
NAME
tunefs -- tune up an existing file system
SYNOPSIS
tunefs [-AFN] [-e maxbpg] [-g avgfilesize] [-h avgfpdir] [-l logsize] [-m minfree] [-o optimize_preference] [-q quota] special | filesys
DESCRIPTION
tunefs is designed to change the dynamic parameters of a file system which affect the layout policies.
The following options are supported by tunefs:
-A Cause the values to be updated in all the alternate superblocks instead of just the standard superblock. If this option is not used,
then use of a backup superblock by fsck(8) will lose anything changed by tunefs. -A is ignored when -N is specified.
-F Indicates that special is a file system image, rather than a device name or file system mount point. special will be accessed
'as-is'.
-N Display all the settable options (after any changes from the tuning options) but do not cause any of them to be changed.
-e maxbpg
This indicates the maximum number of blocks any single file can allocate out of a cylinder group before it is forced to begin allo-
cating blocks from another cylinder group. Typically this value is set to about one quarter of the total blocks in a cylinder group.
The intent is to prevent any single file from using up all the blocks in a single cylinder group, thus degrading access times for all
files subsequently allocated in that cylinder group. The effect of this limit is to cause big files to do long seeks more frequently
than if they were allowed to allocate all the blocks in a cylinder group before seeking elsewhere. For file systems with exclusively
large files, this parameter should be set higher.
-g avgfilesize
This specifies the expected average file size.
-h avgfpdir
This specifies the expected number of files per directory.
-l logsize
This value specifies the size of the in-filesystem journaling log file. The default journaling log file size is described in
wapbl(4). Specifying a size of zero will cause the in-filesystem journaling log file to be removed the next time the filesystem is
mounted. The size of an existing in-filesystem journaling log file can not be changed.
-m minfree
This value specifies the percentage of space held back from normal users; the minimum free space threshold. The default value is set
during creation of the filesystem, see newfs(8). This value can be set to zero, however up to a factor of three in throughput will
be lost over the performance obtained at a 5% threshold. Note that if the value is raised above the current usage level, users will
be unable to allocate files until enough files have been deleted to get under the higher threshold.
-o optimize_preference
The file system can either try to minimize the time spent allocating blocks, or it can attempt to minimize the space fragmentation on
the disk. If the value of minfree (see above) is less than 5%, then the file system should optimize for space to avoid running out
of full sized blocks. For values of minfree greater than or equal to 5%, fragmentation is unlikely to be problematical, and the file
system can be optimized for time.
optimize_preference can be specified as either space or time.
-q quota
enable or disable a quota. quota can be one of user, group, nouser or nogroup to enable or disable the specified quota type. Multi-
ple -q can be used to enable/disable all types at once.
After enabling a quota, fsck_ffs(8) has to be run to compute the correct quota values.
SEE ALSO
wapbl(4), fs(5), dumpfs(8), fsck_ffs(8), newfs(8)
M. McKusick, W. Joy, S. Leffler, and R. Fabry, "A Fast File System for UNIX", ACM Transactions on Computer Systems 2, 3, pp 181-197, August
1984, (reprinted in the BSD System Manager's Manual, SMM:5).
HISTORY
The tunefs command appeared in 4.2BSD.
BUGS
This program should work on mounted and active file systems. Because the super-block is not kept in the buffer cache, the changes will only
take effect if the program is run on unmounted file systems. To change the root file system, the system must be rebooted after the file sys-
tem is tuned.
You can tune a file system, but you can't tune a fish.
BSD
December 15, 2010 BSD