System General Logs flooded

Ramosel

Thanks Gents!

I'll get to it a bit later... tractor is getting warmed up, got work to do.

Steve, if your people do need a real world test on a fix, I'll be glad to run it up on my spare.

Rick

Ramosel

@stephenw10 said in System General Logs flooded:

You can interrupt the boot process at the loader menu to reach the loader prompt. Then enter there:
set hint.ichsmb.0.disabled=1
boot

Great Advice, this works fine.

@johnpoz
John, I know you had a lot of good info on moving to ZFS back when 2.5.2 was new... Do you have anything written up (or committed to memory) on best practices when setting up ZFS on your 4860?

Rick

johnpoz

@ramosel so not really - just using default whatever pfsense sets up out of the box to be honest.

Traveler

@Ramosel @johnpoz Would it be possible to accomplish this with the "System patches" mechanism by creating a custom patch?

Traveler

Never mind. Just added with "vi".

Ramosel

@Traveler said in System General Logs flooded:

Never mind. Just added with "vi".

@Traveler said in System General Logs flooded:

@Ramosel @johnpoz Would it be possible to accomplish this with the "System patches" mechanism by creating a custom patch?

Good question... I'm sure it could have been created as a patch.

Are you installing the latest version (as of today, 23.05.1)?
Is it still even needed? I haven't removed the line I put into /boot.loader.conf.local.

I would have thought they would have included a system check on the pfSense+ version and accounted for this issue in the update.

Rick

Traveler

@Ramosel It definitely was still needed. The line made the logs quiet.

Ramosel

@Traveler said in System General Logs flooded:

@Ramosel It definitely was still needed. The line made the logs quiet.

Thanks for the info. I guess I need to edit the file when I build my new install stick.

Stephen, since this affects Netgate hardware, is there any effort being put into testing for the affected hardware and fixing the issue on the fly? Or will this just always be a problem from now on?
Not complaining, just trying to figure out what I need to put into my recovery docs or not.

Rick

stephenw10

Yes, it's fixed 'correctly' upstream now. it just wasn't accepted soon enough to be included in 23.05.1.

https://reviews.freebsd.org/D39966

It will be fixed in 23.09.

Steve

Ramosel

@stephenw10 said in System General Logs flooded:

Yes, it's fixed 'correctly' upstream now. it just wasn't accepted soon enough to be included in 23.05.1.

https://reviews.freebsd.org/D39966

It will be fixed in 23.09.

Steve

You guys are the BEST.

Thanks,
Rick