AndroidCat

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.

Could you please add 'smbclient' to the docker? It is required to be able to mount SMB shares to Pydio via its plugin. Thanks.

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

How does one make sure timing is correct i.e. unassigned devices is not killed during shutdown, thus unmounting my vmdk during or prior to coping by User Scripts?

Let me try again :-) Is there any way I can insert custom *.sh script which gets launched when Unraid upgrade is finished (as a last step in upgrade routine). Thanks.

After upgrade process is completed (upgrade button pressed and all files got downloaded and copied to flash) I'd like to execute simple command, like cp /boot/xyz /disks/vmdk/ prior to reboot. I have vmdk mounted by unassigned devices, but that script could as well mount it as a first step. Sent from my SM-G955U1 using Tapatalk

@limetech Would you consider adding a hook for a custom script run after Unraid upgrade? I've been running under ESXi for ages and each time I have to manually copy bz* files and such to my boot vmdk. If it's easy to do it on your side...why not. Maybe it could have other uses as well. Thank you. 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.

Great, thanks. Short explanation why mover logging should be disabled? Sent from my SM-G955U1 using Tapatalk

In my case turning on Direct SMB (writing name from memory...) helped as this enabled SMB3. Run "programs and features" and enable this option. Sent from my SM-G955U1 using Tapatalk

+1 Sent from my SM-G955U1 using Tapatalk

Yep, looks like different issue. Sent from my SM-G955U1 using Tapatalk

I had to kill it from cli and start over. Luckily it saves progress periodically and resumes where it left off. Sent from my SM-G955U1 using Tapatalk

Did you use preclear plugin? It tends to die i.e. stops progressing and cpu and memory utilization for preclear script skyrocket to 100%. Sent from my SM-G955U1 using Tapatalk

Pretty bad looking here

+1

Great work on 6.4. No problems upgrading and everything works right away. I'm not sure it this had been addressed already, but virtually all new visual themes put too much spacing between lines of text. It is very evident on 'Main' page, where array disks take a lot of vertical space, because each disk is separated by a big gap. Any way to change it or create compact theme? thanks bonienl...

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.

Lol, that is probably 5th thread requesting iSCSI. It is really simple to implement on Linux. Please Tom give it a thought.

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.

As a matter of fact I did install the swap plugin a few days ago..seems to be working well. Thanks for that suggestion. Hopefully there is some hope it could be resolved more elegantly.

I'd like to be able to limit total memory allocated for all Dockers running. For instance system has 6GB of RAM allocated to unRAID and I want to set a hard limit of max 4GB to be utilized by Dockers, leaving 2GB (in worst case scenario) for NAS subsystem (emhttp, SAMBA, etc). That would hopefully prevent Out of Memory occurrences killing important processes when suddenly some Docker decides to use tons of RAM. That could,for example, be implemented as a global Docker setting in respective GUI. I know this could be solved by manually adding -m parameter to each Docker, but what about simple solution like this: For EACH DOCKER-> IF (-m not specified) append -m <global setting> ELSE use existing -m <value> entered by user EDIT: LOL, I realized the above would not work properly and it doesn't achieve what I wanted i.e. it would not limit TOTAL memory usage. Is there any way to do it at all (cgroups)?

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.

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!