SAMBA Network Share conundrum

Home Forums GeeXboX for PC SAMBA Network Share conundrum

This topic contains 28 replies, has 2 voices, and was last updated by  tomlohave 2 years, 5 months ago.

Viewing 15 posts - 1 through 15 (of 29 total)
  • Author
  • #11556


    I’m running GeexBox on an old PC. I seem to have achieved headless status, accessing the box via telnet.
    My goal is to use it to stream over my LAN to a DLNA capable device. It worked fine at first using an external USB HDD and the various media showed up properly in both the media browser on the player, as well as the network shares over LAN.

    However, I recently upgraded to a larger storage device (5TB), and copied the contents over. Now the new device appears both in the media player as well as on the network, but the shared drive is showing as empty while I know for fact that it has approximately 3TB worth of media on it.
    The drive is formatted NTFS (as was the previous drive).
    Other than brand and storage capacity, there really doesn’t seem to be anything different that I can tell.
    The drive auto-mounted as expected, but the contents simply will not show.
    Any assistance would be greatly appreciated.

    • This topic was modified 2 years, 5 months ago by  Devlah.



    let’s try to begin : as you can access geexbox via telnet :
    what returns
    cat /proc/mounts
    df -h




    Thanks for the reply. Here’s what we have:

    # cat /proc/mounts
    rootfs / rootfs rw 0 0
    /dev/sda1 / ext4 rw,relatime,data=ordered 0 0
    proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
    sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
    devtmpfs /dev devtmpfs rw,nosuid,size=1535572k,nr_inodes=383893,mode=755 0 0
    tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
    devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
    tmpfs /run tmpfs rw,nosuid,nodev,mode=755 0 0
    tmpfs /sys/fs/cgroup tmpfs rw,nosuid,nodev,noexec,mode=755 0 0
    cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd 0 0
    cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
    cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpuacct,cpu 0 0
    cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
    cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
    cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
    mqueue /dev/mqueue mqueue rw,relatime 0 0
    debugfs /sys/kernel/debug debugfs rw,relatime 0 0
    tmpfs /tmp tmpfs rw 0 0
    configfs /sys/kernel/config configfs rw,relatime 0 0
    fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
    tmpfs /media tmpfs rw,relatime 0 0
    /dev/sda1 /mnt/SATA\040Disk\040#1\040GeeXboX\040(0) ext4 rw,relatime,data=ordered 0 0


    # df -h
    Filesystem                Size      Used Available Use% Mounted on
    rootfs                  146.5G    878.4M    145.7G   1% /
    /dev/sda1               146.5G    878.4M    145.7G   1% /
    devtmpfs                  1.5G         0      1.5G   0% /dev
    tmpfs                     1.5G         0      1.5G   0% /dev/shm
    tmpfs                     1.5G    202.4M      1.3G  13% /run
    tmpfs                     1.5G         0      1.5G   0% /sys/fs/cgroup
    tmpfs                     1.5G     20.0K      1.5G   0% /tmp
    tmpfs                     1.5G         0      1.5G   0% /media
    /dev/sda1               146.5G    878.4M    145.7G   1% /mnt/SATA Disk #1 GeeXboX (0)

    Now curiously, it appears that the 5TB drive is not showing in the list of volumes above, however, when I navigate to /mnt it clearly shows up.

    # ls
    SATA_Disk_1_GeeXboX_0         SATA_Disk_2_WabashMedia5TB_0  USB_Disk_2_TOSHIBA_EXT_0      USB_Disk_2_UUI_0

    Does this mean I need to manually edit the FSTAB to include the “SATA_Disk_2_WabashMedia5TB_0” ?
    I’m not entirely ignorant of Linux, but I don’t use it enough to be as literate as I could be.



    just to be sure, do you have ntfs-3g package installed ?
    opkg update && opkg install ntfs-3g

    for , right now unknown reason , your drive is not well mounted

    You can off course edit /etc/fstab to force the mount of your usb hard drive, but it should already work, without this.

    What version of geexbox do you use ?
    Everything should be now mounted on /media

    Can you post the results of

    (pastebin is your friend here :p)

    Cheers !


    # opkg update && opkg install ntfs-3g
    Updated list of available packages in /var/lib/opkg//snapshots.
    Package ntfs-3g (2012.1.15-1) installed in root is up to date.

    If it wasn’t before, then it should be now. :/

    The results of DMESG:

    • This reply was modified 2 years, 5 months ago by  Devlah. Reason: Using Pastebin



    [ 4.642396] sd 4:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
    [ 5.492060] sdb: sdb1 sdb2
    [ 5.493146] sd 4:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
    [ 5.495521] sd 4:0:0:0: [sdb] Attached SCSI disk

    I think that’s maybe the problem

    you can try that just to confirm :

    cd /root
    mkdir sdb1
    mkdir sdb2
    mount /dev/sdb1 /root/sdb1
    mount /dev/sdb2 /root/sdb2

    Do you have errors mounting the disk ?

    As I can see, you are using a very old version of GeeXbox.
    Maybe trying a newer one can solve this issue (


    # cd /root
    # mkdir sdb1
    # mkdir sdb2
    # mount /dev/sdb1 /root/sdb1
    NTFS signature is missing.
    Failed to mount '/dev/sdb1': Invalid argument
    The device '/dev/sdb1' doesn't seem to have a valid NTFS.
    Maybe the wrong device is used? Or the whole disk instead of a
    partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
    mount: mounting /dev/sdb1 on /root/sdb1 failed: Invalid argument
    # mount /dev/sdb2 /root/sdb2
    Failed to write lock '/dev/sdb2': Resource temporarily unavailable
    Error opening '/dev/sdb2': Resource temporarily unavailable
    Failed to mount '/dev/sdb2': Resource temporarily unavailable
    mount: mounting /dev/sdb2 on /root/sdb2 failed: Invalid argument

    I’ll see about updating to a newer version of GeexBox. Be back with news when that’s done.



    Hum, and off course it could be related to 32 bits arch too …

    Then you have 2 solutions :
    * split partitions to max 2TB
    * install a 64 bits version if you can



    Out of curiosity, is there a method I could use to apply the update remotely, or do I need to uproot the machine from it’s place of residence and treat it like a fresh install?



    You can upgrade using opkg, but I think you will be the first one to test that : ie from a so old version

    just edit /etc/opkg/opkg.conf
    and point the link to packages ie :

    src snapshots

    But you can’t change the arch …

    • This reply was modified 2 years, 5 months ago by  tomlohave.


    and do

    opkg update 
    opkg upgrade


    Done. However…When executing “opkg upgrade” every package “has no valid architecture, ignoring.”

    It IS a fairly old machine, I’m not entirely certain that the chip architecture supports x64. I’ll have to investigate. If it does, then it’ll be worth it to make a new Live USB and start all over.



    No valid architecture ?
    you were using i386 ? right ?

    Maybe starting from a clean install is the best solution.



    tested : seems to work here : (from a 3.1 release, i386)

    # opkg update
    Updated list of available packages in /var/lib/opkg/lists/snapshots.
    # opkg upgrade
    Upgrading gcc-final on root from 4.7.3-1 to 4.9.3-3...
    Installing glibc (2.23-3) to root...
    Removing package eglibc from root...
    Upgrading libXrandr on root from 1.4.0-1 to 1.5.1-1...
    Upgrading perl-test-deep on root from 0.108-1 to 0.108-2...
    Upgrading xf86-video-virtualbox on root from 4.2.12-84980-1 to 5.1.8-111374-1...


    The Original image used to setup this machine was: geexbox-3.1-x86_64.iso. That was back on 2/5/2017

    I’ve now downloaded: geexbox-devel-20170215-rabd3c04-x86_64.iso

    Hopefully this will make a difference.

Viewing 15 posts - 1 through 15 (of 29 total)

You must be logged in to reply to this topic.