EMKO

oh crap not what i was hoping for well maybe i can see if i can get this one drive onto my motherboard SATA thanks

yes it is doing a correction every time, i am using two SASLP-MV8 not sure if they are based on Marvel controllers, although i didn't get these errors for a long time.

Does anyone know how i can identify the drive causing the parity check errors? i get 5 every time. Is there a way to make Unraid remember the values on each disk at these error spots and then after a another parity check compare to see what drive is changing these spots? and have ability rerun at these spots to see if its fixed? i have 11 drivers many different sizes maybe i can get a notification when error happens so i can at least narrow it down if it gets passed some smaller drives without errors. or am i limited to having to take a drive out one at a time with a new one rebuild the data and then check with a party check that takes like 20hours? each time?

5 - Obtain the vendor/product ID for that device from the last column. 00:19.0 from my example is 8086:153b. 6 - Edit your syslinux.cfg file and add the following after the append but before initrd=/bzroot. Code: [select] pci-stub.ids=8086:153b what does this do? i have a on board network and a pci 2 port but all show up same 05:00.0 0200: 10ec:8168 (rev 0c) 06:00.0 0200: 10ec:8168 (rev 0c) 0d:00.0 0200: 10ec:8168 (rev 09) i did add the 2 port to my vm and its working but what happens when i reboot the system? will unraid try to use it ?

wow works great can't Unraid automate this? Unraid way i would get USB to work for 1-2min this way works and i can change the usb device at any time. Only problem if i change anything in the VM this VM text gets reset

very buggy, keyboard does not work,some tabs are small with ... instead of names and after using it for 5min i got a black screen not matter what i do i cant get the program to open again. Stopping and restarting the docker results again black screen after the xrdp login dialog

yes please, without it accessing a single file wakes up the whole array with it on it will wake up only the drive the file is on and just browsing the shares is very smooth and fast. Even though cache_dirs is a weird fix it does work and at least make 6 have it until or if you guys can figure out a proper way to do it.

i noticed my windows file history backups has over 400k files and lots of folders so i added -a '-noleaf \( -name Data -prune -o -name data -prune \) -o -print' the folder is /mnt/user/backup/username/folder/Data since i did this i see its running but any time i browse any cached dirs it still wakes up all the drives and takes time so i think its not working correct. Am i using the commands in a wrong way? is there a way to see the status of what is has cached or what it is doing? Jun 12 11:59:59 Tower cache_dirs: ============================================== Jun 12 11:59:59 Tower cache_dirs: command-args=-w -B -a -noleaf ( -name Data -prune -o -name data -prune ) -o -print Jun 12 11:59:59 Tower cache_dirs: vfs_cache_pressure=10 Jun 12 11:59:59 Tower cache_dirs: max_seconds=10, min_seconds=1 Jun 12 11:59:59 Tower cache_dirs: max_depth=9999 Jun 12 11:59:59 Tower cache_dirs: command=find -noleaf ( -name Data -prune -o -name data -prune ) -o -print Jun 12 11:59:59 Tower cache_dirs: version=1.6.7

didn't see your post, i left preclear and its on step 10 post-read. so if this read has no errors then its good?

so i just let it preclear and it will be fine? should i do another preclear after this one? thanks

i have a 2tb wd ears drive and i put a jumper on it. The problem im having is that every time i run preclear it gets stuck at 65% pre-read. Today i tried again and now it got stuck on 65% and unmenu went down, i left my computer and came back 5-10min later and i notice preclear was moving again and unmenu was back but in my syslog i see many errors can someone tell me if its still ok? again at 69% it stopped for 5min and unmenu was down again i have 2 drives that work perfect in the array and i have used unraid for a year now. i added my syslog and preclear smart_start some errors i see syslog.txt smart_start_sdb.txt

my preclear of a 2tb ears drive stops at 65% on pre read, i ran it 2 times and both times is stops at 65%. on the drive i jumper 7 8 syslog i see this Dec 27 07:44:44 Tower kernel: hdc: ide_dma_sff_timer_expiry: DMA status (0x21) Dec 27 07:44:54 Tower kernel: hdc: DMA timeout error Dec 27 07:44:54 Tower kernel: hdc: dma timeout error: status=0x58 { DriveReady SeekComplete DataRequest } Dec 27 07:44:54 Tower kernel: hdc: possibly failed opcode: 0x25 Dec 27 07:44:54 Tower kernel: hdc: DMA disabled Dec 27 07:44:54 Tower kernel: ide1: reset: success in smart_start i have smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WMAZA1789360 Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Mon Dec 27 10:27:39 2010 Local time zone must be set--see zic m 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: (36480) 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3035) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 253 253 021 Pre-fail Always - 1041 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 10 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 8 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 8 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 7 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 36 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 SMART Error Log Version: 1 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.