Date: Mon, 28 Nov 2005 14:59:33 +0200 From: Kirill Klimov <kir@fm.com.ua> To: freebsd-geom@freebsd.org Subject: GEOM mirror newly added HDD booting problem Message-ID: <1011050708278.20051128145933@kserver.kiev.ua>
next in thread | raw e-mail | index | archive | help
Hi list I'm having GEOM mirror setuped on slices of 2 disks. It was setuped as described at http://people.freebsd.org/~rse/mirror/ It has 2 consumers: ad0s1 and ad2s1. # gmirror status Name Status Components mirror/gm0s1 COMPLETE ad0s1 ad2s1 I was needed to replace ad2 with new HDD. What I've done: - removed HDD from the system (physically) - removed it from RAID (gmirror forget gm0s1) - added new HDD to the system (physically). It has been marked as ad2. - dd if=/dev/zero of=/dev/ad2 bs=512 count=79 - created 2 partitions with fdisk. 1st one exactly the same size as ad0s1 also setuped ad2s1 as active slice. - added newly created slice to the mirror (gmirror insert gm0s1 /dev/ad2s1) Wait until new consumer has been synchronised, so now RAID is complete: 14:33(root@box):[/root]# gmirror status Name Status Components mirror/gm0s1 COMPLETE ad0s1 ad2s1 The problem: I wanted to test new configuration - has rebooted the system and turned off 1st HDD (ad0): I wasn't able to boot having following error on boot stage 3: can't load 'kernel'. lsdev shows: disk1s1: FFS bad disklabel So I could reboot only with HDD1. It boots, mirror loads, both RAID consumers are active. I've also tried creating only 1 slice on new HDD (ad2s1 covering the whole disk), added that to mirror and has absolutely the same problem (can't boot from new HDD). Don't you know what is the reason of problem and how I could fix that? Or at least what I could try to do to solve it. Thank you for your time. Any help is highly appreciated. --------------------- Some additional info: 14:49(root@box):[/root]# uname -mpv FreeBSD 5.4-RELEASE-p1 #0: Thu Jul 14 11:56:13 EEST 2005 root@box.sov:/usr/obj/usr/src/sys/LS7 i386 i386 14:49(root@box):[/root]# fdisk ad0 ******* Working on device /dev/ad0 ******* parameters extracted from in-core disklabel are: cylinders=155061 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=155061 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 78156225 (38162 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 0/ sector 63 The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 78156288, size 78140097 (38154 Meg), flag 0 beg: cyl 1023/ head 255/ sector 63; end: cyl 1023/ head 254/ sector 63 The data for partition 3 is: <UNUSED> The data for partition 4 is: <UNUSED> 14:52(root@box):[/root]# fdisk ad2 ******* Working on device /dev/ad2 ******* parameters extracted from in-core disklabel are: cylinders=155061 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=155061 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 78156225 (38162 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 735/ head 15/ sector 63 The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 78156288, size 78139152 (38153 Meg), flag 0 beg: cyl 736/ head 0/ sector 1; end: cyl 430/ head 15/ sector 63 The data for partition 3 is: <UNUSED> The data for partition 4 is: <UNUSED> --------------------- -- Best regards Kirill
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1011050708278.20051128145933>