Shirt Pocket Discussions  
    Home netTunes launchTunes SuperDuper! Buy Now Support Discussions About Shirt Pocket    

Go Back   Shirt Pocket Discussions > SuperDuper! > General

Reply
 
Thread Tools Rate Thread Display Modes
  #1  
Old 10-09-2006, 04:15 PM
jjj jjj is offline
Registered User
 
Join Date: Oct 2006
Posts: 12
System shutting down (sometimes) after scheduled backup

This has happened only twice. The backup runs at 6:30 and takes about ten minutes. Both times, /var/log/system.log looks like this just before the log entries showing where I started the system again:

Code:
Oct  2 06:41:02 slynew diskarbitrationd[42]: applet [1513]:34843 not responding.
Oct  2 06:41:03 slynew kernel[0]: jnl: close: flushing the buffer cache (start 0x66a200 end 0x66c400)
I'm backing up to one of three partitions on a FireWire drive. I leave the mirror backup partition unmounted (with the other two mounted) after discovering that SuperDuper can mount and unmount that partition on its own.

I haven't actually witnessed the shutdown, and it doesn't happen every time the backup runs. I'm judging based on the logs and some circumstantial evidence (someone telling me he couldn't ping my system sometime just before 7:30) that the shutdown is happening right after the backup runs.

So I don't know that its connected to SuperDuper, but before calling Apple I thought I'd ask if anyone else has experienced this and/or if any of the above is illuminating.

Last edited by jjj; 10-09-2006 at 04:18 PM.
Reply With Quote
  #2  
Old 10-09-2006, 04:20 PM
dnanian's Avatar
dnanian dnanian is offline
Administrator
 
Join Date: Apr 2001
Location: Weston, MA
Posts: 14,745
Send a message via AIM to dnanian
Basically, it looks like the drive must have failed or stopped responding properly. Very strange. Running any low-level utilities, antivirus, etc?
__________________
--Dave Nanian
Reply With Quote
  #3  
Old 10-10-2006, 12:07 AM
jjj jjj is offline
Registered User
 
Join Date: Oct 2006
Posts: 12
But would a failure to respond at the end of a backup make the system shut down (i.e. the whole Mac)?

In answer to your question, no antivirus or the like is running. The scheduled update seems to have run fine. And I've just noticed that the message "kernel[0]: jnl: close: flushing the buffer cache" is the same given when I unmount the mirror partition myself in Disk Utility (such as just after booting).

Speaking of which, is there any possibility that my preference for keeping that partition unmounted, and with other partitions remaining mounted, has anything to do with this?
Reply With Quote
  #4  
Old 10-10-2006, 08:54 AM
dnanian's Avatar
dnanian dnanian is offline
Administrator
 
Join Date: Apr 2001
Location: Weston, MA
Posts: 14,745
Send a message via AIM to dnanian
It could be indicative of a system-wide failure, yes... and that could be due to a misbehaving drive. No panic.log?
__________________
--Dave Nanian
Reply With Quote
  #5  
Old 10-10-2006, 02:13 PM
jjj jjj is offline
Registered User
 
Join Date: Oct 2006
Posts: 12
No panic.log, no panic screen ("You need to restart your computer," etc.). Just the next morning, my Mac ain't on.

I watched a scheduled backup this time. Everything seemed to work. This is the system.log:
Code:
Oct 10 06:30:16 slynew diskarbitrationd[42]: disk1s2    hfs      CBADEC29-3F8C-357E-8B45-7D072826D110 Mirror                  /Volumes/Mirror
Oct 10 06:30:33 slynew KernelEventAgent[35]: tid 00000000 received unknown event (256)
Oct 10 06:30:33 slynew KernelEventAgent[35]: tid 00000000 received unknown event (256)
Oct 10 06:40:55 slynew diskarbitrationd[42]: applet [591]:19411 not responding.
Oct 10 06:40:55 slynew kernel[0]: jnl: close: flushing the buffer cache (start 0x176200 end 0x178400)
The mirror partition did unmount (or at least it is unmounted after this), and the backup log shows no complaints.

I guess I'm just going to reschedule this during the day and keep watching it until something happens.
Reply With Quote
  #6  
Old 10-10-2006, 02:33 PM
dnanian's Avatar
dnanian dnanian is offline
Administrator
 
Join Date: Apr 2001
Location: Weston, MA
Posts: 14,745
Send a message via AIM to dnanian
OK. So, "applet" (which is likely our scheduling driver) has asked for the eject. It stops responding while we're waiting for the system to do it. It flushes the journal and then does eject. That seems reasonable without the shutdown, at least!
__________________
--Dave Nanian
Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Details on how Scheduled Backup works jbezdek General 3 10-04-2006 11:59 AM
sleep option after a scheduled backup not working rdlsmith General 11 07-11-2006 08:29 AM
backup (all files) error smtorr General 3 02-09-2006 08:10 AM
How to verify a Scheduled Backup? tuqqer General 3 12-06-2005 06:50 PM
System crash on first backup attempt cabo General 10 08-14-2005 05:27 AM


All times are GMT -4. The time now is 06:26 PM.


Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2021, vBulletin Solutions, Inc.