btrcp2000 Posted March 6, 2018 Share Posted March 6, 2018 Swapped out a USB card and added a tv tuner this morning. Working fine, so I decided to reboot and see if it could come back up on its own inclduing the VMs where the tuners are installed. It takes two attempts to get it back up and running, because the first one results in the screenshot below. After a cold restart the second time, it's fine. unraid-diagnostics-20180306-1010.zip Link to comment
Warrentheo Posted March 7, 2018 Share Posted March 7, 2018 The last few lines of the syslog are Mar 6 10:08:56 UNRAID kernel: RSP: 002b:000014d35dd84228 EFLAGS: 00000246 Mar 6 10:08:56 UNRAID kernel: comskip[8831]: segfault at 0 ip 00000000010b63f8 sp 00007fff7dbb9240 error 4 in comskip[400000+11a8000] which seems to reference: https://github.com/erikkaashoek/Comskip I suspect your tuner card is causing the issue... Might need to disable Comskip or update it... Don't know much specific to that software... Link to comment
btrcp2000 Posted March 8, 2018 Author Share Posted March 8, 2018 That log was taken after the reboot, so those last lines are probably what it happened to be doing when I d'led the log, but it ran fine after that. The error is still something to look into though. It seems to be stable until I reboot the VM, when all hell breaks loose. Last night I rebooted UNRAID from the GUI, and saw the kernel panic again, exact same screen. Had to cold reboot, after which it started okay but my docker image was gone and it of course wanted a parity check. Fixed everything and now it seems fine, but obviously I cant reboot the VM. Comskip is a process that runs when a file appears in a directory, which would only happen if the tuner finishes its job successfully. I wouldn't be surprised if the tuners were involved as they are a PITA, but what makes you think the Comskip error is connected to the tuner? Next time I need to reboot I will do it under FCP troubleshooting mode and post the diags. Could be the hardware, but other folks have a similar setup. Thanks! Link to comment
BobPhoenix Posted March 9, 2018 Share Posted March 9, 2018 I had to turn off comskip in the SageTV docker on one of my unRAID servers. It was causing the docker to crash with OOM errors. Running Windows version of comskip from a Windows VM and DirMon2 is working great. So no crashes but problems when I ran comskip contained in the SageTV docker. It was on the SageTV docker that is recording from HD-PVRs. Have no problem with comskip on any other box that is recording Mpeg2 from OTA and QAM. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.