05-14-2015
Hi hicksd8,
Good to know about the -n switch, So I will run with -n and see it first.
Regards,
Buddhike G
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
What is wrong with my syntax, I am getting bad number error. The following lines of code get the value from INI file but the variable is a combination of multiple variables. When compiling all together, I get a bad number error or changing the '((' with '{{' gets me bad substitution error. The... (2 Replies)
Discussion started by: moan71
2 Replies
3. 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
4. Shell Programming and Scripting
Hi Experts,
I have a shell script in which I have the following if condition.
if
then
CHLREP=`echo "$DSPLINE MCAUSER" | \
\opt\mqm\bin\runmqsc -e $QMGRNAME | \
"ALTER CHANNEL($CHANNEL) CHLTYPE(SVRCONN) MCAUSER('HAK')"`
echo "$CHLREP"
fi
When I run this... (1 Reply)
Discussion started by: hkhan12
1 Replies
5. 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
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
System Solaris 8
When I open a CONSOLE window the following starts scrolling:
"ServiceCommand: :write: Bad FIle Number"
This will continue to scroll without stopping. However, you can type while it is scrolling and login into root and even conduct business within the CONSOLE window. The... (1 Reply)
Discussion started by: Kevin1166
1 Replies
8. 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
9. 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
10. Red Hat
Hi Friends . my linux try to start very slowly after give it this error:
mount: wrong fs type, bad option, bad superblock on /dev/mapper/VolGroup-lv_root,
missing codepage or helper program, or other error
in some cases useful info is found in syslog - try
dmesg : tail or so
Kernel panic... (3 Replies)
Discussion started by: blackjuan
3 Replies
LEARN ABOUT OSF1
devswmgr
devswmgr(8) System Manager's Manual devswmgr(8)
NAME
devswmgr - utility to manage the device switch database
SYNOPSIS
/sbin/devswmgr [-option [parameter]]
OPTIONS
Displays the following information about the device switch database:
Whether a device switch database was read from the primary file or from a backup file
The number of entries that are in the device switch table Displays the major numbers that have been reserved by all drivers, a named
driver, or an instance of a named driver.
A driver that requires more than one entry in the device switch table uses a unique instance number to reference each of its device
switch table entries. Displays help for the devswmgr command. Releases all the major numbers for a device driver if just the
driver name is specified. Releases one major number for a device driver if the NAME and the INSTANCENUM of the driver are speci-
fied.
DESCRIPTION
The devswmgr command helps you manage the device switch table by displaying information about the devices drivers in the table.
You can also use the command to release device switch table entries. Typically, you release the entries for a driver after you have
unloaded the driver and do not plan to reload it later. Releasing the entries frees them for use by other device drivers.
EXAMPLES
The following example shows that a device switch table was loaded from the primary device and that there are 70 entries in it: %
/sbin/devswmgr -display Device switch information
device switch database read from primary file
device switch table has 70 entries The following example shows the major numbers in the device switch table that have been reserved for
the driver named cam_disk: % /sbin/devswmgr -getnum driver=cam_disk
Device switch reservation list
(*=entry in use)
driver name instance major
------------------------------- -------- -----
cam_disk 1 8*
FILES
The file that manages the device switch databases The primary device switch database file The backup device switch database file
SEE ALSO
Commands: scsimgr(8)
devswmgr(8)