Sponsored Content
Operating Systems Solaris OpenSolaris 2009 bad magic number Post 302423908 by lufen on Sunday 23rd of May 2010 07:22:41 AM
Old 05-23-2010
You can have a faulty cdrom or corrupted ISO image, both can produce the same type of errors.
I would check the md5sum of the iso image and see if that is correct and I would try to boot using another media like Solaris 10 sparc cd if you got that.
 

10 More Discussions You Might Find Interesting

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

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

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

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

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

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

8. Filesystems, Disks and Memory

Can't repair super block, bad magic number

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

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

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
MKBOOTDISK(8)						      System Manager's Manual						     MKBOOTDISK(8)

NAME
mkbootdisk - creates a stand-alone boot floppy for the running system SYNOPSIS
mkbootdisk [--version] [--noprompt] [--verbose] [--device devicefile] [--size size] [--kernelargs <args>] [--iso] kernel DESCRIPTION
mkbootdisk creates a boot floppy appropriate for the running system. The boot disk is entirely self-contained, and includes an initial ramdisk image which loads any necessary SCSI modules for the system. The created boot disk looks for the root filesystem on the device sug- gested by /etc/fstab. The only required argument is the kernel version to put onto the boot floppy. OPTIONS
--device devicefile The boot image is created on devicefile. If --device is not specified, /dev/fd0 is used. If devicefile does not exist mkinitrd cre- ates a 1.44Mb floppy image using devicefile as the filename. --noprompt Normally, mkbootdisk instructs the user to insert a floppy and waits for confirmation before continuing. If --noprompt is specified, no prompt is displayed. --verbose Instructs mkbootdisk to talk about what it's doing as it's doing it. Normally, there is no output from mkbootdisk. --iso Instructs mkbootdisk to make a bootable ISO image as devicefile. --version Displays the version of mkbootdisk and exits. --kernelargs args Adds args to the arguments appended on the kernel command line. If this is not specified mkbootdisk uses grubby to parse the argu- ments for the default kernel from grub.conf, if possible. --size size Uses ize (in kilobytes) as the size of the image to use for the boot disk. If this is not specified, mkbootdisk will assume a stan- dard 1.44Mb floppy device. SEE ALSO
grubby(8) mkinitrd(1) AUTHOR
Erik Troan <ewt@redhat.com> 4th Berkeley Distribution Tue Mar 31 1998 MKBOOTDISK(8)
All times are GMT -4. The time now is 02:07 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy