-
-
Also on cases, I think this is an interesting direction for them:
https://www.fractal-design.com/products/cases/terra/terra/It is based around the constraint of the GPU size being the main driver of the case, and because CPU cooling is pretty good nowadays and M2 form factor for SSDs is so small, it really means you can get a powerful machine that can do gaming in a very modest form factor that is barely twice the size of the large GPUs on the market.


-
My case is huge, and the motherboard is standard ATX but really the case is just all air now.
I have a large GPU, but still it looks modest in the case.
The fans and heatsink on the CPU are the only thing that is really large... but then, the whole thing is totally silent as the fans barely kick in and all of the fans are huge so don't have to spin at high speed to offer effective cooling.
8 case / system fans, of which 2 are 180mm (huge!), and the other 6 are all 140mm (still big - this includes the 2 on the CPU cooler at this size).
The GPU has it's own 3 fans separate from this, but they only ever spin up if I play a game.
I have them all set to spin only when temp thresholds are met, and because of the case lighting making patterns on the walls I see that they go idle the majority of the day. Even the CPU ones go idle at times.
Cases are just huge air tanks nowadays, and it's nearly all just down to GPU size.
-
-
-
-
Is there any issue with having my router at the end of a 10m stretch of CAT6 from the rest of the network?
No issue at all, I do this.
Cable comes in the wall and hits the router, a 40M length of cat6 goes up through the loft to the other end of the house, the network equipment all lives there... and another 40M length of cat6 carries "internal network" back to near where the cable lives.
-
I had a Unifi network update that suddenly disabled Chromecast across the network.
Now that needs context, it's not actually disabling Chromecast but it's breaking multicast discovery and I think it did this because I have two WiFi networks, one for IoT things called "Things" which is a 2.4Ghz only network, and then one called "Wi-Fi" which is for phones and laptops and this is a 5Ghz only network.
To enable phones to cast to devices on Things the system needs to be aware that the whole of 192.168.x.x is one network, I VLAN Things, and yet to allow the multicast to cross the VLAN.
But... the 5Ghz network had powersaving enabled, meaning the APs would allow devices to reduce the power consumption when idle by moving the network into a low-power keepalive state which extends the battery life (fractionally) of the devices.
Here's where it gets vague... I think Unifi hadn't implemented that correctly and that the power saving mode was updated and was now implemented correctly. The power saving mode disables the ability for the multicast to cross VLANs, and so... one update and a loss of Chromecast.
I disabled this single feature, the power saving, and full Chromecast discovery and casting works again... weirdest breakage I've had for a while.
-
-
It turns out expanding BTRFS volumes is slow.
I didn't have all the drives at once, which is preferred as I like buying some different batches. So I started with 5 * 16TB HDD, and then added another... that took 3 days. Now it's working I've just added another, which will take another 2-3 days to expand the volume.
I do realise it's doing a lot of work, effectively redistributing all files and their parity across all of the new space in an even way to guarantee durability... but still, it takes a long time.
Top tip for anyone setting up BTRFS in future, wait until you have all the drives before you create the volume.
-
That is interesting, in modem mode the NAT table is held by your own router and not there's.
But, it's still possible to do connection tracking and have a conntrack table that would provide a high confidence signal as to the number of devices on the network.
Virgin famously use a lot of traffic shaping and I would not be surprised if they have flow tracking stats that provide this info from their side and not from the hub — actually I'd say tha this is more likely :)
-
I don't think I had considered how good a video camera the Sony's are. I have a Sony a7IV and paired with a F2.8 24-70mm GM2 went camping and hiking in the Peak District and over Kinder Scout and the videos are soooo much more vivid and clear, more capable of fully capturing what it felt like being there, the wind, the movement, the sound (I have an external mic array)... and it's just incredible how much more they take you there, to the moment.
I first tried the video setting a few weeks back in St Ives on a hot day, and video was so much better at picking up the light being refracted by heat.
Can't really share them though, the videos... as I took them for me, they're not something I want to put on YouTube, and they vary from 300MB for a few seconds all the way up to several GB for a 30-60s capture.
Likely to invest in some ridiculously large and fast storage cards now, could well see me sitting in a forest and just shooting 10 minutes of a scene to fully capture the background noise and movement of it all.
-
-
-
This is more like it, and you're wrong too... https://www.renehersecycles.com/shop/components/bottom-brackets/skf-bottom-bracket-iso-square-taper/ this is the way, everyone else is obviously wrong.
-
-
I mean, I woke up to a long DM from Fabzzz asking "if this kind of behaviour is telerated here towards others is definitely not a spot for me" (behaviour being all of the comments in this thread in the last few days).
For my sins I've read the last few days and OK... strange irrelevant arguments happen on the internet, and people definitely go down some oddly chosen rabbit holes when choosing to have them.
I think we can all say that Fabzzz should have slept better and not been posting all times of day and night. Beyond that, who knows... seems such a storm in a teacup.
-
-
-
-
-
-
weird situation
More weird that it doesn't happen more often TBH.
ECC RAM is not standard, resilient file systems are not standard, CPU errata lists are surprisingly long.
Almost everyone has corrupt files, but that one was in the file header that allows Windows to understand what the file is. Only needs a few bits to be incorrect in the wrong place and it breaks. Mostly though, mostly the bits that are corrupt fall in parts of the file system and files that no-one cares about.
-
New NAS is up and running.
I've only received 5 x 16TB drives so far, and the 2 x 1TB SSDs for the SSD cache, and the 2 x 32GB RAM modules... but that's enough to be up and running.
I've configured it for SHR2 with BTRFS and so far copied over about 5TB of data.
This thing is fast... and it turns out that's because the entirety of the BTRFS metadata can be stored in the SSD cache, so there's zero HDD activity for doing a directory listing or navigating the folder. Given some of my directories have low tens of thousands of things in them and they're now near-instant over the network, the whole experience is incredible.
Still waiting on another 3 x 16TB HDD though, I only have 46TB usable at the moment and will have 96TB usable once I have the other drives in place.
Can we just agree... no? Oh