WEBVTT 00:00:00.719 --> 00:00:03.979 this seems safe 00:00:04.259 --> 00:00:11.340 okay a few weeks ago I'm browsing Facebook Marketplace and I stumble 00:00:07.980 --> 00:00:12.960 across this a once top of the line 00:00:11.340 --> 00:00:16.080 NetApp storage appliance that would have cost around a hundred thousand dollars 00:00:15.059 --> 00:00:22.260 new for five grand and it gets even better 00:00:19.560 --> 00:00:25.859 we low bulb them offering just a thousand dollars and they said yes 00:00:24.300 --> 00:00:29.480 that's how desperate they were to get rid of this thing which raises some 00:00:27.539 --> 00:00:34.380 interesting questions like why does it even work I didn't follow my 00:00:32.820 --> 00:00:38.640 own advice and actually power it on before we carted it away so for all I 00:00:36.480 --> 00:00:43.379 know it's completely dead and even if it's not dead is it so slow by modern 00:00:41.280 --> 00:00:47.700 standards that it really is only worth one percent of what they originally paid 00:00:46.320 --> 00:00:52.980 for it there's some way that we could 00:00:49.559 --> 00:00:55.440 D proprietaryify this thing and roll it 00:00:52.980 --> 00:00:58.680 as commodity storage Hardware we're going to have the answers to those 00:00:56.640 --> 00:01:03.600 questions and more after this message from our sponsor unbounce engage your 00:01:01.800 --> 00:01:07.320 audience with beautiful high performing marketing campaigns in just a few 00:01:05.159 --> 00:01:12.299 minutes with unbounce's AI powered landing page builder on bounce on over 00:01:09.600 --> 00:01:15.720 to the link below and get up to 35 off for those who missed part one of our 00:01:14.159 --> 00:01:21.000 adventure let's take a quick look at what we've got here a NetApp storage 00:01:17.880 --> 00:01:22.560 Appliance is not that dissimilar to the 00:01:21.000 --> 00:01:26.939 kind of Nas that you would build for yourself just everything about it is 00:01:24.540 --> 00:01:30.960 Enterprise grade instead of having a single box that contains everything 00:01:28.259 --> 00:01:35.820 though it's split out so we've got this box here that contains our brain or our 00:01:33.600 --> 00:01:42.540 controller for the appliance and then this particular configuration has four 00:01:38.939 --> 00:01:46.560 24 Bay disk shelves which are as the 00:01:42.540 --> 00:01:49.380 name implies shelves that hold disks 00:01:46.560 --> 00:01:55.680 these ones in particular have 600 Gigabyte 15 000 RPM SAS drives in them 00:01:53.220 --> 00:02:00.360 and then just power supplies at the back in order to power them but here's the 00:01:57.899 --> 00:02:04.140 thing a hard drive is not very useful without a data connection 00:02:02.280 --> 00:02:10.319 but remember how I said these were SAS you can think of SAS kind of like the 00:02:07.320 --> 00:02:14.940 Enterprise Big Brother of SATA and each of these drives is connected to a back 00:02:12.360 --> 00:02:18.660 plane inside our disc shelf that is then connected to our controller through an 00:02:16.739 --> 00:02:22.440 external cable those of you who have been paying very close attention will 00:02:20.280 --> 00:02:26.340 know that this is almost exactly like our mother Vault server keyword being 00:02:24.900 --> 00:02:30.420 almost unlike the mother vault which only has a 00:02:29.040 --> 00:02:34.319 single controller because it doesn't host Mission critical data this is 00:02:32.700 --> 00:02:40.020 designed for what's called high availability which means that no matter 00:02:36.720 --> 00:02:41.580 what in this configuration fails there 00:02:40.020 --> 00:02:46.080 should be something ready to pick up the slack immediately so that there's no 00:02:44.040 --> 00:02:52.080 interruption to your business and it starts with of course the controller box 00:02:48.360 --> 00:02:54.180 which contains not one but actually two 00:02:52.080 --> 00:02:59.760 separate servers Each of which needs to be connected to 00:02:56.940 --> 00:03:04.620 every single one of these j-bots see like that then there's the j-bods 00:03:02.340 --> 00:03:08.640 themselves which contain redundant power supplies so I could literally rip this 00:03:07.019 --> 00:03:14.640 out mid operation and it would keep working contain redundant controllers so 00:03:12.420 --> 00:03:20.159 I could have a controller failure and every Drive in there would still work 00:03:16.560 --> 00:03:22.200 and even have two separate cables 00:03:20.159 --> 00:03:26.519 connected to every Drive with all that said the reason I got this 00:03:24.599 --> 00:03:31.379 at E-Waste pricing is because it kinda is 00:03:28.800 --> 00:03:37.080 and not just because of its age you see NetApp locks down their systems so that 00:03:34.379 --> 00:03:42.000 you can only use them with drives that have customized NetApp firmware and I'm 00:03:40.560 --> 00:03:45.659 sure they'll tell you that this is for your own benefit in some way but the 00:03:43.980 --> 00:03:49.500 real reason they do this is to ensure that you won't be able to take advantage 00:03:47.519 --> 00:03:54.840 of the ever falling pricing of commodity hard drives and you will have to pay the 00:03:51.480 --> 00:03:57.000 NetApp tax for ever with that said 00:03:54.840 --> 00:04:00.840 though if we abandon the NetApp controller which frankly isn't very 00:03:59.040 --> 00:04:06.299 performant or power efficient these days anyway we should be able to use these 00:04:03.480 --> 00:04:11.040 disk Shelf jbods with practically any server or even a desktop computer which 00:04:09.239 --> 00:04:15.360 makes these things pretty valuable in the home lab Community as a cheap way to 00:04:13.140 --> 00:04:19.380 run a bunch of hard drives all we need is some adapter cables a controller 00:04:17.100 --> 00:04:23.460 server and an HBA to plug into but we're getting ahead of ourselves a 00:04:21.120 --> 00:04:28.320 little bit you see neither Jake nor I has ever gotten a chance to play with 00:04:25.440 --> 00:04:33.060 NetApp anything and despite paying a thousand dollars for the entire get up 00:04:29.699 --> 00:04:35.220 we haven't powered it on so why don't we 00:04:33.060 --> 00:04:40.199 start by taking a look at how it's supposed to run the first thing we'll 00:04:37.919 --> 00:04:43.979 need to do is wire this up properly uh what I did earlier was just for 00:04:41.639 --> 00:04:49.740 illustrative purposes these both need to come out so we'll start by taking the 00:04:46.560 --> 00:04:52.020 leftmost port on each of our servers I 00:04:49.740 --> 00:04:55.860 apologize earlier I referred to these as controllers and they are in a sense 00:04:54.479 --> 00:05:00.600 because they're the controller for the entire storage Appliance but these are 00:04:58.860 --> 00:05:06.560 also SAS controllers so I'm just going to call these servers and these controllers moving forward I plug each 00:05:04.380 --> 00:05:12.720 of these into the two controllers on the top jbod just 00:05:11.639 --> 00:05:18.900 like that then one by one top to top bottom to 00:05:15.900 --> 00:05:20.639 bottom I daisy chain in each of the 00:05:18.900 --> 00:05:25.740 additional controllers then once we reach the bottom jbod we actually Loop 00:05:23.039 --> 00:05:30.780 that one back up around to the servers and the reason for this is that if 00:05:28.560 --> 00:05:36.600 there's a failure at any point in the chain it can just go oh well I'll just 00:05:33.620 --> 00:05:39.840 come at it that way there is four power supplies per disc shelf you technically 00:05:38.520 --> 00:05:46.979 only need to plug in the top and the bottom so that both controllers are powered wow that's loud I hope that 00:05:43.560 --> 00:05:49.620 spins down later yeah she goes 00:05:46.979 --> 00:05:52.800 no power buttons on this oh 00:05:50.880 --> 00:05:56.039 wait is this one bad maybe it's just not plugged in oh wait hold on is it not 00:05:54.539 --> 00:06:00.360 plugged yeah those are the same lights that are bad on the yeah yeah ones that 00:05:58.320 --> 00:06:04.800 are unplugged so okay does it push it in maybe oh no it's in there try the other 00:06:02.699 --> 00:06:07.440 side yeah I'll try the other side oh did you just not turn the switch on oh you 00:06:06.240 --> 00:06:12.180 just didn't turn the switch oh I missed the switch on that one there you go high 00:06:09.840 --> 00:06:15.900 defense it took you a minute to see that switch too it's right under the thing 00:06:13.680 --> 00:06:18.539 well I mean in my defense you were flipping all the other switches it'd be 00:06:17.400 --> 00:06:23.220 kind of weird to miss them I can't really serial into both of these at the same time so I'm hoping one is enough 00:06:21.479 --> 00:06:27.600 you think the top one is the primary good thing all right let's try that the 00:06:25.500 --> 00:06:32.639 only link lights that are not illuminated are the ones that are coming 00:06:30.240 --> 00:06:36.180 straight from the servers if it's not booting up that makes sense I also don't 00:06:34.259 --> 00:06:40.199 know does it need boot drives did they take boot drives out in theory we should 00:06:38.220 --> 00:06:44.160 have cereal even at the BIOS so let's try that I guess okay it looks like it's 00:06:42.240 --> 00:06:48.960 doing things nvrd one I'm assuming that's like the non-volatile dim 00:06:45.539 --> 00:06:50.639 interface e5a e5b does not exist were 00:06:48.960 --> 00:06:54.840 all those management ports plugged in it wasn't in their server room anymore so 00:06:52.620 --> 00:06:58.740 they wouldn't be nothing plugged in here I really don't know if it needs boot 00:06:56.940 --> 00:07:05.039 drives oh hey look here's all the instruction manuals they still have them on their website oh my god wow baby's 00:07:03.000 --> 00:07:08.340 first storage cluster data for seven mode 00:07:06.000 --> 00:07:11.520 10 gig Ethernet ports so that makes sense we have those plugged in between 00:07:09.720 --> 00:07:16.199 we have our SAS ports that's right connect gig ports blah blah blah to Gig 00:07:14.039 --> 00:07:21.660 Data Network switches okay all power cords must be used for all units yeah 00:07:19.199 --> 00:07:26.460 whatever what's the point of even having a manual okay so the whole thing has to 00:07:24.000 --> 00:07:32.280 be Daisy chained every single jbot so the farthest drives from the actual SAS 00:07:30.180 --> 00:07:36.120 controller it's just because if one connection dies or like something goes 00:07:34.380 --> 00:07:42.000 wrong the connection can come back the other way okay well we can fix that uh 00:07:39.000 --> 00:07:43.680 let's flip the power switch okay 00:07:42.000 --> 00:07:52.139 now we get to do it all over again with Ethernet ah yes the locked wrench Park transport 00:07:47.699 --> 00:07:55.139 to the first ones ah good quite I 00:07:52.139 --> 00:07:57.720 screwed up one of mine what uh it goes 00:07:55.139 --> 00:08:01.560 top to bottom then bottom to top so I just gotta do a quick uh switchy boo 00:07:59.819 --> 00:08:05.520 here okay those are Blinky that's good oh wait what how did I end up oh God 00:08:03.780 --> 00:08:10.139 we're still not getting a link light back to the server well it's not booted 00:08:07.620 --> 00:08:13.680 so ah oh the link lights are up it's doing stuff yeah something is happening 00:08:11.940 --> 00:08:18.300 now deliver monitor take over disabled blah blah blah it's doing things but 00:08:15.360 --> 00:08:21.960 these controller nodes each have a two Port 10 gig card in there we didn't 00:08:19.979 --> 00:08:26.340 account for that in our like money oh yeah those are worth like 50 100 bucks 00:08:24.240 --> 00:08:30.240 each yeah I think we did pretty well here in spite of the fact that they 00:08:27.900 --> 00:08:35.399 ended up telling us after the fact that the five thousand dollar listing was a 00:08:31.919 --> 00:08:38.159 typo it had intended 500 dollars system 00:08:35.399 --> 00:08:41.459 was down for 5.3 million seconds what the hell is that not saying that was the 00:08:39.779 --> 00:08:46.200 last time it was on well no I oh it's Blinky it's got internet even oh my God 00:08:43.860 --> 00:08:51.660 what is the login install and run system setup software oh register and get your 00:08:49.440 --> 00:08:55.680 license Keys maybe you can download this part of it we could maybe be able to 00:08:53.880 --> 00:09:00.720 download the system setup one but anything further than that I doubt 00:08:57.899 --> 00:09:06.180 download system set of 3.1 or later 2015 was the last time this was updated oh no 00:09:04.500 --> 00:09:10.980 we wanted to check the power consumption because 60 terabytes or whatever what 00:09:08.640 --> 00:09:14.339 does it work out to Yes it really it's only 60 terabytes yeah and you don't 00:09:12.839 --> 00:09:19.200 actually get all of it some of the capacity I think minimum three discs 00:09:17.279 --> 00:09:23.820 have to be used for each node to host their OS so the reason it wouldn't turn 00:09:21.420 --> 00:09:28.140 on after talking to lead eater on the Forum is one of our form admins shout 00:09:25.500 --> 00:09:32.100 out red eater the OS is stored on the array if you move the disc shelves 00:09:30.240 --> 00:09:38.040 around and change the cables and move the discs around 00:09:33.680 --> 00:09:39.839 yeah okay fine 45 terabytes whatever the 00:09:38.040 --> 00:09:44.339 capacity ends up being that's not a bad thing you know I 00:09:42.000 --> 00:09:50.040 wouldn't mind you know tens of terabytes of storage but at what cost these days 00:09:47.820 --> 00:09:55.200 you could get literally two hard drives and that would be a 00:09:52.200 --> 00:09:57.060 total of what like 15 20 watts yeah the 00:09:55.200 --> 00:10:01.740 cost of running this compared to buying two or three new hard drives this takes 00:09:59.459 --> 00:10:04.680 a while to turn off yeah it is off sort of it shuts off the OS and it goes back 00:10:03.660 --> 00:10:10.680 to the loader which is like the bootloader menu and I guess that's as off as it goes and then you just click 00:10:08.940 --> 00:10:16.019 click the button I guess so yesterday trying to get it set back up cleared the 00:10:13.440 --> 00:10:19.920 config and initialized all the discs which is just one command but that means 00:10:17.700 --> 00:10:25.620 it has to zero every single disk and since this is on an old operating system 00:10:21.839 --> 00:10:27.480 it zeroed like sequentially and did that 00:10:25.620 --> 00:10:31.320 overnight sure oh here's the other thing if you update it from the older version 00:10:29.940 --> 00:10:35.760 to the newer version faster row doesn't work you have to fresh install in theory 00:10:34.200 --> 00:10:39.600 this one can be updated to a version that has pass zero but we can't download 00:10:37.800 --> 00:10:43.560 the software because we don't have a license I emailed them and said hey we 00:10:41.580 --> 00:10:48.180 bought this from X company but they said oh you didn't purchase it from NetApp so 00:10:45.540 --> 00:10:52.800 we can't give you access so it literally is e-waste basically 00:10:50.279 --> 00:10:59.300 all I'm saying is it should be illegal to sell Hardware that requires software 00:10:55.440 --> 00:10:59.300 that you need an account to access 00:11:00.000 --> 00:11:10.860 all right let's go three amps a 208 volt whoa holy crap 00:11:07.560 --> 00:11:13.860 it's drawing 15 1600 Watts right now 00:11:10.860 --> 00:11:15.300 eight freaking amps for one year it will 00:11:13.860 --> 00:11:21.000 cost us two thousand dollars in electricity here where electricity is 00:11:17.579 --> 00:11:24.060 like 13 cents a kilowatt Canadian which 00:11:21.000 --> 00:11:26.160 is like 10 cents a kilowatt U.S so six 00:11:24.060 --> 00:11:30.779 grand a year in California 10 grand a year in Europe oh look at how like 00:11:28.260 --> 00:11:35.640 archaic that PCB is on the back well yeah it kind of looks like carbon fiber 00:11:32.880 --> 00:11:39.480 oh man look at that that is just like industrial AF we're not going to destroy 00:11:37.980 --> 00:11:43.740 all these drives if somebody in the comments you want them for your NetApp 00:11:41.940 --> 00:11:47.279 and you live locally and you want to just come pick them up and take them out 00:11:45.240 --> 00:11:50.820 of all of these trays maybe you can have them well NetApp is on now do you want 00:11:49.140 --> 00:11:54.779 to take a quick look at it I do this is quite uh the journey to get working so 00:11:52.860 --> 00:11:58.500 after I installed and zeroed all the drives I booted up the second node which 00:11:57.000 --> 00:12:02.600 was still crashing and had to do the same thing luckily it only zero to three 00:12:00.540 --> 00:12:06.600 drives and it took like an hour we got old school cool bottom and top 00:12:04.920 --> 00:12:11.640 once you set up the cluster on the first node after it's reinstalled itself you 00:12:09.060 --> 00:12:14.760 can then reinstall the second node join that to the cluster but wait it's not 00:12:13.019 --> 00:12:18.660 high availability yet you have to go in and like type a command that allows it 00:12:17.220 --> 00:12:23.160 to be high availability like turn High availability on otherwise it's just two 00:12:20.760 --> 00:12:27.060 separate notes So in theory now both nodes can perform takeover on each other 00:12:24.779 --> 00:12:30.839 it used to be that you needed a base license to even use the software at all 00:12:29.040 --> 00:12:38.399 they've changed that so you can install it but to do basically anything 00:12:34.079 --> 00:12:40.440 sifs like SMB NFS iSCSI you need a 00:12:38.399 --> 00:12:43.500 feature license and NetApp won't give it to me because we're not the owner yeah 00:12:42.000 --> 00:12:46.980 basically right now this is just an expensive storage device that you can't 00:12:45.180 --> 00:12:50.220 really put anything on as far as I can tell because here like I made a 00:12:48.240 --> 00:12:54.480 aggregate which is like a pool and then I made an SV honestly I was about right 00:12:52.260 --> 00:12:58.079 we only have 45 terabytes of actual addressable space which is a storage 00:12:56.279 --> 00:13:01.860 virtual machine you go to edit and I want to turn on sifts which is SMB okay 00:13:00.120 --> 00:13:05.220 and it's just grayed out you can see the cluster based license is deprecated but 00:13:03.480 --> 00:13:08.160 all of these other things you want to use any of these features you need a 00:13:06.899 --> 00:13:15.959 license because we didn't buy it from them or a reseller oh hey look a hard drive look how small the platter is 00:13:13.139 --> 00:13:20.880 so the reason for that is that a smaller platter actually gives you faster seek 00:13:18.240 --> 00:13:25.019 times because the ARM doesn't have to move as far to find the correct track 00:13:23.040 --> 00:13:29.459 that's one of the reasons that these high performance SAS drives in 00:13:27.000 --> 00:13:35.160 appliances like this used smaller disc platters the bigger the platter gets the 00:13:32.040 --> 00:13:37.620 more actual area that is after all of 00:13:35.160 --> 00:13:42.120 that work to get this thing to work it still doesn't really work let's do what 00:13:40.260 --> 00:13:45.240 we intended to do then and try and repurpose this Hardware okay cool I get 00:13:43.920 --> 00:13:50.339 to run that fun really long command again to turn it off classic Jake 00:13:47.700 --> 00:13:53.700 see you later and the like condescending attitude of the people who have told me 00:13:51.959 --> 00:13:58.740 how stupid I am over the years for not buying one of these yeah nothing we have 00:13:56.639 --> 00:14:03.000 is that mission critical especially when the cost is so high that you could 00:14:00.899 --> 00:14:06.079 literally hire a person to come in and deal with it for you 00:14:06.480 --> 00:14:14.040 after your hand whoa I forgot about the handles 00:14:10.459 --> 00:14:15.600 hey hey how you doing yeah this is the 00:14:14.040 --> 00:14:18.959 most junk part of the whole thing I think easily worth the thousand bucks 00:14:17.579 --> 00:14:24.839 right here even if we just give them away at the Christmas party 00:14:22.560 --> 00:14:29.399 and then what did you have in mind for a replacement 00:14:26.839 --> 00:14:33.180 what now we're gonna put old wanak in there oh my God what is it like dual 00:14:31.320 --> 00:14:38.760 high performance 32 course or is that one dual 64 7702 64 cores okay I don't 00:14:37.500 --> 00:14:42.959 know if this is ever what liquid intended this thing to be but um no I 00:14:40.980 --> 00:14:47.220 think they really didn't intend for hard drives the first thing you're going to 00:14:45.420 --> 00:14:51.600 need to make a disc shelf like this work with a different computer is an HBA or 00:14:49.740 --> 00:14:55.139 host bus adapter this is effectively just a storage controller on a PCIe cart 00:14:53.820 --> 00:15:01.620 like what would be on your motherboard just separate this one is a 9305 16 I 00:14:59.399 --> 00:15:04.860 the eye is standing for internal you can see that these are internal connectors I 00:15:03.300 --> 00:15:08.639 see the problem here this is not what you should buy you should buy one that 00:15:06.360 --> 00:15:12.120 ends in e for external which has the proper external mini SAS HD connectors 00:15:11.040 --> 00:15:19.500 we just had a bunch of these laying around and startech makes these internal to external adapters so this is really 00:15:16.680 --> 00:15:24.060 janky it's not that bad okay it's it's not that great 00:15:21.480 --> 00:15:28.680 Enterprise grade Hardware that literally looks like someone hand soldered the 00:15:25.800 --> 00:15:32.100 wires onto the PCB I mean why have a housing and a connector when you can 00:15:30.180 --> 00:15:34.980 just do this and put hot glue over it you'll notice this card has four 00:15:33.420 --> 00:15:38.519 connections and we have two of these adapter things that's because we have 00:15:36.540 --> 00:15:42.420 four disc shelves you could Cascade them and have one cable that goes to all of 00:15:41.160 --> 00:15:45.660 them I don't really have the right cable actually no we could reuse them could 00:15:44.339 --> 00:15:50.639 you reuse it it's slower to do that though yes we would rather have more bandwidth this means we have a full 00:15:48.600 --> 00:15:55.680 connection to each of them I maintain it won't matter for the use case for the 00:15:53.940 --> 00:16:01.500 use case where you're going to be more limited by your random i o re-silver 00:15:58.680 --> 00:16:04.860 replacing a disc okay In fairness to you this ended up being less stupid than I 00:16:03.480 --> 00:16:10.139 expected yeah it's really not that bad get kick hey hey hey hey hey hey kick 00:16:07.800 --> 00:16:16.680 just stop kicking stop the one that we got uses iom 3 controller modules those 00:16:13.740 --> 00:16:21.600 are SAS three gigabit luckily you can buy iom 6 modules which are SAS 00:16:19.560 --> 00:16:25.980 six gigabit which doubles our throughput uh how much money did we waste on those 00:16:23.639 --> 00:16:29.519 20 bucks oh they're 20 bucks each wow that's cheap and we technically only 00:16:27.060 --> 00:16:35.279 need one as far as I'm aware the good news is that the upgrade process is as 00:16:32.519 --> 00:16:40.560 simple as oop so I'll pull out old ones you put in new ones yeah 00:16:38.060 --> 00:16:44.639 upgraded beautiful now we have double the bandwidth double the throughput 00:16:42.360 --> 00:16:49.019 these are qsfp which is what the NetApp uses too many SAS HD which is like the 00:16:47.100 --> 00:16:54.180 modern external SAS cable I don't know if anything other than these use qsfp 00:16:52.320 --> 00:16:57.660 because this is usually a network cable connector like for 40 gig or 100 Gig 00:16:56.040 --> 00:17:03.600 networking yeah I mean in theory it's anything that needs a lot of pins 00:17:01.440 --> 00:17:08.459 handle feels like it's not strong enough it really does it's flexing so hard not 00:17:06.240 --> 00:17:12.780 as hard as I'm flexing man hold on the plastic thing who cares about the 00:17:10.439 --> 00:17:15.839 plastic power cable no I just it might have interfered with that oh it would 00:17:14.339 --> 00:17:19.740 have been fine it might not have been things like 100 pounds Linus actually 00:17:17.939 --> 00:17:23.400 dropped one of these oh my God a foot off the ground onto pavement and all the 00:17:22.319 --> 00:17:31.620 drives still work seemingly wow wiggle while you work 00:17:27.740 --> 00:17:33.720 look at how mint that is Buddy I mean 00:17:31.620 --> 00:17:38.100 from this side it's mint I really hope this just works I don't think it's gonna 00:17:35.760 --> 00:17:42.120 just work really why wait for Jake when I can just turn it on myself food failed 00:17:40.080 --> 00:17:47.640 booting from Debbie just give it a second oh okay I just didn't change the 00:17:43.679 --> 00:17:49.919 boot order oh no my 100 useless capacity 00:17:47.640 --> 00:17:56.100 High wattage drives aren't all detected oh no oh I think we only got one shelf 00:17:53.640 --> 00:17:59.700 yeah we have one okay how do we know which one it is though oh I have no idea 00:17:58.080 --> 00:18:04.080 do an identify thing on the thing and I'll tell you what light flashes 00:18:01.559 --> 00:18:08.880 show me an Access let's go hey it's the top one are they all on yep 00:18:06.780 --> 00:18:13.200 all good I want to point out that as much as we're mocking the power 00:18:10.140 --> 00:18:15.240 efficiency of the original setup only a 00:18:13.200 --> 00:18:19.559 small part of the problem was the server itself and now that we're running a new 00:18:17.280 --> 00:18:24.600 server that's not a problem at all also the power efficiency of these disc 00:18:22.260 --> 00:18:29.580 shelves is only a problem if the capacity is super low if we were to put 00:18:27.419 --> 00:18:32.940 22 terabyte drives in this thing obviously these power supplies aren't 00:18:31.620 --> 00:18:38.820 quite as efficient as something modern you know 80 plus titanium would be but 00:18:35.700 --> 00:18:40.799 your energy usage per capacity would 00:18:38.820 --> 00:18:44.940 actually be much more reasonable and could even be worth the cost savings if 00:18:42.720 --> 00:18:50.880 you were trying to set up a very low cost bulk storage solution for 00:18:48.720 --> 00:18:55.080 a small business honestly if something like this had existed back when we 00:18:52.559 --> 00:18:59.220 started just cheap j-bod disc shelves like this I would have totally gone this 00:18:57.299 --> 00:19:03.080 route they existed they just weren't low cost hey some of these drives are 00:19:01.260 --> 00:19:09.000 different capacity 556.29 and 555.63 that actually makes 00:19:06.960 --> 00:19:14.280 sense because some of them are the two and a half inch replacement drives and 00:19:11.880 --> 00:19:19.080 they would be ever so slightly different even though they're both 600 gigabytes 00:19:16.080 --> 00:19:20.460 failed to wipe disk invalid argument I 00:19:19.080 --> 00:19:23.940 mean that's the whole point of their locked off firmware BS but why would 00:19:22.500 --> 00:19:28.400 they care if you put these discs into something else because 00:19:26.580 --> 00:19:33.900 see you later buddy knock to addition screwdriver coming 00:19:31.440 --> 00:19:38.940 soon you can sign up for an in-stock notification on lttstar.com two 00:19:35.820 --> 00:19:40.440 colorways this is interesting the two 00:19:38.940 --> 00:19:44.160 and a half inch drives have a little adapter magic oh it's just a height 00:19:42.299 --> 00:19:50.039 adapter they've got a screw in from the bottom I have a thing for that hey oh 00:19:47.820 --> 00:19:55.080 interesting this is an interposer we don't need these a 00:19:53.280 --> 00:20:00.600 benefit of using an interposer like this is that you can use sas-ish signaling up 00:19:58.980 --> 00:20:03.720 until the interposer and then it converts to say to right at the drive 00:20:02.100 --> 00:20:07.440 and this has the added benefit of allowing both controllers to see the 00:20:05.280 --> 00:20:12.720 drive which is super cool but the thing is most SAS controllers can read SATA 00:20:11.280 --> 00:20:16.140 drives it doesn't work the other way around you cannot run a SAS drive on a 00:20:14.880 --> 00:20:22.320 SATA controller well without an interposer at least you cannot but the point is we don't need an interposer to 00:20:19.919 --> 00:20:26.460 read these drives necessarily it just is a little better one thing that's a 00:20:24.240 --> 00:20:30.419 little bit confusing are there two separate mounting hole there are there's 00:20:28.919 --> 00:20:36.179 two separate mounting holes on these sleds because they are interposer ready 00:20:33.200 --> 00:20:40.140 wow that's pretty cool we don't have that many spare drives right now but the 00:20:38.220 --> 00:20:44.640 drives that we're going to be using 22 terabytes it's still only detecting 25 00:20:41.940 --> 00:20:48.179 discs McCall Wendell uh hello hello is this level one tech support well 00:20:46.440 --> 00:20:52.200 technically he's level two so we got the death those disc shelves 00:20:50.220 --> 00:20:59.419 set up they're all into the same HBA and it only seems to detect one of them 00:20:55.200 --> 00:20:59.419 es yeah the one it detected is four 00:21:11.220 --> 00:21:16.640 I have a 9305 16i HBA that's what they're plugged into 00:21:20.460 --> 00:21:26.280 the IDS maybe it's just mad because the IDS aren't sequential I think 00:21:24.900 --> 00:21:29.580 you are hitting the button on the front Wendell suggested that part of our 00:21:27.900 --> 00:21:34.140 problem might be these disc shelves complaining about having 15 000 RPM 00:21:31.919 --> 00:21:38.880 drives in them with only two of the power supplies plugged in because 00:21:37.140 --> 00:21:42.059 I see so much more power it'll force you to use staggered startup and you gotta 00:21:41.159 --> 00:21:46.500 have three out of the four power supplies for 15K so we are trying to 00:21:44.700 --> 00:21:51.419 plug in a third power supply for each of our shelves to see if this resolves this 00:21:48.600 --> 00:21:55.919 just weird issue where the top one is detecting drives but the other three are 00:21:52.919 --> 00:21:58.260 not clear SCS util show it still just 00:21:55.919 --> 00:22:00.679 shows the one it's only detecting seven drives 00:22:01.260 --> 00:22:06.419 all the lights are up on the front there was some kernel messaging happening when 00:22:05.220 --> 00:22:11.400 we were unplugging and plugging in enclosures which makes me think that things are happening but it really just 00:22:09.960 --> 00:22:15.299 wasn't detecting anything like you run SES util and it still would only show 00:22:13.380 --> 00:22:19.200 the one enclosure after talking to Wendell for a while it's become pretty 00:22:16.799 --> 00:22:23.520 clear that regardless of how we had this thing hooked up directly to each disc 00:22:21.240 --> 00:22:27.539 shelf or into one and cascaded down to the others this should just work there 00:22:25.980 --> 00:22:32.100 isn't really any config that needs to happen to make this work and it turns 00:22:29.700 --> 00:22:36.360 out it should have been Wendell's setup at home is running Rocky Linux which is 00:22:33.960 --> 00:22:40.799 different than FreeBSD which is what trunass core is based on on the off 00:22:38.820 --> 00:22:44.880 chance that it might work we decided to upgrade to trunass scale which is 00:22:42.539 --> 00:22:50.100 actually based on Linux and as soon as it turned on I immediately saw all the 00:22:47.520 --> 00:22:53.760 drives start populating so I guess it's an issue with true Nas core which is a 00:22:52.080 --> 00:22:57.240 little bit ironic because I specifically chose that thinking that it would be 00:22:55.200 --> 00:23:01.020 more reliable and better suited for this and it turns out it is not the weird 00:22:59.039 --> 00:23:05.460 thing is they show as disc size zero I think it's because of the weird sector 00:23:03.659 --> 00:23:11.159 size these drives with a special NetApp firmware use a 520 byte sector size 00:23:08.039 --> 00:23:12.840 which is not standard for most computers 00:23:11.159 --> 00:23:16.860 but it does turn out you can change them I'm running it on this one right now 00:23:15.179 --> 00:23:20.640 it's probably been going for like 10 minutes already and it's at 45 or 00:23:18.900 --> 00:23:25.140 something like that you can do multiple at a time so it's not going to take like 00:23:22.500 --> 00:23:28.080 a week to do all of these drives but I'm also not gonna do all these drives 00:23:26.580 --> 00:23:31.440 they're really not that useful for us I just wanted to demo it on one so we'll 00:23:30.000 --> 00:23:34.980 see when that's finished and see if it works but in the meantime why don't we 00:23:33.179 --> 00:23:38.039 throw in these 22 terabyte drives I grabbed eight of them and set them up on 00:23:36.480 --> 00:23:42.840 the trays with the interposer so we can do two per disc shelf the other thing 00:23:40.860 --> 00:23:48.240 that's important about this while you can use SATA drives with these disc 00:23:45.120 --> 00:23:50.580 shelves when you have SATA drives and 00:23:48.240 --> 00:23:54.240 SAS drives on the same backplane it's really not recommended because the 00:23:52.320 --> 00:23:58.980 voltage level is different between SAS and SATA so using interposers in a mix 00:23:56.460 --> 00:24:02.220 setup like this is very recommended I'm not even going to try and put just to 00:24:00.840 --> 00:24:06.179 say to dry in here because I don't want to damage anything 00:24:03.960 --> 00:24:10.020 oh luckily I have this like server shelf here when I set up my server at home I 00:24:08.580 --> 00:24:14.580 really wanted to get one of these disc shelves but they're like particularly in 00:24:12.299 --> 00:24:21.539 Canada it's like oh 300 bucks on eBay plus 700 shipping like what they're 00:24:19.320 --> 00:24:24.960 blinking that's a good sign let's go see if it works it takes a sec for them to 00:24:23.520 --> 00:24:28.980 populate but I can already see the number it's increasing around 87.88 00:24:27.000 --> 00:24:35.820 there's another one popping up this is still going 45 eight percent hey 00:24:32.220 --> 00:24:37.140 two three four five six seven eight hey 00:24:35.820 --> 00:24:41.520 look at that plus we have a direct connection to each jbod which means we 00:24:38.880 --> 00:24:45.600 have like not 48 that would be 12. we have 24 gigabit to each disc shelf which 00:24:43.919 --> 00:24:49.140 is two and a half gigabytes a second something like that which is more than 00:24:46.919 --> 00:24:53.520 two drives we'll do hey look it works there we go okay manage devices look at 00:24:51.539 --> 00:24:56.520 that all that's left to do is create a data set and then a share so we can 00:24:55.080 --> 00:25:02.820 access it I'm going to change it also to Z standard compression we have a lot of 00:24:58.679 --> 00:25:03.960 CPU in This Server 128 epic cores and 00:25:02.820 --> 00:25:10.860 that's just gonna serve to make our discs go faster so there's really not really a lot of downside I heard we 00:25:07.799 --> 00:25:12.780 switched to True now's scale yup how 00:25:10.860 --> 00:25:18.360 often have you started on core lately for the better reliability and more 00:25:15.780 --> 00:25:22.320 maturity and then ended up on scale I don't know what it is core very much 00:25:19.740 --> 00:25:25.980 seems to be built for like IX systems which is a company that makes true Nas 00:25:23.580 --> 00:25:30.720 yeah the hardware that they sell these days and scale you know it's Linux it 00:25:29.460 --> 00:25:35.820 kind of just works with everything and sure enough as soon as we booted it up it was like wow look at all these discs 00:25:33.659 --> 00:25:38.940 really that easy right now I'm just plugging in that test Bench way the hell 00:25:37.200 --> 00:25:43.500 over there to 10 gig so we can like do a file transfer I called it the pool is 00:25:41.820 --> 00:25:48.419 called sort of slow this is Wi-Fi oh and then the data set 00:25:46.679 --> 00:25:53.340 is sort of fast we're directly connected to the server over there via 200 foot 00:25:50.900 --> 00:25:57.539 cat68 cable now to this workstation which has a 10 gig Nick in it we have 00:25:55.020 --> 00:26:00.960 two 22 terabyte hard drives in each it should be able to hit about a Gigabyte 00:25:58.980 --> 00:26:06.419 so it should be fine okay wow that's reading from it immediately 00:26:04.260 --> 00:26:08.760 1.1 gigabytes a second it just saturated a 10 gigabit link 00:26:08.220 --> 00:26:11.839 yeah yeah 00:26:12.620 --> 00:26:17.340 okay 600 megabytes a second I mean it 00:26:15.659 --> 00:26:21.059 did like five gigs before it slowed down that's probably just a little bit of RAM 00:26:18.840 --> 00:26:25.020 caching there is nothing to be too concerned about this is a video file as 00:26:23.220 --> 00:26:28.140 well so it's not compressible so even though we have compression enabled over 00:26:26.400 --> 00:26:32.700 there it's really not doing anything if we were to copy a bunch of big Word 00:26:29.940 --> 00:26:38.220 documents or big spreadsheets yeah gold it's worth noting that even though we 00:26:34.740 --> 00:26:41.159 got a great deal on these Drive shelves 00:26:38.220 --> 00:26:45.840 if all you need is a hundred terabytes of storage or less you don't need to do 00:26:43.860 --> 00:26:49.919 any of this stuff with a basic consumer motherboard and consumer chassis you can 00:26:48.120 --> 00:26:54.360 do anywhere from four to eight hard drives pretty easily and spend a 00:26:52.320 --> 00:26:58.919 fraction of what we did here and just direct attach them all it'll work just 00:26:56.700 --> 00:27:03.799 as well with the free or inexpensive software we already mentioned and you 00:27:00.900 --> 00:27:07.980 don't have to deal with the noise of an enterprise-oriented solution that being 00:27:05.940 --> 00:27:11.820 said if you do want more capacity like this I'm one of those people getting one 00:27:10.380 --> 00:27:15.720 of these disc shelves you can probably find one on eBay if you're lucky for two 00:27:13.860 --> 00:27:19.440 three hundred bucks maybe even with the new modules you need an HBA which you 00:27:18.120 --> 00:27:24.659 can buy Chinese ones for a couple hundred bucks and then a cable that's 00:27:21.720 --> 00:27:27.960 basically it yeah and your drives and you're ready to hang out on our slash 00:27:25.919 --> 00:27:31.679 data hoarders yeah assuming that subreddit is still up these days you 00:27:30.480 --> 00:27:35.240 know what is up the Segway 00:27:33.539 --> 00:27:39.600 to our sponsor delete me your personal information is 00:27:38.159 --> 00:27:44.640 out on the web being passed around between companies like hors d'oeuvres at 00:27:41.760 --> 00:27:48.600 a fancy party and it's time to stop With a Little Help from delete me delete me 00:27:46.740 --> 00:27:52.679 will help you find and remove hundreds of online profiles sharing your personal 00:27:50.279 --> 00:27:56.640 info so it can't be used by spammers scammers and even Slammers I don't know 00:27:54.900 --> 00:28:00.659 what those are but they sound bad in more extreme cases Bad actors having 00:27:58.679 --> 00:28:05.039 your data could lead to identity theft or fraud removing all of this 00:28:03.120 --> 00:28:09.179 information by yourself would be a huge task to take many hours but with delete 00:28:07.080 --> 00:28:14.039 me software and team of experts it can be done in minutes on average delete me 00:28:11.700 --> 00:28:17.340 finds and removes over 2 000 pieces of data for a customer in their first two 00:28:15.720 --> 00:28:20.400 years so if you want to get your personal information removed from search 00:28:18.840 --> 00:28:26.220 results on the web go to join deleteme.com Linus techtips and use code 00:28:23.340 --> 00:28:30.000 LTT for 20 off okay if you guys enjoyed this video I think the best one to go 00:28:28.140 --> 00:28:36.500 check out is setting up the mother Vault these are so quiet 00:28:32.400 --> 00:28:36.500 you can have that under your bed no