Skip navigation
This discussion is archived

Sparse Bundle Images on external NTFS formatted drive

11440 Views 11 Replies Latest reply: Sep 11, 2009 3:04 PM by Mal Page RSS
matthiash Calculating status...
Currently Being Moderated
Aug 30, 2009 5:03 PM
I'm currently in the process of re-arranging my own backup setup following on from my recent update to Snow Leopard. For this purpose i have the lend of a NTFS formatted external drive and used a large Sparse bundle disk image.

Under 10.5.7 with the latest MacFuse and and unknown version of NTFS-3G i had no problem using the sparse bundle images, they mounted, I could read and write, and the images where only unmounted when I explicitly ejected them.

Under 10.6 with the latest MacFuse and the latest NTFS-3G i have a very strange behavior.
Read and write works fine on the NTFS drive, as do regular disk images and old style sparse disk images.
However sparse bundle disk images will mount and then immediately dismount again. I have no problems mounting the sparse bundle images from HFS+ drives or when using the NTFS drive read only using apples drivers instead of MacFuser+NTFS3G.

The disk image dose not see the be the source of the problem; as any sparse bundle that opens fine on a HFS+ drive exhibits the behavior when moved onto the NTFS drive. Moving the image back onto a HFS+ drive allows the image to be mounted.

The problem is that I require to move some additional files onto the NTFS drive so I can reformat my backup drive

As a side note mounting using "hdiutil attach -readonly" seems to partially resolve the issue; the image will mount and stays mounted but it is read only.
Mac Book Pro, Mac OS X (10.6), MacFuse 2.0.3 + NTFS-3G 2009.4.4
  • RewAU Calculating status...
    FYI, this issue also appears to extend to sparse bundles located on AFP network shares (which happens to be where my TM backups are located !)

    Salient entries in the log appear to be;

    31.08.09 11:18:21 PM hdiejectd[49324] running
    31.08.09 11:18:22 PM diskimages-helper[49319] terminating disk1 - image is no longer available
    31.08.09 11:18:22 PM fseventsd[40] failed to create the uuid file /Volumes/<volumename>/.fseventsd/fseventsd-uuid
    31.08.09 11:18:22 PM kernel disk1: media is not present.

    Any suggestions would be appreciated.
    Blackbook 2.4Ghz, Mac OS X (10.6)
  • RewAU Level 1 Level 1 (10 points)
    Logs from Console available if anyone is curious to take a look ?
    Blackbook 2.4Ghz, Mac OS X (10.6)
  • RewAU Level 1 Level 1 (10 points)
    I've done some further testing and this might be a possible solution;

    Attach the NTFS disk to a Windows computer and share it over a network. I'm able to mount sparse bundle images over an SMB share (read / write) that appears to be reliable.

    Curious to know if that works for you ?
    Blackbook 2.4Ghz, Mac OS X (10.6)
  • mazatty Calculating status...
    i too am unable to mount and use sparse bundle disk images on an afp share. if i move the external drive to my macbook pro, running 10.6, the sparse bundle disk images mount and are usable. when i try to access the sparse bundle disk images over the network, from the same external drive, they mount briefly before disappearing, rendering them un-usable.

    this is a real issue. there are other uses for shared sparse bundle disk images. hopefully not just an attempt to sell more time capsules.

    my limited testing shows no problems creating and mounting r/w disk images and sparse disk images to an afp share. yet trying to create or mount a sparse bundle disk image to an afp share fails, sometimes silently.
    MPB 13" Unibody 2009, Mac OS X (10.6)
  • Baiste Calculating status...
    Exactly the same here! No luck mounting old or new sparse bundle images from an afp share... My log entry is even less verbose:

    04.09.09 23:46:13 diskimages-helper[536] terminating disk3 - image is no longer available
    04.09.09 23:46:13 kernel disk3s2: media is not present.

    I'm glad I found this thread. So it seems to be a snow leopard issue. Does anyone know how to bring this to apples attention? I'm just wondering how the time capsules keep working without a firmware update. I really find it hard to believe that this is related to marketing interests...

    Message was edited by: sebastianmorsch
    MBP 15" hybridbody :-/, Mac OS X (10.6)
  • Baiste Level 1 Level 1 (0 points)
    I just found out that the image stays mounted when served on a samba share. I can read and write to it.
    Mac OS X (10.6)
  • Robert Goodyear Calculating status...
    I too am having this issue. Intel / 10.5.8 attached to an SMB share from Ubuntu Linux.

    I ran a test of various image types, and while Sparse Image works, Sparse Bundle fails. Here are my logs. Happy to do some testing and log posting if anyone has a test theory to try.



    9/5/09 2:20:29 PM Disk Utility[1822] Disk Utility started.


    9/5/09 2:22:38 PM Disk Utility[1822] Creating Image “test1-rw-disk-image.dmg”

    9/5/09 2:22:38 PM Disk Utility[1822] Initializing…

    9/5/09 2:22:38 PM Disk Utility[1822] Creating…

    9/5/09 2:22:39 PM Disk Utility[1822] Formatting…

    9/5/09 2:22:39 PM com.apple.KernelEventAgent[37] KernelEventAgent: sysctl_queryfs: No such file or directory
    9/5/09 2:22:39 PM Disk Utility[1822] Attaching…

    9/5/09 2:22:40 PM Disk Utility[1822] Finishing…

    9/5/09 2:22:41 PM Disk Utility[1822] Image “test1-rw-disk-image.dmg” created successfully.

    9/5/09 2:23:21 PM Disk Utility[1822] Creating Image “test2-sparse-disk-image.sparseimage”

    9/5/09 2:23:21 PM Disk Utility[1822] Initializing…

    9/5/09 2:23:21 PM Disk Utility[1822] Creating…

    9/5/09 2:23:21 PM Disk Utility[1822] Formatting…

    9/5/09 2:23:21 PM com.apple.KernelEventAgent[37] KernelEventAgent: sysctl_queryfs: No such file or directory
    9/5/09 2:23:21 PM Disk Utility[1822] Attaching…

    9/5/09 2:23:23 PM Disk Utility[1822] Finishing…

    9/5/09 2:23:24 PM Disk Utility[1822] Image “test2-sparse-disk-image.sparseimage” created successfully.

    9/5/09 2:24:04 PM Disk Utility[1822] Creating Image “test3-sparse-bundle-image.sparsebundle”

    9/5/09 2:24:04 PM Disk Utility[1822] Initializing…

    9/5/09 2:24:04 PM Disk Utility[1822] Creating…

    9/5/09 2:24:04 PM Disk Utility[1822] Formatting…

    9/5/09 2:24:05 PM Disk Utility[1822] Finishing…

    9/5/09 2:24:05 PM Disk Utility[1822] Unable to create “test3-sparse-bundle-image.sparsebundle”. (Operation not supported)

    9/5/09 2:24:05 PM Disk Utility[1822]
    Macbook Pro 2,2, Mac OS X (10.5.8)
  • RewAU Level 1 Level 1 (10 points)
    Robert,

    I understand this issue is due to the way permissions are handled on SMB shares. If you create the sparse bundle on a HFS+ drive (say, your desktop !) and then copy the bundle across to the SMB share, it should behave itself thereafter.

    Let me know how you go.
    Blackbook 2.4Ghz, Mac OS X (10.5.6)
  • RewAU Level 1 Level 1 (10 points)
    Currently Being Moderated
    Sep 10, 2009 10:47 PM (in response to Baiste)
    Sebastian,

    I've just installed 10.6.1 update -- I was hoping this issue might be resolved. Unfortunately, it appears that it isn't.

    Would you test again after installing 10.6.1 and verify the behaviour is not resolved -- I have a support case open with Apple.
    Blackbook 2.4Ghz, Mac OS X (10.6)
  • Baiste Level 1 Level 1 (0 points)
    Currently Being Moderated
    Sep 11, 2009 1:48 AM (in response to RewAU)
    RewAU,

    same here, even on my updated 10.6.1 images still re-eject themselves 1 sec after they're mounted. I'm using a regular AFP share and I tried three types of sparsebundles: GUID partition, Apple partition and no partition. No luck...

    Thanks for letting Apple know!

    Sebastian
    Mac OS X (10.6)
  • Mal Page Calculating status...
    Currently Being Moderated
    Sep 11, 2009 3:04 PM (in response to Baiste)
    Ok, I had all of the same probs everyone else here had.. could not work this out.

    I tried to change the password to something really simple in SMB. I changed it to an all numerical password, and it worked! Seems like OSX 10.6 cant authenticate with an alphanumeric pw. For reference, I used an 8 digit numeric one! This was the ONLY change I made, and now it works fine.
    Mac OS X (10.6)

Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.