brandon12777

I'm at a loss here. I followed the instructions below..... You must replace a failed disk with a disk which is as big or bigger than the original and not bigger than the parity disk. If the replacement disk is larger than your parity disk, then the system permits a special configuration change called swap-disable. For swap-disable, you use your existing parity disk to replace the failed disk, and you install your new big disk as the parity disk: Stop the array. Power down the unit. Replace the parity hard disk with a new bigger one. Replace the failed hard disk with you old parity disk. Power up the unit. Start the array. When you start the array, the system will first copy the parity information to the new parity disk, and then reconstruct the contents of the failed disk. After that when I powered the server back on it wouldn't connect to the network at all. It no longer shows as a client under my router's GUI. I changed the drives back but still the same issue. This is a headless server that has been up and running great for years. I thought I was in for a simple replacement of a failed drive and bigger parity. Let me know what you guys recommend. Thanks, Brandon

I did run it when upgrading as the instructions indicated. Since you brought it up I thought anything worth running is worth running again just to be sure. After that it now seems to be working, Utorrent was able to recheck the torrent and is saving to the UnRaid. Pretty weird that the first time didnt fully "take"? and Utorrent was the only thing that was having problems. Either way happy to have it fixed, thank you mr-hexen! Thanks, Brandon

Yes Windows 7, checked Credential Manager and there are no UnRaid related credentials there. Thanks, Brandon

I just upgraded from 4.7 to 5.0.4 everything went well except my torrent client. I normally just use Utorrent on my PC and save to my unraid server, been working flawlessly for 4+ years. Now all the sudden my Utorrent errors out when I try to save to any torrents to my unraid. This is the specific error I get "Error: The system cannon find the path specified. (WriteToDisk)" I get that one then if I try to force a recheck on a torrent that was already in progress I get "Error: Files missing from job. Please recheck." This happens when trying a mapped drive path or the network address and to anyone of my Unraid user shares. It seems the be the only thing not working well everything else regarding accessing, copying, etc. with the raid seems to be working fine. Please let me know what I did wrong. Thanks, Brandon

up

After 2-5 min of manually restarting server I can't use telnet when I try to connect with telnet it just closes. Cant get a updated syslog but all my data can still be accessed. edit: Ok so telnet wasnt working when i tried to login to "tower" like normal but when I used the actual IP it did work so here is a updated syslog. syslog22.zip

Hmmmm after 2-5 min of manually restarting the server I cant access it using telnet either, but can still access my data just fine over the network.

here it is, had to get it through telenet. Version 4.7 syslog.txt

Both the stock and unmenu Web gui wont load but the server seems to be functioning normally and I can access it via telnet. Ideas? Thanks, Brandon Edit: So I am still getting the issue where I can't access the Web Gui but I knew I needed to replace Disk 4 so I went ahead and replaced it hoping it would take care of the issue now I still have the original issue and I seemed to have broke my array cant see any of my data over the network. Here is a new syslog after the drive replacement if someone could save me here and get help me get the GUI back so I can swap drives and be done that would be great. Thanks, Brandon syslog.txt

Statistics for /dev/sde 00D_WD-WCAU41457138 smartctl -a -d ata /dev/sde 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 === Model Family: Western Digital Caviar Green family Device Model: WDC WD10EAVS-00D7B0 Serial Number: WD-WCAU41457138 Firmware Version: 01.01A01 User Capacity: 1,000,203,804,160 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Mon Apr 25 16:01:58 2011 MST 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 See vendor-specific Attribute list for marginal Attributes. General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 121) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: (24000) 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: (0x303f) 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 163 161 021 Pre-fail Always - 6841 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 711 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 051 Old_age Always - 0 9 Power_On_Hours 0x0032 079 078 000 Old_age Always - 15912 10 Spin_Retry_Count 0x0032 100 100 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 051 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 250 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 5 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 711 194 Temperature_Celsius 0x0022 120 101 000 Old_age Always - 30 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 192 192 000 Old_age Always - 1327 198 Offline_Uncorrectable 0x0030 196 192 000 Old_age Offline - 741 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 175 001 051 Old_age Offline In_the_past 3386 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: read failure 90% 15871 513270 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.

So my server has been up for 3 months or so running flawlessly, but that last day or so it was being weird in that it would give me page not found(or take a VERY long time) when trying to find tower or tower:8080. So I thought I might restart it and see if that helped any. Upon restart it began a parity check that is giving me TONS of errors on drive4 50k+ with 37% done, its also going slow on the check 20mb/s instead of the normal 45-47mb/s. The server is still working fine but I don't understand whats going on with that drive. The drive in question is a 1tb WD green EAV drive. MB:C2SEE, just 6 drives 4 2tb EARs and 2 of the 1tb EAVS. unraid 4.7 Thanks, Brandon syslog-2011-04-23.zip

Ok another update. Got everything off the problem drive(woohoo). Formatted in windows works totally fine, and all data was good also. This is where is gets weird put it back in the unraid box and it STILL does the exact same this as before as shown in the pictures. Its important to remember this drive it work perfectly fine for days until shut down to add more drives. As part of trying to figure out the problem I switched the 7/8 pin jumper with another working EARS drive just in case the jumper was bad for some reason and still same result. Now after reading the input from burtjr I was thinking it might be some jumper issue so I removed the jumper and it boots perfectly! I replace it with another jumper and it wont boot again! It was working in windows with the 7/8 jumper in place. Do I have to have that jumper in place for it to work properly? Because at this point it wont seem to work with it no matter what, but at least boots to unraid without it. Thanks, Brandon

Yes it is a WD Green EARS drive and it does have the 7/8 jumper in place I even switched jumpers from another known working drive because I had thought the same thing might be possible. The sequence continues nonstop as best I can tell I have let it try for 5+ min before. I am going to try to get as much data off it as possible and then preclear it as suggested.

Kaygee, When it was working in my unraid box it was plugged directly into PSU sata plug and directly to the MOBO with SATA cable. I did try multiple SATA ports, cables and PSU cables even trying a PSU 4 pin with sata adapter and each time with the same result when ever the problem drive was installed. PSU: Corsair VX450 brand new and the drive is a brand new 2tb WD green ears first time powered when it was working with unraid initially. The screen shots are from my main Win7 box while trying to boot to a ubuntu flash drive and the errors are exactly the same on that machine while trying to boot ubuntu. That computer has a different MOBO but drive still attached directly to MOBO and PSU(corsair HX620). It shows ata2 I assume because that is the port the drive in question is plugged into. ohlwiler, Thanks for that driver using it and YAReg I can see all the drive's data and successfully transferred one 5gb mkv file off that played fine so it looks like the drive is somewhat working?

Ok guys some more information for you detectives. Memtest 17 passes for 10 hours no errors. Plugged the drive causing the issue into my WIN7 machine seems to be detected fine shows up under storage manager. I booted to a Ubuntu USB drive my thinking being that I was going to try to get the data off this drive and while Ubuntu was booting I got the same errors and boot loop that I get when trying to boot unraid with this drive installed. I took pictures of the errors maybe you can make some sense of them. http://picasaweb.google.com/brandon12777/UNRAID# So should I give up on this drive(or at least getting data off it)? Should I try to format it in windows and see if it works fully? Thanks again, Brandon