Changes between Version 6 and Version 7 of Rebooting Sun Hosts
- Timestamp:
- 04/13/06 16:06:46 (20 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Rebooting Sun Hosts
v6 v7 11 11 12 12 === If host has a front panel 'button' === 13 (ie. all SunBlades and all Ultras except for Ultra-1's) 14 then to reboot safely: 13 (ie. all SunBlades and all Ultras except for Ultra-1's) then to reboot safely: 15 14 16 Push and let go quickly the lit button on the front panel. The17 screen will go black. About a minute or two later, the screen will18 light up, a message about syncing the disks will be displayed and19 then the cpu box will be powered off.15 Push and let go quickly the lit button on the front panel. The 16 screen will go black. About a minute or two later, the screen will 17 light up, a message about syncing the disks will be displayed and 18 then the cpu box will be powered off. 20 19 21 After a moment, check that the light in or near the front panel22 button is off. Then push and let go quickly the button. The host23 will boot back up.20 After a moment, check that the light in or near the front panel 21 button is off. Then push and let go quickly the button. The host 22 will boot back up. 24 23 25 NOTE: Host lakme in Room 1325 has a hardware problem and this26 does not work on that host.27 NOTE: If the 'safe' reboot doesn't work, the last resort is28 to hold in the 'button' about 4 seconds or more until the29 cpu box powers off (light is out). If that fails, then30 unplug the cpu box.24 * NOTE: Host lakme in Room 1325 has a hardware problem and this 25 does not work on that host. 26 * NOTE: If the 'safe' reboot doesn't work, the last resort is 27 to hold in the 'button' about 4 seconds or more until the 28 cpu box powers off (light is out). If that fails, then 29 unplug the cpu box. 31 30 32 *See below for errors that occur when the 'safe' reboot isn't possible.*31 * See below for errors that occur when the 'safe' reboot isn't possible. 33 32 34 33 35 2. If host has no front panel 'button' (ie. Ultra-1 attila, isolde, lucia 36 SPARCtation-10 odyssey 37 SPARCstation-5 doncarlo ) 38 then to reboot safely: 39 34 === If host has no front panel 'button' === 35 (ie. Ultra-1: attila, isolde, lucia. 36 SPARCtation-10: odyssey. 37 SPARCstation-5: doncarlo) 38 Then to reboot safely: 39 {{{ 40 40 Hold down 'Stop' key and the 'a' key. This will display the okay prompt: 41 41 OK> … … 57 57 58 58 *See below for errors that occur when the 'safe' reboot isn't possible.* 59 60 59 }}} 61 60 == Is A Reboot Necessary? == 62 61 63 Most Sun hosts act as data disk servers, some also as home directory64 servers and others as mail, print, web, and software servers.62 * Most Sun hosts act as data disk servers, some also as home directory 63 servers and others as mail, print, web, and software servers. 65 64 66 As the Sun systems are interdependent, they are ideally always up and67 running with all disks mounted. Rebooting should be a last resort.65 * As the Sun systems are interdependent, they are ideally always up and 66 running with all disks mounted. Rebooting should be a last resort. 68 67 69 Below are guidelines on how to avoid a reboot/poweroff of a Sun host.70 See guidelines for doing a 'safe' reboot/poweroff above.68 * Below are guidelines on how to avoid a reboot/poweroff of a Sun host. 69 See guidelines for doing a 'safe' reboot/poweroff above. 71 70 72 How to avoid a reboot: 71 == How to avoid a reboot == 73 72 74 1.Keep a 'console' window open. All system error messages are73 * Keep a 'console' window open. All system error messages are 75 74 displayed in the console window. (In CDE's menu, select HOSTS --> 76 75 Terminal Console ) 77 76 78 2.Check the messages in the console window. If they include:77 * Check the messages in the console window. If they include: 79 78 ... server SOME_HOST not responding ... 80 79 then your host is likely just waiting on another host that is … … 83 82 can work without that remote host. 84 83 85 If the console messages include: 84 * If the console messages include: 85 {{{ 86 86 ... server SOME_HOST_X not responding ... 87 87 ... server SOME_HOST_Y not responding ... … … 89 89 then there is likely a network problem and rebooting will not help. 90 90 Get in touch with the system manager. 91 92 3.If your console session is hung or frozen and there are no91 }}} 92 * If your console session is hung or frozen and there are no 93 93 ... server SOME_HOST not responding ... 94 94 messages, then try to kill the session from another host: 95 {{{ 95 96 > ssh -l your_username your_hostname 96 97 > psallw | grep ksh … … 99 100 /usr/dt/bin/Xsession 100 101 > kill 9561 (PID# for your Xsession 'ksh' process) 101 102 102 }}} 103 103 == Likely Errors After 'Unsafe' Reboot/Power Off == 104 104 105 105 These occur when the 'safe' reboot/poweroff described above was 106 106 not possible. 107 107 {{{ 108 108 Disk .../dev/dsk/c0t0d0s0... not OKAY 109 109 … … 113 113 'fsck' on that disk. If no one is available to use the root 114 114 account, the disk and, possibly the host, will remain off line. 115 }}}
