Date: Fri, 22 Jun 2001 12:08:00 -0400 From: Bill Moran <wmoran@iowna.com> To: Len Conrad <LConrad@Go2France.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 2nd ata drive, and resolv.conf options Message-ID: <3B336D60.5DB6F63D@iowna.com> References: <5.1.0.14.0.20010622153827.02fa0da0@mail.Go2France.com> <5.1.0.14.0.20010622173120.035c4658@mail.Go2France.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Len Conrad wrote: > > >[You may get better responses if you send 2 seperate emails with one > >question in each] > > I didnīt want to send TWO OT msgs :))) Tradeoff. I almost didn't read the message because I was confused by the subject line. Other's might complain if you sent two OT messages. Hmmm ... On the -questions list it's regarded as proper to send two messages (per Greg's writeup on proper -questions posting) It's also acceptable to contact the -hackers list if you don't get a response from -questions after a period. Whether that policy of sending multiple messages should transfer from -questions to -hackers is an issue of etiquette that I'm probably not the one to answer. > >Did you use "dangerously dedicated" mode? I was able to get a booting, > >running system on this drive using "dangerously dedicated" mode. > > Iīm booting off ad0. When fdisk of ad1 asked me about the MBR, I said > donīt touch it. Hmmm ... but regardless of that, are you using dangerously dedicated mode? I'm a little confused ... I'm guessing it should write a partition entry even if you tell it to leave the MBR untouched, but I could be wrong. Have you attempted different combinations during this process? > >Odd ... What does fdisk with no parameters say? > > it doesnīt find ad1s1e : My mistake ... fdisk with no parameters gives us partition data from ad0, which isn't what we're interested in. What I should have said is: What does "fdisk ad1" say? > and when I go back into /stand/sysintall fdisk, it shows me: > > Disk name: ad1 FDISK Partition Editor > DISK Geometry: 16435 cyls/145 heads/63 sectors = 150133725 sectors (73307MB) > > Offset Size(ST) End Name PType Desc Subtype Flags > > 0 63 62 - 6 unused 0 > 63 150136497 150136559 ad1s1 3 freebsd 165 C Hmmm. That looks like a DOS compatible partition scheme. (or an error) I used dangerously dedicated mode to get the drive working (because there was no reason to do otherwise) Try redoing it, selecting "A" (for all) and then saying "no" to "do you want to use a true partition entry?" > >If you need the system up immediately, you should probably use a > >different drive. If you can afford to struggle with it for a while, I > >would appreciate it if we could work together to figure out if there's > >something wrong with this model of drive. > > Unfortunately, Iīm on a contract and canīt waste the client'money chasing > this if I canīt fix it pronto. pulling the drives is quicker and cheaper Well, personally, if you haven't run the bill up too high yet, I'd try the above before giving up. But you've got to make the call for your client. Keep me posted as to what you try and the results, Bill -- If a bird in the hand is worth two in the bush, then what can I get for two hands in the bush? 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?3B336D60.5DB6F63D>