Last week, I had a problem with my File Server. This was frustrating because I use it every day and before I go to bed, I like to watch a movie or fall asleep to one on loop. That's not happening without the server. I don't store movies locally. Although I guess I should, pfft! I got this TEMPer 2 temperature sensor I bought in the mail hoping my file server, which also has home assistant installed, could track my room temp and automatically trigger my smart LG portable AC for my room. The temp is different all the time, like it stays out of alignment with the timers you have set for the AC, and you get frustrated with it after long enough that you knee-jerk react with a highly tuned setting for turning on and off regularly to keep the temperature in an expectable range and the second you do that, there's a wide temperature swing like a week later. Then you just deal with that for a month or something before you finally change it again and it changes like a week after that too. And this winter has been strange where I live too because that groundhog said winter was over I think and then the temperature seemed to go up about twenty degrees, then a week or two later we had one of the first snow storms of our entire winter, then a few weeks later, an even bigger snow storm. But I think now it is officially over, the temperature is swinging up into the fifties every few days.
So I got that temperature sensor in the mail hoping to configure the server to trigger my AC on and off according to my room temperature since for some strange reason, this AC is so smart that it won't track the temperature like my last AC did. I am not a fan of smart devices, they just don't seem that smart because they frequently miss the obvious thing or they are intentionally programmed to do so in order to benefit the companies that sell them, like the remote for the AC not being so handy, forcing you to use the app, which forces you to wait while it loads ads every time you want to turn the ac on or off without getting up out of bed or something.
Unfortunately, my attempts to configure the sensor caused me to have to update a python package so the server could read it, which required a Kernel update, which it told me required a reboot and since I wanted to best results possible right now so I could get it working, I decided to reboot. But I thought for some reason that Linux updated the Kernel before reboot and the reboot simply put the changes into affect, like it gets saved to the hard drive and then after reboot, it gets loaded into RAM for actual usage. So when it didn't immediately finish rebooting, I thought something went wrong, but because its headless, and there's no video signal output until you reboot with a screen plugged in and on, then it will just keep negating the video output. So I rebooted with a screen plugged in. Little did I realize what a huge mistake this was. Apparently it loads during reboot, and I interrupted it mid loading. And so I couldn't SSH into it, for some reason it completely escaped me to try pinging it but it's not like that would have changed much. I knew it was running because the motherboard lights and the CPU fan were on. But after many reboots, no screen output still and I couldn't SSH into it at all after many tries. I left it running and went to bed. I think I tried again after I woke up and it still didn't work. I had a friend come over like a few days later I think and he was running through it with me, starting by trying to access the BIOS which I said, hey just so you know, I can't seem to get any screen output just so you know. And there are no keyboard lights either and I tried multiple USB ports too. So I can't tell that it's actually passing POST. But there's no beep code, and I don't recall it ever beeping when booting so I was at a total loss. And first thing when he sat down and had me reboot, he looked up how to access BIOS on this motherboard and started spamming and then just holding down the delete key for my MSI board. And it worked. The SMI logo appeared big on the screen like when it boots, and then it went into BIOS. Typical! It waited till he got here to work fine.
I seriously looked into setting it up to always put out a video signal even if there's no screen plugged in because this one screen output problem has caused me trouble nearly every time I can recall there was an issue in the past year and a half since I built this server. The problem was very simple. In fact, there was no problem. Now that he was here, the screen turned on, unlike before. Now that he was here and we entered BIOS, there was no BIOS setting to fix, boot drive order was fine. We exited without saving and then it booted normal. I checked to make sure I could SSH into it, I could. I checked to see if I could access filed through SMB, I could. Tss!
Then about a week later I realized the TEMPer2 sensor came with a CD ROM probably with a driver to load. I thought, oh, well, since my previous attempts to get the sensor working didn't work, maybe this driver will fix the issue. I did find something online I could install through the CLI, but I wanted to be sure I exhausted all other possibilities before I did it because I don't always install things willy-nilly, just to see if it works and then leave it on there if it doesn't, and I try not to at all because it seems the more you install with reckless abandon, the sooner you'll have to reinstall the OS. So if I do, I try to keep it at a minimum.
Well, was experimenting with something that required my DVD burner that I haven't needed in years, and it was an internal DVD burner and my current case doesn't have a place to install the burner. I could plug it in with some effort to take the desktop off its VESA mount and unscrew the pack and access the cable compartment in the back and fiddle with the wires and figure out a way to get this thing plugged in, but then I realized I had a SATA to USB 3 adapter with a 12 volt power plug attached. I bought it for other reasons but this should work great, I pulled it out and started using it and then because I used it for this other project, I suddenly realized, hey, might as well put the driver CD in it. So I did, and then started thinking for some reason how to get the driver software transferred to the server from Windows. I imagined all the difficulty I went through a few months ago when I accidentally deleted a whole folder full of recordings I didn't want to lose because they couldn't be replaced, and thanked my lucky stars when I realized this is why I utilize cold storage and not not just my RAIFD 5. So I accessed my IronWolf I use for cold storage, which I back up automatically once a week, and it was a nightmare accessing it just to pull the recordings off of it and put them back on the RAID 5. Since then I have concluded that I should have just created another SMB share straight to the IronWolf, assuming there's no reason I can't do that. As a matter of fact now that I think of it, perhaps I could just set up some sort of mechanism that will automatically undo any mistaken deletes, just revive them from cold storage just like File History on Windows. I looked it up and that is a thing you can do in Linux, I would have to adjust my Cron job for RSYNC to run once a week to then organize backups according to date and create a snapshot. And then you can just CD to a directory for easy restoration. But I want something with easier access that doesn't require SCP. Well, I suppose this would make for a good opportunity to get good at using SCP.
So I had this idea over the past week, why am I struggling to find the will power to transfer the files from this CD to my server from my Windows desktop, when I can simply plug the USB 3 adapter into the server for the DVD burner? So I did. And then I was going to work on it remotely when it just didn't work out that way. I am supposed to be studying my butt off to pass y Network + certification these past few weeks so I can take it end of this month. But I had a migraine from a dietary issue I had, which is taking days to go away and it went away briefly after a heavy dose of medicine so I thought, well, this driver issue has just been sitting there waiting for one spare moment, how hard can this be. I mounted it, I explored the contents, and I discovered the driver was in msi format. I started to think this might be an issue because Linux doesn't read .msi, which is meant for Windows. There was a thing I could try but then I thought I would put it down for now and go to bed since it was the end of the day, and then I discovered that my server was totally inaccessible from my Windows desktop I watch movies on before bed. And then I discovered it was totally inaccessible from my Windows laptop too. I could SSH into it no problem, SMB was running, I rebooted my laptop even though I didn't think that would fix the issue because the problem seemed to happen at the exact same time for both Windows computers which is a fantastic coincidence when both are trying to access the same common file share from the Linux File Server, the common denominator. The only thing I know happened was that I mounted the DVD burner in Linux. I looked online to see if that could mess up a file share and the internet said "Yes!" It seemed strange to me that just trying to access a drive could interfere with a share on an unrelated drive. I rebooted the server, nothing. I was out of options and unmounted the drive. That didn't fix anything either. I was just about thinking at this point, well, Robert will come here again and sit down for five minutes just for the server to be like, "What? Misbehaving? Me? You're mistaken!" for the second time. And then when asking ChatGPT about this problem, it suggested rebooting the SMB service. So I did that too.
That fixed it, the share worked just fine again! Gah! At least it only took one hour to fix this time.