Sponsored Content
Full Discussion: wrong magic number
Operating Systems Solaris wrong magic number Post 302321111 by incredible on Saturday 30th of May 2009 07:19:07 AM
Old 05-30-2009
format -> p -> p-> lab (aft confirmation, type "yes") -> q ->q
 

10 More Discussions You Might Find Interesting

1. 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

2. Shell Programming and Scripting

shell magic number with a -

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

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

4. Filesystems, Disks and Memory

Bad Super Block: Magic Number Wrong

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

5. Filesystems, Disks and Memory

Bad super block: Magic number wrong

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

6. UNIX for Dummies Questions & Answers

Solaris magic number problem

Hello, When I boot up my ancient SUNOS 5 system. it stops at the OK prompt and complains about a bad magic number. I have told that I need run fsck but I cannot seem to do so from the OK prompt. How can I get into a diagnostic mode so I can run fsck? Thanks, (1 Reply)
Discussion started by: mojoman
1 Replies

7. Solaris

corrupt label - wrong magic number

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

8. Solaris

Recover label, wrong magic number

Is there a way to recover label? I could install (sparc) Solaris again, but it would take a lot of time. (5 Replies)
Discussion started by: orange47
5 Replies

9. 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

10. Solaris

Magic number error

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
VWRAYS(1)						      General Commands Manual							 VWRAYS(1)

NAME
vwrays - compute rays for a given picture or view SYNOPSIS
vwrays [ -i -u -f{a|f|d} | -d ] { view opts .. | picture [zbuf] } DESCRIPTION
Vwrays takes a picture or view specification and computes the ray origin and direction corresponding to each pixel in the image. This information may then be passed to rtrace(1) to perform other calculations. If a given pixel has no corresponding ray (because it is out- side the legal view boundaries), then six zero values are sent instead. The -i option may be used to specify desired pixel positions on the standard input rather than generating all the pixels for a given view. If the -u option is also given, output will be unbuffered. The -f option may be used to set the record format to something other than the default ASCII. Using raw float or double records for exam- ple can reduce the time requirements of transferring and interpreting information in rtrace. View options may be any combination of standard view parameters described in the rpict(1) manual page, including input from a view file with the -vf option. Additionally, the target X and Y dimensions may be specified with -x and -y options, and the pixel aspect ratio may be given with -pa. The default dimensions are 512x512, with a pixel aspect ratio of 1.0. Just as in rpict, the X or the Y dimension will be reduced if necessary to best match the specified pixel aspect ratio, unless this ratio is set to zero. The -pj option may be used to jitter samples. The default value of 0 turns off ray jittering. If the -d option is given, then vwrays just prints the computed image dimensions, which are based on the view aspect and the pixel aspect ratio just described. The -ld switch will also be printed, with -ld+ if the view file has an aft clipping plane, and -ld- otherwise. This is useful for passing options to the rtrace command line. (See below.) If the view contains an aft clipping plane (-va option), then the magnitudes of the ray directions will equal the maximum distance for each pixel, which will be interpreted correctly by rtrace with the -ld+ option. Note that this option should not be given unless there is an aft clipping plane, since the ray direction vectors will be normalized otherwise, which would produce a uniform clipping distance of 1. If a picture is given on the command line rather than a set of view options, then the view and image dimensions are taken from the picture file, and the reported ray origins and directions will match the center of each pixel in the picture (plus optional jitter). If a depth buffer file is given as well, then vwrays computes the intersection point of each pixel ray (equal to the ray origin plus the depth times the ray direction), and reports this instead of the ray origin. The reported ray direction will also be reversed. The inter- pretation of this data is an image of origins and directions for light rays leaving the scene surfaces to strike each pixel. EXAMPLES
To compute the ray intersection points and returned directions corresponding to a picture and its depth buffer: vwrays scene_v2.hdr scene_v2.zbf > scene_v2.pts To determine what the dimensions of a given view would be: vwrays -d -vf myview.vf -x 2048 -y 2048 To generate a RADIANCE picture using rtrace instead of rpict: vwrays -ff -vf view1.vf -x 1024 -y 1024 | rtrace `vwrays -d -vf view1.vf -x 1024 -y 1024` -ffc scene.oct > view1.hdr AUTHOR
Greg Ward Larson ACKNOWLEDGMENT
This work was supported by Silicon Graphics, Inc. BUGS
Although vwrays can reproduce any pixel ordering (i.e., any image orientation) when given a rendered picture, it will only produce standard scanline-ordered rays when given a set of view parameters. SEE ALSO
rcalc(1), rpict(1), rtcontrib(1), rtrace(1) RADIANCE
1/15/99 VWRAYS(1)
All times are GMT -4. The time now is 01:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy