Jump to content

dlandon

Community Developer
  • Posts

    10,395
  • Joined

  • Last visited

  • Days Won

    20

Everything posted by dlandon

  1. You do not have the device share switch set: Feb 20 14:06:01 Server2 unassigned.devices: Mount cmd: /sbin/mount -t 'xfs' -o rw,noatime,nodiratime '/dev/sdd1' '/mnt/disks/S5SSNF0RA00473W' Feb 20 14:06:01 Server2 kernel: XFS (sdd1): Mounting V5 Filesystem Feb 20 14:06:01 Server2 kernel: XFS (sdd1): Ending clean mount Feb 20 14:06:01 Server2 kernel: xfs filesystem being mounted at /mnt/disks/S5SSNF0RA00473W supports timestamps until 2038 (0x7fffffff) Feb 20 14:06:01 Server2 unassigned.devices: Successfully mounted 'sdd1' on '/mnt/disks/S5SSNF0RA00473W'. Feb 20 14:06:01 Server2 unassigned.devices: Device '/dev/sdd1' is not set to be shared. Feb 20 14:06:02 Server2 unassigned.devices: Mounting partition 'sdc1' at mountpoint '/mnt/disks/transfer'... Feb 20 14:06:02 Server2 unassigned.devices: Mount cmd: /sbin/mount -t 'btrfs' -o rw,noatime,nodiratime,space_cache=v2 '/dev/sdc1' '/mnt/disks/transfer' Feb 20 14:06:02 Server2 kernel: BTRFS info (device sdc1): using free space tree Feb 20 14:06:02 Server2 kernel: BTRFS info (device sdc1): has skinny extents Feb 20 14:06:02 Server2 kernel: BTRFS info (device sdc1): enabling ssd optimizations Feb 20 14:06:02 Server2 unassigned.devices: Successfully mounted 'sdc1' on '/mnt/disks/transfer'. Feb 20 14:06:02 Server2 unassigned.devices: Device '/dev/sdc1' is not set to be shared. If it is set, turn it off and then back on.
  2. It looks like your UD Settings are not correct. Go to UD Settings and re-apply the SMB Security settings: Feb 20 07:49:06 MediaTower unassigned.devices: Mount cmd: /sbin/mount -t 'xfs' -o rw,noatime,nodiratime '/dev/sdd1' '/mnt/disks/Download' Feb 20 07:49:06 MediaTower kernel: xfs filesystem being mounted at /mnt/disks/Download supports timestamps until 2038 (0x7fffffff) Feb 20 07:49:06 MediaTower unassigned.devices: Successfully mounted 'sdd1' on '/mnt/disks/Download'. Feb 20 07:49:06 MediaTower unassigned.devices: Unassigned Devices are not set to be shared.
  3. It looks like the presentation of the device serial numbers are confusing Unraid and/or UD. If you look at those serial numbers, the endings are all the same.
  4. Update to the latest version of UD and then mount a shared disk and post diagnostics. I've added some logging to try to figure this one out.
  5. Hot plug events and device designations are changing after UD Preclear is installed, probably because a hot plug event is initiated by UD Preclear. Feb 20 03:46:15 Tower root: plugin: unassigned.devices.preclear.plg installed Feb 20 03:46:39 Tower emhttpd: error: hotplug_devices, 1730: No such file or directory (2): Error: tagged device HUH72808CLAR8000_VJGR8M7X_35000cca261288218 was (sdaf) is now (sdj) Feb 20 03:46:39 Tower emhttpd: error: hotplug_devices, 1730: No such file or directory (2): Error: tagged device HUH72808CLAR8000_VJHA50UX_35000cca2614ad854 was (sdd) is now (sdk) Feb 20 03:46:39 Tower emhttpd: device /dev/sdy problem getting id Feb 20 03:46:39 Tower emhttpd: error: hotplug_devices, 1730: No such file or directory (2): Error: tagged device HUH728080AL520_X_VLHZMZWY_35000cca2607016cc was (sdy) is now (sdh) Feb 20 03:46:39 Tower emhttpd: device /dev/sdaf problem getting id Feb 20 03:46:39 Tower emhttpd: device /dev/sdd problem getting id Feb 20 03:46:39 Tower emhttpd: device /dev/sdt problem getting id Feb 20 03:46:39 Tower emhttpd: device /dev/sdz problem getting id Feb 20 03:46:39 Tower emhttpd: error: hotplug_devices, 1730: No such file or directory (2): Error: tagged device HUH728080AL4200_2EG9U3ZR_35000cca23b11d6ac was (sdp) is now (sde) Feb 20 03:46:39 Tower emhttpd: device /dev/sdu problem getting id Feb 20 03:46:39 Tower emhttpd: error: hotplug_devices, 1730: No such file or directory (2): Error: tagged device HUH728080AL520_X_VLJ03AAY_35000cca26070ee14 was (sdt) is now (sdb) Feb 20 03:46:39 Tower emhttpd: device /dev/sdf problem getting id Feb 20 03:46:39 Tower emhttpd: error: hotplug_devices, 1730: No such file or directory (2): Error: tagged device HUH728080AL4200_2EGAXXRR_35000cca23b13e130 was (sdn) is now (sdc) Feb 20 03:46:39 Tower emhttpd: device /dev/sdn problem getting id Feb 20 03:46:39 Tower emhttpd: error: hotplug_devices, 1730: No such file or directory (2): Error: tagged device HUH72808CLAR8000_VJH9X6DX_35000cca2614a62e8 was (sdz) is now (sdi) Feb 20 03:46:39 Tower emhttpd: device /dev/sdp problem getting id Feb 20 03:46:39 Tower emhttpd: read SMART /dev/sdh Feb 20 03:46:39 Tower emhttpd: read SMART /dev/sdj Feb 20 03:46:39 Tower emhttpd: read SMART /dev/sdk Feb 20 03:46:39 Tower emhttpd: read SMART /dev/sdb Feb 20 03:46:39 Tower emhttpd: read SMART /dev/sdi Feb 20 03:46:39 Tower emhttpd: read SMART /dev/sdg Feb 20 03:46:39 Tower emhttpd: read SMART /dev/sdq Feb 20 03:46:39 Tower emhttpd: read SMART /dev/sdc Feb 20 03:46:39 Tower emhttpd: read SMART /dev/sde Feb 20 03:46:39 Tower kernel: emhttpd[2720]: segfault at 674 ip 000055d29292a9d4 sp 00007ffcc4755040 error 4 in emhttpd[55d292918000+21000] Feb 20 03:46:39 Tower kernel: Code: 8e 27 01 00 48 89 45 f8 48 8d 05 72 27 01 00 48 89 45 f0 e9 79 01 00 00 8b 45 ec 89 c7 e8 89 b1 ff ff 48 89 45 d8 48 8b 45 d8 <8b> 80 74 06 00 00 85 c0 0f 94 c0 0f b6 c0 89 45 d4 48 8b 45 e0 48 Feb 20 03:46:42 Tower kernel: sd 2:0:5:0: Mode parameters changed Feb 20 03:46:44 Tower kernel: sd 2:0:16:0: Mode parameters changed Unraid is having trouble with the hot plug devices and the device designations are changing. How are these devices connected?
  6. I've added soom additional logging to help understand the issue you are having. Update UD and be sure you mount a shared disk before posting diagnistics again.
  7. UD is not setting up the SMB or NFS shares and I see no reason for that. My only suggestions are: Click on the double arrows on the UD page and see if it fixes the problem. Reboot. If UD has set up the share properly, you'll see it in the testparm output between the [global] and [flash] sections. If neither of these work, let me know and I'll look at it some more tomorrow.
  8. I don't see in the log where samba is setup on the disk share after the disk is mounted. Are you sure you have the disk share switch on?
  9. It does use consume memory, so you might want to back it off a bit.
  10. Yes, make it a large number and then start file activity. Keep increasing until file activity starts. Watch to the right side and be sure the "Available User Watches" is a positive number.
  11. That's generally because there aren't enough inotify watches. Look at the syslog and there should be a message saying that. If that is the case, install the Tips and Tweaks plugin and set the inotify watches so you have enough. A little trial and error will get you there.
  12. It says the version in the update dialog and the "Done" button shows when it is done. What is the concern?
×
×
  • Create New...