Version 4.1.0 Won't Save Custom Location

[mangombia]

Apparently the app auto-updated, and now won't recognize the already moved and saved cache, and even after deleting and setting up new, won't recognize that location on an external NVME. MacOS 26 & 27.

[glouel]

Hi @mangombia

It should have prompted you to upgrade like this, did it not ?

There's more info here about the new system which is based on a sparsebundle now (a little annoying but that's the only way I had to get around a restriction) : #144 (comment)

Can you tell me more about what you tried, what doesn't work, etc, comparing to that discussion ?

[Silmar-99]

Good morning Guillaume,

I have a some kind of similar issue. My Aerial videos are stored on a NAS and the creation of the sparse bundle disk failed. Now it is not even offering me to move it into a disk image anymore...

[glouel]

Good morning Guillaume,

I have a some kind of similar issue. My Aerial videos are stored on a NAS and the creation of the sparse bundle disk failed. Now it is not even offering me to move it into a disk image anymore...

Hi @Silmar-99

Can you use export diagnostics in advanced settings, so I can try and see how the creation failed ? Wondering if figuring disk size maybe failed on your nas (I need the size to size up the sparsebundle).

To try again, you can also check that box, it should then offer to create and migrate :

It likely will fail moving your files though, but at least it should create the sparsebundle. If that works I can guide you from there.

[glouel]

Reproduced the issue with a local NAS, will keep you posted.

[glouel]

@Silmar-99 I assume you use a SMB nas ? Apparently there's an issue with SMB not supporting fullsync writes, and that makes the disk creation fail.

Depending on your NAS, the short term fix is enabling Time Machine support on your nas, which apparently makes SMB compliant with what's needed. On commercial nas it's just a checkbox, and the manual configuration is explained here : https://wiki.samba.org/index.php/Configure_Samba_to_Work_Better_with_Mac_OS_X

I'm looking at alternative fixes right now, it's a bit of a mess, didn't expect that one it's on me.

[Silmar-99]

@glouel

Yes, I'm using a SMS NAS but I'm already using it for Time Machine, so it should work, as it is already setup for that.

For now, the solution that seemed to work (but I haven't finished copied my videos in it) is to create a sparse bundle on another disk, copy it on the NAS, then move the videos from its currently folder on the NAS to it.

I'll let you know once I completed the transfer if this works (but it worked previously with one video).

If it does, it means the issue is in the creation of the sparse bundle itself.

[mangombia]

I had previously setup an alias to the ~/Users/Shared/Aerial directory to point to a directory on an external NVME. Whatever the process in the upgrade either didn't or couldn't take this into account. My solution was to dump both the external directory with all the videos, and the Shared directory to start over from scratch, and then point to a new external cache share during setup to redownload all the videos.

[glouel]

@glouel

Yes, I'm using a SMS NAS but I'm already using it for Time Machine, so it should work, as it is already setup for that.

Ok perfect !

For now, the solution that seemed to work (but I haven't finished copied my videos in it) is to create a sparse bundle on another disk, copy it on the NAS, then move the videos from its currently folder on the NAS to it.

So yes, hdiutil silently failed in my testing there, but creating locally and moving is absolutely fine.

The issue is, without the fullsync thing, you never know if the writes are committed or not, and you can't reliably unmount the sparse volume. In theory things should work since you have time machine enabled. I may ask you to try a couple of things tomorrow to verify if you don't mind.

I'll let you know once I completed the transfer if this works (but it worked previously with one video).

Great, hopefully this should work now, keep me posted and thanks for the update !

[glouel]

I had previously setup an alias to the ~/Users/Shared/Aerial directory to point to a directory on an external NVME. Whatever the process in the upgrade either didn't or couldn't take this into account.

Ok this makes sense,making an alias wasn't something I officially supported or detected, so that's why it didn't know how to migrate from it.

My solution was to dump both the external directory with all the videos, and the Shared directory to start over from scratch, and then point to a new external cache share during setup to redownload all the videos.

Yep you can also move the videos if you kept them, but redownloading is fine ! Thanks for letting me know !