Hi Sivan, If you have a separate issue it's best to write a new email to the list with an appropriate subject, then it will make more sense to those reading or following.
It does sound like you have a few different issues here and I'm not sure I understand your configuration. I also think you might benefit from reading the documentation particularly the INSTALL file, the FAQs and afterboot man page. It seems like you don't understand some of the fundamental differences between Openbsd and other systems. Particularly the disk layout. Regards Ed Gray On Mon, 8 Mar 2021, 7:27 pm Sivan !, <s9952403...@gmail.com> wrote: > Thank you. One unresolved issue. While running fetch, there was an > error pop up that said /usr directory is out of space, though an > entire 250 GB nvme is for OpenBSD, almost with no user files, except > for the ports tree that was being downloaded b the fetch command. > When installing OpenBSD in a 250 GB nvme, I chose GPT and let the > installer decide on partitions. But something went wrong. > > My bios shows this in the hard disk list: > > line No 1: UEFI OS (samsung SSD EVO 970 Plus 250 GB) > line No 2: Samsung SSD 970 EVO Plus 250 GB (238476 MB) > (line No 3 : SATA ... # this is Ubunu > line No 4: SATA .... # this is CentOS) > > In BIOS if I choose item 1, it boots to OpenBSD > If I choose item 2, it shows a blank boot screen shows a one line > error message that says "no active partition" that is it. > > I ran gparted after booting the UEFI OS > > It started with the warning: Not all of the space available to > /dev/nvme0n1 appears to be used, you can fix the GPT to use all the > space (an extra 30 blocks) or > continue with the current setting? > > I chose "ignore", because I suspected that gparted probably saw the > UEFI boot content of (250 GB - 238476 MB) as 30 blocks of "unused" > space. > > Gparted shows: > > EFI System Area fat 16 > /dev/nvme0n1p2 480 KiB > Efi Sstem Aea Used 292 KiB > /dev/ nvme0n1p4 OpenBSD Area 232.89 GiB > > Does this imply that the 232.89 GiB is OpenBSD area, but somehow with > "no active partition" which is perhaps the reason why there was an > error message during fetch that said /usr directory is low on disk > space ? > > Thank you. > > > On Sun, 7 Mar 2021 at 15:54, Ed Gray <e.mask....@gmail.com> wrote: > > > > Glad you solved it. > > > > I would recommend running sysupgrade with the -n switch if you are using > the system. > > > > E.g. sysupgrade -s -n > > > > This delays the reboot but still prepares the upgrade. > > > > Upgrades are now completely automated but you still have to update > packages and your ports tree as well as the base system to keep everything > working properly. > > > > Regards > > Ed Gray > > > > On Sat, 6 Mar 2021, 6:19 pm Sivan !, <s9952403...@gmail.com> wrote: > >> > >> Solved. > >> sysupgrade -s > >> (after reboot, gnome loaded) > >> bash-5.0# uname -r > >> 6.9 > >> > >> On Sat, 6 Mar 2021 at 22:53, Sivan ! <s9952403...@gmail.com> wrote: > >> > > >> > /use/x11/ports/gnome make install didn't work. Images attached. > >> > > >> > On Sat, Mar 6, 2021, 22:12 Sivan ! <s9952403...@gmail.com> wrote: > >> >> > >> >> > >> >> dear Ed, > >> >> > >> >> It wasn't complicated at all in till the unintended upgrade, and I > wish to try and resolve this, even though I a person with copy&paste skills > in command line. OpenBSD 6.8 was booting fine with gnome, but now stuck in > xterm. > >> >> > >> >> Now in xsession cd/use/pets/gnome, typed make, it is making, will > report what happens. > >> >> > >> >> Thank you. > >> >> > >> >> > >> >> On Fri, 5 Mar 2021 at 23:23, Ed Gray <e.mask....@gmail.com> wrote: > >> >> > > >> >> > Hi Sivan, > >> >> > > >> >> > Sorry I've not had chance to look at everything you sent. > >> >> > > >> >> > Firstly the message about SSH keys sounds normal as this is part > of a normal X session startup. I suspect you have a key that has changed or > needs a passphrase entered and it's just picking it up when you try to > start X. > >> >> > > >> >> > The command history looks strange, you're running shutdown and > reboot and then other commands, unless these are from another session? > >> >> > > >> >> > Openbsd needs the -h option to both shutdown and power off the > machine or -r for reboot. > >> >> > > >> >> > Where is your startx program and is it a custom program? > >> >> > > >> >> > If you have done unintended upgrades and your /usr is also full > it's going to cause all sorts of problems. I would recommend reinstalling a > release from scratch if you can. > >> >> > > >> >> > Alternatively when the boot program runs you can choose bad.rd to > get the installer ramdisk and manually repair from there but it's a rather > complex process. > >> >> > > >> >> > On my system I had to boot bad.rd, type s for shell, run the > MAKEDEV script in /dev to create device nodes and then run disklabel > manually to rearrange volumes to make space. > >> >> > > >> >> > You would also need to grow or shrink the volumes. > >> >> > > >> >> > Regarding further troubleshooting of X sessions I would recommend > moving .xsession to .xsession.bak and starting with a fresh configuration. > >> >> > > >> >> > I would need to understand more about how you are starting gnome > like more details of any changes you made to the standard installation. > >> >> > >> >> I see gnome-sessiin-bi.core.core under / > >> >> and .xauthority under /root, as in the attached image > >> >> > Regards > >> >> > Ed Gray > >> >> > > >> >> > On Fri, 5 Mar 2021, 12:03 am Sivan !, <s9952403...@gmail.com> > wrote: > >> >> >> > >> >> >> Dear Stuart Henderson. > >> >> >> > >> >> >> I ran sysmerge. > >> >> >> > >> >> >> I posted, earlier in this thread, 11 images in response to Ed > Gray's > >> >> >> comment that I had not shared sufficient details. In addition > there > >> >> >> are four more images attached here that I think are important. > >> >> >> > >> >> >> One of these four images show the output of sysmerge and startx > commands. > >> >> >> Another is a screenshot of a strange prompt that appears before > boot, > >> >> >> it asks for the ssh password - not an encryption password, which > >> >> >> might be understandable, if I had an encrypted disk, I haven't > >> >> >> encrypted -- so why does it ask for the ssh password, before > asking > >> >> >> for a login password in X Term? > >> >> >> Two more pictures show the reboot sequence that is some sort of a > loop > >> >> >> when shutdown now command is issued as user or root, from x Term, > then > >> >> >> the main screen command line is seen flashing the status, and > >> >> >> invariably reboots the system in X Term. This happened in gnome > (or > >> >> >> gde) before the accidental upgrade to 6.9 beta and happens in x > Term > >> >> >> in 6.9 beta. > >> >> >> > >> >> >> Thank you. > >> >> >> > >> >> >> On Thu, 4 Mar 2021 at 14:10, Stuart Henderson < > s...@spacehopper.org> wrote: > >> >> >> > > >> >> >> > On 2021-03-03, Sivan ! <s9952403...@gmail.com> wrote: > >> >> >> > > After sysupgrade -s, during which there were two or more > automatic > >> >> >> > > reboots, freebsd, upgraded to 6.9 booted after asking > password for ssh key, > >> >> >> > > and started with xvterm console. Startx attempted to switch > to gui, but > >> >> >> > > returned errors. > >> >> >> > > > >> >> >> > > Please advise. > >> >> >> > > > >> >> >> > > Thank you > >> >> >> > > > >> >> >> > > >> >> >> > Make sure you have run sysmerge. > >> >> >> > > >> >> >> > If that doesn't help then we need more than just "returned > errors" - *what* errors? > >> >> >> > >
