Login or Register to Ask a Question and Join Our Community


UNIX for Dummies Questions & Answers

SCO Backup Problem (bad Sblock Magic Number)

 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers SCO Backup Problem (bad Sblock Magic Number)
# 1  
Old 04-21-2006
SCO Backup Problem (bad Sblock Magic Number)
Hi guys,

First I have to say that I'm not Unix expert, I just have medium level experince in Unix scripting and some knowledge with a little of hands on experience of unix administration (Solaris only). I have my plans to move ahead in that field but this is a different story.

I have a client who have Sco Unixware 7.31 and want to do a full system backup. They have Oracle 8i and its backup works properly. I tried first to do a remote backup of their test server to the tape on their live server as test because the client was afraid of making it derictly, he wants to make a test first.

Anyway, I used the ufsdump command hundreds of times, each with different options and arguments and it produces the following error: Bad sblock magic number

I used all even numbers from 2 to 126 for the blocking factor but nothing changes.

They use HP 72 GB tape. The It guy there gave me a paper of file systems: / (type:Vxfs, size:12900), /stand (type:bfs, size:20) etc... but I did not find a vxfdump command on their system.

Ufsdump 0bucf 126 live:/dev/rmt/ctape1 /


Please help and thanks in advance.
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Solaris

Bad magic number in disk label.

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

2. Solaris

Bad magic number error

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

3. Solaris

cpio: Bad magic number/header.

Hi, i got the following error while unpacking the archive file. cpio -icvd < as_sun_x86_101202_disk2.cpio Disk2/stage/Components/oracle.webdb.wwdoc/10.1.2.0.1/1/DataFiles/wwdoc.jar Disk2/stage/Components/oracle.webdb.wwdoc/10.1.2.0.1/1/DataFiles... (2 Replies)
Discussion started by: malikshahid85
2 Replies

4. Solaris

Solaris 8.2 Bad magic number

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

5. Solaris

OpenSolaris 2009 bad magic number

Hi guys, I have a big problem wiht my old Netra T1 200. I want to install OpenSolaris 2009 but there's a problem, I burned the ISO image on a CD-RW and then I tryied to install it on netra, but the setup won't to start and the error is that in the attached image. Thanks for the support and sorry... (5 Replies)
Discussion started by: Ducati87
5 Replies

6. Solaris

BAD magic number in disc label...

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

7. UNIX for Advanced & Expert Users

Bad magic number on /dev/md0

Hello All, (RHEL4) Few weeks ago I had posted a message in this forum about the problem I had when I replaced my two scsi disks and tried rebuild raid1 array. I somehow managed to up the system with working raid1 array. But the main problem persisted.. i.e when I reboot the system, mounting... (0 Replies)
Discussion started by: ravinandan
0 Replies

8. Filesystems, Disks and Memory

Bad Magic Number

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

9. UNIX for Advanced & Expert Users

bad magic number

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

10. UNIX for Dummies Questions & Answers

Bad magic number in super-block

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
Login or Register to Ask a Question

LEARN ABOUT DEBIAN

xpamethod

xpamethod(7)							SAORD Documentation						      xpamethod(7)

NAME

       XPAMethod -  XPA Communication Methods

SYNOPSIS

       XPA supports both inet and unix (local) socket communication.

DESCRIPTION

       XPA uses sockets for communication between processes. It supports three methods of socket communication: inet, localhost, and unix. In gen-
       eral, the same method should be employed for all XPA processes in a session and the global environment variable XPA_METHOD should be used
       to set up the desired method. By default, the preferred method is "inet", which is appropriate for most users. You can set up a different
       method by typing something like:

	 setenv XPA_METHOD local	      # unix csh
	 XPA_METHOD=local; export XPA_METHOD  # unix sh, bash, windows/cygwin
	 set XPA_METHOD=localhost	      # dos/windows

       The options for XPA_METHOD are: inet, unix (or local), and localhost. On Unix machines, this environment setup command can be placed in
       your shell init file (.cshrc, .profile, .bashrc, etc.) On Windows platforms, it can be placed in your AUTOEXEC.BAT file (I think!).

       By default, inet sockets are used by XPA. These are the standard Internet sockets that are used by programs such as Netscape, ftp. etc.
       Inet sockets utilize the IP address of the given machine and a (usually random) port number to communicate between processes on the same
       machine or between different machines on the Internet. (Note that XPA has an Access Control mechanism to prevent unauthorized access of XPA
       access points by other computers on the Net). For users connected to the Internet, this usually is the appropriate communication method.
       For more information about setting up XPA communication between machines, see Communication Between Machines.

       In you are using XPA on a machine without an Internet connection, then inet sockets are not appropriate. In fact, an XPA process often will
       hang for many seconds while waiting for a response from the Domain Name Service (DNS) when using inet sockets. Instead of inet sockets,
       users on Unix platforms can also use unix sockets (also known as local sockets). These sockets are based on the local file system and do
       not make use of the DNS. They generally are considered to be faster than inet sockets, but they are not implemented under Windows. Use
       local sockets as a first resort if you are on a Unix machine that is not connected to the Internet.

       Users not connected to the Internet also can use localhost sockets. These are also inet-type sockets but the IP address used for the local
       machine is the localhost address, 0x7F000001, instead of the real IP of the machine. Depending on how sockets are set up for a given plat-
       form, communication with the DNS usually is not required in this case (though of course, XPA cannot interact with other machines).  The
       localhost method will generally work on both Unix and Windows platforms, but whether the DNS is required or not is subject to individual
       configurations.

       A final warning/reminder: if your XPA-enabled server hangs at startup time and your XPA_METHOD is inet, the problem probably is related to
       an incorrect Internet configuration. This can be confirmed by using the unix method or (usually) the localhost method. You can use these
       alternate methods if other hosts do not need access to the XPA server.

SEE ALSO

       See xpa(7) for a list of XPA help pages

version 2.1.14							   June 7, 2012 						      xpamethod(7)