Author Topic: Disk_Drive device never starts  (Read 993 times)

chrisbirkinshaw

  • Guru
  • ****
  • Posts: 431
    • View Profile
Disk_Drive device never starts
« on: November 24, 2007, 04:48:44 pm »

The Disk_Drive device on my core and media directors never starts. If I look at the modification date for the log file I see it has not worked for a month:

# ls -l 26_Disk_Drive.log
-rw-r--r-- 1 root root 74 2007-10-05 17:21 26_Disk_Drive.log

I'm not sure what this is started by. It's a child of the orbiter so I looked in the orbiter logs but can't see anything interesting (searched for Disk and disk and found nothing). The App server log also contains no references.

How can I fix this or get Disk_Drive to start manually?

Thanks,

Chris

Zaerc

  • Alumni
  • LinuxMCE God
  • *
  • Posts: 2256
  • Department of Redundancy Department.
    • View Profile
Re: Disk_Drive device never starts
« Reply #1 on: November 24, 2007, 06:56:27 pm »
What do you see when you do "sudo screen -r"?

EDIT:

And are there any errors in that log file you mentioned?
« Last Edit: November 24, 2007, 06:57:58 pm by Zaerc »
"Change is inevitable. Progress is optional."
-- Anonymous


chrisbirkinshaw

  • Guru
  • ****
  • Posts: 431
    • View Profile
Re: Disk_Drive device never starts
« Reply #2 on: November 24, 2007, 07:07:09 pm »
The log is empty. I tried adding another disk drive device to the core and nothing happens. No log for the device appears. grep -R Disk /var/log/pluto/Spawn_Device.log returns nothing so it's not even trying to start the disk drive.

I did a bit of investigation on the second PC - a diskless MD - which also will not play from DVD and found that the drive is actually being recognised but has an error in the log:

more /var/log/pluto/103_Disk_Drive.log
== ATTEMPT FRESH START ==
1       11/24/07 17:33:52       Spawn_Device.sh 103 (spawning-device)   10243 Dev: 103; Already Running list: 97,98,
== FRESH START ==
1       11/24/07 17:33:52       Spawn_Device.sh 103 (spawning-device)   device: 103 ip: 192.168.1.1 cmd_line: Disk_Drive
0       11/24/07 17:33:52       103 (spawning-device)   Entering 103
========== NEW LOG SECTION ==========
1       11/24/07 17:33:53       103 (spawning-device)   Starting... 1
1       11/24/07 17:33:53       103 (spawning-device)   Found ./Disk_Drive
01      11/24/07 17:34:16.059           FindFirstRelatedDeviceOfCategory 115 dev 105 never registered <0xb76cf6d0>
05      11/24/07 17:34:16.060           Disk_Drive_Functions::Disk_Drive_Functions warning m_pDevice_MediaIdentifier 105 isn't registered <0xb76cf6d0>
05      11/24/07 17:34:17.347           Disc of type 3 was detected <0xb76cf6d0>
05      11/24/07 17:34:17.347           Not firing the event <0xb76cf6d0>

chrisbirkinshaw

  • Guru
  • ****
  • Posts: 431
    • View Profile
Re: Disk_Drive device never starts
« Reply #3 on: November 24, 2007, 07:14:44 pm »
What do you see when you do "sudo screen -r"?

EDIT:

And are there any errors in that log file you mentioned?

There is no screen open for the Disk Drive. I created one manually like this:

 screen -d -m -S DISK_DRIVE /usr/pluto/bin/Disk_Drive -d 26 -l /var/log/pluto/26_Disk_Drive.log

And now I see the same thing in the log as for the diskless MD (event not fired). However, I think perhaps this is normal as the DCERouter registers something:

Received Message from 0 (unknown / ) to Media Plug-in(10), type 1 id  391 Command:Add Media Attribute, retry none, parameters: <0x615c2b90>
08      11/24/07 17:51:59.881             Parameter 5(Value To Assign): * <0x615c2b90>
08      11/24/07 17:51:59.881             Parameter 122(EK_AttributeType): 30 <0x615c2b90>
08      11/24/07 17:51:59.881             Parameter 145(EK_File): 10948 <0x615c2b90>
05      11/24/07 17:51:59.933           Socket::ReceiveData 0x8857da8 failed, bytes left 0 start: 3000000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 191 Incoming_Conn Socket 191 192.168.1.1 <0x615c2b90>
05      11/24/07 17:51:59.933           Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 191 192.168.1.1 <0x615c2b90>
05      11/24/07 17:51:59.933           TCPIP: Closing connection to -1003 (Router Dev #0) 0x8857da8 m_Socket: -1 <0x615c2b90>
05      11/24/07 17:51:59.933           Router::RemoveAndDeleteSocket 0x8857da8 -1003 <0x615c2b90>

chrisbirkinshaw

  • Guru
  • ****
  • Posts: 431
    • View Profile
Re: Disk_Drive device never starts
« Reply #4 on: November 24, 2007, 07:43:35 pm »
Ok, it's working, though I have to start the device manually. I wrote a little script to do this in an endless loop so that it survives a router reload. Is there anything else I can do?

I also noticed that LMCE cannot rip to an external device. The device is mounted as HDD2 [71] which gets split up and appears in the logs as /home/public/data/videos/HDD2  71 / giving a disk full error. I suspect this is because my root partition does not have space for a DVD and it falls back to ripping it there.

Chris

Zaerc

  • Alumni
  • LinuxMCE God
  • *
  • Posts: 2256
  • Department of Redundancy Department.
    • View Profile
Re: Disk_Drive device never starts
« Reply #5 on: November 24, 2007, 07:54:39 pm »
Normally that device should get started automaticly, is there a "Disk Drive" in the devices tree under the "OnScreen Orbiter"?
"Change is inevitable. Progress is optional."
-- Anonymous


chrisbirkinshaw

  • Guru
  • ****
  • Posts: 431
    • View Profile
Re: Disk_Drive device never starts
« Reply #6 on: November 24, 2007, 08:07:40 pm »
Yes it's there. The problem is worse than I thought. My diskless MD is pretty much useless:

# tail 98_LaunchOrbiter.sh.log
1       11/24/07 18:14:08       98 (spawning-device)    Starting... 1
1       11/24/07 18:14:08       98 (spawning-device)    Found /usr/pluto/bin/LaunchOrbiter.sh
05      11/24/07 18:14:10.152           will overwrite wm window id // void X11wrapper::Assign_WmWindow(Window) <0xb67d7b10>
05      11/24/07 18:14:10.833           Creating child 99 <0xb67d7b10>
05      11/24/07 18:14:10.885           Creating child 101 <0xb67d7b10>
05      11/24/07 18:14:10.926           Creating child 102 <0xb67d7b10>
05      11/24/07 18:14:10.966           Creating child 103 <0xb67d7b10>
05      11/24/07 18:14:11.056           Creating child 104 <0xb67d7b10>
05      11/24/07 18:14:11.086           Creating child 105 <0xb67d7b10>
05      11/24/07 18:14:43.293           Continuing anyway with 5 devices not registered: 97,102,103,105,130, <0xb67d7b10>


Those devices are the app server, mythtv, disk drive, external media indentifier, and the lirc device. Again, the logs do not give any clues at to why they are not being started. I might rebuild the MD and see what happens.


Regards,

Chris