Machine reboots on it's own

As per http://discussions.apple.com/thread.jspa?messageID=3113705
I have just started having this problem.
I think it is when it is going to sleep but it is happening heaps. I have not installed any new software or and new hardware and also if I hit command spacebar or go and search the search is not opening.
I am going to try and run disk repair now, but any other ideas will be greatly appreciated.
Thanks in advance

Interesting. I will have to try that if Samsung cannot find anything. This is going to be a VERY long troubleshooting effort. However, as I stated above, the apps I loaded are completely "normal" apps (I.e. - Facebook, eBay, etc.). How can I be the only one having this issue when thousands of other people use these apps?
Someone else on another forum mentioned that it could possible be a bad ROM update from the cloud. Is that possible? I update it EVERY time is crashes so I doubt that each time it was a bad download.
Also, if it was bad, don't you think it would have crashed as soon as it was installed? This "crash" happens a week or so later...strange.

Similar Messages

My ipad freezes, reboots on its own and when I try to restore the machine reboots before the process ends

Just bought this ipad in June 2013 and then all of a sudden about two weeks ago, I discovered the machine reboots on its own and would only be active for less than 2 minutes. I check the auto-lock assigned minutes and it was set on 15 minutes even at this, it will still go off after less than 2 minutes. I then checked on some of the suggestions on the net for a similar problem and resolved to pressing and holding the sleep/wake button simultaneously with the Home button to force a reboot. Even at this no change. Then I tried connecting the machine to a PC logging on to the itunes to do a backup and restore but the machine will not stay long enough to complete the procedure before rebooting on its own. Any help?

Try here:
iOS: Not responding or does not turn on

Satellite A135 laptop reboots on it's own following normal shutdown

My Satellite A-135 has begin rebooting on it's own after a normal shutdown. Running Vista with 1 GB ram, use Firefox 3.6 browser and all programs, Windows updates, anti virus, anti malware, etc. are kept up to date. I routinely run anti malware and Avira anti virus scans and keep my registry and temp files, etc. clean with CC Cleaner. Use File Hippo and CNET Techtracker to keep aware of new software updates. Also use Win Patrol to monitor what programs and processes are running so I don't think I have a malware or virus problem. haven't added any hardware or software recently. Laptop sits on a cooling fan pad so overheating is not a problem. I can turn it off by removing the battery or by pushing the 'off' button (off button results in a safe mode screen the next time I turn the computer on). Other than this new, aggravating problem the computer runs perfectly. I bought this laptop new a few years ago and am the only user. It has not been dropped or otherwise abused so I'm at at loss as how this happened...unless it's some kind of hardware failure. I haven't done a system restore to see if that helps and will await some expert opinions before doing anything. Any good solution from someone who's solved the same problem will be greatly appreciated.

You might want to try a power reset and setting the defaults in the BIOS.
Turn off computer. Unplug AC adapter and remove the battery. Press and hold
down the power button for 30 seconds.
Put battery back in, Plug Charger back in.
Power on the computer and hold down F2 to enter the BIOS. Load BIOS defaults by
pressing F9 then F10 to save changes.

Solaris machine rebooted when displaying kern error.

Solaris machine rebooted when displaying kern error.
The following info can be found in system log. What is thje problem?
Thanks!
Jun 14 13:47:44 nsclfmaz1-01 unix: [ID 836849 kern.notice]
Jun 14 13:47:44 nsclfmaz1-01 ^Mpanic[cpu21]/thread=2a100a9fcc0:
Jun 14 13:47:44 nsclfmaz1-01 unix: [ID 799565 kern.notice] BAD TRAP: type=34 rp=2a100a9f980 addr=300018c200b mmu_fsr=0
Jun 14 13:47:44 nsclfmaz1-01 unix: [ID 100000 kern.notice]
Jun 14 13:47:44 nsclfmaz1-01 unix: [ID 839527 kern.notice] sched:
Jun 14 13:47:44 nsclfmaz1-01 unix: [ID 123557 kern.notice] alignment error:
Jun 14 13:47:44 nsclfmaz1-01 unix: [ID 381800 kern.notice] addr=0x300018c200b
Jun 14 13:47:44 nsclfmaz1-01 unix: [ID 101969 kern.notice] pid=0, pc=0x1051ec8, sp=0x2a100a9f221, tstate=0x80001604, context=0x0
Jun 14 13:47:44 nsclfmaz1-01 unix: [ID 743441 kern.notice] g1-g7: 1051fa4, d3a1da, 300018c2508, 6ad0, 300018c2000, 16, 2a100a9fcc0
Jun 14 13:47:44 nsclfmaz1-01 unix: [ID 100000 kern.notice]
Jun 14 13:47:44 nsclfmaz1-01 genunix: [ID 723222 kern.notice] 000002a100a9f6a0 unix:die+9c (34, 2a100a9f980, 300018c200b, 0, 2a100a9f760, c1e00000)
Jun 14 13:47:44 nsclfmaz1-01 genunix: [ID 179002 kern.notice] %l0-3: 00000000c0800000 0000000000000034 0000000000000000 00000300018a0920
Jun 14 13:47:44 nsclfmaz1-01 %l4-7: 0000000000003fff 000002a100a9f6f8 7feffffe00000000 0000000001076000
Jun 14 13:47:44 nsclfmaz1-01 genunix: [ID 723222 kern.notice] 000002a100a9f780 unix:trap+690 (2a100a9f980, 10009, 0, 800009, 0, 2a100a9fcc0)
Jun 14 13:47:44 nsclfmaz1-01 genunix: [ID 179002 kern.notice] %l0-3: 0000000000000000 00000000018364c0 0000000000000034 0000000000000000
Jun 14 13:47:44 nsclfmaz1-01 %l4-7: 0000000000000000 000000000000001f 0000000000000002 0000000000010200
Jun 14 13:47:44 nsclfmaz1-01 genunix: [ID 723222 kern.notice] 000002a100a9f8d0 unix:ktl0+48 (300018c2000, 15, 300018c2000, 22f, 1053b98, 1813400)
Jun 14 13:47:44 nsclfmaz1-01 genunix: [ID 179002 kern.notice] %l0-3: 0000000000000005 0000000000001400 0000000080001604 000000000101aa04
Jun 14 13:47:44 nsclfmaz1-01 %l4-7: 0000060002d86500 0000000000000000 0000000000000002 000002a100a9f980
Jun 14 13:47:44 nsclfmaz1-01 genunix: [ID 723222 kern.notice] 000002a100a9fa20 unix:idle+88 (1813400, 0, 300018c2000, fffffffffffffffd, e, 1812000)
Jun 14 13:47:44 nsclfmaz1-01 genunix: [ID 179002 kern.notice] %l0-3: 0000060002dfadb0 000000000000000b 0000000000000000 ffffffffffffffff
Jun 14 13:47:44 nsclfmaz1-01 %l4-7: 0000060002dfadb0 ffffffffffffffff 0000000001843dd8 0000000001053b98
Jun 14 13:47:44 nsclfmaz1-01 unix: [ID 100000 kern.notice]
Jun 14 13:47:44 nsclfmaz1-01 genunix: [ID 672855 kern.notice] syncing file systems...
Jun 14 13:47:45 nsclfmaz1-01 genunix: [ID 904073 kern.notice] done
Jun 14 13:47:46 nsclfmaz1-01 genunix: [ID 111219 kern.notice] dumping to /dev/md/dsk/d20, offset 860749824, content: kernel
Jun 14 13:50:27 nsclfmaz1-01 genunix: [ID 409368 kern.notice] ^M100% done: 246978 pages dumped, compression ratio 5.07,
Jun 14 13:50:27 nsclfmaz1-01 genunix: [ID 851671 kern.notice] dump succeeded
Jun 14 13:51:19 nsclfmaz1-01 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.10 Version Generic_118833-36 64-bit
Jun 14 13:51:19 nsclfmaz1-01 genunix: [ID 172907 kern.notice] Copyright 1983-2006 Sun Microsystems, Inc. All rights reserved.

Hi.
It's strange for me this difference:
Jun 14 13:51:19 nsclfmaz1-01 genunix: [ID 540533 kern.notice] ^MSunOS Release 5.10 Version Generic_118833-36 64-bit
Jun 14 13:51:19 nsclfmaz1-01 genunix: [ID 172907 kern.notice] Copyright 1983-2006 Sun Microsystems, Inc. All rights reserved.
Kernel version: SunOS 5.10 Generic_*147440-12*
It's very many reason that can cause this type of Trap. ( CD-rom version, OBP version, FC-problem - that can be found on support.oracle.com just to click... )
Part of this already fixed via patch.
Core and unix files can help analyse reason of it. Crash Analysis tool - tool that can help.
But even you close one problem, you can steel another. It's reason for install recommended patches.
Analyze system state before this problem - can help test that problem was resolved.
( Hostid; Kernel architecture; Hostname - generaly not provide any usefull information... It's more usefull - what real hardware system (M5000 ; v240 etc ... What changed before, connected hardware etc).
Regards.

Service Template: Automatic Machine Rebooting and Script Restarting via Exit Code in Script Application

Hello,
My question is on Script Applications in
Service Templates:
In VM Templates, in the Application Configuration tab, one can add a Script Application. This can be a PowerShell script, a batch script, etc.
For each Script Application, it is possible (via the Advanced options) to make the
machine reboot when the script exits with one of three
exit codes: 1641, 3010 and 3011.
Problem:
For PowerShell or PS scripts, if I use ‘exit 3010’, the machine should reboot but it doesn’t…
Bad workaround:
Use a batch script which calls the PS script. Then, exit out of the batch script using ‘exit $LASTEXITCODE’. This works. The machine reboots.
I can’t use the workaround. Is there a way to do this using just the PS script?
-Rohan.

In fact yes.
You actually want SCVMM to orchestrate the reboot by sending the proper exit code. Otherwise SCVMM gets all weird about things.
It is in the advanced settings for the script and / or command.
You need to make sure that your script tosses the 3011 or 3010 on exit.
I do it with the 3011:
# Exit 3011
[Environment]::Exit(“3011”)
In the XML you will find this:
<vmmst:RebootExitCodeRegex>{1641}|{3010}|{3011}</vmmst:RebootExitCodeRegex>
But you do not want to enable restarting the script on each reboot or you will find yourself in a loop.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.

My Ipad keeps rebooting itself on its own

My Ipad 3 just started rebooting itself on its own. I had the computer powered off and locked and then turned it on. It came on and then within 30 seconds shut itself down, only to reboot itself without me touching it. I am using 7.1.1, I am using AT &T as the carrier.
I have tried to reboot it holding down the on/off button and the home button at the same time as someone suggested that.

I Must be missing the significance of the computer is this discussion.
You could try restoring the device with iTunes on your computer.
Use iTunes to restore your iOS device to factory settings - Apple Support

Windows 8.0 Volume License machines reboot and windows 8.1 is installed??

We are a small private university with 484 computers running Windows 8.0 with MAK key.
This week we have had 2 Windows 8.0 computers spontaneously upgrade to Windows 8.1.
Since we do have a windows 8.1 MAK key all we had to do was enter the correct key and the computers were fine but everything I am reading about Volume Licensing says that this is not an upgrade path for Windows 8.1.
Is Microsoft pushing out Windows 8.1 slowly to volume licensed computers on Windows 8.0, or is this just some sort of anomaly that may happen occasionally.
One of our operators reported that the usual blue banner prompting upgrade appeared the day before but did not have an option on the banner to deny the upgrade. The next morning when she booted the computer, Windows 8.1 installed and we had to enter
the 8.1 MAK key and all appears to be well.
This is not really a complaint, just that we were VERY surprised when it happened, hoping it was not some sort of hack by a third party.
Jim Smith[REMOVED]
Lubbock Christian University
Technology Services
[removed]

Hi,
I don't know how useful this information will be for that many machines. This was also observed on 8.1 Pro, not Enterprise, but here is what I found while doing multiple different upgrades... just so I could figure out how to stop them...
Windows Update KB2973544 triggers Win 8.1 to automatically install.
http://support.microsoft.com/kb/2973544
In addition, KB3008273 appeared in Nov. 2014, which is also related to the automatic installation of Win 8.1... It actually replaces KB2973544.
http://support.microsoft.com/kb/3008273
Windows Update KB2871389 makes Win 8.1 available in the Store, and is a prerequisite for KB2973544 and\or KB3008273. You might uninstall it also.
https://support.microsoft.com/kb/2871389/en-us
I have found that the installation of KB2973544 and\or KB3008273 create Scheduled Tasks in Task Scheduler under *** Microsoft \ Windows \Setup***
They are...** 8.1 Auto Install Ping** and **8.1 Auto Install V2**. They are scheduled for 8pm Daily.
I clicked on both and selected "RUN", as I didn't want to wait several hours to see what happened... A download started immediately.
After downloading for about an hour, I restarted the machine to see what would happen... The download resumed quickly after the restart.
After the download started again, there were two more Scheduled Tasks added to the same location....   **Windows AutoUpdate Setup Resume Task**... which was running, and
**Windows AutoUpdate Setup Store Resume Task**... which is *Ready*, but has NEVER run.      There was a Service *Modern Setup Host* running in Taskmanager.
***I have found that the only way to stop the installation of Win 8.1 once the Scheculed Task ....   **Windows AutoUpdate Setup Resume Task** is indicating "At Logon" for it's Trigger,
is to end all the tasks showing, starting with that one, and then the ** 8.1 Auto Install Ping** and **8.1 Auto Install V2**.
After Ending the tasks Delete them...
After deleting the Tasks, I had to go to C:\ $Windows.~BT, which is a Hidden File, and delete anything that has a recent date... especially the .esd file (Install.esd) of 2.67GB..
I deleted anything that was newer than one week. You could probably delete everything inside the *Sources*, *Support*, and *Drivers* folders...
Also uninstall the mentioned KB's, starting with the newest, and doing the KB2871389 last, as it requires a reboot.
Any attempt to reboot the machine before doing this results in the installation of Win 8.1 starting...
If you were to End the tasks and disable or delete them while the **Windows AutoUpdate Setup Resume Task** is still showing a
Date and Time for it's trigger, deleting the $Windows.~BT files may not be necessary.
The biggest issue with this process is that you may be denied access to the $Windows.~BT folder. If that is the case, you will need to take Ownership of it.
If you disable and delete the Scheduled Tasks, and uninstall the previously mentioned KB's shortly after selecting *Remind Me Later*
THE FIRST TIME, the process will be stopped, and it won't be necessary to delete anything in the $Windows.~BT folder.
You should have about 24 hours to do this.
After uninstalling the KB's and deleting the scheduled tasks, a new scheduled task has appeared.
It is *Pre-Staged GDR Notification*, and is scheduled to run at *8PM of Every Thursday of Every Week*. My guess was that this is to remind you to install the Win 8.1 Update.
It actually causes another task to be created... *Windows Upgrade Notification Task*... It runs at the *Log On of Any User*
I couldn't get this task to show a notification. The task ran when I did it manually, but generated an error message in the log... *Specified Module Could Not Be Found (0x8007007E) Windows Upgrade Notification*
This is most likely because the KB's have been uninstalled.
I'm sure they can be disabled as well, if you want to stop\prevent the reminders.
I know that once Win 8.1 Update actually installs, those scheduled tasks no longer exist. In fact, the entire SETUP folder disappears.

ActionTec router reboots on it's own?

I originally posted this on Aug 4, but it seems that a whole bunch of posts from that day were lost in the maintenance that night so here goes again! My MI424WR Rev I router several times a day just shuts down and reboots. When it's finished rebooting everything is just fine. I noticed it when I was streaming radio on computer and it would just shut off. I looked at the router and saw that it was off, and then started going through it's booting...red power light, then green along with the rest of the green lights. Since my original post I called Verizon and explained what was happening. I went through all the reboots and shut downs that you can do with the equipment...rebooting the ONT, powering down the router, etc. Still happening at what seems like totally random times. They sent me a new router and I hooked it up today and so far I did have one reboot. Any suggestions as to what I should look at here? I like to troubleshoot and get things right before I call tech support. I'll have to keep watching and see if there is any pattern to these reboots. Maybe today's reboot was just a fluke? Have FIOS here for quite a few years and it's been trouble free up until now. The problem does not seem to affect neither the TV nor the digital voice service. BTW, my main connections to the router are Ethernet connections.

Very similar symptoms. here's my commiseration. I'm undecided as to how to proceed.
I had a Rev F router that a very friendly, competent Vz tech left for me after a visit for an unrelated problem. It's worked fine for several (2+) years. A few months ago I had a day filled with FiOS internet access problems. Phone was fine. TV was ok, except no VOD on any of the STBs. After powering down everything in the house from the ONT (removed the battery too!) to the router, STBs, and PCs multiple times and restarting from the outside inward, I gave up and called Vz support. The (exceptionally clueless?) tech put me through the usual power down/up drill again twice and then declared my router needed replacement. C'est la vie. While I disagreed, I knew arguing was senseless. She put in the order for a replacement to be shipped. That was a Thursday night. I was told it wouldn't arrive until Monday or Tuesday because of the weekend. Since I work at home 3 days a week (M-W-F, lucky me) it would mean making an hour drive into my office(unlucky me) until it arrived. Friday morning before heading out, I crossed my fingers and tried connecting. It worked (again, lucky me.) No problems resurfaced that day, or through the weekend - even VOD came back. When the replacement router arrived Tuesday, it was a new Rev I. While happy, I was reluctant to install it and lived with the old one for another week. I gave in and swapped them, sending back the old one.
As I mentioned, I work from home 3 days a week. I follow the same "work from home" routine on those mornings. 1) reboot my ethernet-wired PC; 2) go get my coffee in the kitchen and let the dog out; 3) about 10 minutes later I start my VPN; 4) I start a Remote Desktop session to my office machine. Up to here, that's been the same for years and aside form that one terrible day, there's been no problem worth mentioning. After connecting the Rev. I all was good as well. However, for the last 2 weeks, when I go through that routine and reach #4, to start the Remote Desktop session, the Rev I spontaneously reboots; just a red light, and then the green lights start and begin to flicker on/off during rediscovery & recognition on the Vz network. While that progresses, I close the not-connected RDP start-up window, and terminate the VPN which is stuck trying to "reconnect". I wait until full internet access is restored. Then I start the VPN. I start the RDP. All is good. If I happen to shut down the RD & VPN during the day, and then restart a connection to work, it connects fine without the router reboot happening. But the next time I try a "morning" attempt 2 or 3 days later, it goes through the same problematic reboot-upon-RD scenario.
While most Vz techs I've dealt with are very good, I live in fear of getting another clueless tech and figure the "devil I know is better than the one I don't". But reading this poster's problem is making me think it isn't "just me". I'm interested in hearing if others are having similar issues.

Hyper-V cluster Backup causes virtual machine reboots for common Cluster Shared Volumes members.

I am having a problem where my VMs are rebooting while other VMs that share the same CSV are being backed up. I have provided all the information that I have gather to this point below. If I have missed anything, please let me know.
My HyperV Cluster configuration:
5 Node Cluster running 2008R2 Core DataCenter w/SP1. All updates as released by WSUS that will install on a Core installation
Each Node has 8 NICs configured as follows:
NIC1 - Management/Campus access (26.x VLAN)
NIC2 - iSCSI dedicated (22.x VLAN)
NIC3 - Live Migration (28.x VLAN)
NIC4 - Heartbeat (20.x VLAN)
NIC5 - VSwitch (26.x VLAN)
NIC6 - VSwitch (18.x VLAN)
NIC7 - VSwitch (27.x VLAN)
NIC8 - VSwitch (22.x VLAN)
Following hotfixes additional installed by MS guidance (either while build or when troubleshooting stability issue in Jan 2013)
KB2531907 - Was installed during original building of cluster
KB2705759 - Installed during troubleshooting in early Jan2013
KB2684681 - Installed during troubleshooting in early Jan2013
KB2685891 - Installed during troubleshooting in early Jan2013
KB2639032 - Installed during troubleshooting in early Jan2013
Original cluster build was two hosts with quorum drive. Initial two hosts were HST1 and HST5
Next host added was HST3, then HST6 and finally HST2.
NOTE: HST4 hardware was used in different project and HST6 will eventually become HST4
Validation of cluster comes with warning for following things:
Updates inconsistent across hosts
  I have tried to manually install "missing" updates and they were not applicable
  Most likely cause is different build times for each machine in cluster
   HST1 and HST5 are both the same level because they were built at same time
   HST3 was not rebuilt from scratch due to time constraints and it actually goes back to Pre-SP1 and has a larger list of updates that others are lacking and hence the inconsistency
   HST6 was built from scratch but has more updates missing than 1 or 5 (10 missing instead of 7)
   HST2 was most recently built and it has the most missing updates (15)
Storage - List Potential Cluster Disks
  It says there are Persistent Reservations on all 14 of my CSV volumes and thinks they are from another cluster.
  They are removed from the validation set for this reason. These iSCSI volumes/disks were all created new for
  this cluster and have never been a part of any other cluster.
When I run the Cluster Validation wizard, I get a slew of Event ID 5120 from FailoverClustering. Wording of error:
  Cluster Shared Volume 'Volume12' ('Cluster Disk 13') is no longer available on this node because of
  'STATUS_MEDIA_WRITE_PROTECTED(c00000a2)'. All I/O will temporarily be queued until a path to the
  volume is reestablished.
Under Storage and Cluster Shared VOlumes in Failover Cluster Manager, all disks show online and there is no negative effect of the errors.
Cluster Shared Volumes
We have 14 CSVs that are all iSCSI attached to all 5 hosts. They are housed on an HP P4500G2 (LeftHand) SAN.
I have limited the number of VMs to no more than 7 per CSV as per best practices documentation from HP/Lefthand
VMs in each CSV are spread out amonst all 5 hosts (as you would expect)
Backup software we use is BackupChain from BackupChain.com.
Problem we are having:
When backup kicks off for a VM, all VMs on same CSV reboot without warning. This normally happens within seconds of the backup starting
What have to done to troubleshoot this:
We have tried rebalancing our backups
  Originally, I had backup jobs scheduled to kick off on Friday or Saturday evening after 9pm
  2 or 3 hosts would be backing up VMs (Serially; one VM per host at a time) each night.
  I changed my backup scheduled so that of my 90 VMs, only one per CSV is backing up at the same time
   I mapped out my Hosts and CSVs and scheduled my backups to run on week nights where each night, there
   is only one VM backed up per CSV. All VMs can be backed up over 5 nights (there are some VMs that don't
   get backed up). I also staggered the start times for each Host so that only one Host would be starting
   in the same timeframe. There was some overlap for Hosts that had backups that ran longer than 1 hour.
  Testing this new schedule did not fix my problem. It only made it more clear. As each backup timeframe
  started, whichever CSV the first VM to start was on would have all of their VMs reboot and come back up.
I then thought maybe I was overloading the network still so I decided to disable all of the scheduled backup
and run it manually. Kicking off a backup on a single VM, in most cases, will cause the reboot of common
CSV members.
Ok, maybe there is something wrong with my backup software.
  Downloaded a Demo of Veeam and installed it onto my cluster.
  Did a test backup of one VM and I had not problems.
  Did a test backup of a second VM and I had the same problem. All VMs on same CSV rebooted
Ok, it is not my backup software. Apparently it is VSS. I have looked through various websites. The best troubleshooting
site I have found for VSS in one place it on BackupChain.com (http://backupchain.com/hyper-v-backup/Troubleshooting.html)
I have tested almost every process on there list and I will lay out results below:
  1. I have rebooted HST6 and problems still persist
  2. When I run VSSADMIN delete shadows /all, I have no shadows to delete on any of my 5 nodes
   When I run VSSADMIN list writers, I have no error messages on any writers on any node...
  3. When I check the listed registry key, I only have the build in MS VSS writer listed (I am using software VSS)
  4. When I run VSSADMIN Resize ShadowStorge command, there is no shadow storage on any node
  5. I have completed the registration and service cycling on HST6 as laid out here and most of the stuff "errors"
   Only a few of the DLL's actually register.
  6. HyperV Integration Services were reconciled when I worked with MS in early January and I have no indication of
   further issue here.
  7. I did not complete the step to delete the Subscriptions because, again, I have no error messages when I list writers
  8. I removed the Veeam software that I had installed to test (it hadn't added any VSS Writer anyway though)
  9. I can't realistically uninstall my HyperV and test VSS
  10. Already have latest SPs and Updates
  11. This is part of step 5 so I already did this. This seems to be a rehash of various other stratgies
I have used the VSS Troubleshooter that is part of BackupChain (Ctrl-T) and I get the following error:
  ERROR: Selected writer 'Microsoft Hyper-V VSS Writer' is in failed state!
  - Status: 8 (VSS_WS_FAILED_AT_PREPARE_SNAPSHOT)
  - Writer Failure code: 0x800423f0 (<Unknown error code>)
  - Writer ID: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
  - Instance ID: {d55b6934-1c8d-46ab-a43f-4f997f18dc71}
  VSS snapshot creation failed with result: 8000FFFF
VSS errors in event viewer. Below are representative errors I have received from various Nodes of my cluster:
I have various of the below spread out over all hosts except for HST6
Source: VolSnap, Event ID 10, The shadow copy of volume took too long to install
Source: VolSnap, Event ID 16, The shadow copies of volume x were aborted because volume y, which contains shadow copy storage for this shadow copy, wa force dismounted.
Source: VolSnap, Event ID 27, The shadow copies of volume x were aborted during detection because a critical control file could not be opened.
I only have one instance of each of these and both of the below are from HST3
Source: VSS, Event ID 12293, Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details RevertToSnashot [hr = 0x80042302, A Volume Shadow Copy Service component encountered an
unexpected error.
Source: VSS, Event ID 8193, Volume Shadow Copy Service error: Unexpected error calling routine GetOverlappedResult. hr = 0x80070057, The parameter is incorrect.
So, basically, everything I have tried has resulted in no success towards solving this problem.
I would appreciate anything assistance that can be provided.
Thanks,
Charles J. Palmer
Wright Flood

Tim,
Thanks for the reply. I ran the first two commands and got this:
Name
Role Metric
Cluster Network 1
3  10000
Cluster Network 2 - HeartBeat                              1   1300
Cluster Network 3 - iSCSI                                    0  10100
Cluster Network 4 - LiveMigration                         1   1200
When you look at the properties of each network, this is how I have it configured:
Cluster Network 1 - Allow cluster network communications on this network and Allow clients to connect through this network (26.x subnet)
Cluster Network 2 - Allow cluster network communications on this network. New network added while working with Microsoft support last month. (28.x subnet)
Cluster Network 3 - Do not allow cluster network communications on this network. (22.x subnet)
Cluster Network 4 - Allow cluster network communications on this network. Existing but not configured to be used by VMs for Live Migration until MS corrected. (20.x subnet)
Should I modify my metrics further or are the current values sufficient.
I worked with an MS support rep because my cluster (once I added the 5th host) stopped being able to live migrate VMs and I had VMs host jumping on startup. It was a mess for a couple of days. They had me add the Heartbeat network as part of the solution
to my problem. There doesn't seem to be anywhere to configure a network specifically for CSV so I would assume it would use (based on my metrics above) Cluster Network 4 and then Cluster Network 2 for CSV communications and would fail back to the Cluster Network
1 if both 2 and 4 were down/inaccessible.
As to the iSCSI getting a second NIC, I would love to but management wants separation of our VMs by subnet and role and hence why I need the 4 VSwitch NICs. I would have to look at adding an additional quad port NIC to my servers and I would be having to
use half height cards for 2 of my 5 servers for that to work.
But, on that note, it doesn't appear to actually be a bandwidth issue. I can run a backup for a single VM and get nothing on the network card (It caused the reboots before any real data has even started to pass apparently) and still the problem occurs.
As to Backup Chain, I have been working with the vendor and they are telling my the issue is with VSS. They also say they support CSV as well. If you go to this page (http://backupchain.com/Hyper-V-Backup-Software.html)
they say they support CSVs. Their tech support has been very helpful but unfortunately, nothing has fixed the problem.
What is annoying is that every backup doesn't cause a problem. I have a daily backup of one of our machines that runs fine without initiating any additional reboots. But most every other backup job will trigger the VMs on the common CSV to reboot.
I understood about the updates but I had to "prove" it to the MS tech I was on the phone with and hence I brought it up. I understand on the storage as well. Why give a warning for something that is working though... I think that is just a poor indicator
that it doesn't explain that in the report.
At a loss for what else I can do,
Charles J. Palmer

Can't shutdown, poweroff: machines reboots instead

No matter which commands I use, systemctl poweroff, shutdown -h, halt -p, my machine will immediately reboot instead. Here are all journalctl lines immediately after calling systemctl poweroff: the system will tell me that it is going to shutdown, but instead it reboots. Also, the last message I see before the reboot occurs is along the lines of “rebooting now”.
Nov 08 13:46:04 rechenschieber systemd-logind[335]: System is powering down.
Nov 08 13:46:04 rechenschieber org.a11y.atspi.Registry[836]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async rea
Nov 08 13:46:04 rechenschieber polkitd[424]: Unregistered Authentication Agent for unix-process:888:1773 (system bus name :1.13, object path /org/freedesktop/PolicyKit1/Authentic
Nov 08 13:46:04 rechenschieber org.a11y.Bus[769]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-err
Nov 08 13:46:04 rechenschieber systemd[609]: Stopping Default.
Nov 08 13:46:04 rechenschieber systemd[609]: Stopped target Default.
Nov 08 13:46:04 rechenschieber systemd[609]: Stopping Basic System.
Nov 08 13:46:04 rechenschieber systemd[609]: Stopped target Basic System.
Nov 08 13:46:04 rechenschieber systemd[609]: Stopping Paths.
Nov 08 13:46:04 rechenschieber systemd[609]: Stopped target Paths.
Nov 08 13:46:04 rechenschieber systemd[609]: Stopping Timers.
Nov 08 13:46:04 rechenschieber systemd[609]: Stopped target Timers.
Nov 08 13:46:04 rechenschieber systemd[609]: Stopping Sockets.
Nov 08 13:46:04 rechenschieber systemd[609]: Stopped target Sockets.
Nov 08 13:46:04 rechenschieber systemd[609]: Starting Shutdown.
Nov 08 13:46:04 rechenschieber systemd[609]: Reached target Shutdown.
Nov 08 13:46:04 rechenschieber systemd[609]: Starting Exit the Session...
Nov 08 13:46:04 rechenschieber rpcbind[399]: rpcbind terminating on signal. Restart with "rpcbind -w"
Nov 08 13:46:04 rechenschieber NetworkManager[331]: <warn> disconnected by the system bus.
Nov 08 13:46:04 rechenschieber NetworkManager[331]: g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-e
Nov 08 13:46:04 rechenschieber systemd[609]: Received SIGRTMIN+24 from PID 897 (kill).
Nov 08 13:46:04 rechenschieber systemd[611]: pam_unix(systemd-user:session): session closed for user janis
Nov 08 13:46:04 rechenschieber systemd[1]: rpcbind.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Nov 08 13:46:04 rechenschieber systemd[1]: Unit rpcbind.service entered failed state.
Nov 08 13:46:04 rechenschieber systemd[1]: rpcbind.service failed.
Nov 08 13:46:05 rechenschieber NetworkManager[331]: <info> caught signal 15, shutting down normally.
Nov 08 13:46:05 rechenschieber NetworkManager[331]: <info> (wlan0): device state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
Nov 08 13:46:05 rechenschieber NetworkManager[331]: ** (NetworkManager:331): CRITICAL **: dbus_g_proxy_call_no_reply: assertion '!DBUS_G_PROXY_DESTROYED (proxy)' failed
Nov 08 13:46:05 rechenschieber NetworkManager[331]: <info> (eth0): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36]
Nov 08 13:46:05 rechenschieber kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Nov 08 13:46:05 rechenschieber wpa_supplicant[536]: Successfully initialized wpa_supplicant
Nov 08 13:46:05 rechenschieber wpa_supplicant[536]: wlan0: CTRL-EVENT-TERMINATING
Nov 08 13:46:05 rechenschieber kernel: e1000e: eth0 NIC Link is Down
Nov 08 13:46:05 rechenschieber kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Nov 08 13:46:05 rechenschieber NetworkManager[331]: (NetworkManager:331): GLib-CRITICAL **: Source ID 37 was not found when attempting to remove it
Nov 08 13:46:05 rechenschieber NetworkManager[331]: <info> exiting (success)
Nov 08 13:46:05 rechenschieber umount[981]: umount: /var: target is busy
Nov 08 13:46:05 rechenschieber umount[981]: (In some cases useful info about processes that
Nov 08 13:46:05 rechenschieber umount[981]: use the device is found by lsof(8) or fuser(1).)
Nov 08 13:46:05 rechenschieber systemd[1]: var.mount mount process exited, code=exited status=32
Nov 08 13:46:05 rechenschieber systemd[1]: Failed unmounting /var.
Nov 08 13:46:05 rechenschieber systemd[1]: Shutting down.
Nov 08 13:46:05 rechenschieber systemd-journal[141]: Journal stopped
-- Reboot --
I tried following up on several suggestions I found around here and online: I disabled Wake-on-Lan in the BIOS, I disabled/stopped tlp.service and tpfand.service (the only power-management-like tools I am running). But that does not help.
Note: the system is not powering off to then reboot. It reboots immediately, just as if I had executed `systemctl reboot'.
FWIW, my system is up to date:
3.17.2-1-ARCH #1
systemd 217
Any fixes? It's getting a bid annoying having to shut down the machine through the syslinux menu after each of these reboots.
Last edited by Stalafin (2014-11-08 12:59:53)

in your log we can read this :
rpcbind.service failed
umount: /var: target is busy
Failed unmounting /var
it's not normal, you could try to solve these errors, it may help to solve the shutdown problem,
use "systemctl --failed --all" at boot in order to know if all is Ok at startup

Managed Servers do not start automatically on machine reboot.

Hi all,
We have installed node manager as windows service.
We have configured a managed server and an admin server which are on same machine.
We are using WLST to start the admin and the managed servers.
The sequence is :
java weblogic.WLST
connect()
nmStart('AdminServer')
nmStart('ManagedServerName')
We are successfully able to start both the server's, however if we reboot the machine, the servers fail to come up even though we have installed node manager as windows service.
We also have Auto Restart and crash recovery as true/enabled.
Do we need to do any other setting??
Any pointers on the same will be highly appreciated..
Thanks.

Hi,
I'm having the same issue. I cannot start a ManagedServer using NodeManager. I'm using WLST script to start the Admin and Managed Server:
nmConnect('username', 'password', 'localhost', '5556', 'base_domain','D:\\product\\Oracle\\11.1.1\\Middleware\\user_projects\\domains\\base_domain','ssl')
nmStart('AdminServer')
connect('username','password','t3://localhost:7001')
start('managedServer', 'Server', t3://localhost:7001')
I've successfully restarted using the "startWeblogic.cmd" and "startManagedServer.cmd" scripts.

Problem with machine rebooting. Essbase 11.1.1 installation.

Hi all,
I have a problem with my Essbase 11.1.1 installation. In a nutshell when I reboot the machine I can't log in EAS anymore. The only way I found out is just reconfigur EPM system after rebooting but It's just a work around.
Thanks for helping

Hi user,
AsI read between lines, it seems that you previously were able to access EAS so your installlation is not the problem but you accessing to EAS isthe problem. As you mentioned you are having problems accessing it after rebooting the server, I think it could be a prolem with the services. Please try stopping all the services in this order:
administration servicese
Essbase services 11.1.1.1_Hypservice_1
Foundation
Openldap
and then restart them from bottom to top. Let me know.
J.

Trouble connecting iMac to internet after Time Machine Reboot

Bear with me here guys.... I recently went to download Aperture onto my Mac but found that I required Mountain Lion, so I purchased it to upgrade from Snow Leopard. Having download the new OS I started the installation and it failed as it appears I have a fault with the Hard Drive; though my Mac gad operated just fine previously. As everytime I restarted my computer it wanted to start installing Mountain Lion but couldn't complete due to HD error; I rebooted via the Snow Leopard CD and loaded my last Time Machine save. I now have the Mountain Lion icon sat on my dock awaiting installation, though after I've had the HD fixed first obviously.
So having just reloaded the OS and rebooted via my Time Machine Backups (For which I use a USB connected Samsung External Drive) my iMac will connect to my wireless network via Airport just fine. Loading the internet via Safari is another matter. It will load the window but will remain blank white with the pinwheel spinning. Eventually I get the message that another computer using the same IP address is already on the network.
Having read the threads on here I have already tried resetting Safari, restarting my Router, I have double checked all the IP adresses of my another connected devices (none hold the same IP address as the iMac) have been round in circles in Network Settings Renewing the DCHP Lease, trying the set the IP address manually, turned everything off and on again and I have spoken with my service provider and they have not been able to tell me any more than the threads on here; and so here I am at a loss now.
Any or advice would be really appreciated.

Just a few more ideas...
Searching the web, I've found some possible fixes, some of which you have probably already tried.
Try connecting directly to the router with an Ethernet cable.
Check your wireless security (you should use WPA2, it's the strongest). Someone could be using your network, so try changing the password and see if that helps (this can be a pain if you have a lot of devices).
Flush the DNS cache:
For Lion and Mountain Lion: Enter the following command into Terminal:
sudo killall -HUP mDNSResponder
For Mavericks:
dscacheutil -flushcache;sudo killall -HUP mDNSResponder
Update the router firmware if it is out of date. Also, you can reflash with the current firmware, which [i]might[/i] help.
Hope some of these help, if not best of luck with getting the fault sorted out.

Machines reboot after update even when SCCM is configured with 'suppress reboot'

Hello,
I need some advice about distributing updates.
My problem : yesterday afternoon I had to deploy an update and eliminate any reboot that could occur.
Everything was ok, the update was deployed with no reboot.
But, this night, some of the machines started to reboot at 03h00 !!
In the eventlog I can see this :
The process C:\Windows\system32\svchost.exe (xxxxxx) has initiated the restart of computer xxxxxxx on behalf of user NT AUTHORITY\SYSTEM for the following reason: Operating System: Recovery (Planned)
Reason Code: 0x80020002
Shutdown Type: restart
Comment:
If I look in the windowsupdate.log I can see that it is the AU client who has done the reboot.
How can I avoid that ?
I thought SCCM would manage every settings for the update distribution/reboot.
I have found a post who says that you have to configure the settings 'No auto-restart with logged on users for scheduled automatic updates installations' in a GPO.
But what can I do when there is no one logged on the machine ? how can I avoid the reboot ?
I know my request is strange to install an update and make no reboot but I was asked so by my management.
Thanks in advance for your help.
Marc

Hi,
It sounds like it is the Windows Update Agent that has rebooted the computer, have you set the group policy for Windows Update "Configure Automatic Updates" to disabled? otherwise it is knwon to restart the client..
Jason describes it here:
http://blog.configmgrftw.com/software-updates-management-and-group-policy-for-configmgr-cont/
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Machine Reboot

Has anybody had this one before?
I increased my AGP Aperture size to 256mb which has now made my VGA card work with the soundcard but my machine now reboots itself when you put in a CD-ROM. Has anyone got any ideas? Please!!!

Check your installation documentation and release note to ensure that EM10g is certified and supported on Fedora 4 before you install.

Machine reboots on it's own

Similar Messages

Maybe you are looking for