511
low effort maymay (programming.dev)

Alt text: O'RLY? generated book cover with a donkey, navy blue accent, header: "It's only free if you don't value your time", title: "Handling Arch Linux Failures", subtitle: "Mom, please cancel my today's agenda!"

you are viewing a single comment's thread
view the rest of the comments
[-] partizan@lemm.ee 23 points 4 months ago
$ head -3 /var/log/pacman.log 
[2009-04-04 12:40] installed filesystem (2009.01-1)
[2009-04-04 12:40] installed expat (2.0.1-2)
[2009-04-04 12:40] installed dbus-core (1.2.4.4permissive-1)

I installed my Arch on Desktop in 2009 and it was just cloned from one disk to another through multitude of PCs, and sure, there were occasional troubles, like upgrade from SysV init to systemd, when KDE plasma 4 released, or the time, when I had to run a custom kernel and mesa which supported the AMD Vega 56 card ~month after release.

But nowadays, I didnt had a single breakage for several years, my RX6800 GPU was well supported 3 months after release, and most things just work... BTW I run arch also on my home server, in 6 years it had literally zero issues.

[-] Andromxda@lemmy.dbzer0.com 7 points 4 months ago

Ok wow! This is really impressive. I couldn't even run Windows or Debian or something like that for 15 years, yet you managed to do it with Arch. May I ask what was the main reason behind trying to keep this Arch installation for so long? Were you just to lazy to reinstall or are there other factors?

[-] llii@discuss.tchncs.de 7 points 4 months ago

My arch install is from 2015. It just works, why should I reinstall?

[-] Andromxda@lemmy.dbzer0.com 2 points 4 months ago

@partizan@lemm.ee mentioned cloning the drive and moving it to another computer. I imagine reinstalling would be easier at that point, that's why I asked.

[-] kuberoot@discuss.tchncs.de 3 points 4 months ago

And reinstalling the packages, moving over all the configs, setting up the partitions and moving the data over? (Not in this order, of course)

Cloning a drive would just require you to plug both the old and new to the same machine, boot up (probably from a live image to avoid issues), running a command and waiting until it finishes. Then maybe fixing up the fstab and reinstalling the bootloader, but those are things you need to do to install the system anyways.

I think the reason you'd want to reinstall is to save time, or get a clean slate without any past config mistakes you've already forgotten about, which I've done for that very reason, especially since it was still my first, and less experienced, install.

[-] partizan@lemm.ee 1 points 4 months ago

Well not really, cloning is much easier than reinstalling and then configuring everything again...

I have LVM set up from the start, so usually I just copy the /boot partition to the new disk, and the rest is in a LVM volume group, so I just use pvmove from old disk to the new one, fix the bootloader and fstab UUIDs, and Im ready to reboot from new disk, while I didnt even left my running system, no live USB needed or anything. (Of course I messed it up a first few times, so had to fix from a live OS).

But once you know all the quirks, I can be up and ready on a new drive withing 20mins (depends mainly on the pvmove), with all the stuff preserved and set

[-] Andromxda@lemmy.dbzer0.com 1 points 4 months ago

That's really cool, how can I learn more about LVM and that kinda stuff?

[-] partizan@lemm.ee 2 points 4 months ago* (last edited 4 months ago)

There is many tutorials and how tos, this is quite nice one:

https://wiki.archlinux.org/title/LVM

BTW some filesystems like btrfs and ZFS already have a similar functionality built in...

[-] Andromxda@lemmy.dbzer0.com 1 points 4 months ago
load more comments (6 replies)
load more comments (8 replies)
this post was submitted on 21 Jun 2024
511 points (94.9% liked)

linuxmemes

21281 readers
131 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 1 year ago
    MODERATORS