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
Code:
***************************
#boot cdrom
or
#boot cdrom -s
****************************
ERROR............
can't open Boot device: disk File and args:
Bad Magic number in disk label
Can't open disk label package
.............................................
after this it returns to OK propmt.
i tried a lot , changhe my CD ROM, installation media, HDD.
everything is detected.
but its not starting the installation.
can someone help me to get rid of this.
Thanks in advance.
Last edited by pludi; 12-10-2009 at 02:51 AM..
Reason: removed links
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)
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)
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)
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)
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)
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)
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)
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)
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 SUSE
mkswap
MKSWAP(8) Linux Programmer's Manual MKSWAP(8)NAME
mkswap - set up a Linux swap area
SYNOPSIS
mkswap [-c] [-f] [-p PSZ] [-L label] [-U uuid] device [size]
DESCRIPTION
mkswap sets up a Linux swap area on a device or in a file.
The device argument will usually be a disk partition (something like /dev/sdb7) but can also be a file. The Linux kernel does not look at
partition Id's, but many installation scripts will assume that partitions of hex type 82 (LINUX_SWAP) are meant to be swap partitions.
(Warning: Solaris also uses this type. Be careful not to kill your Solaris partitions.)
The size parameter is superfluous but retained for backwards compatibility. (It specifies the desired size of the swap area in 1024-byte
blocks. mkswap will use the entire partition or file if it is omitted. Specifying it is unwise - a typo may destroy your disk.)
The PSZ parameter specifies the page size to use. It is almost always unnecessary (even unwise) to specify it, but certain old libc ver-
sions lie about the page size, so it is possible that mkswap gets it wrong. The symptom is that a subsequent swapon fails because no swap
signature is found. Typical values for PSZ are 4096 or 8192.
After creating the swap area, you need the swapon command to start using it. Usually swap areas are listed in /etc/fstab so that they can
be taken into use at boot time by a swapon -a command in some boot script.
WARNING
The swap header does not touch the first block. A boot loader or disk label can be there, but it is not recommended setup. The recommended
setup is to use a separate partition for a Linux swap area.
mkswap like many others mkfs-like utils erases the first block to remove old on-disk filesystems.
mkswap refuses to erase the first block on a device with a disk label (SUN, BSD, ...) or on whole disk (e.g. /dev/sda).
OPTIONS -c Check the device (if it is a block device) for bad blocks before creating the swap area. If any are found, the count is printed.
-f Force - go ahead even if the command is stupid. This allows the creation of a swap area larger than the file or partition it
resides on.
Without this option mkswap will refuse to erase the first block on a device with a partition table or on whole disk (e.g. /dec/sda).
-p PSZ Specify the page size to use.
-L label
Specify a label, to allow swapon by label. (Only for new style swap areas.)
-v0, -v1
Specify the swap space version. This option is deprecated and -v1 is supported only.
The kernel has not supported v0 swap space format since 2.5.22. The new version v1 is supported since 2.1.117.
-U uuid
Specify the uuid to use. The default is to generate UUIDs.
NOTES
The maximum useful size of a swap area depends on the architecture and the kernel version. It is roughly 2GiB on i386, PPC, m68k, ARM,
1GiB on sparc, 512MiB on mips, 128GiB on alpha and 3TiB on sparc64. For kernels after 2.3.3 there is no such limitation.
Note that before 2.1.117 the kernel allocated one byte for each page, while it now allocates two bytes, so that taking a swap area of 2 GiB
in use might require 2 MiB of kernel memory.
Presently, Linux allows 32 swap areas (this was 8 before Linux 2.4.10). The areas in use can be seen in the file /proc/swaps (since
2.1.25).
mkswap refuses areas smaller than 10 pages.
If you don't know the page size that your machine uses, you may be able to look it up with "cat /proc/cpuinfo" (or you may not - the con-
tents of this file depend on architecture and kernel version).
To setup a swap file, it is necessary to create that file before initializing it with mkswap, e.g. using a command like
# dd if=/dev/zero of=swapfile bs=1024 count=65536
Note that a swap file must not contain any holes (so, using cp(1) to create the file is not acceptable).
SEE ALSO fdisk(8), swapon(8)AVAILABILITY
The mkswap command is part of the util-linux-ng package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/.
Linux 13 March 2009 MKSWAP(8)