Recent comments on posts in the blog:
Thanks for the great information.
I've been a Crashplan customer for years for my Windows laptop.
I'm just transitioning to POP OS on the start of my journey away from Big Tech and setting up a backup service was a priority.
Your article suggests that I should be able to continue using Crashplan after all
e2fsck -f /dev/sda1 tune2fs -I 256 /dev/sda1
That'll work just fine on ext2 and ext3 but fails on ext4 filesystem with the flex_bg feature enabled:
# tune2fs -I 256 /dev/sda1
Changing the inode size not supported for filesystems with the flex_bg
feature enabled.
Also, that flag cannot be cleared:
# tune2fs -O ^flex_bg /dev/sda1
Clearing the flex_bg flag would cause the the filesystem to be
inconsistent.
So, unless I'm missing something, there's no two ways about it and, as per the post, copy->mkfs->copy is the only way to fix it.
BTW, the same issue will affect XFS and, potentially, other filesystems.
Thank you for this post. It confirmed me my suspicion and I have found it while making sure how pigtails should be connected.
I was recently upgrading old Omnia to NAS box. Since then I had issues with 2.4 GHz WiFi. Of course, issue was in switched pigtails on one of the antennas. Layout of WiFi cards in slots was the same as on your photo, however, my Omnia has different duplexers. On your photo, 5GHz is connected to the left port, while mine has 5GHz on the right port.
If someone finds this page, make sure you check what duplexers you have in your unit and don't blindly trust photo of other unit, as some components may differ.
Hey François, many thanks for your effort to share this tutorial. Had the same problems as you described. Woks also for RaspberryPi 4 with Raspbian GNU/Linux 10 (buster). Best regards, Uwe
Notice that Zoom WebRTC is not real WebRTC, they are using data channels to integrate with proprietary WebAssembly client code:
https://bloggeek.me/when-will-zoom-use-webrtc/
Real WebRTC does not require WebAssembly or data channels.
Firefox only supports WebAssembly on x86 / amd64
That is why it is not working on Pi 4
Same problem on POWER9 and arm64 workstations.