Date: Fri, 16 Nov 2001 12:47:29 -0800 (PST) From: John Baldwin <jhb@FreeBSD.org> To: Sandeep Joshi <sandeepj@research.bell-labs.com> Cc: hackers@freebsd.org Subject: Re: Tracking down "BTX halted" Message-ID: <XFMail.011116124729.jhb@FreeBSD.org> In-Reply-To: <3BF5799E.1DBCB8A0@research.bell-labs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 16-Nov-01 Sandeep Joshi wrote: > > Mike, > > Mike Smith wrote: >> The only real solution is to hot-plug >> the disks, camcontrol rescan, then dd zeroes over the heads of the disks >> and then re-lable them safely. > > Yep, that method works for now. > > I was hoping its easy enough to crack this myself (with some online > tips & references) but John Baldwin convinced me otherwise :-) > > So here's the entire configuration attached.. > > SUMMARY: > The boot disk (ad0 in attachment) is not the problem. > There are two other IBM SCSI disks attached to two Adaptec cards. > Its these other two SCSI disks-da0,da1 which are empty and > whose disklabels I played with. These cause a BTX error if > they are plugged in during a boot. Were these disks ever formatted with dangerously dedicated mode. If so, you would need to re-fdisk them to get the bogus fdisk table out of the way. dd'ing zeros over the table is one way of doing this, although you will still need to fdisk afterwards. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.011116124729.jhb>