Solved

SBS2010 Server Lockup

Posted on 2013-06-17
3
129 Views
Last Modified: 2014-10-22
Hi

Our server recently locked up. I could not access my server via remote desktop. I logged into my vsphere client and could view the server on console, however I could not log in.

I was forced to perform a STOP machine from the client.

On reboot, it performed a hard disk check.

I tried to establish when the problems started and noticed the following event and wanted to establish whether this may have caused the fault. We had four instances early saturday morning, but we could access the server ok. When the problems seemed to occur may have been later that evening. My primary concern is whether I have a problem with one of my disks? It is a RAID5 array.

We are unsure when the problems occurred.

- System

  - Provider

   [ Name]  Disk
 
  - EventID 51

   [ Qualifiers]  32772
 
   Level 3
 
   Task 0
 
   Keywords 0x80000000000000
 
  - TimeCreated

   [ SystemTime]  2013-06-15T06:04:00.366991600Z
 
   EventRecordID 1359569
 
   Channel System
 
   Computer SILCH021.silchester.local
 
   Security
 

- EventData

   \Device\Harddisk0\DR0
   030080000100000000000000330004802D0100009A0000C0000000000000000000000000000000009BE47E0800000000FFFFFFFF010000005800003000000000E8200A1242032040001010003C000000000000000000000028E88C2980FAFFFF0000000000000000E0682F2680FAFFFF00000000000000009A0000C00000000028000774234000080800000000000000000000000000000000000000000000000000000000000000


--------------------------------------------------------------------------------

Binary data:


In Words

0000: 00800003 00000001 00000000 80040033
0008: 0000012D C000009A 00000000 00000000
0010: 00000000 00000000 087EE49B 00000000
0018: FFFFFFFF 00000001 30000058 00000000
0020: 120A20E8 40200342 00101000 0000003C
0028: 00000000 00000000 298CE828 FFFFFA80
0030: 00000000 00000000 262F68E0 FFFFFA80
0038: 00000000 00000000 C000009A 00000000
0040: 74070028 08004023 00000008 00000000
0048: 00000000 00000000 00000000 00000000
0050: 00000000 00000000  


In Bytes

0000: 03 00 80 00 01 00 00 00   ..¿.....
0008: 00 00 00 00 33 00 04 80   ....3..¿
0010: 2D 01 00 00 9A 00 00 C0   -...¿..À
0018: 00 00 00 00 00 00 00 00   ........
0020: 00 00 00 00 00 00 00 00   ........
0028: 9B E4 7E 08 00 00 00 00   ¿ä~.....
0030: FF FF FF FF 01 00 00 00   ÿÿÿÿ....
0038: 58 00 00 30 00 00 00 00   X..0....
0040: E8 20 0A 12 42 03 20 40   è ..B. @
0048: 00 10 10 00 3C 00 00 00   ....<...
0050: 00 00 00 00 00 00 00 00   ........
0058: 28 E8 8C 29 80 FA FF FF   (è¿)¿úÿÿ
0060: 00 00 00 00 00 00 00 00   ........
0068: E0 68 2F 26 80 FA FF FF   àh/&¿úÿÿ
0070: 00 00 00 00 00 00 00 00   ........
0078: 9A 00 00 C0 00 00 00 00   ¿..À....
0080: 28 00 07 74 23 40 00 08   (..t#@..
0088: 08 00 00 00 00 00 00 00   ........
0090: 00 00 00 00 00 00 00 00   ........
0098: 00 00 00 00 00 00 00 00   ........
00a0: 00 00 00 00 00 00 00 00   ........
0
Comment
Question by:silchester
  • 2
3 Comments
 
LVL 21

Expert Comment

by:Haresh Nikumbh
ID: 39252688
0
 

Accepted Solution

by:
silchester earned 0 total points
ID: 39252710
The system did a check on reboot as I had to turn the image off instaed of a clean shutdown. I also noticed around the time of problem on the Vsphere logs.

Everything seems fine now. I am just concerned whether my disks are Ok. We have only had them for less than a year in RAID5.

Device naa.600605b00414a3a016f9f2dd22a59c69 performance has deteriorated
. I/O latency increased from average value of 6069 microseconds to 187611
microseconds.
warning
16/06/2013 20:01:18
c068.silchester.local

Device naa.600605b00414a3a016f9f2dd22a59c69 performance has deteriorated
. I/O latency increased from average value of 6032 microseconds to 181720
microseconds.
warning
15/06/2013 10:56:06
c068.silchester.local

Device naa.600605b00414a3a016f9f2dd22a59c69 performance has deteriorated
. I/O latency increased from average value of 6024 microseconds to 185623
microseconds.
warning
15/06/2013 09:05:21
c068.silchester.local

Device naa.600605b00414a3a016f9f2dd22a59c69 performance has deteriorated
. I/O latency increased from average value of 5985 microseconds to 211344
microseconds.
warning
14/06/2013 23:40:32
c068.silchester.local

Device naa.600605b00414a3a016f9f2dd22a59c69 performance has deteriorated
. I/O latency increased from average value of 5968 microseconds to 227362
microseconds.
warning
14/06/2013 17:28:46
c068.silchester.local

Device naa.600605b00414a3a016f9f2dd22a59c69 performance has deteriorated
. I/O latency increased from average value of 5961 microseconds to 184781
microseconds.
warning
14/06/2013 16:24:54
c068.silchester.local

Device naa.600605b00414a3a016f9f2dd22a59c69 performance has deteriorated
. I/O latency increased from average value of 5957 microseconds to 188051
microseconds.
warning
14/06/2013 15:55:44
c068.silchester.local

Device naa.600605b00414a3a016f9f2dd22a59c69 performance has deteriorated
. I/O latency increased from average value of 5927 microseconds to 254943
microseconds.
warning
14/06/2013 10:58:43
c068.silchester.local

Device naa.600605b00414a3a016f9f2dd22a59c69 performance has deteriorated
. I/O latency increased from average value of 5927 microseconds to 191528
microseconds.
warning
14/06/2013 10:58:25
c068.silchester.local

Device naa.600605b00414a3a016f9f2dd22a59c69 performance has deteriorated
. I/O latency increased from average value of 5921 microseconds to 188784
microseconds.
warning
14/06/2013 10:15:22
c068.silchester.local

Device naa.600605b00414a3a016f9f2dd22a59c69 performance has deteriorated
. I/O latency increased from average value of 5912 microseconds to 240810
microseconds.
warning
14/06/2013 08:55:40
c068.silchester.local

Device naa.600605b00414a3a016f9f2dd22a59c69 performance has deteriorated
. I/O latency increased from average value of 5909 microseconds to 183033
microseconds.
warning
14/06/2013 08:22:15
c068.silchester.local

Device naa.600605b00414a3a016f9f2dd22a59c69 performance has deteriorated
. I/O latency increased from average value of 5906 microseconds to 194683
microseconds.
warning
14/06/2013 07:58:31
c068.silchester.local

Device naa.600605b00414a3a016f9f2dd22a59c69 performance has deteriorated
. I/O latency increased from average value of 5899 microseconds to 179853
microseconds.
warning
14/06/2013 06:14:42
c068.silchester.local

Device naa.600605b00414a3a016f9f2dd22a59c69 performance has deteriorated
. I/O latency increased from average value of 5879 microseconds to 195501
microseconds.
warning
13/06/2013 22:59:38
c068.silchester.local

Device naa.600605b00414a3a016f9f2dd22a59c69 performance has deteriorated
. I/O latency increased from average value of 5878 microseconds to 177278
microseconds.
warning
13/06/2013 22:58:27
c068.silchester.local

Device naa.600605b00414a3a016f9f2dd22a59c69 performance has deteriorated
. I/O latency increased from average value of 5877 microseconds to 189262
microseconds.
warning
13/06/2013 22:57:20
c068.silchester.local

Device naa.600605b00414a3a016f9f2dd22a59c69 performance has deteriorated
. I/O latency increased from average value of 5850 microseconds to 190886
microseconds.
warning
13/06/2013 15:54:48
c068.silchester.local

Device naa.600605b00414a3a016f9f2dd22a59c69 performance has deteriorated
. I/O latency increased from average value of 5846 microseconds to 180887
microseconds.
warning
13/06/2013 14:41:43
c068.silchester.local

Device naa.600605b00414a3a016f9f2dd22a59c69 performance has deteriorated
. I/O latency increased from average value of 5843 microseconds to 189195
microseconds.
warning
13/06/2013 13:58:19
c068.silchester.local

Device naa.600605b00414a3a016f9f2dd22a59c69 performance has deteriorated
. I/O latency increased from average value of 5828 microseconds to 189977
microseconds.
warning
13/06/2013 10:20:41
c068.silchester.local

Device naa.600605b00414a3a016f9f2dd22a59c69 performance has deteriorated
. I/O latency increased from average value of 5826 microseconds to 185078
microseconds.
warning
13/06/2013 09:57:41
c068.silchester.local
0
 

Author Closing Comment

by:silchester
ID: 40396462
The problem did not appear to be what the expert commented on. No further comment was made so the original question was not properly answered.
You do not have an abandon question option so I had to accept.
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

In the event you manage a Small Business Server 2003, and you are audited for PCI compliance, there are several changes you must make in order to pass the audit. I can take no credit for discovering any of these fixes or workarounds, but there is no…
The articles for turning off the Client firewall policy on the internet are for SBS 2008 and don't really help for SBS 2011. They actually moved the Client firewall policy. In 2011, the client firewall policy has moved to the SBS computers conta…
This video discusses moving either the default database or any database to a new volume.
This video demonstrates how to create an example email signature rule for a department in a company using CodeTwo Exchange Rules. The signature will be inserted beneath users' latest emails in conversations and will be displayed in users' Sent Items…

758 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now