odd1

Members
  • Posts

    27
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

odd1's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Yeah, I saw that too. I upgraded to the latest bios and the cpu is on the approved list but still no go...
  2. I started out with the a760g m2+ and a sempron 140. This setup works great and met my needs for a couple of years. Then I started buying tablets and found Plex. Now I need a processor with more muscle to handle transcoding duties. I settled on a phenom ii x4 910e. It is the fastest quad core running at 65w. According to biostar, it is supported. So I updated the bios and plugged it in. No dice. I get no post message or anything, just a blank screen. I've switched back to the sempron for now. Anybody have any ideas on what I need to do to make it work? I'm sure it has something to do with the bios but I haven't been able to figure it out. I emailed biostar but I thought I'd check with you guys too...
  3. Thanks! I didn't even think of that. I replaced the cable and the drive showed up right away. However, after starting the rebuilding parity process, it is taking a very long time and going extremely slow. Right now the speed is 164KB/s and the finish time is reported to be 244,000 minutes. This is what was happening to my last parity drive and the reason I replaced it (not the one I RMA'd, it was trashed). The very first time I hooked up the new drive and started the process, the speed was a normal 35MB/s give or take. That was with the old, evidently flaky, cable. Any ideas? Here is my syslog taken just now after changing the cable and starting the process early this morning... syslog-2012-02-08.txt
  4. Thanks for reminding me. I just brought the array back up and it still won't show up. Here is the syslog after powering up and starting the array: syslog-2012-02-07.txt
  5. I've run into a problem replacing this parity drive. I started building parity on the new drive after upgrading to 5.0 beta14. After about an hour I refreshed the page to see how far it had gotten The array was started and the parity was no longer building. Red circle and "not installed" next to the parity on the main page. I stopped the array and tried to choose the new drive as the parity drive but it does not show up in the drop down box. Only "unassigned" is there. I've tried restarting, powering down, unplugging the drive, starting back up and starting the array, powering back down plugging in the drive and starting up again but nothing seems to work to make the drive show back up. The drive shows up in the bios of my main pc. I can't access it 'cause that pc is running XP32 and can't see large drives over 2.1TB. Please help...
  6. Thanks all... Just upgraded to 5.0b14. Rebuilding Parity now...
  7. Will v4.7 just see 2.2TB and I loose the rest or will it not work at all?
  8. Hi all, Just RMA'd my 2TB WD green HD and they sent me a 2.5TB WD25EZRS. I am currently running UnRaid 4.7. Do I need to upgrade to 5.0 beta? Thanks,
  9. Fixed it. Did a parity check. Took two days to complete, corrected one sync error and now everything is running normally. Transfers to the array are now running 25-30MB/s. I'll keep an eye on the drive. Thanks to all who helped me track this down.
  10. That's what I was afraid of. This is a brand new drive! Less than 3 months old! Does the spin-up/spin-down process shorten the lives of these drives? I've had drives in my main PC (pre Unraid) that stayed up all the time and lasted for 5 years or more. Since I moved to unraid, I've lost 3 drives!
  11. Pardon my not understanding but can't you just use windows explorer? That's what I use to move files around...
  12. sdc is my parity drive. I did both a short and long SMART self test today and these are the results as reported in the status report: SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed: read failure 90% 5944 158494197 # 2 Short offline Completed: read failure 10% 5944 245286409 Could someone help me interpret this? The complete report: 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 WD20EADS-00W4B0 Serial Number: WD-WCAVY6087956 Firmware Version: 01.00A01 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: Exact ATA specification draft version not indicated Local Time is: Wed Jan 11 15:54:44 2012 CST 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: ( 121) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: (41580) 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 237 234 021 Pre-fail Always - 10125 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 434 5 Reallocated_Sector_Ct 0x0033 177 177 140 Pre-fail Always - 181 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 092 092 000 Old_age Always - 5952 10 Spin_Retry_Count 0x0032 100 100 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 - 23 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 8 193 Load_Cycle_Count 0x0032 136 136 000 Old_age Always - 193856 194 Temperature_Celsius 0x0022 120 116 000 Old_age Always - 32 196 Reallocated_Event_Count 0x0032 080 080 000 Old_age Always - 120 197 Current_Pending_Sector 0x0032 197 197 000 Old_age Always - 1001 198 Offline_Uncorrectable 0x0030 198 198 000 Old_age Offline - 753 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 184 000 Old_age Offline - 22 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: read failure 90% 5944 158494197 # 2 Short offline Completed: read failure 10% 5944 245286409 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.
  13. Here is my syslog from just now after the transfer to and from... syslog-2012-01-10.txt
  14. OK I cleaned up some stuff and moved some things around and no drive is near 100% any more. The problem is still there though. I've reset all routers and switches and rebooted both machines many times. It's not a network problem. I tested moving a 421MB file from the tower to my PC and it took 10 sec. The same file took 6 minutes to be moved back to the tower. It seems to only slow down during writes not reads. Anyone have any ideas? Thanks...
  15. All drives but my newly converted cache drive are reading 99-100% full. Could this be the problem? If so, is it just a matter of moving files from the full drives to the empty one or is there something more I need to do? Right now the same file is still copying and none of the other drives are even spinning, only the one semi-empty one... Oh! it just finished the copy. 5.45GB took 1:21:27! Thanks,