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 PLAN9

u9fs

U9FS(4) 						     Kernel Interfaces Manual							   U9FS(4)

NAME

       u9fs - serve 9P from Unix

SYNOPSIS

       u9fs [ directory ]

DESCRIPTION

       U9fs  is not a Plan 9 program.  Instead it is a program that serves Unix files to Plan 9 machines using the 9P protocol (see intro(5)).	It
       is to be invoked on a Unix machine by inetd with its standard input, output, and error connected to a network connection, typically TCP	on
       an  Ethernet.   It runs as user root and multiplexes access to multiple Plan 9 clients over the single wire.  It simulates Unix permissions
       itself by assuming Plan 9 uids match Unix login names.

       If a directory is specified u9fs first does a Unix chroot system call to that directory.

       Plan 9 calls this service 9fs with TCP service number 564 on the Ethernet.  Set up this way on a machine called, say, kremvax, u9fs may	be
       connected to the name space of a Plan 9 process by

	      9fs kremvax

       Due  to	a bug in some versions of the IP software, some systems will not accept the service name 9fs, thinking it a service number because
       of the initial digit.  If so, run the service as u9fs or 564 and do the srv and mount by hand:

	      srv tcp!kremvax!u9fs
	      mount -c /srv/tcp!kremvax!u9fs /n/kremvax

       For more information on this procedure, see srv(4) and bind(1).

       U9fs serves the entire file system of the Unix machine.	It forbids access to devices because the program is single-threaded and may  block
       unpredictably.	Using  the attach specifier device connects to a file system identical to the usual system except it permits device access
       (and may block unpredictably):

	      srv tcp!kremvax!9fs
	      mount -c /srv/tcp!kremvax!9fs /n/kremvax device

       (The 9fs command does not accept an attach specifier.)  Even so, device access may produce unpredictable results if the block size  of  the
       device is greater than 8192, the maximum data size of a 9P message.

       The  source to u9fs is in the Plan 9 directory /sys/src/cmd/unix/u9fs.  To install u9fs on a Unix system, copy the source to a directory on
       that system.  Edit the makefile to set LOG to a proper place for a log file and to set the compile-time configuration correctly.  Then com-
       pile with an ANSI C compiler and install in /usr/etc/u9fs.  Install this line in inetd.conf:

	      9fs     stream  tcp     nowait  root   /usr/etc/u9fs   u9fs

       and this in services:

	      9fs     564/tcp	    9fs  # Plan 9 fs

SOURCE

       /sys/src/cmd/unix/u9fs

DIAGNOSTICS

       Problems are reported to /tmp/u9fs.log.	A compile-time flag enables chatty debugging.

SEE ALSO

       bind(1), srv(4), ip(3), nfsserver(8)

BUGS

       The implementation of devices is unsatisfactory.

																	   U9FS(4)