I had a similar issue a while ago regarding s1001 error, this is based on how the system re-owned items upon upgrade, I would assume the same thing is occurring for your pre-rolls:
Basically:
Why?
I had a similar issue, but my data was on the same volume. This was due to the way file systems own data for a user.
Data is not actually owned by the Username , but rather a User ID .
e.g.
**user1 = 1001
user2 = 1002
**
When you upgrade the media server it literally recreates the username “ plex ”, every time, this actually creates a NEW USER ID in the jail,
e.g.
plex=1001 original user/owner
plex=1002 new user /non-owner
but doesn’t tell it to reacquire ownership of items belonging to that username.
What’s happening here?
The old one (plex=uid 1001) doesn’t exist, but the environment still recognizes the old user “plex (uid 1001)” as the owner as well as the new user “plex” (uid 1002), which creates the confusion.
Resolution
I corrected this by “re-owning” all files owned by the user “plex” to the new user “plex”
See this topic for a better explanation shaka1001 (Network)
