WEBVTT

00:00:04.080 --> 00:00:13.519
wait what okay that was a reenactment but a

00:00:10.599 --> 00:00:18.560
few weeks ago my computer did die just like that right in the middle of a

00:00:15.160 --> 00:00:21.000
gaming session turns out my boot SSD

00:00:18.560 --> 00:00:26.119
catastrophically failed giving me an excuse to rebuild my gaming rig and my

00:00:23.480 --> 00:00:31.920
kids machines and every other system in my house with no SSD no hard drive no

00:00:29.199 --> 00:00:37.719
storage at all yet look at this I'm gaming I've got Windows I've even got a

00:00:34.879 --> 00:00:44.800
ton of games installed how is this possible I mean I know you can download

00:00:40.559 --> 00:00:46.760
RAM but downloading storage well kind of

00:00:44.800 --> 00:00:51.239
the storage still needs to be somewhere and luckily for you kokia who sponsored

00:00:48.800 --> 00:00:56.920
this video provided some of their cd8 Enterprise ssds but what he's saying is

00:00:54.120 --> 00:01:00.719
true none of them are in the gaming PCs instead it's all in here that is

00:00:58.600 --> 00:01:05.520
freaking amazing did you just pull one out so we got redundancy and everything

00:01:02.879 --> 00:01:10.920
yeah I mean it's cool but there are some disadvantages like uh you kind of made

00:01:08.000 --> 00:01:14.240
every computer in your house a bit we'll get to that later roll the

00:01:22.000 --> 00:01:28.240
thing I am really excited about this because in spite of the fact that

00:01:26.400 --> 00:01:32.000
Network booting has existed for longer than Jake here

00:01:30.479 --> 00:01:37.000
it's not something we've ever really played around with much and certainly

00:01:34.240 --> 00:01:41.880
never for a home gaming setup so how does it wake well the current way to

00:01:39.640 --> 00:01:46.920
network boot from something like a nass network attached storage is ice scuzzy

00:01:43.840 --> 00:01:49.240
there is also like newer stuff like nbme

00:01:46.920 --> 00:01:53.320
over fabric but as far as I know it doesn't really exist at least in Windows

00:01:51.200 --> 00:01:59.039
land yet and certainly it's not within the scope of this project but as silly

00:01:55.159 --> 00:02:01.079
as it sounds to boot from a NZ is it I

00:01:59.039 --> 00:02:06.320
mean you can Video Edit on files from your Nas we do that all the time you can

00:02:03.680 --> 00:02:12.440
game using files on a Nas we do that all the time so why not Windows from your NZ

00:02:10.039 --> 00:02:16.920
it comes with some key advantages for one thing it centralizes your storage

00:02:14.720 --> 00:02:20.760
which means redundancy can be more economical to safeguard against the

00:02:18.519 --> 00:02:25.400
drive failure instead of having to put at least two drives in every one of your

00:02:22.879 --> 00:02:30.879
systems you can just put I don't know six drives in here plus one extra for

00:02:28.480 --> 00:02:35.640
redundancy and it can make for easy management of backups and lightning fast

00:02:33.560 --> 00:02:39.959
system restores which I'm sure is great for kids PCS cuz I bet they mess stuff

00:02:37.760 --> 00:02:44.840
up all the time mine are actually pretty good so far but I'm sure that's coming

00:02:43.319 --> 00:02:50.440
my dad would be happy just cuz he could get rid of MSN Messenger faster I wasn't

00:02:47.319 --> 00:02:52.519
allowed I did it anyways what I am

00:02:50.440 --> 00:02:57.120
allowed to use is D duplication or compression with ZFS as the back end

00:02:54.800 --> 00:03:00.760
that's super cool cuz it gives us even more efficiency out of the storage that

00:02:59.120 --> 00:03:05.000
we have but it's it's not all sunshine and rainbows like what about the lack of

00:03:03.159 --> 00:03:12.480
system okay we're going to talk about that later first let's build a NZ okay

00:03:09.560 --> 00:03:17.720
why don't you tell us about this weird platform you decided to use for this

00:03:14.519 --> 00:03:21.080
project I hate this computer this is the

00:03:17.720 --> 00:03:22.920
worst server I have ever played with at

00:03:21.080 --> 00:03:27.440
least in like the Last 5 Years In fairness to Intel it's a reference

00:03:25.319 --> 00:03:31.560
platform software development platform it is never meant to go to an end user

00:03:29.799 --> 00:03:37.599
but it has been a little Annoying to get working the good news is it's a super

00:03:34.000 --> 00:03:40.720
cool system it's dual 144 core

00:03:37.599 --> 00:03:42.720
processors which is hilarious Overkill

00:03:40.720 --> 00:03:47.239
uh it's not even great for this setup actually cuz icezy not super

00:03:44.680 --> 00:03:51.080
multi-threaded um but he's been looking for an excuse to Tool around with it and

00:03:49.080 --> 00:03:55.959
now we have it but aside from the CPUs we've loaded this thing up with an

00:03:52.239 --> 00:03:58.920
NVIDIA melano connect X6 dual Port 100

00:03:55.959 --> 00:04:04.360
GB per second Nick we don't actually need the fastest network cards in the

00:04:01.439 --> 00:04:08.560
client PCS but what we have to consider is that because this one machine is

00:04:06.439 --> 00:04:14.159
going to serve all of them it needs to be as fast as all of their network cards

00:04:11.799 --> 00:04:17.359
combined that is assuming that they're all trying to hit it at the same time I

00:04:16.000 --> 00:04:23.960
mean you wouldn't want your computers to be slow right no no I really wouldn't

00:04:21.400 --> 00:04:29.440
and with the speed of these cd8 Gen 4 drives that kokia provided for this

00:04:25.720 --> 00:04:31.840
little thought experiment we can use as

00:04:29.440 --> 00:04:36.520
fast fast a Nick as we can possibly get our hands on and never have to worry

00:04:34.080 --> 00:04:40.440
about our drives being the bottleneck now what are we using for networking

00:04:38.320 --> 00:04:46.400
because I don't have a 100 Gig switch Yeah and ubiquity doesn't make one yet

00:04:42.199 --> 00:04:51.680
so instead hey our buddies from microt

00:04:46.400 --> 00:04:53.919
this is the CRS 5181 16xs 2xq not only

00:04:51.680 --> 00:05:00.160
does it have two 100 Gig ports that's the the 2xq but it has 16 25 gig ports

00:04:58.160 --> 00:05:03.759
which is perfect we plug our server in here and then we can plug in all the

00:05:01.840 --> 00:05:07.759
other things Downstream to the 25 gig ports uh at least we could if we had 25

00:05:06.120 --> 00:05:12.320
gig networking in any of our systems well we're going to the funny thing is

00:05:10.000 --> 00:05:17.120
as silly as it feels to use these cd8 drives for gaming this kind of an

00:05:14.639 --> 00:05:20.880
application is not that far off of what drives like this are designed for

00:05:19.039 --> 00:05:24.319
they've got die failure recovery as well as power loss protection and parody

00:05:22.600 --> 00:05:30.039
protection to make them extraordinarily reliable they're available in capacities

00:05:27.080 --> 00:05:34.880
much higher than the 3.84 tabt we're deploying here so if you've got

00:05:32.639 --> 00:05:39.840
simulation work or you're storing gigantic high performance databases

00:05:37.039 --> 00:05:44.919
something like this would be perfect and we're going to put games on it and

00:05:41.840 --> 00:05:47.280
Windows so we've allocated about 10 tab

00:05:44.919 --> 00:05:51.400
of storage for a shared game drive and about one tab for the boot drives for

00:05:49.400 --> 00:05:54.479
each of our systems we've got Network we got storage that's all we really need

00:05:53.039 --> 00:05:58.639
you're going to take us fine I got I got the whole thing

00:05:57.000 --> 00:06:02.039
don't drop it all right oh my God what the oh there wasn't a drive in that TR

00:06:00.160 --> 00:06:05.560
we're good what the hell while Jake gets things hooked up let's talk about the

00:06:03.560 --> 00:06:10.759
long-term plan because obviously I'm not going to be keeping a 288 core Intel

00:06:08.720 --> 00:06:16.919
reference server in my house to boot my computers what I actually want to do is

00:06:13.560 --> 00:06:20.440
take my two loud nazes and consolidate

00:06:16.919 --> 00:06:22.960
them into one quiet one so take that 45

00:06:20.440 --> 00:06:28.599
drives chassis rip out the hard drive mounts put in NVMe mounts and then run

00:06:26.160 --> 00:06:33.319
them all off of that Nas software that I invested in whether or not we boot the

00:06:31.000 --> 00:06:36.400
computers from them that kind of depends on how this proof of concept goes why

00:06:35.199 --> 00:06:41.039
are you taking the drives out we just put them in I told you this server is so

00:06:38.880 --> 00:06:46.199
great right it doesn't boot with ssds in it what so you have to like let it boot

00:06:44.160 --> 00:06:53.720
and then you hot plug the ssds back tried so many things the Intel rep was

00:06:50.039 --> 00:06:56.039
like it's my last day I'm not even

00:06:53.720 --> 00:07:00.919
kidding that is legitimately what happened good luck at wherever you go

00:06:58.479 --> 00:07:03.639
but he's like I took the voluntary payout I'm

00:07:04.759 --> 00:07:10.560
leaving all right let's go look at the software stack now my assumption was we

00:07:09.039 --> 00:07:16.160
were just going to use trass for this because we love tress yeah tress is

00:07:13.280 --> 00:07:20.039
great but we didn't yeah I used it for ice Coy like a couple months ago and it

00:07:18.360 --> 00:07:23.919
was pretty slow there's also this thing called starwind vsan which there's a

00:07:22.479 --> 00:07:28.280
free version that they let you use Forever on even multiple machines you

00:07:25.879 --> 00:07:33.759
can have high availability for free and it's like purpose built for ice cuzy so

00:07:30.879 --> 00:07:38.160
it's a lot easier to just set up and use for this exact workload so why not right

00:07:36.599 --> 00:07:41.800
there is a bare metal install but I didn't notice until I had already set up

00:07:39.599 --> 00:07:45.639
the like proxmox image version so that's what we're using instead it should still

00:07:43.520 --> 00:07:49.879
be performant I just took our Network C and our six ssds and just PCIe pass

00:07:48.319 --> 00:07:53.680
through them right so if there's any performance hit for virtualization it

00:07:51.639 --> 00:08:00.000
should be pretty negligible this system has 512 gigs right but you have to like

00:07:57.440 --> 00:08:04.879
load it so I just picked 200 56 cuz that's faster and I selected 64 cores I

00:08:02.720 --> 00:08:10.599
mean this type of server is really meant for like a web host or like

00:08:07.879 --> 00:08:15.120
virtualization web hosts yeah like something that just parallelizes like

00:08:12.879 --> 00:08:21.240
crazy yeah oh we can see we have our kokia ssds look at that all six of them

00:08:18.240 --> 00:08:24.199
wow and then I went ahead and created a

00:08:21.240 --> 00:08:31.280
ZFS pool it does give you the option to like just make a raid pool um it seems

00:08:28.000 --> 00:08:34.399
to be slower for some reason the ZFS is

00:08:31.280 --> 00:08:35.839
cool because it has RAM caching um and

00:08:34.399 --> 00:08:41.120
that'll it'll just put your files in memory and memory is of course super

00:08:38.360 --> 00:08:45.720
fast so with raid Z1 that means that one of our drives is not contributing to our

00:08:43.959 --> 00:08:49.880
overall storage but it also means that we can lose any one of our drives just

00:08:48.560 --> 00:08:54.000
like I did when I was in the middle of my game and none of our systems should

00:08:52.680 --> 00:08:58.040
go down we're going to show The Real World results of that live test where

00:08:55.959 --> 00:09:01.360
Jake ripped a drive out in the intro a little bit later after that you make a

00:09:00.079 --> 00:09:06.480
volume which is kind of just like a folder so we've got one for our game drive here this really reminds me of the

00:09:04.640 --> 00:09:10.760
trass interface a lot it's like the trass interface but like less crappy you

00:09:08.600 --> 00:09:15.880
notice how like responsive it is yeah and then for ice cuzy we have to make a

00:09:13.480 --> 00:09:19.880
Lun which is kind of like a virtual disc now some of it is just needlessly

00:09:18.200 --> 00:09:24.279
complicated now starwind does a good job of making it less complicated let's

00:09:21.680 --> 00:09:27.320
create one ice guy Standalone because we're not high availability it's just

00:09:25.519 --> 00:09:34.279
one system we'll make it in our Linus smells thing we'll call it Linus re

00:09:30.440 --> 00:09:37.040
smells and 100 gigs and done that's all

00:09:34.279 --> 00:09:42.959
you have to do right so now I have a 100 Gig drive and it lives on my network but

00:09:40.160 --> 00:09:47.040
how do you use it that's the annoying part this is the the overly complicated

00:09:45.160 --> 00:09:52.000
BS I'm talking I'm sure there's a reason for it but this is like the address of

00:09:49.240 --> 00:09:55.040
the storage got it uh I don't know why the date needs to be in there it's not

00:09:53.640 --> 00:09:59.000
supposed to be the current date or the date of creation it's like the date you

00:09:56.839 --> 00:10:02.560
registered your domain as far as I can tell entirely arbitrary you can set it

00:10:00.720 --> 00:10:06.640
to whatever you want one way or another like any other network resource it needs

00:10:04.440 --> 00:10:12.920
an address but what is the difference between an ice scuzzy storage drive and

00:10:09.720 --> 00:10:15.200
an SMB shared folder well one is block

00:10:12.920 --> 00:10:19.880
storage and one is file storage and if you don't care what that means it's

00:10:17.160 --> 00:10:23.360
basically imagine ice cuzy like an SSD it's it's the whole drive it's meant to

00:10:21.320 --> 00:10:27.920
plug right into a computer not be shared and you can imagine SMB as like here's a

00:10:25.800 --> 00:10:32.480
folder you know multiple people can use one folder and they won't conflict with

00:10:30.399 --> 00:10:36.279
each other if they both try to read a file or write to a folder yeah because

00:10:34.839 --> 00:10:40.480
it's designed to handle that luckily starwin can handle both you see SMB

00:10:38.560 --> 00:10:43.519
share that'll be for our games since most games you install them to an SMB

00:10:42.240 --> 00:10:48.240
share you can play them on multiple computers and it just works and then they're going to use their local my

00:10:46.200 --> 00:10:53.040
documents or games folder for any save data or whatever else hopefully some

00:10:50.880 --> 00:10:56.440
games not so good yeah so this is going to be a little Hit or Miss but we can at

00:10:54.639 --> 00:11:00.920
least try it yeah and worst case you can install a game locally question for you

00:10:59.320 --> 00:11:04.959
for this test did you swap out my network card for the fastest one that

00:11:02.560 --> 00:11:10.680
we've got no I mean the one you have right now an X540 T2 dual 10 gig one

00:11:07.720 --> 00:11:16.839
should in theory work just fine for this yeah I mean if you think about it 10 gig

00:11:12.920 --> 00:11:20.360
that's way faster than SATA 3

00:11:16.839 --> 00:11:23.600
yeah yeah but we could go faster let's

00:11:20.360 --> 00:11:25.639
go faster F I mean how fast do you want

00:11:23.600 --> 00:11:29.920
your computer to be I don't know I just want to see what this is capable of I

00:11:27.560 --> 00:11:36.040
think we should do the 100 Gig Nick there is a PCIe slot limitation your

00:11:33.160 --> 00:11:39.760
system only has a buy4 connection that's the thing about high-end desktop

00:11:37.560 --> 00:11:44.000
platforms being effectively dead these days is if you want to get into kind of

00:11:42.200 --> 00:11:48.200
weird home lab stuff like this on a consumer board you're not going to have

00:11:45.920 --> 00:11:54.240
enough PCIe Lanes but this one's cool it still has a second gen 4x4 link to the

00:11:51.560 --> 00:12:00.959
CPU not through the chipset um but this is a gen 3 card so you're going to get

00:11:57.680 --> 00:12:03.720
uh 4 GB a second Max Boom Card

00:12:00.959 --> 00:12:09.680
installation let's go yeah dude this is a buy one slot

00:12:07.320 --> 00:12:13.040
though no it's by four no it's byy one oh well where's the what board is this

00:12:11.480 --> 00:12:17.519
well I got my Thunderbolt card in the by4 why because that it needs it don't

00:12:15.639 --> 00:12:22.079
you have a iicon thing anyways yeah but I also have a Thunderbolt do uh that

00:12:20.120 --> 00:12:26.480
like 1 GB a second is all you're going to get out of

00:12:23.320 --> 00:12:28.079
that oh 10 gig then at that point I

00:12:26.480 --> 00:12:33.000
might as well just leave the 10 gig card in there well we could use this one this

00:12:30.000 --> 00:12:35.519
is a connectx 6 card it's only 25 gig

00:12:33.000 --> 00:12:41.199
ports but it's Gen 4 okay so we'll get 2 GB a second all right how big do you

00:12:38.360 --> 00:12:44.720
want your drive to be terab oh okay I was expecting more but sure fine no

00:12:43.600 --> 00:12:50.399
that's fine so the first thing we have to do of course is make the drive boom

00:12:47.959 --> 00:12:55.079
done okay and now we're done you're officially ice goed okay we should

00:12:52.720 --> 00:12:59.560
probably configure the BIOS then yep since our computer doesn't have a disc

00:12:56.839 --> 00:13:03.959
to boot from we have to tell it where to boot from right and this is potentially

00:13:02.120 --> 00:13:09.320
more complicated and annoying than one might think um the easy way is to set up

00:13:07.720 --> 00:13:13.399
what we're going to set up on a USB stick and just plug it into the computer

00:13:11.120 --> 00:13:17.680
and boot off the USB stick but then we'd be adding storage and we said we're

00:13:15.199 --> 00:13:21.560
getting rid of that right I guess so instead we're going to use our router

00:13:19.800 --> 00:13:26.440
now you might be familiar with a DHCP server it gives devices on your network

00:13:24.000 --> 00:13:30.800
and IP address yeah it can also give them other things specifically where to

00:13:29.880 --> 00:13:35.639
look for storage interesting okay now the router

00:13:34.040 --> 00:13:39.399
you have a ubiquity dream machine doesn't have the most advanced DHCP

00:13:38.000 --> 00:13:44.199
configuration so you can only really tell it one location to look which

00:13:42.560 --> 00:13:47.160
obviously doesn't work great if we have 10 computers trying to boot off of it

00:13:45.839 --> 00:13:51.720
right cuz then they'd all be getting the same drive right so we made it a little

00:13:49.959 --> 00:13:58.040
bit more complicated and I'm running a web server that it talks to and tells it

00:13:55.360 --> 00:14:01.880
its Mac Address mhm and then based on the Mac Address it responds with the

00:13:59.440 --> 00:14:06.600
disc that it's supposed to use it sounds complicated but honestly it's like 30

00:14:05.000 --> 00:14:10.759
lines in a script here you can look at this like this is the name of the device

00:14:09.279 --> 00:14:15.240
and this is the disc it's abouted to go to and this is the Mac Address all right

00:14:13.480 --> 00:14:18.759
I'm going to link all of the like scrip things we used in the description if for

00:14:17.360 --> 00:14:24.519
whatever reason you want to try to do this what we're going to be using to install Windows is Windows PE or the

00:14:22.079 --> 00:14:28.720
Windows pre-installation environment it's like mini Windows that most of the

00:14:27.160 --> 00:14:33.480
time is used for Network installing Windows is what we're doing um you have

00:14:31.360 --> 00:14:38.959
to take the image that you make and modify it slightly namely just to add

00:14:36.120 --> 00:14:43.639
the network drivers in our case that would be melanox drivers and I've

00:14:40.600 --> 00:14:45.920
already done that okay but it also means

00:14:43.639 --> 00:14:51.320
I need to modify this boot script because which Mac Address do you want oh

00:14:48.639 --> 00:14:56.199
boy oh wait yeah yeah right right right right uh it should be 98 checking media

00:14:54.240 --> 00:15:00.199
presence media present okay we're good all right oh it

00:14:58.560 --> 00:15:06.000
worked wow that's that's great we are glossing over a lot of this but you'll

00:15:03.759 --> 00:15:11.519
see the scripts down below this would be the one that you would use to boot wi PE

00:15:08.560 --> 00:15:16.320
we're glossing over so much this is like the glossiest video Lip Gloss it's so

00:15:13.800 --> 00:15:20.920
shiny editor can you make this shot just like really shiny e is that like a

00:15:18.320 --> 00:15:26.920
filter why does it look like wet set boot URL that's like the file storage

00:15:23.959 --> 00:15:32.800
location uh initiator iqn is like the name of your machine and then sand hook

00:15:30.680 --> 00:15:37.959
that attaches the disc y you can see his name lonus this is the bits it needs to

00:15:36.240 --> 00:15:43.160
download for Windows p and then Boot and then when you go to actually boot you

00:15:40.360 --> 00:15:47.880
just change the sand hook to sand Boot and then just comment all this out and

00:15:45.040 --> 00:15:51.480
in theory it should just boot okay yeah wow look at that we're in so we're going

00:15:49.800 --> 00:15:55.199
to mount a network drive that has our Windows installer on it I don't know if

00:15:53.000 --> 00:16:00.160
it's strictly necessary but I like injected the proper drivers into the

00:15:57.759 --> 00:16:03.680
Windows installer okay you can do that while you're like selecting your disc

00:16:01.639 --> 00:16:07.759
it'll say install drivers yeah um it'll just prompt you I just did it because I

00:16:05.800 --> 00:16:14.360
didn't want to have to screw with that it's every time every time my god oh boy

00:16:10.880 --> 00:16:17.519
oh no it's going to do that thing why

00:16:14.360 --> 00:16:17.519
okay well no I can just use this

00:16:19.240 --> 00:16:24.839
one I think you need to unplug the ssds

00:16:22.240 --> 00:16:29.959
this is the step that usually fails please God please please God can't help

00:16:28.000 --> 00:16:34.920
you where we're going this is the step that installs

00:16:32.519 --> 00:16:38.160
drivers I think it's good when I was researching this everyone talked about

00:16:36.600 --> 00:16:42.639
how this is just like an absolute nightmare to do and like disable Windows

00:16:40.120 --> 00:16:47.560
update and all this stuff it seems to just work as long as you have a Nick

00:16:44.920 --> 00:16:52.279
that supports it we ran into one very modern Nick that just didn't support it

00:16:50.240 --> 00:16:55.600
those 10 gig aquanta ones that are in the land PC that's why when we were

00:16:54.519 --> 00:16:59.399
talking about this at the beginning of the video we were saying 2 and 1/2 gig

00:16:57.680 --> 00:17:05.079
because we were using the board real Tech yeah I tried for days to get it to

00:17:02.560 --> 00:17:08.039
work but their driver just refuses to launch at boot time we're going to boot

00:17:06.760 --> 00:17:12.079
into in P one more time because we have to make a registry edit I'm not 100%

00:17:09.799 --> 00:17:14.799
sure if it's 100% necessary but there's a ton of people that mention it causes

00:17:13.400 --> 00:17:19.120
blue screens if you don't okay we're just going to disable the page file to

00:17:16.760 --> 00:17:22.360
be clear disabling your page file could cause more stability problems than it

00:17:20.799 --> 00:17:28.600
solves so it's not something that we would recommend under normal circumstances this is just experimental

00:17:26.559 --> 00:17:33.960
for now is is that just working is this it I think it's just working this

00:17:31.600 --> 00:17:39.280
shouldn't be that cool to me but I'm not going to lie it kind of

00:17:36.240 --> 00:17:40.840
is I'm just using a computer like I

00:17:39.280 --> 00:17:44.960
would normally use a computer I'm going to install a program like I would

00:17:42.679 --> 00:17:50.120
normally install a program there are definitely some red flags you can see

00:17:46.960 --> 00:17:52.799
the active time of my boot drive here is

00:17:50.120 --> 00:17:57.840
100% And my average response time while it's usually pretty reasonable in the

00:17:55.320 --> 00:18:02.919
sub 20 milliseconds range occasionally it'll pop up to

00:17:59.760 --> 00:18:05.440
half a second that's a yikes you don't

00:18:02.919 --> 00:18:11.480
want to see that like this is not a CPU issue how long it's taking to extract

00:18:07.280 --> 00:18:14.360
this steam package I have a 7950 X oh

00:18:11.480 --> 00:18:21.360
wow do you see that average response time as it's testing random RS is

00:18:17.400 --> 00:18:24.440
getting into the multiple seconds that's

00:18:21.360 --> 00:18:27.039
bad also even these sequential results

00:18:24.440 --> 00:18:33.080
are a fraction of what I was expecting to be getting even with the PC slot

00:18:29.960 --> 00:18:35.039
limitations oh wow even before the game

00:18:33.080 --> 00:18:41.280
starts downloading okay there it finally goes just the reservation process was

00:18:38.400 --> 00:18:47.960
taking up 100% of the active time of the drive still is actually network is doing

00:18:44.960 --> 00:18:49.919
nothing and to be clear this is not the

00:18:47.960 --> 00:18:54.120
fault of those kokia drives they're just like yeah we'll send over storage if you

00:18:51.679 --> 00:18:57.880
guys are doing a wild project those are really fast drives so this comes down to

00:18:56.320 --> 00:19:01.919
the limitations of our Network infrastructure and our implementation

00:18:59.960 --> 00:19:08.120
how's it going oh you've got four of them working yeah that's sick how's the

00:19:05.039 --> 00:19:10.080
that oh it's terrible really yeah why

00:19:08.120 --> 00:19:16.200
just everything is terrible like slow what oh yeah huh even just uh launching

00:19:13.640 --> 00:19:21.600
steam huh took a while Jake I'm logging into steam on

00:19:19.240 --> 00:19:28.320
this system and I just got a system leg Spike that was so intense I couldn't

00:19:24.520 --> 00:19:28.320
move the mouse cursor

00:19:29.679 --> 00:19:39.880
not good there's something very wrong with the permissions on the SMB share

00:19:34.640 --> 00:19:44.000
and it just like yeah it oh

00:19:39.880 --> 00:19:46.880
okay it's not very happy it was an

00:19:44.000 --> 00:19:51.799
interesting experiment I want to know now if you can make it go fast me too

00:19:50.159 --> 00:19:56.559
but I think that's an experiment for another day I want to go unplug one SSD

00:19:54.159 --> 00:20:01.080
I'm going to do it right now note that we've got four systems

00:19:59.159 --> 00:20:05.360
running right now one of which is actively verifying the Integrity of oh

00:20:04.320 --> 00:20:11.960
you did it already Okay well that's one thing it

00:20:09.679 --> 00:20:16.679
does well was I supposed to wait but I think it might finally be

00:20:14.880 --> 00:20:21.360
time to talk about the disadvantages which one you made uh

00:20:19.320 --> 00:20:25.799
every computer in your house way slower you added a single point of failure so

00:20:24.159 --> 00:20:30.320
if that server has a problem which it probably will none of your computers

00:20:28.000 --> 00:20:34.360
work uh and how you going to fix that server you don't have a computer to to

00:20:32.559 --> 00:20:38.559
manage it with to try to fix it it's great and you've added a whole bunch of

00:20:37.159 --> 00:20:42.559
cost that realistically you could put two consumer

00:20:41.000 --> 00:20:47.720
grade drives in every one of your machines and run raid one and complexity

00:20:44.720 --> 00:20:49.760
and management headaches but I'm just

00:20:47.720 --> 00:20:54.360
stoked that this worked I think it's cool and the fact that it would work

00:20:51.480 --> 00:20:58.720
with just about any computer even if we wouldn't recommend doing this at home

00:20:56.159 --> 00:21:03.600
like man okay the fact that the real Technics work at all if we could tune it

00:21:00.919 --> 00:21:06.320
something like a Land Cafe oh I could totally see this like that from a

00:21:05.000 --> 00:21:12.039
manageability standpoint where you actually have an IT admin who's working on it instead of just a home user

00:21:09.480 --> 00:21:16.679
usually when you have a big install base of hundreds of computers you might use

00:21:13.960 --> 00:21:20.000
folder redirection you have a local disc and then you just like redirect the user

00:21:18.039 --> 00:21:22.919
folders to a network share or something like that that way you're optimizing

00:21:21.279 --> 00:21:27.919
your storage use through things like d duplication and compression you're also

00:21:25.240 --> 00:21:31.960
making it way easier for it to manage how much space everybody's using and

00:21:30.600 --> 00:21:36.760
make sure that if something gets accidentally deleted or intentionally

00:21:34.799 --> 00:21:42.120
deleted it can be restored

00:21:38.480 --> 00:21:44.600
um but this is dumb I wouldn't recommend

00:21:42.120 --> 00:21:51.320
booting Windows over ice cuy it does seemingly work but but I would recommend

00:21:47.559 --> 00:21:54.080
checking out Kia's cd8s their PCIe Gen 4

00:21:51.320 --> 00:21:59.559
drives with NVMe 1.4 support they use their 112 layer 3D TLC flash they're

00:21:57.480 --> 00:22:03.240
very fast they're very great and they have a whole lineup of other drives if

00:22:01.360 --> 00:22:06.360
they don't specifically meet your need and you can check them all out at the

00:22:04.360 --> 00:22:14.120
link down below thank you kokia for making it possible for us to deploy Jake

00:22:10.720 --> 00:22:16.120
on Fool's errands like this for extended

00:22:14.120 --> 00:22:20.960
periods of time cuz it's it's pretty cool and look now we can take those

00:22:18.279 --> 00:22:24.720
drives and build them into a new Nas yeah and do something useful with them

00:22:22.600 --> 00:22:29.000
me in hard drives that'd be pretty cool if you guys enjoyed this video maybe go

00:22:26.240 --> 00:22:33.919
check out the one where Jake I built an assas at for your house which is no

00:22:31.320 --> 00:22:33.919
longer here