1
00:00:01,280 --> 00:00:09,200
One of the hard drives in my home server, it just died with my data on it.

2
00:00:06,240 --> 00:00:14,719
And that's totally okay because you see I'm smart and always use protection.

3
00:00:12,000 --> 00:00:20,560
Look, devices disabled, but the contents are emulated because I use not one but

4
00:00:17,520 --> 00:00:23,600
two parody drives, meaning I can lose up

5
00:00:20,560 --> 00:00:25,840
to two drives in this bad boy before I

6
00:00:23,600 --> 00:00:30,560
risk the rest of my data. So, all I got to do is plop in a replacement disc, let

7
00:00:28,560 --> 00:00:35,600
it rebuild from parody, and Bob's your uncle. Server fixed. Except I do

8
00:00:33,520 --> 00:00:39,200
actually have a problem today. When I built this machine, it was still the

9
00:00:37,280 --> 00:00:44,239
early days of a company when you could uh borrow stuff that nobody was using.

10
00:00:42,719 --> 00:00:50,000
Stolen. Wo wo wo wo. So, my choice of hardware

11
00:00:47,200 --> 00:00:54,559
was dictated less by what actually made sense and more by what nobody else could

12
00:00:52,800 --> 00:00:59,680
possibly want, which is how I ended up with these 8 TB Seagate archival drives.

13
00:00:58,160 --> 00:01:04,320
To be clear, I'm not saying they're lowquality. I've been running these

14
00:01:01,199 --> 00:01:06,240
since 2016 when they were manufactured.

15
00:01:04,320 --> 00:01:12,400
I'm just saying that shingled magnetic drives are not great for RAID or even

16
00:01:10,240 --> 00:01:17,200
UNRAID for that matter due to their abominably slow write speeds. And what

17
00:01:15,119 --> 00:01:23,520
really sucks is that while these drives are still available on Newegg, cost per

18
00:01:19,600 --> 00:01:25,840
Gigabyte is awful at about $27.

19
00:01:23,520 --> 00:01:31,759
For some context, I could get my hands on Seagate Iron Wolves in the same

20
00:01:28,080 --> 00:01:35,360
capacity. So, proper actual Naz drives

21
00:01:31,759 --> 00:01:37,840
for just around $20 a terabyte. That is

22
00:01:35,360 --> 00:01:41,520
also a terrible deal. See, here's the thing. There's a fixed cost to

23
00:01:39,920 --> 00:01:45,040
manufacture a hard drive. You've got to build a chassis. You've got to have a

24
00:01:43,439 --> 00:01:49,280
motor. You've got to have platters and time on the production line. So, as

25
00:01:46,880 --> 00:01:54,000
newer, higher capacity drives come out, these lower capacity drives can only

26
00:01:51,680 --> 00:01:59,280
reach a certain point in terms of price, which means that there's often a sweet

27
00:01:56,479 --> 00:02:05,759
spot for dollars per gig. For example, a 16 TB Exos, that's an enterprisegrade

28
00:02:02,159 --> 00:02:09,440
drive, is just $15 per terabyte. That is

29
00:02:05,759 --> 00:02:12,000
only a 50% increase in cost for double

30
00:02:09,440 --> 00:02:16,800
the capacity. Now, if this was for work, I might be fussy and demand matching

31
00:02:14,640 --> 00:02:20,239
drives, but this is for my house where I'm running Unrade. One of the key

32
00:02:18,720 --> 00:02:24,000
benefits of which [music] is the ability to mix and match. So, I'm just going to

33
00:02:22,160 --> 00:02:27,840
pick up whatever's the best bang for the buck and stuff it in there.

34
00:02:25,440 --> 00:02:33,040
Unfortunately, with that flexibility comes some trade-offs. like a regular

35
00:02:30,239 --> 00:02:39,760
RAID array. I could replace my dead 8 TBTE drive with a larger one, say a 22

36
00:02:36,959 --> 00:02:45,120
TB Iron Wolf Pro, but I would only get to use a fraction of that capacity. 8 TB

37
00:02:42,800 --> 00:02:50,959
to be precise. So, it matches the rest of my drives. Then, Unrade's flexibility

38
00:02:47,680 --> 00:02:52,959
shows up again. And as long as my par

39
00:02:50,959 --> 00:02:59,120
drives match the capacity of my replacement drive, I get the full juice.

40
00:02:56,080 --> 00:03:02,560
So, I made the call today to replace two

41
00:02:59,120 --> 00:03:04,720
drives, neither of which is my dead one.

42
00:03:02,560 --> 00:03:08,879
Then, I'm going to take my two parody drives and throw them into the array to

43
00:03:07,040 --> 00:03:13,440
replace the dead one to give me a little extra capacity today. And with these

44
00:03:11,280 --> 00:03:18,879
juiced up parody drives to give me an easy, coste effective path to even more

45
00:03:16,720 --> 00:03:24,000
storage. The bad news is, as clever as our devious plan is, it is a little bit

46
00:03:21,440 --> 00:03:28,000
more complicated to execute. A straight drive replacement is pretty simple

47
00:03:26,000 --> 00:03:31,680
because it uses the parody drives to rebuild the data. But if we want to

48
00:03:29,599 --> 00:03:35,120
replace parody drives while we have a dead drive, is there a safe way to do

49
00:03:33,519 --> 00:03:38,879
this? Do we need a third drive [music] to sit and take that spot for now?

50
00:03:37,680 --> 00:03:42,640
I don't know if you can do that in unrated. I do happen to have a third drive. So,

51
00:03:40,799 --> 00:03:47,440
we could just replace the dead one, then do the parody swap. The way to do it would be to replace the

52
00:03:45,360 --> 00:03:49,440
dead drive and then replace the parody drives. I think we should do that. I have a

53
00:03:48,879 --> 00:03:53,760
third drive. Okay, we're going to cheat. I mean, in theory, we could replace one

54
00:03:51,920 --> 00:03:59,120
parody drive at a time. I think. But here's the thing. The most likely

55
00:03:56,640 --> 00:04:03,599
time for a hard drive to die is during an array rebuild because you're putting

56
00:04:01,120 --> 00:04:08,480
strain on all the drives in the array. So having two parody drives means that

57
00:04:06,080 --> 00:04:13,599
even if one more drive does fail while we're doing a rebuild, we're still

58
00:04:10,400 --> 00:04:16,000
golden. If we were to intentionally

59
00:04:13,599 --> 00:04:20,239
take out a parody drive, then lose a drive during a rebuild, we would be

60
00:04:17,840 --> 00:04:23,919
kicking Jake because that was his suggestion. I'd also be kicking myself

61
00:04:22,400 --> 00:04:27,919
because I knew better. I knew better.

62
00:04:25,520 --> 00:04:30,080
Let's just use uh a third drive.

63
00:04:28,880 --> 00:04:35,360
Yeah. And then that way you have even more capacity. Do you happen to know the serial of the

64
00:04:32,160 --> 00:04:37,600
dead one? Does it happen to be

65
00:04:35,360 --> 00:04:39,840
F4SB? What are my odds here?

66
00:04:39,199 --> 00:04:46,400
No. Rat. Ewde. Ewde. Got them.

67
00:04:43,600 --> 00:04:49,600
That's not so bad. Are they screwed in? Uh, I mean they're supposed to be

68
00:04:47,919 --> 00:04:56,000
screwed in. I don't see any screw. Oh, we got one screw, boys. Yep. This server

69
00:04:52,479 --> 00:04:57,919
was built by me with this Noctua edition

70
00:04:56,000 --> 00:05:01,600
LT screwdriver. How freaking awesome does that look? You can sign up for a

71
00:05:00,000 --> 00:05:06,160
notification when it gets in stock. ltstore.com. Two screws is enough,

72
00:05:04,080 --> 00:05:10,560
right? Enough screwing up the segue to our sponsor. Sorry, I was supposed to do

73
00:05:07,600 --> 00:05:15,440
that a while ago. MSI. You can game, stream, and create to your fullest

74
00:05:12,560 --> 00:05:19,199
potential with MSI's RTX 4060 Gaming X Trio graphics card. With their Tri

75
00:05:17,440 --> 00:05:24,160
Frozozer 3 thermal design and support for MSI Afterburner, the sky is the

76
00:05:21,360 --> 00:05:28,000
limit, but don't drop it. It can't actually fly. You can check it out at

77
00:05:26,320 --> 00:05:31,039
the link in the video description. Did you add the other drives yet?

78
00:05:29,360 --> 00:05:34,800
Well, not yet. Do you want me to add the other ones right now? I might as well.

79
00:05:32,720 --> 00:05:38,400
See, I could, but all the hardware for this computer is inside it. Why don't

80
00:05:36,800 --> 00:05:42,720
you just take one screw from that drive that had two screws and use that?

81
00:05:40,080 --> 00:05:45,840
These are really shoddy trays. I don't know if one screw is enough.

82
00:05:44,240 --> 00:05:50,080
I mean, it's just got to hold the drive attached to the sled when you pull it in

83
00:05:47,440 --> 00:05:53,520
and out. I think it's probably fine. Oh my god. Against my better judgment.

84
00:05:52,320 --> 00:06:00,000
What are you talking about? You were just saying your sleds have no screws in them anyways. Better judgment, my ass.

85
00:05:58,240 --> 00:06:03,360
I just put that bloody archive drive back in.

86
00:06:01,759 --> 00:06:09,520
Where did I put it? Oh my gosh. Ew. Ewde. Yeah, it wouldn't have actually

87
00:06:06,960 --> 00:06:14,960
screwed anything up, but it would have confused me really good. Oh no, another

88
00:06:12,560 --> 00:06:18,720
drive died. Got my super convenient radiator on the back of my rack here,

89
00:06:16,720 --> 00:06:23,280
which makes it really easy to get at everything. I'm going to get a little

90
00:06:20,720 --> 00:06:26,960
bit older and I'm going to start really caring a lot more about the ergonomics

91
00:06:24,800 --> 00:06:29,840
of my setups. This procedure is going to vary a bit depending on what NAS

92
00:06:28,720 --> 00:06:34,720
software you're running, but fundamentally the idea is the same.

93
00:06:31,919 --> 00:06:38,400
You've got a disc that is no longer present. You can see it's showing not

94
00:06:36,319 --> 00:06:43,039
installed. And we want to take a combination of the data that's on our

95
00:06:40,720 --> 00:06:47,680
other discs and the data that's on our parody discs and use that to rebuild the

96
00:06:45,280 --> 00:06:51,199
data that used to be on it. I have never actually done this in Unre before.

97
00:06:49,440 --> 00:06:54,240
Yeah, that was a really fun way to say it's a pain in the ass to do this in

98
00:06:52,720 --> 00:06:57,759
Unre. I just happen to be wearing my Trunass

99
00:06:56,080 --> 00:07:01,520
scale shirt today. It's very easy to do in Trunass. You don't even have to shut

100
00:06:59,599 --> 00:07:07,280
down the entire array like I'm about to do. Trunaz is way better in a lot of ways.

101
00:07:05,599 --> 00:07:11,440
But [music] the way that it's not way better is the ability to just

102
00:07:08,960 --> 00:07:15,199
willy-nilly, oh, I don't know, I'll throw one drive in or [music] I'll throw

103
00:07:13,759 --> 00:07:19,440
another drive in. Oh, by the way, they don't match at all. With that said, there are plugins for Trunz that allow

104
00:07:18,240 --> 00:07:24,400
you to get kind of similar functionality. For personal use, I still

105
00:07:21,759 --> 00:07:27,440
think Unra is pretty strong. Um, we just pick whichever one we want.

106
00:07:26,000 --> 00:07:31,599
Yeah. So, this is going to replace our broken drive. How

107
00:07:29,840 --> 00:07:37,039
spicy do you want to get today? Cuz if I do that, this is my secondary copy of this data.

108
00:07:34,880 --> 00:07:42,080
Oh, so then why don't we just full send? Well, because then I will only have one

109
00:07:39,360 --> 00:07:46,000
copy of my data. Besides, you can't full send. You can't do one drive and both

110
00:07:44,560 --> 00:07:49,919
parodies at once anyway. Well, full send in this situation would

111
00:07:47,599 --> 00:07:52,639
be one parody and one drive. I don't know if it'll let us do that, [music]

112
00:07:51,039 --> 00:07:57,520
though. I don't really want to find out. Let's not find out. Okay. Disc in parody slot is not

113
00:07:55,599 --> 00:08:01,360
biggest. Wait, you can't even do [music] this? That's stupid.

114
00:08:00,000 --> 00:08:07,440
What? I should be allowed to at least temporarily do this. If you're adding a

115
00:08:05,199 --> 00:08:10,560
new disc or replacing a disabled disc, try parity swap.

116
00:08:09,039 --> 00:08:14,720
Why wouldn't it just be like, "No, you only get 8 terabytes." Like ZFS.

117
00:08:12,319 --> 00:08:18,639
I could have sworn it did. Parody drive always has to be the largest drive or

118
00:08:16,639 --> 00:08:20,800
the same size as the largest. Okay, so we have to do the parody drives [music]

119
00:08:20,160 --> 00:08:24,960
first. Can we just wipe this? Oh, no. No, no, no. Just

120
00:08:23,840 --> 00:08:30,720
copy it all. No, no, no. Then I'll only have one copy of the data. That is not 321. Jake,

121
00:08:29,520 --> 00:08:35,599
this isn't 321. This is my precious memories. Oh my gosh. Put them on Google Drive or

122
00:08:34,560 --> 00:08:41,120
something. No. Why don't you use cloud storage?

123
00:08:38,240 --> 00:08:46,640
Well, a number of reasons. One is any of the data that is precious to me, I don't

124
00:08:44,560 --> 00:08:49,760
necessarily think should be on a cloud server somewhere, like pictures of my

125
00:08:48,320 --> 00:08:53,519
kids. Number two, you could encrypt it. [music] is any of

126
00:08:51,519 --> 00:08:59,519
the data that isn't particularly precious, like Linux ISOs for example,

127
00:08:56,959 --> 00:09:01,440
what I'm going to pay a monthly fee to have that stored in the cloud somewhere.

128
00:09:00,880 --> 00:09:06,800
No, I'm not. You could just upload just the precious stuff. Yeah, but then it's also super

129
00:09:04,560 --> 00:09:10,080
inconvenient to have to go and get that stuff if I get it again. I can just have

130
00:09:08,160 --> 00:09:14,000
two copies of it. That's what you're supposed to do. You make that face, but

131
00:09:11,760 --> 00:09:18,000
that's what you are supposed to be online. Yeah, [music] but it isn't. It's here.

132
00:09:16,160 --> 00:09:22,800
Okay. Anyways, replacing a parody drive is a lot more annoying. And I'm kind of

133
00:09:19,920 --> 00:09:26,880
worried because this array drive, can I just like what happens if I remove this?

134
00:09:25,040 --> 00:09:29,839
Can I start it with only one parody drive? Disable the missing disc and

135
00:09:28,640 --> 00:09:34,240
bring the array online. Install replacement disc as soon as possible. But what is that going to do? That

136
00:09:32,640 --> 00:09:37,040
doesn't help us. Unless I can use this now as the array disc.

137
00:09:35,680 --> 00:09:41,680
Yes, you probably could. Okay, so that's what we should do then a

138
00:09:39,600 --> 00:09:46,440
hopefully this doesn't break anything. I mean, if it does, it is the second.

139
00:09:46,480 --> 00:09:51,440
Don't you love it when we do a guide and we're figuring it out as we go?

140
00:09:49,600 --> 00:09:55,920
Well, when you replace a parody drive normally, you reset the config, which is

141
00:09:53,680 --> 00:09:58,640
like which slot each disc is assigned to. You add it and then it formats it

142
00:09:57,680 --> 00:10:04,959
and does everything right. But because we're missing that disc, I

143
00:10:01,839 --> 00:10:06,320
was not sure about doing that. I'm less

144
00:10:04,959 --> 00:10:12,080
sure about this even, but this is the route we took. There's no going back [laughter] now.

145
00:10:10,467 --> 00:10:15,707
[snorts] Parody 2, return to normal operation. I

146
00:10:14,079 --> 00:10:17,727
don't think so, homie. [laughter]

147
00:10:17,920 --> 00:10:23,760
It's not there. Just leave it, buddy. Just leave it. It's going to be okay.

148
00:10:22,079 --> 00:10:30,880
It's dismissed now. You are dismissed. So, about truness. Hey, it's fine. Okay.

149
00:10:28,399 --> 00:10:34,000
So, now we shut it off again. This was surprisingly not that difficult. And

150
00:10:32,399 --> 00:10:38,560
it's not forcing us to recalculate the par. We do this.

151
00:10:36,800 --> 00:10:42,000
Can I do these both at the same time? No way. This is actually kind of okay.

152
00:10:41,680 --> 00:10:46,320
Very. You can't do that. It wasn't very obvious to the user, but if this works,

153
00:10:45,680 --> 00:10:51,360
then that's great. Yeah. Okay. What I'm concerned about is if I do this, when I go to add the other 22,

154
00:10:50,079 --> 00:10:53,760
replace this one, is it going to freak out? No, it shouldn't. Okay. So, let's

155
00:10:53,440 --> 00:10:58,720
Okay. I mean, theories. [gasps]

156
00:10:56,800 --> 00:11:02,959
This is a spicy salami. I'm really glad that we are

157
00:11:00,079 --> 00:11:05,680
experimenting on my secondary data right now.

158
00:11:03,360 --> 00:11:09,200
I will say moving to a 22 TB drive is going to kind of suck because now when

159
00:11:07,360 --> 00:11:12,640
you go to rebuild your parody, it's rebuilding 22 TB of parody instead of

160
00:11:11,120 --> 00:11:16,160
eight. [music] But at least it's not a shingled drive. Hey, look. Parody 2 is

161
00:11:14,640 --> 00:11:20,000
being reconstructed. Just give it some time. You're so impatient. Just

162
00:11:18,800 --> 00:11:24,640
Why are you even worried? It's the second copy. Yeah, well, I you know, if you lose your

163
00:11:23,279 --> 00:11:27,440
second copy, then you only have one copy. I only have one copy. [music]

164
00:11:26,560 --> 00:11:32,240
No problem. Oh, one day in 8 hours total. Yeah, cuz

165
00:11:29,839 --> 00:11:35,519
now it has to do 22 terb. So, does that mean that that other parody drive once

166
00:11:33,920 --> 00:11:41,360
this is done is just going to be doing nothing? How does that work? I have no idea. Cuz if it's thinking

167
00:11:38,880 --> 00:11:45,200
that the parody now is 22 TB, this is very No, that's fine because par drives can

168
00:11:43,360 --> 00:11:50,000
be whatever you want. So you have this par drive is as big or larger than all

169
00:11:48,399 --> 00:11:53,839
of the array discs for now. So I wonder what I guess once

170
00:11:52,079 --> 00:11:56,560
if we were to try to add a 22 after this, it would complain. Correct.

171
00:11:55,440 --> 00:11:59,440
Unless you remove the eight. Unless I also upgrade the other parody

172
00:11:59,120 --> 00:12:03,279
drive at the same time. Then I can do whatever I want, which you should be able to do.

173
00:12:02,320 --> 00:12:10,880
Oh, yeah. Right. Yeah. So the next operation, you swap the eight to a 22. You add another 22 or or

174
00:12:09,680 --> 00:12:14,240
don't even I guess. Yeah, that's funny. We are using the parody

175
00:12:12,720 --> 00:12:18,399
drive to replace the other one. Oh, hey. Are you out? She's out. Wow,

176
00:12:16,480 --> 00:12:21,600
these Oh, they're those quality rails that are all plastic. I just had to go

177
00:12:20,320 --> 00:12:25,680
help Alex for a bit. So, in the meantime, I'm going to take his old

178
00:12:23,360 --> 00:12:30,320
server and put it into the new chassis without him even knowing. Fun fact, this

179
00:12:28,160 --> 00:12:37,360
is actually like the original WanX server. Um, like look at this accessory

180
00:12:33,360 --> 00:12:39,680
box. See that WX server?

181
00:12:37,360 --> 00:12:45,279
And even cooler, there's a Windows Windows license sticker stuck to this.

182
00:12:42,320 --> 00:12:49,279
Totally normal LT screwdriver. I remember this computer. [laughter]

183
00:12:47,040 --> 00:12:53,120
This thing is such a piece of crap. It doesn't have a graphics card in it, so

184
00:12:50,880 --> 00:12:58,160
there's no video output. And uh because it's a Workstation X299 board, there's

185
00:12:55,680 --> 00:13:02,240
no onboard graphics. So, this system has no video output. earlier when it wasn't

186
00:13:00,320 --> 00:13:05,600
turning on. I don't know how to see if it's working or not because there's no

187
00:13:03,600 --> 00:13:10,320
video output. You press caps lock on the keyboard, but that's all you're getting.

188
00:13:07,839 --> 00:13:14,320
It's so dusty, too. Look at that. That's Linus skin. Somebody on the internet

189
00:13:12,880 --> 00:13:17,920
would probably pay money for that, man. He never even peeled it. Is that It

190
00:13:16,079 --> 00:13:23,120
still has the plastic on it. Hold on. Oh, brand new underneath. The nicest

191
00:13:20,639 --> 00:13:27,680
part of this machine. This Storinator over here is already pretty much ready

192
00:13:26,000 --> 00:13:30,880
to go. I think I even cleaned it. Yeah, look at that. It's so clean in here.

193
00:13:29,200 --> 00:13:36,959
Doesn't need the boot drives that are in here right now. We're going to take those out and put the Unrade cache

194
00:13:34,160 --> 00:13:41,440
drives in here. Uh Unrade uses a USB stick to boot off of, which is really

195
00:13:38,800 --> 00:13:45,279
not great. Um because USB drives are not very durable and they can fail, which

196
00:13:43,279 --> 00:13:48,959
causes you a lot of headaches. But, uh that's not my problem. That's Linus'

197
00:13:46,800 --> 00:13:53,279
problem and it makes our life a little bit easier. So, let's start moving some

198
00:13:51,360 --> 00:13:57,360
stuff over. I think I've chirped him for this in the past, but this honestly is

199
00:13:55,120 --> 00:14:00,639
kind of a legitimate strat. Uh, you take all the accessories for your your NAS or

200
00:13:59,519 --> 00:14:04,720
your computer and you put them in a baggie and just

201
00:14:03,120 --> 00:14:10,909
tuck them in there. I don't need them, so I think I'm just gonna stop touching

202
00:14:07,519 --> 00:14:10,909
things I don't need. [laughter]

203
00:14:11,839 --> 00:14:17,519
Tastes like 5'1. These are the cache SSDs from Linus' Unrade pool. And we do

204
00:14:16,320 --> 00:14:22,480
need these because they store the virtual machine discs

205
00:14:19,760 --> 00:14:24,959
and those are important. You know, I'm grateful you only put one screw in all

206
00:14:24,000 --> 00:14:28,720
these drives. I know, right? It's going to make this a lot easier.

207
00:14:28,000 --> 00:14:34,560
Look at these. I dropped a screw. I don't think they're magnetic.

208
00:14:32,399 --> 00:14:38,079
They're not really magnetic, but the LT screwdriver is so magnetic that even the

209
00:14:36,639 --> 00:14:44,160
not really magnetic screws still stick to it. I'm going to make a slight modification to this here server. By

210
00:14:42,160 --> 00:14:47,600
default, there's two separate brackets that hold the SSDs at the back. And this

211
00:14:46,240 --> 00:14:51,279
is really annoying because you can't take the SSDs out without unscrewing

212
00:14:49,839 --> 00:14:56,320
four screws at the back that hold these two brackets and then all eight screws

213
00:14:53,199 --> 00:14:58,639
on the SSDs. What you can do is forget

214
00:14:56,320 --> 00:15:01,920
about that piece and just screw the SSDs into the top because that's already

215
00:15:00,399 --> 00:15:06,320
plenty. And then if you need to swap them out, you just take those two screws

216
00:15:03,440 --> 00:15:12,560
out and it comes out. Hey, look at that. Beautiful. We got SSD and other more

217
00:15:10,160 --> 00:15:15,440
different SSD. Now, if you ever wants to move these SSDs or replace them, you

218
00:15:14,320 --> 00:15:19,040
just take out those two screws and the SSD comes right out. Last but not least,

219
00:15:17,600 --> 00:15:22,639
the hard drives. He doesn't have anywhere near the 60 drives that this

220
00:15:20,959 --> 00:15:26,079
chassis can hold. So, I'm going to space them out uh just to make the air flow a

221
00:15:24,639 --> 00:15:33,680
little bit better. It actually does make a pretty substantial difference to the drive temps.

222
00:15:30,560 --> 00:15:35,440
There's dust on the drives, too.

223
00:15:33,680 --> 00:15:38,800
I'm going to plug in that IPMI, which is something this server has that the other

224
00:15:36,720 --> 00:15:42,720
one did not. That allows you to fully access this machine like you have a

225
00:15:40,959 --> 00:15:47,120
monitor, keyboard, and mouse plugged in anywhere on the network, which is

226
00:15:44,240 --> 00:15:50,320
awesome. Um, but then we need Wait, why is there water all over the floor? Is

227
00:15:48,480 --> 00:15:55,600
that supposed to be like that? Ah, it sounds like not our problem.

228
00:15:53,690 --> 00:16:00,079
[laughter] One of the kind of annoying things about

229
00:15:57,199 --> 00:16:04,720
booting from a USB is sometimes certain systems will just be like, "That's not a

230
00:16:02,480 --> 00:16:08,240
boot drive, that's a USB." And then you have to manually configure it to boot to

231
00:16:06,720 --> 00:16:12,959
that as the first option. So, I don't know. It might be turning on. Oh my god,

232
00:16:10,480 --> 00:16:16,880
Lionus. How many things could you possibly tangle around this? What are

233
00:16:15,279 --> 00:16:23,360
the odds of just boot? Oh my god, look at that. It's booting

234
00:16:20,160 --> 00:16:27,199
slow clap. Do you love Linux or what?

235
00:16:23,360 --> 00:16:29,040
Just no around. Windows update

236
00:16:27,199 --> 00:16:30,800
blah blah blah driver blah blah blah. Just load all the drivers. It'll be

237
00:16:30,480 --> 00:16:39,920
fine. Exactly, though. The funny thing is we were just memeing that old server has a Windows 8.1 Pro uh

238
00:16:36,880 --> 00:16:40,399
like OEM license stuck to the side of

239
00:16:39,920 --> 00:16:43,680
it. Oh, yeah. Yeah. Yeah. That's basically Windows Server, right? Yeah.

240
00:16:43,199 --> 00:16:48,560
Yeah, pretty much. Yeah, but Wow. That's what I ran on it.

241
00:16:47,839 --> 00:16:54,160
Yeah, exactly. As our file server. Yeah, exactly. It's great how old that chassis is.

242
00:16:52,000 --> 00:16:57,199
I actually had forgotten that we ever used Windows.

243
00:16:55,120 --> 00:17:03,759
Windows-based SMB server. [music] Not actually that stupid. Not genius.

244
00:17:01,920 --> 00:17:07,120
Look, you said it, not me. Are you ever going to use this second network port?

245
00:17:06,160 --> 00:17:10,799
Nope. I'll just add it to the bond anyways.

246
00:17:09,199 --> 00:17:13,839
What's the point of me even answering questions when you ask them?

247
00:17:12,319 --> 00:17:18,319
Well, you know, I just try to ignore you. You know what they say. Happy

248
00:17:15,839 --> 00:17:20,720
Lionus, happy life. Happy wife's boyfriend, happy life.

249
00:17:19,679 --> 00:17:27,039
Oh my god. Happy boyfriend's wife.

250
00:17:23,360 --> 00:17:28,319
Boyfriend's wife. This server is finally

251
00:17:27,039 --> 00:17:33,840
being put to sleep. You know what? It's earned its sleep.

252
00:17:30,720 --> 00:17:35,039
Did it go from Wikoff

253
00:17:33,840 --> 00:17:38,080
stuff right to your house? Yeah, cuz I think this was the security

254
00:17:36,880 --> 00:17:43,520
server, wasn't it, for a little bit? Yeah, I think it was decommissioned for maybe a few months and then I went, "Oh,

255
00:17:41,280 --> 00:17:46,559
hey, nobody's using this and Jake hates these things." So, we're never going to

256
00:17:44,640 --> 00:17:50,799
use it again. I took it home and it's been working perfectly since then.

257
00:17:48,320 --> 00:17:53,440
Speaking of operating flawlessly, I plugged into the 10 gig nick that was

258
00:17:52,400 --> 00:17:59,360
already in there. Did this one have 10 gig? It must have. It did. So, in theory, my downgrade is complete.

259
00:17:57,440 --> 00:18:06,240
Upgraded my storage, but my processor is actually slower. It's substantially slower. This is like

260
00:18:01,679 --> 00:18:09,760
a Zeon V48 core. I had a really weird

261
00:18:06,240 --> 00:18:11,600
chip in here, the 9990 [music] XE. Intel

262
00:18:09,760 --> 00:18:17,280
only ever made a handful of them. It was 14 cores at 5 GHz on a weird workstation

263
00:18:14,960 --> 00:18:21,280
board. But there's real benefits from moving to server hardware, like the fact

264
00:18:18,960 --> 00:18:24,880
that I can remote in with IPMI, even when the system's powered off, so I can

265
00:18:22,799 --> 00:18:28,240
power cycle it. Or if I'm away and I get a notification that the power's gone off

266
00:18:26,480 --> 00:18:30,160
at my house from my UPS, I can remote in, turn off my server, that kind of

267
00:18:29,679 --> 00:18:34,559
thing. Yeah, this one didn't even have a video output. Like I was saying earlier, we

268
00:18:33,200 --> 00:18:39,679
there was no way to see what it was doing. I took out my one GPU because I put it

269
00:18:37,440 --> 00:18:41,919
in the Trunaz machine so that I could try and use GPU acceleration and Plex,

270
00:18:41,679 --> 00:18:48,577
right? And then it turned out that GPU was defective. Anyway, hey, look at that. The parody sync is

271
00:18:46,160 --> 00:18:52,799
running. So, it's rebuilding this disc [music] and then building the parody on

272
00:18:50,960 --> 00:18:56,799
this disc. So, when this is done, I guess you shut down the array, remove

273
00:18:54,880 --> 00:19:01,200
this disc, start it again so it thinks it's not there anymore, stop it, add the

274
00:18:58,960 --> 00:19:09,919
20. You get the deal. and it will still be slow slow like this segue to our sponsor

275
00:19:07,919 --> 00:19:13,840
Keeper. One of the most important steps to take with personal cyber security is

276
00:19:11,679 --> 00:19:17,520
proper password safety. The majority of security breaches are the result of

277
00:19:15,200 --> 00:19:21,280
human error and weak or stolen passwords are big contributors. Keeper security

278
00:19:19,840 --> 00:19:24,880
lets you manage and track all of your passwords and private info. The platform

279
00:19:23,280 --> 00:19:28,799
autofills your usernames, your passwords, and your 2FA codes on both

280
00:19:26,640 --> 00:19:32,720
mobile and desktop on any device. All you need to remember is your strong

281
00:19:30,160 --> 00:19:36,640
master password to access Keeper. Since they use a zero trust and zero knowledge

282
00:19:34,559 --> 00:19:40,880
security model, only you have access and control over who can see your passwords.

283
00:19:38,880 --> 00:19:46,000
And Keeper is hooking our audience up with a huge 50% off both family and

284
00:19:43,280 --> 00:19:50,480
personal plans with code LTT50. Plus, there's an exclusive 30-day free trial.

285
00:19:48,320 --> 00:19:54,240
And feel free to use that code LTT50 after if you want to keep using Keeper.

286
00:19:52,559 --> 00:19:57,919
Keep your data locked up by clicking the link below. If you guys enjoy this kind

287
00:19:56,160 --> 00:20:00,880
of server maintenance, boy, do we ever have some video suggestions for you. I

288
00:19:59,600 --> 00:20:04,960
don't think I [music] can suggest just one. You know what? Why don't we do the

289
00:20:02,720 --> 00:20:07,888
vlog where we cleaned out the server room with compressed [music]