[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 2.8 sees hard drive; 3.0 doesn't
Ben Goren wrote:
> On Mon, Mar 04, 2002 at 06:46:22PM -0500, Nick Holland wrote:
> > I love dmesg's, thanks! 8-)
> Have you seen any professionals about this?
> > If you want to prove me wrong (or right), swap the drives
> > between the machines, the problem should follow the drive, not
> > the machine.
> I was afraid you'd suggest that--I'm trying to minimize downtime.
Oh, bummer. Can't prove me wrong. 8-)
> I was able to scrounge another drive, a 2 1/2 Gbyte ST32532A. The
> installer sees it, so my immediate problem is solved. Heck, it's
> big enough for an /altroot and then some!
> So, I haven't confirmed that the old drive has problems in the
> other computer, but I have confirmed that a different, newer drive
> has no problem. Good enough diagnostics?
Pretty good diagnostics.
Even better repair. 8-)
> > I'm guessing if you were to disable the pciide driver (which
> > forces the system to use the older non-DMA driver), it will
> > recognize the ST3290A drive. This can be done by doing this: [.
> > . .]
> I think it half-worked. It found a wdc0 but never a wd0.
Hey, what happened to not proving me wrong? 8-)
wdc0 is the first IDE controller. That was a full not-worked,
Nick-Was-Wrong. When you disable pciide, you get wdc instead. But it
still didn't work. (I was drawing a blank on the name of wdc0
Interesting. Going to have to see if I have a ST3290a that works...
> P.S. In light of a recent post of yours (Nick), will I have
> trouble with only 16 Mbytes RAM? They'll be firewalls, of course;
> one a bridge, the other with IPs but no NAT. Nothing but pf, only
> minimal logging. b&
The trick is going to be getting it installed. Once installed, things
should be fine for a while yet. If you have tens of thousands of
connections for the system to track, you might be in trouble, but for
home use, 16M is probably still quite sufficient. Note stratgic use
of the word "probably". 8-)
Speaking of snapshots...
You might want to try a snapshot boot disk... This might run you into
the 16M issue, but if it works, you might have a use for the 250M
drive after all (sorry I didn't think of that yesterday)..might be
worth digging up a couple 8M SIMMs. Again, yes, this would be a pain
to test now that you have already replaced the drive...