sfcredfox
Patron
- Joined
- Aug 26, 2014
- Messages
- 340
Greetings Experts,
I am looking for information on logs and how to determine if my last shutdown was a proper one.
Question: What specific lines would one find in the logs (which log?) that would indicate that the shutdown was a proper one? Will I be able to tell whether an entry is missing or by an entry being present that the shutdown was clean or not?
Situation: I had a 15 min. power failure today, which kicked off a UPS shutdown. My management server initiated a shutdown routine that powers down VM's, ESX hosts, the FreeNAS server, and other equipment in a rack.
I have been searching the forums and google to find log indicators of a clean vs. dirty shutdown. Through checking logs from the UPS (mind you that the UPS is not directly connected/managed by FreeNAS), it physically cut output power to the rack at 1106AM. The last log in /var/logs/messages is at 1101AM before switching over to the boot up logs. You can see the timeouts where FreeNAS looses its iSCSI connections as the ESX hosts shutdown and FreeNAS can't talk to IXsystems. There are no other helpful messages. The shutdown of FreeNAS is initiated by the management host using putty (plink) to log in as root, and delievering a 'shutdown -p now'
From what I can tell (I don't have good experience with FreeBSD logs), it doesn't look like any death messages during boot. Any thoughts/insights would be helpful.
FreeNAS 9.3-Stable 64-bit
I am looking for information on logs and how to determine if my last shutdown was a proper one.
Question: What specific lines would one find in the logs (which log?) that would indicate that the shutdown was a proper one? Will I be able to tell whether an entry is missing or by an entry being present that the shutdown was clean or not?
Situation: I had a 15 min. power failure today, which kicked off a UPS shutdown. My management server initiated a shutdown routine that powers down VM's, ESX hosts, the FreeNAS server, and other equipment in a rack.
I have been searching the forums and google to find log indicators of a clean vs. dirty shutdown. Through checking logs from the UPS (mind you that the UPS is not directly connected/managed by FreeNAS), it physically cut output power to the rack at 1106AM. The last log in /var/logs/messages is at 1101AM before switching over to the boot up logs. You can see the timeouts where FreeNAS looses its iSCSI connections as the ESX hosts shutdown and FreeNAS can't talk to IXsystems. There are no other helpful messages. The shutdown of FreeNAS is initiated by the management host using putty (plink) to log in as root, and delievering a 'shutdown -p now'
From what I can tell (I don't have good experience with FreeBSD logs), it doesn't look like any death messages during boot. Any thoughts/insights would be helpful.
FreeNAS 9.3-Stable 64-bit
FreeNAS Platform:
SuperMicro 826 (8XDTN+)
(x2) Intel(R) Xeon(R) CPU E5200 @ 2.27GHz
72GB RAM ECC (Always!)
APC3000 UPS (Always!)
SuperMicro 826 (8XDTN+)
(x2) Intel(R) Xeon(R) CPU E5200 @ 2.27GHz
72GB RAM ECC (Always!)
APC3000 UPS (Always!)
Intel Pro 1000 (integrated) for CIFS
Two Intel Pro 1000 PT/MT Dual Port Card (Four total ports for iSCSI)
Two SLOGS (one for each iSCSI pool) - Intel 3500 SSD
IBM M1015 (IT Mode) HBA (Port 0) -> BPN-SAS2-826EL1 (12 port backplane with expander)
IBM M1015 (IT Mode) HBA (Port 0) -> SFF-8088 connected -> HP MSA70 3G 25 bay drive enclosure
HP SAS HBA (Port 0) -> SFF-8088 connected -> HP DS2700 6G 25 bay drive enclosure
Two Intel Pro 1000 PT/MT Dual Port Card (Four total ports for iSCSI)
Two SLOGS (one for each iSCSI pool) - Intel 3500 SSD
IBM M1015 (IT Mode) HBA (Port 0) -> BPN-SAS2-826EL1 (12 port backplane with expander)
IBM M1015 (IT Mode) HBA (Port 0) -> SFF-8088 connected -> HP MSA70 3G 25 bay drive enclosure
HP SAS HBA (Port 0) -> SFF-8088 connected -> HP DS2700 6G 25 bay drive enclosure
Pool1 (VM Datastore) -> 24x 3G 146GB 10K SAS into 12 vDev Mirrors
Pool2 (VM Datastore) -> 12x 6G 300GB 10K SAS into 6 vDev Mirrors
Pool3 (Media Storage) -> 8x 3G 2TB 7200 SATA into 1vDev[Z2]
Pool2 (VM Datastore) -> 12x 6G 300GB 10K SAS into 6 vDev Mirrors
Pool3 (Media Storage) -> 8x 3G 2TB 7200 SATA into 1vDev[Z2]
Network Infrastructure:
Cisco SG200-26 (26 Port Gigabit Switch)
Four separate vLANs/subnets for iSCSI
Cisco SG200-26 (26 Port Gigabit Switch)
Four separate vLANs/subnets for iSCSI
- em2 - x.x.101.7/24
- em3 - x.x.102.7/24
- em0 - x.x.103.7/24
- em1 - x.x.104.7/24
- itb - x.x.0.7/24