# Flame Archive Failing

**URL:** <https://forum.logik.tv/t/flame-archive-failing/7026>\
**Category:** Flame Questions\
**Tags:** archive\
**Created:** [October 31, 2022, 3:38pm UTC](https://forum.logik.tv/t/flame-archive-failing/7026 "2022-10-31T15:38:42Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![fbiasi](https://avatars.discourse-cdn.com/v4/letter/f/dbc845/32.png) [@fbiasi](https://forum.logik.tv/u/fbiasi)\
**Post date:** [October 31, 2022, 3:38pm UTC](https://forum.logik.tv/t/flame-archive-failing/7026/1 "2022-10-31T15:38:42Z")

</div>

Hi there,  
wondering if anyone has come across this when archiving a project.  
I am running 2021.2.2 Update. I archive with a segment size of 250GB.  
The problem occurs when the first segment is full. I get a message saying  
'Writing auxiliary file segment then I get kicked out of the archive. When I update  
the archive, it doesn’t recognize the segment that was done and I need to start over.

Has anyone seen this before?

frank

---

<div class="post-metadata">

**Author:** ![PlaceYourBetts](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/placeyourbetts/32/6852_2.png) [@PlaceYourBetts](https://forum.logik.tv/u/PlaceYourBetts)\
**Post date:** [October 31, 2022, 5:41pm UTC](https://forum.logik.tv/t/flame-archive-failing/7026/2 "2022-10-31T17:41:06Z")

</div>

I’ve not had this before so I don’t have any solid solutions.

Make sure that you have permission to write to the location of your archive. Test a much smaller archive and see if that works.

---

<div class="post-metadata">

**Author:** ![randy](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/randy/32/6122_2.png) [@randy](https://forum.logik.tv/u/randy)\
**Post date:** [October 31, 2022, 5:48pm UTC](https://forum.logik.tv/t/flame-archive-failing/7026/3 "2022-10-31T17:48:24Z")

</div>

Hmm. Id write much smaller segments. I like 10Gig segments for no other reason than the math is easier.

Also, whenever this stuff happens I’d write a test archive to wherever your framestore is. Likely it will work, which means something within your shared storage or wherever your archiving to is likely the problem.

---

<div class="post-metadata">

**Author:** ![ytf](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/ytf/32/109_2.png) [@ytf](https://forum.logik.tv/u/ytf)\
**Post date:** [October 31, 2022, 5:56pm UTC](https://forum.logik.tv/t/flame-archive-failing/7026/4 "2022-10-31T17:56:16Z")

</div>

There was a thread on this last summer. I never heard the solve. . . . .

---

<div class="post-metadata">

**Author:** ![fbiasi](https://avatars.discourse-cdn.com/v4/letter/f/dbc845/32.png) [@fbiasi](https://forum.logik.tv/u/fbiasi)\
**Post date:** [October 31, 2022, 5:56pm UTC](https://forum.logik.tv/t/flame-archive-failing/7026/5 "2022-10-31T17:56:37Z")

</div>

I had been archiving to the same location with all the same paramaters earlier in the week without any issues. I will try using smaller sizes. I did manage to get it to work but I had to create 1 massive file for it work.

I’ll test smaller files.

frank

---

<div class="post-metadata">

**Author:** ![fbiasi](https://avatars.discourse-cdn.com/v4/letter/f/dbc845/32.png) [@fbiasi](https://forum.logik.tv/u/fbiasi)\
**Post date:** [October 31, 2022, 6:09pm UTC](https://forum.logik.tv/t/flame-archive-failing/7026/6 "2022-10-31T18:09:27Z")

</div>

I just ran a test archive of 247 GB. I capped the segments at 10GB.  
I did 12 segments. At the start of the 13th segment, the message

’ Writing auxiliary data segment (206 bytes) ’

appeared and the archive stopped.

frank

---

<div class="post-metadata">

**Author:** ![randy](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/randy/32/6122_2.png) [@randy](https://forum.logik.tv/u/randy)\
**Post date:** [October 31, 2022, 6:21pm UTC](https://forum.logik.tv/t/flame-archive-failing/7026/7 "2022-10-31T18:21:27Z")

</div>

Drive full?

---

<div class="post-metadata">

**Author:** ![fbiasi](https://avatars.discourse-cdn.com/v4/letter/f/dbc845/32.png) [@fbiasi](https://forum.logik.tv/u/fbiasi)\
**Post date:** [October 31, 2022, 6:24pm UTC](https://forum.logik.tv/t/flame-archive-failing/7026/8 "2022-10-31T18:24:02Z")

</div>

Unfortunately, no.  
That would be the easy answer

---

<div class="post-metadata">

**Author:** ![PlaceYourBetts](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/placeyourbetts/32/6852_2.png) [@PlaceYourBetts](https://forum.logik.tv/u/PlaceYourBetts)\
**Post date:** [October 31, 2022, 6:39pm UTC](https://forum.logik.tv/t/flame-archive-failing/7026/9 "2022-10-31T18:39:06Z")

</div>

Lets go with the theory that one of your clips is causing corruption 🤔

Save off small ~~segments~~ chunks of the project. Close the archive after each ~~segment~~ chunk and then open and carry on. You might be able to isolate which bit is causing the archive to fail.

Do you have verify switched on?

---

<div class="post-metadata">

**Author:** ![fbiasi](https://avatars.discourse-cdn.com/v4/letter/f/dbc845/32.png) [@fbiasi](https://forum.logik.tv/u/fbiasi)\
**Post date:** [October 31, 2022, 6:47pm UTC](https://forum.logik.tv/t/flame-archive-failing/7026/10 "2022-10-31T18:47:09Z")

</div>

I don’t have verify switched on.  
I don’t think it is a corruption anywhere because the archive will work  
if I make the segment size bigger than the size of the archive.

---

<div class="post-metadata">

**Author:** ![fbiasi](https://avatars.discourse-cdn.com/v4/letter/f/dbc845/32.png) [@fbiasi](https://forum.logik.tv/u/fbiasi)\
**Post date:** [October 31, 2022, 6:51pm UTC](https://forum.logik.tv/t/flame-archive-failing/7026/11 "2022-10-31T18:51:17Z")

</div>

I think it has something to do with the shared storage location and was hoping someone had come across this same issue. I know that storage is over 90% full and thought maybe that was causing the problem but then it had no issues doing the archive in one segment

frank

---

<div class="post-metadata">

**Author:** ![PlaceYourBetts](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/placeyourbetts/32/6852_2.png) [@PlaceYourBetts](https://forum.logik.tv/u/PlaceYourBetts)\
**Post date:** [October 31, 2022, 6:53pm UTC](https://forum.logik.tv/t/flame-archive-failing/7026/12 "2022-10-31T18:53:05Z")

</div>

So if the total archive ended up being 220GB then an archive with segments of 250GB works 🤔

Never had this before. Sorry I am clutching at straws here. I am trying to think what might be going wrong. Even when a segment doesn’t get filled up, it still needs to close it off/save it off.

The way I believe an archive works, having watched the shell a number of times, it spends time making the zip and then saves it off.

Why would this archive struggle to completely close off a segment and start making a new one?

Like I said, I haven’t seen this problem but I have had a corrupt sequence (checkered frame) stop an archive from working before. I have also had Mac screw up my permissions on a drive/server and stop my archive from working. Not much help then. Sorry.

---

<div class="post-metadata">

**Author:** ![fbiasi](https://avatars.discourse-cdn.com/v4/letter/f/dbc845/32.png) [@fbiasi](https://forum.logik.tv/u/fbiasi)\
**Post date:** [October 31, 2022, 7:20pm UTC](https://forum.logik.tv/t/flame-archive-failing/7026/13 "2022-10-31T19:20:24Z")

</div>

No worries. Bit of a head scratcher.

---

<div class="post-metadata">

**Author:** ![PlaceYourBetts](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.logik.tv/placeyourbetts/32/6852_2.png) [@PlaceYourBetts](https://forum.logik.tv/u/PlaceYourBetts)\
**Post date:** [March 17, 2023, 3:04am UTC](https://forum.logik.tv/t/flame-archive-failing/7026/15 "2023-03-17T03:04:27Z")

</div>

We seem to be getting a similar problem here at the moment. Any ideas?
