Looks like you are going to get into really big trouble -- if you are not there already -- and if what you are posting isn't fake. I don't envy your position. Nevertheless, I hope everything somehow will turn out okay for you, eventually, somehow!
I guess I don't get it, what trouble will he be getting into? DM me if you don't want to make it public...
It looks like he's logged in as root to what might be an AT&T infrastructure machine with 256 Epyc cores, 1.5 TiB RAM, and maybe 8 NVMe disks.
Maybe the yabs and the lsblk are fake. I don't know. But, if it really is an AT&T infrastructure machine, it's hard to believe that any Low Ender is authorized to be root and to install Firefox plus lots of other stuff.
It looks like he's logged in as root to what might be an AT&T infrastructure machine with 256 Epyc cores, 1.5 TiB RAM, and maybe 8 NVMe disks.
Maybe the yabs and the lsblk are fake. I don't know. But, if it really is an AT&T infrastructure machine, it's hard to believe that any Low Ender is authorized to be root and to install Firefox plus lots of other stuff.
Giving him the benefit of the doubt, he might just happened to use a VPN. Also, I doubt any AT&T infrastructure machine would be named "server-saya" (my-server in Indonesian/Malay).
Of course, he might be altering the YABS output.
The speedtest portion of YABS is not clocking at gig speed as well, which should be expected of a infra machine.
19 updates can be applied immediately.
To see these additional updates run: apt list --upgradable
3 additional security updates can be applied with ESM Apps.
Learn more about enabling ESM Apps service at https://ubuntu.com/esm
*** System restart required ***
I plan to update and reboot tomorrow morning, September 18, around 11 AM Mountain Standard Time (MST), which will be about 6 PM UTC. I will post here, as usual, before and. after.
Thanks to @crunchbits for beautiful Crunchy! Thanks to all of you who are using Crunchy!
We have an local wired internet outage here in Mexico where I am today. I am connecting via my phone to say that I am going to put off updating and rebooting Crunchy until tomorrow. Thanks!
Maybe yesterday's outage brought an improvement. Our internet today is maybe double the previous speed. In case anybody might be interested, Google Fiber Speed Test results are
Ping 5 ms
Jitter 0 ms
Download 39.9 Mbps
Upload 19.6 Mbps
Great news! Looks like our beautiful Crunchy is back up! Looks like all VMs are running! Thanks @crunchbits! Thanks @babywhale!
Please let me know about any issues! Thanks again!
Welcome to Ubuntu 22.04.5 LTS (GNU/Linux 5.15.0-122-generic x86_64)
[ . . . ]
Last login: Thu Sep 19 16:15:01 2024 from xxx.xxx.xxx.xxx
root@crunchy:~# date
Thu Sep 19 04:36:28 PM UTC 2024
root@crunchy:~# cd bashvm
root@crunchy:~/bashvm# bash bashvm.sh
========================== Main Menu ==========================
1. Virtual Machines 2. Storage Pools 3. Networks
4. Snapshots 5. Edit Properties 6. Firewall Settings
7. Port Forwarding 8. VNC / Console Access 9. System Monitor
q. Exit
Enter your choice: 1
==================== Manage Virtual Machine ====================
s. Show all virtual machines 1. Show more details of a VM
2. Start a VM 3. Reboot a VM
4. Shutdown a VM (graceful) 5. Shutdown a VM (force)
6. Enable autostart of a VM 7. Disable autostart of a VM
8. Create a new / existing VM 9. Undefine a VM
10. Create a new VM (Automated) 11. Console into a VM
12. Change resources of a VM 13. Delete a VM
q. Back to main menu
Enter your choice: s
Id Name State
--------------------------------
1 vm107-crunchy running
2 vm105-crunchy running
3 vm102-crunchy running
4 vm104-crunchy running
5 vm100-crunchy running
6 vm103-crunchy running
7 vm101-crunchy running
8 vm106-crunchy running
- vm1-crunchy shut off
- vm2-crunchy shut off
==================== Manage Virtual Machine ====================
s. Show all virtual machines 1. Show more details of a VM
2. Start a VM 3. Reboot a VM
4. Shutdown a VM (graceful) 5. Shutdown a VM (force)
6. Enable autostart of a VM 7. Disable autostart of a VM
8. Create a new / existing VM 9. Undefine a VM
10. Create a new VM (Automated) 11. Console into a VM
12. Change resources of a VM 13. Delete a VM
q. Back to main menu
Enter your choice:
Crunchy's current end date is November 8. I see October 8 is pretty much a final action date, because, on or about October 8, the Crunchbits billing platform might send me a bill for another year of Crunchy. Therefore, I want to do something prior to the end of September and definitely ahead of October 8.
I'm really grateful to Crunchbits for sponsoring Crunchy free for a whole year! It's wonderful that our friends have been able to enjoy Crunchy VMs for free!
@crunchbits and I have talked briefly a couple of times about possibilities for renewing Crunchy as free for an additional one year term. We also discussed the possibility that Crunchy might be upgraded to Ryzen. However, nothing has as yet been confirmed.
Cancelling Crunchy
Assuming Crunchbit's billing panel will let me do so, I expect to cancel Crunchy in a few days and prior to the end of September, but effective on November 8, the end of the current billing period. The cancellation will occur only because I want to give sufficient and timely notice.
Backups, Redundancy, and Possible Migration
It's never too early to think about backups, redundancy, and the possibility of migration.
Please recall that I am not making backups. Therefore, just to be safe, I recommend that Crunchy users please backup and redeploy to one or more redundant locations. Backups and redeployments should be done as soon as convenient -- soon enough that time still remains to redo failed backups -- it is important to make sure that our backups and redeployments are actually useable.
If anyone needs help with backups, redundancy, or migration, please let me know.
Crunchy has been wonderful! She's been super stable with only one minor hiccup that I know about -- which was caused by a cable cut not Crunchbits' fault. Really, we couldn't ask for better server performance!
Thanks to all of you guys who have been using Crunchy! Thanks again to @crunchbits!
Active participation in this thread's discussion is required!
One of my goals for this thread was to encourage quality LES posts by our Crunchy Neighbors about their Crunchy adventures.
Since we are about to upgrade beautiful Crunchy, please allow me to ask if any of our current Crunchy Neighbors might like to share about their fascinating times aboard Crunchy?
Crunchy has been a fantastic SSH jump host and testing bed for some bash shenanigans! I've surprisingly not nuked my VM to the point its needed a re-install (yet!)
@terrorgen said:
Curious, why are you using a mirror in Netherlands when crunchy is in Spokane?
Thanks for that! I never noticed before! Here's /etc/apt/sources.list. You can see the "NL" entries.
Crunchy's Ubuntu was installed from the Crunchbits image. Maybe @sh97 knows why it's set to a NL mirror?
root@crunchy:~# cat /etc/apt/sources.list
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://nl.archive.ubuntu.com/ubuntu jammy main restricted
# deb-src http://nl.archive.ubuntu.com/ubuntu jammy main restricted
## Major bug fix updates produced after the final release of the
## distribution.
deb http://nl.archive.ubuntu.com/ubuntu jammy-updates main restricted
# deb-src http://nl.archive.ubuntu.com/ubuntu jammy-updates main restricted
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://nl.archive.ubuntu.com/ubuntu jammy universe
# deb-src http://nl.archive.ubuntu.com/ubuntu jammy universe
deb http://nl.archive.ubuntu.com/ubuntu jammy-updates universe
# deb-src http://nl.archive.ubuntu.com/ubuntu jammy-updates universe
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://nl.archive.ubuntu.com/ubuntu jammy multiverse
# deb-src http://nl.archive.ubuntu.com/ubuntu jammy multiverse
deb http://nl.archive.ubuntu.com/ubuntu jammy-updates multiverse
# deb-src http://nl.archive.ubuntu.com/ubuntu jammy-updates multiverse
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://nl.archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
# deb-src http://nl.archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted
# deb-src http://security.ubuntu.com/ubuntu/ jammy-security main restricted
deb http://security.ubuntu.com/ubuntu/ jammy-security universe
# deb-src http://security.ubuntu.com/ubuntu/ jammy-security universe
deb http://security.ubuntu.com/ubuntu/ jammy-security multiverse
# deb-src http://security.ubuntu.com/ubuntu/ jammy-security multiverse
root@crunchy:~#
root@crunchy:~# cat /etc/apt/sources.list.curtin.old
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://archive.ubuntu.com/ubuntu/ jammy main restricted
# deb-src http://archive.ubuntu.com/ubuntu/ jammy main restricted
## Major bug fix updates produced after the final release of the
## distribution.
deb http://archive.ubuntu.com/ubuntu/ jammy-updates main restricted
# deb-src http://archive.ubuntu.com/ubuntu/ jammy-updates main restricted
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://archive.ubuntu.com/ubuntu/ jammy universe
# deb-src http://archive.ubuntu.com/ubuntu/ jammy universe
deb http://archive.ubuntu.com/ubuntu/ jammy-updates universe
# deb-src http://archive.ubuntu.com/ubuntu/ jammy-updates universe
## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team, and may not be under a free licence. Please satisfy yourself as to
## your rights to use the software. Also, please note that software in
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://archive.ubuntu.com/ubuntu/ jammy multiverse
# deb-src http://archive.ubuntu.com/ubuntu/ jammy multiverse
deb http://archive.ubuntu.com/ubuntu/ jammy-updates multiverse
# deb-src http://archive.ubuntu.com/ubuntu/ jammy-updates multiverse
## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://archive.ubuntu.com/ubuntu/ jammy-backports main restricted universe multiverse
# deb-src http://archive.ubuntu.com/ubuntu/ jammy-backports main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted
# deb-src http://security.ubuntu.com/ubuntu/ jammy-security main restricted
deb http://security.ubuntu.com/ubuntu/ jammy-security universe
# deb-src http://security.ubuntu.com/ubuntu/ jammy-security universe
deb http://security.ubuntu.com/ubuntu/ jammy-security multiverse
# deb-src http://security.ubuntu.com/ubuntu/ jammy-security multiverse
root@crunchy:~#
October 8, 2024 has arrived, so E3 Crunchy now has one month to go before expiration on November 8. Of course, as E3 Crunchy's final month progresses, we doubtless will hear details from @crunchbits about when and how E3 Crunchy will be upgraded to Ryzen.
E3 Crunchy has been working really very well, so I have asked @crunchbits for a price quote to enable me to keep the E3 server for personal use following Crunchy's move to Ryzen. However, if someone else wants to take over the E3 server, that's okay. Just let me know, and please make arrangements directly with @crunchbits.
Regretfully, I myself am unable to move to the new Ryzen Crunchy. Other projects are calling. Therefore, I need to ask at this time whether someone from our Community will please step forward and volunteer to take over administration of the new Ryzen Crunchy. Running our Community's server is a great way to pay back for all the benefits of LES membership! Crunchy also offers great opportunities to learn more about system administration. And, last but not least, Crunchy offers excellent resume value for anyone who is going to be looking for employment.
Server migrations are a time when backups are good to have. Everything probably will go perfectly, but . . . things happen . . . so I urge everyone to please backup immediately to more than one safe place.
Crunchy has been super great! Thanks to @crunchbits for wonderful Crunchy! Thanks also to @babywhale for BashVM, the tool which has made most of Crunchy's VPs.S Thanks to LES for hosting this thread! Thanks to everyone who has been using a Crunchy VPS!
Let's all continue to enjoy E3 Crunchy as we begin the time period for the upgrade to the new Ryzen Crunchy!
@Not_Oles said:
Looks like the reboot went okay, and all the BashVM VMs are reported as running. Please let me know about any issues. Thanks!
With multiple servers (I believe you have now) have you thought about doing a cluster and migrating VMs between servers when you need to reboot or do other maintenance on one of them?
@Not_Oles said:
Looks like the reboot went okay, and all the BashVM VMs are reported as running. Please let me know about any issues. Thanks!
With multiple servers (I believe you have now) have you thought about doing a cluster and migrating VMs between servers when you need to reboot or do other maintenance on one of them?
Yes, the idea has crossed my mind. If we were to try it, how should it be implemented? Thanks!
@Not_Oles said:
Looks like the reboot went okay, and all the BashVM VMs are reported as running. Please let me know about any issues. Thanks!
With multiple servers (I believe you have now) have you thought about doing a cluster and migrating VMs between servers when you need to reboot or do other maintenance on one of them?
Yes, the idea has crossed my mind. If we were to try it, how should it be implemented? Thanks!
I don't really have all of the necessary information to be able to say how it should be implemented. Is the hardware identical? If you have 128GB of memory on one server and only 64GB on another it would be hard to failover all of the VMs from the 128GB server to the smaller one. Do you already have shared storage?
You could go the replication-based failover approach, the live migration option or even just a script-based failover setup. You could do it all pretty easily with Proxmox but if that's not ideal for you. Evidian SafeKit is a commercial solution that would work. You should look into oVirt, pacemaker, drbd and keepalived. Whatever route you decide to go make sure you concentrate on your storage replication, network configuration, fencing and your monitoring.
root@crunchy:~# date
Mon Oct 28 06:25:42 AM UTC 2024
root@crunchy:~# apt-get update
Get:1 http://security.ubuntu.com/ubuntu jammy-security InRelease [129 kB]
Hit:2 http://nl.archive.ubuntu.com/ubuntu jammy InRelease
Hit:3 http://nl.archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:4 http://nl.archive.ubuntu.com/ubuntu jammy-backports InRelease
Fetched 129 kB in 2s (71.6 kB/s)
Reading package lists... Done
root@crunchy:~# apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
sosreport
The following packages will be upgraded:
distro-info-data qemu qemu-block-extra qemu-system-common qemu-system-data qemu-system-gui
qemu-system-x86 qemu-utils ubuntu-drivers-common
9 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 15.4 MB of archives.
After this operation, 1,024 B of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://nl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 ubuntu-drivers-common amd64 1:0.9.6.2~0.22.04.8 [59.4 kB]
Get:2 http://nl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 distro-info-data all 0.52ubuntu0.8 [5,302 B]
Get:3 http://nl.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 qemu amd64 1:6.2+dfsg-2ubuntu6.23 [14.0 kB]
Get:4 http://nl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 qemu-system-gui amd64 1:6.2+dfsg-2ubuntu6.23 [220 kB]
Get:5 http://nl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 qemu-block-extra amd64 1:6.2+dfsg-2ubuntu6.23 [68.2 kB]
Get:6 http://nl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 qemu-system-x86 amd64 1:6.2+dfsg-2ubuntu6.23 [10.1 MB]
Get:7 http://nl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 qemu-system-common amd64 1:6.2+dfsg-2ubuntu6.23 [2,048 kB]
Get:8 http://nl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 qemu-utils amd64 1:6.2+dfsg-2ubuntu6.23 [1,525 kB]
Get:9 http://nl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 qemu-system-data all 1:6.2+dfsg-2ubuntu6.23 [1,431 kB]
Fetched 15.4 MB in 9s (1,678 kB/s)
Preconfiguring packages ...
(Reading database ... 136418 files and directories currently installed.)
Preparing to unpack .../0-ubuntu-drivers-common_1%3a0.9.6.2~0.22.04.8_amd64.deb ...
Unpacking ubuntu-drivers-common (1:0.9.6.2~0.22.04.8) over (1:0.9.6.2~0.22.04.7) ...
Preparing to unpack .../1-distro-info-data_0.52ubuntu0.8_all.deb ...
Unpacking distro-info-data (0.52ubuntu0.8) over (0.52ubuntu0.7) ...
Preparing to unpack .../2-qemu_1%3a6.2+dfsg-2ubuntu6.23_amd64.deb ...
Unpacking qemu (1:6.2+dfsg-2ubuntu6.23) over (1:6.2+dfsg-2ubuntu6.22) ...
Preparing to unpack .../3-qemu-system-gui_1%3a6.2+dfsg-2ubuntu6.23_amd64.deb ...
Unpacking qemu-system-gui (1:6.2+dfsg-2ubuntu6.23) over (1:6.2+dfsg-2ubuntu6.22) ...
Preparing to unpack .../4-qemu-block-extra_1%3a6.2+dfsg-2ubuntu6.23_amd64.deb ...
Unpacking qemu-block-extra (1:6.2+dfsg-2ubuntu6.23) over (1:6.2+dfsg-2ubuntu6.22) ...
Preparing to unpack .../5-qemu-system-x86_1%3a6.2+dfsg-2ubuntu6.23_amd64.deb ...
Unpacking qemu-system-x86 (1:6.2+dfsg-2ubuntu6.23) over (1:6.2+dfsg-2ubuntu6.22) ...
Preparing to unpack .../6-qemu-system-common_1%3a6.2+dfsg-2ubuntu6.23_amd64.deb ...
Unpacking qemu-system-common (1:6.2+dfsg-2ubuntu6.23) over (1:6.2+dfsg-2ubuntu6.22) ...
Preparing to unpack .../7-qemu-utils_1%3a6.2+dfsg-2ubuntu6.23_amd64.deb ...
Unpacking qemu-utils (1:6.2+dfsg-2ubuntu6.23) over (1:6.2+dfsg-2ubuntu6.22) ...
Preparing to unpack .../8-qemu-system-data_1%3a6.2+dfsg-2ubuntu6.23_all.deb ...
Unpacking qemu-system-data (1:6.2+dfsg-2ubuntu6.23) over (1:6.2+dfsg-2ubuntu6.22) ...
Setting up qemu (1:6.2+dfsg-2ubuntu6.23) ...
Setting up qemu-system-common (1:6.2+dfsg-2ubuntu6.23) ...
Setting up ubuntu-drivers-common (1:0.9.6.2~0.22.04.8) ...
Setting up distro-info-data (0.52ubuntu0.8) ...
Setting up qemu-system-data (1:6.2+dfsg-2ubuntu6.23) ...
Setting up qemu-utils (1:6.2+dfsg-2ubuntu6.23) ...
Setting up qemu-block-extra (1:6.2+dfsg-2ubuntu6.23) ...
Setting up qemu-system-x86 (1:6.2+dfsg-2ubuntu6.23) ...
Setting up qemu-system-gui (1:6.2+dfsg-2ubuntu6.23) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for man-db (2.10.2-1) ...
Scanning processes...
Scanning candidates...
Scanning processor microcode...
Scanning linux images...
Running kernel seems to be up-to-date.
The processor microcode seems to be up-to-date.
No services need to be restarted.
No containers need to be restarted.
No user sessions are running outdated binaries.
No VM guests are running outdated hypervisor (qemu) binaries on this host.
root@crunchy:~#
No reboot needed. Since Qemu was upgraded, please let me know about any issues with VPSes. Thanks!
No, Crunchy is different hardware from my other servers. Different processors, different amounts of RAM, different drives with different sizes.
However, the two servers I have in Germany are pretty close to identical. The only difference is the manufacturer of the drives, but the drives are of the same type and size.
The servers all have directly attached disks. No shared storage.
@FrankCastle said: You could do it all pretty easily with Proxmox but if that's not ideal for you. Evidian SafeKit is a commercial solution that would work. You should look into oVirt, pacemaker, drbd and keepalived.
Comments
MetalVPS looks like a very nice project - @Not_Oles - thank you for sharing the experience. It's interesting to read and follow.
BashVM looks like a very useful project - @babywhale - will be trying it out. Thank you for creating and sharing.
Hi @sumo! Welcome to LES! Best wishes!
I hope everyone gets the servers they want!
I guess I don't get it, what trouble will he be getting into? DM me if you don't want to make it public...
The all seeing eye sees everything...
Look at the posted yabs and lsblk here: https://lowendspirit.com/discussion/comment/183817/#Comment_183817
It looks like he's logged in as root to what might be an AT&T infrastructure machine with 256 Epyc cores, 1.5 TiB RAM, and maybe 8 NVMe disks.
Maybe the yabs and the lsblk are fake. I don't know. But, if it really is an AT&T infrastructure machine, it's hard to believe that any Low Ender is authorized to be root and to install Firefox plus lots of other stuff.
I hope everyone gets the servers they want!
Giving him the benefit of the doubt, he might just happened to use a VPN. Also, I doubt any AT&T infrastructure machine would be named "server-saya" (my-server in Indonesian/Malay).
Of course, he might be altering the YABS output.
The speedtest portion of YABS is not clocking at gig speed as well, which should be expected of a infra machine.
The all seeing eye sees everything...
Of course!
I hope everyone gets the servers they want!
Hi Guys!
Crunchbuntu says:
I plan to update and reboot tomorrow morning, September 18, around 11 AM Mountain Standard Time (MST), which will be about 6 PM UTC. I will post here, as usual, before and. after.
Thanks to @crunchbits for beautiful Crunchy!
Thanks to all of you who are using Crunchy! 
I hope everyone gets the servers they want!
Good morning!
We have an local wired internet outage here in Mexico where I am today. I am connecting via my phone to say that I am going to put off updating and rebooting Crunchy
until tomorrow. Thanks!
I hope everyone gets the servers they want!
Good morning again!
The internet is back up here, and, as mentioned yesterday, I'm about to try updating, upgrading, and rebooting beautiful Crunchy!
I will post again after it's done!
Thanks to @crunchbits for beautiful
Crunchy!
Maybe yesterday's outage brought an improvement. Our internet today is maybe double the previous speed. In case anybody might be interested, Google Fiber Speed Test results are
I hope everyone gets the servers they want!
Great news! Looks like our beautiful
Crunchy is back up! Looks like all VMs are running! Thanks 
@crunchbits! Thanks 
@babywhale!
Please let me know about any issues! Thanks again!
I hope everyone gets the servers they want!
Crunchy's End Date Approaches!
Crunchy's current end date is November 8. I see October 8 is pretty much a final action date, because, on or about October 8, the Crunchbits billing platform might send me a bill for another year of Crunchy. Therefore, I want to do something prior to the end of September and definitely ahead of October 8.
I'm really grateful to Crunchbits for sponsoring Crunchy free for a whole year!
It's wonderful that our friends have been able to enjoy Crunchy VMs for free! 
@crunchbits and I have talked briefly a couple of times about possibilities for renewing Crunchy as free for an additional one year term. We also discussed the possibility that Crunchy might be upgraded to Ryzen. However, nothing has as yet been confirmed.
Cancelling Crunchy
Assuming Crunchbit's billing panel will let me do so, I expect to cancel Crunchy in a few days and prior to the end of September, but effective on November 8, the end of the current billing period. The cancellation will occur only because I want to give sufficient and timely notice.
Backups, Redundancy, and Possible Migration
It's never too early to think about backups, redundancy, and the possibility of migration.
Please recall that I am not making backups. Therefore, just to be safe, I recommend that Crunchy users please backup and redeploy to one or more redundant locations. Backups and redeployments should be done as soon as convenient -- soon enough that time still remains to redo failed backups -- it is important to make sure that our backups and redeployments are actually useable.
If anyone needs help with backups, redundancy, or migration, please let me know.
Crunchy
has been wonderful! She's been super stable with only one minor hiccup that I know about -- which was caused by a cable cut not Crunchbits' fault. Really, we couldn't ask for better server performance! 
Thanks to all of you guys who have been using Crunchy!
Thanks again to @crunchbits! 
Best wishes!
Tom
I hope everyone gets the servers they want!
On Discord, @crunchbits said
That's great news! Thanks so much @crunchbits!
As mentioned above, I went ahead and cancelled the existing beautiful Crunchy
server effective at the end of the current billing period, November 8.
So it's definitely confirmed that current Crunchy Neighbors will need to migrate.
Thanks again to @crunchbits for beautiful Crunchy!
And for the coming Ryzen! 
I hope everyone gets the servers they want!
From the OP:
One of my goals for this thread was to encourage quality LES posts by our Crunchy Neighbors about their Crunchy adventures.
Since we are about to upgrade beautiful Crunchy,
please allow me to ask if any of our current Crunchy Neighbors might like to share about their fascinating times aboard Crunchy?
Thanks!
I hope everyone gets the servers they want!
Crunchy has been a fantastic SSH jump host and testing bed for some bash shenanigans! I've surprisingly not nuked my VM to the point its needed a re-install (yet!)
@mikewazar Thanks Mike! So glad Crunchy has worked well for you!
I hope everyone gets the servers they want!
Good morning! Today's updates for beautiful Crunchy!
A possible new Neighbor might temporarily be sharing a test VPS.
Hopefully everyone is all ready to migrate? November 8 draws closer every day!
Please let me know about any issues!
Thanks everyone!
Special thanks to @crunchbits for beautiful Crunchy! 
I hope everyone gets the servers they want!
Curious, why are you using a mirror in Netherlands when crunchy is in Spokane?
The all seeing eye sees everything...
Thanks for that! I never noticed before! Here's /etc/apt/sources.list. You can see the "NL" entries.
Crunchy's Ubuntu was installed from the Crunchbits image. Maybe @sh97 knows why it's set to a NL mirror?
I hope everyone gets the servers they want!
Also:
Please see What is the /etc/apt/sources.list.d/ubuntu.sources.curtin file in Ubuntu 22.04? Can you please explain its purpose, meaning and how to use it?
I hope everyone gets the servers they want!
Hello!
Ubuntu's been wanting to update cloud-init for a few days, so I ran the update:
Unpacking cloud-init (24.3.1-0ubuntu0~22.04.1) over (24.2-0ubuntu1~22.04.1) ...Please let me know about any issues. Thanks!
Thanks to @crunchbits for beautiful Crunchy!
Tom
I hope everyone gets the servers they want!
Hello!
October 8, 2024 has arrived, so E3 Crunchy now has one month to go before expiration on November 8. Of course, as E3 Crunchy's final month progresses, we doubtless will hear details from @crunchbits about when and how E3 Crunchy will be upgraded to Ryzen.
E3 Crunchy has been working really very well, so I have asked @crunchbits for a price quote to enable me to keep the E3 server for personal use following Crunchy's move to Ryzen. However, if someone else wants to take over the E3 server, that's okay. Just let me know, and please make arrangements directly with @crunchbits.
Regretfully, I myself am unable to move to the new Ryzen Crunchy. Other projects are calling. Therefore, I need to ask at this time whether someone from our Community will please step forward and volunteer to take over administration of the new Ryzen Crunchy. Running our Community's server is a great way to pay back for all the benefits of LES membership! Crunchy also offers great opportunities to learn more about system administration. And, last but not least, Crunchy offers excellent resume value for anyone who is going to be looking for employment.
Server migrations are a time when backups are good to have. Everything probably will go perfectly, but . . . things happen . . . so I urge everyone to please backup immediately to more than one safe place.
Crunchy has been super great!
Thanks to @crunchbits for wonderful Crunchy! 
Thanks also to @babywhale for BashVM, the tool which has made most of Crunchy's VPs.S 
Thanks to LES for hosting this thread! 
Thanks to everyone who has been using a Crunchy VPS! 
Let's all continue to enjoy E3 Crunchy as we begin the time period for the upgrade to the new Ryzen Crunchy!
I hope everyone gets the servers they want!
Hello!
A few bits of Crunchy usage data in case anyone is interested:
I hope everyone gets the servers they want!
And, Ubuntu says
So maybe about 12 hours from now? I will post again before rebooting. Thanks!
I hope everyone gets the servers they want!
Okay, here comes the reboot!
I hope everyone gets the servers they want!
Looks like the reboot went okay, and all the BashVM VMs are reported as running. Please let me know about any issues. Thanks!
I hope everyone gets the servers they want!
With multiple servers (I believe you have now) have you thought about doing a cluster and migrating VMs between servers when you need to reboot or do other maintenance on one of them?
Yes, the idea has crossed my mind. If we were to try it, how should it be implemented? Thanks!
I hope everyone gets the servers they want!
I don't really have all of the necessary information to be able to say how it should be implemented. Is the hardware identical? If you have 128GB of memory on one server and only 64GB on another it would be hard to failover all of the VMs from the 128GB server to the smaller one. Do you already have shared storage?
You could go the replication-based failover approach, the live migration option or even just a script-based failover setup. You could do it all pretty easily with Proxmox but if that's not ideal for you. Evidian SafeKit is a commercial solution that would work. You should look into oVirt, pacemaker, drbd and keepalived. Whatever route you decide to go make sure you concentrate on your storage replication, network configuration, fencing and your monitoring.
Hello!
I just ran an upgrade:
No reboot needed. Since Qemu was upgraded, please let me know about any issues with VPSes. Thanks!
Thanks to @crunchbits for beautiful Crunchy!
Thanks to @babywhale for BashVM! 
I hope everyone gets the servers they want!
@FrankCastle
Thanks for your comment! Apologies for my tardy reply! Somehow, I missed this one!
No, Crunchy is different hardware from my other servers. Different processors, different amounts of RAM, different drives with different sizes.
However, the two servers I have in Germany are pretty close to identical. The only difference is the manufacturer of the drives, but the drives are of the same type and size.
The servers all have directly attached disks. No shared storage.
Looks like six possible solutions. Thanks x 6!
I hope everyone gets the servers they want!