Can someone give me a clue what went wrong in so described upgrade and what
made Kernel 8.0 REL not to see either disklabel nor even partition of my
gmirror? I need some advice prior starting upgrade process of the rest of my
servers. As you see in my previous posts the problem is NOT in DD mode!
As I guessed, I am using standard, not DD mode. Despite of this I was unable
to boot, and even more: FreeBSD 8.0 sysinstall did not find any partitions
neither on the (g)mirror, hardware RAID I described above or any individual
disks part of the RAID. I had to use FreeBSD 7.2 livefs to copy my
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
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
On Tue, 8 Dec 2009 14:09:16 -0800 (PST), Ivo Karabojkov i...@kit-bg.com wrote:
So I'd like to know how
to distinguish mode of my current filesystems - is it standard or
dangerously dedicated?
If you've first created a slice on the disk, and then
partitions inside the slice, it's standard mode,
On 12/8/09 5:21 PM, Polytropon free...@edvax.de wrote:
On Tue, 8 Dec 2009 14:09:16 -0800 (PST), Ivo Karabojkov i...@kit-bg.com
wrote:
So I'd like to know how
to distinguish mode of my current filesystems - is it standard or
dangerously dedicated?
If you've first created a slice on the
On 12/6/09 1:06 PM, Ivo Karabojkov i...@kit-bg.com wrote:
Since I have some servers to manage I am very interested how should I
upgrade to 8.0 Rel?
this is a big question.
for my production servers i like to keep things simple and use the generic
binary distribution. and i've been trying to
I had to reformat my drive since I had reached the point of no return... So
I am also nervous.
My first failure was with a-kind-of hardware raid, ar, built with cheap VIA
VT6421A controller. After installkernel the system refused to boot and on
its display was message hardware failure, you have
I don't think it's FreeBSD update. I always use CVSup and build world. So I
fall into the same hole with no way up.
I use gmirror, my device names are full including slice (e.g.
/dev/mirror/gm0s1a and it was produced from /dev/ad4s1a some years ago), so
I think I'm not using “dangerously
after running freebsd-update -r 8.0-RELEASE upgrade my system won't boot. it
gets stuck on mountroot and i can't find the magic word it wants.
the system used to have two sata drives /dev/ad4 and ad6. they were
partitioned and sliced using the deafaults that sysinstall suggested.
at the boot
On 12/3/09 11:14 AM, Tom Worster f...@thefsb.org wrote:
after running freebsd-update -r 8.0-RELEASE upgrade my system won't boot. it
gets stuck on mountroot and i can't find the magic word it wants.
the system used to have two sata drives /dev/ad4 and ad6. they were
partitioned and sliced
11 matches
Mail list logo