Unable to select mounted device from dropdown

    • OMV 3.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Again, I'm new at this, so please be patient with me.

      I downloaded PuTTY and used SSH to get to my Raspberry Pi, but it's calling for a password, and the only password I know is the default admin password I use to get to the openmediavault web interface. It's not accepting that.

      There's not another way to send that command to the Pi, is there?
    • when you installed omv3.x or 4.x, a root password was created.

      You need to use those credintial to log in:
      root / thepasswordyoucreated ( not admin/openmediavault, witch is the GUI password )
      ---------------------------------------------------------------------------------------------------------------------
      French, so forgive my english
      Personal Rig: valid.x86.fr/v72uek as a test bench with Oracle VM.
      And YES, my avatar is real, i am flying "parapentes" in St Hilaire du Touvet and at la coupe icare.
    • If you installed the image from here
      sourceforge.net/projects/openm…/Raspberry%20Pi%20images/

      make sure you read the notes.

      You have to enable SSH in the WebUI first. Then credentials for SSH are root/openmediavault.


      OMV_3_0_88_RaspberryPi_2_3_4.9.41.img.xz - OMV Erasmus - Uses 4.9 kernel update to latest official version - not based on Raspbian but Debian/armhf (only compatible to RPi 2 and 3!) - SSH keys are regenerated on first boot but SSH login has to be enabled in web UI prior to usage: Services --> SSH --> Permit root login - Please immediately change default passwords! - A third partition for data use will be automatically resized on first boot but you have to format it manually with the fs of your choice! -

      All details: forum.openmediavault.org/index.php/Thread/18991

      web interface:
      - username = admin
      - password = openmediavault

      console/ssh:
      - username = root
      - password = openmediavault
      Odroid HC2 - armbian - Seagate ST4000DM004 - OMV4.x
      Asrock Q1900DC-ITX - 16GB - 2x Seagate ST3000VN000 - Intenso SSD 120GB - OMV4.x
      :!: Backup - Solutions to common problems - OMV setup videos - OMV4 Documentation - user guide :!:
    • Update: I bought another USB hard drive, and this one is mounted. I have shared folders available. I have SMB/CIFS enabled, and I have my user account set up with read/write access.

      BUT what I still don't have is the final piece...the drive appearing as an option in Windows. It's just not there.

      What am I missing?

      Also, SSH is enabled, but it still won't take the root password. Is there a way to reset that?
      Images
      • Shared Folder.JPG

        85.34 kB, 1,366×730, viewed 114 times
      • SMB Enabled.JPG

        104.27 kB, 1,366×729, viewed 102 times
      • SSH Enabled.JPG

        85.62 kB, 1,366×729, viewed 98 times
    • 1) You have defined a Shared Folder.

      2) You have enabled SMB.

      3) In SMB Shares Tab, have you created the share there? You didn't post a screenshot so I'm guessing you did not. Won't work until you do.


      The root password was defined when you installed OMV. Did you write it down? It is not the same one used for the Web GUI admin account.
      OMV 4.x - ASRock Rack C2550D4I - 16GB ECC - Silverstone DS380
    • mediagiant wrote:

      There's not another way to send that command to the Pi, is there?
      You can create another user and add this user to the ssh and sudo group. This can be done in the WebUI from OMV.
      When done, you can use this user to access the server using SSH/Putty.


      mediagiant wrote:

      Also, SSH is enabled, but it still won't take the root password.
      If you want to login as root, you must also enable root login in the SSH settings of OMV.
      Odroid HC2 - armbian - Seagate ST4000DM004 - OMV4.x
      Asrock Q1900DC-ITX - 16GB - 2x Seagate ST3000VN000 - Intenso SSD 120GB - OMV4.x
      :!: Backup - Solutions to common problems - OMV setup videos - OMV4 Documentation - user guide :!:
    • Root login is enabled, but I wonder if I changed the root password and just don't remember it. (Any idea how one might reset the root password?)

      In any event, I found another way to SSH...but that didn't really get me very far.
      Images
      • SSH result.JPG

        54.58 kB, 670×453, viewed 110 times
      • SSH root login enabled.JPG

        85.9 kB, 1,366×729, viewed 74 times
    • Output:

      [{"fsname": "/dev/disk/by-label/Toshiba", "uuid": "c7ebeeca-d143-4fa6-858d-72828ad95b30", "hidden": false, "type": "ext4", "freq": 0, "dir": "/srv/dev-disk-by-label-Toshiba", "passno": 2, "opts": "defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl"}]
      $ [{"fsname": "/dev/disk/by-label/Toshiba", "uuid": "c7ebeeca-d143-4fa6-858d-72828ad95b30", "hidden": false, "type": "ext4", "freq": 0, "dir": "/srv/dev-disk-by-label-Toshiba", "passno": 2, "opts": "defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl"}]
      -dash: 2: [{fsname:: not found
    • gderf wrote:

      The root password was defined when you installed OMV
      Not on any of the ARM images (RPi included). There it's predefined and has to be changed by the user later.

      The other common problems that pop up in this thread as follows: users don't read the instructions at the download site, especially the most important part:

      Source Code

      1. On first boot the installation will be finished. REMAIN PATIENT PLEASE
      2. since this can take up to 30 minutes with a slow SD card and slow internet
      3. connection (needs internet access to update all packages to latest version).
      4. After one automatic reboot green activity led stops blinking and then your
      5. Raspberry Pi is ready!
      There are tons of threads here that deal with obscure problems on RPis and it's alway the result of not following this simple first step. The screenshot @mediagiant posted shows clearly a horribly outdated kernel version and pending security updates so this first step has never happened and so NTFS will never work (since drivers are missing, same with Wi-Fi and a lot of other stuff) and the whole installation is in a somewhat instable state.

      Most simple solution: start from scratch this time following the readme. Maybe just to realize that Raspberry Pis are crap as a NAS at least with host powered disks since undervoltage is then a huge issue which leads to all sorts of strange problems and even filesystem corruption later. Everything outlined in detail in the thread that is referenced by the readme at the download page (the text no one is reading obviously).

      As a rule of thumb: the best way to use OMV with a Raspberry Pi is to replace the RPi with something more suited for the job prior to attaching any disk(s). Then continue...

      The post was edited 1 time, last by tkaiser ().

    • Getting closer. I installed a new NTFS file system on the drive (I think my mistake before was using ext4).

      But whenever I adjust my configuration, I get an error message. And when Windows asks for my password to access the drive, it doesn't work.
      Images
      • Failed to execute command.JPG

        97.66 kB, 1,366×728, viewed 113 times
      • Toshiba Visible.JPG

        63.46 kB, 684×584, viewed 81 times
    • mediagiant wrote:

      Getting closer
      Not even remotely. Your screenshot clearly states that the necessary module is missing and that you're at kernel 4.9.41.

      You failed to read the instructions that tell you that your RPi needs to be connected to the network at first boot and that you need to have patience since all packages will be updated on first boot and more importantly all the RPi support staff will then be installed. You somehow interfered with this and this problem can not be solved without the installation being finished.

      Stop now, read the instructions and start over from scratch this time allowing to installation to be finished in first boot. Or search the forum, there it's explained how this can be fixed manually.

      The post was edited 1 time, last by tkaiser ().

    • OK, so I started over with a fresh run of OMV. I actually got the new, blank drive to work.

      BUT I'd still like to get the old drive that has all my files on it to work as well.

      That drive is sdb1 now. I have the NTFS file system, and the drive is mounted. However, when I attempt to add a shared folder, I get an error message when I attempt to select a device. So, is this because there are files on this drive?

      If I can't get this mounted, does anyone have any thoughts on how I might quickly move the files to the drive that IS mounted? We're talking about nearly 500 GB of data, so pushing all that over the network at once does not seem efficient.
      Images
      • Device Mounted.JPG

        102.84 kB, 1,366×732, viewed 80 times
      • No such file or directory.JPG

        93.59 kB, 1,366×730, viewed 100 times
    • Did you mount the drive using the WebUI? Or did you mount is from CLI?
      If you want to use the drive with OMV you have to mount it using the WebUI.

      Alternative would be to copy the data using midnight commander from the CLI.

      Install with apt install mc
      and start with mc
      Odroid HC2 - armbian - Seagate ST4000DM004 - OMV4.x
      Asrock Q1900DC-ITX - 16GB - 2x Seagate ST3000VN000 - Intenso SSD 120GB - OMV4.x
      :!: Backup - Solutions to common problems - OMV setup videos - OMV4 Documentation - user guide :!:
    • There seem to be frequent issues with NTFS FS. So far I have not seen what the reason is.

      Have you tried mc to copy your data? I understand this is all you want for the moment.
      Odroid HC2 - armbian - Seagate ST4000DM004 - OMV4.x
      Asrock Q1900DC-ITX - 16GB - 2x Seagate ST3000VN000 - Intenso SSD 120GB - OMV4.x
      :!: Backup - Solutions to common problems - OMV setup videos - OMV4 Documentation - user guide :!: