Re: ports-mgmt/portconfig surprize
In message , Peter writes: > Folks, > > somebody got the idea to replace the dialog4ports options > configuring interface by something named 'ports-mgmt/portconfig'. > (And they did not even find it worth mentioning this in the > UPGRADING file.) > > Now this one looks terrible, the screen is garbled, and it is > quite unintellegible which line is currently entered. > See pictures here (old and new): > https://forums.freebsd.org/threads/2024q1-portbuild-trouble.91770/post-636816 > > What is happening: > I am starting a shell script. That fires up a bhyve. In the bhyve 'make' > is run with stdio connected to the second COM. > In the script on the host, bhyve is put in background, 'cu' is started > and connected to that second COM. There the dialog appears. > Since the script on the host is run from remote, it is run within > tmux. > Point is: it did work before. > > disappointed, > PMc > This should have been posted to freebsd-ports@. Next time use the correct ML. -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org e^(i*pi)+1=0
FreeBSD 13.2-STABLE can not boot from damaged mirror AND pool stuck in "resilver" state even without new devices.
Hello!
I have (remote) physical server with 2 SATA disks. These disks were partitioned with GPT into
"freebsd-boot" (ada{0|1}p1, legacy one, not EFI), "freebsd-swap" (ada{0|1}p2) and
"freebsd-zfs" (ada{0|1}p3).
Both disks were 512/512 (it looks important).
I have only one ZFS pool "zroot", mirror of "ada0p3" and "ada1p3".
I have very fresh "gptzfsboot" on both "ada0p1" and "ada1p1".
Now, ada0 failed. It was replaced by DC support with new disk, which is
512/4096.
After that my server fails to boot, gtpzfsboot from second disk (ada1) reports several
"zio_read error: 5" and
ZFS: i/o error - all block copies unavailable
ZFS: can't read MOS of pool zroot
after that.
I've booted to rescue Linux (unfortunately, there is NO rescue FreeBSD at
Hetzner anymore), and Linux could import (degraded) pool no problem. But Linux
has problems with detecting pool on partition, so I don't do nothing under
Linux.
I've checked "live" disk under Linux, though: it reads, SMART is clear,
everything is Ok.
I've booted FreeBSD 13.2 from installation ISO under qemu with physical
devices as disks. Then I partitioned fresh HDD and started disk replacement in
mirror. It worked, but resilver was unbearable slow. I stopped VM with FreeBSD
to continue process after normal boot.
NO LUCK. "zio_read error: 5", boot failed.
Then I've overwrite ada0 (new disk) with FreeBSD memstick IMG and boot it -
it can import pool from ada1p3 but, of course, resilver is stopped.
I've removed all faulted components, effectivly converting mirror to "simple" device.
But "zpool status" shows that there is resilver!
And "gptzfsboot" still CAN NOT read this ZFS pool and find loader!
Ok, I've converted swap to UFS boot form UFS. It works. It can use pool as root. But
pool still is "reslivering".
Now I have very strange situation:
(1) I have ZFS pool with 1 device which says:
% zpool status -v zroot
pool: zroot
state: ONLINE
status: One or more devices is currently being resilvered. The pool will
continue to function, possibly in a degraded state.
action: Wait for the resilver to complete.
scan: resilver in progress since Fri Jan 5 19:24:07 2024
750G scanned at 472B/s, 40.5G issued at 25B/s, 974G total
0B resilvered, 4.16% done, no estimated completion time
config:
NAMESTATE READ WRITE CKSUM
zroot ONLINE 0 0 0
ada1p3ONLINE 0 0 0
errors: No known data errors
%
(2) gtpzfsboot from very this system version can not read this pool and bot
from it
(3) kernel can use this pool as source of root (and all other) filesystems.
--
// Lev Serebryakov
Re: ports-mgmt/portconfig surprize
On Fri, Jan 5, 2024, 00:45 Peter wrote:
> Folks,
>
> somebody got the idea to replace the dialog4ports options
> configuring interface by something named 'ports-mgmt/portconfig'.
> (And they did not even find it worth mentioning this in the
> UPGRADING file.)
>
> Now this one looks terrible, the screen is garbled, and it is
> quite unintellegible which line is currently entered.
> See pictures here (old and new):
>
> https://forums.freebsd.org/threads/2024q1-portbuild-trouble.91770/post-636816
>
> What is happening:
> I am starting a shell script. That fires up a bhyve. In the bhyve 'make'
> is run with stdio connected to the second COM.
> In the script on the host, bhyve is put in background, 'cu' is started
> and connected to that second COM. There the dialog appears.
> Since the script on the host is run from remote, it is run within
> tmux.
> Point is: it did work before.
>
> disappointed,
> PMc
>
Thank you for the report
I am in a rural place far from my laptop.
I'll investigate the problem on Monday.
However you could run:
# pkg install dialog4ports
and adding
DIALOG4PORTS=${LOCALBASE}/bin/dialog4ports
to /etc/make.conf you can use the previous utility instead of portconfig to
set up ports options via a TUI.
Please next time open a new issue to https://gitlab.com/alfix/portconfig to
report a problem about portconfig.
Alfonso
Re: ports-mgmt/portconfig surprize
On Fri, Jan 05, 2024 at 07:56:16AM -0800, Cy Schubert wrote: ! ! This should have been posted to freebsd-ports@. Next time use the correct ! ML. Hi, I was thinking -ports is for malfunctioning individual ports. Whereas the matter at hand is about general infrastructure (every server needs some ports) and deploy. I currently have no idea where to find the people interested in that, but the port options setting being unconditionally interactive is a conflict with any automated deploy. I always have to hack and refactor this - and that new tool doesn't improve anything (in that regard), it just adds some malfunction (and forces me to understand the new code). But okay, when I'm in a relaxed mood again I will try and do a writeup of the issue and send it to -ports. Let's see if anybody there is interested... cheers, PMc
Re: ports-mgmt/portconfig surprize
In message , Peter writes: > On Fri, Jan 05, 2024 at 07:56:16AM -0800, Cy Schubert wrote: > ! > ! This should have been posted to freebsd-ports@. Next time use the correct > ! ML. > > Hi, > > I was thinking -ports is for malfunctioning individual ports. > Whereas the matter at hand is about general infrastructure (every server > needs some ports) and deploy. > > I currently have no idea where to find the people interested in that, > but the port options setting being unconditionally interactive > is a conflict with any automated deploy. I always have to hack and > refactor this - and that new tool doesn't improve anything (in that > regard), it just adds some malfunction (and forces me to understand > the new code). > > But okay, when I'm in a relaxed mood again I will try and do a writeup > of the issue and send it to -ports. Let's see if anybody there is > interested... > > cheers, > PMc portconfig and dialog4ports are not part of FreeBSD base. Both ports and it is the ports infrastructure, in /usr/ports/Mk, that calls them. Complaining about them on -current or -stable is a waste of everyone's time and will fall on deaf ears. portmgr made the decision to deprecate dialog4ports on Tue Oct 10 13:53:44 2023 (in /usr/ports/Scripts/dialog4ports.sh). If you have concerns about it, that's the forum to discuss it, or a PR. -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org e^(i*pi)+1=0
Re: ports-mgmt/portconfig surprize
On Sat, Jan 06, 2024 at 12:00:13AM +0100, Alfonso Sabato Siciliano wrote:
! Thank you for the report
!
! I am in a rural place far from my laptop.
! I'll investigate the problem on Monday.
Hi,
thank You very much for reporting back! Take Your time, relax, enjoy
the country; this is not an issue of hurry.
So let's find a place where we collect the info, next week.
! However you could run:
! # pkg install dialog4ports
! and adding
! DIALOG4PORTS=${LOCALBASE}/bin/dialog4ports
! to /etc/make.conf you can use the previous utility instead of portconfig to
! set up ports options via a TUI.
Thank You, that is fine - but then, I have to adapt my deploy system
to the new tooling, anyway, sooner or later. (This is an automated
system that provides for OS updates, images and pkgs in an integrated
fashion.)
! Please next time open a new issue to https://gitlab.com/alfix/portconfig to
! report a problem about portconfig.
Lucky You, I'm actually a customer of that company and therefore
allowed to login and participate.
cheerio,
PMc
