Installed Nextcloudpi and set it to store on a large USB disk

Support intro

Sorry to hear you’re facing problems. :slightly_frowning_face:

The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.

If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.

Getting help

In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.

Before clicking submit: Please check if your query is already addressed via the following resources:

(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).

Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can. :heart:

The Basics

  • Nextcloud Server version (e.g., 29.x.x):

    • 30.0.1
  • Operating system and version (e.g., Ubuntu 24.04):
    -nextcloudpi

  • Web server and version (e.g, Apache 2.4.25):

  • Reverse proxy and version _(e.g. nginx 1.27.2)

  • PHP version (e.g, 8.3):

  • Is this the first time you’ve seen this error? (Yes / No):

    • Yes
  • When did this problem seem to first start?
    AFter new installation

  • Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
    Bare metal I guess

  • Are you using CloudfIare, mod_security, or similar? (Yes / No)
    No

Summary of the issue you are facing:

Fails to connect at all and I get the following errors about mariadb

[Job for mariadb.service failed because the control process exited with error code.
See “systemctl status mariadb.service” and “journalctl -xeu mariadb.service” for details.
root@nextcloudpi:/media#

root@nextcloudpi:/media# systemctl status mariadb.service
● mariadb.service - MariaDB 10.11.6 database server
     Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; preset: enabled)
    Drop-In: /etc/systemd/system/mariadb.service.d
             └─ncp-delay-automount.conf
     Active: activating (auto-restart) (Result: exit-code) since Thu 2025-01-09 18:56:18 UTC; 3s ago
       Docs: man:mariadbd(8)
             https://mariadb.com/kb/en/library/systemd/
    Process: 49696 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
    Process: 49697 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
    Process: 49699 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_>
    Process: 49779 ExecStartPre=/bin/sleep 20 (code=exited, status=0/SUCCESS)
    Process: 49804 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
   Main PID: 49804 (code=exited, status=1/FAILURE)
     Status: "MariaDB server is down"
        CPU: 388ms


Jan 09 18:57:22 nextcloudpi systemd[1]: mariadb.service: Scheduled restart job, restart counter is at 1.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ Automatic restarting of the unit mariadb.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Jan 09 18:57:22 nextcloudpi systemd[1]: Stopped mariadb.service - MariaDB 10.11.6 database server.
░░ Subject: A stop job for unit mariadb.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit mariadb.service has finished.
░░
░░ The job identifier is 35209 and the job result is done.
Jan 09 18:57:22 nextcloudpi systemd[1]: Starting mariadb.service - MariaDB 10.11.6 database server...
░░ Subject: A start job for unit mariadb.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit mariadb.service has begun execution.
░░
░░ The job identifier is 35209.
Jan 09 18:57:43 nextcloudpi mariadbd[50256]: 2025-01-09 18:57:43 0 [Warning] Can't create test file '/media/myCloudDrive/nextcloudpi.lower-test' (Errcode: 13 "Permission denied")
Jan 09 18:57:43 nextcloudpi mariadbd[50256]: [97B blob data]
Jan 09 18:57:43 nextcloudpi mariadbd[50256]: 2025-01-09 18:57:43 0 [ERROR] Aborting
Jan 09 18:57:43 nextcloudpi systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit mariadb.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Jan 09 18:57:43 nextcloudpi systemd[1]: mariadb.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit mariadb.service has entered the 'failed' state with result 'exit-code'.
Jan 09 18:57:43 nextcloudpi systemd[1]: Failed to start mariadb.service - MariaDB 10.11.6 database server.
░░ Subject: A start job for unit mariadb.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit mariadb.service has finished with a failure.
░░...]

Steps to replicate it (hint: details matter!):

Log entries

Nextcloud

Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.

[ nc-limits ] (Thu Jan  9 04:57:25 PM UTC 2025)
+ configure
++ get_total_mem
+++ free -b
+++ sed -n 2p
+++ awk '{ print $2 }'
++ local total_mem=3976511488
++ local MAX_32BIT=4096000000
++ [[ aarch64 == \a\r\m\v\7 ]]
++ echo 3976511488
+ local TOTAL_MEM=3976511488
+ file /bin/bash
+ grep 64-bit
+ local AUTOMEM=2982383616
+ local require_fpm_restart=false
+ local CONF=/etc/php/8.3/fpm/conf.d/90-ncp.ini
++ cat /etc/php/8.3/fpm/conf.d/90-ncp.ini
+ local 'CONF_VALUE=; disable .user.ini files for performance and workaround NC update bugs
user_ini.filename =

; from Nextcloud .user.ini
upload_max_filesize=10G
post_max_size=10G
memory_limit=2982383616
mbstring.func_overload=0
always_populate_raw_post_data=-1
default_charset='\''UTF-8'\''
output_buffering=0

; slow transfers will be killed after this time
max_execution_time=3600
max_input_time=3600'
++ tmpl_php_max_memory
+++ get_total_mem
++++ free -b
++++ sed -n 2p
++++ awk '{ print $2 }'
+++ local total_mem=3976511488
+++ local MAX_32BIT=4096000000
+++ [[ aarch64 == \a\r\m\v\7 ]]
+++ echo 3976511488
++ local TOTAL_MEM=3976511488
+++ find_app_param nc-limits MEMORYLIMIT
+++ local script=nc-limits
+++ local param_id=MEMORYLIMIT`````

Web Browser

If the problem is related to the Web interface, open your browser inspector Console and Network tabs while refreshing (reloading) and reproducing the problem. Provide any relevant output/errors here that appear.

PASTE

Web server / Reverse Proxy

The output of your Apache/nginx/system log in /var/log/____:

PASTE HERE

Configuration

Nextcloud

The output of occ config:list system or similar is best, but, if not possible, the contents of your config.php file from /path/to/nextcloud is fine (make sure to remove any identifiable information!):

<?php
$CONFIG = array (
  'passwordsalt' => '***REDACTED***',
  'secret' => '***REDACTED***',
  'trusted_domains' =>
  array (
    0 => 'localhost',
    7 => 'nextcloudpi',
    5 => 'nextcloudpi.local',
    8 => 'nextcloudpi.lan',
    3 => 'nextcloudpi',
    11 => '217.155.70.9',
    1 => '192.168.178.75',
    14 => 'nextcloudpi',
  ),
  'datadirectory' => '/media/USBdrive/ncdata/data',
  'dbtype' => 'mysql',
  'version' => '30.0.4.1',
  'overwrite.cli.url' => 'https://nextcloudpi/',
  'dbname' => 'nextcloud',
  'dbhost' => 'localhost',
  'dbport' => '',
  'dbtableprefix' => 'oc_',
  'mysql.utf8mb4' => true,
  'dbuser' => 'ncadmin',
  'dbpassword' => '***REDACTED***',
  'installed' => true,
  'instanceid' => 'ocut2g9g78ea',
  'memcache.local' => '\\OC\\Memcache\\Redis',
  'memcache.locking' => '\\OC\\Memcache\\Redis',
  'redis' =>
  array (
    'host' => '/var/run/redis/redis.sock',
    'port' => 0,
    'timeout' => 0.0,
    'password' => '***REDACTED***',
  ),
  'tempdirectory' => '/media/USBdrive/ncdata/data/tmp',
  'mail_smtpmode' => 'sendmail',
  'mail_smtpauthtype' => 'LOGIN',
  'mail_from_address' => 'noreply',
  'mail_domain' => 'nextcloudpi.com',
  'preview_max_x' => '2048',
  'preview_max_y' => '2048',
  'jpeg_quality' => '60',

Apps

The output of occ app:list (if possible).

Tips for increasing the likelihood of a response

  • Use the preformatted text formatting option in the editor for all log entries and configuration output.
  • If screenshots are useful, feel free to include them.
    • If possible, also include key error output in text form so it can be searched for.
  • Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.

There seems to be something wrong with write privileges in your setup.
I don’t get it how the new install was done.

All I have done is download the nextcloudpi image for pi boot.
Used it to start the raspberry pi then using the configuration web page asked for it to be moved to my usb disk (3tb).
Disk is formatted from same web page

Sounds quite straight forward.
So your system device is an sd card (do you trust it?).
Reboot and checking logs/error messages.
Check mount option of usb-device.,
Check write access for user mysql and www-data.

Consider to quit using sd card as system device, put raspian os on sd card, boot, fetch newest ncpi image write it raspi imager at the us b-drive, prepare pi to boot from usb; you get a more reliable boot device than sd card, one drawback - the usb-device is ext4 fs,
Keep in mind, new ncpi images are armbian based.

Interestingly, since this is actually only a learning exercise at the moment, I set the permissions on the USB disk, from the mount point to all be 777.
But still mariadb will not run.

geoW, I think I will follow your suggestion,
Can you direct me to where I might be able to find how to modify pi boot to USB.
SO thanks to all who helped.
This can now be closed and I will explore the boot from USD.

Best place start looking is raspberry documentation.
Raspberry Pi boot EEPROM

  • flash sd card with raspian os desktop
  • boot , update && full-upgrade system
  • check boot /eeprom stuff (raspian-config)
  • fetch ncp-image
  • flash usb-drive with rpi-imager (no presets)
  • take out sd card
  • boot from usb-drive
  • follow the instructiuons
  • activate and setup (ssh etc.)
    Good luck :grinning: