Sponsored Content
Operating Systems Solaris ultra 10 boot warning---corrupt label Post 302218188 by itik on Thursday 24th of July 2008 03:12:07 PM
Old 07-24-2008
Sorry, it didn't work.

-format
-label
y
-q
-format
-q

reboot

During boot, it still give the warning.

Any more idea? Thanks.
 

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
REBOOT(8)						    BSD System Manager's Manual 						 REBOOT(8)

NAME
reboot, halt, fastboot, fasthalt -- stopping and restarting the system SYNOPSIS
halt [-lnpq] [-k kernel] reboot [-dlnpq] [-k kernel] fasthalt [-lnpq] [-k kernel] fastboot [-dlnpq] [-k kernel] DESCRIPTION
The halt and reboot utilities flush the file system cache to disk, send all running processes a SIGTERM (and subsequently a SIGKILL) and, respectively, halt or restart the system. The action is logged, including entering a shutdown record into the user accounting database. The options are as follows: -d The system is requested to create a crash dump. This option is supported only when rebooting, and it has no effect unless a dump device has previously been specified with dumpon(8). -k kernel Boot the specified kernel on the next system boot. If the kernel boots successfully, the default kernel will be booted on successive boots, this is a one-shot option. If the boot fails, the system will continue attempting to boot kernel until the boot process is interrupted and a valid kernel booted. This may change in the future. -l The halt or reboot is not logged to the system log. This option is intended for applications such as shutdown(8), that call reboot or halt and log this themselves. -n The file system cache is not flushed. This option should probably not be used. -p The system will turn off the power if it can. If the power down action fails, the system will halt or reboot normally, depending on whether halt or reboot was called. -q The system is halted or restarted quickly and ungracefully, and only the flushing of the file system cache is performed (if the -n option is not specified). This option should probably not be used. The fasthalt and fastboot utilities are nothing more than aliases for the halt and reboot utilities. Normally, the shutdown(8) utility is used when the system needs to be halted or restarted, giving users advance warning of their impending doom and cleanly terminating specific programs. SEE ALSO
getutxent(3), boot(8), dumpon(8), nextboot(8), savecore(8), shutdown(8), sync(8) HISTORY
A reboot utility appeared in Version 6 AT&T UNIX. BSD
October 11, 2010 BSD
All times are GMT -4. The time now is 09:42 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy