Odroid HC2 - cant use/mount Hard Disk -edited

rob33 · 18 June 2018 18:23

First of all, a big compliment! DietPi is super cool!
Unfortunately, I can’t use the hard disk on my odroid hc2. I did a fresh install an i want to use the harddrive(2tb) as for my userdata (nextcloud, ampache…)

During isntall i cant choose the drive for my useredata and i cant mount it with the drive’_manager.
Know after fitst install i tried to format the drive and mount in manually.

Unfortunatelly i still cant use the drive for my userdata. The Strange thing is, that the drive_manager says that the user data is on sda1 and on mmcblk1p1.

Why is sda1 under drive_manager only 15G big? lsbkid shows me the 1.8tb drive as sda1??

Is this normal must i expand the drive?

drive_manager shows this:

lsblk

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1.8T 0 disk
└─sda1 8:1 0 1.8T 0 part /datastore
mmcblk1 179:0 0 14.9G 0 disk
├─mmcblk1p1 179:1 0 71M 0 part /boot
└─mmcblk1p2 179:2 0 14.8G 0 part /

nano /etc/fstab

#Samba Client------------------------------------------------------
#/mnt/samba . Please use dietpi-config and the Networking Options: NAS menu to setup this mount

#FTP Client Mount--------------------------------------------------
#/mnt/ftp_client . Please use dietpi-config and the Networking Options: NAS menu to setup this mount

#NFS Client Mount--------------------------------------------------
#/mnt/nfs_client . Please use dietpi-config and the Networking Options: NAS menu to setup this mount

#TMPFS / MISC ------------------------------------------------------
proc /proc proc defaults 0 0
tmpfs /tmp tmpfs defaults,size=1023M,noatime,nodev,nosuid,mode=1777 0 0
tmpfs /var/log tmpfs defaults,size=20m,noatime,nodev,nosuid,mode=1777 0 0
tmpfs /DietPi tmpfs defaults,size=10m,noatime,nodev,nosuid,mode=1777 0 0

#Internal Drives---------------------------------------------------
UUID=af314fbe-6db6-4970-84b4-19fd22bd6bf7 / auto defaults,noatime 0 0
UUID=7451-4AA3 /boot auto defaults,noatime 0 0
UUID=cce05d0d-6515-497e-a473-b5660d25ab86 / auto defaults,noatime 0 0
/var/swap none swap sw 0 0
UUID=“cce05d0d-6515-497e-a473-b5660d25ab86” /datastore ext4 defaults 0 0

I really hope you can help me. I love dietpi!

prupert · 30 June 2018 09:18

I’ve come across exactly the same issue, it seems the install incorrectly attempts to mount both the SD card and the internal HDD to the same location “/”.

blkid gives

/dev/sda1: LABEL="data" UUID="674cab58-5a9b-4d7a-826b-a5d30218f232" TYPE="ext4" PARTUUID="00008401-01" #internal HDD
/dev/mmcblk1p1: SEC_TYPE="msdos" LABEL="BOOT" UUID="7451-4AA3" TYPE="vfat" PARTUUID="000f1766-01" #SD card
/dev/mmcblk1p2: LABEL="rootfs" UUID="af314fbe-6db6-4970-84b4-19fd22bd6bf7" TYPE="ext4" PARTUUID="000f1766-02" #SD card
/dev/mmcblk1: PTUUID="000f1766" PTTYPE="dos"

/etc/fstab has been auto set as

#Samba Client------------------------------------------------------
#/mnt/samba . Please use dietpi-config and the Networking Options: NAS menu to setup this mount
#FTP Client Mount--------------------------------------------------
#/mnt/ftp_client . Please use dietpi-config and the Networking Options: NAS menu to setup this mount
#NFS Client Mount--------------------------------------------------
#/mnt/nfs_client . Please use dietpi-config and the Networking Options: NAS menu to setup this mount
#TMPFS / MISC ------------------------------------------------------
proc            /proc           proc    defaults                                                                                        0 0
tmpfs /tmp tmpfs defaults,size=1023M,noatime,nodev,nosuid,mode=1777 0 0
tmpfs                   /var/log                tmpfs   defaults,size=20m,noatime,nodev,nosuid,mode=1777  0 0
tmpfs                   /DietPi                 tmpfs   defaults,size=10m,noatime,nodev,nosuid,mode=1777        0 0
#Internal Drives---------------------------------------------------
UUID=af314fbe-6db6-4970-84b4-19fd22bd6bf7    /    auto    defaults,noatime    0 0
UUID=7451-4AA3    /boot    auto    defaults,noatime    0 0
UUID=674cab58-5a9b-4d7a-826b-a5d30218f232    /    auto    defaults,noatime    0 0
/var/swap    none    swap    sw    0   0

You can see under #Internal drives both the HDD and SD card have been assigned the / mount point. Luckily, as the SD card is listed first, the whole system actually works!

If it helps, here is my bug report: 46f39b8c-d723-4434-bb40-e0983f74e0f7

prupert · 30 June 2018 09:49

Simply changing the mount point for the HDD drive to mnt/dietpi_userdata somewhat sorts this - as dietpi disk manager can now see the drive and notes the correct location of user data, but this then seems to result in lots of issues as the installation is now confused since it complains that certain /xxx/xxxx locations are the same as /mnt/dietpi_userdata/xxxx locations. This caused paticular issues with a pre-existing Nextcloud installation and uninstalling and re-installing Nextcloud did not help (lots of the same errors as above where two locations were apparently the same).

So, fabbo.