won't boot after 8.0-RELEASE upgrade
Ivo Karabojkov
ivo at kit-bg.com
Tue Dec 8 22:09:17 UTC 2009
I have no problems with the hardware. In fact neither Release notes nor
UPDATING says anything about my possible (and actually occured) problems.
The only thing is:
“dangerously dedicated” mode for the UFS file system is no longer supported.
I never supposed that I'm using this mode. I format disks and install with
sysinstall without any special tuning for fdisk or disklabel. I prefer
standard options to ensure smooth future upgrades. So I'd like to know how
to distinguish mode of my current filesystems - is it standard or
dangerously dedicated?
Ruben de Groot wrote:
>
> On Mon, Dec 07, 2009 at 08:40:52AM -0800, Ivo Karabojkov typed:
>>
>> I'm sharing this experience to bring your attention to major advice in
>> the
>> update procedure - to take full backup.
>
> While not very new, that's allways good advice ;)
>
>> My question is: how can I guess the result - "Glory" or "Sorrow" BEFORE
>> starting the update?
>
> Before starting: read the relnotes and errata and search for possible
> problems, especially with your particular hardware.
>
> Then, if you decide to go ahead, install the new kernel and try to boot it
> in single user mode. This won't destroy anything and if you experience
> problems
> like missing devices you can easily back out by booting kernel.old.
>
> Ruben
> _______________________________________________
> freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe at freebsd.org"
>
>
--
View this message in context: http://old.nabble.com/won%27t-boot-after-8.0-RELEASE-upgrade-tp26628661p26701709.html
Sent from the freebsd-questions mailing list archive at Nabble.com.
More information about the freebsd-questions
mailing list