reboot after 21 days worked, but with fault - page 3 - General Help and Assistance on using CHDK stable releases - CHDK Forum supplierdeeply
« previous next »
Pages: 1 2 [3] 4   Go Down

reboot after 21 days worked, but with fault

  • 32 Replies
  • 1976 Views
*

Offline waterwingz

  • ******
  • 11980
    • Waterwingz
Re: reboot after 21 days worked, but with fault
« Reply #20 on: 02 / July / 2019, 16:15:23 »
Advertisements
Quote from: Mlapse on 02 / July / 2019, 15:37:10
as far as i know the failed shots are 384, 543, 550, 576.
... plus  five more :
Day 21 Sat Jun  1 19:52:33 2019 IMG_0384.JPG tv: 1/125 f: 3.9 ISO: 75 bv: 681  V: 3.949 T: 38 **1**
Day 21 Sat Jun  1 19:53:00 2019 IMG_0384.JPG tv: 1/125 f: 3.8 ISO: 75 bv: 677  V: 3.94 T: 38

Day 21 Sat Jun  1 21:11:04 2019 IMG_0539.JPG tv: 0.6 f: 3.1 ISO: 75 bv: 14  V: 3.953 T: 37 **2**
Day 21 Sat Jun  1 21:11:30 2019 IMG_0539.JPG tv: 0.6 f: 3.1 ISO: 75 bv: 5  V: 3.94 T: 37

Day 21 Sat Jun  1 21:13:34 2019 IMG_0543.JPG tv: 0.6 f: 3.1 ISO: 75 bv: -27  V: 3.949 T: 37 **3**
Day 21 Sat Jun  1 21:14:00 2019 IMG_0543.JPG tv: 0.6 f: 3.1 ISO: 75 bv: -35  V: 3.94 T: 37

Day 21 Sat Jun  1 21:17:34 2019 IMG_0550.JPG tv: 0.8 f: 3.1 ISO: 75 bv: -89  V: 3.949 T: 37 **4**
Day 21 Sat Jun  1 21:18:00 2019 IMG_0550.JPG tv: 1 f: 3.1 ISO: 75 bv: -97  V: 3.944 T: 37

Day 21 Sat Jun  1 21:31:36 2019 IMG_0576.JPG tv: 1 f: 3.1 ISO: 75 bv: -304  V: 3.953 T: 37 **5**
Day 21 Sat Jun  1 21:32:00 2019 IMG_0576.JPG tv: 1 f: 3.1 ISO: 75 bv: -309  V: 3.916 T: 37

Day 21 Sat Jun  1 21:43:40 2019 IMG_0599.JPG tv: 1 f: 3.1 ISO: 75 bv: -454  V: 3.949 T: 36 **6**
Day 21 Sat Jun  1 21:44:01 2019 IMG_0599.JPG tv: 1 f: 3.1 ISO: 75 bv: -459  V: 3.944 T: 36

Day 22 Sun Jun  2 03:17:09 2019 IMG_0395.JPG tv: 1 f: 3.1 ISO: 75 bv: -370  V: 3.949 T: 35 **7**
Day 22 Sun Jun  2 03:17:32 2019 IMG_0395.JPG tv: 1 f: 3.1 ISO: 75 bv: -365  V: 3.944 T: 35

Day 22 Sun Jun  2 03:33:36 2019 IMG_0426.JPG tv: 1 f: 3.1 ISO: 75 bv: -187  V: 3.944 T: 35 **8**
Day 22 Sun Jun  2 03:34:01 2019 IMG_0426.JPG tv: 1 f: 3.1 ISO: 75 bv: -182  V: 3.94 T: 35

Day 22 Sun Jun  2 03:46:05 2019 IMG_0450.JPG tv: 0.6 f: 3.1 ISO: 75 bv: -27  V: 3.944 T: 35 **9**
Day 22 Sun Jun  2 03:46:31 2019 IMG_0450.JPG tv: 0.6 f: 3.1 ISO: 75 bv: -20  V: 3.944 T: 35


Quote
if you think that adapting the script could give us relevant info I'm willing to test again.
It would interesting to see what comes out of it.  Are you already running a tweaked script?  (Something about longer start/restart delay to allow for card indexing?)

Quote
but I think this problem will also occur if i reboot after a day, so i could try that first if you are interested.
I'm skeptical but it's worth a try if it speeds up time to failure (and thus allows more tesing).

Quote
since it only occurs after reboot,
It happens hours and many shots after the reboot. I have a hard time believing it's reboot related.

Quote
it might be related to the lens zoom done by CF after UI is started?
Again, it happens hours and many shots after the lens zoom.

Quote
The card was new when i did this test and it has given no indication that something is wrong. i did fill it up again after the shoot and verified the writes, all as expected without faults
Well, the card is another potential variable.  If you are running tests, trying a different card seems like another potentially valuable test case.
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline Mlapse

  • ***
  • 237
  • A480 A490 S95 M10
Re: reboot after 21 days worked, but with fault
« Reply #21 on: 02 / July / 2019, 16:38:40 »
I'm running the 1.5 CHDK with a 10 sec. delay at startup, no delay in the script is set (yet)
I have some other tweaks done to UI, but i can do without those.

I'm grasping at straws here.....
I know it takes hours after the reboot, but the double click in debug is only a fraction of a second, so maybe it just takes hours before it becomes seconds and derails the timing.
and I have at least 100 log files of 20.000 shots or more without reboot and without skipped frames

I have no 2nd SD card that can run 2880 shots a day for more than 21 days, but for the setup with a reboot a day I have enough sd cards.

I will try to setup the reboot a day sequence tomorrow, so we might have a result at the end of the week.
Logged
frustration is a key ingredient in progress
*

Offline waterwingz

  • ******
  • 11980
    • Waterwingz
Re: reboot after 21 days worked, but with fault
« Reply #22 on: 02 / July / 2019, 16:52:43 »
Quote from: Mlapse on 02 / July / 2019, 16:38:40
but the double click in debug is only a fraction of a second, so maybe it just takes hours before it becomes seconds and derails the timing.
You've lost me here.  Debug?

Edit :  test version that logs return status of shoot(  ) attached.
« Last Edit: 02 / July / 2019, 17:08:38 by waterwingz »
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline Mlapse

  • ***
  • 237
  • A480 A490 S95 M10
Re: reboot after 21 days worked, but with fault
« Reply #23 on: 02 / July / 2019, 17:27:47 »
before i did the 3 weeks run i did a number of runs in debug.
as you might remember one of the problems i encountered was that after one or two reboots you could hear a double click before the shot.
but i then assumed it had to do with that moving of the lens that only occured after a reboot.
the lens movement seemed to have dissolved after the 10 sec. start delay..and i was so happy with that that i never checked if the double click was gone.

I will test your script in the next couple of days and first set reboot to 1 day. If that does not result in skipped frames I will let it run at day 21 reboot. I will keep all other settings the same as with the previous run.

I wanted to include a log of a week without problems, but the max filesize is 2mb.
if you are interested i can mail them to you or send you a link via wetransfer.
I have some 100 logs of 1 week with 20.000+ pictures per file and a few of 3 weeks with 60.000+ pictures, all without skipped frames and without reboot.
Logged
frustration is a key ingredient in progress
*

Offline c_joerg

  • *****
  • 894
Re: reboot after 21 days worked, but with fault
« Reply #24 on: 03 / July / 2019, 02:00:27 »
Quote from: waterwingz on 02 / July / 2019, 14:58:29
I'd speculate that as the SD card fills up, things start taking longer. And one possibility is the SD card wear leveling algoritm kicking in - we have seen that happen in the past but it typically is more periodic that what seems to be happening here.

I always check my SD cards with ‘h2testw’. The card is completely filled with a test patter. I can’t see that the speed goes down when the card gets full. What’s about the absolute size of the log file?
Logged
M100 100a, M3 101a, 2*G1x (101a,100e), S110 (103a), SX50 (100c), SX230 (101a), S45,
Flickr https://www.flickr.com/photos/136329431@N06/albums
YouTube https://www.youtube.com/channel/UCrTH0tHy9OYTVDzWIvXEMlw/videos?shelf_id=0&view=0&sort=dd
*

Offline Mlapse

  • ***
  • 237
  • A480 A490 S95 M10
Re: reboot after 21 days worked, but with fault
« Reply #25 on: 03 / July / 2019, 02:21:27 »
a week log is about 1700kb, this, more than 3 weeks log, is about 6800kb. (based on 2880 images a day, some 61.000lines)


normally when I start the script the delay before a log entry is made is about 3-5 seconds+exposure time.
(3sec at daytime, 5 at night)
if i look at a 3 weeks log i see no increase in time before the log entries are made.
« Last Edit: 03 / July / 2019, 02:49:29 by Mlapse »
Logged
frustration is a key ingredient in progress
*

Offline waterwingz

  • ******
  • 11980
    • Waterwingz
Re: reboot after 21 days worked, but with fault
« Reply #26 on: 03 / July / 2019, 06:43:32 »


Quote from: c_joerg on 03 / July / 2019, 02:00:27
I always check my SD cards with ‘h2testw’. The card is completely filled with a test patter. I can’t see that the speed goes down when the card gets full. What’s about the absolute size of the log file?
The SD card wear leveling algorithms trigger after a predefined number of writes to the card. The SD card does not need to be full for that to happen.  I've worked around this somewhat in other scripts by buffering log writes in memory and storing larger blocks of data less frequently.
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline Mlapse

  • ***
  • 237
  • A480 A490 S95 M10
Re: reboot after 21 days worked, but with fault
« Reply #27 on: 05 / July / 2019, 16:47:01 »
I've done a bit more testing, but have not narrowed down the problem.
all setting were the same except for run 1) where i used fine instead of superfine for the recorded pics
reboot costs a few frames that i do not mark as missing, since i know they won't be made.

the results are:
256Gb card:
1) 22 day log with rebooot on day21 and after that numbers are missing (image size setting FINE)
2) 22 day log without reboot and no numbers missing (image setting SuperFINE)
64Gb card:
3) 4 day log from UI V4.8x with 2x reboot and no numbers missing. (image setting SuperFINE)
log entry 'fault on switch to shooting mode' at second reboot(day 3), not at first reboot.

So, i'm at a loss here, i can do a new 3 weeks run with reboot on day 21 again, but that would only be to verify attempt 1)

I can insert a script shoot delay to see if that solves the 'fault on switch to shooting mode' but since attempt 3) did not give dropped frames I'm not sure is that would solve anything.
This delay would be because I can see that CF is not ready when the script starts after reboot(it is still busy setting the lens when i see the OSD menu from UI appear on screen)
BTW when running UI in debug mode I have no 'fault on switch to shooting mode' in the log after a reboot.
« Last Edit: 06 / July / 2019, 05:30:33 by Mlapse »
Logged
frustration is a key ingredient in progress
*

Offline waterwingz

  • ******
  • 11980
    • Waterwingz
Re: reboot after 21 days worked, but with fault
« Reply #28 on: 06 / July / 2019, 05:12:27 »
It feels liked the key thing here is a restart when there are a lot of picture files on the card.

Can you try your third scenario of rebooting every day but start the test using an SD card that has 21+ days worth of images already on it?
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline Mlapse

  • ***
  • 237
  • A480 A490 S95 M10
Re: reboot after 21 days worked, but with fault
« Reply #29 on: 06 / July / 2019, 05:23:00 »
sure, i can make that work.

if it is number of pictures related, it might be solved by an even longer delay at start of chdk as discussed here

https://chdk.setepontos.com/index.php?topic=13772.msg140249#msg140249

reyalp made the 10sec. delay version of CHDK to allow for the slow start of a large fat32 formatted card and consequent failure of CHDK to load all modules on start.
however that might not be enough time when the card is full.
« Last Edit: 06 / July / 2019, 07:55:26 by Mlapse »
Logged
frustration is a key ingredient in progress
Pages: 1 2 [3] 4   Go Up
« previous next »
 

Related Topics