bad LIF magic error

Thread Tools Search this Thread
Operating Systems HP-UX bad LIF magic error
# 1  
Old 09-21-2007
bad LIF magic error

i am having b2000 hp- visulized matchine, which i am using as server, i booted in maintanance mode and increased root file system lvm, after reboot i can not boot system and getting "bad LIF magic error", i tried to installed O/S again (hpux 10.20 ro hpux 11) but i can not installed its showing IPL corrupted, even i can not boot system in singel user mode, can somebody help me for this.

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/ Disk2/stage/Components/oracle.webdb.wwdoc/ (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
badsect(8)						      System Manager's Manual							badsect(8)

badsect - Creates files to contain bad sectors SYNOPSIS
/usr/sbin/badsect bbdir sector... DESCRIPTION
The badsect command makes a file to contain a bad sector. Normally, bad sectors are made inaccessible by the standard formatter, which provides a forwarding table for bad sectors to the driver. If a driver supports the bad blocking standard, it is preferable to use that method to isolate bad blocks because the bad block forwarding makes the disk appear perfect, and such disks can then be copied with dd(1). The technique used by badsect is also less general than bad block forwarding, as badsect cannot make amends for bad blocks in the i-list of file systems or in swap areas. On some disks, adding a sector that is suddenly bad to the bad sector table currently requires the running of the standard formatter. Thus, to deal with a newly bad block or on disks where the drivers do not support the bad-blocking standard, badsect can be used to good effect. Use the badsect command on a quiet file system in the following way: Mount the file system and change to its root directory. Make a direc- tory BAD there. Run badsect, giving as argument the BAD directory followed by all the bad sectors you wish to add. (The sector numbers must be relative to the beginning of the file system, as reported in console error messages.) Change back to the root directory, unmount the file system, and run fsck(8) on the file system. The bad sectors should show up in two files or in the bad sector files and the free list. Have fsck remove files containing the offending bad sectors, but do not have it remove the BAD/nnnnn files. This operation will leave the bad sectors in only the BAD files. The badsect command works by giving the specified sector numbers in a mknod(2) system call, creating an illegal file whose first block address is the block containing bad sector and whose name is the bad sector number. When fsck discovers the file, it will ask "HOLD BAD BLOCK?" An affirmative response will cause fsck to convert the inode to a regular file containing the bad block. RESTRICTIONS
If more than one of the sectors comprised by a file system fragment are bad, you should specify only one to badsect, as the blocks in the bad sector files cover all the sectors in a file system fragment. ERRORS
The badsect command refuses to attach a block that resides in a critical area or is out of range of the file system. A warning is issued if the block is already in use. SEE ALSO
Commands: fsck(8) badsect(8)