LaCie "Eco Mode" causing Time Machine problems

I just purchased a LaCie P'9231, which is advertised as an Apple Store Exclusive. I've been having problems with it and Time Machine and I'm starting to think its due to the Eco Mode feature. I'd rather have the HD on all the time and turn "Eco Mode" completely off and I've unchecked the "Put the Hard Disk to Sleep..." option in Energy Saver. Still I'm looking at it right in front of me in Eco Mode (so it didn't help). Any drivers to instal or are others experienceing this problem? Thank you so much!!!!

I just encountered essentially the same problem with a new LaCie "USB 3.0" 3-terabyte d2 drive (part of their new "v3" series). Although it's called the "USB 3.0" drive, it actually has ports for eSata, USB 2.0, USB 3.0, and Firewire 800 -- I use Firewire 800.
The manual says you can turn off Eco Mode using the LaCie Desktop Manager. I want it turned off because I have several drives and waiting for them to spin up one by one every time I use my Mac is unacceptable. Desktop Manager's Eco tab has a single button that takes you to the Energy Saver pane of System Preferences, where I always have the 'Put the Hard Disk to Sleep..." option turned off. The manual says this will stop the drive from spinning down in Eco Mode.
Nevertheless, the drive always spins down after a few minutes of inactivity. Worse, it will NOT spin back up when I open the drive's window or drag a file onto it. Instead, it freezes the Finder so that I can do nothing on my Mac -- among other things, I can't drag the drive icon to the trash to dismount it. I have to turn the drive off using its power switch, which of course brings up an alert telling me that doing this might damage the drive and instead I should dismount it first -- and then the Finder comes back to life. According to Desktop Manager, I could also set up the button on the front of the drive so that pushing it will cause the drive to spin back up. I haven't bothered to try that because I am unwilling to have to turn my devices on and off by pushing hardware buttons all the time.
LaCie tech support just sent me a message telling me that the drive is designed so that you cannot turn off Eco Mode. That is directly inconsistent with the manual, so I assume tech support means that they still don't have the firmware in the drive working right. They released a firmware update in late August that supposedly fixes a wake/sleep problem, but reading between the lines of the tech support messages I received, that apparently relates only to a problem when your Mac goes to sleep -- I have mine set so that it never sleeps.
Bottom line: unless and until LaCie revises the firmware to allow the drive to keep spinning all the time -- as advertised -- this product is essentially unusable to me.

Similar Messages

EFI Update Causes Time Machine Problems

After the EFI update today (10/12) Time Machine will no longer mount its disk image on an external network drive via AFP wireless connection. The external drive is presented through Ubuntu 8.10 with Netatalk 2.03. Anyone else having this problem yet, or better yet have a solution?

Fixed it! Mounting it in Disk Utility and repairing the file system worked. It should be noted however that I can't confirm the update was the cause of of this problem but, its some kawinky-**** huh?

Help, I am about to pull my hair out, can't get into a locked drive and Time Machine problem

I've screwed everything up, I think. I had Time Machine doing backups to an external 500Gig drive and somehow it got locked. I went into Get Info to try and change the access but it won't allow me. On top of this problem, my original drive died and I can't get into Time Machine to restore. When I click "Enter Time Machine", nothing happens. I created an eDisk and a startup disk to another external drive that I'm using now, but since everything that's been backed up is on the other drive that I can't access. When I try accessing the drive it gives: "The folder “G-DRIVE ” can’t be opened because you don’t have permission to see its contents." I'm not knowledgeable enough to work from the command line, so if I need to do that to access the drive, please walk me though it. As for the Time Machine problem, I have no idea how to recover anything since it won't even come up, it just sits there. Outside of blowing my brains out, I don't know what to do. Any help would be greatly appreciated as I can't afford to take it to Apple to let them try and fix it.

Hello, not sure how this might affect a TM drive, or not, but...
Here is what i needed to do for my drive "320GB HD", the last command is just for clean up
Open Terminal and type these commands carefully with the spaces & change 320GB HD to the name of your drive.
sudo chflags 0 "/volumes/320GB HD"
sudo chown root "/volumes/320GB HD"
sudo chmod 1775 "/volumes/320GB HD"
sudo -k
That said, these should be sufficient to do the job:
sudo chflags 0 "/Volumes/320GB HD"
sudo chmod a+rx "/Volumes/320GB HD"

Time Machine problems

My question is this: Is there any way to force Time Machine to make a complete backup of all files, not just the recently changed ones?
My story so far:
Installed Leopard yesterday. Detected brand-new (and newly Mac formatted Extended Journaled) Seagate 300GB hard drive and asked if I wanted to use it for Time Machine. Answered yes. Thought I was through with worrying about Time Machine- wrong! First backups went OK- so I thought. First one took several hours and seemed to back up the whole drive. Subsequent ones were shorter, which seemed to make sense. After a couple backups had been performed, decided to see if I could "go back in time". The only window to show up was the original backup (which I never bothered to check to see if it truly was complete). This morning I was greeted with an error that it couldn't do the backup because it couldn't complete the library.
So I come to this forum and read posts advising me to reformat my drive and name it with no spaces (it was previously "Backup Disk"). I did that, erasing all previous backups. Seemed to help, but...
Now, unfortunately, Time Machine doesn't realize that the backups are not there anymore and will not do a complete backup with my completely empty external drive. I even tried removing the com.apple.TimeMachine.plist file from its place in the directory to see if that would force the program to build a new library. It didn't.
Not even sure that making a complete backup again will solve all my Time Machine problems but it's a start!

I had this same problem when I first started using my Time Machine on my MBP. I had a portable drive (Western Digital 160 gig passport drive).
I was advised by the tech to do the following before the first use of the drive:
1. Turn off the time machine
1. format the drive with your disk utility.
3. configure the time machine for the drive.
4. Turn on the time machine. Make sure your not backing up anything but your main hard drive. (Your shouldn't back up any other external hard drives). At least not the first time you run Time machine.
5. start the backup.
The first backup is always the longest, but it shouldn't take that long, especially if your doing the Macbook Air.
Hope this helps.

Time Machine Problem, Please Help.

Hi, I have a new MacBook Air and TM just doesn't work. I keep getting the "backup volume cannot be found" error message. I've trashed the preference file in Library, quit TM, restart again, and repaired permission to no avail. I have also reinstalled the OS and the same problem persists. I've tried on 3 external drives (Time Capsule wirelessly, WD MyBook connected via USB and a Lacie portable drive connected via USB) and TM fails to backup every time. I've searched this board and other Mac fora and found no solution to my specific problem. Any help or suggestions would be greatly appreciated.

HiDef Jules wrote:
Hi there,
Today I installed a little program to convert flac audio files to mp3. When I ran the program the computer froze, so I rebooted but then I could move the cursor but not click on any menus or icons on the desktop, they just wouldnt respond - so basically I couldnt use the computer. After re-booting a few times with the same result I decided to reinstall the system using time machine from an external hard drive. I reinstalled OSX, then reinstalled Snow Leopard, then reinstalled the system from a previous save from Time Machine.
how exactly did you reinstall the system from TM? please give details. the correct way to do it is to boot from the snow leopard DVD and use the "restore system from backup" utility in the Utilities menu. there is no need to reinstall anything prior to using that utility. the restore utility wipes your hard drive and restores it to the state it was in at the backup time.
It said the installation was successful, but when the computer restarted a message comes up saying "You need to restart your computer. Hold down the Power button until it turns off, then press the Power button again". Ive done this about 5 times now but it always just says the same message without starting properly. WHAT DO I DO???? I really need to use my computer tomorrow so any help is hugely appreciated!!! TIA
PS. i have done a hardware test in "loop mode" and it says everything is fine

Time Machine Problems - Won't Launch Automatically, Won't Mount Disk Image

Hi there,
I have a MacBook Pro (Mid 2009) running OSX Mavericks 10.9.2. I've had Time Machine running successfully with a 2TB Time Capsule for some time. Recently, I reinstalled Parallels VM software and have been having issues with Time Machine ever since. Initially, I had TM backing up the Virtual Machine, but decided that wasn't a great way to go, so turned it off in the VM configurations pane.
Since then, however, I have been unable to successfully back up my MacBook. I notice a few things:
The Time Machine drive does not mount as it used to. It does not show up on my desktop.
When I go into Time Machine Preferences, the drive does not show the usual green disk icon. The icon is blue and has the stick-figure people on it.
I can remove the blue disk drive, and re-select the drive. It stays green for about 30 seconds, then converts to the blue icon.
I get a number of plist errors in the Time Machine dashboard app. Here's the latest feed:
Property list invalid for format: 200 (property lists cannot contain NULL)
Property list invalid for format: 200 (property lists cannot contain NULL)
Property list invalid for format: 200 (property lists cannot contain NULL)
Starting manual backup
Network destination already mounted at: /Volumes/Sean's Time Capsule
Disk image /Volumes/Sean's Time Capsule/Sean's MacBook.sparsebundle mounted at: /Volumes/Time Machine Backups
Backing up to /dev/disk2s2: /Volumes/Time Machine Backups/Backups.backupdb
Backup canceled.
At this point, I'm a bit stumped. I've tried deleting the old sparsebundle, I've reset the Time Capsule, and I've come up with no ideas as to how I can get this woring again. It seems like the property list needs 'something' but can't find the old file or the property list is corrupt or something. I'm assuming that is why the Time Machine disk image won't mount?
Thanks for your help - suggestions are welcome!

1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. But with the aid of the test results, the solution may take a few minutes, instead of hours or days.
2. If you don't already have a current backup, back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. Backup is always a must, and when you're having any kind of trouble with the computer, you may be at higher than usual risk of losing data, whether you follow these instructions or not.
There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
3. Below are instructions to run a UNIX shell script, a type of program. All it does is to collect information about the state of the computer. That information goes nowhere unless you choose to share it. However, you should be cautious about running any kind of program (not just a shell script) at the request of a stranger. If you have doubts, search this site for other discussions in which this procedure has been followed without any report of ill effects. If you can't satisfy yourself that the instructions are safe, don't follow them. Ask for other options.
Here's a summary of what you need to do, if you choose to proceed:
☞ Copy a line of text in this window to the Clipboard.
☞ Paste into the window of another application.
☞ Wait for the test to run. It usually takes a few minutes.
☞ Paste the results, which will have been copied automatically, back into a reply on this page.
The sequence is: copy, paste, wait, paste again. You don't need to copy a second time. Details follow.
4. You may have started the computer in "safe" mode. Preferably, these steps should be taken in “normal” mode, under the conditions in which the problem is reproduced. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual. If you can only test in safe mode, do that.
5. If you have more than one user, and the one affected by the problem is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.
6. The script is a single long line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, though you may not see all of it in the browser window, and you can then copy it. If you try to select the line by dragging across the part you can see, you won't get all of it.
Triple-click anywhere in the line of text below on this page to select it:
PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/libexec;clear;cd;p=(Software Hardware Memory Diagnostics Power FireWire Thunderbolt USB Fonts 51 4 1000 25 5120 KiB/s 1024 85 \\b%% 20480 1 MB/s 25000 ports 'com.autodesk.AutoCad com.evenflow.dropbox com.google.GoogleDrive' DYLD_INSERT_LIBRARIES\ DYLD_LIBRARY_PATH -86 ` route -n get default|awk '/e:/{print $2}' ` 25 N\\/A down up 102400 25600 recvfrom sendto CFBundleIdentifier 25 25 25 );N5=${#p[@]};p[N5]=` networksetup -listnetworkserviceorder|awk ' NR>1 { sub(/^$[0-9]+$ /,"");n=$0;getline;} $NF=="'${p[45]}')" { sub(/.$/,"",$NF);print n;exit;} ' `;f=('\n%s: %s\n' '\n%s\n\n%s\n' '\nRAM details\n%s\n' %s\ %s '%s\n\t(%s)\n' );S0() { echo ' { q=$NF+0;$NF="";u=$(NF-1);$(NF-1)="";gsub(/^ +| +$/,"");if(q>='${p[$1]}')printf("%s (UID %s) is using %s '${p[$2]}'\\\\n",$0,u,q);} ';};s=(' /^ *$|CSConfigDot/d;s/^ */ /;s/[-0-9A-Fa-f]{22,}/UUID/g;s/(ochat)\.[^.]+(\..+)/\1\2/;/Shared/!s/\/Users\/[^/]+/~/g ' ' s/^ +//;5p;6p;8p;12p;' ' {sub(/^ +/,"")};NR==6;NR==13&&$2<'${p[10]} ' 1s/://;3,6d;/[my].+:/d;s/^ {4}//;H;${ g;s/\n$//;/s: [^EO]|x([^08]|02[^F]|8[^0])/p;} ' ' 5h;6{ H;g;/P/!p;} ' ' ($1~/^Cy/&&$3>'${p[11]}')||($1~/^Cond/&&$2!~/^N/) ' ' /:$/{ s/ *:$//;x;s/\n//;/Apple|Genesy|Intel|SMSC/d;s/\n.*//;/\)/p;};/^ *(V.+ [0N]|Man).+ /{ s/ 0x.... //;s/[()]//g;s/(.+: )(.+)/ (\2)/;H;} ' ' s/^.*C/C/;H;${ g;/No th|pms/!p;} ' '/= [^GO]/p' '{$1=""};1' ' /Of/!{ s/^.+is |\.//g;p;} ' ' $0&&!/:/;END { if(NR<100)print "com.apple.";} ' ' $3~/[0-9]:[0-9]{2}$/ { $4="";gsub(" "," ");gsub(/:[0-9:a-f]{14}/,"");} { print|"tail -n'${p[12]}'";} ' ' NR==2&&$4<='${p[13]}' { print $4;} ' ' END { $2/=256;if($2>='${p[15]}')print int($2) } ' ' NR!=13{next};{sub(/[+-]$/,"",$NF)};'"`S0 21 22`" 'NR==2'"`S0 37 17`" ' NR!=5||$8!~/[RW]/{next};{ $(NF-1)=$1;$NF=int($NF/10000000);for(i=1;i<=3;i++){$i="";$(NF-1-i)="";};};'"`S0 19 20`" 's:^:/:p' '/\.kext\/(Contents\/)?Info\.plist$/p' ' s/^.{52}//;s/ .+//p ' ' /Launch[AD].+\.plist$/;END{if(NR<100)print "/System/";} ' '/\.xpc\/(Contents\/)?Info\.plist$/p' ' NR>1&&!/0x|\.[0-9]+$|com\.apple\.launchctl\.(Aqua|Background|System)$/ { print $3;} ' '/\.(framew|lproj)/d;/plist:|:.+(M.+exec|scrip)/s/:[^:]+//p' '/root/p' ' !/\/Contents\/.+\/Contents|Applic|Autom|Frameworks/&&/Lib.+\/Info.plist$/;END{if(NR<100)print "/System/"};' '/^\/usr\/lib\/.+dylib$/p' '/\/etc\/(auto_m|hosts[^.]|peri)/s/^\.\/[^/]+//p' ' /\/(Contents\/.+\/Contents|Frameworks)\//d;p;' 's/\/(Contents\/)?Info.plist$//;p' ' { gsub("^| ","||kMDItem'${p[35]}'=");sub("^.."," ") };1 ' p '{print $3"\t"$1}' 's/\'$'\t''.+//p' 's/1/On/p' '/Prox.+: [^0]/p' '$2>'${p[9]}'{$2=$2-1;print}' ' BEGIN { i="'${p[26]}'";M1='${p[16]}';M2='${p[18]}';M3='${p[31]}';M4='${p[32]}';} !/^A/ { next;} /%/ { getline;if($5<M1) a="user "$2"%, system "$4"%";} /disk0/&&$4>M2 { b=$3" ops/s, "$4" blocks/s";} $2==i { if(c) { d=$3+$4+$5+$6;next;};if($4>M3||$6>M4) c=int($4/1024)" in, "int($6/1024)" out";} END { if(a)print "CPU: "a;if(b)print "I/O: "b;if(c)print "Net: "c" (KiB/s)";if(d)print "Net errors: "d" packets/s";} ' ' /r\[0\] /&&$NF!~/^1(0|72\.(1[6-9]|2[0-9]|3[0-1])|92\.168)\./ { print $NF;exit;} ' ' !/^T/ { printf "(static)";exit;} ' '/apsd|OpenD/!s/:.+//p' ' (/k:/&&$3!~/(255\.){3}0/ )||(/v6:/&&$2!~/A/ ) ' ' /lR/ { if($2<='${p[25]}')print $2;} ' ' BEGIN { FS=":";} $3~/(sh|ng|ic)$/ { n=split($3,a,".");sub(/_2.+/,"",a[n-1]);b=b"\n"$2" "a[n-1]" "a[n]" "$1;c=c$1;} END { d="sort|tail -n'${p[38]}'";print b|d;close(d);if(c)print("\n\t* Code injection");} ' ' NR!=4{next} {$NF=int($NF/10240)} '"`S0 27 14`" ' END { if($3~/[0-9]/)print$3;} ' ' BEGIN { L='${p[36]}';} !/^[[:space:]]*(#.*)?$/ { l++;if(l<=L)f=f"\n "$0;} END { F=FILENAME;if(!F)exit;if(!f) f="\n [N/A]";"file -b "F|getline T;if(T!~/^(A.+ E.+ text$|POSIX sh.+ text ex)/) F=F" ("T")";printf("\nContents of %s\n%s\n",F,f);if(l>L) printf("\n ...and %s more line(s)\n",l-L);} ' ' BEGIN{FS="= "} /Path/{print $2} ' ' /^ +B/{ s/.+= |(-[0-9]+)?\.s.+//g;p;} ' ' END{print NR} ' ' /id: N|te: Y/{i++} END{print i} ' ' /:/{$0="'"${p[28]}"'"};1;' );c1=(system_profiler pmset\ -g nvram fdesetup find syslog df vm_stat sar ps sudo\ crontab sudo\ iotop top pkgutil PlistBuddy whoami cksum kextstat launchctl sudo\ launchctl crontab 'sudo defaults read' stat lsbom mdfind ' for i in ${p[24]};do ${c1[18]} ${c2[27]} $i;done;' defaults\ read scutil sudo\ dtrace sudo\ profiles sed\ -En awk /S*/*/P*/*/*/C*/*/airport networksetup );c2=(com.apple.loginwindow\ LoginHook '-c Print /L*/P*/loginw*' '-c Print L*/P*/*loginit*' '-c Print L*/Saf*/*/E*.plist' '~ $TMPDIR.. $ -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 $' '.??* -path .Trash -prune -o -type d -name *.app -print -prune' '-c Print\ :'${p[35]}' 2>&1' '-c Print\ :Label 2>&1' '{/,}L*/{Con,Pref}* -type f ! -size 0 -name *.plist -exec plutil -s {} \;' "-f'%N: %l' Desktop L*/Keyc*" therm sysload boot-args status '-F bsd -k Sender kernel -k Message Req "Beac|caug|dead[^bl]|GPU |hfs: Ru|inval|jnl:|last value [1-9]|n Cause: -|NVDA$|pagin|proc: t|Roamed|rror|ssert|Thrott|timed? ?o|WARN" -k Message Rne "Goog|ksadm|SMC:" -o -k Sender fseventsd -k Message Req "SL"' '-du -n DEV -n EDEV 1 10' 'acrx -o comm,ruid,%cpu' '-t1 10 1' '-f -pfc /var/db/*/*.{BS,Bas,Es,OSXU,Rem}*.bom' '{/,}L*/Lo*/Diag* -type f \( -exec grep -lq "^Thread c" {} \; -exec printf \* \; -o -true $ -execdir stat -f:%Sc:%N -t%F {} \;' '-L {/{S*/,},}L*/Lau* -type f' '-L /{S*/,}L*/StartupItems -type f -exec file {} +' '-L /S*/L*/{C*/Sec*A,E}* {/,}L*/{A*d,Compon,Ex,In,iTu,Keyb,Mail/B,P*P,Qu*T,Scripti,Sec,Servi,Spo}* -type f -name Info.plist' '/usr/lib -type f -name *.dylib' `awk "${s[31]}"<<<${p[23]}` "/e*/{auto_master,{cron,fs}tab,hosts,{launchd,sysctl}.conf} /usr/local/etc/periodic/*/* .launchd.conf" list getenv /Library/Preferences/com.apple.alf\ globalstate --proxy '-n get default' -I --dns -getdnsservers -getinfo\ "${p[N5]}" -P -m\ / '' -n1 '-R -l1 -n1 -o prt -stats command,uid,prt' '--regexp --only-files --files com.apple.pkg.*|sort|uniq' -kl -l );N1=${#c2[@]};for j in {0..8};do c2[N1+j]=SP${p[j]}DataType;done;N2=${#c2[@]};for j in 0 1;do c2[N2+j]="-n 'syscall::'${p[33+j]}':return {@out[execname,uid]=sum(arg0)} tick-10sec {trunc(@out,1);exit(0)}'";done;l=(Restricted\ files Hidden\ apps 'Elapsed time (s)' POST Battery Safari\ extensions Bad\ plists 'High file counts' User Heat System\ load boot\ args FileVault Diagnostic\ reports Log 'Free space (MiB)' 'Swap (MiB)' Activity 'CPU per process' Login\ hook 'I/O per process' Mach\ ports kexts Daemons Agents launchd Startup\ items Admin\ access Root\ access Bundles dylibs Apps Font\ issues Inserted\ dylibs Firewall Proxies DNS TCP/IP RSSI Profiles Root\ crontab User\ crontab 'Global login items' 'User login items' );N3=${#l[@]};for i in 0 1 2;do l[N3+i]=${p[5+i]};done;N4=${#l[@]};for j in 0 1;do l[N4+j]="Current ${p[29+j]}stream data";done;A0() { id -G|grep -qw 80;v[1]=$?;((v[1]==0))&&sudo true;v[2]=$?;v[3]=`date +%s`;clear;};for i in 0 1;do eval ' A'$((1+i))'() { v[0]=` eval "${c1[$1]} ${c2[$2]}"|'${c1[30+i]}' "${s[$3]}" `;[[ "${v[0]}" ]];};A'$((3+i))'() { v[0]=` while read i;do eval "${c1[$1]} ${c2[$2]}" \"$i\"|'${c1[30+i]}' "${s[$3]}";done<<<"${v[$4]}" `;[[ "${v[0]}" ]];};A'$((5+i))'() { v[0]=` while read i;do '${c1[30+i]}' "${s[$1]}" "$i";done<<<"${v[$2]}" `;[[ "${v[0]}" ]];};';done;A7(){ v[0]=$((`date +%s`-v[3]));};B2(){ v[$1]="${v[0]}";};for i in 0 1;do eval ' B'$i'() { unset v[0];((v['$((i+1))']==0))||{ v[0]=No;false;};};B'$((3+i))'() { v[$2]=`'${c1[30+i]}' "${s[$3]}"<<<"${v[$1]}"`;} ';done;B5(){ v[$1]="${v[$1]}"$'\n'"${v[$2]}";};B6() { v[0]=` paste -d: <(echo "${v[$1]}") <(echo "${v[$2]}")|awk -F: ' {printf("'"${f[$3]}"'",$1,$2)} ' `;};B7(){ v[0]=`grep -Fv "${v[$1]}"<<<"${v[0]}"`;};C0(){ test "${v[0]}"&&echo "$_";};C1() { [[ "${v[0]}" ]]&&printf "${f[$1]}" "${l[$2]}" "${v[0]}";};C2() { v[0]=`echo ${v[0]}`;[[ "${v[0]}" != 0 ]]&&C1 0 $1;};C3() { v[0]=`sed -E "${s[0]}"<<<"${v[0]}"`&&C1 1 $1;};for i in 1 2;do for j in 2 3;do eval D$i$j'(){ A'$i' $1 $2 $3; C'$j' $4;};';done;done;A0;{ A2 0 $((N1+1)) 2;C0;A1 0 $N1 1;C0;B0;C2 27;B0&&! B1&&C2 28;D12 15 37 25 8;A1 0 $((N1+2)) 3;C0;D13 0 $((N1+3)) 4 3;D22 0 $((N1+4)) 5 4;for i in 0 1 2;do D13 0 $((N1+5+i)) 6 $((N3+i));done;D13 1 10 7 9;D13 1 11 8 10;D22 2 12 9 11;D12 3 13 10 12;D23 4 19 44 13;D23 5 14 12 14;D22 6 36 13 15;D22 7 37 14 16;D23 8 15 38 17;D22 9 16 16 18;B1&&{ D22 11 17 17 20;for i in 0 1;do D22 28 $((N2+i)) 45 $((N4+i));done;};D22 12 39 15 21;A1 13 40 18;B2 4;B3 4 0 19;A4 14 6 11 0;B2 0 5;A1 17 41 20;B7 5;C3 22;B4 4 6 21;A4 14 7 11 6;B2 0 7;B3 4 0 22;A4 14 6 11 0;B2 0 8;B5 7 8;B1&&{ A2 19 26 23;B7 7;C3 23;};A2 18 26 23;B7 7;C3 24;A2 4 20 21;B7 6;B2 9;A4 14 7 52 9;B2 10;B6 9 10 4;C3 25;D13 4 21 24 26;B4 4 12 26;B3 4 13 27;A1 4 22 29;B7 12;B2 14;A4 14 6 52 14;B2 15;B6 14 15 4;B3 0 0 30;C3 29;A1 4 23 27;B7 13;C3 30;D23 24 24 32 31;D13 25 37 32 33;A1 23 18 28;B2 16;A2 16 25 33;B7 16;B3 0 0 34;B2 21;A6 47 21&&C0;B1&&{ D13 21 0 32 19;D13 10 42 32 40;D22 29 35 46 39;};D23 14 1 48 42;D22 0 $((N1+8)) 51 32;D13 4 8 41 6;D12 26 28 35 34;D13 27 29 36 35;A2 27 32 39&&{ B2 19;A2 33 33 40;B2 20;B6 19 20 3;};C2 36;D23 33 34 42 37;D22 32 31 43 38;D23 20 42 32 41;D23 14 2 48 43;D13 4 5 32 1;D22 4 4 50 0;D13 14 3 49 5;D23 22 9 37 7;A7;C2 2;} 2>/dev/null|pbcopy;exit 2>&-
Copy the selected text to the Clipboard by pressing the key combination command-C.
7. Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Click anywhere in the Terminal window and paste by pressing command-V. The text you pasted should vanish immediately. If it doesn't, press the return key.
8. If you see an error message in the Terminal window such as "syntax error," enter
exec bash
and press return. Then paste the script again.
9. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. In most cases, the difference is not important. If you don't know the password, or if you prefer not to enter it, press the key combination control-C or just press return three times at the password prompt. Again, the script will still run.
If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.
10. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, there will be nothing in the Terminal window and no indication of progress. Wait for the line
[Process completed]
to appear. If you don't see it within half an hour or so, the test probably won't complete in a reasonable time. In that case, close the Terminal window and report the results. No harm will be done.
11. When the test is complete, quit Terminal. The results will have been copied to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.
At the top of the results, there will be a line that begins with "Model Identifier." If you don't see that, but instead see a mass of gibberish, you didn't wait for the "Process completed" message to appear in the Terminal window. Please wait for it and try again.
If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.
12. When you post the results, you might see the message, "You have included content in your post that is not permitted." It means that the forum software has misidentified something in the post as a violation of the rules. If that happens, please post the test results on Pastebin, then post a link here to the page you created.
Note: This is a public forum, and others may give you advice based on the results of the test. They speak only for themselves, and I don't necessarily agree with them.
Copyright © 2014 by Linc Davis. As the sole author of this work, I reserve all rights to it except as provided in the Use Agreement for the Apple Support Communities website ("ASC"). Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

Time Machine problem after 10.6 upgrade

Hi Guys,
After I installed the snow leopard, I got a prompt regarding the time machine: "cancel backup" "create new backup" "replace backup". I clicked on "create new backup" but that seemed to have been the wrong choice. The time machine said that the last backup was November 28 2008, despite me backing up data every hour since November 28. My question is:
Have I lost all the data between now and Nov. 2008? Is there anyway to access it?
Second, can I resume backing up as before instead of the new back up I accidentally created?
Thanks.

valoo wrote:
I deleted the newly created sparsebundle. I also realized that the computer name had been changed and I changed it back to the original one. Here's the new problem. The TM says that I only have 127 GB and the amount of space needed to back up the disk is 140GB. I don't understand. It almost seems like it is trying to duplicate the entire backup. And this time around, I don't even see any new sparsebundle. I am stuck here.
Something caused TM to decide to start a new "sequence" of backups, as if you'd gotten a new Mac. That means a new, full backup to start with. The only thing that seems to have worked for some folks is a Restart. So if you haven't done one since the latest changes and failed backup attempt, it's worth a try.
If it still wants to do a full backup, you can't prevent it.
Depending on how much space you have on the TM drive/partition, your only choice may be to delete the "old" sparse bundle and let TM start over.
You may be able to delete some of the older backups to make room for the new, full backup, but that's tedious and time-consuming (see item #12 of the Frequently Asked Questions *User Tip.)*
But that still leaves two problems: you'll have to manually "compact" the sparse bundle via Terminal to shrink it; and you'll have to continue to delete old backups this way (and manually compact them) to make room for new ones. Since TM is treating them as if they were from a different Mac, it won't delete them automatically, but will delete the oldest backups from the new set instead.

MacBookPro ****. iPhoto (Time Machine) Problems

I took my MacBook Pro in to the Genius Bar and it was sent to the Depot for a new logic board. I was told to use Time Machine to 'restore/reload' everything. OK. I did.
Then iTunes and iPhoto would not work. Based on the error I got, I think what they loaded when they reloaded the OS was newer than what I had before their work (but still Snow Leopard - 10.6.8.) So I checked for updates and about 8 or 9 things needed updating. So I did.
Well, now I have two problems
iPhoto has lost *many* thumbnails. (Everything else is '09 but iPhoto is now '11 for some reason.) I'm trying to open GarageBand for the first time now. (it's '11 now too.) If I seem confused, it's because the paperwork for repair said that I had '09. I questioned this and was told that I was wrong, I didn't have iLife '11. Perhaps I was right all along.
Anyway, I tried the Alt+cmd when opening and selecting the restore thumbnail options. That DID NOT work.
I'm hesitant to try Time Machine again.
My Time Machine says that this backup was done on a different machine and do I want to use it. (Of course, everything, iTunes, Facebook,etc thinks I am on a new computer.) So I just declined to go any farther before I cause a bigger mess.
Please help me. I have projects that I need the photos for and I need to back up while I am working on that and other things.
Does any one know what to do. To get into this mess, it took 3 trips to the Genius Bar 15 miles and crazy traffic away and 2 calls to Apple Support. Seems there isn't one Genius who is especially rounded and knows more than one area. I need a fully functioning MacBook Pro in *all* areas.
Thank you to anyone that can help.

Please don't think people are ignnoring you. If they are like me, they read your problem and were unable to come up with a solution to help you. It may take a few hours or even a few days before someone comes along that can assist you. I feel your pain, feeling completly helpless and anxiously awaiting a fix. We do have very knowledgable Time Machine users in here. What I can do is direct you to this website, created by a user in here who is one of those very knowledgeable about Time Machine. : http://pondini.org/OSX/Home.html. I hope he or someone else comes along soon to help you. Good luck.

Another Time Machine problem after 10.5.3 update

OK, I have another problem, that I haven't seen listed here. Time Machine will no longer back up my MacBook Pro after the 10.5.3 update. The error message I get in the Console log is:
6/1/08 3:44:42 PM /System/Library/CoreServices/backupd[1395] Volume at path /Volumes/Dave's backup does not appear to be the correct backup volume for this computer. (Cookies do not match)
How do I change the cookies for my backup disk?
Thanks in advance.

I believe I have isolated the problem as a permissions issue which I have logged as bug 5990628:
Summary:
Unable to backup over network after upgrading to 10.5.3.
Steps to Reproduce:
Configure Time Machine to back up Leopard machine over AirPort to another Leopard machine (with external drive and .Mac account configured in this case)
Expected Results:
Backups complete as usual.
Actual Results:
Backups are 'Delayed' with errors like this in the console:
6/6/08 4:25:57 AM /System/Library/CoreServices/backupd[2334] Volume at path /Volumes/Time Machine-1 does not appear to be the correct backup volume for this computer. (Cookies do not match)
Regression:
Yes
Notes:
There are many threads on the subject:
http://discussions.apple.com/thread.jspa?threadID=1538633
http://discussions.apple.com/thread.jspa?threadID=1543033
http://discussions.apple.com/thread.jspa?threadID=1547134
http://discussions.apple.com/thread.jspa?threadID=1546079
The problem appears to relate to being unable to read the cookie:
6/6/08 4:20:23 AM System Preferences[2315] Failed to create remote cookie file at path: /Volumes/Time Machine/.001b63abcdef
And this appears to be because the cookie was owned by a different user (likely due to it wanting to connect using a .Mac username instead of a local one), per my explanation below:
I only ever used Time Machine after upgrading to 10.5.3 so my first experience with it has been fairly ordinary, as the backups were constantly being 'Delayed' with this error in the Console:
6/6/08 4:25:57 AM /System/Library/CoreServices/backupd[2334] Volume at path /Volumes/Time Machine-1 does not appear to be the correct backup volume for this computer. (Cookies do not match)
The first thing I discovered from a blog post was that my .Mac 60 day trial was causing it to connect using my .mac username (which appeared in the username field in the UI as a string of hex characters); disconnecting and reconnecting using a local user seemed to work but the issue remained.
I then spotted this in the console:
6/6/08 4:20:23 AM System Preferences[2315] Failed to create remote cookie file at path: /Volumes/Time Machine/.001b63abcdef
The 'random' characters are your MAC address and the binary inside is likely this 'cookie' - a random value used to transparently and reliably link backups to machines. Curiously I couldn't modify this file over the network despite apparently owning it (in Terminal):
$ cd /Volumes/Time\ Machine
$ ls -la .00*
-r-------- 1 samj staff 16 Jun 6 04:33 .001b63abcdef
But when looking at it on the Mac Mini 'server' I saw that the owner was in fact another user:
-r-------- 1 otheruser staff 16 Jun 6 04:33 .001b63abcdef
So I ran these commands:
sudo chown samj .001b63abcdef
sudo chgrp staff .001b63abcdef
And sure enough I was able to configure Time Machine as expected and it is as we speak backing up my MacBook over Airport to a USB drive attached to my Mac Mini.
Cheers,
Sam
Sam Johnston
Australian Online Solutions
http://www.aos.net.au/

Mavericks Drobo Time Machine problem

On a new iMac with Mavericks, a new (December) Drobo 5D, I get "Time Machine couldn't . . " "Unable to complete backup. An error occurred while creating the backup folder." Disk Utility says everything is OK. Drobo diagnostics (submitted to Drobo Support) apparently show no problems. "Not seeing any issues in the diagnostic file you submitted. No disconnections and no drive issues. Looks clean."
If I reboot, Time Machine works fine. Time Machine backup works fine. Everything seems fine.
Today is the fourth time in three weeks the problem has appeared.
Where does the responsibility for this lie? With Drobo or Apple? Neither side shows a problem. I am feeling frustrated.

Thank you, Norm G.
This "An error occurred while creating the backup folder" is not addressed by that support article. The problem has occurred with both Thunderbolt and USB-3 cables. Restarting currently seems to be the solution.
The Drobo replaces a LaCie 4TB drive that is full; this problem never occurred with that drive. The Drobo was formatted and set-up following Drobo instructions. Drobo has no suggestions since the diagnostics don't show a problem on their end.
So far, I can live with the restarting - since everything else functions normally.

Time Machine problems since upgrading to Snow Leopard

After Time Machine completes the backup I'm unable to do anything! Icons on the desktop disappear. I'm not able the drag the backup drive to the trash. I reboot and it says it did the most current backup but when I enter Time Machine it doesn't recognize the latest backups. Even though the dates appear showing they were backed up you can't access them.

Barry I tried you recommendations except the OS X 10.6 install and it didn't work.
I did come across this in another apple support area:
The most common cause is the TM drive (but not a Time Capsule) not being formatted correctly (even, on occasion, if TM formatted it!). Use Disk Utility (in your Applications/Utilities folder) to verify the setup:
First, select the second line for your internal HD (usually named "Macintosh HD"). Towards the bottom, the Format should be Mac OS Extended (Journaled), although it might be Mac OS Extended (Case-sensitive, Journaled).
Next, select the line for your TM partition (indented, with the name). Towards the bottom, the Format must be the same as your internal HD (above). If it isn't, you must erase the partition (not necessarily the whole drive) and reformat it with Disk Utility.
Sometimes when TM formats a drive for you automatically, it sets it to Mac OS Extended (Case-sensitive, Journaled). Do not use this unless your internal HD is also case-sensitive. All drives being backed-up, and your TM volume, should be the same. TM may do backups this way, but you could be in for major problems trying to restore to a mis-matched drive.
Last, select the top line of the TM drive (with the make and size). Towards the bottom, the Partition Map Scheme must be either GUID (preferred) or Apple Partition Map for an Intel Mac. It must be either Apple Partition Map (preferred) or GUID for a PPC Mac. If this is wrong, you must completely erase the disk and reformat it. See item 5 of the Frequently Asked Questions User Tip at the top of this forum.<<<
Barry, I've noticed that my hard drive is indeed "Journaled" and my backup drive is "Case Sensitive, Journaled." So therefore I'm presuming I do in fact need to erase my backup drive and reformat it. Am I correct in this assessment?

Mountain Lion time machine problems.

Not long after updating to Mountain Lion, my time machine backups started failing. When attempting to backup, it is getting stuck at the "looking for backup disk..." phase and causing my computer to freeze.
To clarify, for at least a few days I had routinely completed a number of backups using time machine after the initial upgrade to Mountain Lion, so I don't think it is a problem with indexing a new backup etc.
Suggestions? Thanks.

Ha, yep, I've been poking around on pondini.org/TM but haven't yet found anything on being stuck at "looking for backup disk..."
Found a discussion of a similar problem when going from 10.6 to 10.7 here: http://lime-technology.com/forum/index.php?topic=13852.0. It sounds like after waiting 45 minutes or so the backup disk was finally found and the problem was resolved. I'm going to let it run for as long as possible and see what happens...

Can't see my 3TB lacie external drive (for Time Machine)

since upgrading to Yosemite my Time Machine backup won't operate, says the drive is Read Only.
Don't see where I can change this, I have verified and run repair and looks good but still no Time Machine backups will function, last successful one was with Mavericks before moving to Yosemite.
It is a Lacie 3TB external drive, worked flawlessly in Mavericks.
I can't see it in the Finder , but I know computer communicates with it because I could run Disk Utility and see the drive.

I restarted the computer and then Time Machine backup worked.

Time Machine problem. Has stopped working for no apparent reason

I've been using Time machine for nearly a year now and have had no problems until recently. Now it will not complete back up and returns with error could not write file.
I have repartioned the backup drive and have no problems writing files to it outside of TM.
The error log shows
02/11/2009 12:05:35 com.apple.launchd[1] (com.memeo.Memeod[9340]) posix_spawnp("/Library/Application Support/Memeo/Memeo LifeAgent/Daemons/Memeod", ...): No such file or directory
which looks like if can't find a Daemon it needs.
Can anyone point me in the right direction to fix this?
Many thanks

Pondini wrote:
That's not the right message. Start with the Time Machine - Troubleshooting *User Tip* at the top of this forum.
It will show you how to locate the message(s) that describe the problem, then help you fix it.
If that doesn't help, post back with details, including all the messages, your setup (especially the destination for the backups), what you've done, and the results.
The message error was "error occurred while copying files to the backup volume"
Thanks for pointing out the Time Machine troubleshooter which led me to Time Machine buddy and from there I had easy access to the detailed Time Machine logs.
A particular directory was not being copied,
Error: (-36) SrcErr:YES Copying /Users/tony/Documents/Microsoft User Data/Office 2004 Identities/Main Identity/Database to (null)
Error: (-36) SrcErr:NO Copying /Users/tony/Documents/Microsoft User Data/Office 2004 Identities/Main Identity/Database to /Volumes/TimeMachine/Backups.backupdb/Tonys-Mac/2009-11-02-104550.inProgress/F2 6B6F3A-726A-4AFD-8A30-3F341BCC2CA3/Macintosh HD/Users/tony/Documents/Microsoft User Data/Office 2004 Identities/Main Identity
Stopping backup.
I removed the direcotry from the back up using Time Machine prefs and reran the backup which then went smoothly.
Thanks for your help

HT201250 Backup using lacie external drive with time machine

Hi, I recently backed up my macbook with a lacie external hard drive using time machine. However, when i try to open my photos, which says there is 11.67GB there, nothing happens. It only opens an empty file. After my backup i deleted the photos from my laptop, after all i was trying to clear disc space on my macbook. Can i resolve this or can i open the file in a different way? Help

One should always confirm copied stuff is where they think it is before deleting the original stuff. See Pondini's TM FAQs, for starters.

LaCie "Eco Mode" causing Time Machine problems

Similar Messages

Maybe you are looking for