 One of the things that you learn if you use Linux long enough is that sometimes Linux breaks. It just is the nature of the beast. And honestly, if you use Linux long enough, sometimes you think Linux just kind of hates you because usually when things go wrong, they go wrong really badly, and they go wrong for a significant portion of time, like things just kind of snowball and things happen over and over again. And a lot of that is because when something goes wrong and then you end up having to like distro hop or something like that, you're going to be setting up a lot of new stuff. And when you're sitting around, when you're setting up a lot of new stuff, chances are you're going to be tinkering with stuff. And when you're thinking we're stuff, things break. So there's a good chance on your new install, things are also going to break, which is going to cause you even more, you know, angst. And it's just, you know, a repeating cycle of horribleness that sometimes it just makes it feel like Linux hates you. And that's where I'm at today. So if you've been paying attention to the channel, you'll know that I failed the six month Linux challenge. I was challenged to use Redcore for six months. I made it for three. And then weird things happened, right? Most of it, if not all of it was a skill issue. And chances are everything that I talk about today is a skill issue. There is probably definitely someone out there who knows way more than I do that could have fixed the problems that I've had on Linux over the course of the last two or three weeks. But I can't be those people. I can only have the skills that I have and learn what I can learn. So, you know, I just have to do the solutions that I can do. So that was some really good, you know, grammarly gymnastics there, Matt. It was fantastic. I'm sure everybody understood exactly what you meant to get across to get disgraceous. Anyways, the point is, it's going to be one of those days. Anyways, let's move on to the rest of the video, Matt. You can do this. You've done this like 600 times. You can definitely make a video. So anyways, I failed the six month Linux challenge. So I stopped using Redcore and I decided I was going to move to arch. So the first arch that I installed was archcraft, which is an arch based distro. And I chose that simply because that was the most recent ISO of an arch based distro that I had. I didn't have any vanilla arch isos laying on hand. And I didn't have any like Arco Linux that were recent, the last Arco ISO that I had on hand was one released last year. So I went with the archcraft ISO that I had on hand installed it and got all my stuff set up and was fairly happy was, you know, it was disappointing that I didn't finish the challenge. But, you know, it was just time to move on because of various reasons. I used archcraft for approximately four days. And then something weird happened where I updated arch restarted as you should when there was a kernel update, because there's always a kernel update. And I, you know, booted back in and it took me right to a TTY, which is never a good sign because that means your display manager didn't, you know, boot up. So I tried to sign in with a TTY and it would not accept my password. Now, I can, if you watch my channel at all, you guys know that I can't type worth a damn, right? I type horribly a lot, right? It's just kind of, it's become a meme, right? So I just figured, well, I mistyped my password, right? Of course, that's what I thought. So I re-typed the password. And again, it wouldn't accept my password. And I did this over and over again until Pamlock apparently, you know, got sick of it and froze me out. Now, I had no clue that Pamlock, the fail lock thing in Pam was a thing at that point. I only learned that recently. But probably what happened was I mistyped my password three times there in archcraft, got locked out for 10 minutes, didn't realize that that was even a thing and just decided to screw it. I'm hopping away from archcraft. You'll never hear anybody say that patience is my virtue. I have very, very little patience for literally anything, most of the time. So when I couldn't log in, and again, I didn't know that the fail lock thing was even a thing. I hopped from archcraft to vanilla arch. I went and downloaded a vanilla arch ISO on my laptop, put it in Ventoy and installed vanilla arch. And I was using that for a few days. And I'm actually not sure what happened to that install. I can't even remember. This is how many times I've had things fail on me. I've reinstalled arch Linux three times now in the last two weeks. The first one, I don't remember what went wrong. Something went funky there. I don't, again, I don't really remember the second one, which was the one that I just had problems with, which was yesterday. And this is kind of what spawned this video. So one of the things that I've been meaning to do for like over a year is to install my brand new backup power supply. It's a battery backup thing that you plug in. And it ensures that if you lose power, which happens a lot here in the country, it allows you to basically have time to shut your stuff down properly so that, you know, you don't lose data and all that stuff, right? And I've had this brand new PSU sitting in a box in my office for over a year. And normally, I don't let technology just sit around that long, but I have a 700 pound oak desk, which my computer sits on, which and moving it is almost impossible without like three people. So the long story short is that the PSU sat there for ages. But today, I had some time on my hands. I felt ambitious. So I decided I'm going to move the desk as much as I can by myself, which is usually enough. I can move it just a little bit, which means I can get back there to where the plug is. And you know, I was I felt ambitious. So I decided I was going to do it. So I shut my computer down after doing an update and after doing a backup. And I was going to be fine. And the process of the PSU went perfectly fine. And I went back to read to plug my computer back in, plugged it back in, boot it back up. And it got to grub past the grub test, which is, you know, usually the hurdle. And then it said that it was putting me into an emergency shell, because it couldn't find my hard drives, none of my hard drives, like specifically the main hard drive, which is an NVMe, right? It said it could it said that you could not it could not find this UU ID no longer existed. And I was like, the fuck? What the hell happened here? Like, all I did was shut the computer down, which I did it properly, like a normal person. I didn't just yank the cord, like, you know, some people would have. And then I come back to it and it was this nonsense. I was like, you know, whatever, chances are I can just see Trude into my arch install from a live ISO and change the FS tab, right? I could just do a block ID and change the FS tab and it'd be fine. I'll just go back into it and carry on with my day. No, it didn't work. So when I installed that version or that install of Arch Linux, there was a bug in Arch install, which required you to encrypt your drive. Now, they have since fixed this, if you update the arch install script on the ISO, but I didn't know that. So I just said screw it. And I encrypted my drive, right? You normally I don't, because this is a desktop. No one else is going to come here, but whatever. This time I did. And it turns out CH routing into an encrypted drive. Not that easy. Okay, it is possible. So I know those of you in the comments section below who are listening to my ramble here are probably saying, Oh, this is 100% possible. You just follow the directions. I did fall in the directions. And one of the first things you have to do is, you know, decrypt the drive or use the encrypt. There's a command that you run on the petition that is encrypted in order for you to mount it, right? But it said it wasn't encrypted, right? The error came back that the partition that I know is encrypted was not encrypted. And I was like, the, the fuck? Like what the hell? Like I know this thing is encrypted. It requires me to enter a password every single time I boot up into the system. Why are you saying it's not encrypted? It didn't make any sense to me. And I spent like maybe a half an hour, 45 minutes or so trying to troubleshoot that. And, you know, I figured, well, I mean, if it's not encrypted, then you should have no problem mounting it, right? Of course, it's not going to mount it because it is encrypted. It was an effing mess. And I was just completely done. I was very disappointed because that install of Arch Linux was running fantastically. I'd gotten all my stuff set up. I had all my VMs and stuff. And that's stupid me because I don't back up my VMs. That's going to change obviously. So I lost all my VMs. I can't believe I for whatever reason, I thought that all my VMs were stored in the home directory, but they're stored in slash var, not slash dot var or home dot var. So I lost some data. But that's just because I'm an idiot. The bottom line is that Linux hates me sometimes and it has for the last couple weeks. And I'm hoping that my string of bad luck here is finally over. I've reinstalled Arch Linux because I'm a masochist apparently. Apparently, you bite me once, you bite me twice, might as well bite me a third time. That's the way the saying goes. I mean, I don't know. I did it. I have installed Arch Linux a third time. I've promised myself that if this one here fails, I'm going back to Fedora probably as fast as my legs can carry me. And I'll be happy on Fedora like I should probably should have been this time. But I'm back in Arch and I'm using it. And I'm hoping that my string of bad luck here is over. So I just wanted to ramble about my problems for a little while. You guys are my audience. And I get to choose what the videos are all about. And today I chose to make a video that was all about my issues. So I just want to reiterate sometimes Linux hates you. Okay, things go wrong on Linux. And it feels like they go wrong over and over again in a short amount of time, because things just happen. And what I hope you take away from this video is that you need to have patience, because I don't have patience. And I probably if I had been patient back there in the Archcraft install, and I had done some research, actually, actual research, I would have found out about Pam fail lock and realized that I probably mistyped my password three times. And that's the reason why I couldn't sign in, because I've been having problems with the password that I have typing it in. For a couple weeks now, I keep putting a capital letter where there shouldn't be whatever reason, I'm just moving too fast when I type it in. And I think I know what the hell I'm doing. I don't apparently, and I keep mistyping it. I did it again. On the last Arch install I had before it broke with the whole UU ID thing. It was yesterday. In fact, type my password in wrong three times fail lock kicked in kicked me out for 10, 10 minutes had something to do with my SSH and stuff. I don't need to tell that story. And the problem is that yesterday I had the patients to go search for the problem because I was like, Oh, no, not this problem again. So I went and searched for it and found out about fail lock, realized that that's what I had done, and was able to wait 10 minutes and it just came back and was perfectly fine. If I had been patient that first time, I probably would still be on Archcraft. So the the moral of the story, when you are having an issue, and I've feel like this happens to me all the time, because I have no patience. When something goes wrong, sure, I'll go try to troubleshoot it for a little while, 1015 minutes, maybe. But if I can't find anything in that 1015 minutes, my patient snaps, I'm done with it. I'm hopping. It happens over and over again. And it's happened for years, I need to do better. But I hope you guys can learn from my mistakes. If you have Linux problems, don't immediately hit the nuclear option. Do as much research as you possibly can because it could save you time and effort from actually having to set up Linux, you know, again. So that is it for this video. If you have thoughts on my woes, you can leave those in the comment section below. I'd love to hear from you. I'm sure that the brief amount of description of the problems that I've had, someone's going to say, Well, I could have fixed this for you, or I could have given you, you know, advice or whatever. I'm sure that there are people out there like that. I'm sure, like I said at the beginning, that there are many more people much more not knowledgeable about Linux that could have solved the problems. But I could have solved the problems if I had just been a little bit more patient. So thanks everybody for watching. You can follow me on Mastodon or Odyssey. Those links will be in the video description. You can support me on Patreon at patreon.com slash the Linux cast. Thanks to everybody who does support me on Patreon and YouTube. You guys are all absolutely amazing. Thank you so very, very much for your support. I truly do appreciate it. You guys just continually blow my mind to support me and I can't thank you enough. So thank you so much. Thanks everybody for watching. I'll see you next time.