AndroidCat
-
Posts
124 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by AndroidCat
-
-
What about...Extent should be file-based and user decides where that file is created. In most cases on SSD cache.
Sent from my SM-G955U1 using Tapatalk -
+100, but nobody seems to care anyway.
Sent from my SM-G955U1 using Tapatalk -
Anybody wanting to use this needs to update kernel-headers version from "19"to "21". Just edit the plg file to do so.
Also prior to installation make sure plg file name is openVMTools_auto.plg
Otherwise the plugin will not be loaded upon next reboot and VMTools will not start.
-
+1
Sent from my SM-G955U1 using Tapatalk -
+1
-
Why iSCSI?
-because every comparable NAS solution already has it (FreeNAS, Synology, Qnap, OpenFiler...),
-because it is easy to add,
-because it would help some of us, already using unRAID for everything else, dump other solutions existing for the sole purpose of serving iSCSI targets (think mostly for ESXi home labs),
-a few other edge cases where access to block-level devices is required or preferred over smb or NFS.
On the other note I don't get why some people uninterested in the topic try to discourage Tom from looking at it. I don't have any use for e.g. graphics card pass-through to VM, but I don't advocate to stop wasting development time on it.
-
2
-
-
Lol, that is probably 5th thread requesting iSCSI. It is really simple to implement on Linux. Please Tom give it a thought.
-
One good case would be for home labs, and for IT professionals using LT NAS in conjunction with other system OS's like Microsoft, Citrix, Redhat, and VMware. ISCSI is a cross platform industry standard for connecting storage and it would be nice to have.
iSCSI is a block-level protocol. How should an iSCSI LUN be mapped to unRAID storage? The only use case I can see for this is a SAN.
Probably like Windows Server and Linux do by creating virtual disk image on existing filesystem and using it for iSCSI target. Even if somebody wants to create plugin they need support in kernel.
-
Mine shows Sao Miguel too, specifically the town of Ponta Delgada, presumably some default. I don't know how it's meant to work out the true location anyway.
There's a lot of information displayed and it's all superficially very pretty but the graphs tend to use subtle shades of a few colours each so are difficult to interpret. Also, it doesn't seem very customisable. I was hoping to be able to monitor my DSL router, which has SNMP enabled, in order to keep an eye on SNR margin and sync speed but so far have only been able to monitor traffic.
SNMP Host location is taken from SNMP definitions of that device. In case of unraid it should be possible to edit SNMP config file and specify location. In case of some home devices, especially managed switches you can specify location in their GUIs.
You can also specify the above in Observium itself (edit host) and don't bother with finding the setting in a given host.
-
Version 2016.02.01 is available. I fixed the situation where the unraid boot flash drive would show up as an unassigned device when another flash drive is installed with an 'UNRAID' label. The inserted flash drive will show in unassigned devices, but won't mount because it has the 'UNRAID' label. Any device with the label of 'UNRAID' will not mount or unmount. The boot flash device will not show up in the unassigned devices.
Because of the changes, please confirm that all your unassigned devices show properly, and the parity, array disks, cache disk(s), and boot flash drive don't show up.
All good here on 2 unraids. Local drives and remote smb shares show up OK and none of the unraid devices is reported by the plugin.
Thanks for your work!
-
dlandon-> happy to report that NFS export works. Thanks again.
-
I will tomorrow... But how is it supposed to work?
-
Thanks dlandon for taking care of this plugin. Since you keep on digging in the code can you tell me how NFS export is supposed to work? I tried many times and didn't see any way to configure NFS export from gui (NFS export enabled in settings).
I will look into this, but I don't use NFS shares so I don't know much about it. Do you have NFS shares enabled under Network Settings?
Yes
-
Thanks dlandon for taking care of this plugin. Since you keep on digging in the code can you tell me how NFS export is supposed to work? I tried many times and didn't see any way to configure NFS export from gui (NFS export enabled in settings).
-
You need a DNS somewhere in your network to resolve "tower" to corresponding IP address.
There is usually a simple DNS in a router provided by ISP.
From my experience with Docker it is not enough to use /etc/hosts on a machine hosting dockers (unraid in your case). There are some tricks to pass that /etc/hosts to docker, but easiest way is to use your own DNS either running on a router or on some server.
-
You need DNS to translate tower to corresponding IP address. Usually there is a simple DNS in a router you've got from your ISP.
-
Did anybody figure out how "NFS Export" is supposed to work?
When I enable this option in "Settings" I see no way from the GUI to export a device under NFS.
Also a bug I suppose:
I am unable to edit remote smb share mountpoint name. Even though I edit the mount point name from GUI it always reverts to system-assigned "smb_<server>_<share>" when I click "mount"
The mountpoint name however gets changed in remote_config.cfg as mountpoint="/mnt/disks/<desired name>", but that is ignored even after reboot. Device keeps mounting under system-assigned name despite specifying custom"mountpoint".
So really two bugs: no ability to edit remote share name mountpoint from gui and ignoring custom mountpoint.
Unraid 6.1.6
plugin v 2015.11.18
Thanks.
-
Updating to v.22b wiped all my samba shares. It also set one local disk sharing to OFF.
Otherwise all good
-
You Sir are awesome.
-
Thank you Sir.
-
You have to provide hostname which can be resolved to IP address. Resolution can happen e.g in your home router.
In other words Observium only accepts hostnames.
-
Great work! Very useful application.
Do you know why Tonido docker ignores (or maybe any docker in general) read-only volume mapping? In my case /unRAID <-> /mnt/disks/ is mapped as :ro but I can still delete/write files there from within Tonido.
I checked how the docker gets invoked and it indeed uses :ro following what had been configured in "Volume Mappings" Does it somehow ignores read-only statement because /mnt/disks contains samba mountpoints?
ls -al /mnt/disks total 8 drwxrwxrwx 6 root root 120 Jul 6 19:12 ./ drwxr-xr-x 14 root root 280 Jul 6 19:12 ../ drwxrwxrwx 3 root root 4096 Dec 31 1969 BOOTUNRAID/ drwxrwxrwx 2 root root 0 Jul 6 03:40 unraid_unraid/ drwxrwxrwx 2 root root 0 Jul 6 03:40 unraid_video/ drwxrwxrwx 1 root root 4096 Jun 16 14:28 wd2t/
docker exec -it Tonido bash root@423b4d2af636:/# ls -al /unRAID/ total 8 drwxrwxrwx 6 root root 120 Jul 6 19:12 . drwxrwxrwx 1 root root 198 Jul 6 20:08 .. drwxrwxrwx 3 root root 4096 Dec 31 1969 BOOTUNRAID drwxrwxrwx 2 root root 0 Jul 6 03:40 unraid_unraid drwxrwxrwx 2 root root 0 Jul 6 03:40 unraid_video drwxrwxrwx 1 root root 4096 Jun 16 14:28 wd2t
/usr/bin/docker run -d --name="Tonido" --net="bridge" -e TZ="America/Chicago" -p 10001:10001/tcp -v "/mnt/user/appdata/tonido":"/config":rw -v "/mnt/disks/":"/unRAID":ro captinsano/tonido
-
I second RobJ, some kind of two-stage approach would be beneficial. Probably 1st threshold to try to spin down and 2nd to unconditionally shut down.
-
Latest update (2015.06.15a) broke my export of USB drive to NFS.
It is independent if I check or not 'run script in background'.
And manual unmount followed by mount properly exports NFS i.e. script is executed.
Tue Jun 16 0:10:34 CDT 2015: Drive found with the following attributes: serial='WD_Elements_10B8_575841314131353253354850-0:0', serial_short='575841314131353253354850', device='/dev/sdk1', part='1', label='Elements', fstype='ntfs', target='', size='2000364240896', used='0', avail='2000364240896', mountpoint='/mnt/disks/wd2t', owner='user', automount='1', shared='1', command='/boot/config/plugins/unassigned.devices/wd2t.sh', command_bg='false' Tue Jun 16 0:10:34 CDT 2015: Adding disk ... Tue Jun 16 0:10:34 CDT 2015: Mounting drive with command: mount -t ntfs -o auto,async,nodev,nosuid,umask=000 '/dev/sdk1' '/mnt/disks/wd2t' Tue Jun 16 0:10:43 CDT 2015: Successfully mounted '/dev/sdk1' on '/mnt/disks/wd2t' Tue Jun 16 0:10:43 CDT 2015: Defining share 'wd2t' on file '/etc/samba/unassigned-shares/wd2t.conf' . Tue Jun 16 0:10:43 CDT 2015: Adding share wd2t to /boot/config/smb-extra.conf Tue Jun 16 0:10:43 CDT 2015: Reloading Samba configuration. Tue Jun 16 0:10:43 CDT 2015: Directory '/mnt/disks/wd2t' shared successfully. Tue Jun 16 0:10:43 CDT 2015: Running command '/boot/config/plugins/unassigned.devices/wd2t.sh' with action 'ADD'. Tue Jun 16 0:10:43 CDT 2015: Disk Elements shared successfully.
cat /tmp/WD_Elements_10B8_575841314131353253354850-0\:0.log exporting *:/mnt/disks/wd2t
In case you can't figure it out can I revert to the previous code?
overlay fs booting method
in Virtualizing Unraid
Posted
Has anybody tried this with recent versions? Although the note is a bit old I don't see why it shouldn't work with 6.9.
I will try it later, but has anybody been using it?
https://github.com/thohell/unRAID-bzoverlay
I've already been using a vmdk bootdisk for unraid under ESXi for years (Unraid boots off vmdk, but config files are still on USB).
The linked method has additional advantages:
-no writes to USB drive
-no need to copy boot files from USB to vmdk during upgrade.