dlandon

I've released a new version of UD. Most noticeable are the changes made to help with the confusion over changing the 'SMB Security' setting from 'No' sharing devices public, to 'No' now being no sharing. This change was made for security reasons and the user needs to specify the type of SMB security they want to use on all UD devices. The default is 'No', meaning no SMB device sharing. The changes are: When UD is updated, it will re-apply security changes to be sure they follow any changes in UD regarding security changes. This means when a user updates now, the 'No' default setting will not share any devices. This will make the change obvious when UD updates and not months later when someone reboots or remounts the device. The device tool tip will show 'Share: Not Available" when neither SMB nor NFS sharing is enabled. The 'Edit Device Settings' page will now display a message under the switches that the UD share settings have to be applied to enable device sharing. Fixed a corner case when a zfs device was mounted with a Pool Name the same as another device's mount point, not allowing a 'Detach'.

You need to set the SMB Security to something other than "No". "No" means don't share any UD devices.

All the empty recycle bin does is delete files in the .Recycle.Bin folder. Is handbrake accessing a file that ended up in the Recyle Bin? Install the open files plugin and see if handbrake is accessing any files moved to the Recycle Bin before you empty it.

I have no idea. Something unique about your system.

Yes. @ljm42 please have a look here.

The only time samba is restarted is when the recycle bin is stopped and started. I'm probably going to change that.

Update UD and see if it works now.

That shouldn't happen, even with a remote share issue.

Thank you. We are on it.

When you can, do a "Crtl-U" and scroll down to line 2510 and show what is there in a screen shot.

Remove CA and UD will probably start to work.

I'm pretty sure it is the JQuery error. I'm working on it.

@Squid I need some help here. I believe this error is in the 'checkPlugin()' script. Can you have a look and advise?

The error is all the way at the top. "uncaught error". It has to do with the checkPlugin() procedure. I'll look into it.

Go to the Settings->Display Settings and set 'Page View' to 'Tabbed' and see if it changes.

This is built into Unraid and @bonienl will have to have a look at it.

That's the disk locación plugin. Remove it please.

What browser are you using?

If you aren't seeing anything in the logs, then something is keeping the UD page from running at all. Did you try the 'Ctrl', 'Shift', 'j' to see if there are any JQuery errors? My suggestion at this point is to reboot in safe mode, then install CA and UD and see if UD will display. If it does, then you have a plugin interferring with UD. Add plugins back one at a time until UD stops working.

It looks like your disk dropped off-line and then came back with a different device designation: Apr 9 13:50:33 DJW-UNRAID kernel: I/O error, dev sdb, sector 7814036768 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Apr 9 13:50:33 DJW-UNRAID kernel: sd 5:0:12:0: [sdb] tag#686 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Apr 9 13:50:33 DJW-UNRAID kernel: sd 5:0:12:0: [sdb] tag#686 Sense Key : 0x2 [current] Apr 9 13:50:33 DJW-UNRAID kernel: sd 5:0:12:0: [sdb] tag#686 ASC=0x4 ASCQ=0x0 Apr 9 13:50:33 DJW-UNRAID kernel: sd 5:0:12:0: [sdb] tag#686 CDB: opcode=0x88 88 00 00 00 00 01 d1 c0 bd 20 00 00 00 08 00 00 Apr 9 13:50:33 DJW-UNRAID kernel: I/O error, dev sdb, sector 7814036768 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Apr 9 13:50:33 DJW-UNRAID kernel: Buffer I/O error on dev sdb, logical block 976754596, async page read Apr 9 13:50:38 DJW-UNRAID kernel: XFS: metadata IO error: 5 callbacks suppressed Apr 9 13:50:38 DJW-UNRAID kernel: XFS (sdh1): metadata I/O error in "xfs_da_read_buf+0x9a/0xff [xfs]" at daddr 0xebc5fc18 len 8 error 5 Apr 9 13:50:38 DJW-UNRAID kernel: XFS (sdh1): metadata I/O error in "xfs_da_read_buf+0x9a/0xff [xfs]" at daddr 0x15e8c56e8 len 8 error 5 Apr 9 13:50:38 DJW-UNRAID kernel: XFS (sdh1): metadata I/O error in "xfs_da_read_buf+0x9a/0xff [xfs]" at daddr 0x15e8c56f0 len 8 error 5 Apr 9 13:50:38 DJW-UNRAID kernel: XFS (sdh1): metadata I/O error in "xfs_da_read_buf+0x9a/0xff [xfs]" at daddr 0x15e8c56f8 len 8 error 5 Apr 9 13:50:38 DJW-UNRAID kernel: XFS (sdh1): metadata I/O error in "xfs_da_read_buf+0x9a/0xff [xfs]" at daddr 0x15e8c5700 len 8 error 5 Apr 9 13:50:38 DJW-UNRAID kernel: XFS (sdh1): metadata I/O error in "xfs_da_read_buf+0x9a/0xff [xfs]" at daddr 0x15e8c5708 len 8 error 5 Apr 9 13:50:38 DJW-UNRAID kernel: XFS (sdh1): metadata I/O error in "xfs_da_read_buf+0x9a/0xff [xfs]" at daddr 0x15e8c5710 len 8 error 5 Apr 9 13:50:38 DJW-UNRAID kernel: XFS (sdh1): metadata I/O error in "xfs_da_read_buf+0x9a/0xff [xfs]" at daddr 0x15e8c5718 len 8 error 5 Apr 9 13:50:38 DJW-UNRAID kernel: XFS (sdh1): metadata I/O error in "xfs_da_read_buf+0x9a/0xff [xfs]" at daddr 0x15e8c5720 len 8 error 5 Apr 9 13:50:38 DJW-UNRAID kernel: XFS (sdh1): metadata I/O error in "xfs_da_read_buf+0x9a/0xff [xfs]" at daddr 0x15e8c5728 len 8 error 5 The disk is mounted as sdh1 and not sdb1: /dev/sdh1 3.7T 2.9T 785G 79% /mnt/disks/WD-WCC4E0978614 /dev/sdg1 3.7T 2.7T 972G 74% /mnt/disks/WD-WMC4E0027693 A reboot is needed to clear this up.

Post diagnostics. Not mounted or not mounted by UD? Does the drive in question show a "Dev X" designtation or a "sdX" designtation on the UD page? The disk can probably be removed, but I'd be careful because you might have something with the same mount point already mounted at /mnt/disks/. Your safest bet is a reboot. Post diagnostics before doing anything else.

I don't see the debug messages. Did you set the log level to 'Refresh and Update"? When you are on the UD page, press 'Ctrl', S'hift', and 'J' and see if there are any JQuery errors.

Update UD and then set the new debug in UD settings. Set "Debug Log Level" to "Refresh and Update". Then go to the UD page and let it sit for a minute or so. Then post new diagnostics here. Set the log level back to "None". The logging can get very chatty and fill your log,

The latest version will install on Unraid 6.9 and higher.