Overview

An unclean shutdown will cause a blockpool verification to run when a reboot occurs. It is typically fixed automatically on reboot. The following shows the results of an unclean shutdown and clean reboot. If there's an unclean shutdown, the messages log will say unclean shutdown in the blockpool startup section. If it's a clean reboot, the unclean shutdown message will not exist in the messages log. 

 

---

Unclean Shutdown 

In System Diagnostics: scratch\collect\node1-collection\os-info\messages
On the system: /var/log/messages

 

The following output shows an example of an unclean shudown in a messages log. The system was unable to shutdown services cleanly. We see an abrupt restart which would indicate that the system was hard reset.

 

Unclean Shut

Mar 15 07:28:48 qtmdxiwalpd01 winbindd[3395]: [2009/03/15 07:28:48, 0] libads/kerberos.c:ads_kinit_password(228)

Mar 15 07:28:48 qtmdxiwalpd01 winbindd[3395]: kerberos_kinit_password

QTMDXIWALPD01$@CORP.AD.FMCNA.COM failed: Client not found in Kerberos database

Mar 15 07:46:53 qtmdxiwalpd01 kernel: [479081.731083] WARNING: pscsi_checker [scsi15:

id: 0 lun: 169]: application has not been responding over 5 minutes - check /proc/pscsi/iostat to see the cdbs and TMFs!

Mar 15 07:46:53 qtmdxiwalpd01 kernel: [479081.771245] WARNING: pscsi_checker [scsi15:

id: 0 lun: 172]: application has not been responding over 5 minutes - check /proc/pscsi/iostat to see the cdbs and TMFs!

Mar 15 08:21:56 qtmdxiwalpd01 syslogd 1.4.1: restart.

Mar 15 08:21:56 qtmdxiwalpd01 syslog: syslogd startup succeeded

 

Mar 15 08:21:56 qtmdxiwalpd01 kernel: klogd 1.4.1, log source = /proc/kmsg started.

Mar 15 08:21:56 qtmdxiwalpd01 kernel: [ 0.000000] Linux version 2.6.19-2smp

(jali@white-galaxy) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-3)) #1 SMP Tue Dec 2

18:14:01 PST 2008 

 

---

Clean Shutdown

The following output shows an example of a clean shudown. We can see service shutdowns completing successfully and the system "exiting on signal 15" and restarting.

 

Mar 9 14:57:47 qtmdxiwalpd01 ipmi: Stopping ipmi drivers:

Mar 9 14:57:47 qtmdxiwalpd01 ipmi: succeeded

Mar 9 14:57:47 qtmdxiwalpd01 ipmi: ESC[60G

Mar 9 14:57:47 qtmdxiwalpd01 ipmi:

Mar 9 14:57:47 qtmdxiwalpd01 rc: Stopping ipmi: succeeded

Mar 9 14:57:47 qtmdxiwalpd01 irqbalance: irqbalance shutdown succeeded

Mar 9 14:57:47 qtmdxiwalpd01 portmap: portmap shutdown succeeded

Mar 9 14:57:47 qtmdxiwalpd01 slpd: slpd shutdown succeeded

Mar 9 14:57:47 qtmdxiwalpd01 kernel: Kernel logging (proc) stopped.

Mar 9 14:57:47 qtmdxiwalpd01 kernel: Kernel log daemon terminating.

Mar 9 14:57:48 qtmdxiwalpd01 syslog: klogd shutdown succeeded

Mar 9 14:57:48 qtmdxiwalpd01 exiting on signal 15

Mar 9 14:59:47 qtmdxiwalpd01 syslogd 1.4.1: restart.

Mar 9 14:59:47 qtmdxiwalpd01 syslog: syslogd startup succeeded

Mar 9 14:59:47 qtmdxiwalpd01 kernel: klogd 1.4.1, log source = /proc/kmsg started.

Mar 9 14:59:47 qtmdxiwalpd01 kernel: [ 0.000000] Linux version 2.6.19-2smp

jali@white-galaxy) (gcc version 3.4.6 20060404 (Red Hat 3.4.6-3)) #1 SMP Thu Feb 28

08:14:50 PST 200

 

---

What's Next?

Determining If an Upgrade Was Successful >