Date: Fri, 24 Aug 2007 11:03:31 +0200 From: =?ISO-8859-1?Q?Johan_Str=F6m?= <johan@stromnet.se> To: freebsd-geom@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Crashed gmirror, single disk marked SYNC and wont boot... Message-ID: <77098FC1-E06C-4A0C-803F-038509F5F8CA@stromnet.se> In-Reply-To: <441B87F4-5846-441B-B6B4-34694B483C73@stromnet.se> References: <8039436E-1824-4C2E-915B-9069DEF23B10@stromnet.se> <20070821143136.GD1132@garage.freebsd.pl> <441B87F4-5846-441B-B6B4-34694B483C73@stromnet.se>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 21, 2007, at 17:53 , Johan Str=F6m wrote: > On Aug 21, 2007, at 16:31 , Pawel Jakub Dawidek wrote: >> >> All in all, your partition table seems to be gone. If you created =20 >> it on >> gmirror before (gm0s1) you may still have the same partition table on >> the other half of the mirror. You can try to move it to ad6 with >> bsdlabel and verify if you can see file system inside partitions. > > Okay, tried that now.. Saved ad0s1 label, reloaded it onto ad6s1.. =20 > Now I got same partition table on ad6s1 as on ad0s1... > Trying to mount any though gives me incorrect super block... fsck =20 > cannot find any superblocks either.. > > So.. What to do now then? Just for get ad6 and start from scratch =20 > from ad2? (as i said, the data isnt very old realy)... > > Im thinking about doing complete reinstall on ad4+ad6 then.. Can I =20 > do that? fdisk both with full partition on both, create a new =20 > gmirror between ad6s1/ad4s1 (or should i go on ad4/ad6?), create =20 > slices, use dump | restore (of course with apps shutdown so no data =20= > is changed.. or at least nothing that I care about) to copy all =20 > files from ad2 to new mirror.. what do I need to do more? bsdlabel -=20= > B on both to write boot blocks? Is there anything else to think about? > Ok just for the record, I plugged both sata disks in, cleared them, =20 created a new mirror on both of them, sliced up and dump -0 -L -f - / =20= | restore -r -f - all filesystems, also bsdlabel -B. and what i =20 missed in the above thext, fdisk -B to write boot0 code.. Now its =20 booted fine on the mirror! altough, one thing that I got curious about. In the fdisk manpage it =20 says -b can be used to change the bootcode.. and that default is /=20 boot/mbr.. What is this? I checked md5 against boot0 and its not the =20 same (altough I guess it might just be some boot0 with different =20 config..). I never found any references to this mbr file in neither =20 man pages or handbook. Again, thanks for the help :)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?77098FC1-E06C-4A0C-803F-038509F5F8CA>