[Solved] Seeing strange errors over the past week.

daringdirk99 · April 9, 2015

I have been running fine on version 5.0.6 for the last few months and out of the blue Couch Potato stopped working. I try to manually start it, but it just keeps shutting down, but SABNZDB, Sickbeard and Plex Server all all still running fine and all are PhAzE Plugins.

I thought maybe there was a physical connection issue on my cache drive, but I have just shut down and made sure everything was as it should be and upon reboot this is the error these are some of the errors I get.

Any advice would be appreciated.

Apr 8 20:47:01 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

Apr 8 20:47:01 Tower kernel: ata3.00: BMDMA2 stat 0x80c0009 (Drive related)

Apr 8 20:47:01 Tower kernel: ata3.00: cmd 25/00:00:f7:c0:3f/00:01:2c:00:00/e0 tag 0 dma 131072 in (Drive related)

Apr 8 20:47:01 Tower kernel: res 51/40:00:17:c1:3f/00:00:2c:00:00/10 Emask 0x9 (media error) (Errors)

Apr 8 20:47:01 Tower kernel: ata3.00: status: { DRDY ERR } (Drive related)

Apr 8 20:47:01 Tower kernel: ata3.00: error: { UNC } (Errors)

Apr 8 20:47:01 Tower kernel: ata3.00: configured for UDMA/100 (Drive related)

Apr 8 20:47:01 Tower kernel: sd 3:0:0:0: [sdb] Unhandled sense code (Drive related)

Apr 8 20:47:01 Tower kernel: sd 3:0:0:0: [sdb] (Drive related)

Apr 8 20:47:01 Tower kernel: Sense Key : 0x3 [current] [descriptor]

Apr 8 20:47:01 Tower kernel: Descriptor sense data with sense descriptors (in hex):

Apr 8 20:47:01 Tower kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00

Apr 8 20:47:01 Tower kernel: 2c 3f c1 17

Apr 8 20:47:01 Tower kernel: sd 3:0:0:0: [sdb] (Drive related)

Apr 8 20:47:01 Tower kernel: ASC=0x11 ASCQ=0x4

Apr 8 20:47:01 Tower kernel: sd 3:0:0:0: [sdb] CDB: (Drive related)

Apr 8 20:47:01 Tower kernel: cdb[0]=0x28: 28 00 2c 3f c0 f7 00 01 00 00

Apr 8 20:47:01 Tower kernel: end_request: I/O error, dev sdb, sector 742375703 (Errors)

Apr 8 20:47:01 Tower kernel: ata3: EH complete (Drive related)

Apr 8 20:47:02 Tower sudo: root : TTY=console ; PWD=/ ; USER=nobody ; COMMAND=/usr/bin/python /mnt/cache/custom/sabnzbd/SABnzbd.py -d -s 0.0.0.0:8800 --config-file /mnt/cache/custom/sabnzbd/config --pidfile /var/run/sabnzbd/sabnzbd.pid

Apr 8 20:47:04 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

Apr 8 20:47:04 Tower kernel: ata3.00: BMDMA2 stat 0x80d0009 (Drive related)

Apr 8 20:47:04 Tower kernel: ata3.00: cmd 25/00:08:17:c1:3f/00:00:2c:00:00/e0 tag 0 dma 4096 in (Drive related)

Apr 8 20:47:04 Tower kernel: res 51/40:00:17:c1:3f/00:00:2c:00:00/10 Emask 0x9 (media error) (Errors)

Apr 8 20:47:04 Tower kernel: ata3.00: status: { DRDY ERR } (Drive related)

Apr 8 20:47:04 Tower kernel: ata3.00: error: { UNC } (Errors)

Apr 8 20:47:04 Tower kernel: ata3.00: configured for UDMA/100 (Drive related)

Apr 8 20:47:04 Tower kernel: sd 3:0:0:0: [sdb] Unhandled sense code (Drive related)

Apr 8 20:47:04 Tower kernel: sd 3:0:0:0: [sdb] (Drive related)

Apr 8 20:47:04 Tower kernel: Sense Key : 0x3 [current] [descriptor]

Apr 8 20:47:04 Tower kernel: Descriptor sense data with sense descriptors (in hex):

Apr 8 20:47:04 Tower kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00

Apr 8 20:47:04 Tower kernel: 2c 3f c1 17

Apr 8 20:47:04 Tower kernel: sd 3:0:0:0: [sdb] (Drive related)

Apr 8 20:47:04 Tower kernel: ASC=0x11 ASCQ=0x4

Apr 8 20:47:04 Tower kernel: sd 3:0:0:0: [sdb] CDB: (Drive related)

Apr 8 20:47:04 Tower kernel: cdb[0]=0x28: 28 00 2c 3f c1 17 00 00 08 00

Apr 8 20:47:04 Tower kernel: end_request: I/O error, dev sdb, sector 742375703 (Errors)

Apr 8 20:47:04 Tower kernel: Buffer I/O error on device sdb1, logical block 92796955 (Errors)

Apr 8 20:47:04 Tower kernel: ata3: EH complete (Drive related)

Apr 8 20:47:10 Tower sudo: root : TTY=unknown ; PWD=/ ; USER=nobody ; COMMAND=/usr/bin/python /mnt/cache/custom/sickbeard/SickBeard.py --daemon --port 8081 --datadir /mnt/cache/custom/sickbeard/config --pidfile /var/run/sickbeard/sickbeard.pid > /dev/null 2>$stuff$1

Apr 8 20:47:24 Tower logger: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D

Apr 8 20:47:24 Tower avahi-daemon[8589]: Failed to find user 'avahi'.

Apr 8 20:47:44 Tower logger: Timeout reached while wating for return value

Apr 8 20:47:44 Tower logger: Could not receive return value from daemon process.

Apr 8 20:47:44 Tower logger: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon: /usr/sbin/avahi-dnsconfd -D

Apr 8 20:47:44 Tower avahi-dnsconfd[8751]: connect(): No such file or directory

Apr 8 20:47:44 Tower avahi-dnsconfd[8751]: Failed to connect to the daemon. This probably means that you

Apr 8 20:47:44 Tower avahi-dnsconfd[8751]: didn't start avahi-daemon before avahi-dnsconfd.

Apr 8 20:49:31 Tower sudo: root : TTY=console ; PWD=/ ; USER=nobody ; COMMAND=/usr/bin/python /mnt/cache/custom/couchpotato/CouchPotato.py --data_dir /mnt/cache/custom/couchpotato/config --daemon --pid_file /var/run/couchpotato/couchpotato.pid

Apr 8 20:49:40 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

Apr 8 20:49:40 Tower kernel: ata3.00: BMDMA2 stat 0x80d0009 (Drive related)

Apr 8 20:49:40 Tower kernel: ata3.00: cmd 25/00:08:17:c1:3f/00:00:2c:00:00/e0 tag 0 dma 4096 in (Drive related)

Apr 8 20:49:40 Tower kernel: res 51/40:00:17:c1:3f/00:00:2c:00:00/10 Emask 0x9 (media error) (Errors)

Apr 8 20:49:40 Tower kernel: ata3.00: status: { DRDY ERR } (Drive related)

Apr 8 20:49:40 Tower kernel: ata3.00: error: { UNC } (Errors)

Apr 8 20:49:40 Tower kernel: ata3.00: configured for UDMA/100 (Drive related)

Apr 8 20:49:40 Tower kernel: sd 3:0:0:0: [sdb] Unhandled sense code (Drive related)

Apr 8 20:49:40 Tower kernel: sd 3:0:0:0: [sdb] (Drive related)

Apr 8 20:49:40 Tower kernel: Sense Key : 0x3 [current] [descriptor]

Apr 8 20:49:40 Tower kernel: Descriptor sense data with sense descriptors (in hex):

Apr 8 20:49:40 Tower kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00

Apr 8 20:49:40 Tower kernel: 2c 3f c1 17

Apr 8 20:49:40 Tower kernel: sd 3:0:0:0: [sdb] (Drive related)

Apr 8 20:49:40 Tower kernel: ASC=0x11 ASCQ=0x4

Apr 8 20:49:40 Tower kernel: sd 3:0:0:0: [sdb] CDB: (Drive related)

Apr 8 20:49:40 Tower kernel: cdb[0]=0x28: 28 00 2c 3f c1 17 00 00 08 00

Apr 8 20:49:40 Tower kernel: end_request: I/O error, dev sdb, sector 742375703 (Errors)

Apr 8 20:49:40 Tower kernel: Buffer I/O error on device sdb1, logical block 92796955 (Errors)

Apr 8 20:49:40 Tower kernel: ata3: EH complete (Drive related)

Apr 8 20:49:53 Tower sudo: root : TTY=console ; PWD=/ ; USER=nobody ; COMMAND=/usr/bin/python /mnt/cache/custom/couchpotato/CouchPotato.py --data_dir /mnt/cache/custom/couchpotato/config --daemon --pid_file /var/run/couchpotato/couchpotato.pid

Apr 8 20:50:02 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

Apr 8 20:50:02 Tower kernel: ata3.00: BMDMA2 stat 0x90d0009 (Drive related)

Apr 8 20:50:02 Tower kernel: ata3.00: cmd 25/00:08:17:c1:3f/00:00:2c:00:00/e0 tag 0 dma 4096 in (Drive related)

Apr 8 20:50:02 Tower kernel: res 51/40:00:17:c1:3f/00:00:2c:00:00/10 Emask 0x9 (media error) (Errors)

Apr 8 20:50:02 Tower kernel: ata3.00: status: { DRDY ERR } (Drive related)

Apr 8 20:50:02 Tower kernel: ata3.00: error: { UNC } (Errors)

Apr 8 20:50:02 Tower kernel: ata3.00: configured for UDMA/100 (Drive related)

Apr 8 20:50:02 Tower kernel: sd 3:0:0:0: [sdb] Unhandled sense code (Drive related)

Apr 8 20:50:02 Tower kernel: sd 3:0:0:0: [sdb] (Drive related)

Apr 8 20:50:02 Tower kernel: Sense Key : 0x3 [current] [descriptor]

Apr 8 20:50:02 Tower kernel: Descriptor sense data with sense descriptors (in hex):

Apr 8 20:50:02 Tower kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00

Apr 8 20:50:02 Tower kernel: 2c 3f c1 17

Apr 8 20:50:02 Tower kernel: sd 3:0:0:0: [sdb] (Drive related)

Apr 8 20:50:02 Tower kernel: ASC=0x11 ASCQ=0x4

Apr 8 20:50:02 Tower kernel: sd 3:0:0:0: [sdb] CDB: (Drive related)

Apr 8 20:50:02 Tower kernel: cdb[0]=0x28: 28 00 2c 3f c1 17 00 00 08 00

Apr 8 20:50:02 Tower kernel: end_request: I/O error, dev sdb, sector 742375703 (Errors)

Apr 8 20:50:02 Tower kernel: Buffer I/O error on device sdb1, logical block 92796955 (Errors)

Apr 8 20:50:02 Tower kernel: ata3: EH complete (Drive related)

Apr 8 20:50:19 Tower sudo: root : TTY=console ; PWD=/ ; USER=nobody ; COMMAND=/usr/bin/python /mnt/cache/custom/couchpotato/CouchPotato.py --data_dir /mnt/cache/custom/couchpotato/config --daemon --pid_file /var/run/couchpotato/couchpotato.pid

Apr 8 20:50:28 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)

Apr 8 20:50:28 Tower kernel: ata3.00: BMDMA2 stat 0x10d0009 (Drive related)

Apr 8 20:50:28 Tower kernel: ata3.00: cmd 25/00:08:17:c1:3f/00:00:2c:00:00/e0 tag 0 dma 4096 in (Drive related)

Apr 8 20:50:28 Tower kernel: res 51/40:00:17:c1:3f/00:00:2c:00:00/10 Emask 0x9 (media error) (Errors)

Apr 8 20:50:28 Tower kernel: ata3.00: status: { DRDY ERR } (Drive related)

Apr 8 20:50:28 Tower kernel: ata3.00: error: { UNC } (Errors)

Apr 8 20:50:28 Tower kernel: ata3.00: configured for UDMA/100 (Drive related)

Apr 8 20:50:28 Tower kernel: sd 3:0:0:0: [sdb] Unhandled sense code (Drive related)

Apr 8 20:50:28 Tower kernel: sd 3:0:0:0: [sdb] (Drive related)

Apr 8 20:50:28 Tower kernel: Sense Key : 0x3 [current] [descriptor]

Apr 8 20:50:28 Tower kernel: Descriptor sense data with sense descriptors (in hex):

Apr 8 20:50:28 Tower kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00

Apr 8 20:50:28 Tower kernel: 2c 3f c1 17

Apr 8 20:50:28 Tower kernel: sd 3:0:0:0: [sdb] (Drive related)

Apr 8 20:50:28 Tower kernel: ASC=0x11 ASCQ=0x4

Apr 8 20:50:28 Tower kernel: sd 3:0:0:0: [sdb] CDB: (Drive related)

Apr 8 20:50:28 Tower kernel: cdb[0]=0x28: 28 00 2c 3f c1 17 00 00 08 00

Apr 8 20:50:28 Tower kernel: end_request: I/O error, dev sdb, sector 742375703 (Errors)

Apr 8 20:50:28 Tower kernel: Buffer I/O error on device sdb1, logical block 92796955 (Errors)

Apr 8 20:50:28 Tower kernel: ata3: EH complete (Drive related)

jc179 · April 9, 2015

Based on the info provided above, and the messages, I'd suspect you have a bad block that hasn't been remapped, or when this bad block occurred a/some file(s) with-in couchpotato was corrupted. Ideally disks should handle this in the background, *but* if it can't read the block, its possible the data is corrupt.

Since sabnzb is ok (assume perhaps python is OK), and perhaps just your couch potato is cooked. Maybe VI the .PY file and see if you anything.

In the meantime before messing about too much:

#1. I'd backup the filesystem where you have this installed to

#2. Run a scan, which checks for bad blocks, one example assuming ext2: e2fsck -c /dev/sdb1

#3. If all is ok, reinstall couch potato to replace corrupted files, if not, dig further, maybe a python lib is nackered.

hope that helps

Jonathan

trurl · April 9, 2015

Attach a complete syslog. Don't bother with the ext2 filesystem check recommended. unRAID doesn't support ext2.

A complete syslog will allow us to give better advice.

dgaschk · April 9, 2015

Does the error column in unRAID Main have any counts?

daringdirk99 · April 11, 2015

My apologies for the delay, I thought I had checked the box to let me know if anyone replied but clearly I did not. I have attached a full sys log and I now I am seeing I have some read errors on disk 3 as well that I did not have before.

Thanks for the help,

syslog-2015-04-10.txt

dgaschk · April 12, 2015

Post a SMART report for disk 3.

daringdirk99 · May 20, 2015

My travel schedule has been very hectic lately, so I have not had an opportunity to look closer at the problem I was having. This past weekend, I was able to finally take a closer look at the error messages and I determined that my drive 3 was toast. It was one of my older drives, so I chose to update it with a brand new 3tb drive and after preclearing the drive over the past few days and rebuilding the array since yesterday and I am back up and running 100%.

As for the couchpotato issue, it turns out that was a corrupt file that was causing the issue and as soon as I deleted that file, everything started working again.

Thanks for the help and in pointing me in the direction of my issues with disk3.

[Solved] Seeing strange errors over the past week.

Recommended Posts

daringdirk99

Link to comment

jc179

Link to comment

trurl

Link to comment

dgaschk

Link to comment

daringdirk99

Link to comment

dgaschk

Link to comment

daringdirk99

Link to comment

Join the conversation