leemik

I didn't want to rebuild disk #9, I just wanted to rebuild the parity with the old disk #9 re-inserted so i just needed #9 to say it was the right disk without any rebuild of #9. I think I found the solution. "New Config" under "utils" seemed to do the trick. It reset the disk config completely but didn't erase the data on any disks. I was able to configure the disks back in the same order because I took a screenshot and now the parity is rebuilding with no data loss. thanks for the reply though rebuilding parity..and all the sizes look correct *sigh of relief* --mike

Hello, I've been an unraid user for a long time. I'm still on v5.0.5 .. I know I should update but the system has been working fine for the past many years. Anyways, I recently had a reported disk failure and so I replace it with a new disk of the same size. I've done this a many times in the past and it has never given me an issue. Unfortunately, I found out later that it was the disk controller card that went bad and not the disk as several disks suddenly started intermittently reporting as bad or missing during the parity rebuild. It also appears that my parity disk got invalidated as well in my effort to troubleshoot and fix the problem. So as a result I ended up with invalid parity and now a bad drive (because the rebuild never finished successfully on the new drive). Fast Forward a week and I install a new controller. I also insert the old disk (#9) which is still functioning fine and only reported as bad because of the faulty controller. Is there any way to make the old disk "valid" because the array hasn't been used and then just rebuild the parity as it is now? --mike

smartctl comes back fine too? smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Alle n Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: ST31500541AS Serial Number: Firmware Version: CC32 User Capacity: 1,500,301,910,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: Wed Sep 7 17:48:42 2011 EDT 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: ( 643) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off supp ort. 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: (0x103f) SCT Status supported. SCT Feature Control supported. SCT Data Table 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 115 099 006 Pre-fail Always - 87493710 3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 099 099 020 Old_age Always - 1154 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 036 036 030 Pre-fail Always - 4140353017000 9 Power_On_Hours 0x0032 081 081 000 Old_age Always - 16679 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 97 183 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 055 055 000 Old_age Always - 45 190 Airflow_Temperature_Cel 0x0022 066 056 045 Old_age Always - 34 (Lifetime Min/Max 33/34) 194 Temperature_Celsius 0x0022 034 044 000 Old_age Always - 34 (0 17 0 0) 195 Hardware_ECC_Recovered 0x001a 061 046 000 Old_age Always - 87493710 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 - 14199161885387 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 4252484845 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 4241162366 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 Short offline Completed without error 00% 16679 - 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.

OK I just did an HDPARM Info on it.. came back fine? HDParm Info for /dev/sdb ST31500541AS_ /dev/sdb: ATA device, with non-removable media Model Number: ST31500541AS Serial Number: Firmware Revision: CC32 Transport: Serial 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: 2930277168 Logical/Physical Sector size: 512 bytes device size with M = 1024*1024: 1430799 MBytes device size with M = 1000*1000: 1500301 MBytes (1500 GB) cache/buffer size = unknown Nominal Media Rotation Rate: 5900 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: 192 Recommended acoustic management value: 254, 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 Power-Up In Standby feature set SET_FEATURES required to spinup after power up SET_MAX security extension * Automatic Acoustic Management feature set * 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) * Native Command Queueing (NCQ) * Phy event counters Device-initiated interface power management * Software settings preservation * SMART Command Transport (SCT) feature set * SCT Long Sector Access (AC1) * SCT LBA Segment Access (AC2) * SCT Error Recovery Control (AC3) * SCT Features Control (AC4) * SCT Data Tables (AC5) unknown 206[12] (vendor specific) Security: Master password revision code = 65534 supported not enabled not locked not frozen not expired: security count supported: enhanced erase 316min for SECURITY ERASE UNIT. 316min for ENHANCED SECURITY ERASE UNIT. Logical Unit WWN Device Identifier: 5000c500162ff1b4 NAA : 5 IEEE OUI : 000c50 Unique ID : 0162ff1b4 Checksum: correct

I have been an unraid user for 3 years now.. The array worked fine until i tried to go to 4.7 and i encountered the dreaded HPA problem.. So I decided to get all new hardware while i was at it... including a bunch of icydock 3-5 hot swap backplanes... well, one of the brand new backplanes died on me while i was adding a drive to the array.. The drive I was adding is #14.. looks like it succeeded but the system hung so i had to hard boot it! when it came back I had to unplug the faulty backplane and, #5 is the one that died totally... #11 i don't know what happened??.. it just suddenly decided it was invalid.. it was not connected to that backplane. am i dead in the water? I think if i can get #11 back I will be forever thankful.. anyway this is possible? here's what my array looks like now =( TIA, --mike syslog-2011-09-07.txt

I have a SB700 chipset motherboard and just upgraded to 4.4.. I'm looking at my syslog and am experiencing the same messages as previous posters: ata1: softreset failed (device not ready) ata1: failed due to HW bug, retry pmp=0 I also have two promise SATA PCI cards and the drives on those do not exhibit this error message--only the ones connected to the motherboard's SATA ports.. The software seems to be working fine however.. I did a parity check.. 0 errors.. I copied some files back to check performance and on my system at least it's about 15% faster on average writing files.. I was having all sorts of problems with adding and deleting sub folders on 4.3.3 and the problem seems to be fixed in 4.4.. Additionally, any folder with a sub folder in 4.3.3 used to always get the most current datestamp after a reboot so if i sorted by modified date they would always pop up 1st but now they keep their actual dates.. So I'm hesitant in going back to 4.3.3 because all my issues seem to be fixed ...

Ok thanks Joe.. The new parity just finished rebuilding this morning.. but I guess I'll take this time to upgrade from 4.3.3 to 4.4 and use the system over the weekend .. run a parity check on Monday before switching the two drives --mike

Thank you for this post.. It was very helpful as I am in process of upsizing my parity as well.. I have an additional question though.. Let's say the old 750GB parity in your example is not going to be a "new" drive but is going to replace an existing 320GB drive in the array.. Do I 1. shutdown the system after the parity has been rebuilt.. 2. Replace the 320 with the 750 3. turn unRAID back on and have it rebuild the drive? just checking for sanity sake thanks, --mike

I just did this.. BEFORE: I copied a large file off unRAID to a SATA drive on my Vista SP1 PC.. was copying at 20-22MB/s (that's what Vista said anyways) AFTER: copied same file off unRAID to same local SATA drive.. was copying at ~34MB/s So i saw an improvement in reads as well.. 34MB/s is more than enough bandwidth to stream media to my PC but I do still see better results if I stream the file from another PC on same network to my Vista machine rather than unRAID.. maybe Vista SP1 is still not optimal with Samba shares.. --mike