10-01-2002
So Many Versions
Thank you for the replies. FreeBSD version of fsck is a bit diffrent than that of Linux of other *nxs.
I have found a site that says try the...
# fsck -F ufs -o /dev/ad0s1e
option but FreeBSD does not use the switches -F or -o all i get is
fsck: illegal option -- F
fsck: ? option?
I will try and use all the alt super blocks option. That might do some good. Also I read last night that i might beable to extract the data of the disk buy using..
# dd if=/dev/ad0s1e of=test2 bs=2k
Has anyone used this with FreeBSD and does it work? I do not know the right use of dd.
I also found a place that said to use this to fix the disk...
# newfs -o b=32 /dev/ad0s1e
But with that I get this...
newfs: ime: unknown optimization preference: use `space' or `time'.
So I am still at a loss. Thank you.
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 DEBIAN
growfs.ufs
GROWFS(8) BSD System Manager's Manual GROWFS(8)
NAME
growfs -- grow size of an existing ufs file system
SYNOPSIS
growfs [-Ny] [-s size] special
DESCRIPTION
The growfs utility extends the newfs(8) program. Before starting growfs the disk must be labeled to a bigger size using bsdlabel(8). If you
wish to grow a file system beyond the boundary of the slice it resides in, you must re-size the slice using fdisk(8) before running growfs.
If you are using volumes you must enlarge them by using vinum(8). The growfs utility extends the size of the file system on the specified
special file. Currently growfs can only enlarge unmounted file systems. Do not try enlarging a mounted file system, your system may panic
and you will not be able to use the file system any longer. Most of the newfs(8) options cannot be changed by growfs. In fact, you can only
increase the size of the file system. Use tunefs(8) for other changes.
The following options are available:
-N ``Test mode''. Causes the new file system parameters to be printed out without actually enlarging the file system.
-y ``Expert mode''. Usually growfs will ask you if you took a backup of your data before and will do some tests whether special is cur-
rently mounted or whether there are any active snapshots on the file system specified. This will be suppressed. So use this option
with great care!
-s size
Determines the size of the file system after enlarging in sectors. This value defaults to the size of the raw partition specified in
special (in other words, growfs will enlarge the file system to the size of the entire partition).
EXAMPLES
growfs -s 4194304 /dev/vinum/testvol
will enlarge /dev/vinum/testvol up to 2GB if there is enough space in /dev/vinum/testvol.
SEE ALSO
bsdlabel(8), dumpfs(8), fdisk(8), ffsinfo(8), fsck(8), newfs(8), tunefs(8), vinum(8)
HISTORY
The growfs utility first appeared in FreeBSD 4.4.
AUTHORS
Christoph Herrmann <chm@FreeBSD.org>
Thomas-Henning von Kamptz <tomsoft@FreeBSD.org>
The GROWFS team <growfs@Tomsoft.COM>
BUGS
The growfs utility works starting with FreeBSD 3.x. There may be cases on FreeBSD 3.x only, when growfs does not recognize properly whether
or not the file system is mounted and exits with an error message. Then please use growfs -y if you are sure that the file system is not
mounted. It is also recommended to always use fsck(8) after enlarging (just to be on the safe side).
For enlarging beyond certain limits, it is essential to have some free blocks available in the first cylinder group. If that space is not
available in the first cylinder group, a critical data structure has to be relocated into one of the new available cylinder groups. On
FreeBSD 3.x this will cause problems with fsck(8) afterwards. So fsck(8) needs to be patched if you want to use growfs for FreeBSD 3.x.
This patch is already integrated in FreeBSD starting with FreeBSD 4.4. To avoid an unexpected relocation of that structure it is possible to
use ffsinfo -g 0 -l 4 on the first cylinder group to verify that nbfree in the CYLINDER SUMMARY (internal cs) of the CYLINDER GROUP cgr0 has
enough blocks. As a rule of thumb for default file system parameters one block is needed for every 2 GB of total file system size.
Normally growfs writes this critical structure to disk and reads it again later for doing more updates. This read operation will provide
unexpected data when using -N. Therefore, this part cannot really be simulated and will be skipped in test mode.
BSD
September 8, 2000 BSD