Ouze

This is what it was. Thank you. I could browse to it on my PC via explorer, and mapped it as a drive, so I didn't check that the share was actually being exported - I assumed if it wasn't I wouldn't see it at all.

Hello all, So, I built an unraid server in 2011 using 4.7. I didn't want to spin up the drives all the time, so I got the cache dirs script and ran it. I then put a utility on my windows PC called Index Your Files which does exactly what it sounds like, it scans the directories every so often and builds a search index. As I recall Windows Search would wake the drives up and IYF did not spin up anything. So, that ran pretty well until now. Last night I upgraded to 5x and then the newest version of 6x. I got unmenu installed, and installed all my normal packages, the email thing, the UPS thing, all working great. I'm having a problem with indexing the server, though. When I manually index, or just let it automatically index, IYF finds nothing at all; as if there were no files on the server. The data actually IS on the server, and it's all great, and I've made no changes to IYF (which actually has almost no settings anyway, it's super simple) so I probably misconfigured cache_dirs somehow. Here is my current syslog entry for cache dirs: So, I don't really know what those commands mean, but my guess is one of them is misconfigured. Here is what the cache_dirs looked like on 4.7: So what do I need to change? And how? Thank you very much.

I can't speak to the promotion, but I did the upgrade last night and there were no major issues. I uninstalled my addons and went from 4.7 to whatever the most current version of 5 is. That went without issue. I then went to the most current version of 6. That was OK too, except one panic moment when I skipped a step and didn't make my USB stick bootable (oops). I suspect I probably didn't even need to pull the USB stick at all, but whatever. All seems well except I am having an issue with my cache dirs. I will take that up in the appropriate thread though. Thank for for the assistance.

Ok, thank you - upgrade it is. Is there a simple guide somewhere I can follow, or do I step from 4.7 to 5.x and then to 6.x?

I have been putting this off forever because I am terrified of upsetting the currently great status quo. I built my 24 bay Norco Unraid box in 2011 and it's been working great since then. I haven't had a single serious issue with it. Now I see that 6 is imminent. My friend that I went in on the license with is using the latest version of 6, and some of the features are amazing. I think it might finally be time to pull the trigger. I've bought a new thumbstick that was on the approved compatible list. What is the easiest way to move to the new version? I was thinking just installing to a new stick and replacing the old one, copying over my license file, might be the way; is that so? Apologies if this is covered elsewhere, I only saw upgrades to 5.x when searching.

Thanks!

OK, the Preclear finished. Is it safe to add this disk to my array? ========================================================================1.9 == invoked as: ./preclear_disk.sh -m #####@gmail.com /dev/sde == Hitachi HDS722020ALA330 JK1121YAG7HR0S == Disk /dev/sde has been successfully precleared == with a starting sector of 63 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 5:46:58 (96 MB/s) == Last Cycle's Zeroing time : 5:14:27 (106 MB/s) == Last Cycle's Post Read Time : 12:07:34 (45 MB/s) == Last Cycle's Total Time : 23:10:12 == == Total Elapsed Time 23:10:12 == == Disk Start Temperature: 33C == == Current Disk Temperature: 38C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sde /tmp/smart_finish_sde ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 157 181 0 ok 38 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ ============================================================================ == == S.M.A.R.T Initial Report for /dev/sde == Disk: /dev/sde smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Hitachi Deskstar 7K2000 Device Model: Hitachi HDS722020ALA330 Serial Number: JK1121YAG7HR0S Firmware Version: JKAOA20N User Capacity: 2,000,398,934,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Sat Mar 17 18:39:23 2012 CDT 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: (0x80) Offline data collection activity was never started. Auto Offline Data Collection: Enabled. 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: (20567) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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. SCT capabilities: (0x003d) 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 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 134 134 054 Pre-fail Offline - 98 3 Spin_Up_Time 0x0007 211 211 024 Pre-fail Always - 285 (Average 399) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 67 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 112 112 020 Pre-fail Offline - 39 9 Power_On_Hours 0x0012 099 099 000 Old_age Always - 8991 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 60 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 330 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 330 194 Temperature_Celsius 0x0002 181 181 000 Old_age Always - 33 (Lifetime Min/Max 17/53) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 SMART Error Log Version: 0 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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. == ============================================================================ ============================================================================ == == S.M.A.R.T Final Report for /dev/sde == Disk: /dev/sde smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Hitachi Deskstar 7K2000 Device Model: Hitachi HDS722020ALA330 Serial Number: JK1121YAG7HR0S Firmware Version: JKAOA20N User Capacity: 2,000,398,934,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Sun Mar 18 17:49:35 2012 CDT 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: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. 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: (20567) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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. SCT capabilities: (0x003d) 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 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 134 134 054 Pre-fail Offline - 98 3 Spin_Up_Time 0x0007 211 211 024 Pre-fail Always - 285 (Average 399) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 67 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 112 112 020 Pre-fail Offline - 39 9 Power_On_Hours 0x0012 099 099 000 Old_age Always - 9014 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 60 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 330 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 330 194 Temperature_Celsius 0x0002 157 157 000 Old_age Always - 38 (Lifetime Min/Max 17/53) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 SMART Error Log Version: 0 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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. == ============================================================================

Hello all, I was low on space on my build, so I took a 2tb I had been using for backups and didn't really need, and added it to the server. I connected via screen and started a preclear. I just checked my syslog and I have the following 2 scary error messages: The first one I've seen now and then, and was told it's because I have 2 AOC-SASLP-MV8's and it happens sometimes. Indeed, I have seen no problems and the server hasn't been turned off since December 2nd, until today. Here's the semi-common one: Mar 17 18:22:06 Shiva kernel: ------------[ cut here ]------------ Mar 17 18:22:06 Shiva kernel: WARNING: at fs/proc/generic.c:590 proc_register+0x11c/0x14b() (Minor Issues) Mar 17 18:22:06 Shiva kernel: Hardware name: C2SEA Mar 17 18:22:06 Shiva kernel: proc_dir_entry 'scsi_tgt/mvst_scst' already registered (Drive related) Mar 17 18:22:06 Shiva kernel: Modules linked in: mvsas(+) libsas scst scsi_transport_sas (Drive related) Mar 17 18:22:06 Shiva kernel: Pid: 816, comm: modprobe Not tainted 2.6.32.9-unRAID #8 (Errors) Mar 17 18:22:06 Shiva kernel: Call Trace: (Errors) Mar 17 18:22:06 Shiva kernel: [<c102449e>] warn_slowpath_common+0x60/0x77 (Errors) Mar 17 18:22:06 Shiva kernel: [<c10244e9>] warn_slowpath_fmt+0x24/0x27 (Errors) Mar 17 18:22:06 Shiva kernel: [<c109cf0e>] proc_register+0x11c/0x14b (Errors) Mar 17 18:22:06 Shiva kernel: [<c109d0cc>] proc_mkdir_mode+0x2f/0x43 (Errors) Mar 17 18:22:06 Shiva kernel: [<c109d0ef>] proc_mkdir+0xf/0x11 (Errors) Mar 17 18:22:06 Shiva kernel: [<f83d8a36>] scst_build_proc_target_dir_entries+0x55/0xdc [scst] (Routine) Mar 17 18:22:06 Shiva kernel: [<f83bfca9>] __scst_register_target_template+0x16c/0x3af [scst] (Routine) Mar 17 18:22:06 Shiva kernel: [<f843dd5d>] mvst_init+0x3b/0x5b [mvsas] (Errors) Mar 17 18:22:06 Shiva kernel: [<f8442895>] mvs_pci_init+0xaa5/0xaf7 [mvsas] (Errors) Mar 17 18:22:06 Shiva kernel: [<c10062d9>] ? dma_generic_alloc_coherent+0x0/0xdb (Errors) Mar 17 18:22:06 Shiva kernel: [<c1142050>] local_pci_probe+0xe/0x10 (Errors) Mar 17 18:22:06 Shiva kernel: [<c11426ad>] pci_device_probe+0x48/0x66 (Errors) Mar 17 18:22:06 Shiva kernel: [<c1194956>] driver_probe_device+0x79/0xed (Errors) Mar 17 18:22:06 Shiva kernel: [<c1194a0d>] __driver_attach+0x43/0x5f (Errors) Mar 17 18:22:06 Shiva kernel: [<c11940a7>] bus_for_each_dev+0x39/0x5a (Errors) Mar 17 18:22:06 Shiva kernel: [<f844a000>] ? mvs_init+0x0/0x45 [mvsas] (Errors) Mar 17 18:22:06 Shiva kernel: [<c119482f>] driver_attach+0x14/0x16 (Errors) Mar 17 18:22:06 Shiva kernel: [<c11949ca>] ? __driver_attach+0x0/0x5f (Errors) Mar 17 18:22:06 Shiva kernel: [<c119451c>] bus_add_driver+0x9f/0x1c5 (Errors) Mar 17 18:22:06 Shiva kernel: [<f844a000>] ? mvs_init+0x0/0x45 [mvsas] (Errors) Mar 17 18:22:06 Shiva kernel: [<c1194ccf>] driver_register+0x7b/0xd7 (Errors) Mar 17 18:22:06 Shiva kernel: [<f844a000>] ? mvs_init+0x0/0x45 [mvsas] (Errors) Mar 17 18:22:06 Shiva kernel: [<c1142882>] __pci_register_driver+0x39/0x8c (Errors) Mar 17 18:22:06 Shiva kernel: [<f844a000>] ? mvs_init+0x0/0x45 [mvsas] (Errors) Mar 17 18:22:06 Shiva kernel: [<f844a030>] mvs_init+0x30/0x45 [mvsas] (Errors) Mar 17 18:22:06 Shiva kernel: [<c1001139>] do_one_initcall+0x4c/0x131 (Errors) Mar 17 18:22:06 Shiva kernel: [<c1042e6e>] sys_init_module+0xa7/0x1dd (Errors) Mar 17 18:22:06 Shiva kernel: [<c1002935>] syscall_call+0x7/0xb (Errors) Mar 17 18:22:06 Shiva kernel: ---[ end trace 870eb559e6698973 ]--- So I'm not too worried about that one. This one, on the other hand, I have never seen before and am somewhat concerned: Mar 17 18:32:48 Shiva login[8214]: ROOT LOGIN on `pts/0' from `192.168.1.145' (Logins) Mar 17 18:36:46 Shiva ata_id[10353]: HDIO_GET_IDENTITY failed for '/dev/block/8:64' (Minor Issues) Mar 17 18:36:46 Shiva kernel: sde: sde1 (Drive related) Mar 17 18:36:46 Shiva kernel: ------------[ cut here ]------------ Mar 17 18:36:46 Shiva kernel: WARNING: at drivers/ata/libata-core.c:5186 ata_qc_issue+0x10b/0x308() (Minor Issues) Mar 17 18:36:46 Shiva kernel: Hardware name: C2SEA Mar 17 18:36:46 Shiva kernel: Modules linked in: md_mod xor i2c_i801 i2c_core ahci r8169 sata_sil24 mvsas libsas scst scsi_transport_sas (Drive related) Mar 17 18:36:46 Shiva kernel: Pid: 10362, comm: smartctl Tainted: G W 2.6.32.9-unRAID #8 (Errors) Mar 17 18:36:46 Shiva kernel: Call Trace: (Errors) Mar 17 18:36:46 Shiva kernel: [<c102449e>] warn_slowpath_common+0x60/0x77 (Errors) Mar 17 18:36:46 Shiva kernel: [<c10244c2>] warn_slowpath_null+0xd/0x10 (Errors) Mar 17 18:36:46 Shiva kernel: [<c11b624d>] ata_qc_issue+0x10b/0x308 (Errors) Mar 17 18:36:46 Shiva kernel: [<c11ac0ba>] ? scsi_init_sgtable+0x5b/0x76 (Errors) Mar 17 18:36:46 Shiva kernel: [<c11ba260>] ata_scsi_translate+0xd1/0xff (Errors) Mar 17 18:36:46 Shiva kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Mar 17 18:36:46 Shiva kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Mar 17 18:36:46 Shiva kernel: [<c11baa40>] ata_sas_queuecmd+0x120/0x1d7 (Errors) Mar 17 18:36:46 Shiva kernel: [<c11bc6df>] ? ata_scsi_pass_thru+0x0/0x21d (Errors) Mar 17 18:36:46 Shiva kernel: [<f841869a>] sas_queuecommand+0x65/0x20d [libsas] (Errors) Mar 17 18:36:46 Shiva kernel: [<c11a816c>] ? scsi_done+0x0/0xd (Errors) Mar 17 18:36:46 Shiva kernel: [<c11a82c0>] scsi_dispatch_cmd+0x147/0x181 (Errors) Mar 17 18:36:46 Shiva kernel: [<c11ace4d>] scsi_request_fn+0x351/0x376 (Errors) Mar 17 18:36:46 Shiva kernel: [<c11269a8>] __generic_unplug_device+0x26/0x29 (Errors) Mar 17 18:36:46 Shiva kernel: [<c112934a>] blk_execute_rq_nowait+0x56/0x73 (Errors) Mar 17 18:36:46 Shiva kernel: [<c11293dc>] blk_execute_rq+0x75/0x91 (Errors) Mar 17 18:36:46 Shiva kernel: [<c11292cc>] ? blk_end_sync_rq+0x0/0x28 (Errors) Mar 17 18:36:46 Shiva kernel: [<c11295fa>] ? blk_recount_segments+0x16/0x24 (Errors) Mar 17 18:36:46 Shiva kernel: [<c11250c6>] ? blk_rq_bio_prep+0x47/0x78 (Errors) Mar 17 18:36:46 Shiva kernel: [<c11ac58a>] scsi_execute+0xbf/0x113 (Errors) Mar 17 18:36:46 Shiva kernel: [<c11bb6d0>] ata_cmd_ioctl+0xf8/0x1ba (Errors) Mar 17 18:36:46 Shiva kernel: [<c11bb940>] ata_sas_scsi_ioctl+0x1ae/0x1e8 (Errors) Mar 17 18:36:46 Shiva kernel: [<c11334a5>] ? radix_tree_lookup_slot+0xd/0xf (Errors) Mar 17 18:36:46 Shiva kernel: [<c1048a7f>] ? find_get_page+0x1d/0x79 (Errors) Mar 17 18:36:46 Shiva kernel: [<c104a179>] ? filemap_fault+0xb8/0x305 (Errors) Mar 17 18:36:46 Shiva kernel: [<f841833d>] sas_ioctl+0x36/0x43 [libsas] (Errors) Mar 17 18:36:46 Shiva kernel: [<c11a94c8>] scsi_ioctl+0x299/0x2ad (Errors) Mar 17 18:36:46 Shiva kernel: [<f8418307>] ? sas_ioctl+0x0/0x43 [libsas] (Errors) Mar 17 18:36:46 Shiva kernel: [<c11b326d>] sd_ioctl+0x80/0x8c (Errors) Mar 17 18:36:46 Shiva kernel: [<c112a420>] __blkdev_driver_ioctl+0x50/0x62 (Errors) Mar 17 18:36:46 Shiva kernel: [<c112ad1c>] blkdev_ioctl+0x8b0/0x8dc (Errors) Mar 17 18:36:46 Shiva kernel: [<c1131e2d>] ? kobject_get+0x12/0x17 (Errors) Mar 17 18:36:46 Shiva kernel: [<c112b0f8>] ? get_disk+0x4a/0x61 (Errors) Mar 17 18:36:46 Shiva kernel: [<c101b028>] ? kmap_atomic+0x14/0x16 (Errors) Mar 17 18:36:46 Shiva kernel: [<c104cbfe>] ? get_page_from_freelist+0x2e4/0x344 (Errors) Mar 17 18:36:46 Shiva kernel: [<c104cd4f>] ? __alloc_pages_nodemask+0xdb/0x42f (Errors) Mar 17 18:36:46 Shiva kernel: [<c104f1e3>] ? lru_cache_add_lru+0x22/0x24 (Errors) Mar 17 18:36:46 Shiva kernel: [<c105fe77>] ? page_add_new_anon_rmap+0x33/0x40 (Errors) Mar 17 18:36:46 Shiva kernel: [<c108b6c6>] block_ioctl+0x2a/0x32 (Errors) Mar 17 18:36:46 Shiva kernel: [<c108b69c>] ? block_ioctl+0x0/0x32 (Errors) Mar 17 18:36:46 Shiva kernel: [<c10769d5>] vfs_ioctl+0x22/0x67 (Errors) Mar 17 18:36:46 Shiva kernel: [<c1076f33>] do_vfs_ioctl+0x478/0x4ac (Errors) Mar 17 18:36:46 Shiva kernel: [<c105c983>] ? expand_downwards+0x109/0x136 (Errors) Mar 17 18:36:46 Shiva kernel: [<c1076f93>] sys_ioctl+0x2c/0x45 (Errors) Mar 17 18:36:46 Shiva kernel: [<c1002935>] syscall_call+0x7/0xb (Errors) Mar 17 18:36:46 Shiva kernel: ---[ end trace 870eb559e6698974 ]--- So what's that all about? The preclear appears to be running OK, but I'd rather get a determination if my drive is flaky or not prior to adding it to the array, not after.... My build is Unraid Server Pro 4.7. syslog-2012-03-17.txt

http://www.newegg.com/Product/Product.aspx?Item=N82E16822148681&Tpk=N82E16822148681 use promo code EMCKDHF22 I don't need any drives, so I haven't researched how well this works with unraid. It does not appear, for good or ill, on Raj's hard drive compatibility list - hopefully someone else can chip in how well they work for Unraid.

ok, running 16 hours, 30 passes, zero errors. Memory looks OK. Any other ideas what it could be? Also, it's possible I had a power outage after the last parity check 25-odd days ago, and before I finally got a UPS in place around 3 weeks ago. Would that have potentially caused it? I'm not really even 100% clear on what a sync error is. Does it mean my files are corrupt, or what? Cause 14k would mean essentially everything.

You mean like Memtest x86 or similar? Not yet, no... should I? I certainly could.

ok, here is the running one. Thanks for looking. I have a few more going back some; the time between parity checks was about 25 days or so. syslog-2011-06-13.txt

Ok, I hope this is what you're referring to (and not the long tests?) Too long to post, attached it. smart_tests.txt

Um. I'm not really sure what to do here. I logged into my server this morning, and did a parity sync. I did it manually via the unraid gui, and it looks like correct is the default option when not running the script. I then saw this: STARTED, 6 disks in array. Parity is Valid:. Last parity check < 1 day ago . Parity updated 14908 times to address sync errors. And, from the syslog: [color=red]Jun 13 03:18:36 Shiva login[23274]: ROOT LOGIN on `pts/0' from `192.168.1.145' (Logins) Jun 13 03:20:42 Shiva kernel: mdcmd (70): check CORRECT (unRAID engine) Jun 13 03:20:42 Shiva kernel: md: recovery thread woken up ... (unRAID engine) Jun 13 03:20:42 Shiva kernel: md: recovery thread checking parity... (unRAID engine) Jun 13 03:20:42 Shiva kernel: md: using 1152k window, over a total of 1953514552 blocks. (unRAID engine) Jun 13 03:20:53 Shiva kernel: md: parity incorrect: 128 (Errors) Jun 13 03:20:53 Shiva kernel: md: parity incorrect: 136 (Errors) Jun 13 03:20:54 Shiva kernel: md: parity incorrect: 65680 (Errors) Jun 13 03:20:54 Shiva kernel: md: parity incorrect: 65688 (Errors) Jun 13 03:20:55 Shiva kernel: md: parity incorrect: 262144 (Errors) Jun 13 03:20:57 Shiva kernel: md: parity incorrect: 524288 (Errors) Jun 13 03:20:58 Shiva kernel: md: parity incorrect: 786432 (Errors) Jun 13 03:20:59 Shiva kernel: md: parity incorrect: 1048576 (Errors) Jun 13 03:21:01 Shiva kernel: md: parity incorrect: 1310720 (Errors) Jun 13 03:21:02 Shiva kernel: md: parity incorrect: 1572864 (Errors) Jun 13 03:21:04 Shiva kernel: md: parity incorrect: 1835008 (Errors) Jun 13 03:21:05 Shiva kernel: md: parity incorrect: 2097152 (Errors) Jun 13 03:21:06 Shiva kernel: md: parity incorrect: 2359296 (Errors) Jun 13 03:21:08 Shiva kernel: md: parity incorrect: 2621440 (Errors) Jun 13 03:21:10 Shiva kernel: md: parity incorrect: 2883584 (Errors) Jun 13 03:21:11 Shiva kernel: md: parity incorrect: 3145728 (Errors) Jun 13 03:21:13 Shiva kernel: md: parity incorrect: 3407872 (Errors) Jun 13 03:21:14 Shiva kernel: md: parity incorrect: 3670016 (Errors) Jun 13 03:21:15 Shiva kernel: md: parity incorrect: 3932160 (Errors) Jun 13 03:21:17 Shiva kernel: md: parity incorrect: 4194304 (Errors) Jun 13 03:24:04 Shiva emhttp: shcmd (39): cp /var/spool/cron/crontabs/root- /var/spool/cron/crontabs/root (Other emhttp) Jun 13 03:24:04 Shiva emhttp: shcmd (40): echo '# Generated mover schedule:' >>/var/spool/cron/crontabs/root (Other emhttp) Jun 13 03:24:04 Shiva emhttp: shcmd (41): echo '40 3 * * * /usr/local/sbin/mover 2>$stuff$1 | logger' >>/var/spool/cron/crontabs/root (Other emhttp) Jun 13 03:24:04 Shiva emhttp: shcmd (42): crontab /var/spool/cron/crontabs/root (Other emhttp) Jun 13 03:24:04 Shiva emhttp: shcmd (43): rm /etc/samba/smb-shares.conf >/dev/null 2>$stuff$1 (Other emhttp) Jun 13 03:24:04 Shiva emhttp: shcmd (44): cp /etc/exports- /etc/exports (Other emhttp) Jun 13 03:24:04 Shiva emhttp: shcmd (45): killall -HUP smbd (Minor Issues) Jun 13 03:24:04 Shiva emhttp: shcmd (46): /etc/rc.d/rc.nfsd restart | logger (Other emhttp) Jun 13 03:47:04 Shiva sSMTP[10079]: Creating SSL connection to host Jun 13 03:47:04 Shiva sSMTP[10079]: SSL connection using RC4-SHA Jun 13 03:47:08 Shiva sSMTP[10079]: Sent mail for root@myemailaddress (221 2.0.0 closing connection r1sm3709667icz.2) uid=0 username=root outbytes=1407 Jun 13 04:47:04 Shiva sSMTP[22354]: Creating SSL connection to host Jun 13 04:47:05 Shiva sSMTP[22354]: SSL connection using RC4-SHA Jun 13 04:47:09 Shiva sSMTP[22354]: Sent mail for root@myemailaddress (221 2.0.0 closing connection fw9sm2713312ibb.30) uid=0 username=root outbytes=1408 Jun 13 05:47:04 Shiva sSMTP[852]: Creating SSL connection to host Jun 13 05:47:04 Shiva sSMTP[852]: SSL connection using RC4-SHA Jun 13 05:47:08 Shiva sSMTP[852]: Sent mail for root@myemailaddress (221 2.0.0 closing connection vn4sm4655819icb.19) uid=0 username=root outbytes=1408 Jun 13 06:47:04 Shiva sSMTP[8766]: Creating SSL connection to host Jun 13 06:47:05 Shiva sSMTP[8766]: SSL connection using RC4-SHA Jun 13 06:47:08 Shiva sSMTP[8766]: Sent mail for root@myemailaddress (221 2.0.0 closing connection s9sm2746914ibe.61) uid=0 username=root outbytes=1408 Jun 13 07:47:05 Shiva sSMTP[17927]: Creating SSL connection to host Jun 13 07:47:05 Shiva sSMTP[17927]: SSL connection using RC4-SHA Jun 13 07:47:09 Shiva sSMTP[17927]: Sent mail for root@myemailaddress (221 2.0.0 closing connection hw7sm4728131icc.15) uid=0 username=root outbytes=1408 Jun 13 08:47:04 Shiva sSMTP[24402]: Creating SSL connection to host Jun 13 08:47:04 Shiva sSMTP[24402]: SSL connection using RC4-SHA Jun 13 08:47:08 Shiva sSMTP[24402]: Sent mail for root@myemailaddress (221 2.0.0 closing connection y1sm4765904ica.16) uid=0 username=root outbytes=1408 Jun 13 09:47:04 Shiva sSMTP[28649]: Creating SSL connection to host Jun 13 09:47:05 Shiva sSMTP[28649]: SSL connection using RC4-SHA Jun 13 09:47:09 Shiva sSMTP[28649]: Sent mail for root@myemailaddress (221 2.0.0 closing connection 4sm2813495ibc.59) uid=0 username=root outbytes=1407 Jun 13 10:47:05 Shiva sSMTP[2574]: Creating SSL connection to host Jun 13 10:47:05 Shiva sSMTP[2574]: SSL connection using RC4-SHA Jun 13 10:47:09 Shiva sSMTP[2574]: Sent mail for root@myemailaddress (221 2.0.0 closing connection hw7sm4860038icc.3) uid=0 username=root outbytes=1406 Jun 13 10:48:33 Shiva kernel: md: sync done. time=26870sec rate=72702K/sec (unRAID engine) Jun 13 10:48:33 Shiva kernel: md: recovery thread sync completion status: 0 (unRAID engine)[/color] So now I don't know what to do. (Or if there is anything to do, since I guess they were corrected?). What could have caused this? And how does Unraid know if the errors are actually with the parity, vs being with the actual data? Unraid Pro, 4.7.

I don't think you can stack this with the other $10 off one.

Hello all, I just moved my Cyberpower UPS onto the server and added the clean powerdown and APCUPS packages. I'm not seeing a (possible not related) segfault. I don't know what this means or if I should be concerned. Everything appears OK. Using Unraid Pro 4.7. Snipped: May 22 15:20:16 Shiva kernel: inotifywait[4968]: segfault at a9522f80 ip b770c628 sp bfcec194 error 6 in ld-2.7.so[b7706000+1c000] (Errors) May 22 15:20:16 Shiva kernel: inotifywait[4970]: segfault at a9567f80 ip b7751628 sp bf898144 error 6 in ld-2.7.so[b774b000+1c000] (Errors) I've attached the full, possibly unneccesary, syslog. Thanks! syslog-2011-05-22.txt

Hello all, I'm having the same problem. Yesterday, I added a disk to preclear and started it. No problem. This morning, around 22 hours in, I tried to move over some pictures - 1.3mb - and it took 20 (twenty) minutes. I didn't want to interrupt the preclear, so I went out and did some stuff. I got an email the preclear was done, great. At this point I can't even browse the server, but telnet seems fine. I stopped the array, which stopped normally. Then I shut it down. I then woke it up using the routers WOL. Fine. I use the webgui to try and stop the array, so I can add the new disk. It won't unmount the disks, and it's filling the syslog about it... er, ok. As I was typing this, it finally stopped, but it dumped about 2600 lines into the syslog, and it's usually more like 700-900. I read the posts previous to mind, butI don't know how to identify which drive, from the syslog, is causing the issue to be able to the use fuser command. Any way to identify what's cause the problem? The only thing I've added recently was SNAP. I can live without it, if that is indeed the root cause. thank you! syslog-2011-05-21.txt

Ok, I found a good replacement - Index Your Files, from, unexpectedly, IndexYourFiles.com. It took about 45 seconds to index 94k files\6tb, and you can set it to rescan however often you want. I set it to scan once an hour. I also tested it to make sure that it doesn't spin up drives when doing the 45 second index, and it does not (which presumably is the magic of cache_dirs). This will work, I think, although I'd still love to see a way to innately snap into Windows Search 4\Win 7.

I alternate between XBMC and Boxee on my HTPC, and it's a good product, but it's not really a solution for my problem. I need to be able to search for many different types of files (pdf, text, excel, mkv, iso, everything) and I'd like to be able to sort them in explorer (or at least an explorer like interface) so I can sort by size, date, etc. For that reason Google Desktop Search also fails. I tried Locate32 which looked promising but after a few days gave less then reliable results (finding files I deleted, not finding files that were there, etc etc - but those problems are a different post, really) There's got to be a way to search the server without it taking from 5 to 15 minutes to return results, right?

Hello All, I'm having a problem with locating files on my new Unraid server. My previous setup was 8 disk Areca raid card on a server running windows server 08 x64. My client PC's are all Win 7 x64. So, I want to see if I have a movie - I do a search on the server, Server 08 is indexed, it passes the indexing into Windows 7, long story short, I know if I have it within about 5 seconds. Great. It's working dramatically differently now. I wasn't sure if I remembered to back up some movies or not, so I did a search for "Halloween". That search did find it, but it took 11.5 minutes to do so. Presumably, it's also spinning up every drive on the server while doing this. This is kind of a problem for me. I'm fairly confident after some forum searching that there is no way to index UNC's with Window's 7, at least not any way that works reliably. I tried the Win7 Library Tool, that didn't work. I've also tried Cache_Dirs, which presumably should resolve this very issue. Clearly that's not working for me, and I'm sure it's because I've misconfigured it. I've added it to my /boot/cofig/go file as /boot/cache_dirs -w . What is the simplest way for me to fix my problem? I don't really care how I do it, either by getting working indexing, or by reconfiguring cache_dirs. Thanks!

Thanks so much for the super fast responses, guys. I'm good

OK, this is kind of an unusual deal. I have 2 disks preclearing, one of which is destined to be delivered to my friend who also is running unraid. Due to a series of foolish events, one is going to finish preclearing within the next 10 minutes. The other won't be done for at least 5 hours (i accidentally ran the preclear script twice on the same device and didn't catch it for a few hours). I'm leaving for work in the next hour, where I will see my friend. I'd like to deliver the precleared disk tonight. Is it possible for me to pull the tray with the disk that has finished preclearing from the running machine without interrupting the preclear in progress on a different tray? If not, no big deal, just wondering. EDIT: OK, I did umount /dev/sdg, said it wasn't mounted, made double sure it wasn't spinning, and pulled it. Nothing bad seemed to have happened, array looks good and is running. Thanks!

Hello all, I did a search and didn't really see anything that clearly answered this. I'm running a Supermicro C2SEA and a pair of AOC-SASLP-MV8 (and also, a 2 port controller, but forget that for now). I'm getting good but not great performance. A disk preclear for a 2TB WD20EARS took 25 hours exactly, which is pretty decent according to the wiki. So now I'm concerned with breaking stuff that is working perfect OK. Specifically, tweaking the performance some. My write speed is not so hot, about 24mb/sec. I haven't added a cache drive, but am considering it... Before I go that route, though, I was wondering - do i need to do anything with the bios for the controller cards? All I did, literally, was plug them into the mobo, hook them up, and run. I don't actually know how to get into their own bioses (if they have one) or what firmware they are. I did set my mobo to AHCI, but not sure if i need to (or if I can) do the same on these controllers. Thanks!

I'm good. Thanks, guys

Pretty sure they're all on the same drive. What's the command to do so? It's like "rmdir" or something, right? Alternately, I'm looking at mc now, and it looks pretty promising, but I don't know what I should be doing. Just lining things up from the left to the right and doing file, rename/move?