..No Boot Device Found. Press any key to reboot..

[mikethe1wheelnut]

"copy from terminal window text area selected by a mouse." -facepalm.. I think maybe I've been using freebsd (including in virtualbox) long enough that I forgot all about this option.. maybe it didn't work there..

ghostbsd@livecd ~> gpart show
=> 3 5767455 da0 GPT (29G) [CORRUPT]
3 26 1 freebsd-boot (13K)
29 51 - free - (26K)
80 4096 2 efi (2.0M)
4176 5763282 - free - (2.7G)

=> 3 5767455 iso9660/GHOSTBSD GPT (29G) [CORRUPT]
3 26 1 freebsd-boot (13K)
29 51 - free - (26K)
80 4096 2 efi (2.0M)
4176 5763282 - free - (2.7G)

=> 3 5767455 diskid/DISK-07009AED1044BA40 GPT (29G) [CORRUPT]
3 26 1 freebsd-boot (13K)
29 51 - free - (26K)
80 4096 2 efi (2.0M)
4176 5763282 - free - (2.7G)

..there is a lot more to respond do, so let's take it all piece-by-piece..

[mikethe1wheelnut]

Note that every time I submit a response, it gives me a white page. so far, I'm quitting firefox each time and re-opening. I'll try opening a new tab and closing the other instead.

"the info are not enough. either shae the whole log file" -don't yet know how to do this.. I'll stumble on it at some point, I'm sure. meanwhile, the problem has already occurred, so it may be too late to instruct the system to create one.. if the system needs such instruction.

"I assume you are trying to install GhostBSD on a disk with other Linux already installed. Thanks for your testing and your detailed explanations. Mike.
Explain what you wish to do with the GhostBSD install. I assume to install alongside other Linux installations on GPT partitioned disk."

I -was- trying to do precisely this. Now, if the whole system is messed up, and I still have no idea if it is, all bets are off.
-Now- what I want is essentially the same thing, but how exactly it get done, I don't really care. I'm pretty sure I had an mbr partitioned disk before and would have chosen to keep it if that could have worked, but if my computer has been nuked, all options are open.
At the end of -this- day, metaphorically speaking, I'd like to have the option of booting either into ubuntu or ghostbsd. I -have- heard that gpt is superior to mbr, even if mbr works fine for those applications it was designed for.

I -do- have something very specific I want to do. I want to install bpy (blender as a python module) into a virtual environment, and run codes using both it and numpy. bpy requires python 3.10, which is not the default python installed in ubuntu, so this is necessary. the folks over at freebsd also recomended using virtual environments. the whole purpose of this exploration is to find out how easy this is to do in bsd. seeing as there is no port yet for bpy. there -are- instructions for how to install it, but I have sufficiently little experience that I have no idea if they even apply to bsd.

I will also observe that ghostbsd, as I've experienced it so far, seems to freeze very easily. if I open too many web-pages, or if I scroll too fast in one, it goes down. I'm hoping that that is because I'm still in the live session..? I've never much used live sessions for anything, do I don't know. the install medium happens to use usb2, not 3..

[mikethe1wheelnut]

"Disable Secure Boot BIOS option. " -I am very hesitant to do this. my system warns me that I might not be able to boot at all if I do this. ..not that I can boot now.. I'm actually vague now as to what constitutes "booting". if I get a list of options when I hit F12 when the computer is starting up, I guess that doesn't qualify as booting..

"USE GPT partition tatble scheme, NOT MBR scheme Master Boot Record" -others seemed to think that mbr could still work. now you're telling me, quite clearly, that it is not expected to. so this is me wishing I'd waited for your answer to my previous question.

""ESP EFI FAT32 260 MB partition" This partition probably conflicts with existing partiton for FAT32 ESP EFI. Not sure how that looks." -now you're speeking greek. here's the info:

ghostbsd@livecd ~> camcontrol devlist
<SAMSUNG SSD SM841N mSATA 128GB DXM45D0Q> at scbus1 target 0 lun 0 (pass0,ada0)
< USB DISK 2.0 PMAP> at scbus2 target 0 lun 0 (da0,pass1)

ghostbsd@livecd ~> geom disk list
Geom name: ada0
Providers:
1. Name: ada0
Mediasize: 128035676160 (119G)
Sectorsize: 512
Mode: r0w0e0
descr: SAMSUNG SSD SM841N mSATA 128GB
lunid: 5002538500000000
ident: S1JXNYAF511288
rotationrate: 0
fwsectors: 63
fwheads: 16

Geom name: da0
Providers:
1. Name: da0
Mediasize: 31042043904 (29G)
Sectorsize: 512
Mode: r0w0e0
descr: USB DISK 2.0
ident: 07009AED1044BA40
rotationrate: unknown
fwsectors: 63
fwheads: 255

ghostbsd@livecd ~> gpart status
Name Status Components
da0p1 CORRUPT da0
da0p2 CORRUPT da0
iso9660/GHOSTBSDp1 CORRUPT iso9660/GHOSTBSD
iso9660/GHOSTBSDp2 CORRUPT iso9660/GHOSTBSD
diskid/DISK-07009AED1044BA40p1 CORRUPT diskid/DISK-07009AED1044BA40
diskid/DISK-07009AED1044BA40p2 CORRUPT diskid/DISK-07009AED1044BA40

ghostbsd@livecd ~> gpart show -lp or gpart show -rp
gpart: No such geom: or.

"t.me/ghostbsd help and support topic GhostBSD Telegram channel, You can attach screenshot fif" -methods of providing screenshots if I can't do it here, I presume. will get back to this.

[mikethe1wheelnut]

"t.me/ghostbsd help and support topic GhostBSD Telegram channel, You can attach screenshot fif" -methods of providing screenshots if I can't do it here, I presume. will get back to this. -> I'll get to this once I'm finished responding to everything here. I'm concerned that if I open too many windows, the live session will crash. which it probably would.

looking into the rEFInd thing now. I may have seen mention of such a thing elsewhere.. not enough though to learn what it actually was.

[mikethe1wheelnut]

..installing refind to the esp, via ubuntu live session..

[mikethe1wheelnut]

well..

ubuntu@ubuntu:~$ sudo dpkg-reconfigure refind
Installing rEFInd to the ESP...
Generating a RSA private key
.....+++++
.............................+++++
writing new private key to '//etc/refind.d/keys/refind_local.key'
-----
cp: error writing '/boot/efi//EFI/refind/refind_x64.efi': No space left on device
mkdir: cannot create directory ‘/boot/efi/EFI/tools’: No space left on device
mkdir: cannot create directory ‘/boot/efi//EFI/refind/keys/’: No space left on device
cp: cannot create regular file '/boot/efi//EFI/refind/keys/': Not a directory
cp: cannot create regular file '/boot/efi//EFI/refind/keys/': Not a directory
cp: cannot create directory '/boot/efi//EFI/refind/icons': No space left on device
mkdir: cannot create directory ‘/boot/efi//EFI/refind/keys’: No space left on device
cp: error writing '/boot/efi//EFI/refind/refind.conf': No space left on device
/usr/bin/iconv: error while closing output file: No space left on device

..great. what now?

[mikethe1wheelnut]

[..old post.., not sure if I actually posted it at all..]

I've been exploring bios/uefi settings. current boot mode is uefi.

I enabled legacy boot options, and that gave me Internal HDD and Onboard NIC as options. Internal HDD didn't work, and Onboard NIC gave me the impression it was waiting for something from me that it didn't get. This was the original failure message I got way back when.

[mikethe1wheelnut]

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 volume fails, similar errors as previously, and the first three all seem to do the same thing. ok, manufacturer mode does seem different, but not a solution to the problem.

next up, I'll try boot repair.

[mikethe1wheelnut]

..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: ___________________________________________________________________________

File system: iso9660
Boot sector type: Unknown
Boot sector info:
Mounting failed: mount: /mnt/BootInfo/FD/sdb: /dev/sdb already mounted or mount point busy.


================================ 0 OS detected =================================


================================ Host/Hardware =================================

CPU architecture: 64-bit
Video: Haswell-ULT Integrated Graphics Controller from Intel Corporation
Live-session OS is Ubuntu 64-bit (Ubuntu 20.04.6 LTS, focal, x86_64)

===================================== UEFI =====================================

BIOS/UEFI firmware: A11(4.6) from Dell Inc.
The firmware is EFI-compatible, and is set in EFI-mode for this live-session.
SecureBoot disabled (confirmed by mokutil).
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0000,0001
Boot0000* rEFInd Boot Manager HD(2,MBR,0x405a23c7,0x573ca4,0x1fc0)/File(\EFI\refind\refind_x64.efi)
Boot0001* UEFI: USB DISK 3.0 PMAP PciRoot(0x0)/Pci(0x1d,0x0)/USB(1,0)/USB(1,0)/HD(1,MBR,0x405a23c7,0x573ca4,0x1fc0)AMBO


============================= Drive/Partition Info =============================

Disks info: ____________________________________________________________________


Partitions info (1/3): _________________________________________________________


Partitions info (2/3): _________________________________________________________


Partitions info (3/3): _________________________________________________________


fdisk -l (filtered): ___________________________________________________________

Disk sda: 119.25 GiB, 128035676160 bytes, 250069680 sectors
Disk sdb: 57.77 GiB, 62008590336 bytes, 121110528 sectors
Disk identifier: 0x405a23c7
Boot Start End Sectors Size Id Type
sdb1 * 0 8498951 8498952 4.1G 0 Empty
sdb2 5717156 5725283 8128 4M ef EFI (FAT-12/16/32)
sdb3 8499200 121110527 112611328 53.7G 83 Linux

parted -lm (filtered): _________________________________________________________

sda:128GB:scsi:512:512:unknown:ATA SAMSUNG SSD SM84:;
sdb:62.0GB:scsi:512:512:unknown: USB DISK 3.0:;

blkid (filtered): ______________________________________________________________

NAME FSTYPE UUID PARTUUID LABEL PARTLABEL
sda
sdb iso9660 2023-03-16-15-57-27-00 Ubuntu 20.04.6 LTS amd64
├─sdb1 iso9660 2023-03-16-15-57-27-00 405a23c7-01 Ubuntu 20.04.6 LTS amd64
├─sdb2 vfat 1544-BBA2 405a23c7-02
└─sdb3 ext4 877155b2-880a-4ccb-970f-ba7d6a3afe77 405a23c7-03 writable

Mount points (filtered): _______________________________________________________

Avail Use% Mounted on
/dev/disk/by-label/writable[/install-logs-2023-09-15.4/crash] 49.9G 0% /var/crash
/dev/disk/by-label/writable[/install-logs-2023-09-15.4/log] 49.9G 0% /var/log
/dev/sdb1 0 100% /cdrom

Mount options (filtered): ______________________________________________________


======================== Unknown MBRs/Boot Sectors/etc =========================

Unknown MBR on /dev/sda

Unknown BootLoader on sdb




Suggested repair: ______________________________________________________________

The default repair of the Boot-Repair utility would not act on the boot.

[mikethe1wheelnut]

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, and.. nothing! it shows the entire hard-drive un-allocated! ..very interesting. so I did a search for -that-. Found another site that recomended running

sudo gdisk -l /dev/sdb

-that- instruction has now given the following:

ubuntu@ubuntu:~$ sudo gdisk -l /dev/sdb
GPT fdisk (gdisk) version 1.0.5

Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present


***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***************************************************************


Warning! Secondary partition table overlaps the last partition by
33 blocks!
You will need to delete this partition or resize it in another utility.
Disk /dev/sdb: 121110528 sectors, 57.8 GiB
Model: USB DISK 3.0
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 4611E155-AD0C-40B5-93A0-47B0D0044FB2
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 121110494
Partitions will be aligned on 4-sector boundaries
Total free space is 8491038 sectors (4.0 GiB)

Number Start (sector) End (sector) Size Code Name
2 5717156 5725283 4.0 MiB EF00 EFI system partition
3 8499200 121110527 53.7 GiB 8300 Linux filesystem

..it occurs to me that that might actually be helpful for you in re-coding your thing so that things like this don't happen again..?