Help with CAM status: Command Timeout
-
I would try another CF card.
-
I would try another CF card.
Really? That one was brand new. Plus I don't have another way to get one soon. Do you think it would work if I just re-installed pfsense on it?
-
You can try. Those look like disk errors to me.
-
Poo. What do you recommend to install it with? Ive been using Rufus but ive heard people do other things to install it on a CF card.
Side note: Ive tried on other machines and i get more CAM errors, even with actual hard drives, leading me to believe the machine is just to old. (Drives were newer than the machine
-
That could be too. It doesn't like something.
-
That could be too. It doesn't like something.
If it helps this is everything I get on boot:
1 pfSense
2 pfSenseF6 PXE
Boot: 1
/boot/config: -S115200 -h
Consoles: serial port
BIOS drive C: is disk0
BIOS 639kB/523264kB available memoryFreeBSD/x86 bootstrap loader, Revision 1.1
(root@ce23-i386-builder, Tue Jul 19 13:40:21 CDT 2016)
Loading /boot/defaults/loader.conf
/boot/kernel/kernel text=0x121f23a data=0x8472ac+0xd9788 syms=[0x4+0xf3b40+0x4+0x16baa5]Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]…
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 1992-2016 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 10.3-RELEASE-p5 #0 7307492(RELENG_2_3_2): Tue Jul 19 14:02:43 CDT 2016
root@ce23-i386-builder:/builder/pfsense-232/tmp/obj/builder/pfsense-232/tmp/FreeBSD-src/sys/pfSense_wrap i386
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
CPU: Intel(R) Pentium(R) III CPU - S 1266MHz (1269.57-MHz 686-class CPU)
Origin="GenuineIntel" Id=0x6b4 Family=0x6 Model=0xb Stepping=4
Features=0x383f9ff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,sep,mtrr,pge,mca,cmov,pat,pse36,mmx,fxsr,sse>real memory = 536870912 (512 MB)
avail memory = 489861120 (467 MB)
random: <software, yarrow="">initialized
ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_ibss_fw, 0xc0814f60, 0) error 1
ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_monitor_fw, 0xc0815010, 0) error 1
iwi_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
iwi_bss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (iwi_bss_fw, 0xc083ca00, 0) error 1
iwi_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
iwi_ibss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (iwi_ibss_fw, 0xc083cab0, 0) error 1
iwi_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/.
iwi_monitor: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (iwi_monitor_fw, 0xc083cb60, 0) error 1
wlan: mac acl policy registered
ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
module_register_init: MOD_LOAD (ipw_bss_fw, 0xc0814eb0, 0) error 1
kbd0 at kbdmux0
ACPI BIOS Error (bug): A valid RSDP was not found (20150515/tbxfroot-258)
ACPI: Table initialisation failed: AE_NOT_FOUND
ACPI: Try disabling either ACPI or apic support.
cryptosoft0: <software crypto="">on motherboard
padlock0: No ACE support.
pcib0 pcibus 0 on motherboard
pir0: <pci 11="" interrupt="" routing="" table:="" entries="">on motherboard
$PIR: Using invalid BIOS IRQ 9 from 2.13.INTA for link 0x63
pci0: <pci bus="">on pcib0
agp0: <intel 82815="" (i815="" gmch)="" host="" to="" pci="" bridge="">on hostb0
pcib1: <pci-pci bridge="">at device 1.0 on pci0
pci1: <pci bus="">on pcib1
pcib2: <pcibios pci-pci="" bridge="">at device 30.0 on pci0
pci2: <pci bus="">on pcib2
safe0 mem 0xe7bfe000-0xe7bfffff irq 3 at device 6.0 on pci2
safe0: SafeNet SafeXcel-1141 rng des/3des aes md5 sha1 null
re0: <realtek 10="" 8139c+="" 100basetx="">port 0xd500-0xd5ff mem 0xefefa000-0xefefa1ff irq 10 at device 9.0 on pci2
re0: Chip rev. 0x74800000
re0: MAC rev. 0x00000000
miibus0: <mii bus="">on re0
rlphy0: <realtek internal="" media="" interface="">PHY 0 on miibus0
rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow
re0: Using defaults for TSO: 65518/35/2048
re0: Ethernet address: 00:90:7f:30:91:83
re1: <realtek 10="" 8139c+="" 100basetx="">port 0xd600-0xd6ff mem 0xefefb000-0xefefb1ff irq 5 at device 10.0 on pci2
re1: Chip rev. 0x74800000
re1: MAC rev. 0x00000000
miibus1: <mii bus="">on re1
rlphy1: <realtek internal="" media="" interface="">PHY 0 on miibus1
rlphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow
re1: Using defaults for TSO: 65518/35/2048
re1: Ethernet address: 00:90:7f:30:91:84
re2: <realtek 10="" 8139c+="" 100basetx="">port 0xd900-0xd9ff mem 0xefefc000-0xefefc1ff irq 11 at device 11.0 on pci2
re2: Chip rev. 0x74800000
re2: MAC rev. 0x00000000
miibus2: <mii bus="">on re2
rlphy2: <realtek internal="" media="" interface="">PHY 0 on miibus2
rlphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow
re2: Using defaults for TSO: 65518/35/2048
re2: Ethernet address: 00:90:7f:30:91:85
re3: <realtek 10="" 8139c+="" 100basetx="">port 0xda00-0xdaff mem 0xefefd000-0xefefd1ff irq 12 at device 12.0 on pci2
re3: Chip rev. 0x74800000
re3: MAC rev. 0x00000000
miibus3: <mii bus="">on re3
rlphy3: <realtek internal="" media="" interface="">PHY 0 on miibus3
rlphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow
re3: Using defaults for TSO: 65518/35/2048
re3: Ethernet address: 00:90:7f:30:91:86
re4: <realtek 10="" 8139c+="" 100basetx="">port 0xdd00-0xddff mem 0xefefe000-0xefefe1ff irq 9 at device 13.0 on pci2
re4: Chip rev. 0x74800000
re4: MAC rev. 0x00000000
miibus4: <mii bus="">on re4
rlphy4: <realtek internal="" media="" interface="">PHY 0 on miibus4
rlphy4: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow
re4: Using defaults for TSO: 65518/35/2048
re4: Ethernet address: 00:90:7f:30:91:87
re5: <realtek 10="" 8139c+="" 100basetx="">port 0xde00-0xdeff mem 0xefeff000-0xefeff1ff irq 6 at device 14.0 on pci2
re5: Chip rev. 0x74800000
re5: MAC rev. 0x00000000
miibus5: <mii bus="">on re5
rlphy5: <realtek internal="" media="" interface="">PHY 0 on miibus5
rlphy5: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow
re5: Using defaults for TSO: 65518/35/2048
re5: Ethernet address: 00:90:7f:30:91:88
isab0: <pci-isa bridge="">at device 31.0 on pci0
isa0: <isa bus="">on isab0
atapci0: <intel ich2="" udma100="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 31.1 on pci0
ata0: <ata channel="">at channel 0 on atapci0
ata1: <ata channel="">at channel 1 on atapci0
cpu0 on motherboard
pmtimer0 on isa0
unknown: <pnp0c01>can't assign resources (memory)
attimer0: <at timer="">at port 0x40-0x43 irq 0 pnpid PNP0100 on isa0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
atrtc0: <at realtime="" clock="">at port 0x70-0x71 irq 8 pnpid PNP0b00 on isa0
Event timer "RTC" frequency 32768 Hz quality 0
atkbdc0: <keyboard controller="" (i8042)="">at port 0x60,0x64 irq 1 pnpid PNP0303 on isa0
atkbd0: <at keyboard="">irq 1 on atkbdc0
kbd1 at atkbd0
atkbd0: [GIANT-LOCKED]
uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 4 flags 0x10 pnpid PNP0501 on isa0
uart0: console (115200,n,8,1)
ppc0: <ecp parallel="" printer="" port="">at port 0x378-0x37f,0x778-0x77a irq 7 drq 3 pnpid PNP0401 on isa0
ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/16 bytes threshold
ppbus0: <parallel port="" bus="">on ppc0
lpt0: <printer>on ppbus0
lpt0: Interrupt-driven port
ppi0: <parallel i="" o="">on ppbus0
orm0: <isa option="" rom="">at iomem 0xe0000-0xe0fff pnpid ORM0000 on isa0
unknown: <pnp0c01>can't assign resources (memory)
random: unblocking device.
Timecounters tick every 1.000 msec
ata0: DMA limited to UDMA33, controller found non-ATA66 cable
ada0 at ata0 bus 0 scbus0 target 0 lun 0
ada0: <cf card="" ver7.04="">ATA-5 device
ada0: Serial Number 5B6610FF0
ada0: 33.300MB/s transfers (UDMA2, PIO 512bytes)
ada0: 3811MB (7806960 512 byte sectors)
ada0: Previously was known as ad0
Timecounter "TSC" frequency 1269573877 Hz quality 800
(ada0:ata0:0:0:0): READ_DMA. ACB: c8 00 ee 1f 77 40 00 00 00 00 01 00
(ada0:ata0:0:0:0): CAM status: Command timeout
(ada0:ata0:0:0:0): Retrying command
ata0: DMA limited to UDMA33, controller found non-ATA66 cable</cf></pnp0c01></isa></parallel></printer></parallel></ecp></at></keyboard></at></at></pnp0c01></ata></ata></intel></isa></pci-isa></realtek></mii></realtek></realtek></mii></realtek></realtek></mii></realtek></realtek></mii></realtek></realtek></mii></realtek></realtek></mii></realtek></pci></pcibios></pci></pci-pci></intel></pci></pci></software></software,></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,sep,mtrr,pge,mca,cmov,pat,pse36,mmx,fxsr,sse> -
Not really. That hardware is getting pretty old. Replacing it with something more current (preferably 64-bit) should cost next to nothing.
It's possible something in FreeBSD 10.3 just doesn't like it. Not a lot of testing is being done on ancient gear like that.
-
IIRC, on one of my older PCs I had to disable some ATA/DMA support in pfSense (add "set hw.ata.ata_dma=0" to /boot/loader.conf.local) to get it to work with my CF card. I think part of the problem was that I did not get a good (industrial grade?) CF card that fully supported UDMA5 or some related features.
I think I found the info on the pfSense wiki or maybe the forums.
-
Good point. See if anything here matches your specific scenario:
https://doc.pfsense.org/index.php/Boot_Troubleshooting
-
@Nullity, I was facing the same problem, " CAM status: Command timeout" and your answer worked for me on pfsense 2.4.4 installation using a pendrive:
I've add "set hw.ata.ata_dma=0" on boot options and install proceeded with no errors.
Once pfsense installed, it was needed to edit the /boot/loader.conf file and add the same option so that persist it on next boot.
Thanks.