Send Motion-user mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."
Today's Topics:
1. Re: Recording Skip (Roger Heflin)
2. Re: Recording Skip (Jack Christensen)
3. Re: Recording Skip (Barry Martin)
----------------------------------------------------------------------
Message: 1
Date: Sat, 12 Apr 2025 12:14:13 -0500
From: Roger Heflin <[email protected]>
To: Motion discussion list <[email protected]>
Subject: Re: [Motion-user] Recording Skip
Message-ID:
<CAAMCDef5g=06fDoVG+abb_S=upvu+fbq2z+45vmto3gy9ny...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
I use an SSD to initially save my images and then daily I move those
images to spinning disks.
Without doing that any slight issue with the disk will cause dropouts.
An error on the disk will cause a 3-30second blip depending on the
what the disks default timeout is.
this is a sample of smartctl output:
smartctl --xall /dev/sda | grep -iE 'sector|UNC'
Sector Sizes: 512 bytes logical, 4096 bytes physical
5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0
197 Current_Pending_Sector -O--CK 200 200 000 - 0
198 Offline_Uncorrectable ----CK 200 200 000 - 0
SMART Log Directory Version 1 [multi-sector log support]
SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
COUNT = Count (was: Sector Count) Register
LL = LBA Low (was: Sector Number) Register ]
40 -- 51 00 00 00 00 bc 9c 57 f8 40 00 Error: UNC at LBA =
0xbc9c57f8 = 3164362744
40 -- 51 00 00 00 00 55 57 f0 88 40 00 Error: UNC at LBA =
0x5557f088 = 1431826568
40 -- 51 00 00 00 01 36 58 20 70 40 00 Error: UNC at LBA =
0x136582070 = 5206712432
40 -- 51 00 00 00 00 47 86 ce 78 40 00 Error: UNC at LBA =
0x4786ce78 = 1200017016
40 -- 51 00 00 00 01 2b e1 e0 00 40 00 Error: UNC at LBA =
0x12be1e000 = 5031190528
40 -- 51 00 00 00 00 87 62 10 48 40 00 Error: UNC at LBA =
0x87621048 = 2271350856
SMART Extended Self-test Log Version: 1 (1 sectors)
The realllocated/pending counts rising will cause a several second
blip, and the UNC errors will cause blips.
I have a cron job that saves a log for each disk daily so I can rule
out a disk issue causing a blip.
On Sat, Apr 12, 2025 at 11:05?AM Barry Martin <[email protected]> wrote:
>
>
> Hi JMB!
> >
> > Try using 'top' to monitor the system load. Maybe 'disk' writes (to
> > the NAS) are piling up. Maybe some background process is consuming
> > excessive CPU? Did it start after a recent 'sudo aptitude safe-update'?
>
> Will try your suggestions -- right now not sure how to correlate (right
> word?) the time of the skip with top's activity reporting but will
> experiment and learn! Most Motion recordings are fine (no skip/glitch)
> -- I did forget to mention that originally. Skip/glitch problem has been
> occurred for some time, so can't blame a specific upgrade.
>
> Will report back!
>
> Barry
>
>
>
>
>
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
------------------------------
Message: 2
Date: Sat, 12 Apr 2025 14:50:54 -0400
From: Jack Christensen <[email protected]>
To: [email protected]
Subject: Re: [Motion-user] Recording Skip
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Sounds similar to an issue I had. Motion was waiting for the
on_movie_end script to end. Fixed by commit 035b1af.
See https://github.com/Motion-Project/motion/issues/1856
On 4/12/25 11:05, Barry Martin wrote:
>
>
> Hi!
>
> ?Slightly? off-topic but involving my Motion cameras. Randomly the
> recording will skip several seconds. There is motion going on, so
> should record, but while the motion is occurring (and being recorded)
> the video will skip several seconds: no grey, no pixelation, just as
> if someone took scissors to the film (showing my age! <g>). Does not
> occur constantly/consistently.
>
>
> Appears has something to do with either the WiFi (5G) between the
> Motion units (so RF transmission/reception) and/or the actual
> recording to the hard drive on the NAS. Looking for a clue how to
> figure out and hopefully correct the problem. Yesterday checked and
> the glitch occurred on two cameras with overlapping fields of view and
> recording simultaneously:
>
> Unit #201 14:15:41 <skip> 14:16:25
>
> Unit #202 14:15:43 <skip> 14:16:25
>
>
> Nothing significant about the time; nobody near the Motion units nor
> WiFi router, so not like someone walked in the RF path. LIS, the
> glitch occurs randomly; just listed the times should the ~45 seconds
> of missing recording have a potential troubleshooting meaning. (I
> don?t know the times of previous glitches.)
>
>
>
> Both units:
>
> *
>
> Motion Version 4.5.1
>
> *
>
> Raspberry Pi 4B, with one USB camera each
>
> *
>
> Individual power supply on UPS
>
> *
>
> Uptime: (several days ago)
>
>
> The WiFi and NAS are also on their own UPSs, and no power issues.
>
>
> Thanks for the help!
>
> Barry
>
>
>
>
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe:https://lists.sourceforge.net/lists/options/motion-user
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 3
Date: Sat, 12 Apr 2025 16:11:49 -0500
From: Barry Martin <[email protected]>
To: [email protected]
Subject: Re: [Motion-user] Recording Skip
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed
Hi Jack!
>
> Sounds similar to an issue I had. Motion was waiting for the
> on_movie_end script to end. Fixed by commit 035b1af.
>
> See https://github.com/Motion-Project/motion/issues/1856
>
Initially looks to be part of Roger's suggestion? to save to SSD.???
...Generally /tmp is on a drive, not RAM. but easy enough to tell where
to (temporarily) store the files.
In my case it seems the final storage location (the NAS's HDD) is the
issue based on Roger's message.? If the glitches were independent (at
different times) I'd think your suggestion was more correct but with the
glitch at almost exactly the same time the HDD issue seems more correct.
I'm definitely not excluding your suggestion -- will be keeping it for
reference -- so thank you!
Barry
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 221, Issue 2
*******************************************
