ultra 10 boot warning---corrupt label


 
Thread Tools Search this Thread
Operating Systems Solaris ultra 10 boot warning---corrupt label
# 8  
Old 07-28-2008
I found the problem. The second HD which was configured previously with another filesystem, I created a newfs and the WARNING is now remove.

Case closed!
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

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

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

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

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

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

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

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

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

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

10. 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
Login or Register to Ask a Question
LILO(8) 						      System Manager's Manual							   LILO(8)

NAME
lilo - install boot loader SYNOPSIS
Main function: /sbin/lilo - install boot loader Auxiliary uses: /sbin/lilo -q - query map /sbin/lilo -R - set default command line for next reboot /sbin/lilo -I - inquire path name of current kernel /sbin/lilo {-u|-U} - uninstall lilo DESCRIPTION
lilo installs a boot loader that will be activated next time you boot. It has lots of options. -v Increase verbosity. Giving one or more -v options will make lilo more verbose. -q List the currently mapped files. lilo maintains a file, by default /boot/map, containing the name and location of the kernel(s) to boot. This option will list the names therein. -m map-file Use specified map file instead of the default. -C config-file lilo reads its instructions about what files to map from its config file, by default /etc/lilo.conf. This option can be used to specify a non-default config file. -d delay If you have specified several kernels, and press Shift at boot-time, the boot loader will present you with a choice of which system to boot. After a timeout period the first kernel in the list is booted. This option specifies the timeout delay in deciseconds. -D label Use the kernel with the given label, instead of the first one in the list, as the default kernel to boot. -r root-directory Before doing anything else, do a chroot to the indicated directory. Used for repairing a setup from a boot floppy. -t Test only. Do not really write a new boot sector or map file. Use together with -v to find out what lilo is about to do. -c Enable map compaction. This will merge read requests from adjacent sectors. Speeds up the booting (especially from floppy). -f disk-tab Specify disk geometry parameter file. (The default is /etc/disktab.) -i boot-sector Specify a file to be used as the new boot sector. (The default is /boot/boot.b.) -l Generate linear sector addresses instead of sector/head/cylinder addresses. -L Generate 32-bit Logical Block Addresses instead of C:H:S addresses, allowing access to all partitions on disks greater than 8.4Gb. -P {fix|ignore} Fix (or ignore) `corrupt' partition tables, i.e., partition tables with linear and sector/head/cylinder addresses that do not corre- spond. -s save-file When lilo overwrites the boot sector, it preserves the old contents in a file, by default /boot/boot.NNNN where NNNN depends on the device. This option specifies an alternate save file for the boot sector. (Or, together with the -u option, specifies from where to restore the boot sector.) -S save-file Normally, lilo will not overwrite an existing save file. This options says that overwriting is allowed. -u device-name Uninstall lilo, by copying the saved boot sector back. A time-stamp is checked. -U device-name Idem, but do not check the time-stamp. -R command line This option sets the default command for the boot loader the next time it executes. The boot loader will then erase this line: this is a once-only command. It is typically used in reboot scripts, just before calling `shutdown -r'. -I label The label of the running kernel can be found in the environment variable BOOT_IMAGE after startup. This command will print the cor- responding path name on stdout. -V Print version number. The above command line options correspond to the key words in the config file indicated below. -b bootdev boot=bootdev -c compact -d dsec delay=dsec -D label default=label -i bootsector install=bootsector -f file disktab=file -l linear -L lba32 -m mapfile map=mapfile -P fix fix-table -P ignore ignore-table -s file backup=file -S file force-backup=file -v verbose=level SEE ALSO
lilo.conf(5). The lilo distribution comes with very extensive documentation. AUTHOR
Werner Almesberger (almesber@bernina.ethz.ch). John Coffman (johninsd@san.rr.com) (lba32 extensions). 20 March 2000 LILO(8)