Other Only /dev/pass*

E

e^ipi

Hello,

Drives plugged in to an Adaptec 51245 only appear as pass(4) devices. I have tried setting the drives up as JBOD or single drive RAID 0. Same results with both. Don't know what to do. I know the Adaptec card isn't the best thing to be using here, but I got it for free and I will not be using it as any sort of file server so I don't really care what happens-I would just like it to at least mostly work.

I will provide any information required later as I do not have access to the machine currently.
 
Don't think that is my issue. I've tried about 10 different drives. New WD red, old WD red, WD black, some Seagate, HGST he6, HGST ultrastar, HGST NAS, and 4 different SSDs.

The drives show up with camcontrol devlist but only as pass()* and in the cards BIOS.
 
Last edited:
e^ipi said:
Drives plugged in to an Adaptec 51245 only appear as pass(4) devices. I have tried setting the drives up as JBOD or single drive RAID 0. Same results with both. Don't know what to do. I know the Adaptec card isn't the best thing to be using here, but I got it for free and I will not be using it as any sort of file server so I don't really care what happens-I would just like it to at least mostly work.
Click to expand...
If # camcontrol devlist shows the correct drive models, but no volumes show up as disk devices, that usually means that the controller isn't exporting them to the operating system properly. Here is an example with an LSI controller:
Code: 
(0:15) gate:~terry# camcontrol devlist
<SEAGATE ST9146852SS HT66>         at scbus0 target 0 lun 0 (pass0)
<SEAGATE ST9146852SS HT66>         at scbus0 target 1 lun 0 (pass1)
<SEAGATE ST9146852SS HT66>         at scbus0 target 2 lun 0 (pass2)
<SEAGATE ST9146852SS HT66>         at scbus0 target 3 lun 0 (pass3)
<SEAGATE ST9146852SS HT66>         at scbus0 target 4 lun 0 (pass4)
<SEAGATE ST9146852SS HT66>         at scbus0 target 5 lun 0 (pass5)
<DP BACKPLANE 1.07>                at scbus0 target 32 lun 0 (ses0,pass6)
The actual disk device shows up as a mfi(4) device:
Code: 
mfid0 on mfi0
mfid0: 557568MB (1141899264 sectors) RAID volume 'SYSDISK' is optimal
Is it possible that the disk is showing up under a device name you aren't expecting? Try doing # grep sectors /var/run/dmesg.boot (assuming you've got an installed and working multi-user FreeBSD setup, otherwise try # dmesg | grep sectors) to see if that is the case.
 
/dev
Code: 
root@abc:/dev # ls -al
total 14
dr-xr-xr-x   8 root  wheel      512 May  2 09:50 .
drwxr-xr-x  18 root  wheel       25 May  2 09:50 ..
crw-r-----   1 root  operator  0x25 May  2 16:50 aac0
crw-r--r--   1 root  wheel     0x21 May  2 16:50 acpi
lrwxr-xr-x   1 root  wheel        4 May  2 16:50 ad10 -> ada0
lrwxr-xr-x   1 root  wheel        6 May  2 16:50 ad10p1 -> ada0p1
lrwxr-xr-x   1 root  wheel        6 May  2 16:50 ad10p2 -> ada0p2
lrwxr-xr-x   1 root  wheel        6 May  2 16:50 ad10p3 -> ada0p3
lrwxr-xr-x   1 root  wheel        4 May  2 16:50 ad12 -> ada1
lrwxr-xr-x   1 root  wheel        6 May  2 16:50 ad12p1 -> ada1p1
lrwxr-xr-x   1 root  wheel        6 May  2 16:50 ad12p2 -> ada1p2
lrwxr-xr-x   1 root  wheel        6 May  2 16:50 ad12p3 -> ada1p3
lrwxr-xr-x   1 root  wheel        4 May  2 16:50 ad16 -> ada2
lrwxr-xr-x   1 root  wheel        6 May  2 16:50 ad16p1 -> ada2p1
lrwxr-xr-x   1 root  wheel        6 May  2 16:50 ad16p2 -> ada2p2
lrwxr-xr-x   1 root  wheel        6 May  2 16:50 ad16p3 -> ada2p3
crw-r-----   1 root  operator  0x5c May  2 16:50 ada0
crw-r-----   1 root  operator  0x6c May  2 16:50 ada0p1
crw-r-----   1 root  operator  0x6e May  2 09:50 ada0p2
crw-r-----   1 root  operator  0x70 May  2 16:50 ada0p3
crw-r-----   1 root  operator  0x72 May  2 16:50 ada1
crw-r-----   1 root  operator  0x7d May  2 16:50 ada1p1
crw-r-----   1 root  operator  0x7f May  2 16:50 ada1p2
crw-r-----   1 root  operator  0x81 May  2 16:50 ada1p3
crw-r-----   1 root  operator  0x74 May  2 16:50 ada2
crw-r-----   1 root  operator  0x84 May  2 16:50 ada2p1
crw-r-----   1 root  operator  0x86 May  2 16:50 ada2p2
crw-r-----   1 root  operator  0x88 May  2 16:50 ada2p3
lrwxr-xr-x   1 root  wheel        4 May  2 16:50 afa0 -> aac0
crw-rw-r--   1 root  operator  0x23 May  2 16:50 apm
crw-rw----   1 root  operator  0x22 May  2 16:50 apmctl
crw-------   1 root  wheel     0x3a May  2 16:50 atkbd0
crw-------   1 root  kmem       0xd May  2 16:50 audit
crw-------   1 root  wheel     0x1f May  2 16:50 bpf
lrwxr-xr-x   1 root  wheel        3 May  2 16:50 bpf0 -> bpf
crw-rw-rw-   1 root  wheel     0x3d May  2 16:50 bpsm0
crw-r-----   1 root  operator  0x5b May  2 16:50 cd0
crw-------   1 root  wheel      0x5 May  2 16:52 console
crw-------   1 root  wheel     0x1c May  2 16:50 consolectl
crw-rw-rw-   1 root  wheel     0x1b May  2 16:50 ctty
crw-rw----   1 uucp  dialer    0x37 May  2 16:50 cuau0
crw-rw----   1 uucp  dialer    0x38 May  2 16:50 cuau0.init
crw-rw----   1 uucp  dialer    0x39 May  2 16:50 cuau0.lock
crw-------   1 root  wheel      0x3 May  2 16:50 devctl
cr--r--r--   1 root  wheel     0x52 May  2 16:50 devstat
crw-rw-rw-   1 root  wheel     0x8a May  2 16:51 dsp0.0
crw-rw-rw-   1 root  wheel     0x83 May  2 16:51 dsp1.0
crw-rw-rw-   1 root  wheel     0x7c May  2 16:51 dsp2.0
crw-rw-rw-   1 root  wheel     0x7b May  2 16:51 dsp3.0
crw-rw-rw-   1 root  wheel     0x7a May  2 16:51 dsp4.0
crw-rw-rw-   1 root  wheel     0x78 May  2 16:51 dsp5.0
crw-rw-rw-   1 root  wheel     0x77 May  2 16:51 dsp6.0
lrwxr-xr-x   1 root  wheel       11 May  2 09:50 dumpdev -> /dev/ada0p2
dr-xr-xr-x   2 root  wheel      512 May  2 16:50 fd
crw-------   1 root  wheel     0x1e May  2 16:50 fido
crw-r-----   1 root  operator   0x4 May  2 16:50 geom.ctl
dr-xr-xr-x   2 root  wheel      512 May  2 16:50 gpt
crw-------   1 root  wheel     0x24 May  2 16:50 hpet0
lrwxr-xr-x   1 root  wheel        4 May  2 16:50 hpn0 -> aac0
crw-------   1 root  wheel     0x14 May  2 16:50 io
lrwxr-xr-x   1 root  wheel        6 May  2 16:50 kbd0 -> atkbd0
lrwxr-xr-x   1 root  wheel        7 May  2 16:50 kbd1 -> kbdmux0
crw-------   1 root  wheel     0x16 May  2 16:50 kbdmux0
crw-------   1 root  wheel     0x18 May  2 16:50 klog
crw-r-----   1 root  kmem      0x1a May  2 16:50 kmem
dr-xr-xr-x   2 root  wheel      512 May  2 16:50 led
lrwxr-xr-x   1 root  wheel       12 May  2 16:51 log -> /var/run/log
crw-------   1 root  wheel     0x4b May  2 16:50 mdctl
crw-r-----   1 root  kmem      0x19 May  2 16:50 mem
crw-rw-rw-   1 root  wheel     0x15 May  2 16:50 midistat
crw-rw-rw-   1 root  wheel     0x44 May  2 16:50 mixer0
crw-rw-rw-   1 root  wheel     0x45 May  2 16:50 mixer1
crw-rw-rw-   1 root  wheel     0x46 May  2 16:50 mixer2
crw-rw-rw-   1 root  wheel     0x47 May  2 16:50 mixer3
crw-rw-rw-   1 root  wheel     0x48 May  2 16:50 mixer4
crw-rw-rw-   1 root  wheel     0x49 May  2 16:50 mixer5
crw-rw-rw-   1 root  wheel     0x4a May  2 16:50 mixer6
crw-------   1 root  kmem       0xa May  2 16:50 nfslock
crw-rw-rw-   1 root  wheel      0x7 May  2 17:00 null
crw-------   1 root  wheel     0x53 May  2 16:50 pass0
crw-------   1 root  wheel     0x54 May  2 16:50 pass1
crw-------   1 root  operator  0x55 May  2 16:50 pass2
crw-------   1 root  operator  0x56 May  2 16:50 pass3
crw-------   1 root  operator  0x57 May  2 16:50 pass4
crw-------   1 root  operator  0x58 May  2 16:50 pass5
crw-------   1 root  operator  0x59 May  2 16:50 pass6
crw-------   1 root  operator  0x5a May  2 16:50 pass7
crw-r--r--   1 root  wheel      0x9 May  2 16:50 pci
crw-rw-rw-   1 root  wheel     0x3c May  2 16:51 psm0
dr-xr-xr-x   2 root  wheel      512 May  2 16:52 pts
crw-rw-rw-   1 root  wheel      0xb May  2 09:50 random
crw-------   1 root  operator  0x5e May  2 16:50 ses0
cr--r--r--   1 root  wheel      0x6 May  2 16:50 sndstat
lrwxr-xr-x   1 root  wheel        4 May  2 16:50 stderr -> fd/2
lrwxr-xr-x   1 root  wheel        4 May  2 16:50 stdin -> fd/0
lrwxr-xr-x   1 root  wheel        4 May  2 16:50 stdout -> fd/1
crw-------   1 root  wheel     0x1d May  2 16:50 sysmouse
crw-------   1 root  wheel     0x34 May  2 16:50 ttyu0
crw-------   1 root  wheel     0x35 May  2 16:50 ttyu0.init
crw-------   1 root  wheel     0x36 May  2 16:50 ttyu0.lock
crw-------   1 root  wheel     0x5f May  2 16:51 ttyv0
crw-------   1 root  wheel     0x60 May  2 16:51 ttyv1
crw-------   1 root  wheel     0x61 May  2 16:51 ttyv2
crw-------   1 root  wheel     0x62 May  2 16:51 ttyv3
crw-------   1 root  wheel     0x63 May  2 16:51 ttyv4
crw-------   1 root  wheel     0x64 May  2 16:51 ttyv5
crw-------   1 root  wheel     0x65 May  2 16:51 ttyv6
crw-------   1 root  wheel     0x66 May  2 16:51 ttyv7
crw-------   1 root  wheel     0x67 May  2 16:50 ttyv8
crw-------   1 root  wheel     0x68 May  2 16:50 ttyv9
crw-------   1 root  wheel     0x69 May  2 16:50 ttyva
crw-------   1 root  wheel     0x6a May  2 16:50 ttyvb
crw-------   1 root  wheel     0x3e May  2 16:50 ufssuspend
lrwxr-xr-x   1 root  wheel        9 May  2 16:50 ugen0.1 -> usb/0.1.0
lrwxr-xr-x   1 root  wheel        9 May  2 16:50 ugen0.2 -> usb/0.2.0
lrwxr-xr-x   1 root  wheel        9 May  2 16:50 ugen1.1 -> usb/1.1.0
lrwxr-xr-x   1 root  wheel        9 May  2 16:50 ugen1.2 -> usb/1.2.0
lrwxr-xr-x   1 root  wheel        6 May  2 16:50 urandom -> random
dr-xr-xr-x   2 root  wheel      512 May  2 16:50 usb
crw-r--r--   1 root  operator  0x42 May  2 16:50 usbctl
crw-------   1 root  operator  0x43 May  2 16:50 xpt0
crw-rw-rw-   1 root  wheel      0x8 May  2 09:50 zero
crw-rw-rw-   1 root  operator  0x40 May  2 16:50 zfs


camcontrol devlist

Code: 
root@abc:/dev # camcontrol devlist
<WDC WD10EFRX-68J 01.0>            at scbus0 target 5 lun 0 (pass0)
<WDC WD10EFRX-68J 01.0>            at scbus0 target 24 lun 0 (pass1)
<WDC WD10EFRX-68J 01.0>            at scbus0 target 26 lun 0 (pass2)
<CSSD-V60GB2 1.0>                  at scbus6 target 0 lun 0 (ada0,pass3)
<Corsair CSSD-F40GB2 2.0>          at scbus7 target 0 lun 0 (ada1,pass4)
<HL-DT-ST DVDRAM GH22LS50 TL02>    at scbus8 target 0 lun 0 (pass5,cd0)
<Corsair CSSD-F80GB2-A 2.1a>       at scbus9 target 0 lun 0 (ada2,pass6)
<AHCI SGPIO Enclosure 1.00 0001>   at scbus12 target 0 lun 0 (ses0,pass7)

grep sectors /var/run/dmesg.boot

Code: 
root@abc:/dev # grep sectors /var/run/dmesg.boot
ada0: 57241MB (117231408 512 byte sectors: 16H 63S/T 16383C)
ada1: 38164MB (78161328 512 byte sectors: 16H 63S/T 16383C)
ada2: 76319MB (156301488 512 byte sectors: 16H 63S/T 16383C)
ada0: 57241MB (117231408 512 byte sectors: 16H 63S/T 16383C)
ada1: 38164MB (78161328 512 byte sectors: 16H 63S/T 16383C)
ada2: 76319MB (156301488 512 byte sectors: 16H 63S/T 16383C)
 
e^ipi said:
camcontrol devlist
grep sectors /var/run/dmesg.boot
Click to expand...
That matches your description.

It would seem that the volumes aren't being exported by the Adaptec controller for some reason. Do a # grep -C 5 -i adaptec /var/run/dmesg.boot, which should give you something like this:
Code: 
pci11: <PCI bus> on pcib9
pcib10: <ACPI PCI-PCI bridge> at device 6.0 on pci0
pci12: <ACPI PCI bus> on pcib10
pcib11: <PCI-PCI bridge> mem 0xfc3fe000-0xfc3fffff at device 0.0 on pci12
pci13: <PCI bus> on pcib11
ahd0: <Adaptec 39320LPE Ultra320 SCSI adapter> port 0xdc00-0xdcff,0xd800-0xd8ff mem 0xfc67e000-0xfc67ffff irq 16 at device 4.0 on pci13
ahd0: [ITHREAD]
aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 101-133MHz, 512 SCBs
pcib12: <PCI-PCI bridge> at device 7.0 on pci0
pci14: <PCI bus> on pcib12
pci0: <base peripheral> at device 8.0 (no driver attached)
Look for the line that says "Adaptec" in your output and locate the device name at the beginning of the line (in my example, ahd0). Now, repeat the grep(1) command, substituting the device name you found. In my example, # grep -C 5 -i ahd0 /var/run/dmesg.boot:
Code: 
pci11: <PCI bus> on pcib9
pcib10: <ACPI PCI-PCI bridge> at device 6.0 on pci0
pci12: <ACPI PCI bus> on pcib10
pcib11: <PCI-PCI bridge> mem 0xfc3fe000-0xfc3fffff at device 0.0 on pci12
pci13: <PCI bus> on pcib11
ahd0: <Adaptec 39320LPE Ultra320 SCSI adapter> port 0xdc00-0xdcff,0xd800-0xd8ff 
mem 0xfc67e000-0xfc67ffff irq 16 at device 4.0 on pci13
ahd0: [ITHREAD]
aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 101-133MHz, 512 SCBs
pcib12: <PCI-PCI bridge> at device 7.0 on pci0
pci14: <PCI bus> on pcib12
pci0: <base peripheral> at device 8.0 (no driver attached)
pcib13: <ACPI PCI-PCI bridge> at device 28.0 on pci0
--
ukbd1: <CHESEN PS2 to USB Converter, class 0/0, rev 1.10/0.10, addr 2> on usbus1
kbd3 at ukbd1
ums1: <CHESEN PS2 to USB Converter, class 0/0, rev 1.10/0.10, addr 2> on usbus1
ums1: 5 buttons and [XYZ] coordinates ID=1
uhub6: 4 ports with 4 removable, self powered
sa0 at ahd0 bus 0 scbus1 target 5 lun 0
sa0: <QUANTUM SDLT600 3737> Removable Sequential Access SCSI-4 device 
sa0: 160.000MB/s transfers (80.000MHz DT, offset 120, 16bit)
ses0 at mfi0 bus 0 scbus0 target 32 lun 0
ses0: <DP BACKPLANE 1.05> Fixed Enclosure Services SCSI-5 device 
ses0: 150.000MB/s transfers
--
pass5: 150.000MB/s transfers
SMP: AP CPU #2 Launched!
SMP: AP CPU #1 Launched!
SMP: AP CPU #3 Launched!
Trying to mount root from ufs:/dev/mfid0s1a
ch0 at ahd0 bus 0 scbus1 target 5 lun 1
ch0: <QUANTUM UHDL 0091> Removable Changer SCSI-2 device 
ch0: 160.000MB/s transfers (80.000MHz DT, offset 120, 16bit)
ch0: 16 slots, 1 drive, 1 picker, 0 portals
bce0: Gigabit link up!
In my example, I have a tape drive and a media changer on my Adaptec controller. You should see some sort of disk volume(s). If you don't, the controller is not reporting any configured volumes to FreeBSD and you should go into the controller's setup utility and see if any volumes are configured, etc.
 
Thanks for the quick response.

Here is what grep -C 5 -i aac0 /var/run/dmesg.boot gives:

Code: 
pcib2: <ACPI PCI-PCI bridge> irq 16 at device 6.0 on pci0
pci2: <ACPI PCI bus> on pcib2
aac0: <Adaptec RAID 51245> mem 0xf7a00000-0xf7bfffff irq 16 at device 0.0 on pci2
aac0: Enabling 64-bit address support
aac0: Enable Raw I/O
aac0: Enable 64-bit array
aac0: New comm. interface enabled
aac0: Adaptec 51245, aac driver 2.1.9-1
aacp0 on aac0
aacp1 on aac0
aacp2 on aac0

I have tried almost all configurations I have thought of in the controller's BIOS but I'll try again..
 
dmesg | grep aac

Code: 
aac0: <Adaptec RAID 51245> mem 0xf7a00000-0xf7bfffff irq 16 at device 0.0 on pci2
aac0: Enabling 64-bit address support
aac0: Enable Raw I/O
aac0: Enable 64-bit array
aac0: New comm. interface enabled
aac0: Adaptec 51245, aac driver 2.1.9-1
aacp0 on aac0
aacp1 on aac0
aacp2 on aac0
pass0 at aacp0 bus 0 scbus0 target 5 lun 0
pass1 at aacp0 bus 0 scbus0 target 24 lun 0
pass2 at aacp0 bus 0 scbus0 target 26 lun 0
module_register: module aac/aacp already exists!
Module aac/aacp failed to register: 17
module_register: module aac/aacd already exists!
Module aac/aacd failed to register: 17
module_register: module pci/aac already exists!
Module pci/aac failed to register: 17
module_register: module pci/aacch already exists!
Module pci/aacch failed to register: 17
module_register: module aacraid/aacraidp already exists!
Module aacraid/aacraidp failed to register: 17
module_register: module pci/aacraid already exists!
Module pci/aacraid failed to register: 17
aac0: <Adaptec RAID 51245> mem 0xf7a00000-0xf7bfffff irq 16 at device 0.0 on pci2
aac0: Enabling 64-bit address support
aac0: Enable Raw I/O
aac0: Enable 64-bit array
aac0: New comm. interface enabled
aac0: Adaptec 51245, aac driver 2.1.9-1
aacp0 on aac0
aacp1 on aac0
aacp2 on aac0
pass0 at aacp0 bus 0 scbus0 target 5 lun 0
pass1 at aacp0 bus 0 scbus0 target 24 lun 0
pass2 at aacp0 bus 0 scbus0 target 26 lun 0
module_register: module aac/aacp already exists!
Module aac/aacp failed to register: 17
module_register: module aac/aacd already exists!
Module aac/aacd failed to register: 17
module_register: module pci/aac already exists!
Module pci/aac failed to register: 17
module_register: module pci/aacch already exists!
Module pci/aacch failed to register: 17
module_register: module aacraid/aacraidp already exists!
Module aacraid/aacraidp failed to register: 17
module_register: module pci/aacraid already exists!
Module pci/aacraid failed to register: 17
aac0: <Adaptec RAID 51245> mem 0xf7a00000-0xf7bfffff irq 16 at device 0.0 on pci2
aac0: Enabling 64-bit address support
aac0: Enable Raw I/O
aac0: Enable 64-bit array
aac0: New comm. interface enabled
aac0: Adaptec 51245, aac driver 2.1.9-1
aacp0 on aac0
aacp1 on aac0
aacp2 on aac0
(probe2:aacp2:0:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00 
(probe2:aacp2:0:0:0): CAM status: CCB request completed with an error
(probe2:aacp2:0:0:0): Retrying command
(probe2:aacp2:0:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00 
(probe2:aacp2:0:0:0): CAM status: CCB request completed with an error
(probe2:aacp2:0:0:0): Retrying command
(probe2:aacp2:0:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00 
(probe2:aacp2:0:0:0): CAM status: CCB request completed with an error
(probe2:aacp2:0:0:0): Retrying command
(probe2:aacp2:0:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00 
(probe2:aacp2:0:0:0): CAM status: CCB request completed with an error
(probe2:aacp2:0:0:0): Retrying command
(probe2:aacp2:0:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00 
(probe2:aacp2:0:0:0): CAM status: CCB request completed with an error
(probe2:aacp2:0:0:0): Retrying command
(probe2:aacp2:0:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00 
(probe2:aacp2:0:0:0): CAM status: CCB request completed with an error
(probe2:aacp2:0:0:0): Error 5, Retries exhausted
ses0 at aacp2 bus 0 scbus2 target 0 lun 0
pass0 at aacp0 bus 0 scbus0 target 5 lun 0
pass1 at aacp0 bus 0 scbus0 target 24 lun 0
pass2 at aacp0 bus 0 scbus0 target 26 lun 0
 
e^ipi said:
I have tried almost all configurations I have thought of in the controller's BIOS but I'll try again..
Click to expand...
If you can't find any controller options that look useful, I'd suggest trying a Linux LiveCD, just to see if it detects the drives / volumes or not. That would help pin it down to either a FreeBSD driver issue or a controller setup issue.
 
e^ipi said:
dmesg | grep aac

Code: 
module_register: module aac/aacp already exists!
Module aac/aacp failed to register: 17
module_register: module aac/aacd already exists!
Module aac/aacd failed to register: 17
module_register: module pci/aac already exists!
Module pci/aac failed to register: 17
module_register: module pci/aacch already exists!
Module pci/aacch failed to register: 17
module_register: module aacraid/aacraidp already exists!
Module aacraid/aacraidp failed to register: 17
module_register: module pci/aacraid already exists!
Module pci/aacraid failed to register: 17
Click to expand...
This looks like you have aac_load="YES" or something similar in /boot/loader.conf. Try removing anything not absolutely essential to booting from that file and see if this error goes away.
Code: 
aac0: <Adaptec RAID 51245> mem 0xf7a00000-0xf7bfffff irq 16 at device 0.0 on pci2
aac0: Enabling 64-bit address support
aac0: Enable Raw I/O
aac0: Enable 64-bit array
aac0: New comm. interface enabled
aac0: Adaptec 51245, aac driver 2.1.9-1
aacp0 on aac0
aacp1 on aac0
aacp2 on aac0
pass0 at aacp0 bus 0 scbus0 target 5 lun 0
pass1 at aacp0 bus 0 scbus0 target 24 lun 0
pass2 at aacp0 bus 0 scbus0 target 26 lun 0
Click to expand...
I don't know why you're getting duplicates of this in the logging buffer. However, the first step will be to clean out your /boot/loader.conf and see what happens.
Code: 
(probe2:aacp2:0:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00 
(probe2:aacp2:0:0:0): CAM status: CCB request completed with an error
(probe2:aacp2:0:0:0): Retrying command
(probe2:aacp2:0:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00 
(probe2:aacp2:0:0:0): CAM status: CCB request completed with an error
(probe2:aacp2:0:0:0): Retrying command
(probe2:aacp2:0:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00 
(probe2:aacp2:0:0:0): CAM status: CCB request completed with an error
(probe2:aacp2:0:0:0): Retrying command
(probe2:aacp2:0:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00 
(probe2:aacp2:0:0:0): CAM status: CCB request completed with an error
(probe2:aacp2:0:0:0): Retrying command
(probe2:aacp2:0:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00 
(probe2:aacp2:0:0:0): CAM status: CCB request completed with an error
(probe2:aacp2:0:0:0): Retrying command
(probe2:aacp2:0:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00 
(probe2:aacp2:0:0:0): CAM status: CCB request completed with an error
(probe2:aacp2:0:0:0): Error 5, Retries exhausted
Click to expand...
This, unfortunately (IMHO), is an all-too-frequent form of blather from the drivers (not restricted to aac(4)) at boot time, and de-sensitizes users to real problems. FreeBSD does this for CD/DVD drives and tape drives with no media inserted at boot time, as well as (new misfeature in 10.x) on mfid(4) member drives. It almost certainly isn't the underlying problem in your situation - the driver is asking the chassis "How many logical units do you have?" and the chassis is responding "I'm a chassis, I don't have logical units!". This repeats 5 times until the driver gives up.
 
It seems I have a similar problem:
Code: 
# camcontrol devlist
<SEAGATE ST1000NM0001 0002>        at scbus0 target 0 lun 0 (pass0)
<SEAGATE ST1000NM0001 0002>        at scbus0 target 1 lun 0 (pass1)
<SEAGATE ST1000NM0001 0002>        at scbus0 target 2 lun 0 (pass2)
<SEAGATE ST1000NM0001 0002>        at scbus0 target 3 lun 0 (pass3)
<TEAC DV-W28E-R 1.0A>              at scbus3 target 0 lun 0 (cd0,pass4)
<WDC WD10EFRX-68PJCN0 01.01A01>    at scbus5 target 0 lun 0 (pass5,ada0)
<PepperC Virtual Disc 1 0.01>      at scbus10 target 0 lun 0 (pass6,cd1)
I've tried the install media of Ubuntu Server 20.04 and it "sees" 5 hard disks.

Any ideas?
 

Attachments

  • dmesg.boot.tkrenn.txt
    11.1 KB · Views: 177
You must log in or register to reply here.
Back
Top