dlandon

This indicates nothing is set to be shared if in fact you have some UD devices mounted: Apr 30 06:33:53 Weechflix unassigned.devices: Updating share settings... Apr 30 06:33:53 Weechflix unassigned.devices: Share settings updated. In Settings->UD Settings, you'll need to have SMB set to something besides 'Disabled'. SMB needs to be enabled in Settings->SMB, and the share switch needs to be on for each UD device you want to share. Test the configuration by unmounting a remote share, then mount the share and look at the log to see if UD enabled the SMB share. If something is not properly set up for sharing, you'll see a log message indicating what is not set.

Possibly, but you should check your cable.

For anyone having the continuous Unraid wave, I have found an issue with special characters in iso file names. I am working on a fix, but until I release the next update of UD, you can stop the constant Unraid wave by deleting the iso config file and then click on the double arrows in the upper right of the UD page. The file is '/flash/config/plugins/unassigned.devices/iso_mount.cfg. You can recreate the iso shares when the next update of UD is relesed and you should not see the continuous Unraid wave.

Your network is dropping out: Apr 23 06:26:13 Weechflix kernel: bond0: (slave eth0): link status definitely down, disabling slave Apr 23 06:26:13 Weechflix kernel: device eth0 left promiscuous mode Apr 23 06:26:13 Weechflix kernel: bond0: now running without any active interface! Apr 23 06:26:13 Weechflix kernel: br0: port 1(bond0) entered disabled state Apr 23 06:26:31 Weechflix kernel: tg3 0000:07:00.0 eth0: Link is up at 1000 Mbps, full duplex Apr 23 06:26:31 Weechflix kernel: tg3 0000:07:00.0 eth0: Flow control is on for TX and on for RX Apr 23 06:26:31 Weechflix kernel: bond0: (slave eth0): link status definitely up, 1000 Mbps full duplex Apr 23 06:26:31 Weechflix kernel: bond0: (slave eth0): making interface the new active one Apr 23 06:26:31 Weechflix kernel: device eth0 entered promiscuous mode Apr 23 06:26:31 Weechflix kernel: bond0: active interface up! Apr 23 06:26:31 Weechflix kernel: br0: port 1(bond0) entered blocking state Apr 23 06:26:31 Weechflix kernel: br0: port 1(bond0) entered forwarding state Apr 23 06:26:34 Weechflix kernel: tg3 0000:07:00.0 eth0: Link is down Apr 23 06:26:34 Weechflix kernel: bond0: (slave eth0): link status definitely down, disabling slave Apr 23 06:26:34 Weechflix kernel: device eth0 left promiscuous mode Apr 23 06:26:34 Weechflix kernel: bond0: now running without any active interface! Apr 23 06:26:34 Weechflix kernel: br0: port 1(bond0) entered disabled state Apr 23 06:26:37 Weechflix kernel: tg3 0000:07:00.0 eth0: Link is up at 1000 Mbps, full duplex Apr 23 06:26:37 Weechflix kernel: tg3 0000:07:00.0 eth0: Flow control is on for TX and on for RX Apr 23 06:26:37 Weechflix kernel: bond0: (slave eth0): link status definitely up, 1000 Mbps full duplex Apr 23 06:26:37 Weechflix kernel: bond0: (slave eth0): making interface the new active one Apr 23 06:26:37 Weechflix kernel: device eth0 entered promiscuous mode Apr 23 06:26:37 Weechflix kernel: bond0: active interface up! And then CIFS is failing: Apr 23 08:42:19 Weechflix kernel: CIFS: __readahead_batch() returned 12/16 Apr 23 08:42:19 Weechflix kernel: CIFS: __readahead_batch() returned 2/16 Apr 23 08:42:20 Weechflix kernel: CIFS: __readahead_batch() returned 12/16 Apr 23 08:42:20 Weechflix kernel: CIFS: __readahead_batch() returned 1/16 Apr 23 08:42:20 Weechflix kernel: CIFS: __readahead_batch() returned 7/16 Apr 23 08:42:20 Weechflix kernel: CIFS: __readahead_batch() returned 3/16 Apr 23 08:42:20 Weechflix kernel: CIFS: __readahead_batch() returned 11/16 Apr 23 08:42:20 Weechflix kernel: CIFS: __readahead_batch() returned 8/16 ### [PREVIOUS LINE REPEATED 1 TIMES] ### Apr 23 08:42:21 Weechflix kernel: CIFS: __readahead_batch() returned 3/16 Apr 23 08:42:21 Weechflix kernel: CIFS: __readahead_batch() returned 6/16 Apr 23 08:42:21 Weechflix kernel: CIFS: __readahead_batch() returned 2/16 Apr 23 08:42:21 Weechflix kernel: CIFS: __readahead_batch() returned 10/16 Apr 23 08:42:21 Weechflix kernel: CIFS: __readahead_batch() returned 9/16 Apr 23 08:42:21 Weechflix kernel: CIFS: __readahead_batch() returned 3/16 Apr 23 08:42:21 Weechflix kernel: CIFS: __readahead_batch() returned 11/16 Apr 23 08:42:21 Weechflix kernel: CIFS: __readahead_batch() returned 4/16 Apr 23 08:42:21 Weechflix kernel: CIFS: __readahead_batch() returned 2/16 Apr 23 08:42:22 Weechflix kernel: CIFS: __readahead_batch() returned 7/16 ### [PREVIOUS LINE REPEATED 1 TIMES] ### Check your network switch and/or router.

Post diagnostics.

Send me the following files from the /flash/config/plugins/unassigned.devices/ folder in a PM. Don't post them on the forum. unassigned.devices.cfg samba_mount.cfg iso_mount.cfg

Go to Settings->Unassigned Devices and set the "Debug Log Level" to "Refresh and Update", then go to the UD page and let it sit there for 10 seconds or so. Then post a new diagnostics. Be sure to go back to the Settings->Unassigned Devices and set the "Debug Log Level" back to "None" as it will log too much if left on.

The Unraid wave is constant. This has been reported in the UD forum. Please respond there and not in this duplicate post.

Post diagnostics.

On both servers it appears that the remote shares auto mounted when your array arrays were started. Are you saying that the shareing is not enabled (SMB and NFS)? Apr 25 22:25:51 U-RJO21 unassigned.devices: Successfully mounted 'U-NAS23:/mnt/user/data' on '/mnt/remotes/U-NAS23_data'. Apr 25 22:25:51 U-RJO21 unassigned.devices: Device 'U-NAS23:/mnt/user/data' is not set to be shared. The 'Share' switch is not on. Also turn off the UD debugging. It is not useful here and is writing too much to the log.

When UD hangs, it is generally from a php error or a Java Script error. I'm trying to determine if there are any php errors showing up in the php log on 6.12. The php log is not part of the syslog. It is a separate log in 6.12 on the Tools page. If there aren't any php errors, then we need to look for Java script errors. If that doesn't show anything, we'll have to look at the UD loop and see if it is stuck somewhere.

You can't.

It is part of 6.12.

I don't see anything in the log. Go to Tools->PHP Settings and set "Error Reporting Level" to "All Categories". Then go to the UD page and stay there for about 5 seconds, then go back to the PHP Settings and look at the log and post any warnings or errors shown.

Start by posting some diagnostics.

Post diagnostics.

The recycle bin is set up properly. Keep in mind that a file with zero length will not be put into the recycle bin when it is deleted.

Post the output of this command: testparm -s

You have a networking problem. Try rebooting the servers.

No, Tips and Tweaks doesn't currently support a command line option to control this.

Be sure you use '/mnt/disks/One_Touch/' and not'/mnt/disks'.

It's based on a random seed the first time you set up a password and used from then on to encrypt and decrypt passwords.

The password is encrypted and stored on the flash device. EDIT: Also, don't share your flash public.

It'll be in the next release of UD.

Don't think so. It looks like you are using a drive bay that is assigning the same serial number to every disk. UD can't handle that. Each drive needs to have a unique serial number.