dashahz

Thanks to everyone for replying! I was able to quickly move the folders from \\tower\disk1\UserShareOld to \\tower\disk1\UserShareNew and they immediately appeared in tower\UserShareNew. I also rebooted (just in case) and everything continued to work. Thanks to everyone for the quick and helpful replies!

Thanks for the replies. I did find an article on using Midnight Commander to move data from one disk to another, but I wasn't sure whether there would be any complications in moving from one User Share to another. Will UnRaid simply "see" the data in the new User Share once it is moved, and will affect Parity (or any other component) be affected in any adverse way? Thanks!

Hello! I have UserShareOld and UserShareNew. I am looking to move data from UserShareOld to UserShareNew. Since the data is already on the Unraid system, is there any way I can easily change/move the files without needing to recopy them? So for instance, could I safely move the folders from \\tower\disk1\UserShareOld to \\tower\disk1\UserShareNew? I attempted to do a Google search, and a search of this forum but could not find a relevant answer. I am using UnRaid 5.0.6. Please let me know if I can provide any other information. Thanks!

Hello! I am using UnRaid 5.0-rc12a. Drive 6 in my array keeps showing a red ball. I have run multiple short and long SMART tests, but they do not reveal any errors. Since they revealed no errors, I attempted to re-add the drive to the array (using the rebuild approach and not the "Trust My Array" approach). Can someone shed any light as to what the problem may be? I've attached more details below: Smart Status Report Statistics for /dev/sdp ST3000DM001-1CH166_Z1F15ZHD smartctl -a -d ata /dev/sdp smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST3000DM001-1CH166 Serial Number: Z1F15ZHD Firmware Version: CC26 User Capacity: 3,000,592,982,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Sat Jun 8 17:44:25 2013 PDT 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: (0x00) Offline data collection activity was never started. 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: ( 89) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 119 100 006 Pre-fail Always - 217777296 3 Spin_Up_Time 0x0003 094 094 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 11 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 46118 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 284 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 8 183 Runtime_Bad_Block 0x0032 098 098 000 Old_age Always - 2 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 063 061 045 Old_age Always - 37 (Min/Max 33/37) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 2 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 111 194 Temperature_Celsius 0x0022 037 040 000 Old_age Always - 37 (0 24 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 137812615626786 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 5860772544 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 5860539487 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% 267 - # 2 Extended offline Completed without error 00% 236 - # 3 Short offline Completed without error 00% 150 - # 4 Short offline Completed without error 00% 117 - # 5 Short offline Completed without error 00% 0 - 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. HDParam: HDParm Info for /dev/sdp ST3000DM001-1CH166_Z1F15ZHD /dev/sdp: ATA device, with non-removable media Model Number: ST3000DM001-1CH166 Serial Number: Z1F15ZHD Firmware Revision: CC26 Transport: Serial, SATA Rev 3.0 Standards: Used: unknown (minor revision code 0x0029) Supported: 8 7 6 5 Likely used: 8 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 268435455 LBA48 user addressable sectors: 5860533168 Logical Sector size: 512 bytes Physical Sector size: 4096 bytes Logical Sector-0 offset: 0 bytes device size with M = 1024*1024: 2861588 MBytes device size with M = 1000*1000: 3000592 MBytes (3000 GB) cache/buffer size = unknown Form Factor: 3.5 inch Nominal Media Rotation Rate: 7200 Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, no device specific minimum R/W multiple sector transfer: Max = 16 Current = ? Advanced power management level: 128 Recommended acoustic management value: 208, current value: 0 DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: * SMART feature set Security Mode feature set * Power Management feature set * Write cache * Look-ahead * Host Protected Area feature set * WRITE_BUFFER command * READ_BUFFER command * DOWNLOAD_MICROCODE * Advanced Power Management feature set SET_MAX security extension * 48-bit Address feature set * Device Configuration Overlay feature set * Mandatory FLUSH_CACHE * FLUSH_CACHE_EXT * SMART error logging * SMART self-test * General Purpose Logging feature set * WRITE_{DMA|MULTIPLE}_FUA_EXT * 64-bit World wide name Write-Read-Verify feature set * WRITE_UNCORRECTABLE_EXT command * {READ,WRITE}_DMA_EXT_GPL commands * Segmented DOWNLOAD_MICROCODE * Gen1 signaling speed (1.5Gb/s) * Gen2 signaling speed (3.0Gb/s) * Gen3 signaling speed (6.0Gb/s) * Native Command Queueing (NCQ) * Phy event counters * unknown 76[15] DMA Setup Auto-Activate optimization Device-initiated interface power management * Software settings preservation * SMART Command Transport (SCT) feature set * SCT LBA Segment Access (AC2) unknown 206[7] unknown 206[12] (vendor specific) unknown 206[13] (vendor specific) Security: Master password revision code = 65534 supported not enabled not locked frozen not expired: security count supported: enhanced erase 326min for SECURITY ERASE UNIT. 326min for ENHANCED SECURITY ERASE UNIT. Logical Unit WWN Device Identifier: 5000c5003ccf56a8 NAA : 5 IEEE OUI : 000c50 Unique ID : 03ccf56a8 Checksum: correct Syslog attached (in zip format since over the 192kb limit). Thanks! syslog-2013-06-07.zip

Will do. Thanks for checking Joe!

Rob: Thanks for pointing out that this error occurred at day and hour 0! In that case, I'll leave things as-is and I'll attempt to re-add it to the array using Joe's instructions at http://lime-technology.com/forum/index.php?topic=2569.msg20649#msg20649. Thanks again Joe L and RobJ for your very prompt and insightful answers!

Thanks for the prompt information Joe! I had bought this server from LimeTech, but I did have to replace the power supply early last year, and I don't recall whether I tried to "clean things up". I've uploaded some photos of how it currently looks below: https://skydrive.live.com/redir?resid=57B825B47436CA07!107&authkey=!APAW42tism9WA3o In case that link breaks since it's too long, here is a shortened link: http://sdrv.ms/11AFkOx The drive in question is in the middle bay. Does this look too tight? And if I remove the tie, can I ignore this error unless I see the error again? Thanks!

UnRaid marked one of my hard drives as red recently. I did a SMART test and while the SMART tests all come back clean (I also put the hard drive into another computer and did other hdd scan tests which revealed no problems). However, on the SMART Status Page, the hard drive also reveals "ATA Error Count: 1" and has some information that my other hard drives do not have. I do not understand this error, especially since the SMART tests keep coming back clean. Should I proceed to insert this disk back into the array, or do I need to proceed to replace it? I should note that I have had to hard reboot this server a few times since I've been having some problems with UnRaid freezing during a robocopy operation. So, I'm not sure if this error may be related to that. Here is the SMART Status Report: Statistics for /dev/sdj SAMSUNG_HD103UJ_S13PJ1CS301478 smartctl -a -d ata /dev/sdj smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: SAMSUNG SpinPoint F1 DT series Device Model: SAMSUNG HD103UJ Serial Number: S13PJ1CS301478 Firmware Version: 1AA01113 User Capacity: 1,000,204,886,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 3b Local Time is: Sun Mar 24 20:03:53 2013 PDT 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: (0x00) Offline data collection activity was never started. 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: (11601) 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: ( 194) minutes. Conveyance self-test routine recommended polling time: ( 21) minutes. SCT capabilities: (0x003f) SCT Status supported. SCT Error Recovery Control 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 0x000f 100 100 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0007 068 068 011 Pre-fail Always - 10310 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 903 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 100 051 Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 100 100 015 Pre-fail Offline - 9853 9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 11730 10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 0 11 Calibration_Retry_Count 0x0012 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 334 13 Read_Soft_Error_Rate 0x000e 100 100 000 Old_age Always - 0 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 26 184 End-to-End_Error 0x0033 100 100 000 Pre-fail Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 067 062 000 Old_age Always - 33 (Min/Max 30/33) 194 Temperature_Celsius 0x0022 068 061 000 Old_age Always - 32 (Min/Max 29/35) 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 494 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 100 100 000 Old_age Always - 199 200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 0 201 Soft_Read_Error_Rate 0x000a 100 100 000 Old_age Always - 0 SMART Error Log Version: 1 ATA Error Count: 1 CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 1 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 00 d0 00 a7 4e 29 e0 at LBA = 0x00294ea7 = 2707111 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 10 97 4e 29 e0 08 05:10:22.830 READ DMA c8 00 e0 b7 45 29 e0 08 05:10:22.810 READ DMA c8 00 08 97 42 29 e0 08 05:10:22.810 READ DMA c8 00 90 07 3e 29 e0 08 05:10:22.800 READ DMA c8 00 98 87 3b 29 e0 08 05:10:22.790 READ DMA 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% 11729 - # 2 Short offline Completed without error 00% 11725 - # 3 Short offline Completed without error 00% 11725 - # 4 Short offline Completed without error 00% 11707 - # 5 Short offline Completed without error 00% 11707 - # 6 Short offline Completed without error 00% 31 - # 7 Short offline Interrupted (host reset) 90% 31 - 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. Any help you can provide would be appreciated. Thanks!

Thanks for responding dgaschk! I didn't get a chance to run the disk checks until today. As a FYI, I was deleting the files and folders on disk14 since it reached 100% (I had a problem with the split level that I will work on later). However, during this operation of deleting the files, the UnRaid web interface stopped working again (I used the "rd <path> /s /q" command from Dos to delete the folders when the web interface stopped responding). I've completed the Disk Checks and it did not report any problems on any of the 14 disks. I've attached the results in case I missed something (I was looking for each report to state "No corruptions found"). Please let me know what else I can try. Thanks! DiskCheck_UnRaid.doc

I had the same problem today where the web interface became inaccessible. I've attached the same reports as before. Some information that may help: 1. During both incidents, I was running robocopy to and from the UnRaid server. The first time, I was copying data from the UnRaid to another server, and today, I was copying data from the other server to the UnRaid. The first time, I had used the robocopy switch to use 8 threads (mt:, but today I used only 2 threads (/mt:2). In both incidents, robocopy was run from my Win8 computer in case that matters/helps. 2. Disk14 (the one that became full during the robocopy - I need to look into this), is not accessible via SMB - it chokes while all of the other disks are accessible. 3. I am able to access UnMenu during today's incident. Free Linux 3.4.26-unRAID. root@Epson:~# free total used free shared buffers cached Mem: 4111692 4008864 102828 0 305944 3378312 -/+ buffers/cache: 324608 3787084 Swap: 0 0 0 ps -ef Attached since too large to paste SysLog Attached as zip since too large for post. FYI that I removed references to file paths that revealed personal information and replaced them with "<snip: removed parent folder>". Please note that I have run a Check Disk but it found no problems. Any help would be appreciated. Thanks! ps_-ef_2013-02-18.txt syslog_2013-02-18_clean.zip

I just ran a Check Disk in Windows 8 and it reported that it successfully scanned the drive and found no errors.

Hello! I have been experiencing problems with accessing the web interface and user shares with my UnRaid server in the past few weeks. I am unsure whether this is related to my upgrading to v5.0-rc11, or whether it is something else. The first time this happened, I forced a power off (pressed the power button until it turned off). I have not done that this time since I would like to get to the root of the issue. I have the MD-1510/LC server offered by Tom that I purchased in 2009. The main interface is not available, but I am able to access UnMenu. I have taken some results that were asked on some other posts and posted them below. BTW, the name of my server is "epson" and it is at 192.168.0.5. The result of "ps -ef" was too long for a single post and so I have attached it as a file instead. free space root@Epson:~# free total used free shared buffers cached Mem: 4111692 3973024 138668 0 265100 3246332 -/+ buffers/cache: 461592 3650100 Swap: 0 0 0 I tried to run "killall emhttp" and then "nohup /usr/local/sbin/emhttp &", but it didn't seem to complete. SysLog Feb 4 04:40:01 Epson syslogd 1.4.1: restart. Feb 4 05:13:36 Epson kernel: mdcmd (173): spindown 0 Feb 4 05:13:37 Epson kernel: mdcmd (174): spindown 1 Feb 4 05:13:37 Epson kernel: mdcmd (175): spindown 14 Feb 4 11:59:58 Epson dhcpcd[1113]: eth0: renewing lease of 192.168.0.5 Feb 4 11:59:58 Epson dhcpcd[1113]: eth0: acknowledged 192.168.0.5 from 192.168.0.1 Feb 4 11:59:58 Epson dhcpcd[1113]: eth0: leased 192.168.0.5 for 86400 seconds Feb 4 18:33:10 Epson in.telnetd[18135]: connect from 192.168.0.20 (192.168.0.20) Feb 4 18:33:17 Epson login[18136]: invalid password for 'UNKNOWN' on '/dev/pts/0' from '192.168.0.20' Feb 4 18:33:36 Epson login[18136]: ROOT LOGIN on '/dev/pts/0' from '192.168.0.20' Feb 4 20:18:54 Epson unmenu[1262]: awk: ./unmenu.awk:630: fatal: print to "/inet/tcp/8080/0/0" failed (Connection reset by peer) Feb 4 20:18:54 Epson unmenu-status: Exiting unmenu web-server, exit status code = 2 Feb 4 20:18:54 Epson unmenu[1262]: unmenu.awk unable to open port. It may already be running Feb 4 20:19:04 Epson unmenu-status: Starting unmenu web-server Feb 4 20:28:48 Epson in.telnetd[22181]: connect from 192.168.0.20 (192.168.0.20) Feb 4 20:28:49 Epson login[22182]: ROOT LOGIN on '/dev/pts/0' from '192.168.0.20' Feb 4 20:28:52 Epson emhttp: unRAID System Management Utility version 5.0-rc11 Feb 4 20:28:52 Epson emhttp: Copyright (C) 2005-2012, Lime Technology, LLC Feb 4 20:28:52 Epson emhttp: Pro key detected, GUID: 054C-02A5-0001-A08102127949 Feb 4 20:28:52 Epson emhttp: get_config_idx: fopen /boot/config/flash.cfg: No such file or directory - assigning defaults Feb 4 20:28:52 Epson emhttp: diskFsStatus.1 not found Feb 4 20:28:52 Epson kernel: emhttp[22195]: segfault at 0 ip b74e6760 sp bf942ed0 error 4 in libc-2.11.1.so[b746d000+15c000] Feb 4 20:32:27 Epson emhttp: unRAID System Management Utility version 5.0-rc11 Feb 4 20:32:27 Epson emhttp: Copyright (C) 2005-2012, Lime Technology, LLC Feb 4 20:32:27 Epson emhttp: Pro key detected, GUID: 054C-02A5-0001-A08102127949 Feb 4 20:32:27 Epson emhttp: get_config_idx: fopen /boot/config/flash.cfg: No such file or directory - assigning defaults Feb 4 20:32:27 Epson emhttp: diskFsStatus.1 not found Feb 4 20:32:27 Epson kernel: emhttp[22652]: segfault at 0 ip b754f760 sp bfa1d0f0 error 4 in libc-2.11.1.so[b74d6000+15c000] Feb 4 20:45:25 Epson in.telnetd[23812]: connect from 192.168.0.20 (192.168.0.20) Feb 4 20:45:25 Epson login[23813]: ROOT LOGIN on '/dev/pts/1' from '192.168.0.20' I've also attached my SysLog. Please let me know if anyone needs any other information. Thanks for your time! [Edit] I unfortunately needed to access some files on the server and so I had to do a hard reboot. The server is currently running a parity check. I've attached a new Syslog in case it helps. Using the UnMenu SysLog area, I've isolated the "Errors" and "Minor Issues" sections: Feb 4 23:07:15 Epson kernel: pci_root PNP0A08:00: ignoring host bridge window [mem 0x000d0000-0x000dffff] (conflicts with Adapter ROM [mem 0x000cc800-0x000d17ff]) (Minor Issues) Feb 4 23:07:15 Epson kernel: pci0000:00: ACPI _OSC request failed (AE_NOT_FOUND), returned control mask: 0x1d (Minor Issues) Feb 4 23:07:15 Epson kernel: usb 3-2: can't read configurations, error -71 (Errors) Feb 4 23:07:15 Epson kernel: usb 3-2: device descriptor read/64, error -71 (Errors) Feb 4 23:07:15 Epson kernel: usb 3-2: device descriptor read/64, error -71 (Errors) Feb 4 23:07:15 Epson kernel: usb 3-2: device not accepting address 4, error -71 (Errors) Feb 4 23:07:15 Epson kernel: usb 3-2: device not accepting address 5, error -71 (Errors) Feb 4 23:07:17 Epson kernel: REISERFS (device md2): replayed 3 transactions in 0 seconds (Minor Issues) Feb 4 23:07:17 Epson kernel: REISERFS (device md3): replayed 3 transactions in 0 seconds (Minor Issues) Feb 4 23:07:17 Epson kernel: REISERFS (device md4): replayed 3 transactions in 0 seconds (Minor Issues) Feb 4 23:07:17 Epson kernel: REISERFS (device md5): replayed 3 transactions in 0 seconds (Minor Issues) Feb 4 23:07:18 Epson kernel: REISERFS (device md6): replayed 3 transactions in 0 seconds (Minor Issues) Feb 4 23:07:18 Epson kernel: REISERFS (device md7): replayed 3 transactions in 0 seconds (Minor Issues) Feb 4 23:07:18 Epson kernel: REISERFS (device md8): replayed 3 transactions in 0 seconds (Minor Issues) Feb 4 23:07:18 Epson kernel: REISERFS (device md9): replayed 3 transactions in 0 seconds (Minor Issues) Feb 4 23:08:30 Epson kernel: REISERFS (device md10): replayed 54 transactions in 72 seconds (Minor Issues) Feb 4 23:09:46 Epson kernel: REISERFS (device md11): replayed 92 transactions in 76 seconds (Minor Issues) Feb 4 23:11:06 Epson kernel: REISERFS (device md12): replayed 77 transactions in 79 seconds (Minor Issues) Feb 4 23:12:14 Epson kernel: REISERFS (device md13): replayed 82 transactions in 68 seconds (Minor Issues) Feb 4 23:12:17 Epson kernel: REISERFS (device md14): replayed 1423 transactions in 3 seconds (Minor Issues) Feb 4 23:12:19 Epson emhttp: shcmd (85): killall -HUP smbd (Minor Issues) Thanks! ps_-ef.txt syslog_2013-02-04.txt syslog_2013-02-04_after_restart.txt

Hello! I just upgraded from 4.7 to v5rc8a. Since the upgrade, I have been working on adding the users and I have noticed that there have been some longer and usual delays when attempting to load the web interface at certain points in the time. I took a look at the SysLog and found the following Errors and Minor Issues (I did not align these with the pauses - I rebooted the server since I had just finished the upgrade thinking that perhaps a reboot would fix it): Dec 9 17:02:32 Epson kernel: pci_root PNP0A08:00: ignoring host bridge window [mem 0x000d0000-0x000dffff] (conflicts with Adapter ROM [mem 0x000cc800-0x000d17ff]) (Minor Issues) Dec 9 17:02:32 Epson kernel: pci0000:00: ACPI _OSC request failed (AE_NOT_FOUND), returned control mask: 0x1d (Minor Issues) Dec 9 17:02:32 Epson kernel: usb 3-2: device descriptor read/64, error -71 (Errors) Dec 9 17:02:32 Epson kernel: usb 3-2: device descriptor read/64, error -71 (Errors) Dec 9 17:02:32 Epson kernel: usb 3-2: device descriptor read/64, error -71 (Errors) Dec 9 17:02:32 Epson kernel: usb 3-2: device descriptor read/64, error -71 (Errors) Dec 9 17:02:32 Epson kernel: usb 3-2: device not accepting address 4, error -71 (Errors) Dec 9 17:02:32 Epson kernel: usb 3-2: device not accepting address 5, error -71 (Errors) Dec 9 17:02:36 Epson emhttp: shcmd (85): killall -HUP smbd (Minor Issues) Dec 9 17:19:30 Epson emhttp: shcmd (93): killall -HUP smbd (Minor Issues) Dec 9 17:19:42 Epson emhttp: shcmd (99): killall -HUP smbd (Minor Issues) Dec 9 17:20:15 Epson emhttp: shcmd (104): killall -HUP smbd (Minor Issues) Dec 9 17:20:28 Epson emhttp: shcmd (108): killall -HUP smbd (Minor Issues) I have the MD-1510/LC and purchased this directly from Tom back in 2009. I currently have all drives occupied and do not use a cache drive. Please let me resolve these problems. If there is any other information needed, please let me know. Thanks!

Thanks for tips I'll have to work on implementing those in the coming weeks. Thanks again!

RobJ: Thanks for responding. The multiple thread theory makes sense. I tried what you asked and pre-created Photos/2002/Sub1/Name on Disk1 with split level=2. But, this still didn't work. I also tried to pre-create with split level=3 (what I was using) and this still didn't work. Below is the reason I am interested in using the Most Free method: The photos are categorized as follows: |--Photos (root folder) |--Year (like 2008, 2009) |--Main Category (like Birthday, Family) |--Date and name (like 01-01 John Doe) From my reading of unRAID, I can lose any 1 of the drives and successfully recover. However, if I lose two of the drives, then at least one disk of information is lost. To minimize the loss of a chunk of a large span of time of photos, I opted for Most-Free. This is because if I selected High Water, then I may potentially have four months or so of photos on one drive until the High Water point is reached and then the next disk is used. In the event of losing two or more disks, I would lose about four months of photos. On the other hand, with the Most Free method, by selecting a split level of 3, each event (like 01-01 John Doe) is all placed on one disk, and the next event is placed on the next disk, etc (assuming each new event is about the same size). In this case, in the event of losing two or more disks, I would potentially only lose a few events in a given timeframe, and even fewer if the disks were not that full. Also, I get decent performance since if I am browsing an event's photos, they are all on one drive (due to the split level) and hence I do not need to spin up other drives to read the photos and prevent stuttering. If you have any suggestions to accomplish this goal, I would appreciate anyone's input. I'll try another sync tool to see if I can avoid this problem. In any case, I recently discovered that SyncToy 2.0 has file corruption issues with NAS devices. I don't know whether unRAID is affected (the photos I copied using SyncToy for these tests were not corrupted), but combined with the split level problem, I will need to consider a different solution. Here are some links to the SyncToy/NAS issues in case you are interested: http://social.microsoft.com/forums/en-US/synctoy/thread/8cd6481c-1e96-43aa-aca6-ee9f95a6b50f http://www.microsoft.com/downloads/details.aspx?FamilyID=c26efa36-98e0-4ee9-a7c5-98d0592d8c52&DisplayLang=en (read the first section in the "Overview").

Anyone have any thoughts on this? Thanks.

Hello again! Apologies for the delay - I had a family emergency. I removed the 2 new drives so that the server now has 3 data drives + 1 data drive (all Samsung HD103UJ 1TB drives). I ran reiserfsck on all three data drives and it reported that no corruptions were found on any of the drives. I tried running SyncToy when the drives were empty and also when each of the 3 drives had a few files on them - the files still were not split correctly. I ran the tests you requested and have posted the results below. I have also attached a file listing of the original files and the files that appear after I copy them using SyncToy and manually using Explorer so you can more easily see the problem. 1. Empty disks size free disk1 ata-SAMSUNG_HD103UJ_S13PJ1CS301518 976,762,552 976,699,896 disk2 ata-SAMSUNG_HD103UJ_S13PJ1CS302055 976,762,552 976,699,896 disk3 ata-SAMSUNG_HD103UJ_S13PJ1CS301519 976,762,552 976,699,896 2. "Photos" user share created - Empty "Photos" folder created on Disk1 3. Files/Folders being copied to server File listing exported to "Original.txt" 4. After manual copy using explorer (files correctly "split") File listing exported to "ExplorerManual.txt" size free disk1 ata-SAMSUNG_HD103UJ_S13PJ1CS301518 976,762,552 976,554,120 disk2 ata-SAMSUNG_HD103UJ_S13PJ1CS302055 976,762,552 976,698,212 disk3 ata-SAMSUNG_HD103UJ_S13PJ1CS301519 976,762,552 976,699,896 4. Deleted all files and folders from all individual disks (same as #1 - Empty Disks) size free disk1 ata-SAMSUNG_HD103UJ_S13PJ1CS301518 976,762,552 976,699,896 disk2 ata-SAMSUNG_HD103UJ_S13PJ1CS302055 976,762,552 976,699,896 disk3 ata-SAMSUNG_HD103UJ_S13PJ1CS301519 976,762,552 976,699,896 5. Removed and recreated "Photos" user share - Empty "Photos" folder created on Disk1 6. After Synctoy operation (files are split incorrectly) File listing exported to "SyncToy.txt" size free disk1 ata-SAMSUNG_HD103UJ_S13PJ1CS301518 976,762,552 976,651,288 disk2 ata-SAMSUNG_HD103UJ_S13PJ1CS302055 976,762,552 976,649,748 disk3 ata-SAMSUNG_HD103UJ_S13PJ1CS301519 976,762,552 976,651,180 Please let me know if you need any additional information. Thanks!

Thanks for responding RobJ. My config is slightly different than it was when I originally experienced the problem: 1. I have added a new hard drive 2. I have copied data to it using Explorer (I needed to clear up some space on one of my other servers). When I originally experienced the problem, I had 3 data drives + 1 parity drive. All drives are 1TB Samsung drives. No data was on the server yet. So, I basically had all of the space available (close to 3TB). When I did the original copy using Synctoy, none of the discs contained the "2009" folder. So, the problem you mentioned that can occur when a folder already exists didn't apply in my case. Yes, I copied using Explorer after the Synctoy operation had completed and I don't believe that I had cleared the files that Synctoy had copied. You may be on to something here with this. I just tested using SyncToy now (with data on the drives) and the SyncToy operation correctly did not split the contents "01-01 New Year". I'm wondering if the problem is due to starting with empty drives. Let me find some space to move the files from the unRAID server so I can delete everything and start from scratch to reproduce the results so we can troubleshoot from there. I'll get back to you on this. Thanks.

Here are my user share settings: Share name: Photos Allocation method: Most-free Min. free space: (blank) Split level: 3 Included disk(s): (blank) Excluded disk(s): (blank) Export (SMB): export read/write Export (NFS): (blank) I verified that I was indeed copying to a user share (\\tower\Photos) and not a disk share (like \\tower\disk1). Another confirmation of using the user share vs the disk share is that the files in the folders are being separated on to individual disk drives - if I was incorrectly using the disk share, then the files would only show up on the same disk (please correct me if my understanding is wrong here). Do I need to do anything differently than simply keep this thread to notify Tom of the issue? Thanks!

Thanks for responding bjp999! Correct - Explorer is producing a different result than SyncToy. When you say that there "is an issue with the user share configuration", do you mean with the configuration I assigned or with the unRAID software itself? If it is with the configuration I assigned, can you please let me know what setting I need to adjust to correct this? If it is the unRAID software itself, do I need to post this bug somewhere for Tom to add to his Things To Do list? Thanks.

Anyone have any ideas about this?

Thanks for responding Biggy2872. True, it is possible to see what forums a user is signed up for. However, let's say that I am reading an interesting thread and I want to sign up for notifications for that thread. By looking at the thread itself, there is no clear indication whether I have signed up for notifications. What I am suggesting is that the "notify" button should say something like "enable notifications" or "disable notifications" depending on the status of the notifications. I realize that all the user would need to do is simply click on "Notify" and infer from the resulting message whether they are signed up for notifications, but this is not intuitive in my opinion. A non-tech savvy user is more likely to use a forum if it is simpler to use and I feel that this would help.

When browsing the forum, there is no indication whether a specific thread or board is set up to send notifications to the user. The only way I have found to do is to click on "Notify" and then if it says "Are you sure you wish to ENABLE notification of new...?" then I infer that notifications have not been set up for the thread or board. And if it says "Are you sure you wish to DISABLE notification of new...?", then notifications have been enabled. I wanted to suggest that the forum offer an easier way to identify whether a thread or board is set up for notifications.

Hello! I am getting my new unRAID server ready to begin using as a backup server. I have found that when I use Microsoft SyncToy (http://www.microsoft.com/downloads/details.aspx?FamilyID=c26efa36-98e0-4ee9-a7c5-98d0592d8c52&DisplayLang=en), the photos that are copied do not respect the split level setting that I have used. Below are two paths of some of my folders on the unRAID server. "Photos" is a user share using the "most-free" allocation method. \\tower\Photos\2009\Family\01-01 New Year 0 1 2 3 4 \\tower\Photos\2009\Family\02-01 Birthday 0 1 2 3 4 I have set the split level to 3 so that any folder and its contents under level 3 ("01-01 New Year" and "02-01 Birthday" in this case) are copied on to the same drive. When I use Windows Explorer to copy the folder "Family" from my primary server to unRAID, "01-01 New Year" and "02-01 Birthday" correctly respect the split level setting. So: "01-01 New Year" is created on Disk1 as "\\disk1\Photos\2009\Family\01-01 New Year", and "02-01 Birthday" is created on Disk2 as "\\disk2\Photos\2009\Family\02-01 Birthday" However, when I use SyncToy to copy the "Family" folder, unRAID appears to act as if the split level is set to something very high since unRAID begins to split the contents of "01-01 New Year" and "02-01 Birthday" across all disks so that for example "01-01 New Year\1.jpg" is on disk1 and "01-01 New Year\2.jpg" is on disk2, etc., even though the split level is 3. I tried to lower the split level down to 2 and got the same results with SyncToy. When I lowered the split level down to 1, files were no longer spread across any of my drives as if the split level was set to 0. I am using unRAID Server Pro v4.5-beta6. I don't see any reason why the software I use to copy the files would make a difference since unRAID should be managing what is copied to it. Is this a bug, or am I missing something? Does anyone have any suggestions as to how I can get around this problem? Any explanation of why this occurs would also be appreciated. Thanks.

I just re-ran the preclear script on all 4 drives and sdb and sdc were successfully precleared. But, sdd and sde this time froze at 88%. This is interesting because when I ran the test on sde earlier, it did complete successfully. However, I will rerun the tests on sdd and sde as JimmyJoe suggested to see what my results are. Can someone help me interpret the SMART results from the two discs that successfully precleared? Here are my results: ============================================================================ == == Disk /dev/sdb has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 71c71 < 190 Airflow_Temperature_Cel 0x0022 071 067 000 Old_age Always - 29 (Lifetime Min/Max 29/29) --- > 190 Airflow_Temperature_Cel 0x0022 069 067 000 Old_age Always - 31 (Lifetime Min/Max 29/31) 78c78 < 201 Soft_Read_Error_Rate 0x000a 253 253 000 Old_age Always - 0 --- > 201 Soft_Read_Error_Rate 0x000a 100 100 000 Old_age Always - 0 ============================================================================ ============================================================================ == == Disk /dev/sdc has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 71c71 < 190 Airflow_Temperature_Cel 0x0022 071 066 000 Old_age Always - 29 (Lifetime Min/Max 29/29) --- > 190 Airflow_Temperature_Cel 0x0022 068 066 000 Old_age Always - 32 (Lifetime Min/Max 29/32) 78c78 < 201 Soft_Read_Error_Rate 0x000a 253 253 000 Old_age Always - 0 --- > 201 Soft_Read_Error_Rate 0x000a 100 100 000 Old_age Always - 0 ============================================================================ I've attached my syslog in case anyone needs it. Thanks.