WEBVTT 00:00:00.000 --> 00:00:06.280 I'm here live in studio with the one and 00:00:03.560 --> 00:00:10.080 only deadmau5. Hey, can I Can I Can I put my arm around you like this? 00:00:08.400 --> 00:00:15.320 I mean Can I kind of rub your back like this? Can I Can I kind of grab your ass like 00:00:13.120 --> 00:00:15.320 this? 00:00:18.480 --> 00:00:26.000 Did you just light up a cigar? No. Have you actually opened this? No, I haven't. 00:00:23.480 --> 00:00:29.680 I like to keep a fresh perspective when I open something for the first time. 00:00:27.600 --> 00:00:33.640 They'll even go and reseal boxes for me. Of course, your first question is 00:00:31.360 --> 00:00:39.160 probably what exactly is it that I have not unboxed yet. It's a collaborative 00:00:36.640 --> 00:00:44.960 product between 45 Drives, who you may remember from their servers that hold 45 00:00:41.960 --> 00:00:48.480 Drives or more, and the one and only 00:00:44.960 --> 00:00:52.120 deadmau5, and it's called the 45 Studio, 00:00:48.480 --> 00:00:54.920 and it is a silent, high-performance, 00:00:52.120 --> 00:01:02.880 local network storage device that is explicitly for Oh, wow, it's 00:00:59.520 --> 00:01:03.040 really sexy. Sorry, explicitly for 00:01:02.880 --> 00:01:09.880 >> [music] >> content creators. Not just sexy content creators. I know, I I feel excluded from 00:01:08.080 --> 00:01:14.440 this list. I would hate for you to feel excluded, Joel. So, why don't you talk 00:01:11.520 --> 00:01:19.920 me through some of what you contributed to this collaborative endeavor? Tell me 00:01:16.640 --> 00:01:21.600 what makes this ideal for a musician. 00:01:19.920 --> 00:01:28.160 You've hooked me onto 45 Drives, and you've done absolutely nothing to accommodate my needs, right? But, we're 00:01:24.960 --> 00:01:30.200 talking from the OG storage units that I 00:01:28.160 --> 00:01:33.600 got, and then eventually upgrading to a storage unit or something like that. 00:01:31.320 --> 00:01:37.320 These units, they got fans, and they are loud. Like, for my needs, it was fine 00:01:35.800 --> 00:01:41.440 because, you know, I've got my machine room. I can tuck that thing away and and 00:01:39.200 --> 00:01:46.560 let it pound the sound. But, that's a privilege to just have an isolated space 00:01:44.520 --> 00:01:49.720 that's separate from their studio space. Correct. I always thought like, how cool 00:01:48.240 --> 00:01:55.560 would this thing be like on my desk and I could just like, you know, have there, 00:01:51.880 --> 00:01:57.520 pick up, bring to my video editor's 00:01:55.560 --> 00:02:01.720 place, you know, in a car or something like that, and just have them have it 00:01:58.760 --> 00:02:07.800 sit on the desk. Right. So, quiet is As for the art on there, language on 00:02:04.320 --> 00:02:10.679 that is Strudel. See this young woman 00:02:07.800 --> 00:02:14.240 on Twitch that live codes music, and it's insane. I want to crack this open 00:02:12.680 --> 00:02:18.520 because You can put a little heat sink on a Raspberry Pi. Good job. You created 00:02:16.200 --> 00:02:21.960 a silent system. Creating a silent, high-performance system, that takes a 00:02:20.360 --> 00:02:25.600 little bit more work. Let's grab a screwdriver. Hey, uh since I'm walking 00:02:23.960 --> 00:02:30.000 around you here, I noticed this is a wonderful hoodie you're wearing. Where 00:02:27.040 --> 00:02:32.880 Where did you get that? Thank you. Uh 00:02:30.920 --> 00:02:35.760 You're a fun guy. Let me see it. Oh, you haven't even seen it? Oh, you're You're 00:02:34.440 --> 00:02:40.760 wearing the same one as me. So, you got some PCIe slots on there. Got like a 00:02:38.840 --> 00:02:44.240 cool patch on the hood. It's pretty gangster. Whole thing's UV reactive 00:02:42.640 --> 00:02:48.400 because, of course, it is. I'm going to have mortgage payments, guy. I just 00:02:46.320 --> 00:02:52.440 recently got my unit. So, we have the same unit. Hey, there we go. All right, 00:02:50.880 --> 00:02:56.720 non-ferrous screws. I know they're higher quality, but 00:02:54.640 --> 00:03:02.680 the 45 Drives. All right, here it is. Check this out. 00:03:01.040 --> 00:03:08.880 Did I hear you correctly? So, that's a vapor chamber base with eight heat 00:03:06.040 --> 00:03:13.320 pipes. So, we've got four running over to this side where we've got these 00:03:11.160 --> 00:03:17.440 copper plates that have a thermal interface material over to these giant 00:03:15.560 --> 00:03:21.360 fins on the side. Then, we've got four more over to the other side. You might 00:03:19.600 --> 00:03:25.280 look at these fins and go, "Okay, well, hey, those aren't very dense fins. Is 00:03:23.280 --> 00:03:28.840 that really going to be that great?" And you're kind of right because it's not as 00:03:26.840 --> 00:03:32.960 much surface area as if you had a bunch of really dense little fins. But, it 00:03:31.080 --> 00:03:37.560 turns out that for passive cooling, you actually don't want the most dense fins 00:03:35.440 --> 00:03:41.160 because you've got to have enough room for the air to heat up next to them, and 00:03:39.280 --> 00:03:46.200 then for convection to take place and carry that heat up away from the system. 00:03:43.440 --> 00:03:50.120 That is a tiny motherboard. This is cool, too. I'm surprised that more 00:03:47.960 --> 00:03:54.520 system builders don't do this. It's a simple little 3D printed part, and it 00:03:52.720 --> 00:03:58.920 performs a simple function, but it's really important. What this does is it 00:03:56.520 --> 00:04:03.800 goes right here over the two passive heat sinks that are already integrated 00:04:01.040 --> 00:04:08.520 onto the motherboard, and it allows them to have intakes at the very bottom, and 00:04:06.400 --> 00:04:13.680 then creates a chimney for them to exhaust their heat up rather than 00:04:11.360 --> 00:04:17.600 allowing them to get heat saturated by all the parts around them that under 00:04:15.480 --> 00:04:21.680 heavy load could be kicking out a fair bit of heat into the inside of the 00:04:19.320 --> 00:04:25.720 chassis. Oh, wow, the power supply is passive, too. That's just chillin' 00:04:23.640 --> 00:04:29.360 there. No pun intended. Well, pun a little bit intended because the system 00:04:27.840 --> 00:04:34.280 doesn't consume that much power. So, the CPU is a quad-core, eight-thread affair. 00:04:32.000 --> 00:04:39.640 This one's configured with 64 gigs of DDR5 memory. It's got a Kingston NVMe 00:04:37.720 --> 00:04:43.480 boot drive, and then you can have up to eight SATA SSDs in the front. Why don't 00:04:42.000 --> 00:04:49.720 we take a look at the back? Do you see it as a problem that it's only got a 00:04:45.600 --> 00:04:52.000 couple USB ports, a VGA video output, 00:04:49.720 --> 00:04:57.080 and then it's got what looks like dual 10 gig Ethernet [music] interfaces? I I 00:04:55.240 --> 00:05:01.240 I do and I don't. This thing's network accessible, so it's just kind of a turn 00:04:58.920 --> 00:05:05.720 it on, let it boot, and then get it on the web server. My only real criticism 00:05:03.440 --> 00:05:09.320 about these kind of devices are the as VGA output. Theoretically, it shouldn't 00:05:08.080 --> 00:05:14.280 be a problem cuz you've got your management port here. You can [music] reconfigure the BIOS. You can install an 00:05:12.440 --> 00:05:19.240 operating system. You never have to hook a display up to it. But, yeah, okay. If 00:05:16.720 --> 00:05:23.040 you do, VGA can feel like a bit of a downer, but that's just standard in the 00:05:20.720 --> 00:05:26.200 server space, and this is a server-grade motherboard, so you're kind of going to 00:05:24.720 --> 00:05:30.600 have to live with it. All right, I'm going to get the panel thrown on, and then I guess we should talk about our 00:05:29.240 --> 00:05:36.200 sponsor. Do we have a sponsor for this video? Our sponsor, UGREEN. Their DH4300 00:05:34.200 --> 00:05:40.840 NAS is an all-in-one beginner-friendly storage solution that has up to 120 00:05:38.800 --> 00:05:44.680 terabytes of storage. That's literally millions of photos, files, and videos. 00:05:43.480 --> 00:05:48.680 One nice thing about it is that it's compatible with a variety of third-party 00:05:46.840 --> 00:05:52.600 hard drives, and you can even check their site for compatibility. Setup is 00:05:50.880 --> 00:05:57.560 simple with the UGREEN app. It connects via NFC, and you get access to your 00:05:55.080 --> 00:06:02.200 files across multiple devices. It syncs quickly with Google Drive, so backups 00:05:59.440 --> 00:06:05.720 are very straightforward. And with a 2.5 gigabit Ethernet port, you know you're 00:06:03.920 --> 00:06:09.160 getting high-speed transfers. It also has real-time virus scanning and 00:06:07.520 --> 00:06:13.320 flexible permission management. Grab your DH4300 Plus at the link in the 00:06:11.400 --> 00:06:16.720 video description. I was just curious as to like, what your thoughts on what kind 00:06:15.320 --> 00:06:23.760 of drives we were going to be putting in there. Good question. So, like other 45 00:06:20.480 --> 00:06:25.960 Drives products, this is a a BYO kind of 00:06:23.760 --> 00:06:29.560 situation in terms of the drives that you equip it with. As for what we chose, 00:06:27.800 --> 00:06:32.320 it's probably whatever we had eight of lying around. 00:06:32.720 --> 00:06:38.800 Ah, yes. As advertised, it's a [ __ ] mix. 00:06:36.120 --> 00:06:43.040 Can you do that? Oh, yeah. You guys are running open-source Rocky Linux on this 00:06:40.800 --> 00:06:48.480 thing. So, investment disclosure, invested in HexOS aside, say for an 00:06:46.120 --> 00:06:53.840 example, you could take these two Micron 5300 Pro Enterprise drives. You could 00:06:51.520 --> 00:06:58.400 pop them into two of the bays over here, and run those in a RAID 1. That's like 00:06:55.880 --> 00:07:02.560 super, super safe. If one of these two drives dies, everything is still there 00:07:00.920 --> 00:07:07.240 on the remaining drive. Then, you could take another six drives like these Team 00:07:04.760 --> 00:07:11.400 Group EX2s. You throw them over here, and you could run these in like a RAID 00:07:09.360 --> 00:07:15.600 Z1. So, that would allow you to have one of these six drives fail, and then the 00:07:13.880 --> 00:07:17.560 remaining five would still have all the data. But, if a second one failed, 00:07:17.544 --> 00:07:22.600 >> [music] >> then you're kind of out of luck. It does require you to do a little bit more of 00:07:21.600 --> 00:07:28.360 your own research [music] before deploying something like this, but I think the flexibility is absolutely 00:07:25.880 --> 00:07:31.200 worth it. Also, this is our first chance to have a look at the front. How 00:07:29.400 --> 00:07:34.720 gorgeous is that? All right, let's go ahead and slide these drives in. I am 00:07:32.440 --> 00:07:38.760 liking this drive sled mechanism. Drive goes in, 00:07:36.480 --> 00:07:41.840 little mechanism pops out. It's like a Super Nintendo. It's like a 00:07:40.240 --> 00:07:44.455 do a shot of you blowing on it and putting it in. >> [laughter] 00:07:44.640 --> 00:07:51.880 >> This is something worth noting, though. Plug any storage [snorts] device, 00:07:48.680 --> 00:07:54.360 especially one that is using RAID or one 00:07:51.880 --> 00:07:58.400 that can be configured with RAM as a write buffer into [music] a UPS, an 00:07:56.640 --> 00:08:03.160 uninterruptible power supply with a battery in it. You do not want things 00:08:00.280 --> 00:08:06.240 like this to be unexpectedly powered off. Or like, living out in the middle 00:08:04.760 --> 00:08:11.440 of the woods where every 2 weeks in winter a tree falls over a power line. 00:08:08.520 --> 00:08:15.120 Or also just like, being way too hard, you know? 00:08:13.160 --> 00:08:19.520 And awesome. No, not that kind of hard. Like like hardcore. I learned a very 00:08:17.320 --> 00:08:24.320 hard lesson about the difference between a Cat 5 and a Cat 6 cable at my Red Rock 00:08:22.640 --> 00:08:28.880 show. What were you trying to do over 10 gig? Basically, my delivery system where 00:08:26.440 --> 00:08:34.760 all the music comes out to communicates to OSC, which is the UDP protocol. But, 00:08:31.440 --> 00:08:36.440 on that same network, I also send NDI to 00:08:34.760 --> 00:08:40.120 front of house [music] as a kind of virtual monitors so I can kind of see 00:08:38.039 --> 00:08:44.520 what I'm doing. I didn't have a network cable to go to the router basically that 00:08:42.640 --> 00:08:48.680 went to front of house. I just looked at the back of the telephone in the hotel 00:08:46.240 --> 00:08:53.560 room, and it had an RJ45 in it, so I just stole it. Everything was just kind 00:08:50.320 --> 00:08:55.200 of working, but not, you know, lagging 00:08:53.560 --> 00:08:58.480 and dropping frames everywhere. I'm like, "Dude, this was working fine the 00:08:56.920 --> 00:09:05.000 other day. I don't know what's wrong." And we traced the problem back to the 00:09:01.800 --> 00:09:07.440 RJ45, which was a Cat 5 cable because it 00:09:05.000 --> 00:09:12.840 was used for a telecom system, and I'm trying to send 10 gig down it. 00:09:10.760 --> 00:09:18.520 Might have even been defective, too. You can actually have a 100 megabit link 00:09:15.720 --> 00:09:22.920 even if one of your signaling pairs is damaged. I think the takeaway is is is 00:09:20.880 --> 00:09:27.480 don't steal cables from telephones in hotel rooms. And stop taking the towels 00:09:25.080 --> 00:09:31.800 in the gym at Smash Champs. But, steal the pillows. Take their 00:09:29.040 --> 00:09:35.080 pillow, put it in your pillow shank, and then take your crap pillow, put it in 00:09:33.600 --> 00:09:39.026 their pillow shank. By the time they notice, you're long gone. That is not 00:09:37.160 --> 00:09:43.440 financial advice. No. >> [laughter] >> All right, let's go ahead and fire up 00:09:41.640 --> 00:09:46.640 this NAS. I'll put my thirst extinguisher there just in case Joel 00:09:45.080 --> 00:09:51.160 gets thirsty. I'm okay. Probably the only guy that's ever smoked 00:09:49.160 --> 00:09:56.120 in here, too. Probably, actually. Smoking also not financial advice. 00:09:54.800 --> 00:09:59.400 You know what's kind of crazy is I think this monitor is louder than the system. 00:09:58.280 --> 00:10:02.960 Like it has a bit of coil whine. Hey, there we 00:10:01.400 --> 00:10:07.680 go. This was working the whole time. We just had a bunk monitor. Very nice. I 00:10:06.320 --> 00:10:12.920 don't know what the password is. I'm going to go with 00:10:09.480 --> 00:10:14.640 Type cookie. Deadmau5 is the greatest. 00:10:12.920 --> 00:10:19.920 I understand what people are trying to do by setting like better default 00:10:17.320 --> 00:10:23.400 passwords, but also just don't. I might have found something here. On fresh 00:10:21.560 --> 00:10:34.000 machines, the user is root and the password is 45 big D small R exclamation 00:10:28.960 --> 00:10:34.702 point v e s. Let's try that. Let's go. 00:10:34.000 --> 00:10:39.200 Okay. >> [music] >> 45 drives? 00:10:37.400 --> 00:10:43.217 Don't do that. We have successfully started using the computer the way that 00:10:41.320 --> 00:10:49.040 it is completely not intended to be used [music] like a desktop. Give us a few 00:10:45.480 --> 00:10:51.360 while we log in. Simple setup. We just 00:10:49.040 --> 00:10:56.040 had to get to this point. Okay, best practice storage architecture. We're 00:10:53.200 --> 00:11:00.360 going to set up ZFS for robust storage, Samba for network sharing, and we're 00:10:58.480 --> 00:11:05.200 going to configure our client backups automatically. That's right. 45 drives 00:11:02.760 --> 00:11:08.680 knows that you're going to be a lazy son of a [ __ ] They're going to make sure 00:11:06.480 --> 00:11:13.480 that you run backups on the regular so that [music] it's both on your computer, 00:11:10.839 --> 00:11:17.839 you dumb son of a [ __ ] and also on your NAS like a smart son of a [ __ ] 00:11:15.839 --> 00:11:20.400 All right, server name. Deadmau5 is great. 00:11:18.920 --> 00:11:23.800 He made me do that. Is it going to go Deadmau5 is neat? Is neat? 00:11:23.440 --> 00:11:30.120 Neat. >> what? Your place was pretty tidy. Yeah, I'll give that to you. Okay, password. 00:11:27.440 --> 00:11:34.640 45 big D R exclamation point v e s. That's an 00:11:33.000 --> 00:11:39.600 intuitive password that other people would think of. Don't forget the big D. 00:11:36.720 --> 00:11:43.560 Ooh, network folder name. Linus stuff. Based on the quantity of storage drives 00:11:41.440 --> 00:11:48.160 you installed in the server, we will set up the storage array with a balance of 00:11:45.640 --> 00:11:52.560 capacity, performance, and redundancy. Very nice. So, we've got our 8 TB 00:11:50.640 --> 00:11:57.839 drives. We can see those. And then we've got a different kind of drive that is 00:11:54.400 --> 00:11:59.880 also eight-ish terabytes, but not quite 00:11:57.839 --> 00:12:06.000 as many. Storage will tolerate two disk failures and gives you 41 kibibytes 00:12:02.839 --> 00:12:10.120 usable. So, it is setting up an array 00:12:06.000 --> 00:12:12.360 with all of my drives, but when you set 00:12:10.120 --> 00:12:16.560 up mismatch capacity drives in a single array, you are going to be limited to 00:12:14.200 --> 00:12:19.400 the capacity of the lowest capacity drives in the array. Two disk 00:12:17.640 --> 00:12:23.880 redundancy, RAID Z2. [music] That's a pretty solid recommendation for eight 00:12:21.200 --> 00:12:29.360 drives. Actually pretty impressed. Complete setup. 00:12:25.400 --> 00:12:29.360 Now we give it a minute. Still quiet? 00:12:29.720 --> 00:12:35.240 Silent even. I'm I'm genuinely pretty impressed at the fact that they not only 00:12:34.120 --> 00:12:41.000 don't have any fans in it cuz [music] that's pretty obvious, but it doesn't have any coil whine. Like even that 00:12:38.480 --> 00:12:46.480 crazy computer we had, the like space age Calios, uh no moving parts, it still 00:12:44.760 --> 00:12:51.520 made noise because you could actually hear the the fluid in it boiling. If you 00:12:49.240 --> 00:12:55.240 struggle to hear anything with your head literally pressed up to it, then I think 00:12:54.000 --> 00:12:59.160 that that passes the bar for quiet. 00:12:57.360 --> 00:13:02.760 >> I might just not have very good hearing though. Remember when you like flipped 00:13:00.960 --> 00:13:07.320 out cuz I turned your speakers up too loud and you're like, "Dude, you're going to like >> Oh god. It still keeps me awake at 00:13:05.880 --> 00:13:10.800 night. No, it never made it into the video, but nicest sound system I've ever 00:13:09.600 --> 00:13:16.240 heard. I'm going to turn it up." HE GOES, "WHOA, WHOA, WHOA. This is all so 00:13:13.520 --> 00:13:19.720 finely tuned that you have no idea how loud what you're listening to is, 00:13:17.800 --> 00:13:24.320 brother. I use my ears for a living." I'm like, "Oh, sorry." What's 130 dB 00:13:22.160 --> 00:13:27.839 between friends? Yeah. All right, configuring ZFS storage. Here we go. All 00:13:26.320 --> 00:13:31.200 right, how long does this thing want to do this? It'd be nice if it gave us some 00:13:29.480 --> 00:13:35.320 kind of ETA. We didn't Is it like low-level formatting everything? Uh 00:13:33.000 --> 00:13:40.680 pretty much, yeah. To be clear, it's, you know, doing it pretty fast, but it's 00:13:38.520 --> 00:13:44.440 not that fast. It's SATA. Cuz if we were to go NVMe, all of a 00:13:42.360 --> 00:13:49.480 sudden we're going to need like a bigger motherboard, more expensive PCIe cabling 00:13:47.760 --> 00:13:54.000 everywhere. I can understand why they did it this way, especially because if 00:13:51.000 --> 00:13:56.640 they're targeting like audio creators, 00:13:54.000 --> 00:14:00.000 video creators, you don't need higher than like, you know, 00:13:57.880 --> 00:14:03.160 2 GB a second. And you're only going to do this initial setup, assuming 00:14:01.400 --> 00:14:07.400 everything goes according to plan, one time. This is Man, this is taking a hot 00:14:05.360 --> 00:14:14.280 minute here. And I think just because we went and we put 45 TB of storage in it. 00:14:11.400 --> 00:14:19.160 >> Oh, yeah. That'll do it. Sweet time. Oh, boy. 00:14:15.959 --> 00:14:21.480 4 days later. Yeah, that never 00:14:19.160 --> 00:14:25.680 completed. So, we had to work with 45 drives support, reinstall our ZFS 00:14:23.560 --> 00:14:31.800 package, something something. The point is now it works. We can create a backup 00:14:28.120 --> 00:14:34.400 schedule. Ooh, simple or custom? 00:14:31.800 --> 00:14:38.959 Hourly, daily, weekly, monthly. Okay, we can set a location. We don't have any 00:14:36.000 --> 00:14:43.880 locations yet. Okay, full disclosure. Okay, I am invested in a NAS software 00:14:41.440 --> 00:14:47.640 company to make setting up your own NAS like simpler. I am not trying to make 00:14:45.760 --> 00:14:50.720 this look hard. You guys are watching everything that I'm doing. Wired 00:14:49.480 --> 00:14:53.920 settings. Here is my IP. 00:14:56.000 --> 00:15:00.760 How the hell do I access the web UI? Has anyone done this or did we just get it 00:14:59.120 --> 00:15:04.000 to the point where we fixed what we knew was broken? That's as far as I'm allowed 00:15:02.760 --> 00:15:08.880 to say. I'll try HTTPS. In fairness, this is a 00:15:07.400 --> 00:15:11.800 brand new product that they are evidently still working on the software 00:15:10.680 --> 00:15:17.640 for. Okay. Add server. 00:15:14.480 --> 00:15:17.640 Okay, there. It's there now. 00:15:17.720 --> 00:15:22.680 Permission denied. Okay, well, no, that's a good sign. I swear I'm not 00:15:21.200 --> 00:15:25.760 trying to make this look difficult, man. Did that work? Can I 00:15:24.200 --> 00:15:29.480 I think I might have just reformatted it. It shouldn't have reformatted yet 00:15:27.480 --> 00:15:34.040 because it does that later in the process. No, no, not the storage drives. 00:15:31.880 --> 00:15:37.839 The boot drive. I think I just >> [snorts] >> Yeah, I think I just factory reset it. 00:15:38.200 --> 00:15:43.800 So, this is not a setup for your 45 drives studio. 00:15:41.640 --> 00:15:47.120 Hey, you now have a network attached server that you can start using 00:15:45.079 --> 00:15:51.280 immediately. Houston command center. Okay, the 00:15:48.839 --> 00:15:55.880 Oh, we have to put the port. Username. Let's go. We have hacked the mainframe. 00:15:54.079 --> 00:15:59.959 Limited access mode. Yeah, no, I'm an administrator. Linus is not that the 00:15:57.959 --> 00:16:02.959 incident will be reported. What 00:16:01.760 --> 00:16:07.800 Oh my god. Again. I am not trying to make this look hard. 00:16:05.959 --> 00:16:13.079 I'm just I'm cursed when it comes to Linux. Uh anyway, storage. We can see 00:16:10.600 --> 00:16:18.360 our array here. Current activity. Very cool. Okay, yeah. Any volumes that are 00:16:15.760 --> 00:16:24.360 on each of our physical devices. Pretty nice, concise little storage 00:16:20.120 --> 00:16:27.400 summary. System usage. Ooh. Okay, I love 00:16:24.360 --> 00:16:29.716 buttons in user interfaces 00:16:27.400 --> 00:16:33.640 that exist only so that it can tell you >> [music] >> that you can't do that and doesn't take 00:16:32.040 --> 00:16:38.000 you to any kind of help file and it doesn't take you to like menu where you 00:16:36.040 --> 00:16:41.839 can configure so you are permitted to do that. Text is not underlined in an 00:16:39.959 --> 00:16:45.400 interface unless it's button. [music] Hyperlink rules literally been around 00:16:43.560 --> 00:16:50.000 since the '90s. Sorry, I'm trying not to like rant here. I'm just a little 00:16:47.120 --> 00:16:55.880 frustrated by this experience so far. We should just access it [music] because 00:16:53.120 --> 00:16:59.040 that is 99% of what most people are going to do with a machine like this. 00:16:57.200 --> 00:17:03.040 They're just going to access it. So, go like that, go [music] like that. Here's 00:17:01.120 --> 00:17:05.741 the video. Boom. No, I'm going to have to go to the 00:17:04.439 --> 00:17:13.720 actual share. >> [music] >> Uh okay, let's try Linus 2. Nope. Okay. 00:17:09.839 --> 00:17:15.959 Let's try just actually going into and 00:17:13.720 --> 00:17:19.800 finding out where the stupid folder is. 00:17:17.560 --> 00:17:24.679 File sharing. Failed to initialize the registry. Samba 00:17:22.520 --> 00:17:28.280 smb.conf run test parm [music] to debug. 00:17:28.840 --> 00:17:35.960 This is not the best out of box experience I've ever had. 45 drives, 00:17:33.960 --> 00:17:41.240 love you guys dearly. We can't just like completely ignore that this just didn't 00:17:38.640 --> 00:17:44.480 work. Hold on, there's still maybe something. Click plus to add a share. 00:17:43.280 --> 00:17:50.760 All right, let's do that. Unique name for your share. Linus 2 share. 00:17:47.240 --> 00:17:54.080 [ __ ] I don't know. You tell me. Linus 00:17:50.760 --> 00:17:55.880 2. Path not absolute. I don't even know 00:17:54.080 --> 00:18:00.817 what the root directory you're putting it in is. You just assume I'm a Linux 00:17:57.720 --> 00:18:00.817 wizard. Okay, navigator [music] 00:18:06.920 --> 00:18:14.840 then. Okay, here we go. This is just giving me the whole ass directory for 00:18:11.560 --> 00:18:17.440 Rocky Linux. Where is my array? File 00:18:14.840 --> 00:18:23.040 systems. Here we Boom. {slash} tank {slash} Linus 2. Guest okay. No problem. 00:18:20.960 --> 00:18:26.440 Per file snapshots. Oh, yeah, that's cool. Optimize share for macOS. No, 00:18:25.000 --> 00:18:30.280 don't need that, but it's nice that it's an option. Error in add share. Failed to 00:18:28.600 --> 00:18:34.600 initialize the registry. Not going to lie, a little frustrated at this point. 00:18:32.240 --> 00:18:37.520 To be clear, I and the team here could absolutely fight our way through these 00:18:36.159 --> 00:18:40.840 problems. We could get on the phone with 45 drives. We could go consult some 00:18:39.200 --> 00:18:45.840 documentation. We could figure it out. But that's not 00:18:43.360 --> 00:18:50.919 really who this product is intended for. So, I would like to see 45 drives have 00:18:48.919 --> 00:18:54.159 this software experience cleaned up, made a little bit more reliable, made a 00:18:52.360 --> 00:18:57.360 little bit more intuitive before they go shipping this to 00:18:55.880 --> 00:19:03.040 a video editor, like, you know, content creator, a musician, someone whose 00:19:00.360 --> 00:19:09.720 life is not about, you know, playing around with war {underscore} access 00:19:06.200 --> 00:19:11.320 {underscore} denied smb.conf run test 00:19:09.720 --> 00:19:15.480 parm to debug. That's not their life. That's not their world. They don't want to deal with that. So, I think there's a 00:19:14.040 --> 00:19:20.040 little bit of work to be done. The hardware looks good and the bones of the 00:19:17.720 --> 00:19:23.880 software look good. Just needs a little more polish on the bones, you 00:19:21.480 --> 00:19:29.040 know? Polished bones. Super cool product, man. Not a cheap product. I 00:19:26.600 --> 00:19:33.040 think it's about 3,500 bucks for the system itself and then you obviously 00:19:31.080 --> 00:19:37.800 have to add your drives to it. But if what you're after is something that is 00:19:35.320 --> 00:19:42.640 dead silent, can be high capacity, has no moving parts, therefore can be 00:19:39.400 --> 00:19:44.520 transported, taken with you on the road, 00:19:42.640 --> 00:19:48.800 I can absolutely see the appeal. Yeah, I I I think it hits a good middle between, 00:19:46.679 --> 00:19:51.520 you know, the prosumer and, you know, the full-time creator. 00:19:50.320 --> 00:19:56.640 >> Like that's the thing. It's all about context, right? Like this is expensive, 00:19:54.160 --> 00:20:00.560 but it's not outlandish. You get what you pay for, you know? 00:19:58.440 --> 00:20:04.240 Kind of applies to [music] Thanks for coming on to check this out. 00:20:02.040 --> 00:20:09.440 Thanks for pimping the merch. You look great, by the way. 00:20:06.000 --> 00:20:11.040 Thank you. Subscribe to ShortCircuit. 00:20:09.440 --> 00:20:13.880 Oh, oh, and you can and you can check out the 45 Studio at the link down 00:20:12.880 --> 00:20:19.280 below. Maybe we'll link your we'll link your music down there, too. You know, help 00:20:16.680 --> 00:20:21.600 out a help out a starting out a artist, you know?