Masalajam

I may have stumbled into the answer. Its the way OS X calculated 'Items' in a view. If I have a folder in "List' view, and click the triangle to reveal the contents of the folder, it includes the count of the items within that folders as 'items' in the view. So if I have 1 folder in the view and it's closed, OS X reports 1 item. If however, I click the triangle and reveal the contents of the folder (.nfo, *.jpg) OS X counts the 2 files in that folders as items, and tells me I have 3 items. This looks to be the case, perhaps your problem is similar.

Something very wrong here. After starting AFP, the SMB share is showing 1379 folders, but the AFP view of the the same share is showing 1183 folders. Going to reboot everything to see if that makes any difference.

I have'nt tried AFP to see if that makes a difference. Will try that and a few other things to see if I can diagnose the problem. thanks

Very unusual problem I have with Unraid 6.1.9 and OS X 10.11.6. The finder view lists 1180 folders, Path Finder list 1181 folders, Windows 10 lists 1374 folders, OS 10.7.5 lists 1374 folders. Has anyone else run into this problem? Is a bug in OS X10.11.6? All ideas appreciated. Thanks

So is the drive order irrelevant? I can plug the existing drives in any order into the new server, and Unraid will detect which drive is Parity and what drives are Data? Thanks.

Thanks!

I have an old Unraid 6 server (built sometime in 2010) that is failing. Rather than spend anymore time diagnosing the server, I'm just going to cannibalize the case and power supply, and build something new. I'd like to move the disks from the old server into the new machine. What is the best procedure for moving drives with existing data on them to a new build. The new build will have a 4TB parity so that I can add larger drives in the future. Do I just move all the drives over to the new server without a parity drive, and assign the new drives as data? Do I then add the new 4TB drive as a parity drive? The Unraid 6 manual is not very helpful here. Thanks.

I replaced both memory sticks (since I already had case open) and ran the memtest for 12 hours. No errors on the new memory. I'm repairing the file system now. Thanks

I attached a monitor, and booted up in safe mode. The system reported corruption on one of the disk. I immediately took the array offline. Since this is an older drive, I'd rather just replace it the drive than try to repair and recover files. From my understanding of how UnRaid works, I should be able to simply: 1 - Remove the corrupted drive 2- restart the array 3 - Unraid will see that there is a new drive, and rebuild the contents of the drive from parity drive Is that correct? Is there any benefit to trying to repair the drive. Still not sure if this is why the entire system was crashing and becoming unresposnsive, but all the suggestions have been helpful Thanks log follows ===================== Feb 5 06:44:50 Tower emhttp: shcmd (190): udevadm settle Feb 5 06:44:50 Tower emhttp: Hitachi_HDS721010CLA332_JP2921HQ200Z2A (sda) 976762584 Feb 5 06:44:50 Tower emhttp: ST2000DL003-9VT166_5YD781ZC (sdb) 1953514584 Feb 5 06:44:50 Tower emhttp: SAMSUNG_HD203WI_S1UYJ1CZ405241 (sdc) 1953514584 Feb 5 06:44:50 Tower emhttp: Hitachi_HDS721010CLA332_JP2921HQ1WWNWA (sdd) 976762584 Feb 5 06:44:50 Tower emhttp: TOSHIBA_DT01ACA200_23JESDVXS (sde) 1953514584 Feb 5 06:44:50 Tower emhttp: array slots: 24 Feb 5 06:44:50 Tower emhttp: cache slots: 1 Feb 5 06:44:50 Tower kernel: mdcmd (1): import 0 8,16 1953514552 ST2000DL003-9VT166_5YD781ZC Feb 5 06:44:50 Tower kernel: md: import disk0: [8,16] (sdb) ST2000DL003-9VT166_5YD781ZC size: 1953514552 Feb 5 06:44:50 Tower kernel: mdcmd (2): import 1 8,0 976762552 Hitachi_HDS721010CLA332_JP2921HQ200Z2A Feb 5 06:44:50 Tower kernel: md: import disk1: [8,0] (sda) Hitachi_HDS721010CLA332_JP2921HQ200Z2A size: 976762552 Feb 5 06:44:50 Tower kernel: mdcmd (3): import 2 8,32 1953514552 SAMSUNG_HD203WI_S1UYJ1CZ405241 Feb 5 06:44:50 Tower kernel: md: import disk2: [8,32] (sdc) SAMSUNG_HD203WI_S1UYJ1CZ405241 size: 1953514552 Feb 5 06:44:50 Tower kernel: mdcmd (4): import 3 8,48 976762552 Hitachi_HDS721010CLA332_JP2921HQ1WWNWA Feb 5 06:44:50 Tower kernel: md: import disk3: [8,48] (sdd) Hitachi_HDS721010CLA332_JP2921HQ1WWNWA size: 976762552 Feb 5 06:44:50 Tower kernel: mdcmd (5): import 4 8,64 1953514552 TOSHIBA_DT01ACA200_23JESDVXS Feb 5 06:44:50 Tower kernel: md: import disk4: [8,64] (sde) TOSHIBA_DT01ACA200_23JESDVXS size: 1953514552 Feb 5 06:44:50 Tower kernel: mdcmd (6): import 5 0,0 Feb 5 06:44:50 Tower kernel: mdcmd (7): import 6 0,0 Feb 5 06:44:50 Tower kernel: mdcmd (: import 7 0,0 Feb 5 06:44:50 Tower kernel: mdcmd (9): import 8 0,0 Feb 5 06:44:50 Tower kernel: mdcmd (10): import 9 0,0 Feb 5 06:44:50 Tower kernel: mdcmd (11): import 10 0,0 Feb 5 06:44:50 Tower kernel: mdcmd (12): import 11 0,0 Feb 5 06:44:50 Tower kernel: mdcmd (13): import 12 0,0 Feb 5 06:44:50 Tower kernel: mdcmd (14): import 13 0,0 Feb 5 06:44:50 Tower kernel: mdcmd (15): import 14 0,0 Feb 5 06:44:50 Tower kernel: mdcmd (16): import 15 0,0 Feb 5 06:44:50 Tower kernel: mdcmd (17): import 16 0,0 Feb 5 06:44:50 Tower kernel: mdcmd (18): import 17 0,0 Feb 5 06:44:50 Tower kernel: mdcmd (19): import 18 0,0 Feb 5 06:44:50 Tower kernel: mdcmd (20): import 19 0,0 Feb 5 06:44:50 Tower kernel: mdcmd (21): import 20 0,0 Feb 5 06:44:50 Tower kernel: mdcmd (22): import 21 0,0 Feb 5 06:44:50 Tower kernel: mdcmd (23): import 22 0,0 Feb 5 06:44:50 Tower kernel: mdcmd (24): import 23 0,0 Feb 5 06:44:50 Tower emhttp: import 24 cache device: no device Feb 5 06:44:50 Tower emhttp: import flash device: sdf Feb 5 06:45:35 Tower emhttp: shcmd (191): rmmod md-mod |& logger Feb 5 06:45:35 Tower kernel: md: unRAID driver removed Feb 5 06:45:35 Tower emhttp: shcmd (192): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger Feb 5 06:45:35 Tower kernel: md: unRAID driver 2.5.3 installed Feb 5 06:45:35 Tower emhttp: get_message: /boot/config/._Plus.key (-4) Feb 5 06:45:35 Tower emhttp: Plus key detected, GUID: 05DC-C75D-7F00-57D7425C7A68 FILE: /boot/config/Plus.key Feb 5 06:45:35 Tower emhttp: Device inventory: Feb 5 06:45:35 Tower emhttp: shcmd (193): udevadm settle Feb 5 06:45:35 Tower emhttp: Hitachi_HDS721010CLA332_JP2921HQ200Z2A (sda) 976762584 Feb 5 06:45:35 Tower emhttp: ST2000DL003-9VT166_5YD781ZC (sdb) 1953514584 Feb 5 06:45:35 Tower emhttp: SAMSUNG_HD203WI_S1UYJ1CZ405241 (sdc) 1953514584 Feb 5 06:45:35 Tower emhttp: Hitachi_HDS721010CLA332_JP2921HQ1WWNWA (sdd) 976762584 Feb 5 06:45:35 Tower emhttp: TOSHIBA_DT01ACA200_23JESDVXS (sde) 1953514584 Feb 5 06:45:35 Tower emhttp: array slots: 24 Feb 5 06:45:35 Tower emhttp: cache slots: 1 Feb 5 06:45:35 Tower kernel: mdcmd (1): import 0 8,16 1953514552 ST2000DL003-9VT166_5YD781ZC Feb 5 06:45:35 Tower kernel: md: import disk0: [8,16] (sdb) ST2000DL003-9VT166_5YD781ZC size: 1953514552 Feb 5 06:45:35 Tower kernel: mdcmd (2): import 1 8,0 976762552 Hitachi_HDS721010CLA332_JP2921HQ200Z2A Feb 5 06:45:35 Tower kernel: md: import disk1: [8,0] (sda) Hitachi_HDS721010CLA332_JP2921HQ200Z2A size: 976762552 Feb 5 06:45:35 Tower kernel: mdcmd (3): import 2 8,32 1953514552 SAMSUNG_HD203WI_S1UYJ1CZ405241 Feb 5 06:45:35 Tower kernel: md: import disk2: [8,32] (sdc) SAMSUNG_HD203WI_S1UYJ1CZ405241 size: 1953514552 Feb 5 06:45:35 Tower kernel: mdcmd (4): import 3 8,48 976762552 Hitachi_HDS721010CLA332_JP2921HQ1WWNWA Feb 5 06:45:35 Tower kernel: md: import disk3: [8,48] (sdd) Hitachi_HDS721010CLA332_JP2921HQ1WWNWA size: 976762552 Feb 5 06:45:35 Tower emhttp: import 24 cache device: no device Feb 5 06:45:35 Tower kernel: mdcmd (5): import 4 8,64 1953514552 TOSHIBA_DT01ACA200_23JESDVXS Feb 5 06:45:35 Tower kernel: md: import disk4: [8,64] (sde) TOSHIBA_DT01ACA200_23JESDVXS size: 1953514552 Feb 5 06:45:35 Tower kernel: mdcmd (6): import 5 0,0 Feb 5 06:45:35 Tower kernel: mdcmd (7): import 6 0,0 Feb 5 06:45:35 Tower kernel: mdcmd (: import 7 0,0 Feb 5 06:45:35 Tower kernel: mdcmd (9): import 8 0,0 Feb 5 06:45:35 Tower kernel: mdcmd (10): import 9 0,0 Feb 5 06:45:35 Tower kernel: mdcmd (11): import 10 0,0 Feb 5 06:45:35 Tower kernel: mdcmd (12): import 11 0,0 Feb 5 06:45:35 Tower kernel: mdcmd (13): import 12 0,0 Feb 5 06:45:35 Tower kernel: mdcmd (14): import 13 0,0 Feb 5 06:45:35 Tower kernel: mdcmd (15): import 14 0,0 Feb 5 06:45:35 Tower kernel: mdcmd (16): import 15 0,0 Feb 5 06:45:35 Tower kernel: mdcmd (17): import 16 0,0 Feb 5 06:45:35 Tower kernel: mdcmd (18): import 17 0,0 Feb 5 06:45:35 Tower kernel: mdcmd (19): import 18 0,0 Feb 5 06:45:35 Tower kernel: mdcmd (20): import 19 0,0 Feb 5 06:45:35 Tower kernel: mdcmd (21): import 20 0,0 Feb 5 06:45:35 Tower kernel: mdcmd (22): import 21 0,0 Feb 5 06:45:35 Tower kernel: mdcmd (23): import 22 0,0 Feb 5 06:45:35 Tower kernel: mdcmd (24): import 23 0,0 Feb 5 06:45:35 Tower emhttp: import flash device: sdf Feb 5 06:45:41 Tower emhttp: shcmd (194): rmmod md-mod |& logger Feb 5 06:45:41 Tower kernel: md: unRAID driver removed Feb 5 06:45:41 Tower emhttp: shcmd (195): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger Feb 5 06:45:41 Tower kernel: md: unRAID driver 2.5.3 installed Feb 5 06:45:41 Tower emhttp: get_message: /boot/config/._Plus.key (-4) Feb 5 06:45:41 Tower emhttp: Plus key detected, GUID: 05DC-C75D-7F00-57D7425C7A68 FILE: /boot/config/Plus.key Feb 5 06:45:41 Tower emhttp: Device inventory: Feb 5 06:45:41 Tower emhttp: shcmd (196): udevadm settle Feb 5 06:45:41 Tower emhttp: Hitachi_HDS721010CLA332_JP2921HQ200Z2A (sda) 976762584 Feb 5 06:45:41 Tower emhttp: ST2000DL003-9VT166_5YD781ZC (sdb) 1953514584 Feb 5 06:45:41 Tower emhttp: SAMSUNG_HD203WI_S1UYJ1CZ405241 (sdc) 1953514584 Feb 5 06:45:41 Tower emhttp: Hitachi_HDS721010CLA332_JP2921HQ1WWNWA (sdd) 976762584 Feb 5 06:45:41 Tower emhttp: TOSHIBA_DT01ACA200_23JESDVXS (sde) 1953514584 Feb 5 06:45:41 Tower emhttp: array slots: 24 Feb 5 06:45:41 Tower emhttp: cache slots: 1 Feb 5 06:45:41 Tower kernel: mdcmd (1): import 0 8,16 1953514552 ST2000DL003-9VT166_5YD781ZC Feb 5 06:45:41 Tower kernel: md: import disk0: [8,16] (sdb) ST2000DL003-9VT166_5YD781ZC size: 1953514552 Feb 5 06:45:41 Tower kernel: mdcmd (2): import 1 8,0 976762552 Hitachi_HDS721010CLA332_JP2921HQ200Z2A Feb 5 06:45:41 Tower kernel: md: import disk1: [8,0] (sda) Hitachi_HDS721010CLA332_JP2921HQ200Z2A size: 976762552 Feb 5 06:45:41 Tower kernel: mdcmd (3): import 2 8,32 1953514552 SAMSUNG_HD203WI_S1UYJ1CZ405241 Feb 5 06:45:41 Tower kernel: md: import disk2: [8,32] (sdc) SAMSUNG_HD203WI_S1UYJ1CZ405241 size: 1953514552 Feb 5 06:45:41 Tower kernel: mdcmd (4): import 3 8,48 976762552 Hitachi_HDS721010CLA332_JP2921HQ1WWNWA Feb 5 06:45:41 Tower kernel: md: import disk3: [8,48] (sdd) Hitachi_HDS721010CLA332_JP2921HQ1WWNWA size: 976762552 Feb 5 06:45:41 Tower kernel: mdcmd (5): import 4 8,64 1953514552 TOSHIBA_DT01ACA200_23JESDVXS Feb 5 06:45:41 Tower kernel: md: import disk4: [8,64] (sde) TOSHIBA_DT01ACA200_23JESDVXS size: 1953514552 Feb 5 06:45:41 Tower kernel: mdcmd (6): import 5 0,0 Feb 5 06:45:41 Tower kernel: mdcmd (7): import 6 0,0 Feb 5 06:45:41 Tower kernel: mdcmd (: import 7 0,0 Feb 5 06:45:41 Tower kernel: mdcmd (9): import 8 0,0 Feb 5 06:45:41 Tower kernel: mdcmd (10): import 9 0,0 Feb 5 06:45:41 Tower kernel: mdcmd (11): import 10 0,0 Feb 5 06:45:41 Tower kernel: mdcmd (12): import 11 0,0 Feb 5 06:45:41 Tower kernel: mdcmd (13): import 12 0,0 Feb 5 06:45:41 Tower kernel: mdcmd (14): import 13 0,0 Feb 5 06:45:41 Tower kernel: mdcmd (15): import 14 0,0 Feb 5 06:45:41 Tower kernel: mdcmd (16): import 15 0,0 Feb 5 06:45:41 Tower kernel: mdcmd (17): import 16 0,0 Feb 5 06:45:41 Tower kernel: mdcmd (18): import 17 0,0 Feb 5 06:45:41 Tower kernel: mdcmd (19): import 18 0,0 Feb 5 06:45:41 Tower kernel: mdcmd (20): import 19 0,0 Feb 5 06:45:41 Tower kernel: mdcmd (21): import 20 0,0 Feb 5 06:45:41 Tower kernel: mdcmd (22): import 21 0,0 Feb 5 06:45:41 Tower kernel: mdcmd (23): import 22 0,0 Feb 5 06:45:41 Tower kernel: mdcmd (24): import 23 0,0 Feb 5 06:45:41 Tower emhttp: import 24 cache device: no device Feb 5 06:45:41 Tower emhttp: import flash device: sdf Feb 5 06:45:55 Tower emhttp: shcmd (197): rmmod md-mod |& logger Feb 5 06:45:55 Tower kernel: md: unRAID driver removed Feb 5 06:45:55 Tower emhttp: shcmd (198): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger Feb 5 06:45:55 Tower kernel: md: unRAID driver 2.5.3 installed Feb 5 06:45:55 Tower emhttp: get_message: /boot/config/._Plus.key (-4) Feb 5 06:45:55 Tower emhttp: Plus key detected, GUID: 05DC-C75D-7F00-57D7425C7A68 FILE: /boot/config/Plus.key Feb 5 06:45:55 Tower emhttp: Device inventory: Feb 5 06:45:55 Tower emhttp: shcmd (199): udevadm settle Feb 5 06:45:55 Tower emhttp: Hitachi_HDS721010CLA332_JP2921HQ200Z2A (sda) 976762584 Feb 5 06:45:55 Tower emhttp: ST2000DL003-9VT166_5YD781ZC (sdb) 1953514584 Feb 5 06:45:55 Tower emhttp: SAMSUNG_HD203WI_S1UYJ1CZ405241 (sdc) 1953514584 Feb 5 06:45:55 Tower emhttp: Hitachi_HDS721010CLA332_JP2921HQ1WWNWA (sdd) 976762584 Feb 5 06:45:55 Tower emhttp: TOSHIBA_DT01ACA200_23JESDVXS (sde) 1953514584 Feb 5 06:45:55 Tower emhttp: array slots: 24 Feb 5 06:45:55 Tower emhttp: cache slots: 1 Feb 5 06:45:55 Tower kernel: mdcmd (1): import 0 8,16 1953514552 ST2000DL003-9VT166_5YD781ZC Feb 5 06:45:55 Tower kernel: md: import disk0: [8,16] (sdb) ST2000DL003-9VT166_5YD781ZC size: 1953514552 Feb 5 06:45:55 Tower kernel: mdcmd (2): import 1 8,0 976762552 Hitachi_HDS721010CLA332_JP2921HQ200Z2A Feb 5 06:45:55 Tower kernel: md: import disk1: [8,0] (sda) Hitachi_HDS721010CLA332_JP2921HQ200Z2A size: 976762552 Feb 5 06:45:55 Tower kernel: mdcmd (3): import 2 8,32 1953514552 SAMSUNG_HD203WI_S1UYJ1CZ405241 Feb 5 06:45:55 Tower kernel: md: import disk2: [8,32] (sdc) SAMSUNG_HD203WI_S1UYJ1CZ405241 size: 1953514552 Feb 5 06:45:55 Tower kernel: mdcmd (4): import 3 8,48 976762552 Hitachi_HDS721010CLA332_JP2921HQ1WWNWA Feb 5 06:45:55 Tower kernel: md: import disk3: [8,48] (sdd) Hitachi_HDS721010CLA332_JP2921HQ1WWNWA size: 976762552 Feb 5 06:45:55 Tower kernel: mdcmd (5): import 4 8,64 1953514552 TOSHIBA_DT01ACA200_23JESDVXS Feb 5 06:45:55 Tower kernel: md: import disk4: [8,64] (sde) TOSHIBA_DT01ACA200_23JESDVXS size: 1953514552 Feb 5 06:45:55 Tower kernel: mdcmd (6): import 5 0,0 Feb 5 06:45:55 Tower kernel: mdcmd (7): import 6 0,0 Feb 5 06:45:55 Tower kernel: mdcmd (: import 7 0,0 Feb 5 06:45:55 Tower kernel: mdcmd (9): import 8 0,0 Feb 5 06:45:55 Tower kernel: mdcmd (10): import 9 0,0 Feb 5 06:45:55 Tower kernel: mdcmd (11): import 10 0,0 Feb 5 06:45:55 Tower kernel: mdcmd (12): import 11 0,0 Feb 5 06:45:55 Tower kernel: mdcmd (13): import 12 0,0 Feb 5 06:45:55 Tower kernel: mdcmd (14): import 13 0,0 Feb 5 06:45:55 Tower kernel: mdcmd (15): import 14 0,0 Feb 5 06:45:55 Tower kernel: mdcmd (16): import 15 0,0 Feb 5 06:45:55 Tower kernel: mdcmd (17): import 16 0,0 Feb 5 06:45:55 Tower kernel: mdcmd (18): import 17 0,0 Feb 5 06:45:55 Tower kernel: mdcmd (19): import 18 0,0 Feb 5 06:45:55 Tower kernel: mdcmd (20): import 19 0,0 Feb 5 06:45:55 Tower kernel: mdcmd (21): import 20 0,0 Feb 5 06:45:55 Tower kernel: mdcmd (22): import 21 0,0 Feb 5 06:45:55 Tower kernel: mdcmd (23): import 22 0,0 Feb 5 06:45:55 Tower kernel: mdcmd (24): import 23 0,0 Feb 5 06:45:55 Tower emhttp: import 24 cache device: no device Feb 5 06:45:55 Tower emhttp: import flash device: sdf Feb 5 06:45:58 Tower emhttp: shcmd (200): rmmod md-mod |& logger Feb 5 06:45:58 Tower kernel: md: unRAID driver removed Feb 5 06:45:58 Tower emhttp: shcmd (201): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger Feb 5 06:45:58 Tower kernel: md: unRAID driver 2.5.3 installed Feb 5 06:45:58 Tower emhttp: get_message: /boot/config/._Plus.key (-4) Feb 5 06:45:58 Tower emhttp: Plus key detected, GUID: 05DC-C75D-7F00-57D7425C7A68 FILE: /boot/config/Plus.key Feb 5 06:45:58 Tower emhttp: Device inventory: Feb 5 06:45:58 Tower emhttp: shcmd (202): udevadm settle Feb 5 06:45:58 Tower emhttp: Hitachi_HDS721010CLA332_JP2921HQ200Z2A (sda) 976762584 Feb 5 06:45:58 Tower emhttp: ST2000DL003-9VT166_5YD781ZC (sdb) 1953514584 Feb 5 06:45:58 Tower emhttp: SAMSUNG_HD203WI_S1UYJ1CZ405241 (sdc) 1953514584 Feb 5 06:45:58 Tower emhttp: Hitachi_HDS721010CLA332_JP2921HQ1WWNWA (sdd) 976762584 Feb 5 06:45:58 Tower emhttp: TOSHIBA_DT01ACA200_23JESDVXS (sde) 1953514584 Feb 5 06:45:58 Tower emhttp: array slots: 24 Feb 5 06:45:58 Tower emhttp: cache slots: 1 Feb 5 06:45:58 Tower kernel: mdcmd (1): import 0 8,16 1953514552 ST2000DL003-9VT166_5YD781ZC Feb 5 06:45:58 Tower kernel: md: import disk0: [8,16] (sdb) ST2000DL003-9VT166_5YD781ZC size: 1953514552 Feb 5 06:45:58 Tower kernel: mdcmd (2): import 1 8,0 976762552 Hitachi_HDS721010CLA332_JP2921HQ200Z2A Feb 5 06:45:58 Tower kernel: md: import disk1: [8,0] (sda) Hitachi_HDS721010CLA332_JP2921HQ200Z2A size: 976762552 Feb 5 06:45:58 Tower kernel: mdcmd (3): import 2 8,32 1953514552 SAMSUNG_HD203WI_S1UYJ1CZ405241 Feb 5 06:45:58 Tower kernel: md: import disk2: [8,32] (sdc) SAMSUNG_HD203WI_S1UYJ1CZ405241 size: 1953514552 Feb 5 06:45:58 Tower kernel: mdcmd (4): import 3 8,48 976762552 Hitachi_HDS721010CLA332_JP2921HQ1WWNWA Feb 5 06:45:58 Tower kernel: md: import disk3: [8,48] (sdd) Hitachi_HDS721010CLA332_JP2921HQ1WWNWA size: 976762552 Feb 5 06:45:58 Tower kernel: mdcmd (5): import 4 8,64 1953514552 TOSHIBA_DT01ACA200_23JESDVXS Feb 5 06:45:58 Tower kernel: md: import disk4: [8,64] (sde) TOSHIBA_DT01ACA200_23JESDVXS size: 1953514552 Feb 5 06:45:58 Tower kernel: mdcmd (6): import 5 0,0 Feb 5 06:45:58 Tower kernel: mdcmd (7): import 6 0,0 Feb 5 06:45:58 Tower kernel: mdcmd (: import 7 0,0 Feb 5 06:45:58 Tower kernel: mdcmd (9): import 8 0,0 Feb 5 06:45:58 Tower kernel: mdcmd (10): import 9 0,0 Feb 5 06:45:58 Tower kernel: mdcmd (11): import 10 0,0 Feb 5 06:45:58 Tower kernel: mdcmd (12): import 11 0,0 Feb 5 06:45:58 Tower kernel: mdcmd (13): import 12 0,0 Feb 5 06:45:58 Tower kernel: mdcmd (14): import 13 0,0 Feb 5 06:45:58 Tower kernel: mdcmd (15): import 14 0,0 Feb 5 06:45:58 Tower kernel: mdcmd (16): import 15 0,0 Feb 5 06:45:58 Tower kernel: mdcmd (17): import 16 0,0 Feb 5 06:45:58 Tower kernel: mdcmd (18): import 17 0,0 Feb 5 06:45:58 Tower kernel: mdcmd (19): import 18 0,0 Feb 5 06:45:58 Tower kernel: mdcmd (20): import 19 0,0 Feb 5 06:45:58 Tower kernel: mdcmd (21): import 20 0,0 Feb 5 06:45:58 Tower kernel: mdcmd (22): import 21 0,0 Feb 5 06:45:58 Tower kernel: mdcmd (23): import 22 0,0 Feb 5 06:45:58 Tower kernel: mdcmd (24): import 23 0,0 Feb 5 06:45:58 Tower emhttp: import 24 cache device: no device Feb 5 06:45:58 Tower emhttp: import flash device: sdf Feb 5 06:45:59 Tower emhttp: shcmd (203): rmmod md-mod |& logger Feb 5 06:45:59 Tower kernel: md: unRAID driver removed Feb 5 06:45:59 Tower emhttp: shcmd (204): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger Feb 5 06:45:59 Tower kernel: md: unRAID driver 2.5.3 installed Feb 5 06:45:59 Tower emhttp: get_message: /boot/config/._Plus.key (-4) Feb 5 06:45:59 Tower emhttp: Plus key detected, GUID: 05DC-C75D-7F00-57D7425C7A68 FILE: /boot/config/Plus.key Feb 5 06:45:59 Tower emhttp: Device inventory: Feb 5 06:45:59 Tower emhttp: shcmd (205): udevadm settle Feb 5 06:45:59 Tower emhttp: Hitachi_HDS721010CLA332_JP2921HQ200Z2A (sda) 976762584 Feb 5 06:45:59 Tower emhttp: ST2000DL003-9VT166_5YD781ZC (sdb) 1953514584 Feb 5 06:45:59 Tower emhttp: SAMSUNG_HD203WI_S1UYJ1CZ405241 (sdc) 1953514584 Feb 5 06:45:59 Tower emhttp: Hitachi_HDS721010CLA332_JP2921HQ1WWNWA (sdd) 976762584 Feb 5 06:45:59 Tower emhttp: TOSHIBA_DT01ACA200_23JESDVXS (sde) 1953514584 Feb 5 06:45:59 Tower emhttp: array slots: 24 Feb 5 06:45:59 Tower emhttp: cache slots: 1 Feb 5 06:45:59 Tower kernel: mdcmd (1): import 0 8,16 1953514552 ST2000DL003-9VT166_5YD781ZC Feb 5 06:45:59 Tower kernel: md: import disk0: [8,16] (sdb) ST2000DL003-9VT166_5YD781ZC size: 1953514552 Feb 5 06:45:59 Tower kernel: mdcmd (2): import 1 8,0 976762552 Hitachi_HDS721010CLA332_JP2921HQ200Z2A Feb 5 06:45:59 Tower kernel: md: import disk1: [8,0] (sda) Hitachi_HDS721010CLA332_JP2921HQ200Z2A size: 976762552 Feb 5 06:45:59 Tower kernel: mdcmd (3): import 2 8,32 1953514552 SAMSUNG_HD203WI_S1UYJ1CZ405241 Feb 5 06:45:59 Tower kernel: md: import disk2: [8,32] (sdc) SAMSUNG_HD203WI_S1UYJ1CZ405241 size: 1953514552 Feb 5 06:45:59 Tower kernel: mdcmd (4): import 3 8,48 976762552 Hitachi_HDS721010CLA332_JP2921HQ1WWNWA Feb 5 06:45:59 Tower kernel: md: import disk3: [8,48] (sdd) Hitachi_HDS721010CLA332_JP2921HQ1WWNWA size: 976762552 Feb 5 06:45:59 Tower kernel: mdcmd (5): import 4 8,64 1953514552 TOSHIBA_DT01ACA200_23JESDVXS Feb 5 06:45:59 Tower kernel: md: import disk4: [8,64] (sde) TOSHIBA_DT01ACA200_23JESDVXS size: 1953514552 Feb 5 06:45:59 Tower kernel: mdcmd (6): import 5 0,0 Feb 5 06:45:59 Tower kernel: mdcmd (7): import 6 0,0 Feb 5 06:45:59 Tower kernel: mdcmd (: import 7 0,0 Feb 5 06:45:59 Tower kernel: mdcmd (9): import 8 0,0 Feb 5 06:45:59 Tower kernel: mdcmd (10): import 9 0,0 Feb 5 06:45:59 Tower kernel: mdcmd (11): import 10 0,0 Feb 5 06:45:59 Tower kernel: mdcmd (12): import 11 0,0 Feb 5 06:45:59 Tower kernel: mdcmd (13): import 12 0,0 Feb 5 06:45:59 Tower kernel: mdcmd (14): import 13 0,0 Feb 5 06:45:59 Tower kernel: mdcmd (15): import 14 0,0 Feb 5 06:45:59 Tower kernel: mdcmd (16): import 15 0,0 Feb 5 06:45:59 Tower kernel: mdcmd (17): import 16 0,0 Feb 5 06:45:59 Tower kernel: mdcmd (18): import 17 0,0 Feb 5 06:45:59 Tower kernel: mdcmd (19): import 18 0,0 Feb 5 06:45:59 Tower kernel: mdcmd (20): import 19 0,0 Feb 5 06:45:59 Tower kernel: mdcmd (21): import 20 0,0 Feb 5 06:45:59 Tower kernel: mdcmd (22): import 21 0,0 Feb 5 06:45:59 Tower kernel: mdcmd (23): import 22 0,0 Feb 5 06:45:59 Tower kernel: mdcmd (24): import 23 0,0 Feb 5 06:45:59 Tower emhttp: import 24 cache device: no device Feb 5 06:45:59 Tower emhttp: import flash device: sdf tower-diagnostics-20160205-0646.zip

Honestly, I don't know. The server is running without a monitor. It does not reboot, that has to be done manually, nor is the computer shut down. The server management page becomes unresponsive, and the network share drops off the network. The power has to be shut off/on before it can be rebooted. Thinking about this more systematically, the computer requires two hard power cycles to boot back up from the USB flash drive. Perhaps the power supply is bad? I frankly have no idea. Thanks for replying.

Hello, Over the last 3 days, my server (Ver 6.1.7) has crashed 3 times and uptime is now about 24 hours before it crashes. SMART status on all disks including Parity is green, which I assume means they're good. This is an older server built about 2011, and has been working fine for years. I am unsure if the USB Flash drive is bad, if the motherboard is bad, or generally what else could be dying. Have not been able to find anything in the forums that would address diagnosing an old server. Attached is the latest SYSLOG and the diagnostics file. Any help is appreciated. Thanks, Jan 28 16:04:50 Tower avahi-daemon[5366]: Successfully called chroot(). Jan 28 16:04:50 Tower avahi-daemon[5366]: Successfully dropped remaining capabilities. Jan 28 16:04:50 Tower avahi-daemon[5366]: Loading service file /services/sftp-ssh.service. Jan 28 16:04:50 Tower avahi-daemon[5366]: Loading service file /services/smb.service. Jan 28 16:04:50 Tower avahi-daemon[5366]: Loading service file /services/ssh.service. Jan 28 16:04:50 Tower avahi-daemon[5366]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.2.67. Jan 28 16:04:50 Tower avahi-daemon[5366]: New relevant interface eth0.IPv4 for mDNS. Jan 28 16:04:50 Tower avahi-daemon[5366]: Network interface enumeration completed. Jan 28 16:04:50 Tower avahi-daemon[5366]: Registering new address record for 192.168.2.67 on eth0.IPv4. Jan 28 16:04:50 Tower avahi-daemon[5366]: Registering HINFO record with values 'X86_64'/'LINUX'. Jan 28 16:04:50 Tower emhttp: shcmd (38): /etc/rc.d/rc.avahidnsconfd start |& logger Jan 28 16:04:50 Tower logger: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D Jan 28 16:04:50 Tower avahi-dnsconfd[5375]: Successfully connected to Avahi daemon. Jan 28 16:04:50 Tower emhttp: Starting Docker... Jan 28 16:04:50 Tower logger: Not starting Docker: no image file defined Jan 28 16:04:51 Tower avahi-daemon[5366]: Server startup complete. Host name is Tower.local. Local service cookie is 3954287376. Jan 28 16:04:52 Tower avahi-daemon[5366]: Service "Tower" (/services/ssh.service) successfully established. Jan 28 16:04:52 Tower avahi-daemon[5366]: Service "Tower" (/services/smb.service) successfully established. Jan 28 16:04:52 Tower avahi-daemon[5366]: Service "Tower" (/services/sftp-ssh.service) successfully established. Jan 28 16:06:28 Tower kernel: mdcmd (40): spinup 0 Jan 28 16:06:28 Tower kernel: mdcmd (41): spinup 1 Jan 28 16:06:28 Tower kernel: mdcmd (42): spinup 2 Jan 28 16:06:28 Tower kernel: mdcmd (43): spinup 3 Jan 28 16:06:28 Tower kernel: mdcmd (44): spinup 4 Jan 28 16:06:28 Tower emhttp: Spinning up all drives... Jan 28 16:06:47 Tower emhttp: shcmd (39): :>/etc/samba/smb-shares.conf Jan 28 16:06:47 Tower emhttp: shcmd (40): cp /etc/exports- /etc/exports Jan 28 16:06:47 Tower avahi-daemon[5366]: Files changed, reloading. Jan 28 16:06:47 Tower emhttp: Restart SMB... Jan 28 16:06:47 Tower emhttp: shcmd (41): killall -HUP smbd Jan 28 16:06:47 Tower emhttp: shcmd (42): smbcontrol smbd close-share 'flash' Jan 28 16:06:47 Tower emhttp: shcmd (43): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service Jan 28 16:06:47 Tower avahi-daemon[5366]: Files changed, reloading. Jan 28 16:06:47 Tower avahi-daemon[5366]: Service group file /services/smb.service changed, reloading. Jan 28 16:06:47 Tower emhttp: shcmd (44): pidof rpc.mountd &> /dev/null Jan 28 16:06:47 Tower emhttp: Start NFS... Jan 28 16:06:47 Tower emhttp: shcmd (45): /etc/rc.d/rc.nfsd start |& logger Jan 28 16:06:47 Tower emhttp: shcmd (46): /etc/rc.d/rc.atalk status Jan 28 16:06:48 Tower avahi-daemon[5366]: Service "Tower" (/services/smb.service) successfully established. tower-diagnostics-20160128-1640.zip

Nothing. Literally nothing. I'll enter the URL of the remote plugin file, click install, and nothing happens. Nothing gets written to the plugin directory. There's also an error message: "Warning: file_get_contents(/boot/syslinux/syslinux.cfg): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(275) : eval()'d code on line 21" I've attached the log below. Thanks Log_Information.txt

Hey, Thanks. I'll try that tonight. I'm curious why it doesn't work. I also can't install plugins on that machine, even though my other unraid installation is working just fine.

Is there a manual way to upgrade from V6b14? The update button on the plugin serve page does not indicate an update is available. Interestingly enough, this fails to work on only 1 of my 2 unraid systems. My other system upgraded just fine. Thanks

(1) Have you rebooted the router as well? I had a Linksys router that had to be rebooted 1X per week. If it was not rebooted, I would not be able to see the Shares on my WDTV Live, even though I could see the Unraid server under network shares. (2) It could be a problem with the WDTVs as well. We have multiple WDTV and a WDTV Live Hub, and they all need to be occasionally rebooted to see the shares on my unraid server. I've always assumed this to be a WDTV problem.

I experienced this yesterday on a mac mini (os x 10.7.5) writing to Unraid 4.7 Plus. I copied a directory full of mp4 files, nested each in a sub-directory. About 200 gb total. After the copy was supposed to be finished, the directory structure was copied, but most of the sub-directories were empty. My guess is that this is an Apple SMB problem. I had this happen before when I first tested unraid in 2010. When I copy files in small batches I do not see this problem. I don't think you have a hardware problem. I have not tried this with Windows 7, but I'm guessing this is an Apple issue.

Thanks for the help.

I replaced a 1 TB (Drive A) drive with a 2 TB drive in my 3 drive unRaid Basic setup about 2 months ago. There is now a 2TB Parity, a 1 TB data, and a 2 TB data drive in my setup which is working perfectly. Since I was using the basic version, I was limited to 3 drives and took the old 1TB Drive A out of my array as per the instruction for replacing a drive. That process went smoothly, and the data was rebuilt on the new 2TB drive. I disconnected the SATA cable on the old 1 TB (Drive A) with the intention of putting the drive back into the array when I bought a Plus license. I just bought the unRaid Plus license, and would like to add back the old 1TB (Drive A) back to the array. Before I do this however, I was wondering if switching a drive that used to be part of the array back into the system will screw anything up. Will unRaid see the old Drive A as a completely new disk and just format it for use in the array, the hoped for result; or will it see the old Drive A, and become confused as to the presence of this old drive A which has not been part of the Array for months? I'm using unRaid 4.7 (Plus version) Any advice appreciated.

If you want something that 'just works', I'd recommend a WDTV Live. For ~$100, you get a small, silent box, with a remote control that will play most video files. I own 3 of them, and it's so simple to operate that visitors can use it with little instruction. Wife Acceptance factor - high If you enjoy tinkering, then a HTPC/XBMC combo may be more to your taste. I've got one of those as well. But the Wife Acceptance factor is low. If it crashes, I have to be the technical support. I also have a Logitech Revue, which is more appliance-like than the HTPC, but still allows room to tinker. Wife acceptance factor is low here. Finally I had a mac mini as a frontend to Plex. This was absolutely the best solution for me, but at $600, a mini was too valuable to use as an HTPC, and was re-purposed as my desktop. wow. 3 WDTV Live +'s, an ION based HTPC, and a Logitech Revue. I think I may have a problem.

Also agree with elevating it off the ground. After a hard rain, I discovered water in my basement that would have damaged my unRaid server. In my new place, the server is elevated about 8 inches of the floor, sitting on a concrete block. I also added a dehumidifier.

Are there any 'store-bought' PCs, as opposed to custom builds, that are known to work with unRaid? I believe I have seen the Dell Dimension 9200 mentioned, but are there other HP/Dell/Gateway units currently being produced that could be used for an unRaid server? With the buying power of a Dell or HP, it is hard to beat their prices on a generic PC if one does not feel comfortable doing a custom build. Any suggestions? Thanks