Bad magic no in disk label

dear all,
i am facing a problem with the above said matter.i have sun fire v480 m/c with solaris 9 loaded.now the problem i am facing is,while booting the system it shows BAD MAGIC NO IN DISK LABEL.CANT OPEN BOOT DISK.
i have tried with following.
booting the system in single user mode with the boot cd and run FSCK.
but it didnt work.
can anybody can help me out.

Standard question posted many times on this forum.
Boot to the prompt.
Type `format`
When presented with menu, choose `label disk`
Follow simple instructions and choose `save` ....
Reboot your machine and the drive should be recognized.
Good luck, John.

Similar Messages

Sun Ultra 25 - Bad magic number in disk label

I have a Sun Ultra 25 SPARC that is booting fine to it's 80GB SATA drive. Solaris 10, OpenBoot 4.22.19.
Here's what I did:
I installed a 2TB Western Digital SATA drive into the HDD1 slot.
I formatted the disk in the HDD1 slot via the format command, labeled the disk, and divided it into partitions.
I then used newfs to build the ufs on all partitions.
I mirrored the disk in HDD0 to the disk in HDD1 using ufsdump for all partitions. The data is accessible and looks ok.
After this was done I did an installboot to /dev/rdsk/c1t1d0s0 (the / partition of the HDD1 slot).
I then did a fsck on every partition to verify that they are okay.
I then took the hard drive in HDD1 and put it in the HDD0 slot, now wanting to boot off that disk.
At the reboot:
Bad magic number in disk label
Can't open disk label package
If I do a probe-scsi:
MPT Version 1.05, Firmware Version 1.08.03.00
Target 0
Unit 0 Disk ATA WDC WD20EADS-00R0A01 3907029168 Bocks, 2000 GB SATA device PhyNum 0
As far as I can tell disk0 is the correct devalias which is:
/pci@1e,600000/pci@0/pci@9/pci@0/scsi@1/disk@0,0
I just don't understand how the fsck is okay, but the boot give bad magic number in disk label?
The 80GB drive in HDD slot 0 works fine with the boot disk0 command, all I'm doing is swapping a larger disk with the same data for the smaller disk.

if it is like any other Sun product, it needs to go through the format command and get a volname.... it is just a label, but it needs to be done.
haroldkarl

T6340 cannot boot disk - Bad magic number in disk label

Hi,
I have a shiny new T6340 that I am just setting up.
When I get through the CMM to the SP and onto the EEPROM,
I then try to start the boot process:
{0} ok boot disk1
Sun Blade T6340 Server Module, No Keyboard
Copyright 2009 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.30.4, 130848 MB memory available, Serial #76313344.
Ethernet address 0:14:4f:8c:73:0, Host ID: 848c7300.
Boot device: /pci@500/pci@0/pci@9/@0/disk@1 File and args:
Bad magic number in disk label
Can't open disk label package
ERROR: boot-read fail
Evaluating:
Can't open boot device
{0} ok show-disks
a) /pci@500/pci@0/pci@9/LSILogic,sas@0/disk
b) /pci@500/pci@0/pci@2/pci@0/usb@0,2/storage@5/disk
c) /pci@500/pci@0/pci@2/pci@0/usb@0,2/storage@1/disk
q) NO SELECTION
Enter Selection, q to quit: q
{0} ok boot /pci@500/pci@0/pci@9/LSILogic,sas@0/disk
Boot device: /pci@500/pci@0/pci@9/LSILogic,sas@0/disk File and args:
Bad magic number in disk label
Can't open disk label package
ERROR: boot-read fail
Can't open boot device
{0} ok This is a brand new B6000 system and has not been booted before.
Please tell me what I need to do to enable the disks, so I can do the next bit!
rachel

@rachel,
In your original post you showed a screen capture of what you tried.
First you typed "boot disk1". ( Why disk1? Why not disk0?)
When that didn't seem to work, you displayed the disks recognized by the system at OpenBoot.
The first of those disks was a device path of
/pci@500/pci@0/pci@9/LSILogic,sas@0/disk{code}
and so you attempted to boot from that but omitted whatever slice might be the boot slice of a factory preinstalled OS. For example...
{code:java}
boot /pci@500/pci@0/pci@9/LSILogic,sas@0/disk@0,0{code}
(just guessing at what could be that bootable slice).
What happens if you simply type "*boot*" when you are at OBP?

Bad Magic Number in Disk Label & DiskSuite

Envrionment:
E450
Solaris 8
DiskSuite 4.2.1
16 disks
Because of a power failure, after reboot one of the disks has bad magic number in its disk label. The slice was in a mirror. DiskSuite has hot spares and one of them took over the failed slice. I am trying to figure out how to get it back to where it was.
I think I should use 'format' to recover the disk label from the backup label. However, once the label is recovered, how do I make it stop using the hotspare and have the failed slice join back to the mirror?
Sorry if this is basic question, I am relatively new to Sun/Solaris and I just took over the E450.
Thanks,

Envrionment:
E450
Solaris 8
DiskSuite 4.2.1
16 disks
Because of a power failure, after reboot one of the
disks has bad magic number in its disk label. The
slice was in a mirror. DiskSuite has hot spares and
one of them took over the failed slice. I am trying to
figure out how to get it back to where it was.
I think I should use 'format' to recover the disk
label from the backup label. However, once the label
is recovered, how do I make it stop using the hotspare
and have the failed slice join back to the mirror?
Sorry if this is basic question, I am relatively new
to Sun/Solaris and I just took over the E450.
Thanks,Since the host spare took over then you're free to repair/replace the bad drive. In this case you could check the drive using format and partition to view the partitions. If the label is bad then I would suspect the drive is still good and a simple format>label and save command would repair the label. Then once this is done if all goes well then the system should rebuild the drive and the hot spare will not longer be used. The system should regonize the drive as a replacement and rebuild it then stop using the hot spare.
Michael

Bad number in disk label?

I am attempting to install Sol.8 on a sparc 10. when I attempt to boot from the cdrom I receive this error:" Bad magic number in disk label
Can't open disk label package"
I can identify the cdrom with the probe-scsi command. I relize that this is being caused because the disk has not yet been formated. Any thoughts on how to format this new disk without accessing the cdrom?Any thoughts would be appreciated!

Looks like your cdrom dive or cd media is defective. Probe scsi will detect the cdrom hardware but can't verify its reading ability .Media can be checked by using it on another system and trying to boot with cd . For cdrom try using another drive or try cd lens cleaning.
Hemant
http://www.adminschoice.com

Yet another question about "bad magic number error"

I have acquired a Sun Blade 1000 w/o installed OS and a set of genuine Solaris 10 media. As a Solaris neophyte I'm either being stupid or I've got a real problem and I can't tell which. So help would be greatly appreciated.
With the sparc disc in, if I let the machine start up I get a common error message for used sun kit:
Bad magic number in disk label
Can't open disk label package
Boot device: net File and args:
Timeout waiting for ARP/RARP packet
I stop-a and try to boot from the sparc disc and get the error message:
Boot device: /pci@8,7000000/scsi@6/disk@6,0:f File and args: -s
Bad magic number in disk label
Can't open disk label package
Can't open boot device
Using probe-scsi-all shows the Seagate HDD (LiD: 1 HA: 1 LUN: 0 ...), /scsi@6,1, and the Toshiba DVD-ROM (/scsi@6). If the DVD drive is done in how can I tell and what are the specification I need to look for in a replacement?
null

Hello "null",
please check if the data cable to the DVD is properly attached.
Some early versions of the Toshiba DVD drive won't boot from a DVD due to outdated firmware (1007).
Review the version (either 1007 or 1009) in the probe-scsi-all output. If the drive currently uses the old firmware,
the fix is to update the drives firmware (1009), which indeed requires an installed Solaris. The updated DVD firmware is contained in patch 111649-02.
If the firmware is uptodate and you have access to CD media (Solaris 9 or 10) you can the try to boot from
Solaris 9 Software 1 or Solaris 10 CD 1.
If no CD media is available, just download the image file of CD 1 from the download center and burn a CD (slower burning speed recommended). Boot from this CD into single-user mode (boot cdrom -s). If this succeeds, download the other CD images and use them to install Solaris.
As a replacement drive any SCSI DVD that can be jumpered to 2048 byte blocksize works.
Michael

"Bad checksum in disk label" & "Can't open disk label package"

Hello,
I'm brand new to Sun/Solaris.
I have a Sun Blade 150, with SunOS 5.8.
I wanted to make a backup to prevent future data loss, so I put the disk in a normal PC with Windows XP to try to make a backup with Norton Ghost, the disk was detected, but not the file volume, so I place the disk on a desktop PC, and used Norton Ghost for DOS, the disk was recognized but once again not the file volume, so I wasn't able to make a disk backup, and I quit.
Put back the disk on the Sun Blade 150 PC, and then I was unable to startup the PC, showing the message "Bad checksum in disk label" and "Can't open disk label package".
What's wrong?
How can I solve this?
I need the data that's inside the hard-disk, so I cannot make a clean install, and i also don't have any install CD.
Thanks for any help,
JS

Thanks for the fast response,
i did't allow WindowsXP to write anythink to the disk, but somethink is written,and I don't know what. So now, the Spark-System dosn't boot from the HDD and the data on the disk is very important for me! When I format the disk all data are lost, right?
Is there a way to "rewrite" the Disk-Label-Checksum? I have an original Boot-CD-ROM, another HDD to install Solaris and so one, but I need the data of the corrupted HDD. And I also have not really a glue to use Solaris or any other UNIX, I'm a Windows-User.........

OCFSV2 : mount.ocfs2: Bad magic number in inode

Hi everyone,
DUe to high load I/O, i can't mount my ocfsV2 partition :
mount.ocfs2: Bad magic number in inode while trying to determine heartbeat information
marge:~# fsck.ocfs2 /dev/sdc1
fsck.ocfs2: Bad magic number in inode while initializing the DLM
The disk is an iscsi device, there are no block damaged.
I try to modify the signature with bvi but the result is the same.
The disk containt image file created with dd (Virtual machine).
Do you have a software or a workaround to recover my vm's ?
Or i must consider to format my parttion ?
Thank you

I know , i wan't to switch to Linux forum but how to do that ? :-)
marge:~# modinfo ocfs2
filename: /lib/modules/2.6.26-2-xen-amd64/kernel/fs/ocfs2/ocfs2.ko
license: GPL
author: Oracle
version: 1.5.0
description: OCFS2 1.5.0
srcversion: C692B48692BFC8597E4D7A7
depends: jbd,ocfs2_stackglue,ocfs2_nodemanager
vermagic: 2.6.26-2-xen-amd64 SMP mod_unload modversions Xen
I created the filesystem with debian :
mkfs.ocfs2 /dev/sdc1
By default it create 4K cluster size. And it make 6 backup off superblock.
But recover superblock doesn"t work :
marge:~# fsck.ocfs2 -r 1 /dev/sdc1
[RECOVER_BACKUP_SUPERBLOCK] Recover superblock information from backup block#262144? <n> y
fsck.ocfs2: Bad magic number in inode while initializing the DLM
marge:~# debugfs.ocfs2 -R stats /dev/sdc1
     Revision: 0.90
     Mount Count: 0 Max Mount Count: 20
     State: 0 Errors: 0
     Check Interval: 0 Last Check: Thu May 7 16:26:37 2009
     Creator OS: 0
     Feature Compat: 1 BackupSuper
     Feature Incompat: 16 Sparse
     Tunefs Incomplete: 0 None
     Feature RO compat: 1 Unwritten
     Root Blknum: 5 System Dir Blknum: 6
     First Cluster Group Blknum: 3
     Block Size Bits: 12 Cluster Size Bits: 12
     Max Node Slots: 4
     Label:
     UUID: 3677066B5C7B424BB79FE30764552B57
     Cluster stack: classic o2cb
     Inode: 2 Mode: 00 Generation: 3020404948 (0xb407b8d4)
     FS Generation: 3020404948 (0xb407b8d4)
     Type: Unknown Attr: 0x0 Flags: Valid System Superblock
     User: 0 (root) Group: 0 (root) Size: 0
     Links: 0 Clusters: 52432135
     ctime: 0x4a02ef9d -- Thu May 7 16:26:37 2009
     atime: 0x0 -- Thu Jan 1 01:00:00 1970
     mtime: 0x4a02ef9d -- Thu May 7 16:26:37 2009
     dtime: 0x0 -- Thu Jan 1 01:00:00 1970
     ctime_nsec: 0x00000000 -- 0
     atime_nsec: 0x00000000 -- 0
     mtime_nsec: 0x00000000 -- 0
     Last Extblk: 0
     Sub Alloc Slot: Global Sub Alloc Bit: 65535
debugs say superblock is ok but unable to mount the partition :
mount.ocfs2: Bad magic number in inode while trying to determine heartbeat information

Can't read disk label

Dear Sun experts,
I am trying to install Solaris 9 on a Sun Ultra 10 Sparc workstation. This system formerly had Solaris 8 on it, but we decided to do a reinstallation to configure things the way we wanted them.Before doing that we encountered a few problems
1.The system failed to recognize the Dell Ultra Sharp Monitor, when the signal cable was plugged into the port behind the computer. To solve this we researched and were told to remove the Video card attached to the mother board, and this we did.The system now recognized the dell monitor and booted in Solaris 8.
2.We ran sys-unconfig to reconfigure the system to change the hostname on a reboot.We powered off the computer.Afterward we would go through the sys-unconfig program in an indefinite loop.So I powered off the computer each time i got stuck.
3.Lastly I tried to do a STOP A to try to go to the 'ok' prompt in order to do a clean installation of Solaris 8 Installation CD, by running
ok boot cdrom [ENTER]
Here's what I am getting:
Boot device: /pci@1f, 0/pci@1,1/ide@3/cdrom@2,0:f File and args:
Can't read disk label.
Can't open disk label package
Can't open boot device
ok
[end]
I want to do a clean installation of the Solaris 9 CD on the sparc ultra 10 computer.Please can anyone help me out? I looked at the solaris 9 installation guide, and it asked that I follow this procedure. Please respond if you can help.
Also of note is that I got this system from a user who had installed Solaris 8 sparc on it earlier.
Thanks a million!
Omon

Hi!
After a day fighting with same problem and found no good solution on the internet , I was able to do a workaround in order to be able to boot my sun bade 1500 that was giving the "can't open disk label" message.
I found no source of the problem but someone with more knowledge could guess. (maybe a default bad alias definition of cdrom ��?)
Well, first of all I plugued a normal IDE CDrom as primary slave, leaving IDE HD as primary master. And inserted solaris 8 installation CD (as it was my only solaris bootable CD, but I guess that I oculd boot any other CD).
After that, I went to the openboot prompt (ok>) and did next:
ok devalias cdrom - this will show you current path to internal CD. Use this to determine what new alias should look like.
ok setenv auto-boot? false
ok reset-all
ok probe-scsi-all - find the path to the new cdrom - write it down & write target # as well
ok show-disks - find the exact path you just wrote down and type that letter
ok nvalias cdrom2 [Ctrl] + [y] which will paste that path. Finish with @sd1,0:f AS IT's PRIMARY SLAVE
ok reset-all
ok boot cdrom2
I found this part in http://www.experts-exchange.com/Operating_Systems/Solaris/Q_ 20757891.html
except teh @sd1,0:f, I found that with my good luck!
After that I was able to boot with CD. the installation failed, but at least I was able to mount / filesystem and modify my /etc/passwd ... my target!
HTH
Cheers!

Sol_10 x86 5/08 disk label corruption (yes i have searched...)

I am truly sorry if the following is going to be a "oh no not this again" issue.
I am having an issue with 3 of my disks having "primary label corrupt: using backup" issues. Here is what I have tried and what has happened thusfar:
first I tried format, which core dumped
# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
       0. c0d0 <drive type unknown>
          /pci@0,0/pci-ide@11/ide@0/cmdk@0,0
       1. c0d1 <drive type unknown>
          /pci@0,0/pci-ide@11/ide@0/cmdk@1,0
       2. c1d0 <drive type unknown>
          /pci@0,0/pci-ide@11/ide@1/cmdk@0,0
       3. c1d1 <DEFAULT cyl 30398 alt 2 hd 255 sec 63>
          /pci@0,0/pci-ide@11/ide@1/cmdk@1,0
       4. c3d0 <DEFAULT cyl 38910 alt 2 hd 255 sec 63>
          /pci@0,0/pci-ide@14,1/ide@1/cmdk@0,0
Specify disk (enter its number): 0
Segmentation Fault - core dumpedok, thats wierd (and it does it with the other "drive type unknown" disks as well"). So I looked around and found a patch for format on x86 with a revision just a bit newer than what I had (137022-01 came with the install, I tried 137022-02's format command), to no avail (same response).
I then tried fmthard to try and read the label, which responded with "disk must be labeled first"
so I thought, ok, I will just use one of the working labels as a start (4 of my 5 disks are identical, so I figured I could fix the 3 bad ones using an existing disk label)
so I used fmthard again to write a disklabel that I had copied from the one good disk:
{code}
# fmthard -i -n "" /dev/rdsk/c1d1s2 > /tmp/partmap
# fmthard -s /tmp/partmap -n "" /dev/rdsk/c0d0s2
fmthard: Partition 8 overlaps partition 2. Overlap is allowed
only on partition on the full disk partition).
fmthard: Partition 9 overlaps partition 2. Overlap is allowed
only on partition on the full disk partition).
expected one reserved partition, but found 0
{code}
which I guess is another way to spell failure, as I still can't read a disklabel from the drive.
prtvtoc also reports "invalid VTOC" on the drives in question.
I have also tried booting a linux live environment, and partitioning these drives with one big solaris (code 'bf') partition on each. this had no effect on the issue.
I would like to point out that this very system was running solaris 10 x86 5/08 with the exact same harddrives 1 week ago. I had to re-install after some momentary laps of reason made me try out linux on the machine. this shouldn't have done much, as these drives have at one point been used in solaris, freebsd, and linux during their lives, and they haven't had much to do anyway, so I am confident in their current condition.
My big question is: why have multiple versions of format failed me? and is there any other way to give a disk a brand new disk label? there is nothing on the drives, so I don't care what happens to the data.
thank you all in advance

thank you both for your responses.
you aren't going to believe this, but format now behaves! it seems as though after creating a zfs pool using the disks that crashed format, the disks now show up just fine under format, in fact format says:
Searching for disks...done
AVAILABLE DISK SELECTIONS:
       0. c0d0 <SAMSUNG-S09QJ1OA10134-0001-232.89GB>
          /pci@0,0/pci-ide@11/ide@0/cmdk@0,0
       1. c0d1 <WDC WD25- WD-WCANKE28342-0001-232.89GB>
          /pci@0,0/pci-ide@11/ide@0/cmdk@1,0
       2. c1d0 <WDC WD25- WD-WCANKE22707-0001-232.89GB>
          /pci@0,0/pci-ide@11/ide@1/cmdk@0,0
       3. c1d1 <SAMSUNG-S09QJ1LL50379-0001-232.89GB>
          /pci@0,0/pci-ide@11/ide@1/cmdk@1,0
       4. c3d0 <DEFAULT cyl 38910 alt 2 hd 255 sec 63>
          /pci@0,0/pci-ide@14,1/ide@1/cmdk@0,0
Specify disk (enter its number): 0
selecting c0d0
NO Alt slice
No defect list found
[disk formatted, no defect list found]
/dev/dsk/c0d0s0 is part of active ZFS pool pool. Please see zpool(1M).I am running 64-bit on an amd phenom 9550 based machine.
I am going to read through the zfs documents (ALL of them, not just the quick-starts) and see what it says about disk labels.
here is pstack's output on the core file of `format'
# pstack ./core
core './core' of 1013: format
----------------- lwp# 1 / thread# 1 --------------------
080626e1 c_disk   (8047560, 8047454, feffb818, 4, 806740e, 0) + 369
08060777 main     (1, 8047498, 80474a0) + 2e3
080547c6 ???????? (1, 80475c8, 0, 80475cf, 8047603, 8047618)
----------------- lwp# 2 / thread# 2 --------------------
feeb5053 _door_return (0, 0, 0, 0) + 23
fec30d3d door_create_func (0) + 29
feeb3a81 _thr_setup (feab0200) + 4e
feeb3d70 _lwp_start (feab0200, 0, 0, febbeff8, feeb3d70, feab0200)
----------------- lwp# 3 / thread# 3 --------------------
feeb3dcb __lwp_park (80c5c08, 80c5c18, 0) + b
feeae60e cond_wait_queue (80c5c08, 80c5c18, 0, 0) + 3b
feeaeb07 _cond_wait (80c5c08, 80c5c18) + 66
feeaeb49 cond_wait (80c5c08, 80c5c18) + 21
fed82bc8 subscriber_event_handler (8091e00) + 3f
feeb3a81 _thr_setup (feab0a00) + 4e
feeb3d70 _lwp_start (feab0a00, 0, 0, feaaeff8, feeb3d70, feab0a00)

OCFS2 bad magic number

Hello.
Do anybody know about what doing with this error:
mount /dev/sde /raid/4
mount.ocfs2: Bad magic number in inode while trying to determine heartbeat information
fsck.ocfs2 /dev/sde
fsck.ocfs2 1.6.4
fsck.ocfs2: Bad magic number in inode while initializing the DLM
sudo debugfs.ocfs2 /dev/sde
debugfs.ocfs2 1.6.4
debugfs: ls //
ls: Bad magic number in inode while checking directory at block 66
debugfs: stats
Revision: 0.90
Mount Count: 0   Max Mount Count: 20
State: 0   Errors: 0
Check Interval: 0   Last Check: Sat Oct 18 06:30:52 2014
Creator OS: 0
Feature Compat: 3 backup-super strict-journal-super
Feature Incompat: 592 sparse inline-data xattr
Tunefs Incomplete: 0
Feature RO compat: 1 unwritten
Root Blknum: 65   System Dir Blknum: 66
First Cluster Group Blknum: 32
Block Size Bits: 12   Cluster Size Bits: 17
Max Node Slots: 16
Extended Attributes Inline Size: 256
Label: mediadisk4
UUID: 1126B3D209AA4BE088260B2A590AB995
Hash: 2997730071 (0xb2adbb17)
DX Seed[0]: 0x00000000
DX Seed[1]: 0x00000000
DX Seed[2]: 0x00000000
Cluster stack: classic o2cb
Inode: 2   Mode: 00   Generation: 2716855348 (0xa1efec34)
FS Generation: 2716855348 (0xa1efec34)
CRC32: 00000000   ECC: 0000
Type: Unknown   Attr: 0x0   Flags: Valid System Superblock
Dynamic Features: (0x0)
User: 0 (root)   Group: 0 (root)   Size: 0
Links: 0   Clusters: 213645733
ctime: 0x50bf9210 -- Wed Dec 5 22:27:28 2012
atime: 0x0 -- Thu Jan 1 03:00:00 1970
mtime: 0x50bf9210 -- Wed Dec 5 22:27:28 2012
dtime: 0x0 -- Thu Jan 1 03:00:00 1970
ctime_nsec: 0x00000000 -- 0
atime_nsec: 0x00000000 -- 0
mtime_nsec: 0x00000000 -- 0
Refcount Block: 0
Last Extblk: 0   Orphan Slot: 0
Sub Alloc Slot: Global   Sub Alloc Bit: 65535
Thanks for any help.

This looks to be filesystem corruption. The reason the fsck's don't find anything is they are really _not_ doing any checking. In the filesystem is an unmounted-cleanly flag. This flag is set when the umount(1) is done. If the system were to crash with the filesystem still mounted, this unmounted-cleanly flag would not be set, so the system would consider the filesystem to need checking: no unmounted-cleanly flag, fsck has work to do; unmounted-cleanly flag set means fsck does nothing.
Be sure the filesystem is unmounted all around the cluster before attempting to repair the filesystem.
So do this:
    # fsck.ocfs2 -f /path/to/device/partition
The "-f" switch forces fsck.ocfs2 to ignore the state of the "unounted-cleanly" flag and actually perform its tests.
Does this repair the problem?

Trying to update OBP getting unrecognized magic number in media label

Two questions both relating to my trying to update my OBP:
1. when I typebanner I get ... AXi (UltraSPARC-IIi), PS/2 keyboard
OpenBoot 3.10.12 SME...
but when I type .version I get OBP 3.10.12
My question is which OBP update to use, AXi OBP 3.10.13 or OBP 3.10.31?
2. When I try to install either I always get the same thing
I copied the .Floppy file to a floppy
then type boot floppy nolabel just like the readme and I get this:
Unrecognized magic number in media label
Can't open disk label package
Can't open boot deviceI have also tried coping the program file to a cd and tyring boot cdrom nolabel but same results
Any ideas?
Thanks

Hello,
because the DTK boards don't support faster CPUs than 333MHz, this is a Sun board.
I was unable to locate the SPARCengine Ultra AXi OEM Service Manual, the file was finally removed. This is an alternate link
http://www.zmicro.com/download/sun-axi.pdf
The Solaris 10 media kits are only available with DVD media, but you can download the CD images. The Solaris documentation is available online
http://docs.sun.com/app/docs/prod/solaris.10?l=en
I would strongly recommend that you give Solaris 10 a try !
You might try Aurora Linux. The Ultrax AXi is among the supported systems. Linux for SPARC capabilities are behind the x86/x64 versions.
This is the link to the project page
http://auroralinux.org/
Aurora SPARC Linux Wiki
http://wiki.auroralinux.net/wiki/
Michael

E2fsck: Bad magic number in super-block

e2fsck: Bad magic number in super-block while trying to open /dev/hda1
Yup, a very tricky one this is. I did the following:
[root@(none)~]#e2fsck /dev/hda1
e2fsck 1.40.2 (12-jul-2007)
/dev/hda1: clean, 310310/4702208 files, 8118002/9396009 blocks
What can I do to fix the super-block? I unable to boot up my system right now, and I can't afford to format my disk.
I have systemrescuedisk with the TestDisk application at hand(if needed?).

B wrote:There is a backup superblock every 8192 blocks if i'm correct. So the next one is at 8193. Try telling e2fsck to use that to fix your partition.
I've tried that, with no luck I'm afraid. So I've gotten more serious and.
With Testdisk I managed to indentify these superblocks.
[Superblocks] where * means it has been e2fsck'ed
0, blocksize=4096*
32768, blocksize=4096*
98304, blocksize=4096*
163840, blocksize=4096*
229376, blocksize=4096*
294912, blocksize=4096*
819200, blocksize=4096*
884736, blocksize=4096*
1605632, blocksize=4096*
2654208, blocksize=4096*
umount /dev/hda1
e2fsck -b 32768 /dev/hda1
/dev/hda1 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
<4 minutes later>
I get the question:
Free inodes count wrong for group #1 (ie. 32254, counted=231)
Fix<y>? y
This question got repeated #286 times, where I answered the same (y) each time.
/dev/hda1: ********* FILE SYSTEM WAS MODIFIED ************
/dev/hda1: ********* REBOOT LINUX **************
/dev/hda1: 310310/4702208 files (1.5% non-contiguous), 8118002/9396009 blocks
So i rebooted... but still the same error occurs during kernel boot. So now I figured I had
to do the same with 98304 and so forth. YUP! I was right, this superblock was dirty too.
e2fsck -b 98304 /dev/hda1
answer yes to all. Reboot, and repeat with 162840. Until your kernel manages to mount
your disk cleanly and hopefully boot up.
Sadly when I e2fsck -b 98304 /dev/hda1 yet again just to check, it still claims to be dirty.
Now I'm kinda back to where I started.
I will look further into if testdisk can provide some automagic solution to my problem.
Pointers is apprecieted!

Can' t read disk label, install issues

can' t read disk label, install issues
i am trying to install solaris 8 on a sparc5 (256mb, 4.2gb,110mhz). i initially installed using the installation disk and it seemed successful as i was able to load the rest of the cds. something went wrong though b/c the system is stuck in a rebooting loop after it finished the last cd. so i went searching and found that i could only have a root partition of no bigger than 1gb. since i used the installation disk, i was not given an option to specify slice sizes. so now, i am trying to redo the install starting from the first disk (1 of 2) and skipping the installation disk. when i do a "boot cdrom" with the 1 of 2 disk, i get the cant read disk label or something about short entry and it will not boot. i am using actual Solaris 8 cds and not downloads. what can i do to get it to boot up from the first disk, or fix the partitioning on the disk?

I am using the offical Solaris 8 Installation 2/02 for SPARC Platform Edition for Sun Computer Systems February 2002, Revision A
Output from the probe-ide command follows:
device 0 (Primary Master)
ATA Model: ST3160023A
device 1 (Primary Slave)
Removable ATAPI Model: LTN4865
device 2 (Secondary Master)
ATA Model: ST340016A
device 3 (Secondary Slave)
not present
device 0 is the new hard disk that I just installed
device 1 is the CDR drive
device 2 is the original hard disk. I can boot this but now get some magic disk errors or something like that
device 3 is not present
I have all devices set to cable select according to the manual.
Thanks for your help...
Tom

Can't read disk label: Booting Blade from CDROM

Folks !
I am trying to boot Sun Blade 100 from its internal IDE CD-ROM drive
using the Solaris 8 boot/installation CD (01/01). When I give the command
"boot cdrom" from ok fromt in OpenBoot, disk seems to spin for a moment
(green light comes on) but it eventually fails complaining:
can't read disk label
can'open disk label package
failed to open boot device.
I have tried following (all to no avail)
"boot /pci@1f,0/ide@d/cdrom@1,0:f" since devalias shows that cdrom is aliased to above. I also tried cdrom@0,0:f, but same result.
tried boot/installation CD from Solaris 9
did set-defaults reset-all
checked probe-ide and show disks output to make sure CDROM is recognized - it is primary slave.
swapped another IDE CD-ROM drived pulled from a PC. It was recognized but still not bootable.
Makes me wonder if PROM/NVRAM is corrupted. Hard disk
drive is trashed as such (another Blade 100 problem, since it was crashing
often, I had to force powerdown using the switch eventually leading
to corruption of basic files like /usr/lib/libnsl.so.1, so I can't force fsck)
I have to boot from CD to recover the machine and hopefully
repair the disk drive or swap it out and upgrade to Solaris 9.
any help would be appreciated.
thanks very much.
-Sanjay Kumar

as per the message it appears either you have a bad CD drive or CD media . If you have another machine try to boot this CD and verify it is working there. If the CD is ok you will have to swap the cd drive for testing
Hemant
http://www.adminschoice.com
Folks !
I am trying to boot Sun Blade 100 from its internal
IDE CD-ROM drive
using the Solaris 8 boot/installation CD (01/01). When
I give the command
"boot cdrom" from ok fromt in OpenBoot, disk seems to
spin for a moment
(green light comes on) but it eventually fails
complaining:
can't read disk label
can'open disk label package
failed to open boot device.
I have tried following (all to no avail)
"boot /pci@1f,0/ide@d/cdrom@1,0:f" since devalias
shows that cdrom is aliased to above. I also tried
cdrom@0,0:f, but same result.
tried boot/installation CD from Solaris 9
did set-defaults reset-all
checked probe-ide and show disks output to make sure
CDROM is recognized - it is primary slave.
swapped another IDE CD-ROM drived pulled from a PC. It
was recognized but still not bootable.
Makes me wonder if PROM/NVRAM is corrupted. Hard disk
drive is trashed as such (another Blade 100 problem,
since it was crashing
often, I had to force powerdown using the switch
eventually leading
to corruption of basic files like
/usr/lib/libnsl.so.1, so I can't force fsck)
I have to boot from CD to recover the machine and
hopefully
repair the disk drive or swap it out and upgrade to
Solaris 9.
any help would be appreciated.
thanks very much.
-Sanjay Kumar

Bad magic no in disk label

Similar Messages

Maybe you are looking for