karateo

Restarting now to safe mode. The thing is that we or better I didn't change anything to my windows 10 install. I updated unraid, rebooted and I also rebooted windows 10 desktop. same problem even in safe mode is it possible to change samba debug level and find some logs?

Restarting now to safe mode. The thing is that we or better I didn't change anything to my windows 10 install. I updated unraid, rebooted and I also rebooted windows 10 desktop.

Another try... C:\WINDOWS\system32>net use w: \\192.168.1.2\Photos /USER:TOWER\tefi Enter the password for 'TOWER\tefi' to connect to '192.168.1.2': System error 86 has occurred. The specified network password is not correct. C:\WINDOWS\system32> Any ideas?!

I also have an Android app called FolderSync which transfers every day my photos to Unraid share but it stopped working. I googled a bit, tried a few steps but nothing worked. Not sure if something is wrong with the following output C:\WINDOWS\system32>net view Server Name Remark ------------------------------------------------------------------------------- \\karateo-DESKTOP \\TOWER Media server The command completed successfully. C:\WINDOWS\system32>nbtstat -a \\TOWER VirtualBox Host-Only Network #2: Node IpAddress: [192.168.56.1] Scope Id: [] Host not found. Ethernet: Node IpAddress: [192.168.1.4] Scope Id: [] Host not found. C:\WINDOWS\system32> C:\WINDOWS\system32>nbtstat -A 192.168.1.2 VirtualBox Host-Only Network #2: Node IpAddress: [192.168.56.1] Scope Id: [] Host not found. Ethernet: Node IpAddress: [192.168.1.4] Scope Id: [] NetBIOS Remote Machine Name Table Name Type Status --------------------------------------------- TOWER <00> UNIQUE Registered TOWER <03> UNIQUE Registered TOWER <20> UNIQUE Registered ??__MSBROWSE__?<01> GROUP Registered WORKGROUP <00> GROUP Registered WORKGROUP <1B> UNIQUE Registered WORKGROUP <1D> UNIQUE Registered WORKGROUP <1E> GROUP Registered MAC Address = 00-00-00-00-00-00 C:\WINDOWS\system32> Desktop 192.168.1.4 Unraid 192.168.1.2 Also, C:\WINDOWS\system32>whoami karateo-desktop\karateo Unraid username is karateo but with different password as windows uses email as login username so I use a very good password for outlook. I tried with a new set of username/password, common for windows and unraid and it didn't work.

yes so is anything I can do to fix the inability to access private smb shares from windows 10? FWIW it works ok for me. Meaning, for private shares I always create an unRaid user with same name and password as my windows logon. For example, if your windows login name is "moe" with password "stooges", then I create an unRaid user named "moe" with same password. Then in your private/secure share(s) give user "moe" the privileges you want. If windows credentials seem to get tangled up what works for me is: 1. make sure all applications and explorer windows that can possibly be referencing a server share are closed. 2. open command window and type net use * /delete 3. open services.msc and restart the "workstation" service. Now when you connect to a private share it just works, no login credentials are prompted because the windows user credentials already match those on the server. I will run some more tests to see if I can break it Tried all steps (and some more) and it didn't help. Are there any samba logs i can post here?

I seem to be having a similar issue, immediately after updating I could no longer acess any Samba shares from Windows 10. Everything I try to access the server via samba a popup asks for credentials, then always says they were invalid. Some things I have tried with no luck: - I have deleted the credentials from windows credentials manager. - I made a new user on Unraid. - I rebooted everything (firewall, switches, servers, computers). - I made sure unraid was the local master. - I Used the permissions script to reset permissions. Nothing I do can get the credentials to work. I have no idea what to do now. I have done exactly the same steps! I give up for today. I hope for a fix tomorrow or I will have to downgrade.

yes so is anything I can do to fix the inability to access private smb shares from windows 10?

is anything changed from previous stable to samba configuration/version?

I upgraded from previous stable with no problems. I restarted server and the SMB shares worked fine. I had to do multiple restarts to my desktop and now I cannot login to private shares. username/password is correct. server is "TOWER is current local master browser" I am using windows 10. Through windows 7 from a VM I can browse the //TOWER/Photos for example with no problem while I cannot from the desktop. I din't change anything! Any ideas?

I searched a bit but couldn't find the most update documentation on this topic. I found this wiki page but it's a bit old so I don't know if something has changed. http://lime-technology.com/wiki/index.php/FAQ#How_do_I_configure_NFS_mounts.3F I am not a linux expert so I will need your help. In server share options I have typed 192.168.1.0/24(rw) I clients /etc/fstab I have added lines like this 192.168.1.2:/mnt/user/Backups /mnt/unraid/backups nfs users,rw,auto 0 0 Are all the above options the right ones? Obviously I need r/w permissions through all 192.168.1.0/24 network Thank you! PS. 1) There is no HELP info in share page 2) There is no official documentation of nfs shares!

Sorry If I have missed something and what I think sounds stupid. But since you have btrfs raid-1 couldn't you "break" it (and keep to seperate copies of data) and try to assing disk1 as array disk1. If this works, then you add disk2 as parity, sync and ready! The only drawback is that you will be left with only one copy of data during the above so if the disk with that copy decides to die you will have a problem!

I am running 6.2.4 and I also couldn't find the explanation of the clone destinations in help. I googled the answer and found this topic.

Thank you both. I will get which one I get in stock near me then.

Quick question WD red 4Tb €169 Hitachi Deskstar NAS 4TB €167 I have good experience with WD disks and I know how to RMA a WD disk. I think I have read that Hitachi is a bit more reliable. Is it worth it to try Hitachi?

I use an android app called FolderSync to sync my pictures taken from mobile devices every day to a temp folder (as you can see) in order to prevent photos loss if a mobile device is stolen/broken etc. I am not sure if it sends part files and after a checksum check at the end of the file transfer it changes the filenames. I just googled and confirmed the above https://groups.google.com/forum/#!msg/tacitdynamics/aoxsUG8L_sY/YODkmFz2BjwJ However I don't know what causes this kind of errors. Could it be dynamic file integrity trying to create checksums?

I plugged a monitor today and saw this screen before hitting enter to prompt login input Is it related to my read errors or some other problem?

the syslog is the problem, because of my full cache drive and dropbox docker trying to do stuff for example the line below. I have changed the CAPS only. Dec 7 16:55:07 TOWER shfs/user: err: shfs_rmdir: rmdir: /mnt/cache/DropboxWIFE/MYNAME/KIDS/1510 (39) Directory not empty I will buy a new wd red and get rid of this drive asap. Thanks for confirming that it's the disk with the problem.

Attached portion of syslog cause it's almost full of Dec 7 16:55:05 TOWER shfs/user: err: shfs_mkdir: assign_disk:xxxxxxxxxxxxxxxxxxxxxxxxxxxxx (28) No space left on device and I don't want to share my folder names! I hope it's enough. Dec 2 13:49:42 TOWER kernel: Linux version 4.4.30-unRAID (root@develop64) (gcc version 5.3.0 (GCC) ) #2 SMP PREEMPT Sat Nov 5 12:09:05 PDT 2016 Dec 2 13:49:42 TOWER kernel: ACPI: Early table checksum verification disabled Dec 2 13:49:42 TOWER kernel: IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 Dec 2 13:49:42 TOWER kernel: Kernel command line: BOOT_IMAGE=/bzimage intel_pstate=disable initrd=/bzroot Dec 2 13:49:42 TOWER kernel: Memory: 11984176K/12329764K available (6321K kernel code, 678K rwdata, 2112K rodata, 924K init, 604K bss, 345588K reserved, 0K cma-reserved) Dec 2 13:49:42 TOWER kernel: Console: colour VGA+ 80x25 Dec 2 13:49:42 TOWER kernel: tsc: Detected 3292.687 MHz processor Dec 2 13:49:42 TOWER kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 6585.37 BogoMIPS (lpj=3292687) Dec 2 13:49:42 TOWER kernel: smpboot: CPU0: Intel(R) Xeon(R) CPU E3-1230 v3 @ 3.30GHz (family: 0x6, model: 0x3c, stepping: 0x3) Dec 2 13:49:42 TOWER kernel: Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver. Dec 2 13:49:42 TOWER kernel: smpboot: Total of 8 processors activated (52682.99 BogoMIPS) Dec 2 13:49:42 TOWER kernel: xor: automatically using best checksumming function: Dec 2 13:49:42 TOWER kernel: libata version 3.00 loaded. Dec 2 13:49:42 TOWER kernel: usbcore: registered new interface driver usbfs Dec 2 13:49:42 TOWER kernel: usbcore: registered new interface driver hub Dec 2 13:49:42 TOWER kernel: usbcore: registered new device driver usb Dec 2 13:49:42 TOWER kernel: fuse init (API version 7.23) Dec 2 13:49:42 TOWER kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) Dec 2 13:49:42 TOWER kernel: ipmi message handler version 39.2 Dec 2 13:49:42 TOWER kernel: ACPI: Thermal Zone [TZ00] (28 C) Dec 2 13:49:42 TOWER kernel: ACPI: Thermal Zone [TZ01] (30 C) Dec 2 13:49:42 TOWER kernel: Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled Dec 2 13:49:42 TOWER kernel: serial 0000:00:16.3: Couldn't register serial port f0a0, irq 19, type 0, error -28 Dec 2 13:49:42 TOWER kernel: lp: driver loaded but no devices found Dec 2 13:49:42 TOWER kernel: AMD IOMMUv2 driver by Joerg Roedel <[email protected]> Dec 2 13:49:42 TOWER kernel: VMware vmxnet3 virtual NIC driver - version 1.4.5.0-k-NAPI Dec 2 13:49:42 TOWER kernel: VFIO - User Level meta-driver version: 0.3 Dec 2 13:49:42 TOWER kernel: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver Dec 2 13:49:42 TOWER kernel: ehci-pci: EHCI PCI platform driver Dec 2 13:49:42 TOWER kernel: ehci-pci 0000:00:1a.0: EHCI Host Controller Dec 2 13:49:42 TOWER kernel: ehci-pci 0000:00:1d.0: EHCI Host Controller Dec 2 13:49:42 TOWER kernel: ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver Dec 2 13:49:42 TOWER kernel: ohci-pci: OHCI PCI platform driver Dec 2 13:49:42 TOWER kernel: uhci_hcd: USB Universal Host Controller Interface driver Dec 2 13:49:42 TOWER kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller Dec 2 13:49:42 TOWER kernel: xhci_hcd 0000:00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x00009810 Dec 2 13:49:42 TOWER kernel: xhci_hcd 0000:00:14.0: xHCI Host Controller Dec 2 13:49:42 TOWER kernel: usbcore: registered new interface driver usb-storage Dec 2 13:49:42 TOWER kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12 Dec 2 13:49:42 TOWER kernel: serio: i8042 KBD port at 0x60,0x64 irq 1 Dec 2 13:49:42 TOWER kernel: serio: i8042 AUX port at 0x60,0x64 irq 12 Dec 2 13:49:42 TOWER kernel: mousedev: PS/2 mouse device common for all mice Dec 2 13:49:42 TOWER kernel: usbcore: registered new interface driver synaptics_usb Dec 2 13:49:42 TOWER kernel: input: PC Speaker as /devices/platform/pcspkr/input/input3 Dec 2 13:49:42 TOWER kernel: hidraw: raw HID events driver (C) Jiri Kosina Dec 2 13:49:42 TOWER kernel: usbcore: registered new interface driver usbhid Dec 2 13:49:42 TOWER kernel: usbhid: USB HID core driver Dec 2 13:49:42 TOWER kernel: nf_conntrack version 0.5.0 (65536 buckets, 262144 max) Dec 2 13:49:42 TOWER kernel: ipip: IPv4 over IPv4 tunneling driver Dec 2 13:49:42 TOWER kernel: gre: GRE over IPv4 demultiplexor driver Dec 2 13:49:42 TOWER kernel: ip_gre: GRE over IPv4 tunneling driver Dec 2 13:49:42 TOWER kernel: IPv4 over IPsec tunneling driver Dec 2 13:49:42 TOWER kernel: registered taskstats version 1 Dec 2 13:49:42 TOWER kernel: floppy0: no floppy controllers found Dec 2 13:49:42 TOWER kernel: ahci 0000:00:1f.2: version 3.0 Dec 2 13:49:42 TOWER kernel: e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k Dec 2 13:49:42 TOWER kernel: e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode Dec 2 13:49:43 TOWER rpc.statd[1541]: Version 1.3.3 starting Dec 2 13:49:43 TOWER sm-notify[1542]: Version 1.3.3 starting Dec 2 13:49:43 TOWER rpc.statd[1541]: Failed to read /var/lib/nfs/state: Success Dec 2 13:49:43 TOWER root: Control file: Found correct version Dec 2 13:49:47 TOWER root: Version: 2016.11.27 Dec 2 13:49:48 TOWER root: Version: 2016.11.11 Dec 2 13:49:48 TOWER root: Version: 2016.11.30 Dec 2 13:49:48 TOWER root: Version: 2016.11.13 Dec 2 13:49:48 TOWER root: Version: 2016.09.20 Dec 2 13:49:48 TOWER root: plugin: not installing older version Dec 2 13:49:48 TOWER root: Version: 2016.11.03 Dec 2 13:49:51 TOWER root: Version: 2016.08.26 Dec 2 13:49:51 TOWER root: Version: 2016.10.27 Dec 2 13:49:52 TOWER root: Version: 2016.11.27b Dec 2 13:49:52 TOWER root: Version: 2016.10.22 Dec 2 13:49:55 TOWER root: Version: 2016.09.26b Dec 2 13:49:56 TOWER root: Version: 2016.10.22b Dec 2 13:49:56 TOWER root: Version: 1.8.4 Dec 2 13:49:56 TOWER root: # of data including linked data in a cell. This forked version adds Dec 2 13:49:57 TOWER root: # what operating system (and OS version) they are running, what type of Dec 2 13:49:58 TOWER root: plugin: skipping: nmap-6.40-x86_64-1.txz - unRAID version too high, requires at most version 6.1.99 Dec 2 13:49:58 TOWER root: Version: 2016.10.24 Dec 2 13:49:58 TOWER emhttp: unRAID System Management Utility version 6.2.4 Dec 2 13:49:58 TOWER rsyncd[8653]: rsyncd version 3.1.2 starting, listening on port 873 Dec 2 13:49:58 TOWER kernel: md: unRAID driver 2.6.8 installed Dec 2 13:49:58 TOWER kernel: mdcmd (1): import 0 sdf 2930266532 0 WDC_WD30EFRX-68EUZN0_WD-WCC4N0PD894N Dec 2 13:49:58 TOWER kernel: md: import disk0: (sdf) WDC_WD30EFRX-68EUZN0_WD-WCC4N0PD894N size: 2930266532 Dec 2 13:49:58 TOWER kernel: mdcmd (2): import 1 sdc 976762552 0 WDC_WD10EADS-00M2B0_WD-WCAV5P380885 Dec 2 13:49:58 TOWER kernel: md: import disk1: (sdc) WDC_WD10EADS-00M2B0_WD-WCAV5P380885 size: 976762552 Dec 2 13:49:58 TOWER kernel: mdcmd (3): import 2 sdd 1953514552 0 WDC_WD20EZRZ-00Z5HB0_WD-WCC4M6ZN00ZJ Dec 2 13:49:58 TOWER kernel: md: import disk2: (sdd) WDC_WD20EZRZ-00Z5HB0_WD-WCC4M6ZN00ZJ size: 1953514552 Dec 2 13:49:58 TOWER kernel: mdcmd (4): import 3 Dec 2 13:49:58 TOWER kernel: mdcmd (5): import 4 Dec 2 13:49:58 TOWER kernel: mdcmd (6): import 5 Dec 2 13:49:58 TOWER kernel: mdcmd (7): import 6 Dec 2 13:49:58 TOWER kernel: mdcmd (: import 7 Dec 2 13:49:58 TOWER kernel: mdcmd (9): import 8 Dec 2 13:49:58 TOWER kernel: mdcmd (10): import 9 Dec 2 13:49:58 TOWER kernel: mdcmd (11): import 10 Dec 2 13:49:58 TOWER kernel: mdcmd (12): import 11 Dec 2 13:49:58 TOWER kernel: mdcmd (13): import 12 Dec 2 13:49:58 TOWER kernel: mdcmd (14): import 13 Dec 2 13:49:58 TOWER kernel: mdcmd (15): import 14 Dec 2 13:49:58 TOWER kernel: mdcmd (16): import 15 Dec 2 13:49:58 TOWER kernel: mdcmd (17): import 16 Dec 2 13:49:58 TOWER kernel: mdcmd (18): import 17 Dec 2 13:49:58 TOWER kernel: mdcmd (19): import 18 Dec 2 13:49:58 TOWER kernel: mdcmd (20): import 19 Dec 2 13:49:58 TOWER kernel: mdcmd (21): import 20 Dec 2 13:49:58 TOWER kernel: mdcmd (22): import 21 Dec 2 13:49:58 TOWER kernel: mdcmd (23): import 22 Dec 2 13:49:58 TOWER kernel: mdcmd (24): import 23 Dec 2 13:49:58 TOWER kernel: mdcmd (25): import 24 Dec 2 13:49:58 TOWER kernel: mdcmd (26): import 25 Dec 2 13:49:58 TOWER kernel: mdcmd (27): import 26 Dec 2 13:49:58 TOWER kernel: mdcmd (28): import 27 Dec 2 13:49:58 TOWER kernel: mdcmd (29): import 28 Dec 2 13:49:58 TOWER kernel: mdcmd (30): import 29 Dec 2 13:49:58 TOWER kernel: md: import_slot: 29 empty Dec 2 13:49:59 TOWER avahi-daemon[8735]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Dec 2 13:49:59 TOWER kernel: mdcmd (31): set md_num_stripes 1280 Dec 2 13:49:59 TOWER kernel: mdcmd (32): set md_sync_window 384 Dec 2 13:49:59 TOWER kernel: mdcmd (33): set md_sync_thresh 192 Dec 2 13:49:59 TOWER kernel: mdcmd (34): set md_write_method Dec 2 13:49:59 TOWER kernel: mdcmd (35): set spinup_group 0 0 Dec 2 13:49:59 TOWER kernel: mdcmd (36): set spinup_group 1 0 Dec 2 13:49:59 TOWER kernel: mdcmd (37): set spinup_group 2 0 Dec 2 13:49:59 TOWER kernel: mdcmd (38): start STOPPED Dec 2 13:49:59 TOWER kernel: md1: running, size: 976762552 blocks Dec 2 13:49:59 TOWER kernel: md2: running, size: 1953514552 blocks Dec 2 13:50:10 TOWER root: Fix Common Problems Version 2016.10.27 Dec 2 13:50:11 TOWER root: Fix Common Problems: Warning: Share TV Series set to not use the cache, but files / folders exist on the cache drive Dec 2 13:51:02 TOWER kernel: tun: Universal TUN/TAP device driver, 1.6 Dec 2 13:51:02 TOWER dnsmasq[10586]: started, version 2.76 cachesize 150 Dec 2 18:51:49 TOWER kernel: mdcmd (39): spindown 2 Dec 2 18:51:51 TOWER kernel: mdcmd (40): spindown 0 Dec 2 18:51:51 TOWER kernel: mdcmd (41): spindown 1 Dec 3 02:42:06 TOWER kernel: mdcmd (42): spindown 0 Dec 3 03:17:39 TOWER kernel: mdcmd (43): spindown 1 Dec 3 04:00:08 TOWER kernel: mdcmd (44): spindown 2 Dec 3 09:40:15 TOWER kernel: mdcmd (45): spindown 1 Dec 3 09:40:26 TOWER kernel: mdcmd (46): spindown 2 Dec 4 02:05:10 TOWER kernel: mdcmd (47): spindown 1 Dec 4 02:13:11 TOWER kernel: mdcmd (48): spindown 0 Dec 4 07:03:49 TOWER kernel: mdcmd (49): spindown 2 Dec 4 14:05:07 TOWER kernel: mdcmd (50): spindown 1 Dec 5 02:05:33 TOWER kernel: mdcmd (51): spindown 1 Dec 5 02:06:31 TOWER kernel: mdcmd (52): spindown 0 Dec 5 03:20:37 TOWER apcupsd[31431]: Power failure. Dec 5 03:20:39 TOWER apcupsd[31431]: Power is back. UPS running on mains. Dec 5 09:40:30 TOWER kernel: mdcmd (53): spindown 1 Dec 5 14:05:53 TOWER kernel: mdcmd (54): spindown 0 Dec 5 14:05:54 TOWER kernel: mdcmd (55): spindown 2 Dec 6 14:21:35 TOWER kernel: mdcmd (56): spindown 0 Dec 7 03:01:49 TOWER kernel: mdcmd (57): spindown 0 Dec 7 14:07:24 TOWER kernel: mdcmd (58): spindown 0 Dec 7 16:49:16 TOWER kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Dec 7 16:49:16 TOWER kernel: ata2.00: failed command: READ DMA EXT Dec 7 16:49:16 TOWER kernel: ata2.00: error: { UNC } Dec 7 16:49:16 TOWER kernel: blk_update_request: I/O error, dev sdc, sector 648048320 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048256 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048264 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048272 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048280 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048288 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048296 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048304 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048312 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048320 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048328 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048336 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048344 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048352 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048360 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048368 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048376 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048384 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048392 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048400 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048408 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048416 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048424 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048432 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048440 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048448 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048456 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048464 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048472 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048480 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048488 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048496 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048504 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048512 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048520 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048528 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048536 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048544 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048552 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048560 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048568 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048576 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048584 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048592 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048600 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048608 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048616 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048624 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048632 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048640 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048648 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048656 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048664 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048672 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048680 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048688 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048696 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048704 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048712 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048720 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048728 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048736 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048744 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048752 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048760 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048768 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048776 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048784 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048792 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048800 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048808 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048816 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048824 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048832 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048840 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048848 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048856 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048864 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048872 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048880 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048888 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048896 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048904 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048912 Dec 7 16:49:16 TOWER kernel: md: disk1 read error, sector=648048920

Hi again! It's the 3rd time the last six months that I get read errors with one specific disk. I always run scrub and SMART long test which both finish without errors! I am not sure if it's the disk or the cables with the problem. I have attached the smart report below. If you need anything else please let me know. One thing I have learned, is that I will not buy again green drives! It's the second, out of two green drives I own, with problems. smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.4.30-unRAID] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green Device Model: WDC WD10EADS-00M2B0 Serial Number: WD-WCAV5P380885 LU WWN Device Id: 5 0014ee 25ae6ad3c Firmware Version: 01.00A01 User Capacity: 1,000,204,886,016 bytes [1.00 TB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS (minor revision not indicated) SATA Version is: SATA 2.6, 3.0 Gb/s Local Time is: Wed Dec 7 16:51:00 2016 +03 SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x02) Offline data collection activity was completed without error. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (21300) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 245) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3037) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 1701 3 Spin_Up_Time 0x0027 186 183 021 Pre-fail Always - 6683 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1726 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 081 081 000 Old_age Always - 14505 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 1351 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 167 193 Load_Cycle_Count 0x0032 147 147 000 Old_age Always - 161822 194 Temperature_Celsius 0x0022 116 100 000 Old_age Always - 31 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 38 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 14005 - # 2 Extended offline Completed without error 00% 11165 - # 3 Extended offline Completed without error 00% 9348 - # 4 Extended offline Completed without error 00% 9320 - # 5 Short offline Completed without error 00% 9316 - # 6 Extended offline Completed without error 00% 7471 - # 7 Extended offline Completed without error 00% 7237 - # 8 Short offline Completed without error 00% 6575 - # 9 Short offline Aborted by host 90% 6575 - #10 Short offline Completed without error 00% 1666 - #11 Short offline Completed: read failure 90% 1621 1953315312 #12 Short offline Completed: read failure 90% 1621 1953315312 #13 Short offline Completed without error 00% 418 - #14 Short offline Completed without error 00% 0 - 2 of 2 failed self-tests are outdated by newer successful extended offline self-test # 1 SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.

Upgraded from 6.2.1 and got Community Applications corrupted. Uninstalled and reinstalled successfully. Attached diagnostics just in case. Anything I should check? tower-diagnostics-20161023-2135.zip

Did that, opened the exported file with Libre Calc used Find all for folder Photos which is the only one I need, deleted all cells contained that text and nothing remained. One thing that could trigger the problem is that I have folders with Greek characters. I don't know how the plugin works but I thought I should mention just in case!

It just happened again! Both disks appear that build is not up to date!

See bonienl's message two comments ago, should help with exclusions. Just did it and cleared some files. Will get back if I get build-up-to-date = false again

I still get file integrity check for files excluded. I had removed/deleted files and reinstalled the plugin but I can't get it right. Also, very often I get not updated build in disk2 but I have enabled Automatically protect new and modified files: Lastly, I have excluded .tonidodb files but it checked it during scheduled verification check Event: unRAID file corruption Subject: Notice [TOWER] - bunker verify command Description: Found 3 files with BLAKE2 hash key corruption Importance: alert BLAKE2 hash key mismatch, /mnt/disk1/Photos/2003 - 2014 ?????/2008 - 2009 ?????/xxxxxxxxxxxxxxxxx/.tonidodb is corrupted BLAKE2 hash key mismatch, /mnt/disk1/Photos/2003 - 2014 ?????/2012 - 2013 ?????/xxxxxxxxxxxxxxxxxx/.tonidodb is corrupted BLAKE2 hash key mismatch, /mnt/disk1/Photos/2003 - 2014 ?????/2012 ???/xxxxxxxxxxxxxxxxxx/.tonidodb is corrupted BLAKE2 hash key mismatch (updated), /mnt/disk1/TV Series/xxxxxxxxxxxxxxxxx/xxxxxxxxxxxx - S01E10 - xxxxxxHDTV-1080p.nfo was modified Pics https://www.dropbox.com/sh/9jb8b7yb79fkjsk/AACE1EA6A9ltaHSagcIVm1dPa?dl=0 Any ideas?

With the latest 6.2.1 update I remembered this topic from yesterday... With more frequent updates we will get more writes and less life expectancy Of course, I prefer the more frequent updates than then €5 for a usb stick every >5 years