• 1 Post
  • 151 Comments
Joined 1 year ago
cake
Cake day: June 20th, 2023

help-circle

  • I may have posted this before, but…late last year I realized my Debian server with circa 2009 hardware, with 4 gb of RAM and Core 2 Quad processor, was no longer up to the tasks I wanted it to perform; in particular, running a Home Assistant server. Back in 2018 or so, I added a software Linux RAID5 array with 5 active 3 TB drives and one hot spare, along with a “cold spare” that I’ve never actually used.

    So, early this year, I bought hardware to upgrade my desktop machine, which was still plenty fast for me, and move the guts to my server. This is how my server usually gets upgraded. Upgrade the desktop machine, give it a few days or weeks to make sure it’s stable, and then upgrade the server.

    I installed the hardware without a problem, booted it up, and everything seemed okay, except that I …couldn’t access the RAID. At first it was like, well, I’m sure it’s nothing serious, but then when mdadm could even FIND it, I started to get extremely worried. Fear set in.

    Long story short: When I built the RAID, I followed directions that used the entire discs as the RAID, instead of making a partition on the disc and using that partition. The old motherboard didn’t care, but the new one saw the bare discs and was like, “Hey, those are messed up, I’ll fix the partition table for you!” Turns out, building Linux RAIDs by using the full discs like that is a VERY BAD IDEA for exactly this reason - but there are still guides out there showing that method and not mentioning the risks.

    I was panicking. I spent days trying to figure out what to do and nothing was working. I was asking for help on the Linux-RAID list (and most of them were as helpful as they could be). Unfortunately my backups were NOT up to par (something I should have checked before starting), and I was at the point where I was like, well, I’ve lost x, y, and z.

    I had basically given up and was just recreating the RAID using the “create command” then trying to see if I could mount the drive read-only. With 6 drives, there are quite a few possible combinations that could be the right one. If I remember correctly, I was able to figure out which drive was the spare, so I could limit my searches to the other 5, and knowing all 5 were in use, it was a matter of trying different orders. I think I got close one time and ext4 gave me weird read error, so after that I swapped two drives, and hit the right order.

    Eventually … I found it. I found the right combination and could reload it! Everything was there, untouched! As quickly as I could, I copied everything to a 10 TB drive I bought and installed into the desktop system. I saved the command, rebooted, and the same thing happened again - so it was definitely a motherboard problem - but this time I knew how to recreate it, and did so.

    Since I now had a backup, I partitioned each drive and rebuilt the array using partitions…and I saved every piece of data I could think of about building the array, outputs of mdadm, outputs of /proc/mdstat, partition IDs, etc. Naturally, having that info likely means I’ll never need it.

    I was so relieved when I saw that mount command work without error. I spent close to a week worrying about it, and in that moment it was a huge rush.

    New setup handles HA and other duties with aplomb and is very reliable, so in the end it was very worth it.

    This is less “silly” and more “horrifying”. Sorry.


  • Zwiftinsider isn’t run by Zwift - he just reports on them (though he definitely has inside information, and they work with him on various things, like letting him use “bots” to test various functionalities).

    That is pretty old. I think there are several approaches now. The one he lists, one using docker (I actually had it running on my desktop Linux machine, but I didn’t actually test it), and I think some people got it working under WINE.

    Zwift’s saving grace is that you can connect most hardware via your phone - trainer, cadence, heart rate monitor, etc. - because it’s designed to also run on things like Apple TVs, iPads, and Android phones and tablets, albeit with probably lower graphics settings. So, you don’t need to worry about the hardware end of it (ANT+ dongle), which very much simplifies the issue. Which reminds me, my heart rate monitor is ANT+ only, and I’d need a bluetooth-capable one to do this.

    (Also, at worst, I could run it on my tablet and hook that up to a monitor, so even if I can’t get it running on Linux, I still have options.)



  • I need to do this with my gaming computer yet. I run Linux on my other machines (and have for many years), but this one is Windows. I bought the computer in 2021, but it doesn’t have the trusted computing module, so I can’t upgrade it to Windows 11 even if I wanted to.

    Last night I tried to add an SSD that I had from a laptop that died, figuring I’ll put a fresh install of Linux on the second SSD and not touch the original drive. Unfortunately, the computer didn’t want to boot off the original drive any more - even when I changed the boot priority to the original drive, I still got grub from the new drive. I had to disconnect the new SSD to get the computer to boot Windows on the original drive (I wasn’t ready to do the Linux install and might need Windows in the mean time).

    I know it’s a temporary issue at worst, as the installer will likely pick up that Windows installation and make it an option in grub. But it was a setback I wasn’t expecting. I figured I’d put in the drive and have it just idling there until I had time to run the Linux installation.






  • limelight79@lemm.eetoLinux@lemmy.mlThe Dislike to Ubuntu
    link
    fedilink
    arrow-up
    109
    arrow-down
    1
    ·
    3 months ago

    Every time this is asked, I post the same comment. I used Kubuntu for years and liked it, but more recently they started doing things that annoyed me. The biggest was related to snaps and Firefox. Now, sandboxing a browser is probably a great idea, but I wanted to use the regular deb install, so I followed the directions to disable the snap install and used the deb. However, Ubuntu overrode that decision several times - I’d start browsing, then realize I was using a snap AGAIN. Happened a few times over a couple years. If it happened once, eh, maybe an error, but it happened 3 or 4 times. I came to the conclusion I wasn’t in control of my system, Ubuntu was.

    I switched to Debian and am happy with my choice.


  • Yeah. I grew up in the days of serial ports and parallel ports, and USB in general is so much better for most purposes. (I recall plugging my first mouse into the serial port…but wait! Where will my Hayes Smartmodem modem plug into then? Also, don’t plug and unplug things from the serial port while the computer is running.)

    And USB-C is even better. My tablet needs a charge? Well my laptop charger is right here… My phone is low and needs a quick charge? Well my USB-C tablet charger will give it a decent boost very quickly. No worries about getting it plugged in the wrong way, either.

    I have a docking station for my work laptop, so when I had to replace my personal laptop, a laptop that supported USB-C power delivery was mandatory. I don’t use it with the docking station very often, but knowing I can without an issue is great. My wife also has a Macbook that works on the docking station, too, in case she ever wants to use my dual monitor setup. All three laptops, from three different brands, are just plug in and go.






  • “If you want to know how Linux works, ask a Slackware user.”

    I’ve mentioned this a lot lately, but I used Slackware from the late 90s (3.x days) until about 2009 on my desktop and laptop, and about 2017 on my server. I just got tired of dealing with dependencies and switched to Debian (all three run Debian now). I had the CD subscription and would automatically receive the latest version about twice a year.

    Patrick Volkerding (if my memory is accurate) has my utmost respect, and I do feel a little bad about abandoning it, but I just didn’t have the time to deal with it any more.


  • That reminds me - for my Lenovo laptop, no issues at all with suspend and resume (just like Kubuntu). But my desktop was going to sleep when I first installed Debian, and it was NOT waking up gracefully; in fact I had to reboot it each time. Since I didn’t want it to go to sleep at all, I didn’t attempt to diagnose the issue beyond turning off the suspend mode in power management.


  • I just had to change a few things - KDE, dark mode, X11 when I couldn’t get screen power off to work under Wayland, and it’s basically good to go. There might be a few other things I changed, but in general out of the box was pretty close to what I wanted. It even installed the AMD driver for my graphics card.


  • That sounds like it’s mostly about the default install, and I don’t have a problem with them making the default a snap - as I said, sandboxing a browser probably is a good idea from a security perspective, and most people probably aren’t going to care about snap vs. deb installs, so why not go with the safer alternative?

    My issue was that it kept switching back to snaps even after I tried to go to .deb installations. It happened at least three or four times. It would be fine for several months, then something would happen during an update, and it would switch back.

    I didn’t have the concerns the article mentions about it automatically updating; it would only update whenever I told software in general to update.


  • I can’t find it at the moment, but a few weeks ago I made a comment that I didn’t really care for the paddle shifters in our car (it’s an automatic, but you can switch to “manual mode” and shift it manually), because I know it’s not going to let me do something stupid, whereas a stick shift will usually let me do stupid things that can damage the engine. That’s partially what prompted the measuring power as ability to screw things up comment. :)