"Waiting for index to be ready (905 0)"

The behavior of TM (and also Time Capsule) seems to have deteriorated significantly since I did the latest TC firmware upgrade. I realize this is the TM forum and that is the basis of this question, but the revised TC is much more difficult to be seen by the TM process since the upgrade and thus results in many failed or unfinished TM backups.
TM has failed in the last three attempts and seems to have fallen into a loop. The log of the atempt before the current one shows the following:
Starting standard backup
Mounted network destination using URL: afp://[email protected]/Data
Backup destination mounted at path: /Volumes/Data
Disk image /Volumes/Data/MacBook3_001b63af0352.sparsebundle mounted at: /Volumes/Backup of MacBook3
Backing up to: /Volumes/Backup of MacBook3/Backups.backupdb
Event store UUIDs don't match for volume: Backup of MacBook3
Node requires deep traversal:/Volumes/Backup of MacBook3 reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|
No pre-backup thinning needed: 736.8 MB requested (including padding), 468.91 GB available
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Waiting for index to be ready (905 > 0)
Stopping backupd to allow ejection of backup destination disk!
Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
Copied 0 files (0 bytes) from volume Macintosh HD.
Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
Error writing to backup log. NSFileH
.... at which point, I guess the sleep timer kicked in.
The current backup attempt has the same initial messages and is presently looping on "Waiting for index to be ready (905>0)".
Any help and advice much appreciated.

travellerva wrote:
When you say "disk problems", do you mean hardware problems, firmware problems or software problems?
On directly-attached disks, we see this when the disk spins down, but won't spin back up fast enough or properly; or with a USB disk that gets its power from the Mac, but not quite enough sometimes; or port or cable problems; or one that's beginning to fail. It's very hard to tell, of course, which.
I'm not very familiar with TCs, but a disk is a disk!

Similar Messages

  • Time Machine error : Waiting for index to be ready (100)

    Hello,
    I'm having issues with Time Machine, the backup starts, an amount of data is backup and complete (ex 80Mb of 80Mb backuped up), then Time Machine goes back in indexing and get stuck in "Waiting for index to be ready (100)".
    Here's what the console output for backupd looks like:
    02/12/10 10:37:46 com.apple.backupd[213] Starting standard backup
    02/12/10 10:37:46 com.apple.backupd[213] Attempting to mount network destination using URL: afp://[email protected]/tm-pedral
    02/12/10 10:37:48 com.apple.backupd[213] Mounted network destination using URL: afp://[email protected]/tm-pedral
    02/12/10 10:37:48 com.apple.backupd[213] Warning: Destination /Volumes/tm-pedral does not support Server Reply Cache
    02/12/10 10:37:55 com.apple.backupd[213] QUICKCHECK ONLY; FILESYSTEM CLEAN
    02/12/10 10:37:59 com.apple.backupd[213] Disk image /Volumes/tm-pedral/pedral-mac_34159e0fb504.sparsebundle mounted at: /Volumes/Time Machine Backups
    02/12/10 10:37:59 com.apple.backupd[213] Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
    02/12/10 10:38:20 com.apple.backupd[213] No pre-backup thinning needed: 795.5 MB requested (including padding), 357.72 GB available
    02/12/10 10:41:07 com.apple.backupd[213] Copied 1842 files (79.2 MB) from volume Macintosh HD.
    02/12/10 10:41:07 com.apple.backupd[213] No pre-backup thinning needed: 716.5 MB requested (including padding), 357.72 GB available
    02/12/10 10:41:07 com.apple.backupd[213] Waiting for index to be ready (100)
    02/12/10 10:42:09 com.apple.backupd[213] Waiting for index to be ready (100)
    02/12/10 10:43:11 com.apple.backupd[213] Waiting for index to be ready (100)
    02/12/10 10:44:13 com.apple.backupd[213] Waiting for index to be ready (100)
    02/12/10 10:45:15 com.apple.backupd[213] Waiting for index to be ready (100)
    02/12/10 10:46:17 com.apple.backupd[213] Waiting for index to be ready (100)
    This backup-up has been working for days in the same conditions.
    I've tried everything in #D2 in Time Machine - Troubleshooting but nothing changed. How to get more details on what's happening.
    Thanks!
    Laurent

    pedral wrote:
    Hello,
    Hi, and welcome to the forums.
    02/12/10 10:37:48 com.apple.backupd[213] Warning: Destination /Volumes/tm-pedral does not support Server Reply Cache
    What are you backing-up to? That message indicates it may not be fully compatible with Time Machine.
    If you've done everything in #D2, and it's a NAS, check with the maker. They may have updates or other troubleshooting info. Or it may be a hardware problem.

  • Time Machine hangs at Waiting for index to be ready...help!

    Installed widget, copied messages. Searched forum and google for answers, still can't figure it out.
    Any ideas? - Thanks, Paul
    Starting standard backup
    Attempting to mount network destination using URL: afp://Paul%[email protected]/Time%20Capsule
    Mounted network destination using URL: afp://Paul%[email protected]/Time%20Capsule
    QUICKCHECK ONLY; FILESYSTEM CLEAN
    Disk image /Volumes/Time Capsule/Paul's Mac_001f5bf5d5b8.sparsebundle mounted at: /Volumes/Backup of Paul's Mac
    Backing up to: /Volumes/Backup of Paul's Mac/Backups.backupdb
    Event store UUIDs don't match for volume: Macintosh HD
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)

    Okay, still no progress on getting my Time Machine working again. The last backup was 12/2, so I've been trying for 4 days to get it going. Any other ideas?
    Starting standard backup
    Network destination already mounted at: /Volumes/Time Capsule
    QUICKCHECK ONLY; FILESYSTEM CLEAN
    Disk image /Volumes/Time Capsule/Paul's Mac_001f5bf5d5b8.sparsebundle mounted at: /Volumes/Backup of Paul's Mac
    Backing up to: /Volumes/Backup of Paul's Mac/Backups.backupdb
    Event store UUIDs don't match for volume: Macintosh HD
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)

  • Stuck on calculating changes - Waiting for index to be ready

    I've got a Time Machine which had my disk properly backed up (~500 Gigs). Then, I used Entourage Time Machine to save my email database to a set of local XML files (tens of thousands of new files). Since then, it's stuck on Calculating Changes; I tried stopping it, removing the .plist file, stopping/restarting the service, etc. I restarted it again and now it's once again on Calculating Changes for 12 hours now. Time Machine Buddy says "Waiting for index to be ready". Could it possibly really be doing what it needs to do or is it stuck somehow and is there anything else I can do??
    thanks in advance,
    Mike

    Michael Levin wrote:
    Then verify your internal HD and repair your backups, per #A5 in Troubleshooting.
    did that - repaired the disk, no problems found.
    Uh, you need to check your internal, too, if you didn't. It's probably ok, but it's best to be sure. Then Restart your Mac.
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    Waiting for index to be ready (100)
    A few of those may not be a problem, especially after a failed backup. The backups have to be indexed for TM to work right.
    why isn't the index ready - could it have anything to do with Spotlight (which is also going like mad, but at least now gives a time estimate) - is that the index it's talking about??
    Perhaps. Both Spotlight and Time Machine use the mds process to index.
    |
    Ok, so I disabled Spotlight, deleted all the .Spotlight files on all volumes, and restarted Time Machine having excluded the Entourage database and 56 Gigs worth of .xml files of individual messages.
    56 GB? Holy moley!
    Event store UUIDs don't match for volume: Main Internal Drive (Leopard)
    Forcing deep traversal on source: "Main Internal Drive (Leopard)" (mount: '/' fsUUID: 22E61BEA-43E3-3C1C-985D-4589FACE5629 eventDBUUID: D2A7E78E-C39A-46A3-B273-CCEE5048369C), {1, 1, 1, 0}
    Node requires deep traversal:/ reason:must scan subdirs|require scan|
    Normal after a failed backup; Time Machine's not sure what was where when the "lights went out," so has to compare everything on your system to the backups to figure out what needs to be backed-up.
    No pre-backup thinning needed: 24.38 GB requested (including padding), 983.14 GB available
    The deep traversal completed. It found about 20 GB to back up (plus 20% for workspace -- the "padding" in the message).
    Error: Flushing index to disk returned an error: 0
    That's another problem writing the index to the TM drive.
    Try a +*Repair Disk+* on it again, and make sure all connections are snug and secure, and try the backup again.
    If this continues, it's beginning to look like a problem with the disk or connections. Try different ports, cables, and combinations of the two -- cables do deteriorate, and a plug that works fine in one port may not make good contact in another one.

  • Stuck on waiting for device to become ready...

    I did a slide show on iDVD now I'm trying to burn it on a Phillips dvd but it reads waiting for device to become ready. this continues & it does not burn the dvd. I tried the save as disk image but the same thing happens. the utility was no help on getting it started

    Hi Don't:
    Just assuming here (which is always dangerous)...
    Is there any audio associated with your slideshow?
    Sue
    PS Verbatim DVD-R (you are using DVD-R, right?) is about the best there is....

  • [Restore] "Waiting for iPod to become Ready"? [ver 1.2 iTunes 7.0]

    I just updated my iTunes from version 6.0.5 to 7.0. This install also updated my iPod. My iPod is no longer read by my computer or any other. ***? Now when I attmept to connect it to any Mac it freezes up and fails to mount. Come on apple. Also, why the is there no longer an iPod preference section in the new iTunes. I keep trying to Restore the firmware, but I keep getting the "Waiting for iPod to become ready" message.
    Attempted solutions:
    • Re-installing iTunes 7.0 (no luck)
    • Resetting the iPod (no luck)
    • Forcing the iPod into disk mode (no luck)
    • Re-installing iPod software (iPod won't mount...so that didn't work)
    HELP!!!

    You may want to look at this:
    http://docs.info.apple.com/article.html?artnum=61705
    You may want to look at this:
    http://docs.info.apple.com/article.html?artnum=61705
    I had the same problem and was able to fix it by following the directions on resetting the iPod, renaming the iPod and also ensuring that I removed any files that might not be understood by the iPod from the 'notes' folder on the iPod (if you have enabled disk access):
    http://discussions.apple.com/message.jspa?messageID=3111498#3111498
    PS: If you need to get out of the 'Do not disconnect' screen so that you can apply these changes you need to hold down the 'menu' and 'select' or center button until you see the Apple logo. When the iPod mount you can proceed to reset the iPod to original settings which will erase everything from the iPod but not your iTunes library on your computer

  • "Waiting for device to become ready" can't burn additional copies

    I created an iMovie and burned about six copies on iDVD. When i went to put in the seventh disk it sort of froze up with the "Waiting for device to become ready" message never going away. I attempted to shut everything down, even turned the computer off for awhile thinking maybe it was overheated but several hours later its doing the same thing. It will burn the first copy but get hung up when attempting to burn additional ones. Any suggestions???

    It's often recommended areound here to let the optical drive cool down after burning 3-4 disks in a row.
    See if you can burn any kind of disk via the Finder to make sure the drive is OK.  Also I suggest you follow this workflow for future projects:
    Once you have the project as you want it save it as a disk image via the  File ➙ Save as Disk Image  menu option.  This will separate the encoding process from the burn process. 
    To check the encoding mount the disk image and launch DVD Player and play it.  If it plays OK with DVD Player the encoding was good.
    Then burn to disk with Disk Utility or Toast at the slowest speed available (2x-4x) to assure the best burn quality.  Always use top quality media:  Verbatim, Maxell or Taiyo Yuden DVD-R are the most recommended in these forums.
    The save as disk image as mishmumken recommended will save you from having to reencode the project if you want to burn another copy at a later date.  It also lets you verify the encoding process before committing the project to disk.
    OT

  • Time Machine hang- Waiting for Index to become available (100)

    Hi- I'm trying to create a new Time Machine backup to a new external HD (FW800). I've formatted the drive as Mac OS Extended and told TM to use this as the backup drive. I should note that I've done TM backups in the past with a different drive which was a USB2.0 drive, but just got this FW800 and thought it would be much faster to use.
    Anyway, now I'm getting the dreaded 'Waiting for Index to become available (100)' message from the TM buddy widget. This keeps repeating every few seconds. I let it run overnight and about 14 hours later, TM backed up 6G from a 150G total. As I watched the backup run, it's copying over about 1M every few minutes. How can this be? I've read through some of the forum entries and I tried placing the external drive in the Spotlight exclusion, and I also uninstalled any traces of Norton that I had installed. Nothing is making this backup go any faster.
    So why in the past, has the first backup run fairly quickly, and now this is running like it will take several days to complete?
    Please- any help will be greatly appreciated!! thanks.

    BrianMBM wrote:
    As far as the communication issue, the external drive mounts just fine, and I can access it in the finder, so I don't believe physical connection is the culprit here.
    Not necessarily. A marginal connection may work, but with lots of retries, resulting in things being quite slow. It's fairly rare, but can happen.
    I just don't understand why just months ago, the first TM backup started right away and now this is taking forever- Is this a change that was released in an update from Apple in how TM works?
    No. In fact, they're supposed to be somewhat faster on Snow Leopard.
    How can I delete every trace of previous TM backups and completely start from scratch?
    You can erase the drive. If you're going to do that anyway, you might as well reformat it, with the GUID *Partition Map Scheme.* APM should work fine, but if you ever want to use it as a boot drive, GUID is preferred for an Intel Mac.
    There's obviously something that's causing this indexing thing to take so long that's never happened in the past.
    Try the reformat. (You'll probably have to exclude it from Spotlight again.)
    Is it a multi-interface drive? If so, try connecting via USB temporarily.
    If that doesn't help, try just copying a large file or folder and see how fast it is. If that's slow, too, you know it isn't Time Machine but something else associated with your F/W card, port, cable, or drive.

  • "waiting for device to become ready" then ejects

    Hello,
    I have two music videos set up as chapters and am trying to burn a DVD with this.
    Everything plays fine when "reviewing" then when I hit "burn dvd" it asks for a recordable disc. I put in a DVD-R disc, which has plenty of room on it, and it accepts it. Then is says "waiting for device to become ready" spins it around, stops it, spins it around, stops it, and ejects the disc and says "no disc in drive. please insert a recordable disc".
    Yes, I have a DVD superdrive that can burn DVDs. I do not understand what is going on!!!

    says "no disc in drive. please insert a recordable disc"
    Either your media is bad or your burner is bad.
    Are you certain the media has never been used? What brand and rated burn speed is the media? To test the media and the burner independent of iDVD, try burning a data DVD from the finder.
    F Shippey

  • Hangs at "verifying identity" or "waiting for network to be ready"

    We have an older computer that we would like to use and connect to the internet, but it won't connect through the Jetpack 890L. We have Windows XP Home version 2002, svc pk 2. It will just hang and show the messages above. I have researched and tried several different settings in advanced settings, and received a few different messages. I am afraid our computer may just be too old. At one point I tried "repairing the connection" button and received messages something like "be sure your network adapter is properly connected" -- Atheros 5005g, 2005 version 4.1.2.56-- old! Any suggestions? We are not tech savvy, but thought someone may be able to help us stumble through. Thanks for any help!

    WinXP displays the verifying identity message when it cannot fully authenticate to the network.  Most of the time this is because you are connecting over a WiFi security protocol that is not supported by your computers wireless card.  To resolve the problem you need to select a different security mode or update your wireless card to one that supports the features of your jetpack.
    If you try all of the available security modes (open/WEP/WPA/WPA2) and the problem is not resolved then it is most likely a password conflict.  Wipe out your saved passwords/wireless profiles on XP and start over.
    This same logic applies to the waiting for network to be ready message.

  • Satellite L300-29U hangs at waiting for ODD to become ready

    I sell Toshiba's.
    I always make recovery dics for my customers. I do it on Philips DVD's.
    Now I have tried Windows 7 on one positively and tried to recover to vista again before selling the laptop.
    The problem is that when I try to recover, the system hangs at "waiting for ODD to become ready "
    I tried several things,
    -formatting the harddisk
    -removing the partition
    -windows vista oem CD (installs fine, so does 7) etc etc.
    I have another laptop in stock so I used the recovery discs of that one, result is that it hangs at the same point.
    Now I tried to restore the other laptop (same model) and there the recovery dvd hangs at the same point.
    I think there is an programming error in the recovery dvd program.
    Greets,
    Vincent
    Holland

    Not a chance.
    Toshiba is sending out an update for the imaging program because they found out it did not work themselves.
    Now just wait for the helpdesk to send out free copies for the people who burnt themselves faulty rescue dvd's?

  • How to get OIM workflow waiting for a task successfully completed?

    The requirement is to get OIM provisiong workflow pending and wait for a external status ready. When the external status not ready, I return "REJECTED" which mapped to "P" in "Task->Reponse" tab. Meanwhile, in the "Task->General" tab, I set the "Retry Count" to 5 and "Retry Period in Minutes" to 1.
    I have hoped that once the task return "REJECTED", the workflow enter status "Pending". One minute later, the task re-instanced by OIM to have another check for whether the external status ready. If ready, return "COMPLETED". If not yet, return "REJECTED" and workflow re-enter pending. And on and on, until to max to 5 times attempt. But in fact, OIM workflow never attempt to re-enter the task again after the 1st time "REJECTED" returned.
    How to do with this?

    Use the code snippet below to get the task status. Based on this you can filter rejected tasks.
    userintf = (tcUserOperationsIntf) ioUtilityFactory.getUtility("Thor.API.Operations.tcUserOperationsIntf");
    provintf = (tcProvisioningOperationsIntf)ioUtilityFactory.getUtility("Thor.API.Operations.tcProvisioningOperationsIntf");
    long userKey=100;
    tcResultSet userresultSet = userintf.getObjects(userKey);
    for(int i=0;i<userresultSet.getRowCount();i++)
         userresultSet.goToRow(i);
         long processKey = userresultSet.getLongValue("Process Instance.Key");
         tcResultSet provresultSet = provintf.getProcessDetail(processKey);
         for(int j=0; i<provresultSet.getRowCount();j++)
              provresultSet.goToRow(j);
              String taskName = provresultSet.getStringValue("Process Definition.Tasks.Task Name");
              String taskStatus = provresultSet.getStringValue("Process Instance.Task Details.Status");
    Let me know if you have any queries...

  • Waiting until a process is 'ready'.

    Basically, in my application I have to start a process (a server to be precise), wait for it to be ready and then run a program which connects to it. The problem is the server doesn't give any output when it's ready. It gives some output, but then looking at the CPU usage I can see it grinds for half a minute or so and then it's ready. I tested it and for the other process to connect the server must be 'ready' (ie. stopped using huge amounts of processing power).
    There are no paramaters or anything to make the server output more info so I can't do it by reading output. The only way I can think of doing it is to keep trying to connect to the server and then when it's ready it will work, but I'd rather do it differently for other error/exception reasons.
    Can anyone think of a way I could make my program wait until the processing has stopped to continue? Thanks.

    most servers write into a logfile during startup. If
    you know that file, your program can wait until no
    more changes are done to this logfile.This implies that the client has to wait (no more changes made to the logfile). Wouldn't it be
    simpler then to attempt to connect, wait, say 30 seconds if the attempt failed and try again?
    The OP wrote that the server can be up after 30 seconds of whatchamacallit, so, say, five
    retries with a sleep of 30 seconds would be adequate, don't you think?
    kind regards,
    Jos

  • IPhone: Stuck on "Waiting for device to connect.."

    I just had to reinstall the latest 2.0 build after something trashed my iPod Touch, and now I can no longer install software on it. I get the very non-specific "Waiting for device to become ready in 5 seconds". When that expires, nothing happens.
    Any ideas?

    Found it: Something in xcode got confused. Rebooting the machine got things talking to each other again.

  • [Solved] Wait for external usb disk before mounting partition

    Hello,
    I have a fresh setup where 3 btrfs subvolumes are supposed to be mounted on /var /home and /opt. Those subvolumes are on an external usb drive (root fs is on a sd card).
    During boot, systemd tries to mount /var first but encounter "var not empty, mounting anyway" (probably due to several boot attempts) and then "special device uUID=12f15a3e-cf5c-4bc2-9475-6b4686a30f90 does not exist" where 12f15a3e-cf5c-4bc2-9475-6b4686a30f90 is the correct id of the drive.
    From journactl extract it seems that usb drive is not ready yet when /var is being mounted.
    Is there a way to make systemd wait for "the disk is ready" before trying to mount /var ?
    Information:
    - mounting /var in rescue mode works perfectly (mount -o subvol=var /dev/sda /var)
    - device is a raspberry but I think it has no link to the issue (except maybe being slow to send power to usb)
    - the usb drive is behind a 4 port usb hub (externally powered)
    - the usb drive indeed take some time to be powered up
    - /home and /opt are mounted in rescue mode automatically a few seconds later
    journatctl wrote:Jan 01 01:00:07 capodimonte systemd[1]: Starting Local File Systems (Pre).
    Jan 01 01:00:07 capodimonte systemd[1]: Reached target Local File Systems (Pre).
    Jan 01 01:00:07 capodimonte systemd[1]: Mounting /var...
    Jan 01 01:00:07 capodimonte systemd[1]: var.mount: Directory /var to mount over is not empty, mounting anyway.
    Jan 01 01:00:07 capodimonte systemd-udevd[138]: starting version 218
    Jan 01 01:00:07 capodimonte mount[139]: mount: special device uUID=12f15a3e-cf5c-4bc2-9475-6b4686a30f90 does not exist
    Jan 01 01:00:07 capodimonte kernel: scsi 0:0:0:0: Direct-Access     Inateck                   0001 PQ: 0 ANSI: 6
    Jan 01 01:00:07 capodimonte kernel: sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
    Jan 01 01:00:07 capodimonte kernel: sd 0:0:0:0: [sda] Write Protect is off
    Jan 01 01:00:07 capodimonte systemd[1]: var.mount mount process exited, code=exited status=32
    Jan 01 01:00:07 capodimonte kernel: sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
    Jan 01 01:00:07 capodimonte kernel: sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
    Jan 01 01:00:07 capodimonte systemd[1]: Failed to mount /var.
    Jan 01 01:00:09 capodimonte kernel:  sda: unknown partition table
    Jan 01 01:00:09 capodimonte kernel: sd 0:0:0:0: [sda] Attached SCSI disk
    Jan 01 01:00:09 capodimonte kernel: random: nonblocking pool is initialized
    Jan 01 01:00:09 capodimonte kernel: BTRFS: device label external_hdd devid 1 transid 24 /dev/sda
    Jan 01 01:00:09 capodimonte systemd[1]: Found device NS1066 external_hdd.
    Jan 01 01:00:09 capodimonte systemd[1]: Mounting /home...
    Jan 01 01:00:09 capodimonte systemd[1]: Mounting /opt...
    Jan 01 01:00:09 capodimonte kernel: BTRFS info (device sda): enabling auto defrag
    Jan 01 01:00:09 capodimonte kernel: BTRFS info (device sda): disk space caching is enabled
    Jan 01 01:00:09 capodimonte kernel: BTRFS: has skinny extents
    Jan 01 01:00:09 capodimonte systemd[1]: Mounted /home.
    Jan 01 01:00:09 capodimonte systemd[1]: Mounted /opt.
    Jan 01 01:00:09 capodimonte systemd[1]: Startup finished in 5.088s (kernel) + 4.607s (userspace) = 9.696s.
    My fstab:
    # /dev/mmcblk0p3
    UUID=4660fa0a-bcf6-4d83-b956-d7bf9df222b9 / ext4 rw,relatime,data=ordered 0 1
    # /dev/sda LABEL=external_hdd
    UUID=12f15a3e-cf5c-4bc2-9475-6b4686a30f90 /home btrfs rw,relatime,space_cache,noatime,compress=lzo,autodefrag,subvol=home 0 0
    # /dev/sda LABEL=external_hdd
    uUID=12f15a3e-cf5c-4bc2-9475-6b4686a30f90 /var btrfs rw,relatime,space_cache,noatime,compress=lzo,autodefrag,x-systemd.device-timeout=30s,subvol=var 0 0
    # /dev/sda LABEL=external_hdd
    UUID=12f15a3e-cf5c-4bc2-9475-6b4686a30f90 /opt btrfs rw,relatime,space_cache,noatime,compress=lzo,autodefrag,subvol=opt 0 0
    # /dev/mmcblk0p1
    UUID=95DB-C13B /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro 0 2
    Last edited by kamaradclimber (2015-03-12 19:25:40)

    Thanks for your reply.
    I don't see any btrfs subvolume information in /dev.
    Here is the var.mount config:
    systemctl show var.mount wrote:Where=/var
    What=/dev/sda
    Options=rw,relatime,compress=lzo,space_cache,autodefrag
    Type=btrfs
    TimeoutUSec=1min 30s
    ControlPID=0
    DirectoryMode=0755
    SloppyOptions=no
    Result=exit-code
    ExecMount={ path=/bin/mount ; argv[]=/bin/mount -n uUID=12f15a3e-cf5c-4bc2-9475-6b4686a30f90 /var -t btrfs -o rw,relatime,space_cache,noatime,compress=lzo,autodefrag,subvol=var ; ignore_errors=no ; start_time=[Thu 1970-01-01 01:00:07 CET] ; stop_time=[Thu 1970-01-01 01:00:07 CET] ; pid=141 ; code=exited ; status=32 }
    Slice=system.slice
    ControlGroup=/system.slice/var.mount
    Delegate=no
    CPUAccounting=no
    CPUShares=18446744073709551615
    StartupCPUShares=18446744073709551615
    CPUQuotaPerSecUSec=infinity
    BlockIOAccounting=no
    BlockIOWeight=18446744073709551615
    StartupBlockIOWeight=18446744073709551615
    MemoryAccounting=no
    MemoryLimit=18446744073709551615
    DevicePolicy=auto
    UMask=0022
    LimitCPU=18446744073709551615
    LimitFSIZE=18446744073709551615
    LimitDATA=18446744073709551615
    LimitSTACK=18446744073709551615
    LimitCORE=18446744073709551615
    LimitRSS=18446744073709551615
    LimitNOFILE=4096
    LimitAS=18446744073709551615
    LimitNPROC=7329
    LimitMEMLOCK=65536
    LimitLOCKS=18446744073709551615
    LimitSIGPENDING=7329
    LimitMSGQUEUE=819200
    LimitNICE=0
    LimitRTPRIO=0
    LimitRTTIME=18446744073709551615
    OOMScoreAdjust=0
    Nice=0
    IOScheduling=0
    CPUSchedulingPolicy=0
    CPUSchedulingPriority=0
    TimerSlackNSec=50000
    CPUSchedulingResetOnFork=no
    NonBlocking=no
    StandardInput=null
    StandardOutput=journal
    StandardError=inherit
    TTYReset=no
    TTYVHangup=no
    TTYVTDisallocate=no
    SyslogPriority=30
    SyslogLevelPrefix=yes
    SecureBits=0
    CapabilityBoundingSet=18446744073709551615
    MountFlags=0
    PrivateTmp=no
    PrivateNetwork=no
    PrivateDevices=no
    ProtectHome=no
    ProtectSystem=no
    SameProcessGroup=yes
    IgnoreSIGPIPE=yes
    NoNewPrivileges=no
    SystemCallErrorNumber=0
    RuntimeDirectoryMode=0755
    KillMode=control-group
    KillSignal=15
    SendSIGKILL=yes
    SendSIGHUP=no
    Id=var.mount
    Names=var.mount
    Requires=-.mount
    Wants=system.slice
    RequiredBy=systemd-journal-flush.service man-db.service shadow.timer man-db.timer local-fs.target systemd-random-seed.service logrotate.timer systemd-update-utmp.service
    Conflicts=umount.target
    Before=systemd-journal-flush.service man-db.service shadow.timer man-db.timer local-fs.target systemd-random-seed.service logrotate.timer systemd-update-utmp.service umount.target
    After=local-fs-pre.target -.mount systemd-journald.socket system.slice
    RequiresMountsFor=/
    Documentation=man:fstab(5) man:systemd-fstab-generator(8)
    Description=/var
    LoadState=loaded
    ActiveState=active
    SubState=mounted
    FragmentPath=/run/systemd/generator/var.mount
    SourcePath=/etc/fstab
    UnitFilePreset=disabled
    InactiveExitTimestamp=Thu 1970-01-01 01:01:11 CET
    InactiveExitTimestampMonotonic=71204114
    ActiveEnterTimestamp=Thu 1970-01-01 01:01:11 CET
    ActiveEnterTimestampMonotonic=71204114
    ActiveExitTimestampMonotonic=0
    InactiveEnterTimestamp=Thu 1970-01-01 01:00:07 CET
    InactiveEnterTimestampMonotonic=7409499
    CanStart=yes
    CanStop=yes
    CanReload=yes
    CanIsolate=no
    StopWhenUnneeded=no
    RefuseManualStart=no
    RefuseManualStop=no
    AllowIsolate=no
    DefaultDependencies=yes
    OnFailureJobMode=replace
    IgnoreOnIsolate=yes
    IgnoreOnSnapshot=no
    NeedDaemonReload=no
    JobTimeoutUSec=0
    JobTimeoutAction=none
    ConditionResult=yes
    AssertResult=yes
    ConditionTimestamp=Thu 1970-01-01 01:00:07 CET
    ConditionTimestampMonotonic=7365732
    AssertTimestamp=Thu 1970-01-01 01:00:07 CET
    AssertTimestampMonotonic=7365738
    Transient=no

Maybe you are looking for