..well, that's interesting.. ..I'm obviously curious about why exactly the bot kicked me off. cause whose to say it won't happen again? I have zero interest in going through that experience again, as you can well imagine. and yes, I've re-installed ubuntu again, configurred it all nice, weeks ago, s...

dudes!! ..I've done some research now on what can cause this, and if my conclusions are accurate.. the last thing I said on telegram was the following: "that's what I'm going to do soon. this is all about.. I'll let fred explain." I can only conclude that it's because I said that that I go...

With apologies to the people I was chatting with, for no reason known to me, Telegram has.. decided to deny me access. I get: "Sorry, this group is not accessible". ..Maybe I've used up some kind of trial period or something? Or maybe it's my phone service interfering? no idea. It has alwa...

note that this will likely only work if you have 8 gigs of ram (or more), not 4 or less. because the vm has to be installed in an operating system, so you have operating system on vm on operating system. and this will take more than 4 gigs. ..just a cautionary note for anybody considering this on an...

ubuntu@ubuntu:~$ sudo blkid /dev/sdb1: UUID="2023-03-16-15-57-27-00" LABEL="Ubuntu 20.04.6 LTS amd64" TYPE="iso9660" PTUUID="405a23c7" PTTYPE="dos" PARTUUID="405a23c7-01" /dev/loop0: TYPE="squashfs" /dev/loop1: TYPE="squashfs...

I stumbled on some more things to try: ubuntu@ubuntu:~$ sudo fdisk -l Disk /dev/loop0: 2.23 GiB, 2392006656 bytes, 4671888 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/loop1: 63.29 MiB,...

I just realized that the info in that last post is invalid. it's for the usb-key, not the hard-drive. here is the info for the hard-drive: ubuntu@ubuntu:~$ sudo gdisk -l /dev/sda GPT fdisk (gdisk) version 1.0.5 Partition table scan: MBR: not present BSD: not present APM: not present GPT: not present...

ok.. now we're getting somewhere! ..I think.. first, I did a search for "No known boot loader is installed in the MBR of /dev/sda." and found a site where it recomended that I run gparted to check if my boot partition had the boot flag. I did that, curious to see what gparted would show, a...

..ok, got boot-repair to work.. ..not particularly encouraging, but perhaps enlightining for you.. boot-repair-4ppa203 [20230915_2207] ============================== Boot Info Summary =============================== => No known boot loader is installed in the MBR of /dev/sda. sdb: __________________...

Finally managed to get into rEFInd.. (..after hitting F12 during boot..) Options are: 1) Ubuntu (from the usb, I assume..) 2) Ubuntu 'safe graphics' (?) 3) OEM insall (for manufacturers) (?) 4) Boot from next volume (?) 5) UEFI Firmware Settings (..a place I've been before..) ok. boot from next volu...