rattfink

Members
  • Posts

    22
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

rattfink's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Think I have a controller card/connectors going bad again. Here are the errors I see in the log: Whatever link ATA-9 is on is failing? May 13 09:37:08 Tower kernel: sas: ata9: end_device-1:0: dev error handler May 13 09:37:08 Tower kernel: ata9.00: ATA-9: WDC WD30EZRX-00D8PB0, WD-WMC4N0F1LJZN, 80.00A80, max UDMA/133 Whatever link ATA-10 is on is failing? May 13 09:37:08 Tower kernel: sas: ata10: end_device-1:1: dev error handler May 13 09:37:08 Tower kernel: ata10.00: ATA-8: WDC WD20EADS-00S2B0, WD-WCAVY0922071, 01.00A01, max UDMA/133 Whatever link ATA-11 is on is failing? May 13 09:37:08 Tower kernel: sas: ata11: end_device-1:2: dev error handler And then I also see this SATA link being limited to 1.5Gbps; this must be on a bad connector/SATA cable maybe? May 13 09:41:39 Tower kernel: ata5.01: limiting SATA link speed to 1.5 Gbps May 13 09:41:39 Tower kernel: ata5.01: exception Emask 0x10 SAct 0x0 SErr 0x4850002 action 0x0 frozen May 13 09:41:39 Tower kernel: ata5.01: SError: { RecovComm PHYRdyChg CommWake LinkSeq DevExch } May 13 09:41:39 Tower kernel: ata5.01: failed command: READ DMA EXT May 13 09:41:39 Tower kernel: ata5.01: cmd 25/00:00:3f:00:01/00:04:00:00:00/f0 tag 0 dma 524288 in May 13 09:41:39 Tower kernel: res 40/00:00:01:4f:c2/00:00:00:00:00/10 Emask 0x14 (ATA bus error) May 13 09:41:39 Tower kernel: ata5.01: status: { DRDY } May 13 09:41:39 Tower kernel: ata5.00: hard resetting link May 13 09:41:39 Tower kernel: ata5.01: hard resetting link syslog.txt
  2. I just let Unraid handle the designation of the TV/Movie files. Assuming your drives are SATA and not decade+ old IDE the speed will be fine. Here's My Folder Structure which is defined in CouchPotato: Movies -> [decades] -> 1950 -> 1960 -> 1970 -----> [name of movie] ---------------> Movie File -> 1980 -> 1990 -> etc...
  3. I reset (disconnected/reconnected) the two drives in question along with the cabling. Everything responding nicely after the first night; thanks for checking my syslog.
  4. unresponsive again... This is redic. Not sure what to do. Currently I can access the shares over the network but the website is unresponsive. Shouldn't the website be the one thing that's always up?
  5. My system becomes unresponsive after about 30-60mins uptime it seems. I disabled Sonarr and Plex plugins thinking those might be causing it and to free up RAM but this morning it's once again unresponsive. Attached is a syslog.txt. I also notice a message on the server screen when I login at the console something like "Make sure all modules are loaded for your kernal". I took some screenshots with my camera but turned out very blurry. If you think you need to see those messages (hopefully contained within the syslog anyways) let me know and I'll try and get better pictures. syslog.txt
  6. Finished pre-clearing new drive and raid is now rebuilding on new drive. What I couldn't figure out and wondering for future reference is how and is it possible to force a rebuild to the existing "red ball" drive? I couldn't find an option to force a rebuild.
  7. root@Tower:~# smartctl -a /dev/sdk smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.18.5-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green (AF, SATA 6Gb/s) Device Model: WDC WD30EZRX-00SPEB0 Serial Number: WD-WCC4ECYT5N92 LU WWN Device Id: 5 0014ee 20a890e1d Firmware Version: 80.00A80 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2 (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Tue Feb 24 17:52:28 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: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (38880) 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: ( 390) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x7035) 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 181 177 021 Pre-fail Always - 7950 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 124 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 1492 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 - 65 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 44 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1517 194 Temperature_Celsius 0x0022 130 119 000 Old_age Always - 22 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 SMART Error Log Version: 1 Warning: ATA error count 2553 inconsistent with error log pointer 4 ATA Error Count: 2553 (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 2553 occurred at disk power-on lifetime: 34 hours (1 days + 10 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 61 46 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 46 00 00 00 a0 08 1d+10:07:02.205 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 1d+10:07:02.185 IDENTIFY DEVICE c8 00 08 00 10 00 e0 08 1d+10:07:01.676 READ DMA ec 00 00 00 00 00 a0 08 1d+10:07:01.656 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 1d+10:07:01.636 SET FEATURES [set transfer mode] Error 2552 occurred at disk power-on lifetime: 34 hours (1 days + 10 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 61 08 00 10 00 e0 Device Fault; Error: ABRT 8 sectors at LBA = 0x00001000 = 4096 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 00 10 00 e0 08 1d+10:07:01.676 READ DMA ec 00 00 00 00 00 a0 08 1d+10:07:01.656 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 1d+10:07:01.636 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 1d+10:07:01.616 IDENTIFY DEVICE c8 00 08 00 10 00 e0 08 1d+10:07:01.107 READ DMA Error 2551 occurred at disk power-on lifetime: 34 hours (1 days + 10 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 61 46 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 46 00 00 00 a0 08 1d+10:07:01.636 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 1d+10:07:01.616 IDENTIFY DEVICE c8 00 08 00 10 00 e0 08 1d+10:07:01.107 READ DMA ec 00 00 00 00 00 a0 08 1d+10:07:01.086 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 1d+10:07:01.067 SET FEATURES [set transfer mode] Error 2550 occurred at disk power-on lifetime: 34 hours (1 days + 10 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 61 08 00 10 00 e0 Device Fault; Error: ABRT 8 sectors at LBA = 0x00001000 = 4096 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 00 10 00 e0 08 1d+10:07:01.107 READ DMA ec 00 00 00 00 00 a0 08 1d+10:07:01.086 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 1d+10:07:01.067 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 1d+10:07:01.047 IDENTIFY DEVICE c8 00 08 00 10 00 e0 08 1d+10:07:00.537 READ DMA Error 2549 occurred at disk power-on lifetime: 34 hours (1 days + 10 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 61 46 00 00 00 a0 Device Fault; Error: ABRT Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- ef 03 46 00 00 00 a0 08 1d+10:07:01.067 SET FEATURES [set transfer mode] ec 00 00 00 00 00 a0 08 1d+10:07:01.047 IDENTIFY DEVICE c8 00 08 00 10 00 e0 08 1d+10:07:00.537 READ DMA ec 00 00 00 00 00 a0 08 1d+10:07:00.517 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 1d+10:07:00.497 SET FEATURES [set transfer mode] 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:~# Yes I normally always run a preclear; actually running one now on new drive as possibly replacement but I guess I can't say 100% sure I ran preclear on the drive in question or not. So it sounds like what you're saying once a drive gets "RED BALL" for ANY reason unraid won't start using it again until a rebuild is executed or new config. Even if RED BALL was due to a faulty cable then a rebuild or new config would still need to be executed upon installing a new cable in order to remove the redball.
  8. Well the disk that is redball is a new 3TB which has only been running for maybe a week or 2. What are the steps to determine if this is indeed a BAD disk and I need to replace it or if it's some other problem. I'm sure the recommended solution to every red ball disk is NOT to just replace it and rebuild... Isn't this real problem with the disk in the syslog? I just don't see anything in the syslog I attached which provides information on what the problem with the disk is. Maybe the steps to determine if a RED BALL disk should be replaced is by executing a smart report and that'll determine the need to replace the disk or not.
  9. I have a couple disks with reallocated sectors I need to upgrade ASAP but of course this morning one of my disks redballed so need to figure out what's wrong with this before replacing the other disks with reallocated sectors. I'm running Unraid 6b14. Disk 1 is showing "Faulty" on the Dashboard page and Red Ball on the "Main" page in Unraid. syslog.txt
  10. I can telnet and have attached the syslog. I have a 500gb (disk 6) that is disappearing in unraid so I stop array and shutdown. Replace 500gb with 2TB disk and unraid won't start. If I put the 500gb back in unraid will start. https://dl.dropboxusercontent.com/u/27844309/syslog
  11. Back on unraid 4.7 I had Sickbeard with Sabnzb setup perfectly. After upgrading to Unraid v5.0 and installing Sab/Sickbeard using Influencers plugins I've been unable to get post-processing working 100%. Anyone know a good link to configuring post-processing for sickbeard/sab on Unraid v5.0? Currently after tv episodes are downloaded they're put directly into the base TV folder and not the corresponding [series]\[season#] folder. 1) Sickbeard sends nzb to Sab to download. 2) Sab downloads nzb assigning the TV category. 3) TV Category in Sab is setup to run sabToSickBeard.py script with a path set to "mnt/user/TV" Shouldn't the sabToSickBeard.py be taking the downloaded episode and copying it to the correct [series]\[season] folder?
  12. Correct I don't see the 30GB drive show up in the ls command. The 30GB drive does show up in the motherboard BIOS... After work I'll run a syslog and see if the Motherboard IDE controller is getting identified. The motherboard is a Supermicro C2SEA.
  13. /dev/disk/by-id: total 0 lrwxrwxrwx 1 root root 9 Aug 30 18:24 ata-WDC_WD1001FALS-00J7B0_WD-WMATV1032698 -> ../../sdf lrwxrwxrwx 1 root root 10 Aug 30 18:24 ata-WDC_WD1001FALS-00J7B0_WD-WMATV1032698-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 Aug 30 18:24 ata-WDC_WD20EADS-00R6B0_WD-WCAVY4300399 -> ../../sdb lrwxrwxrwx 1 root root 10 Aug 30 18:24 ata-WDC_WD20EADS-00R6B0_WD-WCAVY4300399-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Aug 30 18:24 ata-WDC_WD20EADS-00R6B0_WD-WCAVY4403879 -> ../../sda lrwxrwxrwx 1 root root 10 Aug 30 18:24 ata-WDC_WD20EADS-00R6B0_WD-WCAVY4403879-part1 -> ../../sda1 lrwxrwxrwx 1 root root 9 Aug 30 18:24 ata-WDC_WD20EADS-00R6B0_WD-WCAVY4428072 -> ../../sdc lrwxrwxrwx 1 root root 10 Aug 30 18:24 ata-WDC_WD20EADS-00R6B0_WD-WCAVY4428072-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 Aug 30 18:24 ata-WDC_WD5000AAKS-00TMA0_WD-WCAPW3910149 -> ../../sdd lrwxrwxrwx 1 root root 10 Aug 30 18:24 ata-WDC_WD5000AAKS-00TMA0_WD-WCAPW3910149-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 Aug 30 18:24 scsi-SATA_WDC_WD1001FALS-_WD-WMATV1032698 -> ../../sdf lrwxrwxrwx 1 root root 10 Aug 30 18:24 scsi-SATA_WDC_WD1001FALS-_WD-WMATV1032698-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 Aug 30 18:24 scsi-SATA_WDC_WD20EADS-00_WD-WCAVY4300399 -> ../../sdb lrwxrwxrwx 1 root root 10 Aug 30 18:24 scsi-SATA_WDC_WD20EADS-00_WD-WCAVY4300399-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Aug 30 18:24 scsi-SATA_WDC_WD20EADS-00_WD-WCAVY4403879 -> ../../sda lrwxrwxrwx 1 root root 10 Aug 30 18:24 scsi-SATA_WDC_WD20EADS-00_WD-WCAVY4403879-part1 -> ../../sda1 lrwxrwxrwx 1 root root 9 Aug 30 18:24 scsi-SATA_WDC_WD20EADS-00_WD-WCAVY4428072 -> ../../sdc lrwxrwxrwx 1 root root 10 Aug 30 18:24 scsi-SATA_WDC_WD20EADS-00_WD-WCAVY4428072-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 Aug 30 18:24 scsi-SATA_WDC_WD5000AAKS-_WD-WCAPW3910149 -> ../../sdd lrwxrwxrwx 1 root root 10 Aug 30 18:24 scsi-SATA_WDC_WD5000AAKS-_WD-WCAPW3910149-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 Aug 30 18:24 usb-SanDisk_U3_Cruzer_Micro_2400130F3C83899F-0:0 -> ../../sde lrwxrwxrwx 1 root root 10 Aug 30 18:24 usb-SanDisk_U3_Cruzer_Micro_2400130F3C83899F-0:0-part1 -> ../../sde1 /dev/disk/by-label: total 0 lrwxrwxrwx 1 root root 10 Aug 30 18:24 Kids -> ../../sdd1 lrwxrwxrwx 1 root root 10 Aug 30 18:24 RAID1 -> ../../sdf1 lrwxrwxrwx 1 root root 10 Aug 30 18:24 UNRAID -> ../../sde1 /dev/disk/by-path: total 0 lrwxrwxrwx 1 root root 9 Aug 30 18:24 pci-0000:00:1a.7-usb-0:2:1.0-scsi-0:0:0:0 -> ../../sde lrwxrwxrwx 1 root root 10 Aug 30 18:24 pci-0000:00:1a.7-usb-0:2:1.0-scsi-0:0:0:0-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 Aug 30 18:24 pci-0000:00:1f.2-scsi-0:0:0:0 -> ../../sdc lrwxrwxrwx 1 root root 10 Aug 30 18:24 pci-0000:00:1f.2-scsi-0:0:0:0-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 Aug 30 18:24 pci-0000:00:1f.2-scsi-1:0:0:0 -> ../../sdd lrwxrwxrwx 1 root root 10 Aug 30 18:24 pci-0000:00:1f.2-scsi-1:0:0:0-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 Aug 30 18:24 pci-0000:00:1f.2-scsi-4:0:0:0 -> ../../sdf lrwxrwxrwx 1 root root 10 Aug 30 18:24 pci-0000:00:1f.2-scsi-4:0:0:0-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 Aug 30 18:24 pci-0000:01:00.0-scsi-2:0:0:0 -> ../../sda lrwxrwxrwx 1 root root 10 Aug 30 18:24 pci-0000:01:00.0-scsi-2:0:0:0-part1 -> ../../sda1 lrwxrwxrwx 1 root root 9 Aug 30 18:24 pci-0000:01:00.0-scsi-3:0:0:0 -> ../../sdb lrwxrwxrwx 1 root root 10 Aug 30 18:24 pci-0000:01:00.0-scsi-3:0:0:0-part1 -> ../../sdb1 /dev/disk/by-uuid: total 0 lrwxrwxrwx 1 root root 10 Aug 30 18:24 0bcc8314-2774-4ba9-bcbe-81cbda36d903 -> ../../sda1 lrwxrwxrwx 1 root root 10 Aug 30 18:24 7EFAA9C1FAA975D5 -> ../../sdf1 lrwxrwxrwx 1 root root 10 Aug 30 18:24 8641-AE15 -> ../../sde1 lrwxrwxrwx 1 root root 10 Aug 30 18:24 88D84AAFD84A9B78 -> ../../sdd1 lrwxrwxrwx 1 root root 10 Aug 30 18:24 a369ab3b-bb7e-427a-b296-95de2348f0c9 -> ../../sdc1
  14. Running Unraid 4.5.6 Pro. Installed a 30GB WD IDE drive which is detected by bios but doesn't appear under the drop-down box under the Devices page in Unraid. Can't seem to find a solution for this... Maybe this is just an incompatible drive with Unraid?