Date: Fri, 17 Aug 2001 23:46:58 -0400 (EDT) From: timothyk@server1.wallnet.com To: "Long, Scott" <Scott_Long@btc.adaptec.com> Cc: "'Tim Kellers'" <timothyk@wallnet.com>, Chris Dillon <cdillon@wolves.k12.mo.us>, Scott Long <scottl@FreeBSD.ORG>, Joseph Koenig <joe@jwebmedia.com>, freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: RE: Serious Problems with PERC3 Dual Channel and FreeBSD 4.3 Message-ID: <998106418.3b7de53277165@dhcp199-23.njit.edu> In-Reply-To: <50486691668CD511BB660000D11ABE9214721B@btcexc01.btc.adaptec.com> References: <50486691668CD511BB660000D11ABE9214721B@btcexc01.btc.adaptec.com>
next in thread | previous in thread | raw e-mail | index | archive | help
The "box" hung at the "Waiting for SCSI devices to settle." Usually that takes 15 seconds or so, this time it stopped at that message for 8 hours and never continued. Tell me what more info you require and I'll be happy to provide it. Tim CPE/NJIT Quoting "Long, Scott" <Scott_Long@btc.adaptec.com>: > What do you mean by the box wouldn't boot? Did it panic/freeze/catch > fire/shoot death rays? Is the problem related to the PERC controller? > Being this close to the release of 4.4, I'd like as much information as > you > can quickly give me. > > To answer the second part, we think that we have the issue resolved. It > was > a matter of using boot floppies and install CD of the correct version > and > date. > > Thanks. > > Scott > > > -----Original Message----- > > From: Tim Kellers [mailto:timothyk@wallnet.com] > > Sent: Friday, August 17, 2001 7:41 PM > > To: Chris Dillon; Scott Long > > Cc: Joseph Koenig; freebsd-scsi@freebsd.org; > > freebsd-stable@freebsd.org > > Subject: Re: Serious Problems with PERC3 Dual Channel and FreeBSD 4.3 > > > > > > I'm currently running a Dell 2500 dual processor server with > > a PERC 3 di RAID > > controller and 4.4 Pre-release. Oddly enough, last night. I > > cvsupped and > > built the world then the kernel and installed the kernel (4.4 > > RC) on my > > production server (single processor PII) and the kernel build > > worked fine, > > but the box wouldn't boot the kernel. I dropped back to > > loading kernel.old > > from a boot command prompt and the box came up fine (whew!). > > > > I think somthing might be amiss with the sources for kernel > > from about the > > past 48 hours or so. > > > > But, to get back to your problem, you might want to get the > > July 21, 2001 > > snapshot, make the boot disks and install from there. From > > that snapshot my > > 2500 booted happily. > > > > (My 2500 has 3 36 GB drives, RAID 5 and a 67 (+) GIG container) > > > > Tim Kellers > > > > CPE/NJIT > > > > > > > > On Thursday 16 August 2001 13:38, Chris Dillon wrote: > > > Copied to -STABLE... > > > > > > On Thu, 16 Aug 2001, Scott Long wrote: > > > > This is very strange. Is it possible to send me the > > dmesg output? If > > > > not, can you page back the console and see of the card > > and container are > > > > being detected? I'll look into it in the mean time. > > > > > > > > Scott > > > > > > > > On Thu, Aug 16, 2001 at 09:35:58AM -0500, Joseph Koenig wrote: > > > > > Let me first say I have posted this question on Newbies > > and Questions > > > > > and no one has been able to help yet and suggested I > > try the SCSI list. > > > > > Here's what's going on. I've got a Dell PowerEdge 2500 > > 1GHz, 1GB RAM, > > > > > 3x18GB U160 SCSI Drives in RAID 5 with the PERC3 Dual Channel > > > > > controller - 128MB Write Cache. There is 1 container > > set up on the > > > > > drives that is about 34GB. It is detected at "aacd0". > > Installation goes > > > > > just fine, but when I try to reboot, I get the > > following message: > > > > > > > > > > -------------------------------------------- > > > > > no devsw (majdev=0 bootdev=0xa0200000) > > > > > Mounting root from ufs:/dev/aacd0s1a > > > > > no such device 'aacd' > > > > > setrootbyname failed > > > > > ffs_mountroot: can't find rootvp > > > > > Root mount failed: 6 > > > > > > > > > > Manual root filesystem specification: > > > > > <fstype>:<device> Mount <device> using filesystem <fstype> > > > > > eg. ufs:/dev/da0s1a > > > > > ? List valid disk boot devices > > > > > <empty line> Abort manual input > > > > > ------------------------------------------- > > > > > > > > > > I have been unable to get past this point in any way. > > The last thing I > > > > > tried was to install via FTP from releng4.FreeBSD.org - > > I grabbed the > > > > > snapshot from yesterday and still have the same > > problem. I've also > > > > > tried just using the regular MBR as opposed to the Boot > > Manager, as > > > > > someone suggested. I've been scrounging books and the > > net for the past > > > > > week and have been unable to get anywhere with this. > > Any help would be > > > > > much appreciated. I'm willing to try anything. Thanks, > > > > > > I think you're seeing the same problem I am. It isn't > > related to your > > > RAID controller. Something in -STABLE broke bus probing on > > a few rare > > > machines such as yours and mine. I'll bet your dmesg > > output is quite > > > short since most of your devices aren't being probed. I tried to > > > narrow down the commit that may have caused it last night, but I > > > didn't have any luck. I'm hoping others can give me suggestions on > > > recent -STABLE changes (within three weeks or a month) to revert to > > > try and find the problem. I can check out previous dates > > of the tree > > > to try and narrow it down, too, but thats a bit of a pain. > > > > > > > > > -- > > > Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net > > > FreeBSD: The fastest and most stable server OS on the planet > > > - Available for IA32 (Intel x86) and Alpha architectures > > > - IA64, PowerPC, UltraSPARC, and ARM architectures under > > development > > > - http://www.freebsd.org > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-stable" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?998106418.3b7de53277165>