Trouble mounting/navigating to second drive on NUC8?

RailsD · November 26, 2021 at 9:52 PM

I'm new to Linux (read: started today), but eager to learn.

Read through this thread from a couple weeks back but didn't see any resolution. I'm in a very similar situation and could use assistance. I've troubleshooted to a point where I believe the drive is properly formatted and mounted.

LibreElec is installed on my NVME. I wish to keep the OS (and containers?) on the 500GB NVME and storage on my 2.5mm 2TB drive.

df -h

Code

Filesystem                Size      Used Available Use% Mounted on
devtmpfs                  3.7G      4.0K      3.7G   0% /dev
tmpfs                     1.5G      9.3M      1.5G   1% /run
/dev/nvme0n1p1          511.7M    263.7M    248.0M  52% /flash
/dev/loop0              243.0M    243.0M         0 100% /
/dev/nvme0n1p2          457.0G    822.6M    456.1G   0% /storage
tmpfs                     3.8G         0      3.8G   0% /dev/shm
tmpfs                     4.0M         0      4.0M   0% /sys/fs/cgroup
tmpfs                     3.8G      2.8M      3.8G   0% /var
tmpfs                     3.8G      4.0K      3.8G   0% /tmp
/dev/sda1                 1.8T     76.0M      1.7T   0% /var/media/media

Display More

parted -l

Code

Model: ATA ST2000LM015-2E81 (scsi)
Disk /dev/sda: 2000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:

Number  Start   End     Size    File system  Name   Flags
 1      32.3kB  2000GB  2000GB  ext4         MEDIA


Model: Samsung SSD 970 EVO Plus 500GB (nvme)
Disk /dev/nvme0n1: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number  Start   End    Size   Type     File system  Flags
 1      4194kB  541MB  537MB  primary  fat16        boot, lba
 2      541MB   500GB  500GB  primary  ext4

Display More

I cannot seem to navigate to the drive. I'm sure this is user error, but nothing I'm trying seems to work.

While I'm at it, is it possible to run the docker containers off my NVME yet store my downloads on the HDD? I'm trying to follow this guide for setting up directories but I'm not sure I understand how to specify the download location being on a different drive? Looking at their docker-compose example:

Code

volumes:
      - /etc/localtime:/etc/localtime:ro
      - /docker/appdata/radarr:/config
      - /data:/data

is it as simple as adding /dev/sda1/data (or /media/data/ ?)

It's likely painfully obvious how over my head I am, but as I said I'm very eager to learn. Just seems I've hit a roadblock atm and am stuck. Any help is appreciated!

**heitbaum** · November 26, 2021 at 10:36 PM

Yes. Is the quick answer. Something similar is how I do things at the bottom.

Things to consider: overlays, symbolic links (ln) docker configuration, if it breaks it all goes bad. I have grabbed a section my autostart.sh. Please don’t use it as-is. As I use my nvme0n1p6 drive as DATA but also store my docker setups.

For running a docker container - I use

Code

docker run --workdir /var/media/DATA/home-rudi/LibreELEC.tv --privileged -v /storage:/storage -v /var/media/DATA:/var/media/DATA -it le-focal:latest bash

There is no reason if you wanted /var/media/DATA as DATA - use

-v /var/media/DATA:/DATA

My autostart changes - don’t use as-is

Code

more .config/autostart.sh 
(
        # mount the overlays
        mkdir -p /storage/.kodi/userdata/addon_data/service.system.docker/docker/overlay2
        mkdir -p /var/media/DATA
        mount -o rw,suid,dev,exec,atime /dev/nvme0n1p6 /var/media/DATA
        mount -o rw,suid,dev,exec,atime /var/media/DATA/.docker/overlay2 /storage/.kodi/userdata/addon_data/service.system.docker/docker/overlay2



        mkdir /var/media/ramdisk
        mount -t tmpfs -o size=32g tmpfs /var/media/ramdisk
        # docker pull oznu/homebridge:ubuntu
        # docker container prune
        # docker run --net=host --name=homebridge -v /storage/homebridge:/homebridge oznu/homebridge:ubuntu
        docker restart homebridge
) &

Display More

RailsD · November 26, 2021 at 11:17 PM

Well I feel like an idiot, you've inadvertently helped me realize I've been trying to access the HDD in every way but the right one.

so based on my file structure

Code

/dev/sda1                 1.8T     76.0M      1.7T   0% /var/media/media

I should makdir /var/media/data/

then my code will be

-v /var/media/data:/data for each image in my docker-compose? Is this correct? The second media folder contains lost+found.

To confirm my understanding: The above indicates that, in my instance, the "real" data is stored on my HDD while the container reads/links from the NVME.

If I understood, thats great news for me and I can continue chugging away at getting this figured out! I'm way over my head, but it's a lot of fun so far

I haven't even begun to look into autostart configs, so that should be a great can of worms when I get to it. I appreciate your reply!

**heitbaum** · November 28, 2021 at 2:14 AM

Stepping back a bit: the udevil service on LE mounts the hard drives under /var/media

Any disk that does not meet the following conditions is automatically mounted - https://github.com/LibreELEC/Libr…vil-mount.rules if you do not want something automounted by udevil - then it must be excluded by one of these criteria.

Going to your question - using the docker argument: -v /var/media/data:/data would be like typing the following command in the Docker container: # mount /dev/sda1 /data

So it’s not really an nvme / sata question. More as saying - I am mounting a directory from my host operating system as a mount point in my container.

Code

# journalctl -f
***** I disconnected my USB drive with a disk label of ZZ4
Nov 28 12:54:33 nuc11 kernel: usb 4-4.2.2: USB disconnect, device number 6
Nov 28 12:54:33 nuc11 systemd[1]: Stopping Udevil mount service...
Nov 28 12:54:33 nuc11 systemd[1]: var-media-ZZ4.mount: Deactivated successfully.
Nov 28 12:54:33 nuc11 systemd[1]: udevil-mount@-dev-sdc2.service: Deactivated successfully.
Nov 28 12:54:33 nuc11 systemd[1]: Stopped Udevil mount service.
***** I connected my USB drive with a disk label of ZZ4
Nov 28 12:54:37 nuc11 kernel: usb 4-4.2.2: new SuperSpeed USB device number 7 using xhci_hcd
Nov 28 12:54:37 nuc11 kernel: usb-storage 4-4.2.2:1.0: USB Mass Storage device detected
Nov 28 12:54:37 nuc11 kernel: scsi host4: usb-storage 4-4.2.2:1.0
Nov 28 12:54:38 nuc11 kernel: scsi 4:0:0:0: Direct-Access     WD       Elements 25A1    1005 PQ: 0 ANSI: 6
Nov 28 12:54:38 nuc11 kernel: scsi 4:0:0:0: Attached scsi generic sg2 type 0
Nov 28 12:54:38 nuc11 kernel: sd 4:0:0:0: [sdc] Spinning up disk...
Nov 28 12:54:44 nuc11 kernel: ......ready
Nov 28 12:54:44 nuc11 kernel: sd 4:0:0:0: [sdc] 3906963456 512-byte logical blocks: (2.00 TB/1.82 TiB)
Nov 28 12:54:44 nuc11 kernel: sd 4:0:0:0: [sdc] Write Protect is off
Nov 28 12:54:44 nuc11 kernel: sd 4:0:0:0: [sdc] Mode Sense: 53 00 10 08
Nov 28 12:54:44 nuc11 kernel: sd 4:0:0:0: [sdc] No Caching mode page found
Nov 28 12:54:44 nuc11 kernel: sd 4:0:0:0: [sdc] Assuming drive cache: write through
Nov 28 12:54:44 nuc11 kernel:  sdc: sdc1 sdc2
Nov 28 12:54:44 nuc11 kernel: sd 4:0:0:0: [sdc] Attached SCSI disk
Nov 28 12:54:45 nuc11 systemd[1]: Starting Udevil mount service...
Nov 28 12:54:45 nuc11 udevil[3486724]: Mounted /dev/sdc2 at /media/ZZ4
Nov 28 12:54:45 nuc11 systemd[1]: Finished Udevil mount service.

# mount | grep ZZ4
/dev/sdc2 on /var/media/ZZ4 type exfat (rw,nosuid,nodev,noexec,noatime,fmask=0022,dmask=0022,iocharset=utf8,errors=remount-ro)

Display More

GDPR-7 · November 28, 2021 at 3:38 PM

Quote from heitbaum

if you do not want something automounted by udevil - then it must be excluded by one of these criteria.

AFAIK, "masking" of the appropriate service in systemctl will do too, e.g.

systemctl mask udevil-mount@....

Trouble mounting/navigating to second drive on NUC8?

Similar Threads

New 10.0 install on Raspberry Pi 4 does nothing...