pegounet

Hello there , I'm getting exact same message than @Toobie I'm getting stuck at step 6 "Update in Progress" => Any help please ?

just put shareCacheFloor="1GB" in \config\share.cfg & diskShareFloor="1GB" for each & every cache pool ( config file content reflects the one of the WebUI while clicking on the first disk in the pool) => FCP stills shows the warning "Cache Disk free space is less than the cache floor setting" => So it seems to be a bug in FCP

ok shareCacheFloor="90GB" seems to be in flash\config\share.cfg but no more available in the UI. So i guess this is a general setting applicable for every & each of my cache pool ? I'd rather have 1 different shareCacheFloor per cache pool if possible. would u recommand me to change it directly in the file? would it survive a reboot?

ok thk u for diag analysis, but i can't access to cache floor settings in "Global Share Settings" since ugrade in 6.9.x from 6.8.3. I've seen https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-690-beta25-available-r990/page/4/ "Part of same bug: shareCacheFloor in share.cfg is not used anymore at all. An individual floor setting for a pool can be set by editing the pools/<pool name>.cfg file and specify value for 'diskFloor'. " but i only get diskShareFloor="0" in my \\UNRAID\flash\config\pools\cache.cfg file , no diskFloor=90. I can't even see where this 90GB limit is defined /where i can change it? Should i change/define anything in this config\pools\cache.cfg file? is /will this bug (be) corrected somewhere in the UI?

Hello my FixProblems states Cache Disk free space is less than the cache floor setting, but it is not the case, i have 35% space left on my cache share. (& my 2 other cache pools have 54 % & 74% space left) Any ideas ? config Unraid 6.9.1 Pro attached diagnostic file tower-diagnostics-20210405-0053.zip

OK, how do u do that ?

i reply to myself in case it can help other users: issue was inisde my syslinux.cfg file , i had just " label Unraid OS menu default kernel /bzimage append intel_iommu=off initrd=/bzroot " i changed last line in " append intel_iommu=on initrd=/bzroot " and it worked like a charm

em... ok so how is it possible that it is stated that IOMMU is disbaled as the VT-d is enabled in BIOS?

Hello I have a Asus P8BWS motherboard with VT-x & VT-d enabled. Bios version is last one from 2019. https://www.asus.com/us/supportonly/P8B WS/HelpDesk_BIOS/ CPU is Xeon E3-1245. https://ark.intel.com/content/www/us/en/ark/products/65729/intel-xeon-processor-e3-1245-v2-8m-cache-3-40-ghz.html So everything should be fine in order to pass trough PCIe devices, but IOMMU appears disabled in unraid . Please note that years ago i was able to pass trough devices such as HardDrives to ESXi in RDM mode of vsphere. Is it something not working as expected in Unraid OS version 6.8.3 for IOMMU support? Here enclosed some more info for ur support please any advise welcome tower-diagnostics-20201122-2226.zip

Hello, My \download share is configured with Minimum free space of 40Go and Cache Settings has min free space set at 10Go. \download is made of [ SSD disk pool cache of 1.25 To + 1 physical drive of 2To in the array] Refering to cache settings min free space definition "This represents a "floor" of the amount of free space remaining on the cache disk. If the free space becomes less than this value, then new files written to user shares with cache enabled will go to the array and not the cache disk" i thought that it is not possible that any file whatever is size can be downloaded onto cache pool when the free space becomes less than 10Go. I'm right or not? i'm downloading through sonarr/radarr/couchpotato/headphones

Hello, - got "**** /var/log is getting full (currently 93 % used) **** **** Unable to write to cache **** **** Unable to write to Docker Image **** **** Cache Disk free space is less than the cache floor setting **** " - unable to start docker My understanding is that i don't have any left space on my cache drive, but normally no new downloads should occur on it, but on the array (download share in "prefer" mode) attached is my diagnostics tower-diagnostics-20191117-2304.zip

hello I don't understand why i have daily error msg related to out of memory errors. SOmetimes, system seems to kill "mono" process, and sometimes "plex". I can also see "rmdir error directory isnot empty" tower-diagnostics-20181023-0031.zip can someone explain please?

hello there, since a few days i have every day OOM errors in my logs and fixcommon script tower-diagnostics-20181021-2346.zip Any help targeting what's the issue ? thk u

hello squid you're right it seems i forgot to disable my user script weekly backup targeting a no more existing device. thk u so much,

hello i have those 2 errors following schedulded excecution of fix common problems script: **** Rootfs file is getting full (currently 100 % used) **** **** Out Of Memory errors detected on your server **** I have attached here corresponding syslog file before reboot 110108192018-syslog-pegounet.txt and executed diagnostic after reboot thk u in advance for ur support tower-diagnostics-20180819-1724.zip

thk u guys i have changed sata cable and provided partiy check works like a charm

Hi all, I am running firmware version 6.4.0 and I have a drive checked with a red x . I had just powered the unit on after a move, so I checked and it looks like the drive in question had become unsecured. I secured it and made sure it was plugged in. I have since completed a SMART report and it passed. I've attached the smart report and diagnostics below. i also passed an extended smart self-test in device page and it completed without error. Based on the Smart report, am I safe to rebuild the drive? tower-diagnostics-20180731-2218.zip

hello i have tried something else for my issue with 4TB seagate passing through USB: i have plugged it into a RAID adapter as single volume. Then U.D. could see my disk without any issue. I have then formatted it with XFS thanks to U.D. => works well. I was hoping i could see it later while connected in an USB enclosure. But no chance... issue is different that time, but U.D. is still unable to mount this drive (only when connected through USB. Please note i have tried with 2 different USB enclosures => same bad result...) any advise? /// Jul 30 18:59:23 Tower kernel: usb 1-1.1: USB disconnect, device number 5 Jul 30 18:59:23 Tower unassigned.devices: benchmark: shell_exec(/usr/bin/timeout 20 /bin/df '/dev/sdp1' --output=size,used,avail|/bin/grep -v '1K-blocks' > /tmp/unassigned.devices/df 2>/dev/null) took 19.064277s. Jul 30 18:59:23 Tower kernel: sd 10:0:0:0: [sdp] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 Jul 30 18:59:23 Tower kernel: sd 10:0:0:0: [sdp] tag#0 CDB: opcode=0x8a 8a 00 00 00 00 00 e8 d0 00 44 00 00 00 02 00 00 Jul 30 18:59:23 Tower kernel: print_req_error: I/O error, dev sdp, sector 3905945668 Jul 30 18:59:23 Tower kernel: XFS (sdp1): metadata I/O error: block 0xe8d00004 ("xlog_iodone") error 5 numblks 64 Jul 30 18:59:23 Tower kernel: XFS (sdp1): xfs_do_force_shutdown(0x2) called from line 1232 of file fs/xfs/xfs_log.c. Return address = 0xffffffffa02b5c11 Jul 30 18:59:23 Tower kernel: XFS (sdp1): Log I/O Error Detected. Shutting down filesystem Jul 30 18:59:23 Tower kernel: XFS (sdp1): Please umount the filesystem and rectify the problem(s) Jul 30 18:59:23 Tower unassigned.devices: benchmark: shell_exec(/usr/bin/timeout 20 /bin/df '/dev/sdp1' --output=size,used,avail|/bin/grep -v '1K-blocks' > /tmp/unassigned.devices/df 2>/dev/null) took 18.465126s. Jul 30 18:59:23 Tower unassigned.devices: benchmark: shell_exec(/usr/bin/timeout 20 /bin/df '/dev/sdp1' --output=size,used,avail|/bin/grep -v '1K-blocks' > /tmp/unassigned.devices/df 2>/dev/null) took 18.477993s. Jul 30 18:59:23 Tower unassigned.devices: benchmark: shell_exec(/usr/bin/timeout 20 /bin/df '/dev/sdp1' --output=size,used,avail|/bin/grep -v '1K-blocks' > /tmp/unassigned.devices/df 2>/dev/null) took 17.152884s. Jul 30 18:59:23 Tower kernel: usb 1-1.1: new high-speed USB device number 6 using ehci-pci Jul 30 18:59:23 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 30 18:59:23 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 30 18:59:24 Tower kernel: usb 1-1.1: new high-speed USB device number 7 using ehci-pci Jul 30 18:59:24 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 30 18:59:24 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token Jul 30 18:59:24 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 30 18:59:24 Tower kernel: usb 1-1-port1: attempt power cycle Jul 30 18:59:25 Tower kernel: usb 1-1.1: new high-speed USB device number 8 using ehci-pci Jul 30 18:59:25 Tower kernel: usb 1-1.1: device not accepting address 8, error -71 Jul 30 18:59:25 Tower kernel: usb 1-1.1: new high-speed USB device number 9 using ehci-pci Jul 30 18:59:26 Tower kernel: usb 1-1.1: device not accepting address 9, error -71 Jul 30 18:59:26 Tower kernel: usb 1-1-port1: unable to enumerate USB device Jul 30 19:03:12 Tower kernel: usb 1-1.1: new high-speed USB device number 10 using ehci-pci Jul 30 19:03:12 Tower kernel: usb-storage 1-1.1:1.0: USB Mass Storage device detected Jul 30 19:03:12 Tower kernel: usb-storage 1-1.1:1.0: Quirks match for vid 152d pid 2329: 8020 Jul 30 19:03:12 Tower kernel: scsi host11: usb-storage 1-1.1:1.0 Jul 30 19:03:13 Tower kernel: scsi 11:0:0:0: Direct-Access ST4000DM 004-2CV104 PQ: 0 ANSI: 2 CCS Jul 30 19:03:13 Tower kernel: sd 11:0:0:0: Attached scsi generic sg15 type 0 Jul 30 19:03:13 Tower kernel: sd 11:0:0:0: [sdq] Very big device. Trying to use READ CAPACITY(16). Jul 30 19:03:13 Tower kernel: sd 11:0:0:0: [sdq] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) Jul 30 19:03:13 Tower kernel: sd 11:0:0:0: [sdq] Write Protect is off Jul 30 19:03:13 Tower kernel: sd 11:0:0:0: [sdq] Mode Sense: 28 00 00 00 Jul 30 19:03:13 Tower kernel: sd 11:0:0:0: [sdq] No Caching mode page found Jul 30 19:03:13 Tower kernel: sd 11:0:0:0: [sdq] Assuming drive cache: write through Jul 30 19:03:13 Tower kernel: sd 11:0:0:0: [sdq] Very big device. Trying to use READ CAPACITY(16). Jul 30 19:03:13 Tower kernel: GPT:Primary header thinks Alt. header is not at the end of the disk. Jul 30 19:03:13 Tower kernel: GPT:7811891199 != 7814037167 Jul 30 19:03:13 Tower kernel: GPT:Alternate GPT header not at the end of the disk. Jul 30 19:03:13 Tower kernel: GPT:7811891199 != 7814037167 Jul 30 19:03:13 Tower kernel: GPT: Use GNU Parted to correct GPT errors. Jul 30 19:03:13 Tower kernel: sdq: sdq1 Jul 30 19:03:13 Tower kernel: sd 11:0:0:0: [sdq] Very big device. Trying to use READ CAPACITY(16). Jul 30 19:03:13 Tower kernel: sd 11:0:0:0: [sdq] Attached SCSI disk Jul 30 19:03:14 Tower unassigned.devices: Adding disk '/dev/sdq1'... Jul 30 19:03:14 Tower unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sdq1' '/mnt/disks/ST4000DM004-2CV104_ZFN15573' Jul 30 19:03:14 Tower kernel: XFS (sdq1): Filesystem has duplicate UUID 4df411d4-f5e6-402d-85e3-463d6d5e3101 - can't mount Jul 30 19:03:14 Tower unassigned.devices: Mount of '/dev/sdq1' failed. Error message: mount: /mnt/disks/ST4000DM004-2CV104_ZFN15573: wrong fs type, bad option, bad superblock on /dev/sdq1, missing codepage or helper program, or other error. Jul 30 19:03:14 Tower unassigned.devices: Partition 'ST4000DM004-2CV104_ZFN15573' could not be mounted... Jul 30 19:03:17 Tower sSMTP[15643]: Creating SSL connection to host Jul 30 19:03:17 Tower sSMTP[15643]: SSL connection using ECDHE-RSA-AES128-GCM-SHA256 Jul 30 19:03:20 Tower sSMTP[15643]: Sent mail for [email protected] (221 2.0.0 closing connection y191-v6sm108132wmy.4 - gsmtp) uid=0 username=root outbytes=880 Jul 30 19:03:46 Tower kernel: usb 1-1.1: reset high-speed USB device number 10 using ehci-pci Jul 30 19:03:46 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 30 19:03:46 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 30 19:03:46 Tower kernel: usb 1-1.1: reset high-speed USB device number 10 using ehci-pci Jul 30 19:03:46 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 30 19:03:46 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 30 19:03:46 Tower kernel: usb 1-1.1: reset high-speed USB device number 10 using ehci-pci Jul 30 19:03:47 Tower kernel: usb 1-1.1: device not accepting address 10, error -71 Jul 30 19:03:47 Tower kernel: usb 1-1.1: reset high-speed USB device number 10 using ehci-pci Jul 30 19:03:47 Tower kernel: usb 1-1.1: device not accepting address 10, error -71 Jul 30 19:03:47 Tower kernel: usb 1-1.1: USB disconnect, device number 10 Jul 30 19:03:47 Tower kernel: usb 1-1.1: new high-speed USB device number 11 using ehci-pci Jul 30 19:03:48 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 30 19:03:48 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 30 19:03:48 Tower kernel: usb 1-1.1: new high-speed USB device number 12 using ehci-pci Jul 30 19:03:48 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 30 19:03:48 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 30 19:03:48 Tower kernel: usb 1-1-port1: attempt power cycle Jul 30 19:03:49 Tower kernel: usb 1-1.1: new high-speed USB device number 13 using ehci-pci Jul 30 19:03:49 Tower kernel: usb 1-1.1: device not accepting address 13, error -71 Jul 30 19:03:49 Tower kernel: usb 1-1.1: new high-speed USB device number 14 using ehci-pci Jul 30 19:03:50 Tower kernel: usb 1-1.1: device not accepting address 14, error -71 Jul 30 19:03:50 Tower kernel: usb 1-1-port1: unable to enumerate USB device tower-diagnostics-20180730-1908.zip

hello i have just capturd in my system log following out of memory errors seems related to plex media scan ... any advise to avoid that? Should i check plex logs or repair some plex index ? " Jul 6 23:17:45 Tower kernel: java invoked oom-killer: gfp_mask=0x14201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), nodemask=(null), order=0, oom_score_adj=0 Jul 6 23:17:45 Tower kernel: java cpuset=f2c181c24e778f9f78e36ea1469058c838d3cbaad01fe384dc1b66cf7ba4b613 mems_allowed=0 Jul 6 23:17:45 Tower kernel: CPU: 6 PID: 7200 Comm: java Not tainted 4.14.13-unRAID #1 Jul 6 23:17:45 Tower kernel: Hardware name: System manufacturer System Product Name/P8B WS, BIOS 0904 10/24/2011 Jul 6 23:17:45 Tower kernel: Call Trace: Jul 6 23:17:45 Tower kernel: dump_stack+0x5d/0x79 Jul 6 23:17:45 Tower kernel: dump_header+0x8f/0x23c Jul 6 23:17:45 Tower kernel: ? _raw_spin_lock+0x12/0x20 Jul 6 23:17:45 Tower kernel: oom_kill_process+0x7e/0x38a Jul 6 23:17:45 Tower kernel: out_of_memory+0x3ad/0x3cd Jul 6 23:17:45 Tower kernel: __alloc_pages_nodemask+0x958/0xb03 Jul 6 23:17:45 Tower kernel: ? __radix_tree_lookup+0x5a/0x7e Jul 6 23:17:45 Tower kernel: filemap_fault+0x2e6/0x42e Jul 6 23:17:45 Tower kernel: __do_fault+0x12/0x4a Jul 6 23:17:45 Tower kernel: __handle_mm_fault+0x8cb/0xfeb Jul 6 23:17:45 Tower kernel: handle_mm_fault+0x125/0x174 Jul 6 23:17:45 Tower kernel: __do_page_fault+0x25d/0x3e2 Jul 6 23:17:45 Tower kernel: ? page_fault+0x36/0x60 Jul 6 23:17:45 Tower kernel: page_fault+0x4c/0x60 Jul 6 23:17:45 Tower kernel: RIP: 0033:0x14c6f9399749 Jul 6 23:17:45 Tower kernel: RSP: 002b:000014c6da6c7bf0 EFLAGS: 00010202 Jul 6 23:17:45 Tower kernel: Mem-Info: Jul 6 23:17:45 Tower kernel: active_anon:1864069 inactive_anon:15684 isolated_anon:0 Jul 6 23:17:45 Tower kernel: active_file:870 inactive_file:3323 isolated_file:64 Jul 6 23:17:45 Tower kernel: unevictable:0 dirty:139 writeback:13 unstable:0 Jul 6 23:17:45 Tower kernel: slab_reclaimable:15177 slab_unreclaimable:44926 Jul 6 23:17:45 Tower kernel: mapped:28563 shmem:128216 pagetables:11246 bounce:0 Jul 6 23:17:45 Tower kernel: free:42043 free_pcp:0 free_cma:0 Jul 6 23:17:45 Tower kernel: Node 0 active_anon:7456276kB inactive_anon:62736kB active_file:3480kB inactive_file:13292kB unevictable:0kB isolated(anon):0kB isolated(file):256kB mapped:114252kB dirty:556kB writeback:52kB shmem:512864kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 2615296kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no Jul 6 23:17:45 Tower kernel: Node 0 DMA free:15360kB min:256kB low:320kB high:384kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15980kB managed:15360kB mlocked:0kB kernel_stack:0kB pagetables:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB Jul 6 23:17:45 Tower kernel: lowmem_reserve[]: 0 3064 7796 7796 Jul 6 23:17:45 Tower kernel: Node 0 DMA32 free:71100kB min:53024kB low:66280kB high:79536kB active_anon:3095340kB inactive_anon:604kB active_file:828kB inactive_file:4416kB unevictable:0kB writepending:52kB present:3300676kB managed:3287308kB mlocked:0kB kernel_stack:3648kB pagetables:16192kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB Jul 6 23:17:45 Tower kernel: lowmem_reserve[]: 0 0 4732 4732 Jul 6 23:17:45 Tower kernel: Node 0 Normal free:81712kB min:81880kB low:102348kB high:122816kB active_anon:4361164kB inactive_anon:62132kB active_file:1668kB inactive_file:9392kB unevictable:0kB writepending:556kB present:4978688kB managed:4846096kB mlocked:0kB kernel_stack:13344kB pagetables:28792kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB Jul 6 23:17:45 Tower kernel: lowmem_reserve[]: 0 0 0 0 Jul 6 23:17:45 Tower kernel: Node 0 DMA: 0*4kB 0*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 1*1024kB (U) 1*2048kB (U) 3*4096kB (M) = 15360kB Jul 6 23:17:45 Tower kernel: Node 0 DMA32: 1765*4kB (UM) 2040*8kB (UE) 1402*16kB (UME) 584*32kB (UE) 115*64kB (UE) 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 71860kB Jul 6 23:17:45 Tower kernel: Node 0 Normal: 61*4kB (UM) 21*8kB (UM) 1661*16kB (UME) 1254*32kB (UE) 235*64kB (UE) 2*128kB (U) 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 82412kB Jul 6 23:17:45 Tower kernel: 132348 total pagecache pages Jul 6 23:17:45 Tower kernel: 0 pages in swap cache Jul 6 23:17:45 Tower kernel: Swap cache stats: add 0, delete 0, find 0/0 Jul 6 23:17:45 Tower kernel: Free swap = 0kB Jul 6 23:17:45 Tower kernel: Total swap = 0kB Jul 6 23:17:45 Tower kernel: 2073836 pages RAM Jul 6 23:17:45 Tower kernel: 0 pages HighMem/MovableOnly Jul 6 23:17:45 Tower kernel: 36645 pages reserved Jul 6 23:17:45 Tower kernel: 0 pages cma reserved Jul 6 23:17:45 Tower kernel: [ pid ] uid tgid total_vm rss nr_ptes nr_pmds swapents oom_score_adj name Jul 6 23:17:45 Tower kernel: [ 1194] 0 1194 7327 1043 16 3 0 -1000 udevd Jul 6 23:17:45 Tower kernel: [ 1466] 0 1466 59474 571 24 3 0 0 rsyslogd Jul 6 23:17:45 Tower kernel: [ 1591] 81 1591 4937 537 14 3 0 0 dbus-daemon Jul 6 23:17:45 Tower kernel: [ 1599] 32 1599 3373 551 11 4 0 0 rpcbind Jul 6 23:17:45 Tower kernel: [ 1603] 32 1603 4869 1485 14 3 0 0 rpc.statd Jul 6 23:17:45 Tower kernel: [ 1621] 0 1621 6149 109 15 3 0 -1000 sshd Jul 6 23:17:45 Tower kernel: [ 1638] 44 1638 25707 1276 24 3 0 0 ntpd Jul 6 23:17:45 Tower kernel: [ 1644] 0 1644 1123 23 7 3 0 0 acpid Jul 6 23:17:45 Tower kernel: [ 1653] 0 1653 1649 428 8 3 0 0 crond Jul 6 23:17:45 Tower kernel: [ 1655] 0 1655 1646 376 7 3 0 0 atd Jul 6 23:17:45 Tower kernel: [ 1662] 0 1662 54652 1487 104 3 0 0 nmbd Jul 6 23:17:45 Tower kernel: [ 1664] 0 1664 75049 3975 142 3 0 0 smbd Jul 6 23:17:45 Tower kernel: [ 1666] 0 1666 73428 1248 135 3 0 0 smbd-notifyd Jul 6 23:17:45 Tower kernel: [ 1667] 0 1667 73432 1180 134 3 0 0 cleanupd Jul 6 23:17:45 Tower kernel: [ 1669] 0 1669 67617 1971 126 3 0 0 winbindd Jul 6 23:17:45 Tower kernel: [ 1671] 0 1671 68038 3281 130 3 0 0 winbindd Jul 6 23:17:45 Tower kernel: [ 1888] 0 1888 1647 444 8 3 0 0 inetd Jul 6 23:17:45 Tower kernel: [ 5542] 0 5542 1655 446 8 3 0 0 agetty Jul 6 23:17:45 Tower kernel: [ 5543] 0 5543 1655 457 8 3 0 0 agetty Jul 6 23:17:45 Tower kernel: [ 5544] 0 5544 1655 466 9 3 0 0 agetty Jul 6 23:17:45 Tower kernel: [ 5545] 0 5545 1655 465 8 3 0 0 agetty Jul 6 23:17:45 Tower kernel: [ 5546] 0 5546 1655 426 8 3 0 0 agetty Jul 6 23:17:45 Tower kernel: [ 5547] 0 5547 1655 421 8 3 0 0 agetty Jul 6 23:17:45 Tower kernel: [ 5587] 0 5587 38750 1206 17 3 0 0 apcupsd Jul 6 23:17:45 Tower kernel: [ 5612] 61 5612 8175 845 20 3 0 0 avahi-daemon Jul 6 23:17:45 Tower kernel: [ 5613] 61 5613 8078 65 19 3 0 0 avahi-daemon Jul 6 23:17:45 Tower kernel: [ 5622] 0 5622 3215 28 11 3 0 0 avahi-dnsconfd Jul 6 23:17:45 Tower kernel: [ 5635] 0 5635 73683 744 23 3 0 0 emhttpd Jul 6 23:17:45 Tower kernel: [ 5662] 0 5662 26342 1421 22 3 0 0 ttyd Jul 6 23:17:45 Tower kernel: [ 5665] 0 5665 16062 917 17 3 0 0 nginx Jul 6 23:17:45 Tower kernel: [ 5666] 99 5666 17779 2226 22 3 0 0 nginx Jul 6 23:17:45 Tower kernel: [ 5763] 0 5763 2451 676 9 3 0 0 diskload Jul 6 23:17:45 Tower kernel: [ 5819] 0 5819 45025 3108 70 3 0 0 php-fpm Jul 6 23:17:45 Tower kernel: [ 6043] 0 6043 38365 132 16 3 0 0 shfs Jul 6 23:17:45 Tower kernel: [ 6056] 0 6056 563136 36768 139 5 0 0 shfs Jul 6 23:17:45 Tower kernel: [ 6090] 99 6090 5968 1312 15 3 0 0 openvpn Jul 6 23:17:45 Tower kernel: [ 6229] 0 6229 334769 12932 101 7 0 -500 dockerd Jul 6 23:17:45 Tower kernel: [ 6247] 0 6247 248094 3380 54 6 0 -500 docker-containe Jul 6 23:17:45 Tower kernel: [ 6578] 0 6578 88679 576 22 5 0 -500 docker-containe Jul 6 23:17:45 Tower kernel: [ 6596] 0 6596 7270 1248 17 3 0 0 my_init Jul 6 23:17:45 Tower kernel: [ 6648] 0 6648 88263 874 21 5 0 -500 docker-containe Jul 6 23:17:45 Tower kernel: [ 6666] 0 6666 1127 19 7 3 0 0 sh Jul 6 23:17:45 Tower kernel: [ 6716] 0 6716 1099 23 7 3 0 0 runsvdir Jul 6 23:17:45 Tower kernel: [ 6717] 0 6717 1061 19 7 3 0 0 runsv Jul 6 23:17:45 Tower kernel: [ 6718] 0 6718 1061 18 7 3 0 0 runsv Jul 6 23:17:45 Tower kernel: [ 6719] 0 6719 1061 18 7 3 0 0 runsv Jul 6 23:17:45 Tower kernel: [ 6720] 0 6720 1061 18 7 3 0 0 runsv Jul 6 23:17:45 Tower kernel: [ 6721] 0 6721 1061 19 7 3 0 0 runsv Jul 6 23:17:45 Tower kernel: [ 6722] 0 6722 1061 18 7 3 0 0 runsv Jul 6 23:17:45 Tower kernel: [ 6723] 0 6723 1905 28 8 3 0 0 tail Jul 6 23:17:45 Tower kernel: [ 6724] 0 6724 5321 58 14 3 0 0 run Jul 6 23:17:45 Tower kernel: [ 6725] 0 6725 21362 5617 35 3 0 0 Xvnc Jul 6 23:17:45 Tower kernel: [ 6726] 0 6726 5319 58 14 3 0 0 run Jul 6 23:17:45 Tower kernel: [ 6727] 0 6727 18115 403 39 3 0 0 syslog-ng Jul 6 23:17:45 Tower kernel: [ 6728] 0 6728 46669 857 79 3 0 0 openbox Jul 6 23:17:45 Tower kernel: [ 6730] 0 6730 5330 76 15 3 0 0 bash Jul 6 23:17:45 Tower kernel: [ 6737] 0 6737 1700009 171992 546 9 0 0 java Jul 6 23:17:45 Tower kernel: [ 6747] 0 6747 4536 92 13 3 0 0 noip.sh Jul 6 23:17:45 Tower kernel: [ 6755] 0 6755 24760 3381 49 3 0 0 python Jul 6 23:17:45 Tower kernel: [ 6801] 65534 6801 4274 49 13 3 0 0 noip2-x86_64 Jul 6 23:17:45 Tower kernel: [ 6822] 0 6822 882 419 7 5 0 -500 docker-proxy Jul 6 23:17:45 Tower kernel: [ 6832] 0 6832 71943 628 21 5 0 -500 docker-containe Jul 6 23:17:45 Tower kernel: [ 6850] 0 6850 8192 1181 20 3 0 0 my_init Jul 6 23:17:45 Tower kernel: [ 6919] 0 6919 2753 1756 10 5 0 0 controlr Jul 6 23:17:45 Tower kernel: [ 6945] 0 6945 5321 67 15 3 0 0 startapp.sh Jul 6 23:17:45 Tower kernel: [ 7065] 0 7065 882 419 6 5 0 -500 docker-proxy Jul 6 23:17:45 Tower kernel: [ 7077] 0 7077 882 419 7 5 0 -500 docker-proxy Jul 6 23:17:45 Tower kernel: [ 7089] 0 7089 2643 331 10 5 0 -500 docker-proxy Jul 6 23:17:45 Tower kernel: [ 7098] 0 7098 88263 1385 22 5 0 -500 docker-containe Jul 6 23:17:45 Tower kernel: [ 7116] 0 7116 1070 15 7 3 0 0 tini Jul 6 23:17:45 Tower kernel: [ 7158] 0 7158 26058 3251 54 4 0 0 supervisord Jul 6 23:17:45 Tower kernel: [ 7181] 0 7181 1117559 73338 337 7 0 0 java Jul 6 23:17:45 Tower kernel: [ 7365] 0 7365 4024 151 11 3 0 0 start.sh Jul 6 23:17:45 Tower kernel: [ 7366] 99 7366 3991 125 11 3 0 0 sabnzbd.sh Jul 6 23:17:45 Tower kernel: [ 7367] 99 7367 3991 118 11 4 0 0 privoxy.sh Jul 6 23:17:45 Tower kernel: [ 7746] 0 7746 882 419 6 5 0 -500 docker-proxy Jul 6 23:17:45 Tower kernel: [ 7758] 0 7758 882 403 6 5 0 -500 docker-proxy Jul 6 23:17:45 Tower kernel: [ 7770] 0 7770 882 419 6 5 0 -500 docker-proxy Jul 6 23:17:45 Tower kernel: [ 7782] 0 7782 882 419 6 5 0 -500 docker-proxy Jul 6 23:17:45 Tower kernel: [ 7803] 0 7803 2771 479 10 5 0 -500 docker-proxy Jul 6 23:17:45 Tower kernel: [ 7848] 0 7848 55495 823 19 5 0 -500 docker-containe Jul 6 23:17:45 Tower kernel: [ 7865] 0 7865 1070 15 7 3 0 0 tini Jul 6 23:17:45 Tower kernel: [ 7966] 0 7966 26065 3272 55 3 0 0 supervisord Jul 6 23:17:45 Tower kernel: [ 8630] 0 8630 4024 145 11 3 0 0 start.sh Jul 6 23:17:45 Tower kernel: [ 8631] 99 8631 4024 137 11 3 0 0 deluge.sh Jul 6 23:17:45 Tower kernel: [ 8632] 99 8632 3991 115 12 3 0 0 deluge-web.sh Jul 6 23:17:45 Tower kernel: [ 8633] 99 8633 3991 119 12 4 0 0 privoxy.sh Jul 6 23:17:45 Tower kernel: [ 8928] 0 8928 19490 317 38 3 0 0 openvpn Jul 6 23:17:45 Tower kernel: [ 9796] 99 9796 3455 135 11 3 0 0 privoxy Jul 6 23:17:45 Tower kernel: [10461] 99 10461 3455 136 11 3 0 0 privoxy Jul 6 23:17:45 Tower kernel: [10546] 99 10546 696061 35883 214 6 0 0 python2 Jul 6 23:17:45 Tower kernel: [10758] 0 10758 882 419 6 5 0 -500 docker-proxy Jul 6 23:17:45 Tower kernel: [10773] 0 10773 88263 823 21 5 0 -500 docker-containe Jul 6 23:17:45 Tower kernel: [10790] 0 10790 49 1 3 2 0 0 s6-svscan Jul 6 23:17:45 Tower kernel: [10870] 0 10870 49 1 3 2 0 0 s6-supervise Jul 6 23:17:45 Tower kernel: [11092] 0 11092 49 1 3 2 0 0 s6-supervise Jul 6 23:17:45 Tower kernel: [11096] 99 11096 92284 48097 183 3 0 0 python Jul 6 23:17:45 Tower kernel: [11301] 0 11301 55559 825 21 5 0 -500 docker-containe Jul 6 23:17:45 Tower kernel: [11319] 0 11319 8501 1258 20 3 0 0 my_init Jul 6 23:17:45 Tower kernel: [11374] 0 11374 18092 393 39 3 0 0 syslog-ng Jul 6 23:17:45 Tower kernel: [11401] 99 11401 135246 39785 166 5 0 0 deluged Jul 6 23:17:45 Tower kernel: [11456] 99 11456 79353 13021 96 3 0 0 deluge-web Jul 6 23:17:45 Tower kernel: [11468] 0 11468 1098 21 7 3 0 0 runsvdir Jul 6 23:17:45 Tower kernel: [11469] 0 11469 1060 19 7 3 0 0 runsv Jul 6 23:17:45 Tower kernel: [11470] 0 11470 1060 19 7 3 0 0 runsv Jul 6 23:17:45 Tower kernel: [11471] 0 11471 1060 19 7 3 0 0 runsv Jul 6 23:17:45 Tower kernel: [11473] 0 11473 7744 62 18 3 0 0 cron Jul 6 23:17:45 Tower kernel: [11529] 0 11529 882 419 6 5 0 -500 docker-proxy Jul 6 23:17:45 Tower kernel: [11541] 0 11541 2090 482 8 5 0 -500 docker-proxy Jul 6 23:17:45 Tower kernel: [11581] 0 11581 71943 1149 21 5 0 -500 docker-containe Jul 6 23:17:45 Tower kernel: [11599] 0 11599 1070 15 7 3 0 0 tini Jul 6 23:17:45 Tower kernel: [11633] 0 11633 26050 3237 53 3 0 0 supervisord Jul 6 23:17:45 Tower kernel: [11667] 99 11667 1126 17 7 3 0 0 start_pms Jul 6 23:17:45 Tower kernel: [11696] 99 11696 3991 103 12 3 0 0 start.sh Jul 6 23:17:45 Tower kernel: [11697] 99 11697 1146833 138344 594 9 0 0 mono Jul 6 23:17:45 Tower kernel: [11711] 99 11711 244075 31116 307 4 0 0 Plex Media Serv Jul 6 23:17:45 Tower kernel: [11770] 0 11770 882 419 6 5 0 -500 docker-proxy Jul 6 23:17:45 Tower kernel: [11792] 0 11792 88263 632 21 5 0 -500 docker-containe Jul 6 23:17:45 Tower kernel: [11810] 0 11810 1070 16 7 3 0 0 tini Jul 6 23:17:45 Tower kernel: [11853] 0 11853 26025 3236 55 4 0 0 supervisord Jul 6 23:17:45 Tower kernel: [11890] 99 11890 438873 13012 121 4 0 0 Plex Script Hos Jul 6 23:17:45 Tower kernel: [11927] 99 11927 1110324 280309 766 8 0 0 python2 Jul 6 23:17:45 Tower kernel: [11988] 99 11988 123318 11126 117 4 0 0 Plex DLNA Serve Jul 6 23:17:45 Tower kernel: [11989] 99 11989 150643 839 62 4 0 0 Plex Tuner Serv Jul 6 23:17:45 Tower kernel: [11996] 99 11996 242254 6968 93 4 0 0 Plex Script Hos Jul 6 23:17:45 Tower kernel: [11998] 99 11998 455824 49264 193 5 0 0 Plex Script Hos Jul 6 23:17:45 Tower kernel: [12001] 99 12001 244718 9897 98 4 0 0 Plex Script Hos Jul 6 23:17:45 Tower kernel: [12115] 99 12115 235476 18715 76 16 0 0 scrapmagnet Jul 6 23:17:45 Tower kernel: [12176] 99 12176 243512 8499 97 4 0 0 Plex Script Hos Jul 6 23:17:45 Tower kernel: [12213] 99 12213 533826 60937 247 6 0 0 Plex Script Hos Jul 6 23:17:45 Tower kernel: [12747] 0 12747 67617 1033 125 3 0 0 winbindd Jul 6 23:17:45 Tower kernel: [14864] 0 14864 49 4 3 2 0 0 runsvdir Jul 6 23:17:45 Tower kernel: [14865] 0 14865 44 2 3 2 0 0 runsv Jul 6 23:17:45 Tower kernel: [14866] 0 14866 44 3 3 2 0 0 runsv Jul 6 23:17:45 Tower kernel: [14867] 0 14867 44 2 3 2 0 0 runsv Jul 6 23:17:45 Tower kernel: [14868] 0 14868 44 3 3 2 0 0 runsv Jul 6 23:17:45 Tower kernel: [14869] 0 14869 44 3 3 2 0 0 runsv Jul 6 23:17:45 Tower kernel: [14872] 0 14872 95647 2953 122 3 0 0 php5-fpm Jul 6 23:17:45 Tower kernel: [14873] 0 14873 2291 23 8 3 0 0 tail Jul 6 23:17:45 Tower kernel: [14874] 0 14874 7110 71 17 3 0 0 cron Jul 6 23:17:45 Tower kernel: [14875] 0 14875 24066 331 42 3 0 0 nginx Jul 6 23:17:45 Tower kernel: [14877] 99 14877 24432 654 40 3 0 0 nginx Jul 6 23:17:45 Tower kernel: [14878] 99 14878 24387 673 41 3 0 0 nginx Jul 6 23:17:45 Tower kernel: [14879] 99 14879 24434 693 41 3 0 0 nginx Jul 6 23:17:45 Tower kernel: [14880] 99 14880 24251 524 40 3 0 0 nginx Jul 6 23:17:45 Tower kernel: [18475] 0 18475 2974 655 10 3 0 0 mount.ntfs Jul 6 23:17:45 Tower kernel: [32756] 0 32756 3035 725 10 5 0 -500 docker-proxy Jul 6 23:17:45 Tower kernel: [32762] 0 32762 88263 885 21 5 0 -500 docker-containe Jul 6 23:17:45 Tower kernel: [ 312] 0 312 49 1 3 2 0 0 s6-svscan Jul 6 23:17:45 Tower kernel: [ 382] 0 382 49 1 3 2 0 0 s6-supervise Jul 6 23:17:45 Tower kernel: [ 834] 0 834 49 1 3 2 0 0 s6-supervise Jul 6 23:17:45 Tower kernel: [ 837] 99 837 432102 108327 370 6 0 0 mono Jul 6 23:17:45 Tower kernel: [31648] 0 31648 18959 315 39 3 0 0 openvpn Jul 6 23:17:45 Tower kernel: [13502] 0 13502 75673 3985 143 3 0 0 smbd Jul 6 23:17:45 Tower kernel: [27142] 99 27142 96666 5668 128 3 0 0 php5-fpm Jul 6 23:17:45 Tower kernel: [30352] 99 30352 96272 5312 127 3 0 0 php5-fpm Jul 6 23:17:45 Tower kernel: [ 895] 99 895 96405 5445 127 3 0 0 php5-fpm Jul 6 23:17:45 Tower kernel: [ 931] 99 931 96666 5664 128 3 0 0 php5-fpm Jul 6 23:17:45 Tower kernel: [ 6991] 0 6991 3486 968 11 3 0 0 bash Jul 6 23:17:45 Tower kernel: [ 7866] 0 7866 25863 3407 48 3 0 0 python Jul 6 23:17:45 Tower kernel: [ 9530] 0 9530 73683 674 23 3 0 0 emhttpd Jul 6 23:17:45 Tower kernel: [ 9532] 0 9532 2441 664 9 3 0 0 sh Jul 6 23:17:45 Tower kernel: [ 9533] 0 9533 1126 204 7 3 0 0 tail Jul 6 23:17:45 Tower kernel: [14585] 0 14585 45518 3605 70 3 0 0 php-fpm Jul 6 23:17:45 Tower kernel: [15044] 0 15044 45518 3603 70 3 0 0 php-fpm Jul 6 23:17:45 Tower kernel: [15211] 0 15211 45518 3606 70 3 0 0 php-fpm Jul 6 23:17:45 Tower kernel: [15490] 0 15490 45518 3602 70 3 0 0 php-fpm Jul 6 23:17:45 Tower kernel: [15569] 0 15569 45518 3611 70 3 0 0 php-fpm Jul 6 23:17:45 Tower kernel: [15654] 99 15654 1010724 525850 1963 7 0 0 Plex Media Scan Jul 6 23:17:45 Tower kernel: [15842] 0 15842 1095 19 7 3 0 0 sleep Jul 6 23:17:45 Tower kernel: [15857] 0 15857 45518 3603 70 3 0 0 php-fpm Jul 6 23:17:45 Tower kernel: [15873] 99 15873 1484 16 7 3 0 0 sleep Jul 6 23:17:45 Tower kernel: [15912] 99 15912 1484 16 6 3 0 0 sleep Jul 6 23:17:45 Tower kernel: [15929] 0 15929 1484 15 6 3 0 0 sleep Jul 6 23:17:45 Tower kernel: [15938] 0 15938 1118 216 7 3 0 0 sleep Jul 6 23:17:45 Tower kernel: [15977] 0 15977 643 10 7 3 0 0 pgrep Jul 6 23:17:45 Tower kernel: Out of memory: Kill process 15654 (Plex Media Scan) score 259 or sacrifice child Jul 6 23:17:45 Tower kernel: Killed process 15654 (Plex Media Scan) total-vm:4042896kB, anon-rss:2103344kB, file-rss:56kB, shmem-rss:0kB Jul 6 23:17:45 Tower kernel: oom_reaper: reaped process 15654 (Plex Media Scan), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB "

hello i have tried to powerdown USB enclosure with seagate in it UNRAID sees the drive a very short time, even the partition in the UD interface, but strangely disappears few seconds later... " Jul 6 23:12:33 Tower kernel: usb 1-1.1: new high-speed USB device number 24 using ehci-pci Jul 6 23:12:33 Tower kernel: usb-storage 1-1.1:1.0: USB Mass Storage device detected Jul 6 23:12:33 Tower kernel: usb-storage 1-1.1:1.0: Quirks match for vid 152d pid 2329: 8020 Jul 6 23:12:33 Tower kernel: scsi host9: usb-storage 1-1.1:1.0 Jul 6 23:12:34 Tower kernel: scsi 9:0:0:0: Direct-Access ST4000DM 004-2CV104 PQ: 0 ANSI: 2 CCS Jul 6 23:12:34 Tower kernel: sd 9:0:0:0: Attached scsi generic sg15 type 0 Jul 6 23:12:34 Tower kernel: sd 9:0:0:0: [sdp] Very big device. Trying to use READ CAPACITY(16). Jul 6 23:12:34 Tower kernel: sd 9:0:0:0: [sdp] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) Jul 6 23:12:34 Tower kernel: sd 9:0:0:0: [sdp] Write Protect is off Jul 6 23:12:34 Tower kernel: sd 9:0:0:0: [sdp] Mode Sense: 28 00 00 00 Jul 6 23:12:34 Tower kernel: sd 9:0:0:0: [sdp] No Caching mode page found Jul 6 23:12:34 Tower kernel: sd 9:0:0:0: [sdp] Assuming drive cache: write through Jul 6 23:12:34 Tower kernel: sd 9:0:0:0: [sdp] Very big device. Trying to use READ CAPACITY(16). Jul 6 23:12:34 Tower kernel: sdp: sdp1 Jul 6 23:12:34 Tower kernel: sd 9:0:0:0: [sdp] Very big device. Trying to use READ CAPACITY(16). Jul 6 23:12:34 Tower kernel: sd 9:0:0:0: [sdp] Attached SCSI disk Jul 6 23:12:34 Tower unassigned.devices: Adding disk '/dev/sdp1'... Jul 6 23:12:34 Tower unassigned.devices: No filesystem detected on '/dev/sdp1'. Jul 6 23:12:34 Tower unassigned.devices: Partition 'ST4000DM004-2CV104_ZFN15573' could not be mounted... Jul 6 23:13:08 Tower kernel: usb 1-1.1: reset high-speed USB device number 24 using ehci-pci Jul 6 23:13:08 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 6 23:13:08 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 6 23:13:08 Tower kernel: usb 1-1.1: reset high-speed USB device number 24 using ehci-pci Jul 6 23:13:08 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 6 23:13:08 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 6 23:13:08 Tower kernel: usb 1-1.1: reset high-speed USB device number 24 using ehci-pci Jul 6 23:13:09 Tower kernel: usb 1-1.1: device not accepting address 24, error -71 Jul 6 23:13:09 Tower kernel: usb 1-1.1: reset high-speed USB device number 24 using ehci-pci Jul 6 23:13:09 Tower kernel: usb 1-1.1: device not accepting address 24, error -71 Jul 6 23:13:09 Tower kernel: usb 1-1.1: USB disconnect, device number 24 Jul 6 23:13:09 Tower kernel: usb 1-1.1: new high-speed USB device number 25 using ehci-pci Jul 6 23:13:09 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 6 23:13:10 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 6 23:13:10 Tower kernel: usb 1-1.1: new high-speed USB device number 26 using ehci-pci Jul 6 23:13:10 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 6 23:13:10 Tower unassigned.devices: Removing partition '1' from disk '/dev/sdp'. Jul 6 23:13:10 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 6 23:13:10 Tower kernel: usb 1-1-port1: attempt power cycle Jul 6 23:13:11 Tower kernel: usb 1-1.1: new high-speed USB device number 27 using ehci-pci Jul 6 23:13:11 Tower kernel: usb 1-1.1: device not accepting address 27, error -71 Jul 6 23:13:11 Tower kernel: usb 1-1.1: new high-speed USB device number 28 using ehci-pci Jul 6 23:13:12 Tower kernel: usb 1-1.1: device not accepting address 28, error -71 Jul 6 23:13:12 Tower kernel: usb 1-1-port1: unable to enumerate USB device " => what is the meaning of 'device descriptor read error & device not accepting address..." ? any advise please ?

Hello there i have a seagate 4 Tb disk i want to use with UD, i formated it through USB on my windows laptop with EXT4 with partition wizard 10 device is not showing in UD when being plugged. any advise there on below error msg please? " Jul 5 07:46:01 Tower kernel: scsi 9:0:0:0: Direct-Access ST4000DM 004-2CV104 PQ: 0 ANSI: 2 CCS Jul 5 07:46:01 Tower kernel: sd 9:0:0:0: Attached scsi generic sg15 type 0 Jul 5 07:46:01 Tower kernel: sd 9:0:0:0: [sdp] Very big device. Trying to use READ CAPACITY(16). Jul 5 07:46:01 Tower kernel: sd 9:0:0:0: [sdp] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) Jul 5 07:46:01 Tower kernel: sd 9:0:0:0: [sdp] Write Protect is off Jul 5 07:46:01 Tower kernel: sd 9:0:0:0: [sdp] Mode Sense: 28 00 00 00 Jul 5 07:46:01 Tower kernel: sd 9:0:0:0: [sdp] No Caching mode page found Jul 5 07:46:01 Tower kernel: sd 9:0:0:0: [sdp] Assuming drive cache: write through Jul 5 07:46:01 Tower kernel: sd 9:0:0:0: [sdp] Very big device. Trying to use READ CAPACITY(16). Jul 5 07:46:01 Tower kernel: sdp: sdp1 Jul 5 07:46:01 Tower kernel: sd 9:0:0:0: [sdp] Very big device. Trying to use READ CAPACITY(16). Jul 5 07:46:01 Tower kernel: sd 9:0:0:0: [sdp] Attached SCSI disk Jul 5 07:46:01 Tower unassigned.devices: Adding disk '/dev/sdp1'... Jul 5 07:46:01 Tower unassigned.devices: No filesystem detected on '/dev/sdp1'. Jul 5 07:46:01 Tower unassigned.devices: Partition 'ST4000DM004-2CV104_ZFN15573' could not be mounted... Jul 5 07:46:36 Tower kernel: usb 1-1.1: reset high-speed USB device number 14 using ehci-pci Jul 5 07:46:36 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 5 07:46:36 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 5 07:46:37 Tower kernel: usb 1-1.1: reset high-speed USB device number 14 using ehci-pci Jul 5 07:46:37 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 5 07:46:37 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 5 07:46:37 Tower kernel: usb 1-1.1: reset high-speed USB device number 14 using ehci-pci Jul 5 07:46:37 Tower kernel: usb 1-1.1: device not accepting address 14, error -71 Jul 5 07:46:37 Tower kernel: usb 1-1.1: reset high-speed USB device number 14 using ehci-pci Jul 5 07:46:38 Tower kernel: usb 1-1.1: device not accepting address 14, error -71 Jul 5 07:46:38 Tower kernel: usb 1-1.1: USB disconnect, device number 14 Jul 5 07:46:38 Tower kernel: usb 1-1.1: new high-speed USB device number 15 using ehci-pci Jul 5 07:46:38 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 5 07:46:38 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 5 07:46:38 Tower kernel: usb 1-1.1: new high-speed USB device number 16 using ehci-pci Jul 5 07:46:38 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 5 07:46:39 Tower kernel: usb 1-1.1: device descriptor read/64, error -71 Jul 5 07:46:39 Tower kernel: usb 1-1-port1: attempt power cycle Jul 5 07:46:39 Tower kernel: usb 1-1.1: new high-speed USB device number 17 using ehci-pci Jul 5 07:46:40 Tower kernel: usb 1-1.1: device not accepting address 17, error -71 Jul 5 07:46:40 Tower kernel: usb 1-1.1: new high-speed USB device number 18 using ehci-pci Jul 5 07:46:40 Tower kernel: usb 1-1.1: device not accepting address 18, error -71 Jul 5 07:46:40 Tower kernel: usb 1-1-port1: unable to enumerate USB device "

thk u

oups... thank you for your advise, i have checked my mappings in dockers and the delugeVPN was defined with Container Path: /data = "/mnt/user/download " - with the space a big sorry for disturbing => my fault... thk u

hello thanks trurl for your support regarding docker image, yes i did have issue in the past with docker due to misconfig and increased the size accordingly at that time After reconfiguration, now and since about a year i don't have any issue with docker image. I agree 75Gb size seems overkill but i have about 400gb cache so i' don't really care with that docker size. i'm getting memory error message at 4:40 AM from time to time. which is the default daily schedule corresponding to execution of fix.common.problems.sh, logrotate, user.script.start.daily.sh I can't see any issue by myself with the server but was wondering about possible impacts of those ERR messages... do you want me to reexecute fix.common.problems.sh and take according diag file ?

ok understood. thk u for ur remarks ! yes they both have content but different contents, check enclosed image files: krusader-5 jpg shows the content. the left side of the windows content is the directory without the space, which is also the one i can map in windows client. what bother me is that one could had been created with a space (how could that be, through an app' or so ?) i can't access and my downloads currently occurs in it.