Sponsored Content
Operating Systems Solaris ultra 10 boot warning---corrupt label Post 302217976 by incredible on Thursday 24th of July 2008 02:22:19 AM
Old 07-24-2008
Yes, you must label the disk from format utility
Before doing that, ensure that you partition table is shown as what you want exactly. Then.. you label the disk. When you do #format again, you should not see that corrupt lable anymore
 

10 More Discussions You Might Find Interesting

1. Linux

Help! Boot failure - corrupt superblock

Hi everyone, OK, I've made a monumental fsck-up of my linux installation AND I did not backup my data properly (idiot!), so I'm really up the proverbial without a paddle here. Basically the problem is I re-sized my /home partition (hda13) using Partition Magic 8.0, after doing so my mandrake... (0 Replies)
Discussion started by: alarmcall
0 Replies

2. Solaris

Ultra 60 won't boot

I just was given an Ultra 60 that I'm trying to get started so that I can re-load the system with Solaris 10. I can't seem to get the system to boot past the initial memory check. I've tried to do an Stop-A to get to the eeprom, but can't do that. My next step is to try to send a break from the... (0 Replies)
Discussion started by: zosojohnny
0 Replies

3. Solaris

Warning: No Disk Label

Hi Fellows, I am trying to mirror 2 identical disks on a SUN Ultra 10 machines (with new installation of Solaris 8). In the process, I found 2 issues: 1. prtvtoc /dev/rdsk/c0t0d0s0 | fmthard -s - /dev/rdsk/c0t1d0s0 Result: Disk partitions between the 2 disks do not match up. 2. manually... (2 Replies)
Discussion started by: o51974
2 Replies

4. Solaris

Corrupt label bad geometry

Hi, I have a Sun X4200, when I try to reboot the machine it's not detecting the drive and it shows the following error when I try to rebuilt it. I am not sure whether its a bad HD or something else. Label says 983040 blocks: Drive says 983039 blocks WARNING:... (1 Reply)
Discussion started by: gunnervarma
1 Replies

5. Solaris

corrupt label - wrong magic number

I have created 1 LUN. 1)LUN 00BB 200GB /dev/rdsk/c1t3d44 /dev/rdsk/c2t28d44 /dev/rdsk/c3t19d44 /dev/rdsk/c4t12d44 2) Already added the new entry into sd.conf and rebooted. 3) Already done these: powercf –q power config 4) power display dev=all I can see the new Symmetrix device.... (1 Reply)
Discussion started by: sirius20d
1 Replies

6. UNIX for Advanced & Expert Users

Linux on vmware won't boot due to corrupt library file!

We have an issue here: The libc.so.6 file (link) is corrupted and it causes the system unbootable. It even doesn't boot to single user mode. How can we boot the system to fix the library file? Or is there any other solutions for this issue? Here are some boot messages:... (6 Replies)
Discussion started by: aixlover
6 Replies

7. Filesystems, Disks and Memory

Original SAN to a New Solaris Server: Corrupt Label

I've seen several posts that are similar to what I'm trying to do but no dice. I have a server (SunFire V215) that went belly up. I've set up a new one. I'm getting a corrupt label: wrong magic number error. Everything I'm seeing says label the drives, but if I do I'm afraid I'll lose the data... (0 Replies)
Discussion started by: tnelson
0 Replies

8. Emergency UNIX and Linux Support

Ubuntu filesystem error corrupt GPT label

Need help/advice urgently.:wall: I really shot myself in the foot this time. Here is the scenario Have a Solaris server Solaris 10 x86 Update 8. Installed an LSI MegaRaid 9280 raid controller and attached a 16 bay JBOD box to it, created a RAID6 virtual drive with 1 hot spare. Created a... (2 Replies)
Discussion started by: ccj4467
2 Replies

9. Solaris

Ultra 45 Boot Loop

I am trying to get an old Ultra 45 to boot and it is stuck in a loop. I cannot get anything to come up on a monitor, so when I hook up a serial connection to the TTYa interface I see the following output: @(#)OBP 4.21.2 2005/12/22 17:17 Sun Ultra 45 Workstation Clearing TLBs Loading... (0 Replies)
Discussion started by: Madrox72
0 Replies

10. Solaris

Sun Ultra 30 boot problems

Hi all, I've just replaced the eprom battery on my Sun Ultra-30 and having boot issues. For some reason its trying to boot off the network instead of the DISK1. Howe can I change it so the open boot does not default to the boot device: NET Thanks, Rob (3 Replies)
Discussion started by: robbo007
3 Replies
SUNLABEL(8)						    BSD System Manager's Manual 					       SUNLABEL(8)

NAME
sunlabel -- read or modify a SunOS disk label SYNOPSIS
sunlabel [-mnqs] device DESCRIPTION
sunlabel reads or modifies a SunOS disk label on device, which is used by the PROM on NetBSD/sparc hardware to find partitions to boot from. sunlabel only reads/writes the first 512 bytes of device. The supported options are: -m Ignore an incorrect magic number in the disk label. -n Synthesize a new label rather than reading what is there. -q Quiet mode - don't print unnecessary babble (currently this suppresses the ``sunlabel>'' prompt). -s Ignore checksum errors when reading the label. Note that -m is dangerous, especially when combined with -s, since it will then happily believe whatever garbage it may find in the label. When using these flags, all values should be checked carefully, both those printed by L and the partition table printed by P. sunlabel prints a prompt ``sunlabel>'' and expects commands. The following commands are understood: ? Show a short help message. [abcdefghijklmnop] <cylno> <size> Change partition (see below). L Print label, except for the partition table. P Print the partition table. Q Quit program (error if no write since last change). Q! Quit program (unconditionally) [EOF also quits]. S Set label in the kernel (orthogonal to W). V <name> <value> Change a non-partition label value. W Write (possibly modified) label out. The a through p commands will accept, for the <size> parameter, the nnn/nnn/nnn syntax used by SunOS 4.x format. (For those not familiar with this syntax, a/b/c means a cylinders + b tracks + c sectors. For example, if the disk has 16 tracks of 32 sectors, 3/4/5 means (3*16*32)+(4*32)+5=1669. This calculation always uses the nsect and ntrack values as printed by the L command; in particular, if they are zero (which they will initially be if -n is used), this syntax is not very useful. Some additional strings are accepted. For the <cylno> parameter, ``end-X'' (where X is a partition letter) indicates that the partition should start with the first free cylinder after partition X; ``start-X'' indicates that the partition should start at the same place as partition X. For the <size> parameter, ``end-X'' indicates that the partition should end at the same place as partition X (even if partition X ends partway through a cylinder); ``start-X'' indicates that the partition should end with the last cylinder before partition X; and ``size-X'' means that the partition's size should exactly match partition X's size. Note that sunlabel supports 16 partitions. SunOS supports only 8. Labels written by sunlabel, when partitions i through p are all set offset=0 size=0, are identical to Sun labels. If any of the ``extended'' partitions are nontrivial, information about them is tucked into some otherwise unused space in the Sun label format. The V command changes fields printed by the L command. For example, if the L command prints ascii: ST15230N cyl 5657 alt 2 hd 19 sec 78 rpm: 0 pcyl: 0 apc: 0 obs1: 0 obs2: 0 intrlv: 1 ncyl: 5657 acyl: 0 nhead: 19 nsect: 78 obs3: 0 obs4: 0 then V ncyl 6204 would set the ncyl value to 6204, or V ascii Seagate ST15230N cyl 5657 hd 19 sec varying would set the ascii-label string to that string. sunlabel performs very few consistency checks on the values you supply, and the ones it does perform never generate errors, only warnings. AUTHORS
der Mouse <mouse@rodents.montreal.qc.ca> BUGS
It may be that the space in the label where the information for the extended partitions is saved is used by SunOS. Not very many consistency checks are done on the V arguments, and those only produce warnings. NetBSD doesn't support 16 partitions in a Sun disk label yet. BSD
December 21, 2002 BSD
All times are GMT -4. The time now is 08:24 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy