Tag: fixed

[FIXED?] Browning BL-22 misfires

Next to some other issues that I have with my Browning BL22 is that it very often misfires. And after a lot of thinking, trial and error, I think I have found the issue.

Remember the post about the little plate that came loose? The misfires are related to this as far as I have been able to figure out. There is a locking block that locks itself via this little plate. (I think i see wear on that block as well). Since it looks like the original plate is hand-made, I think somewhere in the process, someone did a very sloppy job.

OBSERVATION: The bolt is not sitting snug in its place when a cartridge is loaded. This cause the hammer to push through the play first and with the little energy that is remaining, the firing pin is being hit. This is causing the rimfire cartridge not being struck hard enough and thus causes a misfire.

The original plate is 20mm long, 10mm wide and 2mm thick.

I decided to print a few plates in two different lengths, 21 and 22mm. I know the prints are not exact, but this is close enough. 22 mm was way too long and the lever would not close. 21 mm was too long as well, so I decided to sand it down, little by little. If your lever does not FULLY close, do not force it shut and fire a live round! Your bolt may NOT be locked!

Ignore the 20mm one, not sure why I printed that one!

Eventually, with A LOT of assembling and disassembling, trial and error, I found out that the plate should be 20.15mm long. The size may vary per rifle, so keep that in mind.

A rough cut of the new plate

I colored the piece of metal to make the scribe lines better visible, started measuring and scribing. I then used my desktop belt sander to gradually sand it so size. It is not hard to do but do wear gloves as the plate will be hot.

Look how nice the new plate fits snugly into its place. I temporarily glued it in place and went to the range to see how the rifle behaved.

The first 5 shots went without any problem. The next 5 produced 1 misfire and the next 5 were almost all misfires. What the heck happened??

Well, what happened is that I underestimated how much force is put onto the bolt and I had not harden the new plate.

The dent is clearly visible.

Look at that dent! I did not expect that to happen, but this also points out to never underestimate the force that is put on the bolt.

So what to do now? Well, make an exact new one and harden it! The latter will have to be done later. Enjoy the photos and once I have hardened the plate and tested everything, I will post a follow-up.

Loading

unRAID Docker image corrupted solution

Warning: This method worked for me and I used this source for it. Proceed at your own risk. Also I need to note that I do not use Cache in any form.

The problem:
You have rebooted your unRAID server and your docker service is refusing to start. What you may see is the following:

and

Apr 2 02:25:30 Tower emhttpd: shcmd (264): /etc/rc.d/rc.docker start
Apr 2 02:25:30 Tower root: starting dockerd ...
Apr 2 02:25:36 Tower kernel: BTRFS error (device loop2): parent transid verify failed on 23757324288 wanted 2572174 found 2572201
Apr 2 02:25:36 Tower kernel: BTRFS error (device loop2): parent transid verify failed on 23757324288 wanted 2572174 found 2572201
Apr 2 02:25:46 Tower kernel: BTRFS error (device loop2): parent transid verify failed on 23729225728 wanted 2572162 found 2572190
Apr 2 02:25:46 Tower kernel: BTRFS error (device loop2): parent transid verify failed on 23729225728 wanted 2572162 found 2572190
Apr 2 02:25:46 Tower kernel: BTRFS: error (device loop2) in __btrfs_free_extent:6805: errno=-5 IO failure
Apr 2 02:25:46 Tower kernel: BTRFS info (device loop2): forced readonly
Apr 2 02:25:46 Tower kernel: BTRFS: error (device loop2) in btrfs_run_delayed_refs:2935: errno=-5 IO failure
Apr 2 02:25:46 Tower kernel: BTRFS warning (device loop2): btrfs_uuid_scan_kthread failed -30
Apr 2 02:25:51 Tower emhttpd: shcmd (266): umount /var/lib/docker
Apr 2 02:25:51 Tower root: umount: /var/lib/docker: target is busy.

This of course, made me extremely nervous. Luckily this only meant that my docker file got corrupted. It happened most likely while I was moving it while the docker service was still active. Yeah, it happens.

Solution:
It’s fairly simple, but it takes a little bit of time.

  1. Go to Settings -> Docker -> Enable Docker, and set to No, then click the Apply button (this disables Docker support)
  2. Go to the location of your docker image and rename the file to docker.img.bak – The file may be in 
    /mnt/user/system/docker

    I’m asking you to make a backup, because in all cases, safety first. “Why didn’t you have a backup in the first place?”, I hear you say. Yeah yeah, we all make mistakes every so often! D:

  3. Go to Settings -> Docker -> Enable Docker, and set to Yes and this creates a fresh and empty Docker image. The docker service should now be started. You can see this as this on the docker settings page:

    and on the dashboard you should now see an empty docker field.

  4. Now go to the Apps Tab, Previous Apps Section. Then check off all of your previous applications and hit “Install”

I recommend to do it one by one so you can double-check the settings and clean up the unused templates after you’re done. If you want to make a copy of the templates, FTP into your server and go to

/boot/config/plugins/dockerMan

After you have restored your docker apps, you’re done. Check all the things and make a backup 😉

 

 

Loading