Jump to content
RESET Forums (homeservershow.com)

Troubleshoot reboot?


psykix
 Share

Recommended Posts

If I try to reboot my Gen8 which is running Server 2012 R2 Essentials from a RDC, then it invariably fails to reboot. Nothing appears to happen, and if I have an iLO remote console open then I can see that Windows is still on the lock screen. However, sending CTRL+ALT+Del to the sever does nothing.

 

I have to use the iLO remote console to issue a cold boot.

 

Any idea how to figure out what's preventing the reboot? Reboots did work reliably, but then suddenly stopped a week or so ago.

 

Cheers!

 


Also, I have used the instructions on here for the MicroSD boot.

 

I am using a brand new 8Gb MicroSD card (Sandisk) and I keep getting the following in the event logs :-

Log Name:      System
Source:        disk
Date:          09/07/2015 21:23:24
Event ID:      153
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      GEN8.DOMAIN.local
Description:
The IO operation at logical block address 0x767000 for Disk 6 (PDO name: \Device\00000044) was retried.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="disk" />
    <EventID Qualifiers="32772">153</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-07-09T20:23:24.494149600Z" />
    <EventRecordID>22139</EventRecordID>
    <Channel>System</Channel>
    <Computer>GEN8.DOMAIN.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>\Device\Harddisk6\DR6</Data>
    <Data>0x767000</Data>
    <Data>6</Data>
    <Data>\Device\00000044</Data>
    <Binary>0F01040004002C00000000009900048000000000000000000000000000000000000000000000000000000928</Binary>
  </EventData>
</Event>
Link to comment
Share on other sites

Disk 6 is the brand new MicroSD. I'm not saying it can't have issues, but it seems a bit odd. I would have thought that the disk was only used for reading.

Link to comment
Share on other sites

Nope, just have it set to be the boot device using the instructions in the Gen8 stickies thread. The OS is on an SSD in the ODD

Link to comment
Share on other sites

It enables you to boot off of the ODD SATA Port in AHCI Mode -- the process is outlined in the Gen8 Links stickie

Link to comment
Share on other sites

Okay, but the Event error is pointing to an error with that drive.  I would try replacing it.

Link to comment
Share on other sites

Well it is brand new, and StableBit Scanner reports no problems. Surface scan has a clean bill of health. After a reboot then the event logs stay clear. After a while though, then they begin to reoccur.

 

It's as though something suddenly decides to try to write to the MicroSD card or something, but I can't see that anything would need to write to it.

 

I'll have to do a bit more digging.

Link to comment
Share on other sites

I think I have narrowed down the disk errors.

 

It appears to be whenever it tries to do a Shadow Copy. See below :-

Log Name:      Application
Source:        VSS
Date:          12/07/2015 13:01:53
Event ID:      12289
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      GEN8.DOMAIN.local
Description:
Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{8f8a07b6-3baf-488b-ad20-b0e8d38d7314} - 00000000000001BC,0x0053c008,000000CE0A001370,0,000000CE0974A670,4096,[0]).  hr = 0x80820001, The bootfile is too small to support persistent snapshots.
. 

Operation:
   Processing EndPrepareSnapshots

Context:
   Execution Context: System Provider
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="VSS" />
    <EventID Qualifiers="0">12289</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-07-12T12:01:53.000000000Z" />
    <EventRecordID>12470</EventRecordID>
    <Channel>Application</Channel>
    <Computer>GEN8.DOMAIN.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>DeviceIoControl(\\?\Volume{8f8a07b6-3baf-488b-ad20-b0e8d38d7314} - 00000000000001BC,0x0053c008,000000CE0A001370,0,000000CE0974A670,4096,[0])</Data>
    <Data>0x80820001, The bootfile is too small to support persistent snapshots.
</Data>
    <Data>

Operation:
   Processing EndPrepareSnapshots

Context:
   Execution Context: System Provider</Data>
    <Binary>2D20436F64653A20494E434943484C4830303030303532312D2043616C6C3A2053505251534E504330303030303137342D205049443A202030303031333939362D205449443A202030303031343336302D20434D443A2020433A5C57696E646F77735C53797374656D33325C737663686F73742E657865202D6B2073777072762D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>
  </EventData>
</Event>
Log Name:      System
Source:        disk
Date:          12/07/2015 13:00:22
Event ID:      153
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      GEN8.DOMAIN.local
Description:
The IO operation at logical block address 0x800 for Disk 6 (PDO name: \Device\00000045) was retried.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="disk" />
    <EventID Qualifiers="32772">153</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-07-12T12:00:22.014805400Z" />
    <EventRecordID>24301</EventRecordID>
    <Channel>System</Channel>
    <Computer>GEN8.DOMAIN.local</Computer>
    <Security />
  </System>
  <EventData>
    <Data>\Device\Harddisk6\DR6</Data>
    <Data>0x800</Data>
    <Data>6</Data>
    <Data>\Device\00000045</Data>
    <Binary>0F01040004002C00000000009900048000000000000000000000000000000000000000000000000000000928</Binary>
  </EventData>
</Event>

Can I fix this or disable VSS? The VSS service is set to manual, so what triggers it?

 

Anyone else using the MicroSD boot method that has similar issues? I presume it's not doing any harm, but I would rather not have any disk errors in the event logs in case I miss something that is actually important!

 

I did try using my extra PCI SATA card to boot my OS drive from, but although it boots up, soon after hitting the logon screen, it blue screens. So I'm back to the MicroSD boot method!

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...