Files missing after upgrade, "user" directories appearing in an odd location

Server
1

Morning All,

I’ve just upgraded to 10.16.0.0 using the scripts provided in the documentation on an Ubuntu 20.04 server with php 7.4.3 and MariaDB 10.5.27.

I had a couple of errors related to marketplace items when upgrading but disabled the problematic ones and that seemed to work ok. Everything else went fine.

When logging on to the web interface as a user there are no files showing up. Tried the occ files:scan and that runs quickly (too quickly!) and returns something like 3 folders found.

In the old config.php I have ‘datadirectory’ => ‘/srv/owncloud_data’ so during the scripted upgrade I said I was using links and (I think) told it that the data is stored there. When I checked the new setup I see that datadirectory is set to /var/www/my.domain.tld/data and that this path is symlinked to /srv/owncloud_data*/data* not to srv/owncloud_data.

No drama, file layout has changed slightly, I thought I’ll move all the files that were in /srv/owncloud_data over to /srv/owncloud_data/data. I ran the files:scan again. Still no files showing up.

Tried changing the datadirectory in config to /srv/owncloud_data and /srv/owncloud_data/data and then ran files:scan…. nope… I did however at this point spot that something had re-created, for example /srv/owncloud_data/ for a couple of the users (but not all…)

At this point I decided that I should stop messing and ask for help!

So… Can anyone suggest where I need to start to fix this please.

2

Update:

After noticing the folders re-appearing in the /srv/owncloud_data directory I tried moving some of the existing data back to that location and that seems to be working.

Obviously that’s good on one hand because my stuff is working but I’m worried that the path in the config.php and the path that /var/www/my.domain.tld/data is linked to are now not the paths that contain the data and what that might mean going forward.

3

so you moved your data folder (my intention or by accident) - here is on how to perform this operation correctly: Manually Move the Data Directory :: Documentation for ownCloud (A Kiteworks Company)

4

Yeah I guess that’s probably right @DeepDiver1975. Certainly not intentionally and I would argue that I probably didn’t move the data but rather the upgrade changed where OC was looking for the data due to my not fully understanding things… but that’s symantecs!

I’ll had a quick look at the article you linked to (thanks) and it looks like it’s going to help me figure it out.

In a “normal” install with a symlinked data folder, presumably the config file points to the symlink in the webroot and not to the actual data location as mine currently does. I think it makes sense for me to “move” it all there so that it’s as close to standard as I can be to try and avoid such problems the next time I update.