Sponsored Content
Full Discussion: Solaris 8.2 Bad magic number
Operating Systems Solaris Solaris 8.2 Bad magic number Post 302444646 by kumarmani on Thursday 12th of August 2010 10:33:14 AM
Old 08-12-2010
Are you still able to boot the from the disk into single user mode? If not then the 1st option seems to be booting the system from CD or in case if you have boot server in single user mode and mounting the slick on /a and running the fsck. Once you are through you can execute iostat -En to see if you an find something unusual in output
 

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

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

NAME
iostat - Reports I/O statistics SYNOPSIS
iostat [drive...] [interval] [count] OPERANDS
Forces iostat to display specific drives. If drive is not specified (or the specified drive does not exist on the system or cluster, iostat displays the first two drives (even if more than two disk drives are configured in the system). Causes iostat to report once each interval seconds. The first report is for all time since the system was last booted, and each subsequent report is for the last interval only.The value must not be 0. Specifies the number of reports. For example, iostat 1 10 would produce 10 reports at 1-second intervals. You cannot specify count without interval because the first numeric argument to iostat is assumed to be interval. DESCRIPTION
The iostat command reports the following information: For terminals (collectively), the number of characters read and written per second. For each disk, the number of transfers per second and bytes transferred per second (in kilobytes). For the system, the percentage of time the system has spent in user mode, in user mode running low priority (nice) processes, in system mode, and idling. To compute this information, iostat counts data transfer completions, the number of words transferred for each disk, and the collective number of input and output characters for terminals. Also, each sixtieth of a second, iostat examines the state of each disk and makes a tally if the disk is active. When you issue an iostat command on a cluster member, it displays statistics only for those disks that are local to the member and that member's usage of those shared disks that it has mounted. It displays 0 for other disks in the cluster (those it doesn't have mounted), regardless of whether they are on the shared bus or are local to some other member. EXAMPLES
The output from this example displays cpu, terminal, and disk statistics for the first two disks on the system providing 5 reports at 1 second intervals: # iostat 1 5 tty floppy1 dsk9 cpu tin tout bps tps bps tps us ni sy id 0 3 0 0 0 0 1 0 4 95 4 58 0 0 0 0 1 0 2 97 1 53 0 0 0 0 0 0 2 98 5 59 0 0 0 0 1 0 1 98 6 60 0 0 0 0 1 0 2 97 The second example specifies device names in the command: # iostat dsk2 dsk3 cdrom2 tty dsk2 cdrom2 dsk3 cpu tin tout bps tps bps tps bps tps us ni sy id 0 13 11 5 5 2 2427 1213 0 1 1 98 SEE ALSO
Commands:vmstat(1) iostat(1)
All times are GMT -4. The time now is 02:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy