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!
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!