WEBVTT

00:00:01.280 --> 00:00:08.480
Snatch and smash. It's the viral trend that's breaking all the rules and maybe

00:00:06.080 --> 00:00:12.080
your phone. This clip with over 6 million views on Tik Tok shows an

00:00:10.240 --> 00:00:16.080
elderly man sneaking up on an unsuspecting Zoomer snatching her phone

00:00:14.400 --> 00:00:19.520
and smashing it right in front of her. Hey Billy, did you see this on the TV

00:00:18.640 --> 00:00:24.560
news? It's fake news, Dad. Look, it's the same guy in a different

00:00:22.320 --> 00:00:27.760
hat. I reverse AI searched him and his LinkedIn employer just says he has

00:00:26.000 --> 00:00:31.679
contracts at Google and Apple. It's just a stunt to promote iCloud and Google 1.

00:00:29.920 --> 00:00:35.680
But you have the iDrive, right? No, Dad. My generation can't afford

00:00:34.320 --> 00:00:39.440
BMWs. Unsettling, if true. [music]

00:00:37.680 --> 00:00:45.040
Now, it's time for today's Tech Tip Minute, where we're going to be showing you an affordable way to safeguard your

00:00:42.559 --> 00:00:49.680
data. Watch this. I press this button and instantly, my photos are syncing

00:00:47.360 --> 00:00:54.640
over the internet. But instead of to an expensive cloud storage provider, I'm

00:00:51.760 --> 00:01:01.199
backing up to the NAS board right behind me. Wow, look at it go. Of course,

00:00:58.079 --> 00:01:03.920
networkattached storage or NAS devices

00:01:01.199 --> 00:01:10.799
are nothing new. What's special here is the value. The friendly elect CM3588

00:01:08.000 --> 00:01:16.320
NAS kit costs about what you'd spend for 2 TB of cloud storage per year, and its

00:01:13.920 --> 00:01:22.799
ARMbased processor from Rock Chip crushes the CPU in this $700 bigname

00:01:19.840 --> 00:01:27.520
NAS. As a bonus, it's so efficient, it can be powered by just a 2 amp 12volt

00:01:25.200 --> 00:01:30.640
input. There is one more thing you'll need to know before you can stop paying

00:01:29.119 --> 00:01:35.400
that monthly subscription, and we're going to tell you all about it after the

00:01:32.400 --> 00:01:35.400
break.

00:01:41.040 --> 00:01:49.439
Despite being able to purchase the CM3588 standalone, it's really intended

00:01:46.079 --> 00:01:51.040
to slot into their bundle $35 .naz NAS

00:01:49.439 --> 00:01:57.680
kit that comes equipped with 2 and 1/2 gig Ethernet, three HDMI ports, one in,

00:01:54.240 --> 00:02:00.479
two out, USB 3, USBC, a micro SD slot,

00:01:57.680 --> 00:02:08.319
and the star of the show, four full-sized M.2 PCIe Gen 3 slots. How is

00:02:04.960 --> 00:02:09.920
this only $35? I mean, I guess if you

00:02:08.319 --> 00:02:14.720
take away the expensive bits like the SOC and the RAM, a PCB, and some

00:02:12.080 --> 00:02:18.640
connectors. It even has GPIO. Still doesn't cost very much. All we got to do

00:02:16.640 --> 00:02:23.680
is install a cute little heat sink, click it into place, and we're done. But

00:02:21.360 --> 00:02:30.080
this ease of use is only part of the story. The other part is modularity. For

00:02:26.879 --> 00:02:32.640
now, Friendly only has this one board.

00:02:30.080 --> 00:02:37.200
But in the future, who knows? A SATA version for hard drives or maybe one

00:02:34.800 --> 00:02:42.160
with a PCI Express slot. That would be sick. And what's cool is in the future,

00:02:40.400 --> 00:02:45.440
if your daughter board still meets your needs, but you want more performance,

00:02:43.840 --> 00:02:50.000
you could potentially upgrade the brain of your tiny Naz without having to scrap

00:02:47.760 --> 00:02:53.680
the whole thing. I mean, no promises. The first iteration kind of has to

00:02:51.760 --> 00:02:58.080
succeed for there to be a follow-up, but as it stands right now, I kind of love

00:02:56.160 --> 00:03:03.840
it. This version of the compute board comes with 4 gigs of DDR4X memory and no

00:03:01.440 --> 00:03:09.280
onboard storage. So, the expectation is you either use the SD slot on the NAS

00:03:06.239 --> 00:03:11.360
kit or you upgrade to the 8 or 16 gig

00:03:09.280 --> 00:03:16.800
RAM versions, which include 64 gigs of eMMC storage. We ended up with the

00:03:13.680 --> 00:03:19.440
ladder, which brought our price to $160.

00:03:16.800 --> 00:03:23.920
It's not cheap, but it's a really solid value when you consider that that's a

00:03:21.040 --> 00:03:29.440
onetime cost. Kind of like our LT screwdriver. Yeah, one driver, many

00:03:27.040 --> 00:03:32.879
different bits. Let's get these drives installed. But while we're doing that,

00:03:31.120 --> 00:03:39.280
let's talk about the options that we have. Each of these slots is a PCIe Gen

00:03:36.319 --> 00:03:44.080
3x1 connection. So that does limit our bandwidth a little bit, but it also

00:03:41.120 --> 00:03:48.239
opens up some very interesting options. For example, with inexpensive adapters,

00:03:46.239 --> 00:03:54.319
we could turn each of these into as many as five SATA ports, giving us support

00:03:50.480 --> 00:03:56.959
for 20 conventional hard drives. We were

00:03:54.319 --> 00:04:02.159
more interested though in a tiny power efficient solidstate NAS. Now, with only

00:04:00.400 --> 00:04:06.480
one lane per port, we're not going to be setting any speed records here. But

00:04:04.239 --> 00:04:10.560
realistically, our 2 and 1/2 gig network interface is going to limit us long

00:04:08.480 --> 00:04:13.920
before those PCIe lanes will, which realistically gave us a lot of

00:04:12.239 --> 00:04:18.239
flexibility when it came to choosing our SSDs. We obviously don't want anything

00:04:16.400 --> 00:04:22.079
unreliable, so we're not going to go with the cheapest thing, but we don't

00:04:19.840 --> 00:04:28.320
need to spend a fortune either. So, we picked these 4 TB MP34 drives from

00:04:24.800 --> 00:04:30.320
Tegroup for $165 each. They're only Gen

00:04:28.320 --> 00:04:34.400
3, but they have a 5-year warranty, and they even come with a DRAM cache, though

00:04:32.720 --> 00:04:38.320
that shouldn't really have an impact on the relatively sequential video editing

00:04:36.720 --> 00:04:43.120
work that we would do off of this thing at a trade show or something. And for

00:04:40.479 --> 00:04:47.759
that matter, most NAS duties are pretty similar, whether you're using it for PC

00:04:45.120 --> 00:04:51.440
backup, photo and movie backup, or even running a video streaming server with

00:04:49.280 --> 00:04:55.360
Plex or Jellyfin. And besides, because you're configuring your own, you can

00:04:53.280 --> 00:05:00.000
choose lower capacity drives or you can populate just two slots, run them in a

00:04:57.840 --> 00:05:03.840
mirror for redundancy. Then six months later, when you get a nice paycheck, you

00:05:01.759 --> 00:05:08.320
can add one or two more. So, some of you are probably wondering then, why do you

00:05:05.919 --> 00:05:13.759
need a NAS instead of just using external hard drives anyway? Well, for

00:05:11.120 --> 00:05:19.440
starters, these things suck. They're a single point of failure, and they're

00:05:15.520 --> 00:05:21.680
super easy to lose. By comparison, a NAS

00:05:19.440 --> 00:05:25.759
can be shared with anyone else on your network, which leads to point two.

00:05:24.160 --> 00:05:33.039
Having all of your data on your personal machine is something that I have advocated against for years. Your daily

00:05:30.320 --> 00:05:38.400
driver is the most likely to be infected by malware or to suffer a malfunction,

00:05:35.600 --> 00:05:43.520
putting any data that's on it at risk. With that said, a single copy on a NAS

00:05:41.680 --> 00:05:48.080
isn't best practice either, and you should always follow the 321 rule. three

00:05:46.160 --> 00:05:52.800
copies of your data on two types of media with one of them being offsite.

00:05:50.479 --> 00:05:57.360
Now, we usually turn to trunaz for these types of projects, but with this board

00:05:55.120 --> 00:06:02.800
being ARMbased, we were forced to look for another option and eventually we

00:05:59.360 --> 00:06:05.039
settled on OMV or Open Media Vault.

00:06:02.800 --> 00:06:09.520
Conveniently, Friendly website includes a link to a Google Drive that has all

00:06:06.960 --> 00:06:13.280
the install files and instructions for the different methods of installation.

00:06:11.600 --> 00:06:18.160
We're going to be going from an SD card to our eMMC storage. The process took

00:06:16.000 --> 00:06:23.440
about 25 minutes and at the end gave us an IP that we could use to access the

00:06:20.319 --> 00:06:25.440
guey for open media vault. We chose RAID

00:06:23.440 --> 00:06:32.639
5 for a balance of protection and capacity and after compiling and syncing

00:06:28.240 --> 00:06:34.720
we were left with dang almost 11.2 TB of

00:06:32.639 --> 00:06:39.120
capacity. Now we want to connect it to our Windows-based computers. So we

00:06:36.720 --> 00:06:43.280
enable SMB the protocol that Windows uses for network file sharing and then

00:06:41.039 --> 00:06:49.360
create a shared drive. Let's see how we did. Different media file copying from

00:06:45.840 --> 00:06:51.360
our desktop to our tiny nez. Wow.

00:06:49.360 --> 00:06:54.720
Completely saturating our two and a half gig interface. That's awesome.

00:06:52.880 --> 00:06:56.319
I wonder how much CPU usage is happening. Yeah, you can actually check

00:06:56.000 --> 00:07:02.880
that. We could check that. Yeah, pretty substantial amount.

00:07:01.520 --> 00:07:07.120
Not very powerful. And transfer back. Wow. There you go.

00:07:05.199 --> 00:07:10.720
It's almost like that's a lot of interface for a 2 and 1/2 gig

00:07:08.800 --> 00:07:17.120
connection. Did I mention it's completely flipping silent?

00:07:14.080 --> 00:07:18.560
Barely even hot to the touch.

00:07:17.120 --> 00:07:21.840
What am I even listening for? There's no fan on it. Just whatever. It doesn't matter.

00:07:20.400 --> 00:07:23.840
Do you know where there are fans though? Flow plane.

00:07:23.440 --> 00:07:29.039
Oh, go subscribe to Flow Plane. This is all fine and good, but it

00:07:27.120 --> 00:07:34.319
doesn't answer the question of how do we protect ourselves against the very real

00:07:30.800 --> 00:07:36.800
threat of snatch and smash? Well, under

00:07:34.319 --> 00:07:41.680
the plug-in section in OMV, you can grab Photo Prism, an AI powered photo library

00:07:39.680 --> 00:07:47.840
that we can use a separate application to sync to. In our case, we used Photo

00:07:44.560 --> 00:07:50.319
Sync. So, for just over $5, we're able

00:07:47.840 --> 00:07:54.400
to sync our photos with almost any storage solution you can think of,

00:07:52.000 --> 00:07:59.280
including Photo Prism. And what's really cool is the sync can work both ways. So,

00:07:57.440 --> 00:08:04.240
if your phone ever dies and you need to replace it, you just resign into

00:08:01.680 --> 00:08:09.440
Photosync and you can sync back from your NAS to whatever new phone you get.

00:08:07.039 --> 00:08:14.960
No monthly subscription, just a one-time payment of this many dollars for the

00:08:11.919 --> 00:08:17.280
app. Compared to more common setups, x86

00:08:14.960 --> 00:08:20.960
processors on Trunaz or Unread, for example, we did have times when we

00:08:19.199 --> 00:08:24.720
needed a little extra tinkering and knowhow to get things working. But after

00:08:23.199 --> 00:08:32.000
Jake spent a couple of hours getting Plex up and running in a Docker container, this little guy handled

00:08:28.879 --> 00:08:34.880
streaming just great to two concurrent

00:08:32.000 --> 00:08:39.039
clients. At least at 1080p it did. Once we bumped it up to 4K, that was a

00:08:37.120 --> 00:08:43.120
different story. But hey, if you're not super satisfied with the playback off of

00:08:40.880 --> 00:08:47.519
this device, that's okay. You can run the Plex server on a more powerful

00:08:45.120 --> 00:08:51.600
machine in your house, say your gaming desktop, and then just use this as a

00:08:49.839 --> 00:08:56.080
beefcaked out little external hard drive. All you need is a network switch.

00:08:54.240 --> 00:08:59.760
I am curious to see how it'll handle video editing, though. As it turns out,

00:08:58.080 --> 00:09:05.200
the entire editing department is on lunch right now. So, [snorts]

00:09:02.480 --> 00:09:09.519
I guess I get to do this. [laughter] I am scrubbing. I am starting to thing.

00:09:08.000 --> 00:09:13.279
We've got our Apple Vision Pro video here. This is the Facebook version of

00:09:11.120 --> 00:09:17.120
though, hence the super obnoxious aspect ratio. I can't even tell what the heck's

00:09:14.720 --> 00:09:22.399
going on. People watch videos like this. This is terrible. But, you know what?

00:09:18.720 --> 00:09:24.160
Isn't the NAS? Why don't we try 1/2

00:09:22.399 --> 00:09:28.480
resolution? It's not the fastest thing ever, but realistically, this is

00:09:26.160 --> 00:09:33.200
reasonably heavy 4K footage. This was such a great moment in this video, and

00:09:31.440 --> 00:09:38.880
you can't really appreciate it at all because stupid aspect ratio. Yeah,

00:09:36.320 --> 00:09:42.880
Facebook. So, it's pretty great. And if Open Media Vault isn't your thing, El's

00:09:40.959 --> 00:09:47.839
list of supported OSS includes versions of Debian, Friendly Wr, Ubuntu, and even

00:09:46.000 --> 00:09:53.040
Android. So, what are you waiting for? It's a line of sized NASD that can scale

00:09:49.839 --> 00:09:55.440
up to 32 TB of storage with a topsp spec

00:09:53.040 --> 00:09:59.920
price of $160 if you're okay with doing a bit of work.

00:09:57.600 --> 00:10:03.519
And the value is especially apparent when you look at the cost of the larger

00:10:01.839 --> 00:10:09.200
storage plans from the major cloud providers. Google, for instance, wants

00:10:06.000 --> 00:10:11.040
$600 a year for their 10 TBTE cloud

00:10:09.200 --> 00:10:16.320
storage plan. That means it would take less than a year and a half to pay off

00:10:13.200 --> 00:10:18.959
this exact NAS in this configuration

00:10:16.320 --> 00:10:24.800
with all the SSDs. And that's with us going full LTT and making a solid state

00:10:21.519 --> 00:10:26.640
NAZ. So, what can I say other than I

00:10:24.800 --> 00:10:30.560
give a strong recommendation to this small boy, just like I give a strong

00:10:28.480 --> 00:10:35.200
recommendation to this small boy. If you guys enjoyed this video, go check out

00:10:32.399 --> 00:10:39.839
the 90 TBTE NVMe server that I ended up building and not taking home to my

00:10:37.920 --> 00:10:43.839
house. It's kind of the opposite of this, but it's still a fun educational