Unable to use entirety of hard drive for storage

Maybe it’s a problem with your partition settings.

I fixed the problem. It was a problem with my partition settings. Not a next cloud problem, just a me problem

1 Like

Can you explain exactly what you did? I am having the same issue here. :frowning:

1 Like

If you check screenshot from above, partitions were not correctly set. There was no 3TB partition, only small ones. If you have the same issue, please post here output of following commands:

df -h

and

lsblk

dfh lsblk

It is easy :slight_smile:
You have 16 GB SD card mounted as root /and it is 100% being used (16GB of 16GB).
Your 3.7 TB HDD is mounted under /media/SATAHD, but seems that you set nextcloud data folder to be on your SD Card, or just used defaults.
Just move your data folder to your HDD and change the config of NC to the new location. Default seems to be/var/snap/nextcloud/common/ what is on your SD card, not HDD.

Thanks so much for this! As a noob to nextcloud/linux though, I wasn’t sure what commands in ubuntu exactly accomplish these, specifically when moving my data folder and changing my config?

Not sure if this was what you were talking about but I found this: HowTo: Change / Move data directory after installation

Sorry for a long response time, I think in your case it should be exact this one:

Basically you need to move you data to /media/SATAHD. Probably your data folder is under /var/snap/nextcloud/common/nextcloud/data you have to move it to something like /media/SATAHD/data or /media/SATAHD/nextcloud/data. This is valid when you install NC via snap.

I have the same issue my NCDATA is 1.5 and i have harddisk with 3TB

root@nextcloud:/home/ncadmin# df -h
Filesystem Size Used Avail Use% Mounted on
udev 3.9G 0 3.9G 0% /dev
tmpfs 797M 1.3M 796M 1% /run
/dev/mapper/nextcloud–vg-root 39G 7.1G 30G 20% /
tmpfs 3.9G 72K 3.9G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
ncdata 1.5T 1.3T 196G 87% /mnt/ncdata
overlay 39G 7.1G 30G 20% /var/lib/docker/overlay2/d 64b8196bfb290c7d11917fd58c70f8e7e361163a994c4b0a61654935e7e5808/merged
overlay 39G 7.1G 30G 20% /var/lib/docker/overlay2/0 187f2a0e5662791f9bf009760a6a160eaf33f194a2b15bbc93fad142d0d10c0/merged
tmpfs 797M 0 797M 0% /run/user/1000
root@nextcloud:/home/ncadmin# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
fd0 2:0 1 4K 0 disk
sda 8:0 0 40G 0 disk
└─sda1 8:1 0 40G 0 part
├─nextcloud–vg-root 253:0 0 39G 0 lvm /
└─nextcloud–vg-swap_1 253:1 0 976M 0 lvm [SWAP]
sdb 8:16 0 3T 0 disk
└─sdb1 8:17 0 3T 0 part
root@nextcloud:/home/ncadmin# [sudo] password for ncadmin:
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
ncdata 1.5T 1.3T 196G 87% /mnt/ncdata
overlay 39G 7.1G 30G 20% /var/lib/docker/overlay2/d 64b8196bfb290c7d11917fd58c70f8e7e361163a994c4b0a61654935e7e5808/merged
overlay 39G 7.1G 30G 20% /var/lib/docker/overlay2/0 187f2a0e5662791f9bf009760a6a160eaf33f194a2b15bbc93fad142d0d10c0/merged
tmpfs 797M 0 797M 0% /run/user/1000
root@nextcloud:/home/ncadmin# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
fd0 2:0 1 4K 0 disk
sda 8:0 0 40G 0 disk
└─sda1 8:1 0 40G 0 part
├─nextcloud–vg-root 253:0 0 39G 0 lvm /
└─nextcloud–vg-swap_1 253:1 0 976M 0 lvm [SWAP]
sdb 8:16 0 3T 0 disk
└─sdb1 8:17 0 3T 0 part

I’m having a similar issue: nextcloud uses 200 GB out of 1 TB. But the output looks a bit different.

Here is my output:

It looks like its mounted on the right place right? But where are the other 730 GB?

Thanks!

As per above:

How? I have no mount point.

Do not really catch what you mean.

Based on your screenshot, looks like you need to extend your LVM logical volume mounted under root. Be careful with partitions under root. You need to execute something like this to extend it to e.g. 500Gb, please read more about.

lvextend -L500G /dev/vg-ubuntu/volume

Tanks I’ll try it!

Screenshot 2021-03-09 at 6.34.09 PM

Hey, @gas85 can you please help me too? Seem like you know what to do!!

P.S. - It’s a Raid1 8 TB HDD

1 Like

Hi, really appreciate it, but what can I do here?

I know this is kind of late, but here is what I did:

First increase the size of the logical volume to that of the volume group:

sudo lvextend -l 100%VG ubuntu-vg/ubuntu-lv

fdisk -l /dev/mapper/ubuntu–vg-ubuntu–lv
should then give you the new size.

Now, increase the size of the filesystem to that of the logical volume (I suppose ext4 here for ‘/’; if it is a different filesystem, you will have to use a different command!):

sudo resize2fs /dev/mapper/ubuntu–vg-ubuntu–lv

This is possible for a mounted filesystem, when the kernel supports it, which all recent kernels should do.

Found here:

2 Likes

Same issue here- I used gparted to increase my hard drive space from 40gb to 250GB- but nextcloud is running out of space:

root@nextcloud:/home/ncadmin# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 250G 0 disk
├─sda1 8:1 0 1G 0 part /boot/efi
├─sda2 8:2 0 2G 0 part /boot
└─sda3 8:3 0 246.9G 0 part
└─ubuntu–vg-ubuntu–lv 253:0 0 246.9G 0 lvm /
sdb 8:16 0 250G 0 disk
├─sdb1 8:17 0 40G 0 part
└─sdb9 8:25 0 8M 0 part
root@nextcloud:/home/ncadmin#

Okay, I had the same problem as described above and this link provided the solution:

It’s pretty much the ubuntu installer not allocating all the available disk space to a usable drive, hence it not showing up in nextcloud.

Easy fix with the following instructions:

"To check for existing free space on your Volume Group (where it is left by the installer default settings), run the command vgdisplay and check for free space. Here you can see I have 49.25GB of free space ready to be used. If you don’t have any free space, move on to the next section to use some free space from an extended physical (or virtual) disk.

To use up that free space on your Volume Group (VG) for your root Logical Volume (LV), first run the lvdisplay command and check the Logical Volume size, then run lvextend -l +100%FREE /dev/ubuntu-vg/ubuntu-lv to extend the LV to the maximum size usable, then run lvdisplay one more time to make sure it changed.

At this point you have increased the size of the block volume where your root filesystem resides, but you still need to extend the filesystem on top of it. First, run df -h to verify your (almost full) root file system, then run resize2fs /dev/mapper/ubuntu–vg-ubuntu–lv to extend your filesystem, and run df -h one more time to make sure you’re successful."

Hope it helps!