Re: won't boot after 8.0-RELEASE upgrade
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!
Ivo Karabojkov wrote:
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 data after I formatted one of the disks with new 8.0 sysinstall.
I think this makes our problem totally unexplained.
As an example I'll show you my unable to boot system with gmirror fstab:
# DeviceMountpoint FStype Options Dump
Pass#
/dev/mirror/gm0s1b noneswapsw 0
0
/dev/mirror/gm0s1a / ufs rw 1
1
/dev/mirror/gm0s1d /usrufs rw 2
2
/dev/mirror/gm0s1e /varufs rw,acls 2
2
/dev/acd0 /cdrom cd9660 ro,noauto 0 0
Something I've noticed: when formatting an entire disk with sysinstall
prior 7.0 its partition looks like this:
Offset Size(ST)End Name PType Desc Subtype
Flags
0 63 62- 12 unused0
63 781417602 781417664ad4s1 8freebsd 165
781417665 2990 781420654- 12 unused0
When formatted with later versions of sysinstall it looks like this:
Offset Size(ST)End Name PType Desc Subtype
Flags
0 63 62- 12 unused0
63 625142385 625142447ad4s1 8freebsd 165
I notice that the free part at the end is missing. My hardware raid,
described above in this thread, stores its metadata in the beginning of
the disk. Writes in the first sectors result in mirror break and the error
I wrote already. I know all of this because I did a lot of tests to help
all of you to find our problem out.
I have to say that my problems occured with system initially installed
with FreeBSD 5 or 6. One system with single drive installed with 7.2
(second example) upgraded with no problems.
I hope my tests will help to find out what happens wit our older
disklabelled systems.
Polytropon 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 disk, and then
partitions inside the slice, it's standard mode, e. g.
ad0 ab d e f g
{ [ (/) (swap) (/tmp) (/var) (/usr) (/home) ] }
s1
If you've omitted the slice, and created the partitions
on the disk device itself, it's dangerosly dedicated mode, e. g.
ad0
{ (/) (swap) (/tmp) (/var) (/usr) (/home) }
ab d e f g
You can tell by the existence of ad0s1[adefg] vs. ad0[adefg]
in /dev, or by trying to print the disks's slice table.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
freebsd-questions-unsubscr...@freebsd.org
--
View this message in context:
http://old.nabble.com/won%27t-boot-after-8.0-RELEASE-upgrade-tp26628661p26739396.html
Sent from the freebsd-questions mailing list archive at Nabble.com.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: won't boot after 8.0-RELEASE upgrade
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 data
after I formatted one of the disks with new 8.0 sysinstall.
I think this makes our problem totally unexplained.
As an example I'll show you my unable to boot system with gmirror fstab:
# DeviceMountpoint FStype Options Dump
Pass#
/dev/mirror/gm0s1b noneswapsw 0
0
/dev/mirror/gm0s1a / ufs rw 1
1
/dev/mirror/gm0s1d /usrufs rw 2
2
/dev/mirror/gm0s1e /varufs rw,acls 2
2
/dev/acd0 /cdrom cd9660 ro,noauto 0 0
Something I've noticed: when formatting an entire disk with sysinstall prior
7.0 its partition looks like this:
Offset Size(ST)End Name PType Desc Subtype
Flags
0 63 62- 12 unused0
63 781417602 781417664ad4s1 8freebsd 165
781417665 2990 781420654- 12 unused0
When formatted with later versions of sysinstall it looks like this:
Offset Size(ST)End Name PType Desc Subtype
Flags
0 63 62- 12 unused0
63 625142385 625142447ad4s1 8freebsd 165
I notice that the free part at the end is missing. My hardware raid,
described above in this thread, stores its metadata in the beginning of the
disk. Writes in the first sectors result in mirror break and the error I
wrote already. I know all of this because I did a lot of tests to help all
of you to find our problem out.
I have to say that my problems occured with system initially installed with
FreeBSD 5 or 6. One system with single drive installed with 7.2 (second
example) upgraded with no problems.
I hope my tests will help to find out what happens wit our older
disklabelled systems.
Polytropon 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 disk, and then
partitions inside the slice, it's standard mode, e. g.
ad0 ab d e f g
{ [ (/) (swap) (/tmp) (/var) (/usr) (/home) ] }
s1
If you've omitted the slice, and created the partitions
on the disk device itself, it's dangerosly dedicated mode, e. g.
ad0
{ (/) (swap) (/tmp) (/var) (/usr) (/home) }
ab d e f g
You can tell by the existence of ad0s1[adefg] vs. ad0[adefg]
in /dev, or by trying to print the disks's slice table.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
freebsd-questions-unsubscr...@freebsd.org
--
View this message in context:
http://old.nabble.com/won%27t-boot-after-8.0-RELEASE-upgrade-tp26628661p26706523.html
Sent from the freebsd-questions mailing list archive at Nabble.com.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: won't boot after 8.0-RELEASE upgrade
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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: won't boot after 8.0-RELEASE upgrade
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@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@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. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: won't boot after 8.0-RELEASE upgrade
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, e. g.
ad0 ab d e f g
{ [ (/) (swap) (/tmp) (/var) (/usr) (/home) ] }
s1
If you've omitted the slice, and created the partitions
on the disk device itself, it's dangerosly dedicated mode, e. g.
ad0
{ (/) (swap) (/tmp) (/var) (/usr) (/home) }
ab d e f g
You can tell by the existence of ad0s1[adefg] vs. ad0[adefg]
in /dev, or by trying to print the disks's slice table.
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: won't boot after 8.0-RELEASE upgrade
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 disk, and then
partitions inside the slice, it's standard mode, e. g.
ad0 ab d e f g
{ [ (/) (swap) (/tmp) (/var) (/usr) (/home) ] }
s1
If you've omitted the slice, and created the partitions
on the disk device itself, it's dangerosly dedicated mode, e. g.
ad0
{ (/) (swap) (/tmp) (/var) (/usr) (/home) }
ab d e f g
You can tell by the existence of ad0s1[adefg] vs. ad0[adefg]
in /dev, or by trying to print the disks's slice table.
thank you. that's good to know.
now that i know that my machine was not using DD mode before the upgrade to
8.0, it seems there ought to be a chance to make it boot.
the boot loader can see the partitions ad4s1[abdef] but the 8.0 kernel that
was installed with freebsd-update can't. isn't there some trick with dd to
zero out the geom metadata and makes the partitions look like ordinary
again?
(i was about 30 hours into copying the data off the disk to another machine
when my router died so i'm back at square 1 now, which was described in my
email at 11.14am est on dec 3rd.)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: won't boot after 8.0-RELEASE upgrade
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 develop a habit of using freebsd-update. but now i'm very nervous. unlike the machine that failed, my production systems have hw raid and don't use gmirror so i suspect the update may go smoothly. i also have a redundant config so i can take a machine offline to do the update. nevertheless, this experience has unnerved me. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: won't boot after 8.0-RELEASE upgrade
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 to destroy and build the mirror again. You will lose ALL data. Frightening, isn't it. So i tested the disks, found them OK and replaced the controller - newer MB with GEOM mirror. Reformat, of course, occurred and all the data was salvaged from the mirror disk. Now I see the card works. It's something with FreeBSD 8.0. This system was installed with FreeBSD 5.1 about may be 4 years ago and upgraded via cvsup til now. I'm sharing this experience to bring your attention to major advice in the update procedure - to take full backup. I think good RAIDs do not store data on the disks in readable by any adapter with same interface format. My question is: how can I guess the result - Glory or Sorrow BEFORE starting the update? Otherwise, needless to say, 8.0 works perfectly. I mostly use AMD64 version. Tom Worster wrote: 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 develop a habit of using freebsd-update. but now i'm very nervous. unlike the machine that failed, my production systems have hw raid and don't use gmirror so i suspect the update may go smoothly. i also have a redundant config so i can take a machine offline to do the update. nevertheless, this experience has unnerved me. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- View this message in context: http://old.nabble.com/won%27t-boot-after-8.0-RELEASE-upgrade-tp26628661p26679927.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: won't boot after 8.0-RELEASE upgrade
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 dedicated” mode... After the update I'm unable to mount root. Thanks God I have my old (7.2 release) kernel... Since I have some servers to manage I am very interested how should I upgrade to 8.0 Rel? Thanks in advance for all your advices! Regards, Ivo Tom Worster 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 using the deafaults that sysinstall suggested. at the boot prompt, lsdev says: disk devices disk0: BIOS drive C: disk0s1a: FFS disk0s1b: swap disk0s1d: FFS disk0s1e: FFS disk0s1f: FFS disk1: BIOS drive D: disk1s1a: FFS disk1s1b: swap disk1s1d: FFS disk1s1e: FFS disk1s1f: FFS which looks right, although i'm not familiar with the disk nomenclature. entering ? at mountroot mentions ad4 and ad6. geom_mirror was being used. i've tried saying load geom_mirror and/or enable-module geom_mirror at the boot prompt. neither made any difference. nothing i've said to mountroot works: ufs:/dev/ad4s1a ufs:/dev/ad6s1a ufs:/dev/mirror/gm0s1a ufs:/dev/disk0s1a ufs:/dev/disk1s1a does anyone know the magic word? i'd be very grateful. tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org -- View this message in context: http://old.nabble.com/won%27t-boot-after-8.0-RELEASE-upgrade-tp26628661p26667339.html Sent from the freebsd-questions mailing list archive at Nabble.com. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
won't boot after 8.0-RELEASE upgrade
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 prompt, lsdev says: disk devices disk0: BIOS drive C: disk0s1a: FFS disk0s1b: swap disk0s1d: FFS disk0s1e: FFS disk0s1f: FFS disk1: BIOS drive D: disk1s1a: FFS disk1s1b: swap disk1s1d: FFS disk1s1e: FFS disk1s1f: FFS which looks right, although i'm not familiar with the disk nomenclature. entering ? at mountroot mentions ad4 and ad6. geom_mirror was being used. i've tried saying load geom_mirror and/or enable-module geom_mirror at the boot prompt. neither made any difference. nothing i've said to mountroot works: ufs:/dev/ad4s1a ufs:/dev/ad6s1a ufs:/dev/mirror/gm0s1a ufs:/dev/disk0s1a ufs:/dev/disk1s1a does anyone know the magic word? i'd be very grateful. tom ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: won't boot after 8.0-RELEASE upgrade
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 using the deafaults that sysinstall suggested. at the boot prompt, lsdev says: disk devices disk0: BIOS drive C: disk0s1a: FFS disk0s1b: swap disk0s1d: FFS disk0s1e: FFS disk0s1f: FFS disk1: BIOS drive D: disk1s1a: FFS disk1s1b: swap disk1s1d: FFS disk1s1e: FFS disk1s1f: FFS which looks right, although i'm not familiar with the disk nomenclature. entering ? at mountroot mentions ad4 and ad6. geom_mirror was being used. i've tried saying load geom_mirror and/or enable-module geom_mirror at the boot prompt. neither made any difference. nothing i've said to mountroot works: ufs:/dev/ad4s1a ufs:/dev/ad6s1a ufs:/dev/mirror/gm0s1a ufs:/dev/disk0s1a ufs:/dev/disk1s1a does anyone know the magic word? i'd be very grateful. and i'm not getting anywhere with fixit using livefs. it says: ldconfig could not create the ld.so hints file and indeed programs like ls fail in a most ugly manner. is there anything useful to be done with the holographic shell? the only mount i can find is mount_nfs. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
