BTX errors on Intel SR1200 following gvinum ?crash
David Adam
zanchey at ucc.gu.uwa.edu.au
Fri Jul 4 09:26:37 UTC 2008
It looks like the problems I experienced below were due to creating a
vinum volume starting at offset 0, instead of offset 16, thus overwriting
the bootloader. I realise this is documented - apologies for the noise.
Thanks,
David Adam
zanchey at ucc.gu.uwa.edu.au
On Tue, 1 Jul 2008, David Adam wrote:
> I have a reasonably old (P3-class) Intel SR1200 which has three SCSI
> drives installed. I've installed FreeBSD 7.0-RELEASE over NFS onto the
> first drive.
>
> While configuring gvinum, I issued the following commands:
>
> ---
> blade# gvinum
> gvinum -> list
> 1 drive:
> D r0 State: down /dev/da0s1b A: 32677/32677 MB
> (100%)
>
> 0 volumes:
>
> 0 plexes:
>
> 0 subdisks:
> gvinum -> rm r0
> ---
>
> At this point, my SSH session to the machine stopped responding and
> eventually timed out. I presume it rebooted; I didn't get to the console
> in time, and this was all that was displayed:
>
> int=00000006 err=00000000 efl=00010246 eip=0000275c
> eax=00091300 ebx=00000000 ecx=00000000 edx=00000000
> esi=00000004 edi=00003dd4 ebp=00000000 esp=000903fc
> cs=002b ds=0033 es=0033 fs=0033 gs=0033 ss=0033
> cs:eip=f0 49 08 28 00 82 07 28-00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00
> ss:esp=29 20 00 00 00 00 00 00-00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00
> BTX halted
>
> This error persists on reboot. I have tried using sysinstall to rewrite
> the MBR (with /boot/mbr-style booting).
>
> The partition table looks like this:
> ---
> blade# bsdlabel da0s1
> # /dev/da0s1:
> 8 partitions:
> # size offset fstype [fsize bsize bps/cpg]
> a: 4194304 66924544 4.2BSD 0 0 0
> b: 66924544 0 vinum
> c: 71119692 0 unused 0 0 # "raw" part, don't edit
> ---
>
> Some web searching of the various values has turned up no information
> that I can understand; where should I go from here?
>
> The FreeBSD installer disc1 boots ok on this machine, as did the
> 7.0-RELEASE install until the gvinum crash. Getting a dmesg out of the
> machine is proving to be a little challenging but if required I will
> provide this tomorrow.
>
> Please keep me in the reply chain; I am not subscribed to -questions.
>
> Thanks,
>
> David Adam
> zanchey at ucc.gu.uwa.edu.au
More information about the freebsd-questions
mailing list