Re: Problem with multiple scsi adapters and drive assignments
On Tue, Mar 18, 2008 at 7:45 PM, Erik Trulsson <[EMAIL PROTECTED]> wrote: > > The solution is not to change the order in which things are probed, but to > hard-wire which name is assigned to which disk. > See the SCSI(4) manpage for information on how to do this by setting hints > in /boot/device.hints. > > > > > > -- > > Erik Trulsson > [EMAIL PROTECTED] > I love it when I get multiple answers that are great looking answers. My personal preferences told me to try this one first. My system is now up and running correctly. I will keep both of these answers in my mail archives and the next time I add some drives, will try Patrick's answer. Thank you for a quick response. John A. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Problem with multiple scsi adapters and drive assignments
I've searched all over (not totally exhaustive, but close) and can't find an answer that I thought would have come up before. Basically, I need to change the order that the kernel assigns drive names on bootup. It all started out with an old Intel server board with NCR/Symbios scsi builton. I added a QLogic QLA2100 fibre controller and everything was fine except that it was a little slow and couldn't hold enough ram. I took another (newer) Intel server board and put it in the case. This board has an Adaptec AIC7896 builtin. My custom kernel didn't have the aic driver so I took the opportunity to upgrade to 7.0 and built a new kernel. Everything was fine until I turned on the external fibre chassis and found that my da0 became da7. The board is in a rack-mount case so I cant put the QLA into a different slot and the bios doesn't have any way to change irq settings on the pci slots. I my mind, the logical answer is to tell FBSD to scan ahc0 before isp0. Through all my searching through docs and the mailing list archives, I can't find any mention of how to do this. I did find one mention of turning off the bios on the offending scsi card (it was a system with 2 Adaptecs). Been there, tried that, didn't work. Feel free to slap my face and call me stupid as long as you point my to the proper info if I somehow missed it. Here are the relevant parts of dmesg if that helps (I didn't include the drives themselves since I can't get it boot with the external chassis turned on): FreeBSD 7.0-RELEASE #1: Mon Mar 17 14:43:04 EDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYKERN Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel Pentium III (596.92-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x681 Stepping = 1 Features=0x383fbff real memory = 2139029504 (2039 MB) avail memory = 2087882752 (1991 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <24-bit timer at 3.579545MHz> port 0xc08-0xc0b on acpi0 cpu0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: on hostb0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib2: at device 15.0 on pci1 pci2: on pcib2 isp0: port 0x2000-0x20ff mem 0xf450-0xf4500fff irq 19 at device 9.0 on pci0 firmware_get: failed to load firmware image isp_2100 isp0: [ITHREAD] isp0: Board Type 2100, Chip Revision 0x3, resident F/W Revision 1.15.21 pci0: at device 11.0 (no driver attached) ahc0: port 0x2400-0x24ff mem 0xf4501000-0xf4501fff irq 19 at device 12.0 on pci0 ahc0: [ITHREAD] aic7896/97: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs ahc1: port 0x2800-0x28ff mem 0xf4502000-0xf4502fff irq 19 at device 12.1 on pci0 ahc1: [ITHREAD] aic7896/97: Ultra2 Wide Channel B, SCSI Id=15, 32/253 SCBs Thanks in advance for your help, the archives of this list have been very helpful over the past 5 years. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ethernet issue: works one way but not another
ger around, I have to move to another os. I prefer not to follow the other sys admin and convert to peguin. I have BSDI servers that have been up for over 2 years. On average, penguin boxes have to be rebooted every quarter. My FBSD streamer has been up fro 281 days (and that was due to power and ups failure at a co-lo facility). I'm hoping that this will turn out to not be the head scratcher I fear it might. Hope this information helps. John A. On Fri, 18 Mar 2005 07:15:50 -0600, Greg Barniskis <[EMAIL PROTECTED]> wrote: > Abu Khaled wrote: > ... > > Am I the only one interested in this topic? Where is the rest of our > > lovely community? > > Come on guys let's scratch those gray cells and help John out. > > > > Although progress is being made on getting detail, it's still > insufficient (and, not entirely consistent? if the connection in > question is *wired* then probably the fact that a wireless access > point exists on the same subnet is not likely relevant). Anyway, I > do not have a clear vision of what connects to what, how. > > The relevant portions of rc.conf, ifconfig output (and ipconfig > output from the M$ box), the syntax of the tcpdump, the specs of the > box, and other relevant details might spur more response. A simple > ASCII representation of the network might help. > > FWIW, I've seen tcpdump behave poorly if the box or card just > doesn't have the horsepower required to parse the volume of all the > packets being seen on the network. > > re: can't ping M$ box... M$ firewall sounds like the most likely > culprit. If you try to ping and get no response, does the M$ box > nevertheless show up in FreeBSD's arp table (compare arp -an before > and after the ping test)? If the MAC address shows up, you've got > connectivity just fine, but something's dropping the ICMP packets. > > PS to Abu -- your written English is as good or better than many > native speakers of the language, so don't apologize for it. =) > > -- > Greg Barniskis, Computer Systems Integrator > South Central Library System (SCLS) > Library Interchange Network (LINK) > , (608) 266-6348 > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ethernet issue: works one way but not another
No problem with the english, if you didn't mention it, I wouldn't have known. I can ping FBSD from M$, can't ping anything from FBSD. M$ box works when plugged into hub and directly into radio. All systems are on same subnet. FBSD box worked when plugged into a 100mb hub, but doesn't work when plugged into 10mb hub or directly into radio. Both hubs are 3Com and are working with other systems plugged into them. FBSD has no firwall configured. All I did was perform a standard installation loading all binaries and sources from ftp. I just tested another FBSD 5.3 box that I have and it does the same thing, works fine at 100mb, but appears to get lost at 10mb. Hope this answers some of your questions. John A. On Fri, 18 Mar 2005 01:18:46 +0200, abu khaled <[EMAIL PROTECTED]> wrote: > > First, you have to excuse my English it is my third language and I do > not have that much experience. > > This seems like a puzzle to me and I cannot figure out the topology of > your network. > > * Can you ping the M$ box from FreeBSD? You need to enable incoming > echo request in M$ firewall. > * Are both systems on the same subnet? > * Have you tried to plug the radio directly into FreeBSD box and test > the connection like you did for M$ box? > * Does your FreeBSD box have a firewall configured? > > You mentioned that the connection works if you plug the radio directly > to M$ box. Does it also work when you plug both to the hub? If not > then it might be a crossover cable problem. > > As you can see, many pices in this puzzle need sorting out. > > -- > Kind regards > Abu Khaled > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ethernet issue: works one way but not another
The system uses a standard installation. I have only configured the ethernet card with the proper ip address for the wireless side of the network. The windoze box is running M$ firewall, but it works fine and allows me to ping my gateway and the FBSD box. What concerns me at this point is the fact that tcpdump takes so long to respond. If I let it run, it will display a packet about one every 2 min. They seem to be in time order with timestamps only ms apart. Let me know if any other information will help. John A. On Thu, 17 Mar 2005 04:16:51 +0200, abu khaled <[EMAIL PROTECTED]> wrote: > > Well I am sure some one well help you if you provide more information > about your network configuration/firewall rules,etc... > > Do you have a firewall configured on the freebsd box/M$windoze? > > -- > Kind regards > Abu Khaled > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
