[Nextcloudpi] Only 647.6 MB available despite using nc-automount

we found it!! thanks for the patience

you still have to move the data folder. Run nc-datadir to /media/myCloudDrive/ncdata, or do the wizard again

1 Like

Amazing!! Thank you so much!
That worked!

Maintenance mode enabled
moving data dir from /media/USBdrive/ncdata to /media/myCloudDrive/ncdata...
Nextcloud is in maintenance mode - no app have been loaded

System config value datadirectory set to string /media/myCloudDrive/ncdata
Nextcloud is in maintenance mode - no app have been loaded

Maintenance mode disabled

Now it’s giving me the correct space! Could you figure out what the problem was?
Thank you so much anyway for this amazing project and your incredible support here in the forum! You are awesome! :slight_smile:

nice!!! Yes, I know what the problem is, I’ll fix it ASAP

thanks for your help to fix it!

we can mark this as solved

2 Likes

I have been following this thread since few days since I am also facing exact same issue. Before moving the data to external storage, I am having issues accessing some commands since the root file system seems to be full. Can you tell me where are the user files (Photos, Music, etc) stored in the SD card, so that I can delete them ? Eg, when running nextcloudpi-config and nc-datadir, I get the following error, however I see that the data has been copied to external storage.

Launching nc-datadir

[Symfony\Component\Console\Exception\CommandNotFoundException]
There are no commands defined in the “config:system” namespace.

Error reading data directory. Is NextCloud running and configured?
Done. Press any key…

root@nextcloudpi:~# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root 2.7G 2.5G 0 100% /
devtmpfs 460M 0 460M 0% /dev
tmpfs 464M 0 464M 0% /dev/shm
tmpfs 464M 6.3M 458M 2% /run
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 464M 0 464M 0% /sys/fs/cgroup
/dev/mmcblk0p1 42M 21M 21M 51% /boot
/dev/sda1 916G 749M 869G 1% /media/myCloudDrive3
tmpfs 93M 0 93M 0% /run/user/1000

root@nextcloudpi:~# ls -l /media/
total 20
drwx------ 2 root root 4096 Nov 22 06:56 myCloudDrive
drwx------ 2 root root 4096 Nov 22 11:17 myCloudDrive1
drwx------ 2 root root 4096 Nov 22 11:44 myCloudDrive2
drwxr-xr-x 4 root root 4096 Nov 23 15:56 myCloudDrive3
drwxr-xr-x 3 root root 4096 Nov 21 16:58 USBdrive
lrwxrwxrwx 1 root root 20 Nov 23 16:25 USBdrive3 -> /media/myCloudDrive3

@shrijith1 oh man what a mess

free some space with sudo apt-get clean, and then find where your files are with sudo du -shc /media/*. Once you know the folder with your data is you can delete it from /media/XXX/ncdata/_USER_/files/

Then run ncp-update to fix your NCP installation, and hope that your NC instance is not misconfigured because of disk full.

Anyhow, now NCP prevent users to inadvertedly moving the datadir to the SD card, precisely to prevent this situation.

After disconnecting the Pi from power (wanted to try a different power adapter and didn’t shut it down properly :see_no_evil: ), I’m now getting an error message in the nextcloud. I’m using the same power adapter as before now, but apparently the USB stick can not be mounted properly anymore…

pi@nextcloudpi:~ $ sudo mount /dev/sda1 /mnt
mount: /dev/sda1: can't read superblock

I guess this is a totally different problem and has nothing to do with the difficulties before this, right?
Guess I’ll have to format the USB stick and start all over?

first: always shut down your pi with the shutdown command or from ncp-web, and umount your USB drives before extracting.

second: try to recuperate with

sudo fsck.ext4 /dev/sda1
1 Like

Awesome, that worked! You’re the best!
I’ll be more careful in the future!

Is there any way to support you and this amazing project financially? (Obviously my linux knowledge is non-existent and therefore no help at all :smiley: )

pi@nextcloudpi:~ $ sudo fsck.ext4 /dev/sda1
e2fsck 1.43.4 (31-Jan-2017)
myCloudDrive: recovering journal
JBD2: Invalid checksum recovering block 1 in log
JBD2: Invalid checksum recovering block 1 in log
Journal checksum error found in myCloudDrive
myCloudDrive was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (7634371, counted=6888335).
Fix<y>? yes
Free inodes count wrong (1950229, counted=1947899).
Fix<y>? yes

myCloudDrive: ***** FILE SYSTEM WAS MODIFIED *****
myCloudDrive: 2341/1950240 files (0.7% non-contiguous), 912497/7800832 blocks

pi@nextcloudpi:~ $ sudo mount /dev/sda1 /mnt
mount: /dev/sda1 is already mounted or /mnt busy
   /dev/sda1 is already mounted on /mnt

great!

there’s many ways to help, see this post

1 Like

Thanks a lot for your timely support. There were some issues due to zero space, so re-installed from scratch and gave path in nc-datadir as /media/myCloudDrive/ncdata and the whole process went on fine. I think the default location shown in Wizard/nextcloudpi-config should be changed from /media/USBdrive to /media/myCloudDrive. Correct ?

good

they are the same, one is a symlink to the other

1 Like