Sponsored Content
Full Discussion: Bad magic number error
Operating Systems Solaris Bad magic number error Post 302912031 by dunkpancakes on Tuesday 5th of August 2014 09:46:11 AM
Old 08-05-2014
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 [pathname] command but receive the Bad Magic Number Error. Does an OS need to be installed prior to updating OB and ALOM? I ask this first before we try other routes like formatting.

Thanks.
 

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

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

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

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

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

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
BOOTCTL(1)							      bootctl								BOOTCTL(1)

NAME
bootctl - Control the firmware and boot manager settings SYNOPSIS
bootctl [OPTIONS...] status bootctl [OPTIONS...] list bootctl [OPTIONS...] update bootctl [OPTIONS...] install bootctl [OPTIONS...] remove DESCRIPTION
bootctl checks, updates, installs or removes the boot loader from the current system. bootctl status checks and prints the currently installed versions of the boot loader binaries and all current EFI boot variables. bootctl list displays all configured boot loader entries. bootctl update updates all installed versions of systemd-boot, if the current version is newer than the version installed in the EFI system partition. This also includes the EFI default/fallback loader at /EFI/BOOT/BOOT*.EFI. A systemd-boot entry in the EFI boot variables is created if there is no current entry. The created entry will be added to the end of the boot order list. bootctl install installs systemd-boot into the EFI system partition. A copy of systemd-boot will be stored as the EFI default/fallback loader at /EFI/BOOT/BOOT*.EFI. A systemd-boot entry in the EFI boot variables is created and added to the top of the boot order list. bootctl remove removes all installed versions of systemd-boot from the EFI system partition, and removes systemd-boot from the EFI boot variables. If no command is passed, status is implied. OPTIONS
The following options are understood: -h, --help Print a short help text and exit. --version Print a short version string and exit. --path= Path to the EFI System Partition (ESP). If not specified, /efi, /boot, and /boot/efi are checked in turn. It is recommended to mount the ESP to /boot, if possible. -p, --print-path This option modifies the behaviour of status. Just print the path to the EFI System Partition (ESP) to standard output and exit. --no-variables Do not touch the EFI boot variables. EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise. SEE ALSO
Boot loader specification[1] systemd boot loader interface[2] NOTES
1. Boot loader specification https://www.freedesktop.org/wiki/Specifications/BootLoaderSpec 2. systemd boot loader interface https://www.freedesktop.org/wiki/Software/systemd/BootLoaderInterface systemd 237 BOOTCTL(1)
All times are GMT -4. The time now is 09:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy