Please help me fix MyController on a Raspberry Pi that is very sick due to a full SSD



  • Recently the SSD filled up on my Raspberry Pi system which runs MyController. The full disk was my fault (Motioneye), not MyController. I've removed files from the SSD and now have a lot of empty space, but MyController is not very happy. Some of the problems are:

    • Very slow to display a dashboard (many minutes)
    • Sensor Graphical View and Sensor Custom Buttons widgets don't display (spinning circle with "loading" in a Chrome browser)
    • Error from the Sensors widget ("could not resolve all promises: could not load template:")
    • Error when sending a raw message ("403: Forbidden")

    Following are some message from the MyController server log. There are lots of errors which I'm not sure how to fix.

    vletDispatcher.java:51)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    	at Acme.Serve.Serve$ServeConnection.runServlet(Serve.java:2328)
    	at Acme.Serve.Serve$ServeConnection.parseRequest(Serve.java:2282)
    	at Acme.Serve.Serve$ServeConnection.run(Serve.java:2054)
    	at Acme.Utils$ThreadPool$PooledThread.run(Utils.java:1402)
    	at java.lang.Thread.run(Thread.java:748)
    Caused by: java.net.SocketException: Broken pipe (Write failed)
    	at java.net.SocketOutputStream.socketWrite0(Native Method)
    	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:111)
    	at java.net.SocketOutputStream.write(SocketOutputStream.java:143)
    	at Acme.Serve.Serve$ServeOutputStream.flush(Serve.java:4889)
    	at Acme.Serve.Serve$ServeOutputStream.close(Serve.java:4923)
    	at org.jboss.resteasy.plugins.server.servlet.HttpServletResponseWrapper$DeferredOutputStream.close(HttpServletResponseWrapper.java:58)
    	at org.jboss.resteasy.util.CommitHeaderOutputStream.close(CommitHeaderOutputStream.java:87)
    	at org.jboss.resteasy.util.DelegatingOutputStream.close(DelegatingOutputStream.java:60)
    	at com.fasterxml.jackson.core.json.UTF8JsonGenerator.close(UTF8JsonGenerator.java:1060)
    	at org.jboss.resteasy.plugins.providers.jackson.ResteasyJackson2Provider.writeTo(ResteasyJackson2Provider.java:209)
    	at org.mycontroller.standalone.api.jaxrs.mixins.McJacksonJson2Provider.writeTo(McJacksonJson2Provider.java:120)
    	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.writeTo(AbstractWriterInterceptorContext.java:131)
    	at org.jboss.resteasy.core.interception.ServerWriterInterceptorContext.writeTo(ServerWriterInterceptorContext.java:60)
    	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.proceed(AbstractWriterInterceptorContext.java:120)
    	at org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor.aroundWriteTo(GZIPEncodingInterceptor.java:100)
    	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.proceed(AbstractWriterInterceptorContext.java:124)
    	at org.jboss.resteasy.core.ServerResponseWriter.writeNomapResponse(ServerResponseWriter.java:98)
    	at org.jboss.resteasy.core.SynchronousDispatcher.writeResponse(SynchronousDispatcher.java:466)
    	... 12 more
    
    [Fri Mar 22 04:50:09 CST 2019] Unexpected problem running servlet: org.jboss.resteasy.spi.UnhandledException: RESTEASY003770: Response is committed, can't handle exception
    2019-03-22 04:50:12,920 WARN [mc-th-pool-8] [org.mycontroller.standalone.rule.McRuleEngine:184] Scheduled Rule exuection skipped. Engine not available for more than 4000 ms
    2019-03-22 04:50:13,769 WARN [mc-th-pool-6] [org.mycontroller.standalone.rule.McRuleEngine:184] Scheduled Rule exuection skipped. Engine not available for more than 4000 ms
    2019-03-22 04:52:06,319 WARN [mc-th-pool-0] [org.mycontroller.standalone.rule.McRuleEngine:184] Scheduled Rule exuection skipped. Engine not available for more than 4000 ms
    2019-03-22 04:53:57,361 WARN [mc-th-pool-7] [org.mycontroller.standalone.rule.McRuleEngine:184] Scheduled Rule exuection skipped. Engine not available for more than 4000 ms
    [Fri Mar 22 04:55:45 CST 2019] Unexpected problem running servlet
    org.jboss.resteasy.spi.UnhandledException: RESTEASY003770: Response is committed, can't handle exception
    	at org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:167)
    	at org.jboss.resteasy.core.SynchronousDispatcher.writeResponse(SynchronousDispatcher.java:471)
    	at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:415)
    	at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:202)
    	at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221)
    	at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
    	at org.jboss.resteasy.plugins.server.tjws.TJWSServletDispatcher.service(TJWSServletDispatcher.java:40)
    	at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    	at Acme.Serve.Serve$ServeConnection.runServlet(Serve.java:2328)
    	at Acme.Serve.Serve$ServeConnection.parseRequest(Serve.java:2282)
    	at Acme.Serve.Serve$ServeConnection.run(Serve.java:2054)
    	at Acme.Utils$ThreadPool$PooledThread.run(Utils.java:1402)
    	at java.lang.Thread.run(Thread.java:748)
    Caused by: java.net.SocketException: Broken pipe (Write failed)
    	at java.net.SocketOutputStream.socketWrite0(Native Method)
    	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:111)
    	at java.net.SocketOutputStream.write(SocketOutputStream.java:143)
    	at Acme.Serve.Serve$ServeOutputStream.flush(Serve.java:4889)
    	at Acme.Serve.Serve$ServeOutputStream.close(Serve.java:4923)
    	at org.jboss.resteasy.plugins.server.servlet.HttpServletResponseWrapper$DeferredOutputStream.close(HttpServletResponseWrapper.java:58)
    	at org.jboss.resteasy.util.CommitHeaderOutputStream.close(CommitHeaderOutputStream.java:87)
    	at org.jboss.resteasy.util.DelegatingOutputStream.close(DelegatingOutputStream.java:60)
    	at com.fasterxml.jackson.core.json.UTF8JsonGenerator.close(UTF8JsonGenerator.java:1060)
    	at org.jboss.resteasy.plugins.providers.jackson.ResteasyJackson2Provider.writeTo(ResteasyJackson2Provider.java:209)
    	at org.mycontroller.standalone.api.jaxrs.mixins.McJacksonJson2Provider.writeTo(McJacksonJson2Provider.java:120)
    	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.writeTo(AbstractWriterInterceptorContext.java:131)
    	at org.jboss.resteasy.core.interception.ServerWriterInterceptorContext.writeTo(ServerWriterInterceptorContext.java:60)
    	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.proceed(AbstractWriterInterceptorContext.java:120)
    	at org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor.aroundWriteTo(GZIPEncodingInterceptor.java:100)
    	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.proceed(AbstractWriterInterceptorContext.java:124)
    	at org.jboss.resteasy.core.ServerResponseWriter.writeNomapResponse(ServerResponseWriter.java:98)
    	at org.jboss.resteasy.core.SynchronousDispatcher.writeResponse(SynchronousDispatcher.java:466)
    	... 12 more
    
    [Fri Mar 22 04:55:45 CST 2019] Unexpected problem running servlet: org.jboss.resteasy.spi.UnhandledException: RESTEASY003770: Response is committed, can't handle exception
    2019-03-22 04:55:49,589 WARN [mc-th-pool-8] [org.mycontroller.standalone.rule.McRuleEngine:184] Scheduled Rule exuection skipped. Engine not available for more than 4000 ms
    [Fri Mar 22 04:57:37 CST 2019] Unexpected problem running servlet
    org.jboss.resteasy.spi.UnhandledException: RESTEASY003770: Response is committed, can't handle exception
    	at org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:167)
    	at org.jboss.resteasy.core.SynchronousDispatcher.writeResponse(SynchronousDispatcher.java:471)
    	at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:415)
    	at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:202)
    	at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221)
    	at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
    	at org.jboss.resteasy.plugins.server.tjws.TJWSServletDispatcher.service(TJWSServletDispatcher.java:40)
    	at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    	at Acme.Serve.Serve$ServeConnection.runServlet(Serve.java:2328)
    	at Acme.Serve.Serve$ServeConnection.parseRequest(Serve.java:2282)
    	at Acme.Serve.Serve$ServeConnection.run(Serve.java:2054)
    	at Acme.Utils$ThreadPool$PooledThread.run(Utils.java:1402)
    	at java.lang.Thread.run(Thread.java:748)
    Caused by: java.net.SocketException: Broken pipe (Write failed)
    	at java.net.SocketOutputStream.socketWrite0(Native Method)
    	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:111)
    	at java.net.SocketOutputStream.write(SocketOutputStream.java:143)
    	at Acme.Serve.Serve$ServeOutputStream.flush(Serve.java:4889)
    	at Acme.Serve.Serve$ServeOutputStream.close(Serve.java:4923)
    	at org.jboss.resteasy.plugins.server.servlet.HttpServletResponseWrapper$DeferredOutputStream.close(HttpServletResponseWrapper.java:58)
    	at org.jboss.resteasy.util.CommitHeaderOutputStream.close(CommitHeaderOutputStream.java:87)
    	at org.jboss.resteasy.util.DelegatingOutputStream.close(DelegatingOutputStream.java:60)
    	at com.fasterxml.jackson.core.json.UTF8JsonGenerator.close(UTF8JsonGenerator.java:1060)
    	at org.jboss.resteasy.plugins.providers.jackson.ResteasyJackson2Provider.writeTo(ResteasyJackson2Provider.java:209)
    	at org.mycontroller.standalone.api.jaxrs.mixins.McJacksonJson2Provider.writeTo(McJacksonJson2Provider.java:120)
    	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.writeTo(AbstractWriterInterceptorContext.java:131)
    	at org.jboss.resteasy.core.interception.ServerWriterInterceptorContext.writeTo(ServerWriterInterceptorContext.java:60)
    	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.proceed(AbstractWriterInterceptorContext.java:120)
    	at org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor.aroundWriteTo(GZIPEncodingInterceptor.java:100)
    	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.proceed(AbstractWriterInterceptorContext.java:124)
    	at org.jboss.resteasy.core.ServerResponseWriter.writeNomapResponse(ServerResponseWriter.java:98)
    	at org.jboss.resteasy.core.SynchronousDispatcher.writeResponse(SynchronousDispatcher.java:466)
    	... 12 more
    
    [Fri Mar 22 04:57:37 CST 2019] Unexpected problem running servlet: org.jboss.resteasy.spi.UnhandledException: RESTEASY003770: Response is committed, can't handle exception
    [Fri Mar 22 04:57:38 CST 2019] Unexpected problem running servlet
    org.jboss.resteasy.spi.UnhandledException: RESTEASY003770: Response is committed, can't handle exception
    	at org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:167)
    	at org.jboss.resteasy.core.SynchronousDispatcher.writeResponse(SynchronousDispatcher.java:471)
    	at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:415)
    	at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:202)
    	at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221)
    	at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
    	at org.jboss.resteasy.plugins.server.tjws.TJWSServletDispatcher.service(TJWSServletDispatcher.java:40)
    	at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    	at Acme.Serve.Serve$ServeConnection.runServlet(Serve.java:2328)
    	at Acme.Serve.Serve$ServeConnection.parseRequest(Serve.java:2282)
    	at Acme.Serve.Serve$ServeConnection.run(Serve.java:2054)
    	at Acme.Utils$ThreadPool$PooledThread.run(Utils.java:1402)
    	at java.lang.Thread.run(Thread.java:748)
    Caused by: java.net.SocketException: Broken pipe (Write failed)
    	at java.net.SocketOutputStream.socketWrite0(Native Method)
    	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:111)
    	at java.net.SocketOutputStream.write(SocketOutputStream.java:143)
    	at Acme.Serve.Serve$ServeOutputStream.flush(Serve.java:4889)
    	at Acme.Serve.Serve$ServeOutputStream.close(Serve.java:4923)
    	at org.jboss.resteasy.plugins.server.servlet.HttpServletResponseWrapper$DeferredOutputStream.close(HttpServletResponseWrapper.java:58)
    	at org.jboss.resteasy.util.CommitHeaderOutputStream.close(CommitHeaderOutputStream.java:87)
    	at org.jboss.resteasy.util.DelegatingOutputStream.close(DelegatingOutputStream.java:60)
    	at com.fasterxml.jackson.core.json.UTF8JsonGenerator.close(UTF8JsonGenerator.java:1060)
    	at org.jboss.resteasy.plugins.providers.jackson.ResteasyJackson2Provider.writeTo(ResteasyJackson2Provider.java:209)
    	at org.mycontroller.standalone.api.jaxrs.mixins.McJacksonJson2Provider.writeTo(McJacksonJson2Provider.java:120)
    	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.writeTo(AbstractWriterInterceptorContext.java:131)
    	at org.jboss.resteasy.core.interception.ServerWriterInterceptorContext.writeTo(ServerWriterInterceptorContext.java:60)
    	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.proceed(AbstractWriterInterceptorContext.java:120)
    	at org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor.aroundWriteTo(GZIPEncodingInterceptor.java:100)
    	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.proceed(AbstractWriterInterceptorContext.java:124)
    	at org.jboss.resteasy.core.ServerResponseWriter.writeNomapResponse(ServerResponseWriter.java:98)
    	at org.jboss.resteasy.core.SynchronousDispatcher.writeResponse(SynchronousDispatcher.java:466)
    	... 12 more
    
    [Fri Mar 22 04:57:38 CST 2019] Unexpected problem running servlet: org.jboss.resteasy.spi.UnhandledException: RESTEASY003770: Response is committed, can't handle exception
    2019-03-22 04:57:41,079 WARN [mc-th-pool-1] [org.mycontroller.standalone.rule.McRuleEngine:184] Scheduled Rule exuection skipped. Engine not available for more than 4000 ms
    [Fri Mar 22 04:58:42 CST 2019] Unexpected problem running servlet
    org.jboss.resteasy.spi.UnhandledException: RESTEASY003770: Response is committed, can't handle exception
    	at org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:167)
    	at org.jboss.resteasy.core.SynchronousDispatcher.writeResponse(SynchronousDispatcher.java:471)
    	at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:415)
    	at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:202)
    	at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221)
    	at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56)
    	at org.jboss.resteasy.plugins.server.tjws.TJWSServletDispatcher.service(TJWSServletDispatcher.java:40)
    	at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51)
    	at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    	at Acme.Serve.Serve$ServeConnection.runServlet(Serve.java:2328)
    	at Acme.Serve.Serve$ServeConnection.parseRequest(Serve.java:2282)
    	at Acme.Serve.Serve$ServeConnection.run(Serve.java:2054)
    	at Acme.Utils$ThreadPool$PooledThread.run(Utils.java:1402)
    	at java.lang.Thread.run(Thread.java:748)
    Caused by: java.net.SocketException: Broken pipe (Write failed)
    	at java.net.SocketOutputStream.socketWrite0(Native Method)
    	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:111)
    	at java.net.SocketOutputStream.write(SocketOutputStream.java:143)
    	at Acme.Serve.Serve$ServeOutputStream.flush(Serve.java:4889)
    	at Acme.Serve.Serve$ServeOutputStream.close(Serve.java:4923)
    	at org.jboss.resteasy.plugins.server.servlet.HttpServletResponseWrapper$DeferredOutputStream.close(HttpServletResponseWrapper.java:58)
    	at org.jboss.resteasy.util.CommitHeaderOutputStream.close(CommitHeaderOutputStream.java:87)
    	at org.jboss.resteasy.util.DelegatingOutputStream.close(DelegatingOutputStream.java:60)
    	at com.fasterxml.jackson.core.json.UTF8JsonGenerator.close(UTF8JsonGenerator.java:1060)
    	at org.jboss.resteasy.plugins.providers.jackson.ResteasyJackson2Provider.writeTo(ResteasyJackson2Provider.java:209)
    	at org.mycontroller.standalone.api.jaxrs.mixins.McJacksonJson2Provider.writeTo(McJacksonJson2Provider.java:120)
    	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.writeTo(AbstractWriterInterceptorContext.java:131)
    	at org.jboss.resteasy.core.interception.ServerWriterInterceptorContext.writeTo(ServerWriterInterceptorContext.java:60)
    	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.proceed(AbstractWriterInterceptorContext.java:120)
    	at org.jboss.resteasy.plugins.interceptors.encoding.GZIPEncodingInterceptor.aroundWriteTo(GZIPEncodingInterceptor.java:100)
    	at org.jboss.resteasy.core.interception.AbstractWriterInterceptorContext.proceed(AbstractWriterInterceptorContext.java:124)
    	at org.jboss.resteasy.core.ServerResponseWriter.writeNomapResponse(ServerResponseWriter.java:98)
    	at org.jboss.resteasy.core.SynchronousDispatcher.writeResponse(SynchronousDispatcher.java:466)
    	... 12 more
    

    I restored a MyController backup from before the problem, but that didn't help. I also rebooted the Raspberry Pi.

    If I was close to the system I would restore the SSD from an image I made on a Windows PC, however I won't be able to touch the system for about two months due to my current location.

    I'd like to be as cautions as possible in fixing this problem since I can't physically access the Raspberry Pi or serial gateway (for a power cycle).

    My basic hardware and software configuration is:

    • Raspberry Pi 3 B+
    • 120 GB SSD and SD card (for booting)
    • Raspbian 9 (Stretch)
    • MyController 1.4.0-Snapshot (this fixed a problem I was having)
    • MySensors 2.3.0 serial gateway

    FYI, I use the https://remote.it/ service for HTTP and SSH access to the Raspberry Pi. It works well without opening ports on your router.

    Thanks much in advance.



  • @TomG can you send complete logs to my mail? jkandasa at gmail dot com

    Also, I need the following commands output.

    df -h
    df -h /path/to/mycontroller
    free -m
    ps -ef | grep mycontroller
    


  • @jkandasa, I just emailed you the information your requested.

    Thanks much for your help!



  • @TomG @jkandasa

    Sorry to hear about the problem TomG - I have 2 things to add to this....

    1. Did you manage to resize the image once it was on the SSD? I have copied my SD card across but only the SD card size seems to be available. Maybe someone knows how to resize image on ssd (not the same as SD card procedure).

    2. I have motioneye on a separate pi to mycontroller. I have asked if image streams from this could be accommodated in mycontroller 2 in the future. I think it would be good to have a page in mycontroller that either has an embedded image from a camera with us being able to see the room we want to control and add buttons to control the camera pan/tilt (all easily done with mysensors and a couple of small stepper motors).

    Or, have mycontroller be able to show video in full window with selected control buttons overlaid on the image. Again we can then see if the lights really do turn on etc.....

    Getting back to the problem, do you have a good quality power supply for the system? Motioneye alone is a power beast and needs a good stable power supply. Also, what are you doing about heat? Again motioneye generates a lot of heat on the CPU and even with the largest heatsink it gets very hot. I will be re-housing mine soon to add a fan as well as it is one of the few pi machines here without one (and it seems it would benefit greatly from one)!...

    Just some thoughts....



  • @skywatch

    I didn't move the image from the SD card to the SSD. I created a new partition on the SSD and used rcp to copy the root partition from the SD to the SSD (there is more involved to make this work). My boot partition is still on the SD. I couldn't get the Pi to reboot with the entire system on the SSD (it worked fine from a power cycle). This was probably fixable, but I had spent enough time on it and I gave up. My goal was to have the larger capacity and reliability of an SSD, and booting from the SD and having the running system on the SSD accomplished that goal.

    Camera support in MyController would be nice, however Motioneye does a good job.

    My power supply is the 2.5a one that came with the CanaKit Raspberry Pi (https://www.amazon.com/dp/B07BC7BMHY/ref=cm_sw_em_r_mt_dp_U_qaULCbCN3G2DF). I haven't heard of any problems with this power supply.

    My Pi has 3 heat sinks and a case with a fan. It is possible the fan failed, but I won't know that for a couple of months when I travel to the location with the system.

    Keeping the MyController and Motioneye systems separated is (in retrospect) a good idea. It was cheaper and easier to manage remotely with both of them on one system. My one Raspberry Pi has enough storage and CPU performance to handle both programs, but that didn't make it a good idea.

    Thanks much for your thoughts and suggestions.



  • @TomG

    I didn't move the image from the SD card to the SSD. I created a new partition on the SSD and used rcp to copy the root partition from the SD to the SSD (there is more involved to make this work).

    Please can you tell me more on this? I have tried and tried to get it to boot meos from ssd without any luck (cmdline.txt with root=/dev/sda1 and various other connotations)..... The dev is no help at all despite many people with the same issue 😞 .
    Jkandasa is a god in comparison to this guy. 🙂 🙂 🙂

    My boot partition is still on the SD. I couldn't get the Pi to reboot with the entire system on the SSD (it worked fine from a power cycle).

    I have experienced the exact same thing. But now sometimes it will reboot, just that it is not at all reliable. So I only do this when I am home and near the pi just in case 😉

    booting from the SD and having the running system on the SSD accomplished that goal.

    I may have to do this too then. Pity to waste an SD card for something that is supported by the pi though. Sooner or later this will have to be done.

    Camera support in MyController would be nice, however Motioneye does a good job.

    Yes. I just think that we could use mysensors to control diy pan/tilt stepper or servo controls that would be nice. To have just one page with video image, pan/tilt
    and other related controls in one place would be good. You could turn on the lights and instantly see confirmation in the video window.....

    My Pi has 3 heat sinks and a case with a fan. It is possible the fan failed, but I won't know that for a couple of months when I travel to the location with the system.
    You can use mcagent to keep a record of cpu temperature. I use this and always know if the fan stalled or got something stuck in it!
    My one Raspberry Pi has enough storage and CPU performance to handle both programs, but that didn't make it a good idea.
    Nor a bad one, just a learning curve of experience! 😉

    Thanks much for your thoughts and suggestions.
    You are welcome. I am no genius with this stuff but it doesn't stop me trying to help people! 😉

    A little bit late now I suppose, but you can limit the the storage used my meos in the settings. Or send that data to a remote ftp server.



  • @skywatch said in Please help me fix MyController on a Raspberry Pi that is very sick due to a full SSD:

    Please can you tell me more on this? I have tried and tried to get it to boot meos from ssd without any luck (cmdline.txt with root=/dev/sda1 and various other connotations).....

    I'll write up my notes on this and post them to the forum.



  • @TomG Don't worry about it for me - I was responding line by line and only later learned you were booting from SD, so not of interest to me...... I'll keep trying with ssd boot or try another cctv app.

    Thanks for the offer though! 🙂



  • @skywatch

    FYI, even thought I'm still booting from the SD card, everything runs off the SSD after the system is up and running.



  • @TomG Thanks - I have a few pi2 running like that as they can't boot from SD, so I know how you do that.

    I have thoughts on what I can do next, but it is Mothers Day here tomorrow and I will be busy all weekend 😞


Log in to reply
 

Suggested Topics

5
Online

483
Users

412
Topics

2.5k
Posts