Error mounting sambashare

    • Error mounting sambashare

      Helo people,

      I have OMV version 3.0.88, and I created a smb share, I can acces this share from my windows pc and my mac mini.
      now I have another Raspberry pi with raspbian and I want to mount the shared folder located on my OMV

      and I enter this code:

      Source Code

      1. pi@raspberrypi:/mnt $ sudo mount -t cifs //pinas.local/srv/dev-disk-by-id-ata-ST1000LM024_HN-M101MBB_S2ZPJ9AF409434-part1/Shares /mnt/samba -o user=user,pass=pass
      2. Retrying with upper case share name
      3. mount error(6): No such device or address
      4. Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)




      when I login at OMV and I type mount:
      i see this:


      Source Code

      1. root@pinas:/dev# mount
      2. /dev/mmcblk0p2 on / type ext4 (rw,noatime,data=ordered)
      3. devtmpfs on /dev type devtmpfs (rw,relatime,size=492508k,nr_inodes=123127,mode=755)
      4. sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
      5. proc on /proc type proc (rw,relatime)
      6. tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
      7. devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
      8. tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
      9. tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
      10. tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
      11. cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
      12. cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
      13. cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
      14. cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
      15. cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
      16. cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
      17. cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
      18. systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=23,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
      19. debugfs on /sys/kernel/debug type debugfs (rw,relatime)
      20. mqueue on /dev/mqueue type mqueue (rw,relatime)
      21. configfs on /sys/kernel/config type configfs (rw,relatime)
      22. fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
      23. tmpfs on /tmp type tmpfs (rw,relatime)
      24. /dev/mmcblk0p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro)
      25. /dev/sda1 on /srv/dev-disk-by-id-ata-ST1000LM024_HN-M101MBB_S2ZPJ9AF409434-part1 type ext4 (rw,noexec,relatime,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group)
      26. /dev/sda1 on /export/Shares type ext4 (rw,noexec,relatime,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group)
      27. /dev/mmcblk0p2 on /var/folder2ram/var/log type ext4 (rw,noatime,data=ordered)
      28. folder2ram on /var/log type tmpfs (rw,nosuid,nodev,noexec,relatime)
      29. /dev/mmcblk0p2 on /var/folder2ram/var/tmp type ext4 (rw,noatime,data=ordered)
      30. folder2ram on /var/tmp type tmpfs (rw,nosuid,nodev,noexec,relatime)
      31. /dev/mmcblk0p2 on /var/folder2ram/var/lib/openmediavault/rrd type ext4 (rw,noatime,data=ordered)
      32. folder2ram on /var/lib/openmediavault/rrd type tmpfs (rw,nosuid,nodev,noexec,relatime)
      33. /dev/mmcblk0p2 on /var/folder2ram/var/spool type ext4 (rw,noatime,data=ordered)
      34. folder2ram on /var/spool type tmpfs (rw,nosuid,nodev,noexec,relatime)
      35. /dev/mmcblk0p2 on /var/folder2ram/var/lib/rrdcached type ext4 (rw,noatime,data=ordered)
      36. folder2ram on /var/lib/rrdcached type tmpfs (rw,nosuid,nodev,noexec,relatime)
      37. /dev/mmcblk0p2 on /var/folder2ram/var/lib/monit type ext4 (rw,noatime,data=ordered)
      38. folder2ram on /var/lib/monit type tmpfs (rw,nosuid,nodev,noexec,relatime)
      39. /dev/mmcblk0p2 on /var/folder2ram/var/lib/netatalk/CNID type ext4 (rw,noatime,data=ordered)
      40. folder2ram on /var/lib/netatalk/CNID type tmpfs (rw,nosuid,nodev,noexec,relatime)
      41. /dev/mmcblk0p2 on /var/folder2ram/var/cache/samba type ext4 (rw,noatime,data=ordered)
      42. folder2ram on /var/cache/samba type tmpfs (rw,nosuid,nodev,noexec,relatime)
      43. nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
      44. binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime)
      45. tracefs on /sys/kernel/debug/tracing type tracefs (rw,relatime)
      46. tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=99424k,mode=700)
      47. rpc_pipefs on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
      Display All


      I don't understand line 25 and 26

      The shares folder is located here (OMV): /srv/dev-disk-by-id-ata-ST1000LM024_HN-M101MBB_S2ZPJ9AF409434-part1/Shares

      As i mentioned before: the share is accesible from my mac computer and windows computer.

      Does anyone know I to access my sambashare from my rasbian?

      regards,

      Ralph
    • please revise remotemount-plugin to see if satisfize your needs:
      Images
      • 1.jpg

        41.92 kB, 709×383, viewed 29 times
      OMV 3.0.88 x64 on a HP T510, 8GB CF as Boot Disk & 32GB SSD 2,5" disk for Data, 4 GB RAM, CPU VIA EDEN X2 U4200 is x64 at 1GHz

      Post: HPT510 SlimNAS ; HOWTO Install Pi-Hole ; HOWTO install MLDonkey ; HOHTO Install ZFS-Plugin ; OMV_OldGUI ; ShellinaBOX ;
    • raffie77 wrote:

      mount -t cifs //pinas.local/srv/dev-disk-by-id-ata-ST1000LM024_HN-M101MBB_S2ZPJ9AF409434-part1/Shares /mnt/samba -o user=user,pass=pass

      You try to use the local mountpoint on the OMV box using CIFS which simply can not work. You can check on the OMV server the share's name using the 'testparm' command, on the Raspbian box using 'smbclient -L pinas.local -U user' or check on macOS with 'df' after you mounted the CIFS share there. The CIFS URI will consist of a single path element like //pinas.local/samba for example.
      'OMV problems' with XU4 and Cloudshell 2? Nope, read this first. 'OMV problems' with Cloudshell 1? Nope, just Ohm's law or queue size.
    • raulfg3 wrote:

      please revise remotemount-plugin to see if satisfize your needs:
      Hi Raulfg,
      remote mount is not in my pluginlist, so I can't install it


      tkaiser wrote:

      raffie77 wrote:

      mount -t cifs //pinas.local/srv/dev-disk-by-id-ata-ST1000LM024_HN-M101MBB_S2ZPJ9AF409434-part1/Shares /mnt/samba -o user=user,pass=pass
      You try to use the local mountpoint on the OMV box using CIFS which simply can not work. You can check on the OMV server the share's name using the 'testparm' command, on the Raspbian box using 'smbclient -L pinas.local -U user' or check on macOS with 'df' after you mounted the CIFS share there. The CIFS URI will consist of a single path element like //pinas.local/samba for example.
      Thanks man that worked:

      I use this command now
      sudo mount //10.0.1.23/Shares/Muziek /mnt/samba/ -o username=user,password=password
      and I see the files @ /mnt/samba

      thanks a lot! :thumbup:
    • raffie77 wrote:

      sudo mount //10.0.1.23/Shares/Muziek /mnt/samba/ -o username=user,password=password

      So this is stuff you could now add to /etc/fstab to make this persistent (check /etc/mtab on the Raspberry and add the nofail flag in any case!). If it's just enabling the connection on demand @geaves is right and this should work from the normal Raspbian GUI. But there exist countless reports that such 'GUI mounts' -- at least when relying on Gnome Virtual File System (gvfs) with version prior to 3.0 -- result in a severe CIFS performance drop. On the other hand Raspberries are that bottlenecked by their slow network that it should be irrelevant here anyway. And 'Muziek' sounds like bandwidth requirements are below 1 MB/s anyway :)
      'OMV problems' with XU4 and Cloudshell 2? Nope, read this first. 'OMV problems' with Cloudshell 1? Nope, just Ohm's law or queue size.
    • ohhhh boy

      I add a line in /etc/mtab and restarted the pi and now my root account is locked, see attached file.
      it doesn't mater how many times I press enter, it keeps saying the same.
      I googled it and most users who had this problem where able to login in the shell, i can't

      when I enter my SD card into my mac, I see only the image with the overlay folder etc, so that doesn't help. I use berryboot btw.

      does anyone had a idea how to fix this?
      Images
      • IMG_20170919_193721.jpg

        838.48 kB, 2,232×1,260, viewed 28 times
    • raffie77 wrote:

      does anyone had a idea how to fix this?
      If it's really related to your fstab modification (/etc/mtab isn't adjustable) the most simply approach is to use a Linux system (your OMV Raspberry for example), an USB card reader, the card mounted there and reverting the change.

      If you don't have such an USB card reader but your Mac is a MacBook check for an SD card slot (they were equipped with such a thing a few years, IIRC it stopped in 2016). If there's an SD card slot you could use VirtualBox with the card reader mapped to Linux and any 'rescue Linux' distro to do this.

      It might be possible to access ext4 partitions directly on macOS (do a web search for 'fuse ext4 mac') but at least I have no experiences whether it really works.
      'OMV problems' with XU4 and Cloudshell 2? Nope, read this first. 'OMV problems' with Cloudshell 1? Nope, just Ohm's law or queue size.
    • tkaiser wrote:

      raffie77 wrote:

      does anyone had a idea how to fix this?
      If it's really related to your fstab modification (/etc/mtab isn't adjustable) the most simply approach is to use a Linux system (your OMV Raspberry for example), an USB card reader, the card mounted there and reverting the change.
      If you don't have such an USB card reader but your Mac is a MacBook check for an SD card slot (they were equipped with such a thing a few years, IIRC it stopped in 2016). If there's an SD card slot you could use VirtualBox with the card reader mapped to Linux and any 'rescue Linux' distro to do this.

      It might be possible to access ext4 partitions directly on macOS (do a web search for 'fuse ext4 mac') but at least I have no experiences whether it really works.
      well that got my heart raised :S
      I had a other raspian image, I booted that and entered my "bad" sd card in a usb card reader and inserted that in my pi.
      I opened the file explorer and searched for my usb storage.
      go to /etc
      open that folder in terminal (right mouse button on etc)
      sudo nano fstab
      and removed that bad line (you were right it was the fstab)
      Booted again and it all works.

      well listen kids: don't ever just copy/paste lines in fstab if you (like me) don't know what your doing :P
      Tomorrow I'll make a study about how to use the fstab.

      @tkaiser thanks a lot you're a big help :thumbup:
      thanks man
    • raffie77 wrote:

      I had a other raspian image, I booted that and entered my "bad" sd card in a usb card reader and inserted that in my pi.

      If you're already there think about cloning your SD card now (just like HDDs they'll all die so preparing for this is always a good idea): forum.armbian.com/index.php?/t…findComment&comment=21126
      'OMV problems' with XU4 and Cloudshell 2? Nope, read this first. 'OMV problems' with Cloudshell 1? Nope, just Ohm's law or queue size.
    • raffie77 wrote:

      I found a real nice article about how to clone your SD card with a mac: link
      O no, this is just a compilation how NOT to do it. :(
      • Using dd is always wrong
      • using /dev/diskX instead of /dev/rdiskX is always wrong
      • 'formatting' a card in any way when it will be completely overwritten in the next step is always wrong since just a waste of time
      • when playing with dd not using at least 'bs=1m' is always wrong (takes ages for nothing since reading only 512 byte at a time)
      Better variant:
      • To read an SD card use ddrescue, this tool cares about your data unlike dd! On a Mac get homebrew, do a 'brew install ddrescue' and from then on 'sudo ddrescue /dev/rdisk2 yourimage.img'
      • Use SD association's 'SD formatter' not to 'format' the card (useless anyway) but to perform the equivalent of a TRIM operation (ERASE CMD38, choose 'full erase')
      • Never write an image with dd but use Etcher instead (since it cares about your data unlike dd!)
      'OMV problems' with XU4 and Cloudshell 2? Nope, read this first. 'OMV problems' with Cloudshell 1? Nope, just Ohm's law or queue size.

      The post was edited 2 times, last by tkaiser ().

    • raffie77 wrote:

      Ill install homebrew end ddrescue

      It's a matter of minutes, ddrescue will tell you if there is any reading trouble and performance is also great. The card reader in my MacBook writes/reads with up to 80MB/s and ddrescue on average reads with ~40MB/s (though different story since the card reader is passed through to a Linux virtual machine that checks the OS images directly after)
      'OMV problems' with XU4 and Cloudshell 2? Nope, read this first. 'OMV problems' with Cloudshell 1? Nope, just Ohm's law or queue size.
    • Users Online 1

      1 Guest