08-29-2006
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 Motorola 68040, i.e. HP382 controller.
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
backup(1M) backup(1M)
NAME
backup - backup or archive file system
SYNOPSIS
[-archive]
DESCRIPTION
The command uses find(1) and cpio(1) to save a archive of all files that have been modified since the modification time of on the default
tape drive should be invoked periodically to ensure adequate file backup.
The option suppresses warning messages regarding optional access control list entries. backup(1M) does not backup optional access control
list entries in a file's access control list (see acl(5)). Normally, a warning message is printed for each file having optional access
control list entries.
The option causes backup to save all files, regardless of their modification date, and then update using touch(1).
prompts you to mount a new tape and continue if there is no more room on the current tape. Note that this prompting does not occur if you
are running from cron(1M).
The option causes to start a file system consistency check (without correction) after the backup is complete. For correct results, it is
important that the system be effectively single-user while is running, especially if is allowed to automatically fix whatever inconsisten-
cies it finds. does not ensure that the system is single-user.
You can edit to customize it for your system. Several local values are used that can be customized:
specifies which directories to back up recursively (usually
meaning all directories);
file name where start and finish times, block counts, and error messages
are logged;
file name whose date is the date of the last archive;
file name that is checked by
to remind the next person who logs in to change the backup tape;
file name where start and finish times and
output is logged.
You may want to make other changes, such as whether or not does automatic correction (according to its arguments), where output is
directed, other information logging, etc.
In all cases, the output from is a normal archive file (or volume) which can be read using with the option.
File Recovery
creates archive tapes with all files and directories specified relative to the root directory. When recovering files from an archive tape
created by you should be in the root directory and specify the directory path names for recovered files relative to the root directory When
specifying the directory path name for file recovery by do not precede the leading directory name with a slash. If you prefer, you can
also use with a option to determine how files and directories are named on the archive tape before attempting recovery.
WARNINGS
Refer to in cpio(1).
When runs out of tape, it sends an error to standard error and demands a new special file name from
To continue, rewind the tape, mount the new tape, type the name of the new special file at the system console, and press
If is being run unattended from cron(1M) and the tape runs out, terminates, leaving the process still waiting. Kill this process when you
return.
FILES
parameterized file names
SEE ALSO
cpio(1), find(1), touch(1), cron(1M), fbackup(1M), frecover(1M), fsck(1M), acl(5).
backup(1M)