mcleanap

Ok. I am getting there. One thing I wanted to see is if I could re-use the other "failing" drives. Is that possible, or are these drives worthless now? I did a preclear on one of them to see what the results would be: ========================================================================1.15 == WDCWD20EARS-00MVWB0 WD-WCAZA8054351 == Disk /dev/sdg has been successfully precleared == with a starting sector of 64 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdg /tmp/smart_finish_sdg ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VA LUE Seek_Error_Rate = 100 200 0 ok 0 Temperature_Celsius = 115 123 0 ok 35 Current_Pending_Sector = 1 200 0 near_thresh 65535 No SMART attributes are FAILING_NOW 12 sectors were pending re-allocation before the start of the preclear. 18 sectors were pending re-allocation after pre-read in cycle 1 of 1. 65535 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 65535 sectors are pending re-allocation at the end of the preclear, a change of 65523 in the number of sectors pending re-allocation. 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. root@Tower:/boot#

One question. If I have removed the current parity and the array is stopped, how can I see the new data drive in order to copy the files back?

I was just about to come back and delete my idiotic post, but you beat me to it. Yep....just figured that out. For some reason, I kept reading Y for yes.

So....after 5 months, I finally purchased a few drives. I am trying to pre-clear one of the drives, and running into an issue. Pre-Clear unRAID Disk /dev/sdb ################################################################## 1.15 Device Model: TOSHIBA DT01ACA300 Serial Number: 255BRYBGS Firmware Version: MX6OABB0 User Capacity: 3,000,592,982,016 bytes Disk /dev/sdb: 3000.6 GB, 3000592982016 bytes 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Disk /dev/sdb doesn't contain a valid partition table ######################################################################## invoked as ./preclear_disk.sh /dev/sdb ######################################################################## (MBR 4k-aligned set. Partition will start on sector 64 for disks <= 2.2TB and se ctor 1 for disks > 2.2TB) Are you absolutely sure you want to clear this drive? (Answer Yes to continue. Capital 'Y', lower case 'es'): Y Clearing will NOT be performed root@Tower:/boot# Any idea why it would say "Clearing will NOT be performed"? In the log, it says "Tower kernel: sdb: unknown partition table"

Thank you to you both. I will now be on the hunt for 2 drives in the next week or so. I can refrain from writing to the server until this is resolved. I'll probably have a few more questions when I get started on this, but I should be good for now.

Wow....this is awesome, and exactly what I needed. I think I understand this a bit more now. So, currently looking for new drives. Could these be used? http://www.ncix.com/detail/wd-elements-4tb-desktop-external-bb-103285-1356.htm?affiliate_id=58025&click_id=1183544611 Sounds like they could be removed from their enclosures. They have the WD40EZRX in them.

Thanks Frank1940. A few questions. 1. After copying the files off of Disk 2, what should I do with that drive? Does it get tossed? Or can it be used again? 2. You said I need 2 more drives....is that replacing Disk 2 and Parity? What happens with both of the current drives? Again....are they garbage? 3. Once I copy off the files from Disk 2 (no, I don't have any room, but I may pick and choose what I keep from that disk as I do not need it all), then what happens? Do I mount both new drives, assign 1 to parity, and the other as a partition, then copy back those files? Thanks again!

Thanks dgaschk, however I am lost with some of this stuff. I was hoping for a more step 1, step 2, etc, kind of like this post: http://lime-technology.com/forum/index.php?topic=4068.msg91731#msg91731 I guess I am hoping for some magic too. Doing another parity check right now, and the drive errors are increasing.

I'm open to all suggestions. So what you are saying is that 2 drives are potentially falling? The parity plus 1 other? I currently do not run any backups and I honestly wouldn't even know how to back up this data. I basically set up this unraid server added some plugins and was essentially hands off the last 3 years. Looking for advice on how to proceed. You mentioned buying a 4tb to replace the parity. I can certainly do that but not sure what to do with the existing parity drive or the other problematic one. Thanks

I am also attaching a screen capture of the Smart View of the drives. I tried to attach it to the previous post, but I could not include additional attachments for some reason.

This is great! Thanks very much for the help. Should I just be running the short tests? I didn't even know about these tests, but I will run them now to see what results I get. I am attaching the Smart Test for the other drives. They seemed to all be completed without errors, but you mentioned about pending sector and on SDB I see 66 in pending (if I am reading that correctly). My question is, do I have any issues with the other drives? sdb.txt sdc.txt sdf.txt sdd.txt

smartctl -a -d ata /dev/sdg smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WCAZA8054351 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: Sat Jan 24 23:38:31 2015 EST 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: (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: (40260) 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 171 169 021 Pre-fail Always - 6408 4 Start_Stop_Count 0x0032 098 098 000 Old_age Always - 2361 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 059 059 000 Old_age Always - 30125 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 - 36 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 8 193 Load_Cycle_Count 0x0032 193 193 000 Old_age Always - 22200 194 Temperature_Celsius 0x0022 127 117 000 Old_age Always - 23 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 10 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 27 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 196 196 000 Old_age Offline - 1209 SMART Error Log Version: 1 ATA Error Count: 13 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 13 occurred at disk power-on lifetime: 30027 hours (1251 days + 3 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 68 a8 f1 e6 Error: UNC 8 sectors at LBA = 0x06f1a868 = 116500584 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 68 a8 f1 e6 08 35d+14:33:51.753 READ DMA c8 00 08 38 5c e2 e6 08 35d+14:33:51.721 READ DMA Error 12 occurred at disk power-on lifetime: 29912 hours (1246 days + 8 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 68 48 d4 ee Error: UNC 8 sectors at LBA = 0x0ed44868 = 248793192 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 68 48 d4 ee 08 30d+19:16:43.915 READ DMA ef 10 02 00 00 00 a0 08 30d+19:16:43.915 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 30d+19:16:43.912 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 30d+19:16:43.911 SET FEATURES [set transfer mode] Error 11 occurred at disk power-on lifetime: 29912 hours (1246 days + 8 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 68 48 d4 ee Error: UNC 8 sectors at LBA = 0x0ed44868 = 248793192 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 68 48 d4 ee 08 30d+19:16:41.206 READ DMA ef 10 02 00 00 00 a0 08 30d+19:16:41.206 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 30d+19:16:41.203 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 30d+19:16:41.202 SET FEATURES [set transfer mode] Error 10 occurred at disk power-on lifetime: 29912 hours (1246 days + 8 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 68 48 d4 ee Error: UNC 8 sectors at LBA = 0x0ed44868 = 248793192 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 68 48 d4 ee 08 30d+19:16:38.497 READ DMA ef 10 02 00 00 00 a0 08 30d+19:16:38.497 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 30d+19:16:38.494 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 30d+19:16:38.493 SET FEATURES [set transfer mode] Error 9 occurred at disk power-on lifetime: 29912 hours (1246 days + 8 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 08 68 48 d4 ee Error: UNC 8 sectors at LBA = 0x0ed44868 = 248793192 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 08 68 48 d4 ee 08 30d+19:16:35.788 READ DMA ef 10 02 00 00 00 a0 08 30d+19:16:35.788 SET FEATURES [Reserved for Serial ATA] ec 00 00 00 00 00 a0 08 30d+19:16:35.784 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 30d+19:16:35.784 SET FEATURES [set transfer mode] 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% 30116 218471296 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.

Wait....I think I am reading this wrong. Parity status shows: Last checked on Fri Jan 23 23:42:37 2015 EST, finding 0 errors. But for my parity drive, it shows: Temp. Size Free Reads Writes Errors parity WDC_WD20EARS-00MVWB0_WD-WCAZA8054351 (sdg) 1953514552 23°C 2 TB - 26192839 1041484 840 So I am not sure what those 840 errors are representing.

Thanks for the reply. There were no parity errors before as the were regular parity checks done prior to the upgrade. Last one that was done prior was 21 days ago, so perhaps there were parity errors during this time, but I doubt it. I don't shut down without stopping the array first, but before I ran the upgrade, it appeared that when I shut down the array, it was hanging, so I did had to shut down without knowing if the array was completely stopped or not. Could have caused the errors I suppose. In that case, what options do I have for correction? For the permissions....damn, I totally forgot about that. I noticed that part before signing off for the night and completely forgot before writing this post. I will try that, and it should work fine. Thanks.

I haven't really touched anything on my server in a long time...it was probably running for at least half a year without any intervention. Lately, I wanted to see if I could get Plex running on it and since I was still on 4.7 I decided I would try upgrading to 5.0.6. It seemed to work fine, however after doing the first parity check it looks like there are 840 errors. It says parity is valid though. Should I be worried? Anything for me to do or check? One other thing is that on my windows 7, it seems like I cannot get access to any of my shares. It will always give me access denied, but from my ATV2, the shares still seem to work fine. Any ideas? Thanks

Hello, I have the Monthly Parity Check package installed and for the last year has worked great. I noticed though that I see that it has not been run in 67 days. What could have caused this to stop operating and what can I do to fix it? For now, I just ran the parity check manually. Thanks!

Ok, I think I have most of it figured out. There was another post that basically did the same thing. #!/bin/bash # Extract root's crontable. crontab -u root -l | grep -q "/boot/scripts/scheduler.sh" > /tmp/crontab.tmp grep -q "/boot/scripts/scheduler.sh" /tmp/crontab.tmp 1>/dev/null 2>&1 if [ "$?" = "1" ] then # Append new entries to root's crontable cat <<-EOF >> /tmp/crontab.tmp # Schedule wget : #59 * * * * /boot/scripts/scheduler.sh >/dev/null 2>&1 EOF # Update root's crontable. crontab /tmp/crontab.tmp -u root # If we don't copy the new crontab to "root-", the additions will be deleted # if you use the management interface to make any changes. cp /tmp/crontab.tmp /var/spool/cron/crontabs/root- fi rm /tmp/crontab.tmp So then in scheduler.sh, I have a bunch of wget to the websites I want to fire off at the 59th minute of every hour (just an example). So to get this to stay active on a reboot, could I just add "/boot/scripts/cron_web_scheduler.sh" in the GO file? Is there a quick way to see what cron jobs are active, and a way to easily remove jobs?

Thanks for the info guys. Being a windows guy I am not really sure how to set this up. Any clues? What do I do with wget and at? How do I set up a schedule?

By firing off a URL I mean connect to a web page on the Internet that may run some code. Basically my shared web hosting charges a lot for scheduled tasks so I thought I could run these from unraid.

Would anyone be able to tell me if scheduling a cron job to fire off a URL is possible in unRAID? If so, would anyone be able to show me how to do so? Thanks!

I have a pretty basic setup. Running Intel Core i3 2100 on a ASUS P8H67-M LX MB. No controller cards. Just 4 drives at the moment.

Looks like I will stick with 4.7. Unless it's buried deep, I don't see much about hardware issues in any of the announcement threads, at least not in the OP or release notes. I'm assuming it's not obvious and made by posters who have had issues with certain versions.

I've tried the mySQL central database before, but I found it sluggish and slow. I was hoping Plex would be as efficient as I have now with one library on ATV2. I was more interested in hearing about which beta version has been the most stable.

I have been using unRAID 4.7 since July, and everything has been smooth. No issues whatsoever. I am using ATV2 with XBMC to stream content from the unRAID server, but I recently purchased a second ATV2, and would like a way to synchronize libraries on each device. From what I have read, PLEX on unRAID with PleXBMC would give me what I need. The only issue is that in order to run PLEX on unRAID, I would have to install one of the beta releases. Would anyone be able to recommend which beta version I should upgrade to? If any? Thanks in advance.

Yes, I am running an all n wireless network right now, and the 7-8 MB/s is fairly consistent. I just ran some more tests, both reading files from unRAID to the same PC. Powerline: 7.5 MB/s which seemed to keep getting higher as it went on. 7.54 MB/s was the highest I saw, but it started at 2 MB/s, and just slowly crept up on a 1.2 GB file transfer. WIFI: 7.9 MB/s, but stayed around that the whole time, but initially started at 11 MB/s. It's very odd that Powerline results in lower speeds. Both powerline adapters are plugged into the wall. Buffering is really inconsistent. Sometimes, it happens once, maybe at the beginning, and then maybe once more throughout the rest of the movie/show. Other times, it's unwatchable, as it does it every 30 seconds for a 5 minute period. Can't wait for the gigabit network to be done in a few months. Unfortunately, we won't be able to do it upstairs, which is where I was hoping this Powerline would work well.