14:14:48 <mage> any idea if FreeBSD support RDMA on the target-side of iSCSI ?
14:46:04 <mage> hello, we have to modernize and merge some of our storage infrastructure. One of the merge side ("my" side) uses FreeBSD and no SAN-like storage (only DAS) and the other an HPE MSA 2060, connected (with MPIO) to two windows server through SAS
14:47:41 <mage> we received an offer to replace the MSA side part (MSA 2070, VMWARE, 2 servers, setup, etc) which is ~90 000€
14:48:46 <mage> the load is heavy on this side (~500+ clients)
14:51:32 <mage> do you think it is feasible to replace all of this with two supermicro-like servers backed by SSD (or flash), connected to a 10GB switch (4x10GBITS with LACP), create ZVOLs on each server and export them through iSCSI to the Windows and FreeBSD hosts ?
14:53:46 <mage> I've already played with iSCSI and setuped something like this in my $homelab and it worked well (for the little tests I made). But I haven't any idea if it would handle the load like the MSA does ..?
15:45:44 <rwp> mage, A while back someone had a problem with Samsung EVO QVO SSDs in a high rate storage array.  Something you might want to be aware of.  https://lists.freebsd.org/archives/freebsd-hackers/2022-April/000954.html and https://lists.freebsd.org/archives/freebsd-hackers/2022-April/000964.html
19:52:26 <Retrofan> Hi
19:54:25 <Retrofan> Guys remember me from yesterday.. I got access to an another pc
19:56:08 <Retrofan> After I rebooted for freebsd install, the system is no more working; due to removed amdgpu pkgs
19:56:29 <Retrofan> I forget to remove them from loader.conf and rc.conf
19:58:18 <Retrofan> I tried to enter the loader promat "OK" and "unload" all modules, then boot with the kernel only in single user mode
19:58:42 <Retrofan> I used "boot /boot/kernel/kernel -s"
19:58:54 <Retrofan> -s for single as far as I know
19:59:11 <Retrofan> But no luck still the same
20:00:05 <Retrofan> with my access to an another pc, I will try internet..
20:00:17 <Retrofan> *searching
20:23:04 <CrtxReavr> I think -s is a linux thing.  The kernel should pause at a menu, allowing you to chose single user and some other options.
20:25:04 <Retrofan> As I know at that menu..
20:25:21 <Retrofan> the kernel still not loaded
20:26:12 <Retrofan> I used that command; to continuethe boot with the kernel module only..
20:26:58 <Retrofan> CrtxReavr: I entered the loader promat
20:26:59 <Retrofan> (number 3) from that menu
20:28:19 <Tenkawa> Retrofan: this on x86?
20:28:22 <Retrofan> yeah
20:28:34 <Tenkawa> interrupt boot and set boot_single
20:28:37 <Tenkawa> then boot
20:28:41 <Tenkawa> see if that works
20:31:25 <CrtxReavr> It'll mount / read only.  You'll need to run 'mount -u -w /' (I think.) to write to it.
20:33:55 <Retrofan> Tenkawa: My problem is stopping the system from loading gpu modules, not booting in single user..
20:34:43 <Tenkawa> then why were you adding -s?
20:34:53 <Tenkawa> thats single user at best
20:35:22 <Retrofan> To prevent kernel from loading modules
20:35:49 <Retrofan> the modules is loaded from
20:36:02 <Retrofan> loader.con and rc.conf at kernel level
20:36:35 <Tenkawa> set module_blacklist='some previously present modules nvidia nvidia-modeset'
20:36:50 <Tenkawa> there's an example
20:37:06 <Retrofan> already done... then the rc.conf load them
20:37:10 <Retrofan> *will
20:37:34 <Retrofan> loader.conf at the boot level
20:37:49 <Retrofan> rc.conf is at kernel level as I know
20:37:56 <Tenkawa> are you using the "boot" command .. you can't yse the menu
20:37:58 <Tenkawa> er use
20:38:12 <Retrofan> and the twice have amd modules added
20:38:46 <Retrofan> boot? yeah I am at OK promat..
20:39:42 <Retrofan> then I tried to load only the kernel  "boot /boot/kernel/kernel"
20:39:53 <Retrofan> with -s for single mode...
20:40:08 <Retrofan> But no luck :(
20:41:14 <Retrofan> Unix learned me pain XD
20:41:53 <Tenkawa> Is the GPU locking up your display?
20:42:17 <Retrofan> yeah.. its an amd readeon bug
20:42:23 <Tenkawa> ouch
20:43:12 <Retrofan> I remember years ago first time installed freebsd, it took me 2weeks to make gpu working for x11
20:43:24 <Retrofan> due to that bug
20:43:58 <Retrofan> I think the problem is in rc.conf
20:47:10 <Retrofan> wait..
20:47:42 <Retrofan> Could I use rescue commands in OK promat?
20:47:57 <Retrofan> like /rescue/vi ?
20:47:58 <ek> Retrofan: Might be fastest to just boot into mfsBSD, mount your boot and root and edit the .conf files.
20:48:25 <Retrofan> on USB?
20:50:04 <ek> Retrofan: Sure. However you'd like to boot it.
20:50:18 <Retrofan> I think I can't do that
20:50:36 <Retrofan> No media right now :(
20:50:48 <Retrofan> *I own
20:50:56 <ek> PXE?
20:52:10 <Retrofan> No PXE or like that stuff
20:52:32 <Retrofan> I am using freebsd as my Workstation desktop stuff
20:52:46 <Retrofan> *for
20:54:41 <ek> Do you know the exact module names you're loading?
20:55:24 <ek> Does: set module_blacklist="amdgpu drm whatever"
20:55:27 <ek> ANd then: boot
20:55:33 <ek> ... not work?
20:59:46 <Retrofan> Yeah
21:00:05 <Retrofan> Wait..
21:00:20 <Retrofan> I blacklisted them before that
21:00:50 <Retrofan> I readed now that makes loader pass to rc.conf
21:01:09 <Retrofan> maybe if I set blacklist to nothing will work?
21:01:32 <Retrofan> + unload the modules like I did before
21:04:06 <Retrofan> not working :(
21:04:23 <ek> What did you try?
21:04:39 <Retrofan> set blacklist to nothing
21:04:45 <ek> I'd think blacklisting would keep both loader.conf and rc.conf from loading those modules.
21:04:45 <Retrofan> + unload the modules like I did before
21:05:31 <Retrofan> So there is some module that I don't know is caseing that?
21:05:50 <ek> Just try an 'unload' and then 'set module_blacklist="vesa"' and then a 'boot' at the OK prompt.
21:06:07 <ek> Retrofan: Could be another module. Hard to say without seeing it.
21:06:17 <Retrofan> yeah
21:06:18 <kevans> no
21:06:22 <Retrofan> what?
21:06:29 <kevans> module_blacklist only works for loader
21:06:30 <ek> Err... 'set module_blacklist="amdgpu whatever else"'. Not vesa.
21:06:38 <ek> kevans: Ah. Bummer.
21:06:51 <kevans> thre's a separate thing for devmatch, if you're actually getting it picked up there. haven't read scrollback
21:07:09 <kevans> devmatch_blocklist in rc.conf
21:07:29 <Retrofan> kevans: yeah for loader.conf
21:07:39 <Retrofan> devmatch_blocklist for rc.conf?
21:08:17 <kevans> boot -s is fine, but the -s needs to be before a filename
21:08:22 <ek> I was thinking if you could get past loader.conf, a 'boot -s' would get your through rc.conf.
21:08:44 <Retrofan> yeah that what I am saying
21:08:51 <Retrofan> I need to stop rc.conf
21:09:16 <kevans> if you're loading the gpu module, you only need to worry about devmatch. we've long-since blocked them from being loaded accidentally in loader.conf
21:09:46 <kevans> (boot_single is another way to spell `boot -s`)
21:10:45 <kevans> if you boot -s then you're interrupting the boot sequence prior to where /etc/rc would've been run at all, yes
21:10:48 <Retrofan> Ah, I remembered I done that long ago; to make modules only load from rc.conf
21:11:02 <Retrofan> due to bug when been loaded from loader.conf
21:11:25 <kevans> yeah, we stopped that common footgun around 12.0
21:11:39 <Retrofan> 12.0?
21:11:40 <kevans> recently added nvidia modules to the list because they will similarly blow up if loaded that early
21:11:44 <kevans> freebsd 12.0
21:11:49 <Retrofan> I am 13.2
21:11:52 <kevans> yes
21:11:56 <Retrofan> and bug is still there
21:12:02 <kevans> not the same bug, no
21:13:04 <Retrofan> So now add them to the devmatch block list?
21:13:08 <ek> Retrofan: I believe kevans is strictly talking about module loading conditions. Not the module itself. Do what kevans said and use devmatch_blocklist.
21:13:40 <Retrofan> yeah I understood
21:24:04 <ek> Retrofan: Are you saying this module is crashing the system or are you just not able to get to a login prompt after boot?
21:24:23 <Retrofan> look like I can't add more than one module in devmatch_blocklist
21:24:24 <ek> Sorry. Kind of scrolling through the issue as mentioned above.
21:24:35 <kevans> note that ... ok
21:25:34 <kevans> i'd put $$ that they're just reassigning to module_blocklist multiple times rather than space-separated
21:26:29 <Retrofan> sorry my internet
21:26:33 <kevans> Retrofan: you're using space-separated value and not reassigned to the same variable multiple times, right?
21:26:55 <Retrofan> it crashes my screen, can't seee anything
21:27:25 <Retrofan> kevans: mm, yeah
21:27:55 <ek> Retrofan: Have you tried CTRL+F1 (or F2, or F3, etc...) to get to a new tty?
21:28:14 <Retrofan> tried it before
21:28:20 <Retrofan> it's an old bug
21:28:23 <Retrofan> I know it
21:29:19 <Retrofan> I can write.. but I don't know what I do..
21:29:30 <Retrofan> *am doing
21:30:21 <ek> Retrofan: Is it ZFS?
21:30:25 <Retrofan> no
21:31:09 <ek> If you can write blindly, have you tried su'ing to root and then "mv /etc/rc.conf /etc/rc.conf.orig" and rebooting?
21:31:31 <ek> I'm still surprised that a single-user mode boot won't allow you in.
21:31:41 <Retrofan> ah
21:31:52 <kevans> i don't think i've seen any evidence that they've actually tried it
21:31:56 <Retrofan> look like that will fix it :)
21:32:20 <Retrofan> Unix you need to think outter the box XD
21:32:28 <ek> kevans: There was mention earlier they tried single-user but it didn't work (I think?)
21:32:37 <Retrofan> multi user work
21:32:52 <Retrofan> I can write blindly
21:32:57 <kevans> they tried `boot <kernel> -s`, but didn't seem to confirm that they'd tried boot_single, the menu option, or the more correct `boot -s <kernel>`
21:33:11 <Retrofan> but never thinked of moving rc.conf file to .old
21:33:59 <ek> Retrofan: Did you not try the boot menu option for single-user mode?
21:34:29 <ek> I figured that was the very first thing tried.
21:36:03 <Retrofan> tried
21:36:37 <Retrofan> tried boot_single
21:36:42 <Retrofan> no luck
21:36:53 <kevans> can you define 'no luck'?
21:37:32 <kevans> if you booted into single user you would not be having the same problem unless you've misdiagnosed it and presented an X-Y problem
21:38:21 <kevans> we drop into single-user in init before it had a chance to invoke /etc/rc, devmatch isn't a thing until we've fired up devd
21:39:05 <kevans> or maybe I misunderstood: do you just never have a console on this machine unless you have amdgpu loaded?
21:39:50 <Retrofan> tried to rename the /etc/rc.conf no luck :(
21:40:27 <Retrofan> No consle until amdgpu load
21:40:51 <kevans> ok, so I misunderstood all the way back here: 15:33 < Retrofan> Tenkawa: My problem is stopping the system from loading gpu modules, not booting in single
21:41:22 <kevans> we don't have a console driver for whatever reason (maybe it's just not associated) and you're trying to recover amdgpu, not prevent it from loading
21:41:35 <Retrofan> wait
21:42:11 <ek> Yup. Now I'm confused.
21:42:21 <CrtxReavr> kevans, the lack of luck.
21:42:53 <Retrofan> I remember It was loading the console back in the day without any modules.. but resolution is low and no x11
21:43:15 <Retrofan> I can't recover amdgpu, it deleted while my upgrade process!
21:43:24 <kevans> are you setting kern.vty in loader.conf?
21:43:52 <kevans> if you're relying on vesa, I don't remember if vesafb landed in time for 13.2.  try dropping to the loader prompt and switching to syscons. set kern.vty=sc
21:43:54 <Retrofan> the system is loading a non-exist module
21:44:19 <Retrofan> ok I will try
21:44:22 <kevans> (er, vbefb)
21:45:40 <kevans> it seems to have landed in time for 13.0, but still worth trying
21:49:35 <Retrofan> kevans: amm, it's just freeze
21:49:40 <Retrofan> the system
21:49:54 <Retrofan> even with unload and single user mode
21:53:11 <kevans> define freeze. blank screen? tail end of loader output? other?
21:55:12 <Retrofan> no blank, just tail end of loader output
21:55:17 <Retrofan> then freeze
22:00:40 <Retrofan> kevans: Need I to try vbefb?
22:14:12 <Retrofan> haha
22:14:31 <Retrofan> https://www.youtube.com/watch?v=lJdljt8c0oY
22:14:54 <Retrofan> this the last thing I had done before I moved form WIN to BSD
22:20:31 <Retrofan> To late
22:20:40 <Retrofan> Going for sleep
22:21:30 <Retrofan> see you tomorrow
22:23:10 <Macer> what version of gnome is in the 14 repo?