[GiGaBlue QUAD] Every night at around 21:00 box hangs for about 10 - 30 seconds

[Ojustaboo]

Hi, I've probably set up something silly but cant for the life of me find out what.

For the past few nights, I've been watching recorded programs and at around 21:00, the box hangs for a while. It's fine at all other times.

Tonight it did it twice. Very briefly at 21:00, and at about 21:30 it hung for about 30+ seconds with the ViX logo spinning.

I don't have to do anything, can just wait and eventually it springs back into life and the program carries on playing.

if it makes any difference, every morning when I turn my PC on, I telnet into my quad and issue the "shutdown -r now" command so that it correctly mounts my two PC shared video folders. If I don't do this, I cant access my PC folders (mount -a doesn't mount them) and when I press the video button on the remote, the box hangs indefinitely, well the UI does, I can telnet in and issue the shutdown command.

Messages file attached, errors at 21:00 and 21:30 are

Dec 12 21:02:23 gbquad user.err kernel: ata1.00: exception Emask 0x0 SAct 0x7 SErr 0x0 action 0x6 frozen
Dec 12 21:02:23 gbquad user.err kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 12 21:02:23 gbquad user.err kernel: ata1.00: cmd 60/00:00:10:c4:1c/02:00:06:00:00/40 tag 0 ncq 262144 in
Dec 12 21:02:23 gbquad user.err kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 12 21:02:23 gbquad user.err kernel: ata1.00: status: { DRDY }
Dec 12 21:02:23 gbquad user.err kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Dec 12 21:02:23 gbquad user.err kernel: ata1.00: cmd 61/08:08:38:14:00/00:00:07:00:00/40 tag 1 ncq 4096 out
Dec 12 21:02:23 gbquad user.err kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 12 21:02:23 gbquad user.err kernel: ata1.00: status: { DRDY }
Dec 12 21:02:23 gbquad user.err kernel: ata1.00: failed command: WRITE FPDMA QUEUED
Dec 12 21:02:23 gbquad user.err kernel: ata1.00: cmd 61/30:10:18:f2:01/00:00:10:00:00/40 tag 2 ncq 24576 out
Dec 12 21:02:23 gbquad user.err kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 12 21:02:23 gbquad user.err kernel: ata1.00: status: { DRDY }
Dec 12 21:02:23 gbquad user.info kernel: ata1: hard resetting link
Dec 12 21:02:23 gbquad user.info kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Dec 12 21:02:23 gbquad user.info kernel: ata1.00: configured for UDMA/133
Dec 12 21:02:23 gbquad user.warn kernel: ata1.00: device reported invalid CHS sector 0
Dec 12 21:02:23 gbquad user.warn kernel: ata1.00: device reported invalid CHS sector 0
Dec 12 21:02:23 gbquad user.warn kernel: ata1.00: device reported invalid CHS sector 0
Dec 12 21:02:23 gbquad user.info kernel: ata1: EH complete
Dec 12 21:10:00 gbquad daemon.notice automount[30760]: >> mount: mounting /dev/.Trash on /autofs/.Trash failed: No such file or directory
Dec 12 21:10:00 gbquad daemon.err automount[30760]: mount(generic): failed to mount /dev/.Trash (type auto) on /autofs/.Trash
Dec 12 21:10:00 gbquad daemon.err automount[30760]: failed to mount /autofs/.Trash
Dec 12 21:10:00 gbquad daemon.notice automount[30788]: >> mount: mounting /dev/movie on /autofs/movie failed: No such file or directory
Dec 12 21:10:00 gbquad daemon.err automount[30788]: mount(generic): failed to mount /dev/movie (type auto) on /autofs/movie
Dec 12 21:10:00 gbquad daemon.err automount[30788]: failed to mount /autofs/movie
Dec 12 21:31:16 gbquad user.err kernel: ata1.00: exception Emask 0x0 SAct 0x1f SErr 0x0 action 0x6 frozen
Dec 12 21:31:16 gbquad user.err kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 12 21:31:16 gbquad user.err kernel: ata1.00: cmd 60/f0:00:10:87:3d/00:00:06:00:00/40 tag 0 ncq 122880 in
Dec 12 21:31:16 gbquad user.err kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 12 21:31:16 gbquad user.err kernel: ata1.00: status: { DRDY }
Dec 12 21:31:16 gbquad user.err kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 12 21:31:16 gbquad user.err kernel: ata1.00: cmd 60/10:08:00:08:3f/01:00:06:00:00/40 tag 1 ncq 139264 in
Dec 12 21:31:16 gbquad user.err kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 12 21:31:16 gbquad user.err kernel: ata1.00: status: { DRDY }
Dec 12 21:31:16 gbquad user.err kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 12 21:31:16 gbquad user.err kernel: ata1.00: cmd 60/00:10:10:09:3f/02:00:06:00:00/40 tag 2 ncq 262144 in
Dec 12 21:31:16 gbquad user.err kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 12 21:31:16 gbquad user.err kernel: ata1.00: status: { DRDY }
Dec 12 21:31:16 gbquad user.err kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 12 21:31:16 gbquad user.err kernel: ata1.00: cmd 60/08:18:60:0a:28/00:00:04:00:00/40 tag 3 ncq 4096 in
Dec 12 21:31:16 gbquad user.err kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 12 21:31:16 gbquad user.err kernel: ata1.00: status: { DRDY }
Dec 12 21:31:16 gbquad user.err kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 12 21:31:16 gbquad user.err kernel: ata1.00: cmd 60/08:20:68:0a:28/00:00:04:00:00/40 tag 4 ncq 4096 in
Dec 12 21:31:16 gbquad user.err kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 12 21:31:16 gbquad user.err kernel: ata1.00: status: { DRDY }
Dec 12 21:31:16 gbquad user.info kernel: ata1: hard resetting link
Dec 12 21:31:16 gbquad user.info kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Dec 12 21:31:16 gbquad user.info kernel: ata1.00: configured for UDMA/133
Dec 12 21:31:16 gbquad user.warn kernel: ata1.00: device reported invalid CHS sector 0
Dec 12 21:31:16 gbquad user.warn kernel: ata1.00: device reported invalid CHS sector 0
Dec 12 21:31:16 gbquad user.warn kernel: ata1.00: device reported invalid CHS sector 0
Dec 12 21:31:16 gbquad user.warn kernel: ata1.00: device reported invalid CHS sector 0
Dec 12 21:31:16 gbquad user.warn kernel: ata1.00: device reported invalid CHS sector 0
Dec 12 21:31:16 gbquad user.info kernel: ata1: EH complete

Many thanks



View attachment messages.txt

 

[Ojustaboo]

Anyone got any ideas please.

My son watched about 5 hours of stuff on the HD today with zero problems. Then watching something this evening, again the following error and the vid pauses 3 times (8:23. 8:33 and 8:41pm) for 10 odd secs then carries on.

Dec 18 20:11:14 gbquad daemon.notice automount[32045]: >> mount: mounting /dev/logs on /autofs/logs failed: No such file or directory
Dec 18 20:11:14 gbquad daemon.err automount[32045]: mount(generic): failed to mount /dev/logs (type auto) on /autofs/logs
Dec 18 20:11:14 gbquad daemon.err automount[32045]: failed to mount /autofs/logs
Dec 18 20:23:02 gbquad user.err kernel: ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x6 frozen
Dec 18 20:23:02 gbquad user.err kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 18 20:23:02 gbquad user.err kernel: ata1.00: cmd 60/00:00:20:ea:20/01:00:0e:00:00/40 tag 0 ncq 131072 in
Dec 18 20:23:02 gbquad user.err kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 18 20:23:02 gbquad user.err kernel: ata1.00: status: { DRDY }
Dec 18 20:23:02 gbquad user.err kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 18 20:23:02 gbquad user.err kernel: ata1.00: cmd 60/00:08:20:e9:20/01:00:0e:00:00/40 tag 1 ncq 131072 in
Dec 18 20:23:02 gbquad user.err kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 18 20:23:02 gbquad user.err kernel: ata1.00: status: { DRDY }
Dec 18 20:23:02 gbquad user.info kernel: ata1: hard resetting link
Dec 18 20:23:02 gbquad user.info kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Dec 18 20:23:02 gbquad user.info kernel: ata1.00: configured for UDMA/133
Dec 18 20:23:02 gbquad user.warn kernel: ata1.00: device reported invalid CHS sector 0
Dec 18 20:23:02 gbquad user.warn kernel: ata1.00: device reported invalid CHS sector 0
Dec 18 20:23:02 gbquad user.info kernel: ata1: EH complete
Dec 18 20:33:12 gbquad user.err kernel: ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x6 frozen
Dec 18 20:33:12 gbquad user.err kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 18 20:33:12 gbquad user.err kernel: ata1.00: cmd 60/00:00:20:f2:2b/01:00:0e:00:00/40 tag 0 ncq 131072 in
Dec 18 20:33:12 gbquad user.err kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 18 20:33:12 gbquad user.err kernel: ata1.00: status: { DRDY }
Dec 18 20:33:12 gbquad user.err kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 18 20:33:12 gbquad user.err kernel: ata1.00: cmd 60/00:08:20:f1:2b/01:00:0e:00:00/40 tag 1 ncq 131072 in
Dec 18 20:33:12 gbquad user.err kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 18 20:33:12 gbquad user.err kernel: ata1.00: status: { DRDY }
Dec 18 20:33:12 gbquad user.info kernel: ata1: hard resetting link
Dec 18 20:33:12 gbquad user.info kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Dec 18 20:33:12 gbquad user.info kernel: ata1.00: configured for UDMA/133
Dec 18 20:33:12 gbquad user.warn kernel: ata1.00: device reported invalid CHS sector 0
Dec 18 20:33:12 gbquad user.warn kernel: ata1.00: device reported invalid CHS sector 0
Dec 18 20:33:12 gbquad user.info kernel: ata1: EH complete
Dec 18 20:33:51 gbquad user.err kernel: ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x6 frozen
Dec 18 20:33:51 gbquad user.err kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 18 20:33:51 gbquad user.err kernel: ata1.00: cmd 60/00:00:20:50:2c/01:00:0e:00:00/40 tag 0 ncq 131072 in
Dec 18 20:33:51 gbquad user.err kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 18 20:33:51 gbquad user.err kernel: ata1.00: status: { DRDY }
Dec 18 20:33:51 gbquad user.err kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 18 20:33:51 gbquad user.err kernel: ata1.00: cmd 60/00:08:20:51:2c/01:00:0e:00:00/40 tag 1 ncq 131072 in
Dec 18 20:33:51 gbquad user.err kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 18 20:33:51 gbquad user.err kernel: ata1.00: status: { DRDY }
Dec 18 20:33:51 gbquad user.info kernel: ata1: hard resetting link
Dec 18 20:33:51 gbquad user.info kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Dec 18 20:33:51 gbquad user.info kernel: ata1.00: configured for UDMA/133
Dec 18 20:33:51 gbquad user.warn kernel: ata1.00: device reported invalid CHS sector 0
Dec 18 20:33:51 gbquad user.warn kernel: ata1.00: device reported invalid CHS sector 0
Dec 18 20:33:51 gbquad user.info kernel: ata1: EH complete
Dec 18 20:41:39 gbquad user.err kernel: ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x6 frozen
Dec 18 20:41:39 gbquad user.err kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 18 20:41:39 gbquad user.err kernel: ata1.00: cmd 60/00:00:20:38:30/01:00:0e:00:00/40 tag 0 ncq 131072 in
Dec 18 20:41:39 gbquad user.err kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 18 20:41:39 gbquad user.err kernel: ata1.00: status: { DRDY }
Dec 18 20:41:39 gbquad user.err kernel: ata1.00: failed command: READ FPDMA QUEUED
Dec 18 20:41:39 gbquad user.err kernel: ata1.00: cmd 60/00:08:20:39:30/01:00:0e:00:00/40 tag 1 ncq 131072 in
Dec 18 20:41:39 gbquad user.err kernel:          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec 18 20:41:39 gbquad user.err kernel: ata1.00: status: { DRDY }
Dec 18 20:41:39 gbquad user.info kernel: ata1: hard resetting link
Dec 18 20:41:39 gbquad user.info kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Dec 18 20:41:39 gbquad user.info kernel: ata1.00: configured for UDMA/133
Dec 18 20:41:39 gbquad user.warn kernel: ata1.00: device reported invalid CHS sector 0
Dec 18 20:41:39 gbquad user.warn kernel: ata1.00: device reported invalid CHS sector 0
Dec 18 20:41:39 gbquad user.info kernel: ata1: EH complete

I rewound the video after a bit to before it paused, this time it played through the same part with zero problems, so its not the actual video file that's corrupted.

It does this with the same error message whether I'm watching videos on the Quads internal HD or whether I'm watching network mounted vids, always with the error message relating to the internal quad HD. I have zero problem if I'm watching live TV.

I've googled the error and theres various people that have had this problem on Linux PC's and so far I've read it could be a faulty drive or an EXT4 bug.

As the box is used most of the day at the moment and the recorded videos are heavily used (copied a load of media files to HD) and is 100% fine until around 9pm (tonight was the earliest it's done this), I cant believe it's a problem with the hard drive beginning to die, otherwise surely this would happen at random times and not every day in the same approx 1 hr time slot?

The only common thing each day is a few mins before this starts, the daemon automount error for /dev/logs thats at the top of the errors quoted above, gets written to the messages log.

Many thanks

 

[andyblac]

something strange going on

[COLOR=#333333]Dec 12 21:10:00 gbquad daemon.notice automount[30760]: >> mount: mounting /dev/.Trash on /autofs/.Trash failed: No such file or directory[/COLOR]Dec 12 21:10:00 gbquad daemon.err automount[30760]: mount(generic): failed to mount /dev/.Trash (type auto) on /autofs/.Trash
Dec 12 21:10:00 gbquad daemon.err automount[30760]: failed to mount /autofs/.Trash
Dec 12 21:10:00 gbquad daemon.notice automount[30788]: >> mount: mounting /dev/movie on /autofs/movie failed: No such file or directory
Dec 12 21:10:00 gbquad daemon.err automount[30788]: mount(generic): failed to mount /dev/movie (type auto) on /autofs/movie
Dec 12 21:10:00 gbquad daemon.err automount[30788]: failed to mount /autofs/movie

those location should not be use the for those folders.


i would reflash, no restore and reset up

 

[Ojustaboo]

Many thanks, finally just managed to get near the TV to reflash

Reflashed, didn't restore

Haven't even set up any channels yet.

I've set up my tuners, my network (Quad did it automatically) and I downloaded the display skin plugin AAF_LCDSkiin_2

I then went to my PC to ftp across my own skin_display.xml (I modified the AAF_LCDSkin_2 one) , thought I'd check the messages file first,

note the last few lines

Jan  1 01:00:22 gbquad user.err kernel: proc_set_vmpeg_dst_apply()LINE=5499
Jan  1 01:00:27 gbquad user.err kernel: Hotplug - connected=1,1,1
Dec 24 07:39:45 gbquad daemon.notice ntpdate[388]: step time server 178.18.118.13 offset 1387870757.611607 sec
Dec 24 07:39:51 gbquad daemon.notice automount[620]: >> mount: mounting /dev/logs on /autofs/logs failed: No such file or directory
Dec 24 07:39:51 gbquad daemon.err automount[620]: mount(generic): failed to mount /dev/logs (type auto) on /autofs/logs
Dec 24 07:39:51 gbquad daemon.err automount[620]: failed to mount /autofs/logs
Dec 24 07:40:33 gbquad authpriv.notice login[683]: ROOT LOGIN  on '/dev/pts/0' from '192.168.0.3:50522'

Latest Vix release 3.0.808

View attachment messages.txt

Best

Joe

 

[Ojustaboo]

Just an update.

This has been bugging me for months now, can watch recorded stuff in the day, no problems (Well very very occasional ones) but without fail, regardless if something was being recorded or not, if I watched a prerecorded program (or MKV/AVI that I'd put on the HD) between around 8pm and 9:30pm, it would suddenly pause for anything up to 30 secs with the ViX spinning logo, then would continue without any input needed from me.

It would often do it 3 or 4 times in an hour.

I reformatted and installed the Zeus image, problem still happening.

It made zero sense to me, only plugins were the ones ViX installed as default and FileBrowser. Nothing in Cron running at those times etc.

After trying Vix Zeus and it still happening and it appearing that it's only me that's having the problem, I decided on an experiment.

I have one of the latest 500GB PS3 after my previous one died. As both hard drives are the same size, I swapped them around. PS3 still seems to work flawlessly.

I've had the PS3 drive in the Quad for nearly a week, and it no longer pauses at all.

So it appears to be some weird incompatibility problem with the drive I had in the Quad.

For ref, the drive I had problems with says the following on it's label (Has two different part numbers on the label)

Hitachi
Z5K500-500
HTS545050A7E380
P/N: H2T500854S7

500GB
SATA
5V 700mA

P/N: 0J23505
MLC: DA4938
CHS: 16383/16/63

0J23505DA49380P28

 

[chrcoluk]

yeah all those ata errors equals either hdd, cable or controller issue.