10-19-2011
well I've tried all of them and each time got same error
"BAD SUPER BLOCK: MAGIC NUMBER WRONG"
Last edited by orange47; 10-19-2011 at 10:25 AM..
10 More Discussions You Might Find Interesting
1. Solaris
I tried rebooting my Sun server just a few minutes ago and I got the following at boot:
--
Sun Fire 280R (UltraSPARC-III+) , No Keyboard
Copyright 1998-2002 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.5, 1024 MB memory installed, Serial #xxxxxxxxx
Ethernet address... (6 Replies)
Discussion started by: deckard
6 Replies
2. Shell Programming and Scripting
In one of our internal scripts (unix.run), I have noticed that the following shebang.
#!/bin/sh -
for i in test1 test2 test3 ; do
.
.
.
Any idea what the - in the magic number stands for ?
And what impact does it have on the script ?
Continuing on the same script, I have the... (3 Replies)
Discussion started by: vino
3 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. UNIX for Advanced & Expert Users
Can any one let me know like how cn i set an label or number for each function whihc are there in an shells script:
for example
cd /opt/qcom/test/
function1()
function2()
function3()
-------
i ahe a script like this .now i want to count each of this function like 1, 2, 3,............... (3 Replies)
Discussion started by: lalitka
3 Replies
5. 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
6. 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
7. Solaris
Hello All,
I m very new to this forum.
i m having SUN NETRA X1 server with 40 GB HDD (Seagate) & 128 MB RAM.
i m trying this server for SUN 10 Practise.
As i m installing SUN 9 /10 with CD ,its giving me error after OK propmt
***************************
#boot cdrom
or
#boot cdrom... (16 Replies)
Discussion started by: amrut_k
16 Replies
8. Solaris
I have created 1 LUN.
1)LUN 00BB 200GB /dev/rdsk/c1t3d44
/dev/rdsk/c2t28d44
/dev/rdsk/c3t19d44
/dev/rdsk/c4t12d44
2) Already added the new entry into sd.conf and rebooted.
3) Already done these:
powercf –q
power config
4) power display dev=all
I can see the new Symmetrix device.... (1 Reply)
Discussion started by: sirius20d
1 Replies
9. Solaris
hi . my " /usr " was full ,so i went into the failsafe mode in solaris 10 and used format utilily to adjust space for it and labeled it. But after that whenever i try to boot solaris normally ,it is giving "magic number error"
I tried
fsck -o b=32 /dev/dsk/c0d0s6 (for /usr)
newfs -N... (6 Replies)
Discussion started by: tushardul
6 Replies
10. Solaris
This is first time post...found this forum when looking for possible solution to fix my sun pc. Just one day can't boot it already showing the following:
Boot device: disk File args:
Bad magic number in disk label
Can't open disk label package
Evaluating: boot
Can't open boot device... (40 Replies)
Discussion started by: SHuKoSuGi
40 Replies
LEARN ABOUT NETBSD
badsect
BADSECT(8) BSD System Manager's Manual BADSECT(8)
NAME
badsect -- create files to contain bad sectors
SYNOPSIS
badsect bbdir sector ...
DESCRIPTION
badsect makes a file to contain a bad sector. Normally, bad sectors are made inaccessible by the standard formatter, which provides a for-
warding table for bad sectors to the driver; see bad144(8) for details. If a driver supports the bad blocking standard it is much preferable
to use that method to isolate bad blocks, since the bad block forwarding makes the pack appear perfect, and such packs can then be copied
with dd(1). The technique used by this program is also less general than bad block forwarding, as badsect can't make amends for bad blocks
in the i-list of file systems or in swap areas.
On some disks, adding a sector which is suddenly bad to the bad sector table currently requires the running of the standard DEC formatter.
Thus to deal with a newly bad block or on disks where the drivers do not support the bad-blocking standard badsect may be used to good
effect.
badsect is used on a quiet file system in the following way: First mount the file system, and change to its root directory. Make a directory
BAD there. Run badsect giving as argument the BAD directory followed by all the bad sectors you wish to add. The sector numbers must be
relative to the beginning of the file system, but this is not hard as the system reports relative sector numbers in its console error mes-
sages. Then change back to the root directory, unmount the file system and run fsck(8) on the file system. The bad sectors should show up
in two files or in the bad sector files and the free list. Have fsck(8) remove files containing the offending bad sectors, but do not have
it remove the BAD/nnnnn files. This will leave the bad sectors in only the BAD files.
badsect works by giving the specified sector numbers in a mknod(2) system call, creating an illegal file whose first block address is the
block containing bad sector and whose name is the bad sector number. When it is discovered by fsck(8) it will ask ``HOLD BAD BLOCK ?'' A
positive response will cause fsck(8) to convert the inode to a regular file containing the bad block.
DIAGNOSTICS
badsect refuses to attach a block that resides in a critical area or is out of range of the file system. A warning is issued if the block is
already in use.
SEE ALSO
bad144(8), fsck(8)
HISTORY
The badsect command appeared in 4.1BSD.
BUGS
If more than one of the sectors in a file system fragment are bad, you should specify only one of them to badsect, as the blocks in the bad
sector files actually cover all the sectors in a file system fragment.
BSD
June 5, 1993 BSD