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 bootThen you can boot into the installer as normal. You can also do that at the first boot after install so it boots normally before adding the loader.conf.local file.
Steve
-
@ramosel said in System General Logs flooded:
do a new install the screens are just flooded with the "ichsmb0" error as well...
Really? hmm I didn't put this in until after I had updated, and I don't recall having any problem with accessing the gui.. Maybe I updated it before I accessed the gui? No I recall it logging in, pretty sure..
But I was still connected to the console, and yeah the console was not able to be used with the flooding. I always console in when doing an update so I can watch the actual progress of the update.
I just ssh'd in to pfsense and created the file and put in the info, and then did a reboot.. Don't recall if did the reboot from my ssh session or from the gui though?
I had seen the info about it, and was going to do it before I did the update, but then I was like oh its just console log - wanted to see how bad it was spamming, etc. So kind of glad I didn't put it in before.
Yah know - now that I think about, yeah I was on the gui, wanted to make sure the few packages I had left were updated, etc. before did the reboot after update.
-
@stephenw10 I heard from Jordan and it sounds like someone is working on a "fix" and that there might be a revision coming. I'm in no hurry so I told him to let your support folks know I have the backup (offline) SG-4860 that I always update from the boot thumbdrive first so I know I have a ready to go viable backup BEFORE I update my production router. So I'm happy to test any potential revision/fix/update if they need a guinea pig.
-
@johnpoz said in System General Logs flooded:
@ramosel said in System General Logs flooded:
do a new install the screens are just flooded with the "ichsmb0" error as well...
Really? hmm I didn't put this in until after I had updated, and I don't recall having any problem with accessing the gui.. Maybe I updated it before I accessed the gui? No I recall it logging in, pretty sure..
Thanks John, This wasn't the gui.
Old habits die hard... Since I have a second SG-4860 I always start with a bare-metal rebuild on it to prove I can function should I have a catastrophic outage. When you boot to a thumbdrive the system essentially comes up to the Text based config boxes (not gui) where you set your build parameters... ie: selecting ZFS/UFS, key mapping, etc (YOU know, the old DOS style setup boxes). The ichsmb0 flooding is already in full swing by that point and just trashes the screen. At best you can only go with defaults. I'm not in any hurry to update so I think I'll just wait (see my response to Steve). I'll be glad to test a fix if they need it... as it will be non-destructive to my production router.
Normally that initial build on the secondary box is just overkill... this time it caught something.
Rick
-
If you upgraded from the webgui you likely wouldn't notice this at all until you next connect to the console. You can add the loader line from there and never see that error.
-
@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 bootThen you can boot into the installer as normal. You can also do that at the first boot after install so it boots normally before adding the loader.conf.local file.
Cool, thanks! I'll give that a shot this morning. Well, after I move a $hit-ton of snow.
Once I get the backup router stable on 23.01... Is there any issue with setting that config under the working 22.05 build before I start the update??
Rick
-
@ramosel said in System General Logs flooded:
Is there any issue with setting that config under the working 22.05 build before I start the update??
Nope - that was what I was originally going to do, and prob should of done. But it was good experience to see the flooding, it is a lot! ;)
-
@johnpoz said in System General Logs flooded:
it is a lot! ;)
It sure is! Interestingly it doesn't actually prevent you installing if you know what the expected input is. Obviously that's not an option for many people but if you just keep hitting return it will install with the default values.
Steve
-
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
-
@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 bootGreat 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
-
@ramosel so not really - just using default whatever pfsense sets up out of the box to be honest.
-
-
Never mind. Just added with "vi".
-
@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
-
@Ramosel It definitely was still needed. The line made the logs quiet.
-
@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
-
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
-
@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
