Upgrade 2.3 Improperly Dismounted root
-
Hello,
Running into this issue on my HA boxes where they were working great on 2.2.6 (failover, reboots, maintenance, etc…) but after the 2.3 upgrade I'm getting this after "Trying to mount Root from ufs:/dev/ufsid/ <mumble>[rw]…"
WARNING: / was not properly dismounted
Upgrade worked great my stand alone boxes but NONE of my HAs. I've wiped the drive, fresh install works great. Import the config, same result. Now, I went to the extent to backup each section then imported those one at a time into a fresh install and had no issues.
So my questions are: 1) WHAT would cause it to improperly dismount? 2) What in the config could be causing this?
One big item I noticed is missing on 2.3 is the 'tunables' do I need to remove these from the Backed up config before importing my config in 2.3
Please, help. Thanks in advance for your assistance. Looking to give out some +Karma</mumble>
-
Anyone?
Even if you aren't 100% sure but have hunch, it's more then I'm getting now.
-
I ran into the same issue. I did the update through the console and when it restarted i got weird issues on the web interface. I looked at the console and I lost all my IP address settings and I got the same error that you got with the CF not properly dismounted.
I had to do a fresh install and then when i did the restore config, thats when i ran into the same issue. I think what happened initially was that the upgrade tried to use the old config but there is something on it that messes up the CF mounting. So right now i have to manually reconstruct my configuration.HTH,
rafiks
-
Thanks for sharing!
High level observation: I noticed that the tunables in the 2.2.6 config are numerous but after the upgrade the 2.3 config the tunables section of the config are almost non existent. I'm wondering if there is a setting in the tunables that is causing it.
Also, I am not having any issues upgrading NON HA setups. So the question must be asked, what does CARP/HA, root mounting issues after upgrade, & lack of tunables in the config after the upgrade have in common?
Worth noting, Upgrade; mounting issue. Fresh build then import config; mounting issue. Fresh build then manually restore each section individually; NO mounting issue.
-
Now that 2.3 has been out for awhile, any thoughts as to what in the config would cause the drive to be dismounted improperly?
I'm honestly stuck.
I really want to upgrade my HA boxes but don't have the time to import each section one at a time. It appears that it tries to fix/repair something but eventually, after 1-3 reboots just sits there.
-
Are these full installs or nanobsd?
The issue rafiks noted is what happens with flash media that's very slow to rw->ro mount that isn't permanent rw.
https://redmine.pfsense.org/issues/6184that doesn't apply to full installs though.
-
Dang, that’s exactly the kind of issue I seem to have had, too!
https://forum.pfsense.org/index.php?topic=111080.msg618509#msg618509
I was mislead, because it had issues with interfaces, but since my interfaces never change (they are all functional, and built-in onto the motherboard, so invariable hardware config).
But some of the issues you mentioned, what works and what doesn’t, is a 100% match to my issues…
-
@cmb:
Are these full installs or nanobsd?
The issue rafiks noted is what happens with flash media that's very slow to rw->ro mount that isn't permanent rw.
https://redmine.pfsense.org/issues/6184that doesn't apply to full installs though.
I have a full install, with a modern SSD as drive. And the issue I have sounds 100% ident. Hence the wild goose chase in this line here (although some of the suggestions I made there remain valid regardless of the cause of the problem):
https://forum.pfsense.org/index.php?topic=111080.msg618509#msg618509
-
I had this same issue when trying to upgrade from 2.3.1 to 2.3.2 last night. After the update on the first reboot I received the same error message. Tried another cloned HDD and SATA port and the issue remained.
I reinstalled 2.3.1 on the exact same drive and restored my configuration to solve the issue. I will likely wait until the next update before trying again.