From owner-freebsd-current Wed Aug 11 22:45:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from mercury.is.co.za (mercury.is.co.za [196.4.160.222]) by hub.freebsd.org (Postfix) with ESMTP id DB8B114E07 for ; Wed, 11 Aug 1999 22:45:47 -0700 (PDT) (envelope-from geoffr@is.co.za) Received: from ISJHBEX (isjhbexnode.is.co.za [196.26.1.2]) by mercury.is.co.za (8.9.3/8.9.3) with ESMTP id HAA14609; Thu, 12 Aug 1999 07:40:03 +0200 Received: by isjhbex.is.co.za with Internet Mail Service (5.5.2448.0) id ; Thu, 12 Aug 1999 07:46:30 +0200 Message-ID: From: Geoff Rehmet To: "'Kevin Street'" , Soren Schmidt Cc: brian@pobox.com, current@FreeBSD.ORG Subject: RE: ATA - Trouble mounting secondary master Date: Thu, 12 Aug 1999 07:46:29 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just rebooted on an August 11 kernel. My system still is happy with the disks. Hmm. I can't remember exactly where my tracing went, before I left off before, but the message you are seeing comes from /sys/i386/isa/diskslice_machdep.c, line 200 (version 1.35). What you will probably find, is that if you put a line that goes: goto reread_mbr instead of "goto done", you will find that, on the second attempt, it reads the mbr successfully. The above is a severe kludge, and that is why I never committed any code to do anything of the sort. I think the error is actually somewhere in the ATA code (sorry Soren). I don't want to patch around a bug. Now somebody remarked that after the probe, a drive status light stayed on - maybe, the probe is not doing something properly for some drives, or there is somethign timing out. > -----Original Message----- > From: Kevin Street [mailto:street@iname.com] > Sent: 12 August 1999 03:10 > To: Soren Schmidt > Cc: geoffr@is.co.za; brian@pobox.com; current@FreeBSD.ORG > Subject: Re: ATA - Trouble mounting secondary master > > > Kevin Street writes: > > Soren Schmidt writes: > > > > Hmm, damn, after the problem went away for Geoff I > thought it to be > > > solved since I've never heard of it anywhere else, and I > cant reproduce > > > it here no matter what I try. > > > Does it help eany if you only has the root partition use > the wd dev > > > and have the rest use the prober ad dev entries ?? It > could be some > > > artifact from this... > > > > I tried with the ad dev entries for my problem as well with no > > improvement. I've also tried using: > > dd if=/dev/ad0s6 of=/dev/null bs=512 count=1 > > as the first access to one of the failing drives (ad0). > > The first dd fails with device not configured, but any subsequent > > access works fine. It seems it's left in an odd state by the driver > > start up, but all it takes is a read to get it sorted out again. > > More on this. > I just booted with -v and now when I do the first dd I see: > ad0: invalid primary partition table: no magic > and the same on ad2 when the swapon fails. > > So how do I get the magic back into my relationship with my drives? > > -- > Kevin Street > street@iname.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message