Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Plugin: Drive Mount (simple features required)

Featured Replies

Was never mounted in unmenu till after trying to use the plug in.  Formatted unmounted disk /dev/sdn with partition /dev/sdn1, unmenu not even running after a reboot.  Install the plugin and immediately shows as I listed above, showing the drive as (/dev/sd), mount point of /boot and saying it's enabled.  Try to make changes and as described, nothing changes, remove plugin reboot and use unmenu to mount and share the drive for now, because it at least worked for me.  Would prefer to use gui plugin and a name for the mount point other than the "likely to change disk designation" /dev/sdn1

Did you give the disk a volume label of UNRAID, because typically the disk with that label is mounted at /boot.

 

Joe L.

  • Replies 94
  • Views 21.6k
  • Created
  • Last Reply

in my case

root@p5bplus:~#  ls /dev/disk/by-id/* -l | grep -v -- "-part" | grep -v -- "wwn" | grep -v -- "ata" | cut -c60-
scsi-SATA_Hitachi_HDT7210_STF607MH3N350K -> ../../sdv
scsi-SATA_Hitachi_HDT7210_STF6L7MS38PHNK -> ../../sdx
scsi-SATA_SAMSUNG_HD204UIS2H7J9BB209163 -> ../../sdi
scsi-SATA_SAMSUNG_HD204UIS2H7J9BB209255 -> ../../sdj
scsi-SATA_SAMSUNG_HD204UIS2H7J9JB614304 -> ../../sdh
scsi-SATA_SAMSUNG_HD501LJS0MUJ1FP838164 -> ../../sdw
scsi-SATA_WDC_WD10EACS-00_WD-WCASJ1706614 -> ../../sdm
scsi-SATA_WDC_WD10EACS-00_WD-WCAU45503540 -> ../../sdg
scsi-SATA_WDC_WD10EADS-00_WD-WCAU47390558 -> ../../sdd
scsi-SATA_WDC_WD10EADS-00_WD-WCAU4C232503 -> ../../sdr
scsi-SATA_WDC_WD10EADS-00_WD-WCAU4C868355 -> ../../sds
scsi-SATA_WDC_WD10EADS-00_WD-WCAU4C868508 -> ../../sdq
scsi-SATA_WDC_WD10EADS-00_WD-WCAU4D176083 -> ../../sdp
scsi-SATA_WDC_WD10EADS-00_WD-WCAV50808985 -> ../../sdb
scsi-SATA_WDC_WD10EADS-00_WD-WMAV50182262 -> ../../sdf
scsi-SATA_WDC_WD10EADS-11_WD-WCAV5A500947 -> ../../sdo
scsi-SATA_WDC_WD10EARS-00_WD-WCAV5F042945 -> ../../sdk
scsi-SATA_WDC_WD10EARS-00_WD-WCAV5M103508 -> ../../sdt
scsi-SATA_WDC_WD10EARS-00_WD-WCAV5M598858 -> ../../sdl
scsi-SATA_WDC_WD10EARS-00_WD-WCAZA0747326 -> ../../sdn
scsi-SATA_WDC_WD10EARS-22_WD-WCAV5H743762 -> ../../sdc
scsi-SATA_WDC_WD5000AAKS-_WD-WCATR3564669 -> ../../sde
scsi-SATA_WDC_WD7500AACS-_WD-WCASM0013559 -> ../../sdu
usb-Swissbit_miniTWIST_000010004631BE0001d9-0:0 -> ../../sda

 

and

 

# drive_mount configuration
[scsi-SATA_WDC_WD5000AAKS-_WD-WCATR3564669]
DRIVE_NAME="sde"
DRIVE_MOUNT=""
DRIVE_MOUNTED="disable"
DRIVE_ENABLED="disable"
[usb-Swissbit_mi]
DRIVE_NAME="issbit_mi"
DRIVE_MOUNT=""
DRIVE_MOUNTED="disable"
DRIVE_ENABLED="disable"

 

mounttool.jpg

 

the disk showing above as mounted (sd)  is disk 19 in the array (sdn)

 

the swissbit is my UNRAID boot thumbdrive ...  in my eyes should also not show here ...

 

i don't dare to mount the 500gb trough the script now as i am afraid to mess up my array

using unmenu to mount him now but seems unmenu doesn't let him spin down ?

 

Oh Yeas just did a reboot to see if it solved things ... only thing what happened is that before he showed disk 13 in the array as mounted and now disk 19

i didn't do anything with the script not after install not after this reboot

 

I find it unusual that both you and I have disk SDN report as just SD, maybe something in the script is having a problem parsing SDN

  • 3 weeks later...

using unmenu to mount him now but seems unmenu doesn't let him spin down ?

Disks mounted via unMENU do have their internal spin-down timer set.  It sets a 1 hour spin-down timer.

 

This is a function built into most disks. 

The actual command used is:

          system("hdparm -S242 /dev/" substr(d[2],1,3) " >/dev/null")

 

-S242 = a 1 hour spindown timer.

 

You can use the hdparm command to set any spin-down interval you might desire within its available settings.

This is an excerpt from the manual page

-S

    Put the drive into idle (low-power) mode, and also set the standby (spindown) timeout for the drive. This timeout value is used by the drive to determine how long to wait (with no disk activity) before turning off the spindle motor to save power. Under such circumstances, the drive may take as long as 30 seconds to respond to a subsequent disk access, though most drives are much quicker. The encoding of the timeout value is somewhat peculiar. A value of zero means "timeouts are disabled": the device will not automatically enter standby mode. Values from 1 to 240 specify multiples of 5 seconds, yielding timeouts from 5 seconds to 20 minutes. Values from 241 to 251 specify from 1 to 11 units of 30 minutes, yielding timeouts from 30 minutes to 5.5 hours. A value of 252 signifies a timeout of 21 minutes. A value of 253 sets a vendor-defined timeout period between 8 and 12 hours, and the value 254 is reserved. 255 is interpreted as 21 minutes plus 15 seconds. Note that some older drives may have very different interpretations of these values.

I was attempting to use an extra thumb drive for my apps but I found that my server wouldn't boot - I think it is due to the fact that it is the same brand as my *real* boot thumb drive and the bios couldn't differentiate? Thoughts? Removing the new apps drive allowed my tower to boot as normal... odd.

 

It was an NTFS formatted thumb drive if that should affect anything, maybe try reiserfs?

I was attempting to use an extra thumb drive for my apps but I found that my server wouldn't boot - I think it is due to the fact that it is the same brand as my *real* boot thumb drive and the bios couldn't differentiate? Thoughts? Removing the new apps drive allowed my tower to boot as normal... odd.

 

It was an NTFS formatted thumb drive if that should affect anything, maybe try reiserfs?

no, probably just was trying to boot from it.  Did you go into the BIOS and select the correct flash drive to boot from????

 

Joe L.

I did, it only showed one USB as a boot option...

Benni, great plugin, but the UI doesn't work in Safari. I can get it working with FireFox no problems.. but the Mount Directory input never becomes editable in in Safari.

 

whiteatom

One more thing.. does anyone know how to set this plugin to auto-mount the drive before my other plugins start? I have sabnzbd starting as well, and it creates it's folders in /mnt/apps... and then the drive won't mount because the mount point's not empty.

 

I have to shut sabnzbd down, delete the files, manually mount the drive, and then restart sabnzbd... and this seems like it should be automatable.

 

Cheers,

 

whiteatom

Are you using the sabnzbd plugin?

I don't have a problem using sab/sb/cp/drive mount plugins. They are working nicely together.

 

Sent from my DROID2 using Tapatalk

  • 2 weeks later...

Several restarts... Sab is starting before the drive mounts, and then I get an error because there's stuff in the mount point folder. Any ideas what I might have done wrong?

 

Whiteatom

Several restarts... Sab is starting before the drive mounts, and then I get an error because there's stuff in the mount point folder. Any ideas what I might have done wrong?

 

Whiteatom

You are not delaying its start until after the arrray is online and disks mounted.

You are not delaying its start until after the arrray is online and disks mounted.

 

I haven't set it to do that.... Where would I find out if it's delayed or not?

 

Cheers,

 

whiteatom

hi

 

Just installed your plugin on 5.0-Beta14 ... is reports a syntax error in the drive_mount.sh script

 

root@Tower:/boot/config/plugins/drive_mount# ./drive_mount.sh update

./drive_mount.sh: eval: line 34: syntax error near unexpected token `}'

./drive_mount.sh: eval: line 34: `}'

root@Tower:/boot/config/plugins/drive_mount#

 

hence the webgui is blank and no drives can be mounted. Script looks ok to me - any idears ?

 

br. tsatsa

 

ps got the  plex-media-server-noarch-0.9.5.3a-ds.plg from link in this thread, script below:

 

#!/bin/bash

 

write_config() {

  echo "# drive_mount configuration" > /boot/config/plugins/drive_mount/drive_mount.cfg

  for INDEX in ${!device_id[@]}; do

echo "[${device_id[$INDEX]}]" >> /boot/config/plugins/drive_mount/drive_mount.cfg

    echo "DRIVE_NAME=\"${device_disk[$INDEX]}\"" >> /boot/config/plugins/drive_mount/drive_mount.cfg

    echo "DRIVE_MOUNT=\"${device_mount[$INDEX]}\"" >> /boot/config/plugins/drive_mount/drive_mount.cfg

    echo "DRIVE_MOUNTED=\"${device_mounted[$INDEX]}\"" >> /boot/config/plugins/drive_mount/drive_mount.cfg

    echo "DRIVE_ENABLED=\"${device_enabled[$INDEX]}\"" >> /boot/config/plugins/drive_mount/drive_mount.cfg

  done

}

 

cfg.parser () {

ini="$(<$1)"                # read the file

ini="${ini//[/\[}"          # escape [

ini="${ini//]/\]}"          # escape ]

IFS=$'\n' && ini=( ${ini} ) # convert to line-array

ini=( ${ini[*]//;*/} )      # remove comments with ;

ini=( ${ini[*]//#*/} )      # remove comments with #

ini=( ${ini[*]/\    =/=} )  # remove tabs before =

ini=( ${ini[*]/=\  /=} )  # remove tabs be =

ini=( ${ini[*]/\ =\ /=} )  # remove anything with a space around =

ini=( ${ini[*]/#\\[/\}$'\n'cfg.section.} ) # set section prefix

ini=( ${ini[*]/%\\]/ \(} )    # convert text2function (1)

ini=( ${ini[*]/=/=\( } )    # convert item to array

ini=( ${ini[*]/%/ \)} )    # close array parenthesis

ini=( ${ini[*]/%\\ \)/ \\} ) # the multiline trick

ini=( ${ini[*]/%\( \)/\(\) \{} ) # convert text2function (2)

ini=( ${ini[*]/%\} \)/\}} ) # remove extra parenthesis

ini[0]="" # remove first element

ini[${#ini[*]} + 1]='}'    # add the last brace

eval "$(echo "${ini[*]}")" # eval the resul

<========== line 34

 

 

  • 3 months later...

Looks like the host for the plg file is down. Looks interesting with the webgui..too bad it can't be maintained - especially with queeg out as well.

  • 4 months later...

 

I recommend using only one subdirectory in /mnt, like /mnt/Apps (on my server, i use /mnt/usenet).

 

to access that drive via network, you have to edit the smb-extra file in /boot/config

here is my file, as an example:

 

[usenet]
   path = /mnt/usenet
   read only = no
   guest ok = yes

max protocol = SMB2

 

when i have time to do it, this script will also allow easy sharing of mounted drives...

 

Gidday Benni

 

On recommendation of Influencer I changed from the SNAP plugin to your driver_mount plugin, as I want Sickbeard and SabNZdb on a stand-alone drive.

 

Can I recommend that if possibly, your able to finish this plugin with smb_conf support.  It wasn't till I got to page 2 of this thread that I found had to manually add lines to smb_conf to get the drive visible on my network.  In the mean-time, maybe post the above code into your OP for easy reference.

 

Apart from this one hitch, your plugin is perfect.  Starts before sickbeard and Sab so allows my data to persist.

 

Thanks again.

 

Rob

  • Author

yeah, i'll add the updates to this plugin to my todo list :)

 

(actually i'm no longer using it myself, since i changed the drive i used before to cache drive. but nevertheless, i'll update this plugin as soon as i've got time. I'm currently working on several other new plugins...)

Well, I gotta say it's a life saver.

 

Specially for those on Basic systems (ie: no cache drive).  And I'll be adding this to three other systems for friends I know who use usenet programs on their PC's.  Now can add extra download drive just for Sab & Sickbeard, and their PC's can get switch off at night.  Cheers.

 

Rob

I installed snap just a few days ago and it failed to install properly. So when I saw this program I was very excited. I couldn't get it work just the way I wanted (prob my fault) but I was able to successfully mount the ntfs drive to a folder. So I am very happy to use this plugin especially if you add some of the features you talked about (smb). Thanks for the hard work!

  • Author

just to let you know, there is a new version, which now handles old ide-drives, too.

also, drives with multiple partitions are supported now.

 

there is a new config line (smb share). this does not do anything yet. just added it for some tests (yes, share config is coming soon) and forgot to remove it, before uploaded. i'm just leaving it there for now.

 

note: if you update, you will have to reconfigure your mounts. the config file has a new format, sorry for that.

 

plans for (near) future:

finally get share config included (smb only for now)

new layout for config page (maybe using simple features, which would be a necessary requirement then)

save drive config, even if it has been removed

automaticly handle new disks (yes, snap does this (and lot else) already, but i've never been too happy with the way, snap works. that was the first reason for developing this plugin) (this feature is way off... so don't expect this anytime soon)

Can't wait to try it when I get home. Any more info on why some drives in the array show up as being enabled through this plugin. If I remember correctly I think it was drive (sdn) for me and a few other people. Thanks for the update.

  • Author

those drives should not be listed at all...

BUT: there was a bug (a typo), which caused trouble as soon as you got to sdn... it's fixed now

Hi Benni

 

Great job on this Plugin.  Fantastic.

 

One small glitch, I can't seem to select "No" and hit apply.  They won't unmount.  Actually, seems to take a very long time to disable.

# drive_mount configuration
[467825e9-015f-438b-ace9-424cc33ab312]
DRIVE_ID="WDC_WD1600AAJS-00PSA0_WD-WMAP9H476754"
DRIVE_NAME="sdb1"
DRIVE_MOUNT=""
DRIVE_MOUNTED="disable"
DRIVE_ENABLED="disable"
SMB_SHARE=""
[69f916b7-2917-43c3-9a36-95b20efc851c]
DRIVE_ID="WDC_WD400JB-00FMA0_WD-WCAJC1023700"
DRIVE_NAME="hda2"
DRIVE_MOUNT="/mnt/backup"
DRIVE_MOUNTED="disable"
DRIVE_ENABLED="enable"
SMB_SHARE=""
[6f0bbd8e-88ae-473f-96b2-c9bd89a24988]
DRIVE_ID="ST380011A_5JVJMG7J"
DRIVE_NAME="hdb1"
DRIVE_MOUNT="/mnt/apps"
DRIVE_MOUNTED="disable"
DRIVE_ENABLED="enable"
SMB_SHARE=""
[9484-B610]
DRIVE_ID="WDC_WD400JB-00FMA0_WD-WCAJC1023700"
DRIVE_NAME="hda1"
DRIVE_MOUNT="/boot"
DRIVE_MOUNTED="enable"
DRIVE_ENABLED="enable"
SMB_SHARE=""

 

most drives are gone from /mnt but still show as "Yes" in enable drive.

 

But, this isn't really an issue for me, as once I have it all set up how I want, the drive will be running all the time.

Paste121020120.jpg.1e9e32febf75f470dcb661c4af2dfcf8.jpg

Benni,

I've made some modifications to this plugin for my own use that I'd love to fold back in to your code base if you're interested....

 

Whiteatom

  • Author

One small glitch, I can't seem to select "No" and hit apply.  They won't unmount.  Actually, seems to take a very long time to disable.

 

make sure, that nothing is still accessing those drives.

 

i've added a better unmount to my todo-list.

 

Benni,

I've made some modifications to this plugin for my own use that I'd love to fold back in to your code base if you're interested....

 

Whiteatom

 

sure, i'll gladly take a look at it.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.