GFOviedo

The guide link doesn't work anymore. Any other guides available? I've been searching for a few days now. If your question is about setting up the script for Sickbeard to work with Sab, might I suggest trying out Sonarr. Sonarr will not need a script to work with Sab as it will interact using Sab's API and the category setting. I usually do all the TV Shows download by hand. However, I am trying to set something up where this gets down automatically. A friend of mine advised me to use sickbeard, Sab and couchpotato to accomplish this. So, I've been trying to find a "HOW TO" thread for a newbie, but it appears this doesn't exist.

The guide link doesn't work anymore. Any other guides available? I've been searching for a few days now.

I use both Kodi and Plex. It's pretty simple to change the poster / background if it is wrong. However, I've been using the following name format for movies NAME OF MOVIE (YEAR) and for TV shows NAME OF SHOW SxxExx. I've had both Kodi and Plex not being able to scrape a few movie, but it was easy to edit. I use Kodi to stream movie to my HTPC and Plex to stream out side network. My family and friends love Plex!

I believe I've got two from my current server server. The only issue with them is one of the bays led doesn't light up. Otherwise they are fully functional. Reason for selling is that my 1.5 year keeps opening the bay's while the server is on. 3 of my drive have gone bad, and now I've got a 4th one to replace. Let me know if you are interested. I'm located in Visalia, Ca 93277.

I agree that seems like it should do it but it actually doesn't. Click on the Plex docker icon and select Restart. That will force it to go get the newer version and install it. Takes a minute or two to finish before the Plex server admin page will again be available so you can check if the version is up-to-date. Actually I just did the update a few minutes ago. I clicked on the "update ready" link. Another window came up with the update status complete. I went ahead and rebooted to be on the safe side, and it's working fine.

How did you update Plex in Docker? You should have just restarted the Plex docker and it will update itself to latest version. Don't update from within Plex. I went to the docker section and next to the plex icon had an update link. I clicked on it and it did the update.

I've been using Docker / Plex for a while now. I went ahead and updated to the latest Plex version. Thereafter, everyone in my family started calling me because they couldn't access Plex. Now, I'm doing some research, and found that I can't start Plex via Docker at all. Then I went ahead and re-booted my UnRaid server, and Plex started by itself. It appears that you have to reboot after updating Plex. I never rebooted before.

I had to turn off password protection for network sharing under the Network and Sharing Center / All Network option.

The only way to verify that would be to try one of the PCI NICS. It looks like monkeymajik may be at the point of "absolutely have to" with a PCI NIC to isolate the issue. Agreed, will power down array now and try. The PCI NICs are a completely different chipset, so I'm fairly sure they will work fine. I was just hoping I could get the onboard working again with a different driver. I had a similar issue with my onboard as well. I ended up with a PCI Intel NIC and fixed the issue.

I was looking at your inventory. Does the quantity of 0 mean that you don't have any Norco SS-500? Also the Zotac HTPC is that being sold at MSRP?

Reduced to $60 $55 lower 48 states.

Shipping and PayPal fee included. I just posted that cause it was done to me in other sales.

Thanks, but it is a SASLP. It says on it.

I've got a AOC-SASLP-MV8 for $70shipping and paypal fees included. Pictures REDUCED TO $60 $55 $40 shipped lower 48 states.

What capacity were those? According to this is seems like the 3TB are terrible, but 4Tb don't seem out of line with the rest of the failure rate. https://www.backblaze.com/blog/best-hard-drive/ Anecdotally, what you are saying has been echoed in reviews, forums, etc. Knock on wood, I have had good luck with Seagates, but those are all 2TB or 4TB. Having Seagate say it is good, but unraid say it isn't, seems really frustarating. I know with my WD, it would report good in a short test, but bad in the long test. I looked at the Reds, it looks like the standard red has 3 years. The red pros have 5 years. Right now on amazon for a 4TB, it is $154 vs. $218 for the pro. (green is $135 with 2 year warranty). That's $19 for an additional year (year 3), and then another $64 additional to get 2 more to year 5. So that's $83 to go from 2 years to 5 years. Assuming you never loose data, one could look at it as would I be able to buy a new 4Tb drive for $83 in 5 years from now... flips I've had one 3TB and 2 2TB Seagates go bad. All the WD's green drive are still going strong, including a Samsung drive. One of my Hitachi 3TB drives has some relocated sectors. So, I'm probably going to have to replace it soon.

The last 3 drives that have failed in my array have been Seagates. One of them is still in warranty. However, whenever I've ran the Seagate software to see if the drive is bad, and it comes back as a good drive. I've pre-cleared the drive again, installed it in the array, and a few days later it had a red x next to it. I don't think I will be buying Seagates drives. I'm trying to stick with WD red drives now. That 5 year warranty is a must for me now.

So, I've been dealing with some family issues at the moment. So, I haven't had time to get back to this. However, I just turned on my server, and it told me that the Hitachi hdd was not install. I stopped the array, and I was able to pick the Hitachi hdd this time. Now, it is rebuilding the array. This is weird because before, the Hitachi hdd was not on the list, and I wasn't able to chose it. I've attached a system.log this time. Thanks for all the help! tower-syslog-20150812-2026.zip

The server is off at the moment since I had to go to work, and I just got home. I will turn it back on and get a system log. I completely forgot to include one.

Thanks, I guess it is call Shrink Array! Now, the new issue. When I brought up the GUI, now Disk 1 has a red X, and under it says Not Installed. I stopped the array, and Disk 1 (Hitachi) isn't on the list anymore. WTF!

Using UnRaid 6.0.1. So, I've got this Seagate HDD that UnRaid said was bad. I ran a smart report twice and nothing was found bad with it. I ran the Seagate software to see if anything was wrong with it, and it didn't find anything wrong with it. So, I pre-cleared it again, and added it back to the array. Well, today I am trying to access my server, and I can't. It too 30 min to finally get access to the GUI, and I noticed that same drive had an red X. The drive at the moment is empty and has no data in it. I was wondering if I can remove the hard drive from the array, and re-start the array with out that hard drive? If it is possible what's the process?

Awesome. Thanks for all the help!

So the question now becomes, are they good enough to be added back to my array? Would you trust them?

This is the second drive (sdm) report via telnet. Tower login: root Linux 4.0.4-unRAID. Last login: Thu Jul 16 16:38:34 -0700 2015 on /dev/pts/0 from GusGus. root@Tower:~# smartctl -s on /dev/sdm smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.0.4-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF ENABLE/DISABLE COMMANDS SECTION === SMART Enabled. root@Tower:~# smartctl -a /dev/sdm smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.0.4-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Barracuda Green (AF) Device Model: ST2000DL003-9VT166 Serial Number: 5YD515ED LU WWN Device Id: 5 000c50 03e1bb59e Firmware Version: CC32 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Size: 512 bytes logical/physical Rotation Rate: 5900 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Thu Jul 16 16:43:24 2015 PDT 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: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 612) 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 329) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x30b7) 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 119 099 006 Pre-fail Always - 220873032 3 Spin_Up_Time 0x0003 091 088 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 099 099 020 Old_age Always - 1990 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 066 060 030 Pre-fail Always - 4636190 9 Power_On_Hours 0x0032 074 074 000 Old_age Always - 23117 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 658 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 099 000 Old_age Always - 1 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 073 054 045 Old_age Always - 27 (Min/Max 25/27) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 93 193 Load_Cycle_Count 0x0032 099 099 000 Old_age Always - 2039 194 Temperature_Celsius 0x0022 027 046 000 Old_age Always - 27 (0 17 0 0 0) 195 Hardware_ECC_Recovered 0x001a 031 006 000 Old_age Always - 220873032 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 - 124523986816675 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 2405191976 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 2800156465 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. root@Tower:~#

This is what I get running smart reports via Putty / Telnet for the first drive (sdl). I'm not really sure what I am looking for that shows this drive is bad / faulty. So, if someone can help me it would be awesome. Tower login: root Linux 4.0.4-unRAID. Last login: Thu Jul 16 16:36:15 -0700 2015 on /dev/pts/0 from GusGus. root@Tower:~# smartctl -s on /dev/sdl smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.0.4-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF ENABLE/DISABLE COMMANDS SECTION === SMART Enabled. root@Tower:~# smartctl -a /dev/sdl smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.0.4-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Barracuda Green (AF) Device Model: ST2000DL003-9VT166 Serial Number: 5YD3XDFE LU WWN Device Id: 5 000c50 038bf183d Firmware Version: CC32 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Size: 512 bytes logical/physical Rotation Rate: 5900 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Thu Jul 16 16:39:08 2015 PDT 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: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 612) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off supp ort. 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 336) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x30b7) 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 - 85344960 3 Spin_Up_Time 0x0003 092 089 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 094 094 020 Old_age Always - 6265 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 067 060 030 Pre-fail Always - 5418053 9 Power_On_Hours 0x0032 075 075 000 Old_age Always - 22225 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 642 183 Runtime_Bad_Block 0x0032 001 001 000 Old_age Always - 1844 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 099 000 Old_age Always - 1 189 High_Fly_Writes 0x003a 099 099 000 Old_age Always - 1 190 Airflow_Temperature_Cel 0x0022 074 054 045 Old_age Always - 26 (0 11 26 24 0) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 92 193 Load_Cycle_Count 0x0032 097 097 000 Old_age Always - 6328 194 Temperature_Celsius 0x0022 026 046 000 Old_age Always - 26 (128 0 0 0 0) 195 Hardware_ECC_Recovered 0x001a 019 005 000 Old_age Always - 85344960 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 198 000 Old_age Always - 1848 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 128801774243482 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 816113232 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 2634538107 SMART Error Log Version: 1 ATA Error Count: 1 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 1 occurred at disk power-on lifetime: 1329 hours (55 days + 9 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 -- -- -- -- -- -- -- 04 51 00 98 ee 00 00 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ea 00 00 00 00 00 a0 00 4d+13:38:26.648 FLUSH CACHE EXT b0 d0 01 00 4f c2 00 00 4d+13:38:13.182 SMART READ DATA b0 d8 00 01 4f c2 00 00 4d+13:38:13.182 SMART ENABLE OPERATIONS e5 00 00 00 00 00 00 00 4d+13:38:13.182 CHECK POWER MODE e3 00 00 00 00 00 00 00 4d+13:38:13.131 IDLE 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% 22204 - 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.

I'm currently using UnRaid version 6.0.1. The plugin I'm running at the moment is Plex Server, and the whatever is pre-install with UnRaid OS. So, several weeks ago, my 1 year old figure out how to remove my hard drive from my server's supermicro / norco cages. Two of those drives appeared to be faulty according to the UnRaid's Dashboard status. Therefore, I replaced them with 3 TB hard drives just to be on the safe side. However, I just finished pre-clearing one of the faulty drives, and it didn't show any errors. So, now I am in the process of pre-clearing the second drive. My question is, would pre-clearing a faulty drive show if it is faulty? Or would it pass pre-clear even if it is faulty? Or would only finished pre-clearing if it isn't faulty? I'm going to do a smart report for both drives as well. Thanks for any help! preclear_finish_5YD515ED_2015-07-16.txt