Date: 11 Aug 1999 21:09:32 -0400 From: Kevin Street <street@iname.com> To: Soren Schmidt <sos@freebsd.dk> Cc: geoffr@is.co.za, brian@pobox.com, current@FreeBSD.ORG Subject: Re: ATA - Trouble mounting secondary master Message-ID: <87yafhn6sz.fsf@mired.eh.local> In-Reply-To: Kevin Street's message of "11 Aug 1999 20:11:59 -0400" References: <199908110653.IAA56765@freebsd.dk> <87hfm5vovk.fsf@mired.eh.local>
next in thread | previous in thread | raw e-mail | index | archive | help
Kevin Street <street@iname.com> writes: > Soren Schmidt <sos@freebsd.dk> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87yafhn6sz.fsf>