Sponsored Content
Full Discussion: Sun Fire won't boot anymore
Operating Systems Solaris Sun Fire won't boot anymore Post 302280210 by incredible on Monday 26th of January 2009 09:41:08 AM
Old 01-26-2009
use anti-static mat and wrist before you open up the H/W.
check wher you find the memory module, use the small release-catch to release the memory and re-seat them in again into the slots

to halt the system to ok> prompt, use the Stop+A keys on the SUN keyboard
 

10 More Discussions You Might Find Interesting

1. Slackware

After installing linux cannot boot PC anymore?

After installing linux (slackware) my (experimental) computer can't boot anymore. When I start the pc it says: "There was an error during linux startup" (or something like that, it was written in my language and I'm a bad translator) And after that my computer doesn't do a thing anymore. I... (4 Replies)
Discussion started by: RellioN
4 Replies

2. AIX

won't mount /usr...won't boot fully

Hello: NOOB here. I attempted to use smit mkcd. Failed on first attempt, not enough space. 2nd attempt tried to place iso on /usr, not enough space there. Cleanup ran for about 5 minutes after aborting. Now AIX won't boot. LCD display on 7029-6E3 says: 0517 MOUNT /USR. Attempted to boot from CD... (11 Replies)
Discussion started by: bbird
11 Replies

3. Solaris

Sun Fire 280R Sun Solaris CRT/Monitor requirements

I am new to Sun. I brought Sun Fire 280R to practice UNIX. What are the requirements for the monitor/CRT? Will it burn out old non-Sun CRTs? Does it need LCD monitor? Thanks. (3 Replies)
Discussion started by: bramptonmt
3 Replies

4. Solaris

Error while trying to boot from cdrom on Sun Fire T2000

Hi Guyz, I recently downloaded sol-10-u6-ga1-sparc-dvd.iso from Sun. I burned the disk as cd .iso. When trying to boot at the ok> boot cdrom i get the following error: ----------------------------------------------------------------------- Boot device:... (2 Replies)
Discussion started by: Mwamba
2 Replies

5. Solaris

Sun Sparc Ultra 4 won't boot - disk errors

Hi all. I am seeing in one of our less-used servers that it crashed and now won't restart. I get the message 'continue with normal startup or boot into maintenance mode'. I go into maintenance and run fsck on /usr0 (mentioned in error at restart) it then reboots but goes right back to... (3 Replies)
Discussion started by: jamie_collins
3 Replies

6. UNIX for Dummies Questions & Answers

SUN Ultra 10 won't boot - Help Please

Folks; My SUN Ultra 10 5.9 won't boot. It only stops after counting the memory on the white screen then hangs there with nothing. even the power button won't take it down from there, i had to unplug it then re-plug it again. i inserted a disk with Solaris 9 iso trying to rebuild it but nothing... (1 Reply)
Discussion started by: Katkota
1 Replies

7. UNIX for Advanced & Expert Users

pkill won't work on firefox anymore

Can someone tell me why pkill won't work on firefox anymore? (11 Replies)
Discussion started by: cokedude
11 Replies

8. Solaris

Sun-Fire V440 boot disk issue

Hi, I have Sun Fire V440. Boot disks are mirrored. system crashed and it's not coming up. Error message is Insufficient metadevice database replicas located. Use Metadb to delete databases which are broken. Boot disks are mirrored and other disks are ZFS configuration. Please... (2 Replies)
Discussion started by: samnyc
2 Replies

9. Solaris

Sun Fire 480 - devfsadm -C not working after replacing one of the boot disks

Our SunFire 480 - one of the boot disks failed. It is mirrored with VxVm. I followed the exact steps that is detailed in the veritas and sun guides (I can not post the URL since I don't have 5 posts yet.) After removing the failed disk, I ran devfsadm -C -c disk and it still shows the device... (7 Replies)
Discussion started by: jtamminen
7 Replies

10. What is on Your Mind?

They won't need so many sys admins anymore

Nice eye catching title huh ;) I got laid off along with 55000 others from HP worldwide have been expecting this for some time and now it's finally my turn. Most of the folks I know get laid off at around this age of 40+ so do take note. Ideas that ran thru my head this last few weeks:... (16 Replies)
Discussion started by: sparcguy
16 Replies
HALT(8) 						Linux System Administrator's Manual						   HALT(8)

NAME
halt, reboot, poweroff - stop the system. SYNOPSIS
/sbin/halt [-n] [-w] [-d] [-f] [-i] [-p] [-h] /sbin/reboot [-n] [-w] [-d] [-f] [-i] /sbin/poweroff [-n] [-w] [-d] [-f] [-i] [-h] DESCRIPTION
halt notes that the system is being brought down in the file /var/log/wtmp, and then either tells the kernel to halt, reboot or power-off the system. If halt or reboot is called when the system is not in runlevel 0 or 6, in other words when it's running normally, shutdown will be invoked instead (with the -h or -r flag). For more info see the shutdown(8) manpage. The rest of this manpage describes the behaviour in runlevels 0 and 6, that is when the systems shutdown scripts are being run. OPTIONS
-n Don't sync before reboot or halt. Note that the kernel and storage drivers may still sync. This implies -d. -w Don't actually reboot or halt but only write the wtmp record (in the /var/log/wtmp file). -d Don't write the wtmp record. -f Force halt or reboot, don't call shutdown(8). -i Shut down all network interfaces just before halt or reboot. -h Put all hard drives on the system in stand-by mode just before halt or power-off. -p When halting the system, switch off the power. This is the default when halt is called as poweroff. DIAGNOSTICS
If you're not the superuser, you will get the message `must be superuser'. NOTES
Under older sysvinit releases , reboot and halt should never be called directly. From release 2.74 on halt and reboot invoke shutdown(8) if the system is not in runlevel 0 or 6. This means that if halt or reboot cannot find out the current runlevel (for example, when /var/run/utmp hasn't been initialized correctly) shutdown will be called, which might not be what you want. Use the -f flag if you want to do a hard halt or reboot. The -h flag puts all hard disks in standby mode just before halt or power-off. Right now this is only implemented for IDE drives. A side effect of putting the drive in stand-by mode is that the write cache on the disk is flushed. This is important for IDE drives, since the kernel doesn't flush the write cache itself before power-off. The halt program uses /proc/ide/hd* to find all IDE disk devices, which means that /proc needs to be mounted when halt or poweroff is called or the -h switch will do nothing. AUTHOR
Miquel van Smoorenburg, miquels@cistron.nl SEE ALSO
shutdown(8), init(8) Nov 6, 2001 HALT(8)
All times are GMT -4. The time now is 01:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy