May 23, 201115 yr Running unraid 4.6. When watching anime or tv shows, every couple of episodes there is a 5-15 second pause before it resumes. In my syslog I have this: May 21 21:21:42 Namek ifplugd(eth0)[1373]: Link beat detected. (Network) May 22 11:19:01 Namek kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) May 22 11:19:01 Namek kernel: ata6.00: failed command: CHECK POWER MODE (Minor Issues) May 22 11:19:01 Namek kernel: ata6.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0 (Drive related) May 22 11:19:01 Namek kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) (Errors) May 22 11:19:01 Namek kernel: ata6.00: status: { DRDY } (Drive related) May 22 11:19:01 Namek kernel: ata6: hard resetting link (Minor Issues) May 22 11:19:02 Namek kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) May 22 11:19:02 Namek kernel: ata6.00: configured for UDMA/133 (Drive related) May 22 11:19:02 Namek kernel: ata6: EH complete (Drive related) May 22 12:21:36 Namek kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) May 22 12:21:36 Namek kernel: ata6.00: failed command: CHECK POWER MODE (Minor Issues) May 22 12:21:36 Namek kernel: ata6.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0 (Drive related) May 22 12:21:36 Namek kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) (Errors) May 22 12:21:36 Namek kernel: ata6.00: status: { DRDY } (Drive related) May 22 12:21:36 Namek kernel: ata6: hard resetting link (Minor Issues) May 22 12:21:36 Namek kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) May 22 12:21:36 Namek kernel: ata6.00: configured for UDMA/133 (Drive related) May 22 12:21:36 Namek kernel: ata6: EH complete (Drive related) May 22 12:33:38 Namek kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) May 22 12:33:38 Namek kernel: ata6.00: failed command: CHECK POWER MODE (Minor Issues) May 22 12:33:38 Namek kernel: ata6.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0 (Drive related) May 22 12:33:38 Namek kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) (Errors) May 22 12:33:38 Namek kernel: ata6.00: status: { DRDY } (Drive related) May 22 12:33:38 Namek kernel: ata6: hard resetting link (Minor Issues) May 22 12:33:38 Namek kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) May 22 12:33:38 Namek kernel: ata6.00: configured for UDMA/133 (Drive related) May 22 12:33:38 Namek kernel: ata6: EH complete (Drive related) May 22 12:38:39 Namek kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) May 22 12:38:39 Namek kernel: ata6.00: failed command: CHECK POWER MODE (Minor Issues) May 22 12:38:39 Namek kernel: ata6.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0 (Drive related) May 22 12:38:39 Namek kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) (Errors) May 22 12:38:39 Namek kernel: ata6.00: status: { DRDY } (Drive related) May 22 12:38:39 Namek kernel: ata6: hard resetting link (Minor Issues) May 22 12:38:39 Namek kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) May 22 12:38:39 Namek kernel: ata6.00: configured for UDMA/133 (Drive related) May 22 12:38:39 Namek kernel: ata6: EH complete (Drive related) May 22 12:46:40 Namek kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) May 22 12:46:40 Namek kernel: ata6.00: failed command: CHECK POWER MODE (Minor Issues) May 22 12:46:40 Namek kernel: ata6.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0 (Drive related) May 22 12:46:40 Namek kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) (Errors) May 22 12:46:40 Namek kernel: ata6.00: status: { DRDY } (Drive related) May 22 12:46:40 Namek kernel: ata6: hard resetting link (Minor Issues) May 22 12:46:40 Namek kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) May 22 12:46:40 Namek kernel: ata6.00: configured for UDMA/133 (Drive related) May 22 12:46:40 Namek kernel: ata6: EH complete (Drive related) May 22 13:35:54 Namek kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) May 22 13:35:54 Namek kernel: ata6.00: failed command: CHECK POWER MODE (Minor Issues) May 22 13:35:54 Namek kernel: ata6.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0 (Drive related) May 22 13:35:54 Namek kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) (Errors) May 22 13:35:54 Namek kernel: ata6.00: status: { DRDY } (Drive related) May 22 13:35:54 Namek kernel: ata6: hard resetting link (Minor Issues) May 22 13:35:54 Namek kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) May 22 13:35:54 Namek kernel: ata6.00: configured for UDMA/133 (Drive related) May 22 13:35:54 Namek kernel: ata6: EH complete (Drive related) May 22 16:09:04 Namek kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) May 22 16:09:04 Namek kernel: ata6.00: failed command: CHECK POWER MODE (Minor Issues) May 22 16:09:04 Namek kernel: ata6.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0 (Drive related) May 22 16:09:04 Namek kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) (Errors) May 22 16:09:04 Namek kernel: ata6.00: status: { DRDY } (Drive related) May 22 16:09:04 Namek kernel: ata6: hard resetting link (Minor Issues) May 22 16:09:04 Namek kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) May 22 16:09:04 Namek kernel: ata6.00: configured for UDMA/133 (Drive related) May 22 16:09:04 Namek kernel: ata6: EH complete (Drive related) May 22 18:49:04 Namek kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) May 22 18:49:04 Namek kernel: ata6.00: failed command: CHECK POWER MODE (Minor Issues) May 22 18:49:04 Namek kernel: ata6.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0 (Drive related) May 22 18:49:04 Namek kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) (Errors) May 22 18:49:04 Namek kernel: ata6.00: status: { DRDY } (Drive related) May 22 18:49:04 Namek kernel: ata6: hard resetting link (Minor Issues) May 22 18:49:05 Namek kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) May 22 18:49:05 Namek kernel: ata6.00: configured for UDMA/133 (Drive related) May 22 18:49:05 Namek kernel: ata6: EH complete (Drive related) May 22 19:21:37 Namek kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) May 22 19:21:37 Namek kernel: ata6.00: failed command: CHECK POWER MODE (Minor Issues) May 22 19:21:37 Namek kernel: ata6.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0 (Drive related) May 22 19:21:37 Namek kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) (Errors) May 22 19:21:37 Namek kernel: ata6.00: status: { DRDY } (Drive related) May 22 19:21:37 Namek kernel: ata6: hard resetting link (Minor Issues) May 22 19:21:37 Namek kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) May 22 19:21:37 Namek kernel: ata6.00: configured for UDMA/133 (Drive related) May 22 19:21:37 Namek kernel: ata6: EH complete (Drive related) Apr 25 21:32:54 Namek emhttp: shcmd (26): rm /etc/samba/smb-shares.conf >/dev/null 2>$stuff$1 (Other emhttp) Apr 25 21:32:54 Namek emhttp: _shcmd: shcmd (26): exit status: 1 (Other emhttp) Apr 25 21:32:54 Namek emhttp: shcmd (27): cp /etc/exports- /etc/exports (Other emhttp) Apr 25 21:32:54 Namek emhttp: shcmd (28): mkdir /mnt/user (Other emhttp) Apr 25 21:32:54 Namek emhttp: shcmd (29): /usr/local/sbin/shfs /mnt/user -o noatime,big_writes,allow_other,default_permissions (Other emhttp) Apr 25 21:32:55 Namek shfs: duplicate object: /mnt/disk3/./.DS_Store (Minor Issues) Apr 25 21:32:55 Namek shfs: duplicate object: /mnt/disk4/./.DS_Store (Minor Issues) Apr 25 21:32:55 Namek emhttp: shcmd (30): killall -HUP smbd (Minor Issues) Apr 25 21:32:55 Namek emhttp: shcmd (31): /etc/rc.d/rc.nfsd restart | logger (Other emhttp) Apr 25 21:32:57 Namek kernel: ata7.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen (Errors) Apr 25 21:32:57 Namek kernel: ata7.00: irq_stat 0x08000000, interface fatal error (Errors) Apr 25 21:32:57 Namek kernel: ata7: SError: { UnrecovData Handshk } (Errors) Apr 25 21:32:57 Namek kernel: ata7.00: failed command: WRITE DMA EXT (Minor Issues) Apr 25 21:32:57 Namek kernel: ata7.00: cmd 35/00:00:4f:9d:04/00:04:00:00:00/e0 tag 0 dma 524288 out (Drive related) Apr 25 21:32:57 Namek kernel: res 50/00:00:4e:9d:04/00:00:00:00:00/e0 Emask 0x10 (ATA bus error) (Errors) Apr 25 21:32:57 Namek kernel: ata7.00: status: { DRDY } (Drive related) Apr 25 21:32:57 Namek kernel: ata7: hard resetting link (Minor Issues) Apr 25 21:32:57 Namek kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) Apr 25 21:32:57 Namek kernel: ata7.00: configured for UDMA/133 (Drive related) Apr 25 21:32:57 Namek kernel: ata7: EH complete (Drive related) Apr 25 21:32:57 Namek kernel: ata7.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen (Errors) Apr 25 21:32:57 Namek kernel: ata7.00: irq_stat 0x08000000, interface fatal error (Errors) Apr 25 21:32:57 Namek kernel: ata7: SError: { UnrecovData Handshk } (Errors) Apr 25 21:32:57 Namek kernel: ata7.00: failed command: WRITE DMA EXT (Minor Issues) Apr 25 21:32:57 Namek kernel: ata7.00: cmd 35/00:00:4f:c4:04/00:04:00:00:00/e0 tag 0 dma 524288 out (Drive related) Apr 25 21:32:57 Namek kernel: res 50/00:00:4e:c4:04/00:00:00:00:00/e0 Emask 0x10 (ATA bus error) (Errors) Apr 25 21:32:57 Namek kernel: ata7.00: status: { DRDY } (Drive related) Apr 25 21:32:57 Namek kernel: ata7: hard resetting link (Minor Issues) Apr 25 21:32:58 Namek kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) Apr 25 21:32:58 Namek kernel: ata7.00: configured for UDMA/133 (Drive related) Apr 25 21:32:58 Namek kernel: ata7: EH complete (Drive related) Apr 25 21:32:58 Namek kernel: ata7.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen (Errors) Apr 25 21:32:58 Namek kernel: ata7.00: irq_stat 0x08000000, interface fatal error (Errors) Apr 25 21:32:58 Namek kernel: ata7: SError: { UnrecovData Handshk } (Errors) Apr 25 21:32:58 Namek kernel: ata7.00: failed command: WRITE DMA EXT (Minor Issues) Apr 25 21:32:58 Namek kernel: ata7.00: cmd 35/00:00:4f:ec:04/00:04:00:00:00/e0 tag 0 dma 524288 out (Drive related) Apr 25 21:32:58 Namek kernel: res 50/00:00:4e:ec:04/00:00:00:00:00/e0 Emask 0x10 (ATA bus error) (Errors) Apr 25 21:32:58 Namek kernel: ata7.00: status: { DRDY } (Drive related) Apr 25 21:32:58 Namek kernel: ata7: hard resetting link (Minor Issues) Apr 25 21:32:58 Namek kernel: ata7: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) Apr 25 21:32:58 Namek kernel: ata7.00: configured for UDMA/133 (Drive related) Apr 25 21:32:58 Namek kernel: ata7: EH complete (Drive related) Apr 25 21:33:00 Namek cache_dirs: =================================== Entire syslog is attached. I've tried reseating the cables to the drives and the drives passed a long and short SMART test. Anything else it can be? Thanks as always! syslog-2011-05-22.txt
May 24, 201115 yr ata6 = disk2 and ata7=disk3. Get SMART reports on those drives. Do they share a controller card?
May 24, 201115 yr Author ata6 = disk2 and ata7=disk3. Get SMART reports on those drives. Do they share a controller card? I ran smart tests on them when I noticed this last time, both passed, but I will run them again. All of my drives are hooked into my motherboard.
June 13, 201115 yr Author Bump. Replaced the cable with a higher quality one and again I have the same issue. The eps. I'm watching freezes for around 30 secs and keeps playing. The syslog shows this: Jun 12 09:24:39 Namek kernel: NTFS driver 2.1.29 [Flags: R/O MODULE]. (System) Jun 12 21:29:40 Namek kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) Jun 12 21:29:40 Namek kernel: ata6.00: failed command: CHECK POWER MODE (Minor Issues) Jun 12 21:29:40 Namek kernel: ata6.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0 (Drive related) Jun 12 21:29:40 Namek kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) (Errors) Jun 12 21:29:40 Namek kernel: ata6.00: status: { DRDY } (Drive related) Jun 12 21:29:40 Namek kernel: ata6: hard resetting link (Minor Issues) Jun 12 21:29:41 Namek kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) (Drive related) Jun 12 21:29:41 Namek kernel: ata6.00: configured for UDMA/133 (Drive related) Jun 12 21:29:41 Namek kernel: ata6: EH complete (Drive related) Hard drive passes smart, new cable, sata port directly on motherboard. What else can it be?
June 13, 201115 yr Author Please post SMART reports. The details of the report may indicate the problem. Thanks for all of the help thus far! Don't mind the aborted by user, that was me not knowing what I was doing. Here is the smart result. Statistics for /dev/sde ST3750330AS_9QK052ND smartctl -a -d ata /dev/sde smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Seagate Barracuda 7200.11 family Device Model: ST3750330AS Serial Number: 9QK052ND Firmware Version: SD1A User Capacity: 750,156,374,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Mon Jun 13 12:30:03 2011 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: ( 634) 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: ( 176) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x103b) 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 114 100 006 Pre-fail Always - 58785980 3 Spin_Up_Time 0x0003 093 093 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 140 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 063 060 030 Pre-fail Always - 2223038 9 Power_On_Hours 0x0032 094 094 000 Old_age Always - 5812 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 25 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 099 093 000 Old_age Always - 261997002813 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 079 058 045 Old_age Always - 21 (Lifetime Min/Max 21/37) 194 Temperature_Celsius 0x0022 021 042 000 Old_age Always - 21 (0 16 0 0) 195 Hardware_ECC_Recovered 0x001a 043 033 000 Old_age Always - 58785980 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 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 without error 00% 5338 - # 2 Short offline Aborted by host 90% 5338 - # 3 Short offline Aborted by host 90% 5338 - # 4 Short offline Aborted by host 90% 5338 - # 5 Short offline Aborted by host 90% 5338 - # 6 Short offline Completed without error 00% 5338 - # 7 Short offline Aborted by host 90% 5338 - # 8 Short offline Aborted by host 90% 5338 - # 9 Short offline Aborted by host 90% 5338 - #10 Short offline Aborted by host 90% 5338 - #11 Short offline Aborted by host 90% 5338 - #12 Short offline Aborted by host 90% 5338 - #13 Extended offline Aborted by host 90% 5338 - #14 Extended offline Aborted by host 90% 5338 - #15 Extended offline Aborted by host 90% 5338 - #16 Extended offline Aborted by host 90% 5338 - #17 Extended offline Completed without error 00% 5331 - #18 Extended offline Aborted by host 90% 5328 - #19 Extended offline Aborted by host 90% 5328 - #20 Extended offline Aborted by host 90% 5328 - #21 Extended offline Aborted by host 90% 5328 - 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. Thanks.
June 13, 201115 yr Author Report looks ok. Are the files for these episodes split between disks? The episodes are on a single disk (they were put there before I set up shares) currently it's set as Split Level 1. Also what are you using for playback and networking? Wireless or Gigabit. Josh I'm using Wired Gigabit. Thanks.
June 13, 201115 yr Your syslog shows this more than once: Apr 30 15:16:27 Namek ifplugd(eth0)[1373]: Link beat lost. Apr 30 15:16:32 Namek apcupsd[1662]: Running on UPS batteries. Apr 30 15:16:38 Namek ifplugd(eth0)[1373]: Executing '/etc/ifplugd/ifplugd.action eth0 down'. Apr 30 15:16:38 Namek logger: /etc/rc.d/rc.inet1: /sbin/dhcpcd -k -d eth0 Apr 30 15:16:39 Namek ifplugd(eth0)[1373]: client: Stopping NTP daemon... Apr 30 15:16:39 Namek ifplugd(eth0)[1373]: Program executed successfully. Apr 30 15:28:10 Namek apcupsd[1662]: Mains returned. No longer on UPS batteries. Apr 30 15:28:10 Namek apcupsd[1662]: Power is back. UPS running on mains. Apr 30 15:28:11 Namek apcupsd[1662]: Power failure. Apr 30 15:28:16 Namek apcupsd[1662]: Running on UPS batteries. Apr 30 15:36:29 Namek apcupsd[1662]: Mains returned. No longer on UPS batteries. Apr 30 15:36:29 Namek apcupsd[1662]: Power is back. UPS running on mains. Apr 30 15:36:33 Namek kernel: r8169: eth0: link up Apr 30 15:36:34 Namek ifplugd(eth0)[1373]: Link beat detected. How often does you power go down? Is the Ethernet going down during the skips?
June 13, 201115 yr Author Your syslog shows this more than once: Apr 30 15:16:27 Namek ifplugd(eth0)[1373]: Link beat lost. Apr 30 15:16:32 Namek apcupsd[1662]: Running on UPS batteries. Apr 30 15:16:38 Namek ifplugd(eth0)[1373]: Executing '/etc/ifplugd/ifplugd.action eth0 down'. Apr 30 15:16:38 Namek logger: /etc/rc.d/rc.inet1: /sbin/dhcpcd -k -d eth0 Apr 30 15:16:39 Namek ifplugd(eth0)[1373]: client: Stopping NTP daemon... Apr 30 15:16:39 Namek ifplugd(eth0)[1373]: Program executed successfully. Apr 30 15:28:10 Namek apcupsd[1662]: Mains returned. No longer on UPS batteries. Apr 30 15:28:10 Namek apcupsd[1662]: Power is back. UPS running on mains. Apr 30 15:28:11 Namek apcupsd[1662]: Power failure. Apr 30 15:28:16 Namek apcupsd[1662]: Running on UPS batteries. Apr 30 15:36:29 Namek apcupsd[1662]: Mains returned. No longer on UPS batteries. Apr 30 15:36:29 Namek apcupsd[1662]: Power is back. UPS running on mains. Apr 30 15:36:33 Namek kernel: r8169: eth0: link up Apr 30 15:36:34 Namek ifplugd(eth0)[1373]: Link beat detected. How often does you power go down? Is the Ethernet going down during the skips? Ahhh, I had an electricion turnning power on and off so he could work on a broken fixture. It has not gone off again since that one time.
June 13, 201115 yr Are the skips always in the same location? IF you watch the same episode again does it skip in the same place?
June 13, 201115 yr Author Are the skips always in the same location? IF you watch the same episode again does it skip in the same place? That is a fantastic questions, I will have to check. I'll find out when I get home tonight and post back. Thanks.
June 14, 201115 yr If you are wiring through the wall/switch etc, see if you can also try different porst or even better a direct connection. I found faulty wiring through the wall caused skipping on mine. Josh
June 15, 201115 yr Report looks ok. Are the files for these episodes split between disks? I'm not so sure that report looks okay. Nothing has outright failed, but I certainly do think the drive is probably the source of his problem. I'm pretty sure that for that particular drive model, the starting value for the RAW READ ERROR RATE is 120. So the fact that his is at 114 means his drive has been experiencing read errors. This would explain his freezing. The Seek Error Rate also looks suspect. This doesn't count how many seek errors there have been, but just tries to establish a measure for their rate of occurrence. I do know that the Seek Error Rate starts at 100 on this drive model and diminishes (so 100 would be no seek errors). It looks like his is at 63, indicating to me a high number of seek errors. Failure is at 30. So 100 indicates no seek errors and 30 indicates so many seek errors that the drive is practically unusable for anything. His drive is sitting right in the middle. This drive was also notorious for the Seagate clicking noise. A new drive starts off silent, then gradually develops a ticking sound, particularly when it spins up or spins down. The ticking gets louder and then the drive completely fails. A drop in the Seek Error Rate is usually a leading indicator of drive failure. The ticking sound is actually coming from the head positioning mechanism. It becomes damaged during parking and unparking. This damage causes the Seek Error Rate value to drop. Typically once this drive starts ticking, the value drops to the 50s or 60s, which is where you are at. Spin your drives up and down so that the heads park and unpark. Listen for a ticking noise when you do so (you may need to be near the drive to hear it initially). Do you hear a ticking noise? As the failure worsens, the ticking will get much louder, and you won't need to be near the drive to hear it. You're seek error rate value will be in the 30's or 40s then. Then your drive will then completely fail and probably not even spin up anymore.
June 15, 201115 yr Author Oh jeez, I came here to anwser some previous question and read KYThrill's post. When the eps. skips, if I rewind it to just before the skip, it will not skip in same place again. The skips are compeltely at random. As far as the wiring goes, if I play a file from another source (another networked computer) I don't experieecne any skips. I think that KYThrill may be right as to a failling HD. I'll give Seagate a call to have it replaced, or do you guys think I should just buy a newer better drive? Thanks for all the help thus far
June 15, 201115 yr As far as the wiring goes, if I play a file from another source (another networked computer) I don't experieecne any skips. I assume another source using the same cable and ports? I think that KYThrill may be right as to a failling HD. I'll give Seagate a call to have it replaced, or do you guys think I should just buy a newer better drive? I don't have experience with seagate drives as I've heard a few bad things but I'd buy a new one, get the data backed up and then RMA the seagate drive. A spare drive won't hurt. Josh
Archived
This topic is now archived and is closed to further replies.