LSI MegaRaid pass through causing kernel panics and reboots

dev/null

Cadet
Joined
Apr 19, 2021
Messages
9
I am running an hp DL380 G7 with dual 5620 Xeons that are accompanied to 4, 16gb, DDR3 Sticks. The raid card is a Perc 320 Ultrascsi. The pciconf shows an address of 0:12:14:0, and I entered it in under 12/14/0. I had to quickly delete the VMs twice on boot up or it would panic and take the whole machine with it. I could stop it at boot up, but these vms would crash if and only if the pass through was added to the device list.

I followed> this tutorial <to the 'T' and this is the result.

Any clues?
 

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,681
PCI passthru support was very weak on systems before Sandy Bridge, lots of problems have been reported over the years with people trying to run FreeNAS as a VM under ESXi on gear that predates Sandy.

It sounds like you have something truly ancient like a PERC 4, running on a very old machine, the G7. There is little reason to think that the PERC 4 will work correctly; PCI passthru is a bit of a trick that really requires both a card and the host it is in to be very well behaved, something not really observed in a lot of older hardware.
 

dev/null

Cadet
Joined
Apr 19, 2021
Messages
9
PCI passthru support was very weak on systems before Sandy Bridge, lots of problems have been reported over the years with people trying to run FreeNAS as a VM under ESXi on gear that predates Sandy.

It sounds like you have something truly ancient like a PERC 4, running on a very old machine, the G7. There is little reason to think that the PERC 4 will work correctly; PCI passthru is a bit of a trick that really requires both a card and the host it is in to be very well behaved, something not really observed in a lot of older hardware.

Then is there a way to get the program "mtx" working so I can operate the tape library in a jail? I am not familiar with the device tree in bsd, and I cannot identify the tape drive or library for control.
 

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,681
In my opinion, the jail is much more likely to be a viable option, but may require some tinkering to get it to work. A jail is working in the kernel of the host system, so as long as it is supported by the kernel, there's at least a reasonable chance.

Jails have, by default, a limited view of the devices in /dev, controlled by the selection of devfs_ruleset in the jail setup. Since I don't use jails or VM's under FreeNAS, I am speaking from a general knowledge of FreeBSD jails, but I do not have specific guidance for you, sorry. I know that there have been discussions of this on the forum in the past.
 

dev/null

Cadet
Joined
Apr 19, 2021
Messages
9
In my opinion, the jail is much more likely to be a viable option, but may require some tinkering to get it to work. A jail is working in the kernel of the host system, so as long as it is supported by the kernel, there's at least a reasonable chance.

Jails have, by default, a limited view of the devices in /dev, controlled by the selection of devfs_ruleset in the jail setup. Since I don't use jails or VM's under FreeNAS, I am speaking from a general knowledge of FreeBSD jails, but I do not have specific guidance for you, sorry. I know that there have been discussions of this on the forum in the past.

Since the component that uses UltraSCSI 3 is an lto4 library would it be more sensible at this point for me to just install the necessary components directly to the main os? The backup programs used for the library are as integral as snapshots and adding disk shelves. Even the humble program "tar" is in the main runup.
 

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,681
It's not sensible from the aspect that while it might result in an easier fix today, it may break horribly down the road, in less-easy-to-resolve ways. Just my opinion.
 

dev/null

Cadet
Joined
Apr 19, 2021
Messages
9
This may not matter. I have learned what the drive naming scheme for scsi is supposed to be, and the drives do not show up -_-
 

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,681
I doubt the tape driver is included by default. Perhaps we could take this one step at a time and not rush to conclusions.

Does your new SCSI adapter show up in the output of /var/run/dmesg.boot?

I wouldn't be shocked if it was showing up as an mpt SCSI adapter. That would be a great start.
 

dev/null

Cadet
Joined
Apr 19, 2021
Messages
9
I found amr0: <LSILogic PERC 4e/DC> under amr0: along with "delete logical drives supported by controller". Unfortunately it is an inappropriate ioctl device for both tar and mt.
 

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,681
Yeah, but that's the SCSI controller. The device would be /dev/sa0, but I'm having a bit of a time confirming that's actually been compiled into the kernel. If you can locate the kernel config file over on github, look for "device sa". Or just see if /dev/sa0 exists on your system.
 

dev/null

Cadet
Joined
Apr 19, 2021
Messages
9
found it

Code:
# ATA/SCSI peripherals
device        scbus            # SCSI bus (required for ATA/SCSI)
device        ch            # SCSI media changers
device        da            # Direct Access (disks)
device        sa            # Sequential Access (tape etc)
device        cd            # CD
device        pass            # Passthrough device (direct ATA/SCSI access)
device        ses            # Enclosure Services (SES and SAF-TE)
device        ctl            # CAM Target Layer
 

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,681
That's the ticket.

See if any lines starting with 'sa' show up on /var/run/dmesg.boot
 

dev/null

Cadet
Joined
Apr 19, 2021
Messages
9
Grep returned no device that starts with "sa". The closest return is an isa0 isa bus (I should figure out where that is so I can hook into it later on).
 

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,681
Then it's probably necessary to see more of what's going on. If you're willing, bearing in mind that it can reveal identifying information like ethernet MAC addresses, please consider posting the contents of /var/run/dmesg.boot after making sure the tape drive is hooked up and ready to go and doing a reboot, so the system gets a chance to scan for the tape drive. You are also welcome to just take a real close look at the contents yourself and see if you can figure out anything interesting that looks related to amr0, sa0, scbus0, etc.
 

dev/null

Cadet
Joined
Apr 19, 2021
Messages
9
Code:
Copyright (c) 1992-2020 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 12.2-RELEASE-p6 f2858df162b(HEAD) TRUENAS amd64
FreeBSD clang version 10.0.1 (git@github.com:llvm/llvm-project.git llvmorg-10.0.1-0-gef32c611aa2)
VT(vga): text 80x25
CPU: Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz (2399.36-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x206c2  Family=0x6  Model=0x2c  Stepping=2
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x29ee3ff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AESNI>
  AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
  AMD Features2=0x1<LAHF>
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
  TSC: P-state invariant, performance statistics
real memory  = 68719476736 (65536 MB)
avail memory = 66671452160 (63582 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: <HP     ProLiant>
FreeBSD/SMP: Multiprocessor System Detected: 16 CPUs
FreeBSD/SMP: 2 package(s) x 4 core(s) x 2 hardware threads
random: unblocking device.
Firmware Warning (ACPI): Invalid length for FADT/Pm1aControlBlock: 32, using default 16 (20200430/tbfadt-850)
Firmware Warning (ACPI): Invalid length for FADT/Pm2ControlBlock: 32, using default 8 (20200430/tbfadt-850)
ioapic1 <Version 2.0> irqs 24-47 on motherboard
ioapic0 <Version 2.0> irqs 0-23 on motherboard
Launching APs: 1 11 10 13 9 4 2 7 3 6 15 5 14 12 8
Timecounter "TSC-low" frequency 1199682474 Hz quality 1000
random: entropy device external interface
kbd1 at kbdmux0
mlx5en: Mellanox Ethernet driver 3.5.2 (September 2019)
nexus0
vtvga0: <VT VGA driver> on motherboard
aesni0: <AES-CBC,AES-CCM,AES-GCM,AES-ICM,AES-XTS> on motherboard
padlock0: No ACE support.
cryptosoft0: <software crypto> on motherboard
acpi0: <HP ProLiant> on motherboard
acpi0: Power Button (fixed)
acpi0: _OSC failed: AE_BUFFER_OVERFLOW
cpu0: <ACPI CPU> on acpi0
attimer0: <AT timer> port 0x40-0x43 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 950
Event timer "HPET" frequency 14318180 Hz quality 350
Event timer "HPET1" frequency 14318180 Hz quality 340
Event timer "HPET2" frequency 14318180 Hz quality 340
Event timer "HPET3" frequency 14318180 Hz quality 340
atrtc0: <AT realtime clock> port 0x70-0x71 on acpi0
atrtc0: registered as a time-of-day clock, resolution 1.000000s
Event timer "RTC" frequency 32768 Hz quality 0
apei0: <ACPI Platform Error Interface> on acpi0
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x908-0x90b on acpi0
pcib0: <ACPI Host-PCI bridge> on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
ciss0: <HP Smart Array P410i> port 0x4000-0x40ff mem 0xfbc00000-0xfbdfffff,0xfbbf0000-0xfbbf0fff irq 28 at device 0.0 on pci1
ciss0: PERFORMANT Transport
pcib2: <ACPI PCI-PCI bridge> at device 2.0 on pci0
pci2: <ACPI PCI bus> on pcib2
pcib3: <ACPI PCI-PCI bridge> at device 3.0 on pci0
pci3: <ACPI PCI bus> on pcib3
pcib4: <ACPI PCI-PCI bridge> at device 4.0 on pci0
pci4: <ACPI PCI bus> on pcib4
pcib5: <ACPI PCI-PCI bridge> at device 5.0 on pci0
pci5: <ACPI PCI bus> on pcib5
pcib6: <ACPI PCI-PCI bridge> at device 6.0 on pci0
pci6: <ACPI PCI bus> on pcib6
pcib7: <ACPI PCI-PCI bridge> at device 7.0 on pci0
pci7: <ACPI PCI bus> on pcib7
isp0: <Qlogic ISP 2432 PCI FC-AL Adapter> port 0x5000-0x50ff mem 0xfbff0000-0xfbff3fff irq 30 at device 0.0 on pci7
pcib8: <ACPI PCI-PCI bridge> at device 8.0 on pci0
pci8: <ACPI PCI bus> on pcib8
pcib9: <ACPI PCI-PCI bridge> at device 0.0 on pci8
pci9: <ACPI PCI bus> on pcib9
amr0: <LSILogic MegaRAID 1.53> mem 0xf1af0000-0xf1afffff,0xfbec0000-0xfbefffff irq 38 at device 14.0 on pci9
amr0: Using 64-bit DMA
amr0: delete logical drives supported by controller
amr0: <LSILogic PERC 4e/DC> Firmware 5B2D, BIOS H435, 128MB RAM
pcib10: <ACPI PCI-PCI bridge> at device 0.2 on pci8
pci10: <ACPI PCI bus> on pcib10
pcib11: <ACPI PCI-PCI bridge> at device 9.0 on pci0
pci11: <ACPI PCI bus> on pcib11
pcib12: <ACPI PCI-PCI bridge> at device 10.0 on pci0
pci12: <ACPI PCI bus> on pcib12
pci0: <base peripheral, interrupt controller> at device 20.0 (no driver attached)
pci0: <base peripheral, interrupt controller> at device 20.1 (no driver attached)
pci0: <base peripheral, interrupt controller> at device 20.2 (no driver attached)
pcib13: <ACPI PCI-PCI bridge> at device 28.0 on pci0
pci13: <ACPI PCI bus> on pcib13
bce0: <HP NC382i DP Multifunction Gigabit Server Adapter (C0)> mem 0xf4000000-0xf5ffffff irq 16 at device 0.0 on pci13
miibus0: <MII bus> on bce0
brgphy0: <BCM5709 10/100/1000baseT PHY> PHY 1 on miibus0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
bce0: Using defaults for TSO: 65518/35/2048
bce0: Ethernet address: HEX
bce0: ASIC (0x57092003);
bce0: link state changed to DOWN
Rev (C0); Bus (PCIe x2, 2.5Gbps); B/C (5.2.3); Bufs (RX:2;TX:2;PG:8); Flags (SPLT|MSI|MFW); MFW (NCSI 2.0.6)
Coal (RX:6,6,18,18; TX:20,20,80,80)
bce1: <HP NC382i DP Multifunction Gigabit Server Adapter (C0)> mem 0xf2000000-0xf3ffffff irq 17 at device 0.1 on pci13
miibus1: <MII bus> on bce1
brgphy1: <BCM5709 10/100/1000baseT PHY> PHY 1 on miibus1
brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
bce1: Using defaults for TSO: 65518/35/2048
bce1: Ethernet address: 4HEX
bce1: ASIC (0x57092003);
bce1: link state changed to DOWN
Rev (C0); Bus (PCIe x2, 2.5Gbps); B/C (5.2.3); Bufs (RX:2;TX:2;PG:8); Flags (SPLT|MSI|MFW); MFW (NCSI 2.0.6)
Coal (RX:6,6,18,18; TX:20,20,80,80)
pcib14: <ACPI PCI-PCI bridge> at device 28.2 on pci0
pci14: <ACPI PCI bus> on pcib14
bce2: <HP NC382i DP Multifunction Gigabit Server Adapter (C0)> mem 0xf8000000-0xf9ffffff irq 18 at device 0.0 on pci14
miibus2: <MII bus> on bce2
brgphy2: <BCM5709 10/100/1000baseT PHY> PHY 1 on miibus2
brgphy2:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
bce2: Using defaults for TSO: 65518/35/2048
bce2: Ethernet address: 4HEX
bce2: ASIC (0x57092003); Rev (C0); Bus (PCIe x2, 2.5Gbps); B/C (5.2.3); Bufs (RX:2;TX:2;PG:8); Flags (SPLT|MSI)
Coal (RX:6,6,18,18; TX:20,20,80,80)
bce3: <HP NC382i DP Multifunction Gigabit Server Adapter (C0)> mem 0xf6000000-0xf7ffffff irq 19 at device 0.1 on pci14
miibus3: <MII bus> on bce3
brgphy3: <BCM5709 10/100/1000baseT PHY> PHY 1 on miibus3
brgphy3:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow
bce3: Using defaults for TSO: 65518/35/2048
bce3: Ethernet address: 4HEX
bce3: ASIC (0x57092003); Rev (C0); Bus (PCIe x2, 2.5Gbps); B/C (5.2.3); Bufs (RX:2;TX:2;PG:8); Flags (SPLT|MSI)
Coal (RX:6,6,18,18; TX:20,20,80,80)
pcib15: <ACPI PCI-PCI bridge> at device 28.4 on pci0
pci15: <ACPI PCI bus> on pcib15
uhci0: <HP iLO Standard Virtual USB controller> port 0x3c00-0x3c1f irq 17 at device 0.4 on pci15
usbus0 on uhci0
usbus0: 12Mbps Full Speed USB v1.0
uhci1: <Intel 82801JI (ICH10) USB controller USB-A> port 0x1000-0x101f irq 20 at device 29.0 on pci0
usbus1 on uhci1
usbus1: 12Mbps Full Speed USB v1.0
uhci2: <Intel 82801JI (ICH10) USB controller USB-B> port 0x1020-0x103f irq 23 at device 29.1 on pci0
usbus2 on uhci2
usbus2: 12Mbps Full Speed USB v1.0
uhci3: <Intel 82801JI (ICH10) USB controller USB-C> port 0x1040-0x105f irq 22 at device 29.2 on pci0
usbus3 on uhci3
usbus3: 12Mbps Full Speed USB v1.0
uhci4: <Intel 82801JI (ICH10) USB controller USB-F> port 0x1060-0x107f irq 23 at device 29.3 on pci0
usbus4 on uhci4
usbus4: 12Mbps Full Speed USB v1.0
ehci0: <Intel 82801JI (ICH10) USB 2.0 controller USB-A> mem 0xf1bf0000-0xf1bf03ff irq 20 at device 29.7 on pci0
usbus5: EHCI version 1.0
usbus5 on ehci0
usbus5: 480Mbps High Speed USB v2.0
pcib16: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci16: <ACPI PCI bus> on pcib16
vgapci0: <VGA-compatible display> port 0x2000-0x20ff mem 0xe8000000-0xefffffff,0xf1cf0000-0xf1cfffff irq 23 at device 3.0 on pci16
vgapci0: Boot video device
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel ICH10 SATA300 controller> port 0x1080-0x1087,0x1088-0x108b,0x1090-0x1097,0x1098-0x109b,0x10a0-0x10af,0x10b0-0x10bf irq 17 at device 31.2 on pci0
ata2: <ATA channel> at channel 0 on atapci0
ata3: <ATA channel> at channel 1 on atapci0
acpi_tz0: <Thermal Zone> on acpi0
ipmi0: <IPMI System Interface> port 0xca2-0xca3 on acpi0
ipmi0: KCS mode found at io 0xca2 on acpi
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
acpi_syscontainer0: <System Container> port 0x2e-0x2f,0x620-0x65f,0x680-0x69f,0x600-0x61f,0x660-0x67f,0x300-0x31f on acpi0
uart0: <Non-standard ns8250 class UART with FIFOs> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
ichwd0: <Intel ICH10 watchdog timer> on isa0
ichwd0: ICH WDT present but disabled in BIOS or hardware
device_attach: ichwd0 attach returned 6
ichwd0: <Intel ICH10 watchdog timer> at port 0x930-0x937,0x960-0x97f on isa0
ichwd0: ICH WDT present but disabled in BIOS or hardware
device_attach: ichwd0 attach returned 6
orm0: <ISA Option ROM> at iomem 0xc0000-0xcafff pnpid ORM0000 on isa0
uart1: <Non-standard ns8250 class UART with FIFOs> at port 0x2f8 irq 3 on isa0
coretemp0: <CPU On-Die Thermal Sensors> on cpu0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 13
device_attach: est0 attach returned 6
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 13
device_attach: est1 attach returned 6
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 13
device_attach: est2 attach returned 6
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 13
device_attach: est3 attach returned 6
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 13
device_attach: est4 attach returned 6
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 13
device_attach: est5 attach returned 6
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 13
device_attach: est6 attach returned 6
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 13
device_attach: est7 attach returned 6
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 13
device_attach: est8 attach returned 6
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 13
device_attach: est9 attach returned 6
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 13
device_attach: est10 attach returned 6
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 13
device_attach: est11 attach returned 6
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 13
device_attach: est12 attach returned 6
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 13
device_attach: est13 attach returned 6
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 13
device_attach: est14 attach returned 6
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 13
device_attach: est15 attach returned 6
Timecounters tick every 1.000 msec
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
ipfw2 (+ipv6) initialized, divert enabled, nat enabled, default to accept, logging disabled
amr0: delete logical drives supported by controller
ipmi0: IPMI device rev. 1, firmware rev. 1.26, version 2.0, device support mask 0xf
ipmi0: Number of channels 0
ipmi0: Attached watchdog
Trying to mount root from zfs:boot-pool/ROOT/default []...
Root mount waiting for: CAM usbus0 usbus1 usbus2 usbus3 usbus4 usbus5ugen3.1: <Intel UHCI root HUB> at usbus3

uhub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus3
ugen2.1: <Intel UHCI root HUB> at usbus2
uhub1: ugen5.1: <Intel EHCI root HUB> at usbus5
<Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus2
ugen4.1: <Intel UHCI root HUB> at usbus4
uhub2: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus5
ugen1.1: <Intel UHCI root HUB> at usbus1
ugen0.1: <HP UHCI root HUB> at usbus0
uhub3: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
uhub4: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus4
uhub5: <HP UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
uhub0: 2 ports with 2 removable, self powered
uhub4: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
uhub5: 2 ports with 2 removable, self powered
uhub3: 2 ports with 2 removable, self powered
Root mount waiting for: CAM usbus0 usbus5
ada0 at ata2 bus 0 scbus3 target 0 lun 0
ada0: <PLEXTOR PX-256M7VG 1.01> ATA8-ACS SATA 3.x device
ada0: Serial Number P02618122918
ada0: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 512bytes)
ada0: 244198MB (500118192 512 byte sectors)
da1 at ciss0 bus 0 scbus0 target 1 lun 0
da1: <HP RAID 1(1+0) OK> Fixed Direct Access SPC-3 SCSI device
da1: Serial Number 50014380165F7E10
da1: 135.168MB/s transfers
da1: Command Queueing enabled
da1: 69973MB (143305920 512 byte sectors)
da0 at ciss0 bus 0 scbus0 target 0 lun 0
da0: <HP RAID 1(1+0) OK> Fixed Direct Access SPC-3 SCSI device
da0: Serial Number 50014380165F7E10
da0: 135.168MB/s transfers
da0: Command Queueing enabled
da0: 69973MB (143305920 512 byte sectors)
da2 at ciss0 bus 0 scbus0 target 2 lun 0
da2: <HP RAID 0 OK> Fixed Direct Access SPC-3 SCSI device
da2: Serial Number 50014380165F7E10
da2: 135.168MB/s transfers
da2: Command Queueing enabled
da2: 139979MB (286677120 512 byte sectors)
da3 at ciss0 bus 0 scbus0 target 3 lun 0
da3: <HP RAID 0 OK> Fixed Direct Access SPC-3 SCSI device
da3: Serial Number 50014380165F7E10
da3: 135.168MB/s transfers
da3: Command Queueing enabled
da3: 139979MB (286677120 512 byte sectors)
da4 at ciss0 bus 0 scbus0 target 4 lun 0
da4: <HP RAID 0 OK> Fixed Direct Access SPC-3 SCSI device
da4: Serial Number 50014380165F7E10
da4: 135.168MB/s transfers
da4: Command Queueing enabled
da4: 858451MB (1758109232 512 byte sectors)
da5 at ciss0 bus 0 scbus0 target 5 lun 0
da5: <HP RAID 0 OK> Fixed Direct Access SPC-3 SCSI device
da5: Serial Number 50014380165F7E10
da5: 135.168MB/s transfers
da5: Command Queueing enabled
da5: 858451MB (1758109232 512 byte sectors)
ugen0.2: <HP Virtual Keyboard> at usbus0
ukbd0 on uhub5
ukbd0: <Virtual Keyboard > on usbus0
kbd2 at ukbd0
ums0 on uhub5
ums0: <Virtual Mouse> on usbus0
Root mount waiting for: usbus5
uhub2: 8 ports with 8 removable, self powered
lo0: link state changed to UP
GEOM_MIRROR: Cancelling unmapped because of da3p1.
GEOM_MIRROR: Cancelling unmapped because of da4p1.
GEOM_MIRROR: Cancelling unmapped because of da5p1.
GEOM_MIRROR: Device mirror/swap0 launched (3/3).
GEOM_ELI: Device mirror/swap0.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI:     Crypto: hardware
hwpmc: SOFT/16/64/0x67<INT,USR,SYS,REA,WRI> TSC/1/64/0x20<REA> IAP/4/48/0x3ff<INT,USR,SYS,EDG,THR,REA,WRI,INV,QUA,PRC> IAF/3/48/0x67<INT,USR,SYS,REA,WRI> UCP/8/48/0x3f8<EDG,THR,REA,WRI,INV,QUA,PRC> UCF/1/48/0x60<REA,WRI>
CPU: Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz (2399.36-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x206c2  Family=0x6  Model=0x2c  Stepping=2
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
  Features2=0x29ee3ff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,POPCNT,AESNI>
  AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
  AMD Features2=0x1<LAHF>
  Structured Extended Features3=0x9c000000<IBPB,STIBP,L1DFL,SSBD>
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
  TSC: P-state invariant, performance statistics
root@nas[~]# 
 

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,681
Well, that's interesting.

First, I hope you know that your RAID controller that you are using for the pool is a bad choice; this is (probably) unrelated to your problems.

https://www.truenas.com/community/t...s-and-why-cant-i-use-a-raid-controller.81931/

You're right in that nothing seems to be showing up. I do notice that it looks like the amr is being allocated scbus designations. If I'm correct, that's a two-bus controller, and it looks like it is getting assigned scbus1 and scbus2 ... which appear nowhere in the dmesg output, but you can feel them there because there is a scbus3.

Does anything interesting happen if you do a "camcontrol rescan all"? "camcontrol devlist -v"? Has this tape drive been used with this controller configured in the manner it currently is in the past?
 

dev/null

Cadet
Joined
Apr 19, 2021
Messages
9
You are right that it is a raid controller, but I went ahead and fired up Ubuntu live on the server to see if it would work. Not only did it spot the tape library, but it also ran its full initialization procedure checking the drive, magazines, and transport.

Here are the results for: camcontrol rescan all
Code:
Re-scan of bus 0 was successful
Re-scan of bus 1 was successful
Re-scan of bus 2 was successful
Re-scan of bus 3 was successful
Re-scan of bus 4 was successful
Re-scan of bus 5 was successful


And here is the result for: camcontrol devlist -v
Code:
scbus0 on ciss0 bus 0:
<HP RAID 1(1+0) OK>                at scbus0 target 0 lun 0 (pass0,da0)
<HP RAID 1(1+0) OK>                at scbus0 target 1 lun 0 (pass1,da1)
<HP RAID 0 OK>                     at scbus0 target 2 lun 0 (pass2,da2)
<HP RAID 0 OK>                     at scbus0 target 3 lun 0 (pass3,da3)
<HP RAID 0 OK>                     at scbus0 target 4 lun 0 (pass4,da4)
<HP RAID 0 OK>                     at scbus0 target 5 lun 0 (pass5,da5)
scbus1 on ciss0 bus 32:
scbus2 on isp0 bus 0:
<>                                 at scbus2 target -1 lun ffffffff ()
scbus3 on ata2 bus 0:
<PLEXTOR PX-256M7VG 1.01>          at scbus3 target 0 lun 0 (pass6,ada0)
<>                                 at scbus3 target -1 lun ffffffff ()
scbus4 on ata3 bus 0:
<>                                 at scbus4 target -1 lun ffffffff ()
scbus5 on camsim0 bus 0:
<>                                 at scbus5 target -1 lun ffffffff ()
scbus-1 on xpt0 bus 0:
<>                                 at scbus-1 target -1 lun ffffffff (xpt0)
 

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,681
I'm sorry, but I'm just not spotting a particular issue. It could be that the amr driver isn't working correctly on your system. If you're intent on trying to make this work, it could be that a different parallel SCSI controller might work.

The mpt driver, generally well supported by FreeBSD, claims to support the LSI Logic 53c1030 and LSI2x320-X controllers.

You could also try checking on the FreeBSD-scsi mailing list to see if anyone has any suggestions.
 
Top