AD File Corrupted randomly, file also hung on saving just prior

[afroniquely]

Ok, so I am in the middle of working on a project and then hit save as usual and then the saving was lagging for forever (it basically wouldn't save). Then the app force quit and once tried to reopen the file it says: file corrupted and now I cannot open it at all.

1. Which Operating System are you using? - macOS Monterey 12.6.2
2. Which version of Affinity did the file last get saved in? Affinity Designer 2.0.0
3. What drive type was the file last saved/saving to?
   Network Server

4. Any other information you think would help us try to find the problem?

I suspect the issue was triggered from the fact that file wouldn't save and then the app force quit. Really hoping the Affinity team can help me recover it.

Thanks for your help!

 

 

[afroniquely]

Please let me know if there is somewhere I can privately send the file for you all to look at it. Thanks so much

[v_kyr]

2 hours ago, afroniquely said:

I suspect the issue was triggered from the fact that file wouldn't save and then the app force quit.

That and the fact that you worked with your project file directly on a network server. The Affinity apps also in the past had partly problems with working directly on NAS, cloud drives and network service drives etc.

Note that it is always much safer and recommended with any Affinity app, to work with files only on your local drives file system instead. - So you best work always (open/save/store) with any Affinity format files locally on your local disk and thus use external storage drives/spaces only for backups and file exchange (aka copying Affinity files for exchange between your local & remote storage places with the MacOS Finder then).

[DGee]

12 hours ago, v_kyr said:

That and the fact that you worked with your project file directly on a network server. The Affinity apps also in the past had partly problems with working directly on NAS, cloud drives and network service drives etc.

Note that it is always much safer and recommended with any Affinity app, to work with files only on your local drives file system instead. - So you best work always (open/save/store) with any Affinity format files locally on your local disk and thus use external storage drives/spaces only for backups and file exchange (aka copying Affinity files for exchange between your local & remote storage places with the MacOS Finder then).

is it still risky to edit Affinity files on an external hard drive?

[v_kyr]

1 hour ago, DGee said:

is it still risky to edit Affinity files on an external hard drive?

Even I'm personally not using any Affinity v2 apps yet, I do think so, and the OP's above posting here (aka this thread) looks very much like it.

[DGee]

23 minutes ago, v_kyr said:

Even I'm personally not using any Affinity v2 apps yet, I do think so, and the OP's above posting here (aka this thread) looks very much like it.

yeah but he's saving his documents on the cloud which is not the same.

[DGee]

I'm not having any issues so far with V2, but if my files get corrupted I can go crazy.

[v_kyr]

31 minutes ago, DGee said:

yeah but he's saving his documents on the cloud which is not the same.

Whatever external connection (USB-drive, NAS, Cloud, etc.), if that connection is temporary in sleep mode/not mounted/or has access dropouts, then you will have a problem during file saving operations. And since the Affinity apps file format is an incremental nature one, it doesn't always behave brave here.

[emmrecs01]

@DGee @v_kyr

All my Affinity data files (all three apps, both versions) are saved to an external USB drive.  That drive is never allowed to go to sleep whilst the computer is on and I've never yet experienced any problem with file saving or files being corrupted.

[v_kyr]

44 minutes ago, emmrecs01 said:

That drive is never allowed to go to sleep whilst the computer is on

That's the reason you didn't had problems so far, but inexperienced users do probably not know about such things and can therefore as default have the systems USB power saving options enabled, which might sooner or later then yield to Affinity file saving problems & possible non recoverable data lost.

[emmrecs01]

17 hours ago, v_kyr said:

That's the reason you didn't had problems so far, but inexperienced users do probably not know about such things and can therefore as default have the systems USB power saving options enabled, which might sooner or later then yield to Affinity file saving problems & possible non recoverable data lost.

I agree!

[afroniquely]

Just adding - the server never sleeps/is never off

Anyways, let's see if the Affinity Team is able to parse through it and possibly recover it. I started recreating locally what I can remember

And yes, it is definitely true: as much as possible work directly off your local disks, which is what I usually/mostly do, but in this rare occurrence, alas, a network file and wonky tonk happenings abound (first time ever though, because I've worked off the network server on AD/AP files before without these kinds of issues before) - point is I agree, it's definitely not meant to be the default method (was more so emergency).

[DGee]

Just now, afroniquely said:

Just adding - the server never sleeps/is never off

Anyways, let's see if the Affinity Team is able to parse through it and possibly recover it. I started recreating locally what I can remember

And yes, it is definitely true: as much as possible work directly off your local disks, which is what I usually/mostly do, but in this rare occurrence, alas, a network file and wonky tonk happenings abound (first time ever though, because I've worked off the network server on AD/AP files before without these kinds of issues before) - point is I agree, it's definitely not meant to be the default method (was more so emergency).

I currently work from a solid state external drive, I don't think those go to sleep ever, but I can be wrong. For me it would be a real pain to work on my macbook pro local drive... 

[DWright]

With the 2.0.4 update installed are you still encountering any file corruption and save issues.