devros

This disk is connected directly to a SATA port on the motherboard. The motherboard is a current generation X11 Supermicro

Here is a strange one. I added a 4T drive to my setup, used UD to format it as XFS, gave it a custom mount point, mounted it, and turned on auto mount. After I started using it I noticed that the OS was only seeing it as a 2T drive. I checked the partition table and there was just one partition and it was 4T. UD was showing it was 2T in the GUI. After I rebooted, it did not auto mount and the mount button was greyed out just for that drive(destructive mode is on) I tried manually mounting it: mount -t xfs /dev/sdd1 /mnt/disks/tmp/ mount: /mnt/disks/tmp: wrong fs type, bad option, bad superblock on /dev/sdd1, missing codepage or helper program, or other error. I removed the lines about it in the .cfg file and rebooted, same issue. Tried running an xfs_repair, but no superblock was found. Any ideas would be much appreciated.

Can confirm it's working fine under 6.6.7

update for 6.7.0 soon? Doesn't look like there has been a ZOL update since 0.7.12 in Nov

with ZFS you can create ZVOLs, which present themselves as a normal block device /dev/zd0 for example. You can partition, create other filesystems on it, just like you would a hard drive. I created a test one and had UD rescan to see if it would pick it up, which it did not. Since its just a regular block device, would it be possible to have UD recognize it and treat it like a hard drive?

Asked this question in more detail here, but figured this could be something UD might be able to help with: I noticed that UD has some hooks/scripts in it somewhere that can keep UD shared devices in /etc/exports even if files services get restarted(the file gets blown away and rebuilt) so just a user script at array startup that echos those lines in and restarts nfsd won't work. I have a ZFS file system I would like to share and was wondering if I could somehow use UD to share it over NFS, even though it is not mounted by UD itself. Thanks, -dev

I currently have a zpool of a few SSDs with a few ZFS volumes on there. I need to export one of the volumes over NFS. The problem is that, unlike the SMB settings where you can add extra config, there is no such option for NFS. Unassigned devices won't recognize ZFS volumes, so I can't use that. If I use the zfs set sharenfs=on command, it will work then, but will not stay shared after a reboot or if any changes are made to any share setting. My solution was to write a script that runs when the array is 1st started that echos the lines of config I need into /etc/exports and then restarts nfsd. The problem is that whenever some config changes are made, it results in /etc/exports getting blown away, regenerated and a restart of nfsd. Any thoughts on how I could get the two extra lines I need added every time /etc/exports get regenerated? TIA, -dev

Just switch to lsiodev/ombi-preview It's been working great for me, but you do have to set it up fresh. V2 was crashing all the time on me. V3 has been really great for the past 2 months I have been using it

I've been using lsiodev/ombi-preview. Seems to be working great so far except is won't do newsletters yet. For that I've switched over to https://github.com/ninthwalker/NowShowing which has been working great so far and is more customizable. You do need to start from scratch with your configs though. Ombi v3 will not upgrade a v2 config.

That worked great, thanks. For some reason, even with the share unmounted, the. name was still showing up as if it was a link.

I'm using the plugin now to mount a NFS share hosted on another linux box in my house. Just wondering if there is any way to change the local path that share gets mounted at to something other than /mnt/disks/<IP of server>_<name of share>. It would be nicer if I could just have it mounted at /mnt/disks/plexdl. This feature exists for mounted local drives. TIA for any help, and I apologize if I missed something really obvious here

Would it be possible to get the Ombi docker updated so there is an option to run the v3 beta?

What would I need to change to have it pull down/run the v2 branch? thanks, devros

Will you have an update for 6.3.4 soon? I had just upgraded when I stumbled onto this plugin.