Upfail to 2.2
-
same thing
had to reconnect the old ddwrt router
after upgrade, system wont connect to the net and cpu usage shows 100%…
may need to reinstall manually
really wanted to avoid having to reinstall, loads of settings etc…...
did the backup before upgrade thing, but that's pretty useless if i can't access the hard drive with the backup on it.
-
Seems to match up to this similar situation.
https://forums.freebsd.org/threads/nanobsd-9-1-system-hangs-at-boot-root-mount-waiting-for-graid.38551/That server looks like it has one of those Intel fake RAID cards, where the OS can see the individual disks as well as the RAID array. Seems might be something along the lines of GEOM seeing something on those underlying disks.
At the initial boot menu, escape to the loader prompt and run:
set kern.geom.raid.enable="0" bootI suspect it'll boot with that. If it does, edit (or create) /boot/loader.conf.local and add this line:
kern.geom.raid.enable="0" -
same thing
after upgrade, system wont connect to the net and cpu usage shows 100%…
that has nothing to do with OP's issue, please start a new thread describing what you're seeing. If you have 100% CPU usage, what does "top -SH" show? "Won't connect to the net" could be countless different things, add as many details as you can about what works and what doesn't (can you hit the LAN IP, does DNS work, can you ping Internet by IP, ping work from Diag>Ping on firewall, etc.).
-
@cmb:
Seems to match up to this similar situation.
https://forums.freebsd.org/threads/nanobsd-9-1-system-hangs-at-boot-root-mount-waiting-for-graid.38551/That server looks like it has one of those Intel fake RAID cards, where the OS can see the individual disks as well as the RAID array. Seems might be something along the lines of GEOM seeing something on those underlying disks.
At the initial boot menu, escape to the loader prompt and run:
set kern.geom.raid.enable="0" bootI suspect it'll boot with that. If it does, edit (or create) /boot/loader.conf.local and add this line:
kern.geom.raid.enable="0"that's the magic bullet, lol.
-
Good, glad that worked. That might be a GEOM bug in FreeBSD 9.x-10.x, though those Intel cards presenting their disks and the array is just wrong… not the best things in the world (I'd use gmirror from our installer and disable the RAID on those cards, personally).
Regardless, that setting will persist across upgrades and that problem won't happen again. Remember if you replace the disks or blow it away and reinstall at some point that you'll need to put it back.
-
@cmb:
Good, glad that worked. That might be a GEOM bug in FreeBSD 9.x-10.x, though those Intel cards presenting their disks and the array is just wrong… not the best things in the world (I'd use gmirror from our installer and disable the RAID on those cards, personally).
Regardless, that setting will persist across upgrades and that problem won't happen again. Remember if you replace the disks or blow it away and reinstall at some point that you'll need to put it back.
you're still not off the hook for making me use vi, lol.
-
Other editors are available. ;)
Steve
-
Other editors are available. ;)
Steve
I use "ee" which is on the standard pfSense distribution. It actually tells you how to exit and save changes :)
-
I get a sudden overwhelming urge to wear bell-bottom jeans and watch starshy and hutch every time I use vi
-
Ha!
I'm all about Easy Editing. I've been stuck in some obscure vi mode too many times. ::)
Steve
