Using an existing BTRFS filesystem with NCP

[shaan7]

Hi,

I had used the NCP first time setup wizard to move all my data to a USB drive (it used to automount in /media/myCloudDrive). Everything worked fine until recently when my drive had a hardware failure. Thankfully I have a daily backup of the ncdata and ncp-backups dirs (using duplicity to a remote machine), so I created a new BTRFS filesystem manually on a new USB drive and restored these dirs.

Now Nextcloud itself works great but if I try to run nc-snapshot I get:

Running nc-snapshot
Maintenance mode enabled
Nextcloud is in maintenance mode - no apps have been loaded

ERROR: not a btrfs filesystem: /media/myCloudDrive/../ncp-snapshots
Maintenance mode disabled

I guess that is because the NCP setup wizard might have done some more setup that is not present in the BTRFS filesystem I created myself. So what should I do now? Is there a list of such missing things that I should create myself, or can I run something to create those automatically?

[mentex]

Maybe my issue from yesterday could help you

Btrfs snapshot not working

Yes, I know that I have installed it myself. I was just wondering why ncp does not use it… Also the ncp.cfg looks strange… I am bullseye and using as told before 8.0 which is recommended in the documentation. { “nextcloud_version”: “23.0.2”, “php_version”: “7.3”, “release”: “buster”, “datadir”: “/media/data1/ncdata1/data” } the good thing, also with the error my nc-datadir was moved and snapshots are working. So i will open another thread to correct the php version. Thanks @nachoparker

[shaan7]

Thanks! I’m a bit embarrassed that I missed that thread -.-

@nachoparker I tried what you suggested on the other thread and got this:

Running nc-datadir
Maintenance mode enabled
moving data directory from /media/myCloudDrive/ncdata to /media/myCloudDrive/ncdata1...
BTRFS filesystem detected
Create subvolume '/media/myCloudDrive/ncdata1'
mv: cannot remove '/media/myCloudDrive/ncdata': Directory not empty
Done. Press any key...

# ls /media/myCloudDrive/ncdata
nextcloud.log

I’m guessing the Directory not empty was because of the nextcloud.log that was left behind. Now my data has been moved to ncdata1 but config.php was not updated:

# ls /media/myCloudDrive/
ncdata  ncdata1  ncp-backups.bak
# ls /media/myCloudDrive/ncdata1/
data

# ls /media/myCloudDrive/ncdata1/data/
appdata_ocfgwleo0gzc  index.html  nextcloud.log  shantanu user2  tmp

# grep /media /var/www/nextcloud/config/config.php
  'datadirectory' => '/media/myCloudDrive/ncdata',
  'tempdirectory' => '/media/myCloudDrive/ncdata/tmp',
  'logfile' => '/media/myCloudDrive/ncdata/nextcloud.log',

Is it safe for me to manually change all that to ncdata1 paths, or would nc-datadir have missed some other important steps (besides updating the config) because of the Directory not empty error?

[shaan7]

I took another backup and simply manually moved ncdata1/* back to ncdata, deleted nextcloud.log and this time nc-datadir worked fine.