Cyberpanel not recognizing additional drive

Support and Discussion
1

First: i’m windows and azure tribe, so not totally stupid but not up to speed on linux but getting there.

  1. cyberpanel is on an ubuntu VM in Azure

  2. Iused the azure marketplace package for cyberpanel setup -
    (note ithat it may be worth updating to with a data disk for the future - the original os disk in azure should not hold apps/data as its possible to get wiped totally)

  3. i added a drive to the machine - df -h results below

Filesystem Size Used Avail Use% Mounted on
/dev/root 29G 18G 12G 62% /
devtmpfs 2.0G 0 2.0G 0% /dev
tmpfs 2.0G 136K 2.0G 1% /dev/shm
tmpfs 393M 1.2M 392M 1% /run
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 2.0G 0 2.0G 0% /sys/fs/cgroup
/dev/sdc 49G 52K 47G 1% /data
/dev/loop1 56M 56M 0 100% /snap/core18/2679
/dev/loop0 56M 56M 0 100% /snap/core18/2667
/dev/loop2 64M 64M 0 100% /snap/core20/1738
/dev/loop3 64M 64M 0 100% /snap/core20/1778
/dev/loop4 92M 92M 0 100% /snap/lxd/23991
/dev/loop5 50M 50M 0 100% /snap/snapd/17883
/dev/loop6 50M 50M 0 100% /snap/snapd/17950
/dev/loop7 92M 92M 0 100% /snap/lxd/24061
/dev/loop8 1.5G 360K 1.4G 1% /tmp
/dev/sdb15 105M 5.2M 100M 5% /boot/efi
tmpfs 393M 0 393M 0% /run/user/5002

  1. i’ve read a few posts from here and i saw reference to /home in this post - (ask) how to use 2nd disk

the /home reference in this post
is that refereing to a users home directory or to root i.e. “/”
or is there a mount somewhere that i’m not seeing called /home

  1. assuming /home refers to “/” please could you confirm my understanding. I read this and other posts as
    a: cyberpanel will only function off the root mount?
    b: from the above it leads to your only choices is to extend the “/” partition?(i saw reference to getting alarger plan in some post)
    c: i saw mention of mounting /the new drive as /home (???)

sorry if i’m missing fundamentals but you were warned at the top :wink:

update - yes i get that /home is user directory - if i run an ls /home i get …
ls /home
aristotle docker kwiklink.ml mzansi.directory practical.toys vmail
cyberpanel elasticsearch linksafe.ml nxautomation ubuntu

so its the websites + apps - could i copy all of this to my existing data mount - then mount thaty as /home?

2

Welcome @Sandrat Happy you are here

You want to mount /home directory to another drive ?

No those are different partitions:

  • / is root partition (physical area of storage)

  • /home is home partition (physical area of storage)

For an already installed cyberpanel home looks like this ls /home

cyberpanelrocks.org         customer1.com        api.customer1.com
backups                   cyberpanel               panel.cyberpanelrocks.org
docker                    vmail

Can you post the results of the following command

$ fdisk -l

Ideally the sequence of creating a new partition and mounting it as a volume is pretty simple I am still not sure if it work for an already setup cyberpanel installation

  1. creating the partition from free space
  2. creating a file system on/in that partition
  3. mounting the new filesystem making it a volume
  4. copy over /home folder
  5. update os file system table using fstab
  6. run checks like df /dev/sdb3 assuming /dev/sb3 is the new volume

You can try these steps on a fresh installation if you are at liberty to. I do not guarantee they will make cyberpanel still work but ideally these are the steps to move /home directory to a new drive (hdd/ssd)

3

Thanks a million - i’m okay in my world and hate to ask , so really appreciate your answer.

some additional research brought me to How to Convert a /Home Directory to Partition in Linux

which looks pretty similar to what you are recomending, am i correct?

btw - nice to meet :smiley: and thanks for taking the effort
xx

4

Yes pretty much. I believe all these steps should be done before setting up cyberpanel. This is ideally the way!

5

the fdisk results:

aristotle@VM-cberpanel:~$ sudo fdisk -l
Disk /dev/loop0: 55.62 MiB, 58310656 bytes, 113888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop1: 55.62 MiB, 58310656 bytes, 113888 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop2: 63.24 MiB, 66301952 bytes, 129496 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop3: 63.28 MiB, 66347008 bytes, 129584 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop4: 91.83 MiB, 96272384 bytes, 188032 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop5: 49.64 MiB, 52031488 bytes, 101624 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop6: 49.85 MiB, 52248576 bytes, 102048 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop7: 91.85 MiB, 96292864 bytes, 188072 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/sda: 8 GiB, 8589934592 bytes, 16777216 sectors
Disk model: Virtual Disk
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xb873880d

Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 16775167 16773120 8G 7 HPFS/NTFS/exFAT

Disk /dev/sdb: 30 GiB, 32213303296 bytes, 62916608 sectors
Disk model: Virtual Disk
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 0BF5CEA1-33AC-426E-AD8B-9F211198DEC8

Device Start End Sectors Size Type
/dev/sdb1 227328 62916574 62689247 29.9G Linux filesystem
/dev/sdb14 2048 10239 8192 4M BIOS boot
/dev/sdb15 10240 227327 217088 106M EFI System

Partition table entries are not in disk order.

Disk /dev/sdc: 50 GiB, 53687091200 bytes, 104857600 sectors
Disk model: Virtual Disk
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/loop8: 1.48 GiB, 1572864000 bytes, 3072000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

6

sorry missed your reply - okay thank much - i think i can sort it now. again. much appreciated.