Cam status ccb request completed with an error freenas

Модераторы: rewuxiin, kulia

Вернуться в «FreeNAS»

CAM status: CCB request completed with an error

dfriestedt

Dabbler

I’m getting a recurring error message: CAM status: CCB request completed with an error

The system is rebooting every 2 hours or so. Any thought on what could be happening here from the error logs?

John Digital

dfriestedt

Dabbler

John Digital

sretalla

Powered by Neutrality

Aiming to mostly replicate the build from @Stux (with some mods, hopefully around about as good as that link)

• 4 xSamsung 850 EVO Basic (500GB, 2.5″) — — VMs/Jails
• 1 xASUS Z10PA-D8 (LGA 2011-v3, Intel C612 PCH, ATX) — — Dual socket MoBo
• 2 xWD Green 3D NAND (120GB, 2.5″) — — Boot drives (maybe mess around trying out the thread to put swap here too link)
• 1 x Kingston UV400 120GB SSD — boot drive (hit the 3D NAND/TRIM bug with the original WD green selection, failing scrub and showing as corrupted OS files) Decided to go with no mirror and use the config backup script
• 2 xIntel Xeon E5-2620 v4 (LGA 2011-v3, 2.10GHz) — — 8 core/16 threads per Chip
• 2 xNoctua NH-U9S (12.50cm)
• 1 xCorsair HX1200 (1200W) — PSU to support 24 HDD + several SSD and PCI cards
• 4 xKingston Value RAM (32GB, DDR4-2400, ECC RDIMM 288)
• 2 xNoctua NF-A8 PWM Premium 80mm PC Computer Case Fan
• 3 xNoctua NF-F12 PWM Cooling Fan
• 3 xNoctua NF-F12 PPC 3000 PWM (120mm) * having noted later in Stux’s thread that 1500 RPM is not sufficient to cool the HDDs. Corsair Commander Pro to control the fans (see script and code)
• 1 xNORCO 4U Rack Mount 24 x Hot-Swappable SATA/SAS 6G Drive Bays Server Rack mount RPC-4224
• 6 xCableCreation Internal Mini SAS HD Cable, Mini SAS SFF-8643 to Mini SAS 36Pin SFF-8087 Cable
• 1 xLSI Logic Controller Card 05-25699-00 9305-24i 24-Port SAS 12Gb/s PCI-Express 3.0 Host Bus Adapter
• TrueNAS Core 13.0-U3.1
• Use existing Drives 8 x10TB WD Red, 8 x4TB WD Purple, + a mix of WD Purple and shucked WD Elements 12TB x 8

ESXi-pfSense-FreeNAS-Docker host

CASE: Fractal Node 804
MB: ASUS x-99M WS
CPU: Xeon E5-2620v4 + Corsair H60 Cooler block
RAM: CRUCIAL 64GB DDR4-2133 ECC RDIMMs
HDD: WD RED 3TBx8
SSD: 4 xSamsung 850 EVO Basic (500GB, 2.5″) — — VMs/Jails
HBA: LSI 9300-16i
OS: 1 x Kingston UV400 120GB SSD — boot drive
PSU: Corsair RM1000
Version: TrueNAS CORE 13.0 -U3.1
FANS: 3xFractal R3 120mm — 3 Front, 1 Rear. Corsair Commander Pro to control the fans (see script and code)
CPU FAN: 1xCorsair H60 CPU Radiator — Front
NIC: Intel EXPI9402PTBLK Pro, Dual-Gigabit Adapter (plus the 2 onboard Intel NICs, 1x 210, 1x 218)

VM/Docker host, using ESXi and running pfSense alongside FreeNAS (separate Dual Intel NIC added, dedicated to the pfSense VM)

TrueNAS CORE test system:

CASE: Old Silverstone HTPC case
MB: ASUS x-99M WS
CPU: Xeon E5-2620v4 + Corsair H60 Cooler block
RAM: CRUCIAL 32GB DDR4-2133 ECC RDIMMs
HDD: WD RED 8TBx3
OS: 1 x Kingston UV400 120GB SSD — boot drive
PSU: Corsair RM1000
Version: TrueNAS CORE 13.0-U3

2x Intel NUCs running TrueNAS SCALE 22.12 RC1
64GB RAM
10th Generation Intel i7
Samsung NVME SSD 1TB, QVO SSD 1TB
Boot from Samsung Portable T7 SSD USBC

CASE: Fractal Node 304 running TrueNAS SCALE 22.12 RC1
MB: ASUS P10S-I Series
RAM: 32 GB
CPU: Intel(R) Xeon(R) CPU E3-1240L v5 @ 2.10GHz
HDD: 3 WD REDs and a few SSDs
PSU: Fractal ION 2+ 650W

dfriestedt

Dabbler

Both PASSED the test just now. I’ll start by replacing the cable. This is a new setup and with it I’ve been TEARING through hard drives at an alarming rate. They are the Western Digital 8TB Ultrastar DC HC320 SATA HDD — 7200 RPM Class, SATA 6 Gb/s, 256MB Cache, 3.5″

I bought them online from Amazon and figured they were selling me crappy drives. I literally replaced about 10 of them through the WD warranty service. But even the replaced drives from WD are going bad quickly. I have 1 go bad every week. No kidding. I’m wondering if the failure rate has something to do with the errors I’m seeing in the logs.

I will replace the cable in question. It’s this one: «CableCreation 6.6FT External HD Mini SAS SFF-8644 to SFF-8644 Cable»

Fredda

dfriestedt

Dabbler

Here is the output. Now that I think about it I should list 2 controller cards in my signature. One for the Expander Chassis and one for the local drives. The expander card is: LSI Logic Controller Card 05-25704-00 9305-16e 16-Port External SAS 12Gb/s PCI-Express 3.0 Host Bus Adapter Single

I need to add the new local card, for the drives in the Freenas Chassis. I will do that this AM. But the output below looks to be for the 9305 card.

sretalla

Powered by Neutrality

It’s more likely the inverse. the errors in the logs are to do with the failures you’re seeing.

Certainly finding a root cause is a good idea with that very high failure rate.

Aiming to mostly replicate the build from @Stux (with some mods, hopefully around about as good as that link)

• 4 xSamsung 850 EVO Basic (500GB, 2.5″) — — VMs/Jails
• 1 xASUS Z10PA-D8 (LGA 2011-v3, Intel C612 PCH, ATX) — — Dual socket MoBo
• 2 xWD Green 3D NAND (120GB, 2.5″) — — Boot drives (maybe mess around trying out the thread to put swap here too link)
• 1 x Kingston UV400 120GB SSD — boot drive (hit the 3D NAND/TRIM bug with the original WD green selection, failing scrub and showing as corrupted OS files) Decided to go with no mirror and use the config backup script
• 2 xIntel Xeon E5-2620 v4 (LGA 2011-v3, 2.10GHz) — — 8 core/16 threads per Chip
• 2 xNoctua NH-U9S (12.50cm)
• 1 xCorsair HX1200 (1200W) — PSU to support 24 HDD + several SSD and PCI cards
• 4 xKingston Value RAM (32GB, DDR4-2400, ECC RDIMM 288)
• 2 xNoctua NF-A8 PWM Premium 80mm PC Computer Case Fan
• 3 xNoctua NF-F12 PWM Cooling Fan
• 3 xNoctua NF-F12 PPC 3000 PWM (120mm) * having noted later in Stux’s thread that 1500 RPM is not sufficient to cool the HDDs. Corsair Commander Pro to control the fans (see script and code)
• 1 xNORCO 4U Rack Mount 24 x Hot-Swappable SATA/SAS 6G Drive Bays Server Rack mount RPC-4224
• 6 xCableCreation Internal Mini SAS HD Cable, Mini SAS SFF-8643 to Mini SAS 36Pin SFF-8087 Cable
• 1 xLSI Logic Controller Card 05-25699-00 9305-24i 24-Port SAS 12Gb/s PCI-Express 3.0 Host Bus Adapter
• TrueNAS Core 13.0-U3.1
• Use existing Drives 8 x10TB WD Red, 8 x4TB WD Purple, + a mix of WD Purple and shucked WD Elements 12TB x 8

ESXi-pfSense-FreeNAS-Docker host

CASE: Fractal Node 804
MB: ASUS x-99M WS
CPU: Xeon E5-2620v4 + Corsair H60 Cooler block
RAM: CRUCIAL 64GB DDR4-2133 ECC RDIMMs
HDD: WD RED 3TBx8
SSD: 4 xSamsung 850 EVO Basic (500GB, 2.5″) — — VMs/Jails
HBA: LSI 9300-16i
OS: 1 x Kingston UV400 120GB SSD — boot drive
PSU: Corsair RM1000
Version: TrueNAS CORE 13.0 -U3.1
FANS: 3xFractal R3 120mm — 3 Front, 1 Rear. Corsair Commander Pro to control the fans (see script and code)
CPU FAN: 1xCorsair H60 CPU Radiator — Front
NIC: Intel EXPI9402PTBLK Pro, Dual-Gigabit Adapter (plus the 2 onboard Intel NICs, 1x 210, 1x 218)

VM/Docker host, using ESXi and running pfSense alongside FreeNAS (separate Dual Intel NIC added, dedicated to the pfSense VM)

TrueNAS CORE test system:

CASE: Old Silverstone HTPC case
MB: ASUS x-99M WS
CPU: Xeon E5-2620v4 + Corsair H60 Cooler block
RAM: CRUCIAL 32GB DDR4-2133 ECC RDIMMs
HDD: WD RED 8TBx3
OS: 1 x Kingston UV400 120GB SSD — boot drive
PSU: Corsair RM1000
Version: TrueNAS CORE 13.0-U3

2x Intel NUCs running TrueNAS SCALE 22.12 RC1
64GB RAM
10th Generation Intel i7
Samsung NVME SSD 1TB, QVO SSD 1TB
Boot from Samsung Portable T7 SSD USBC

CASE: Fractal Node 304 running TrueNAS SCALE 22.12 RC1
MB: ASUS P10S-I Series
RAM: 32 GB
CPU: Intel(R) Xeon(R) CPU E3-1240L v5 @ 2.10GHz
HDD: 3 WD REDs and a few SSDs
PSU: Fractal ION 2+ 650W

Источник

USB disks unusable (CCB request completed with an error)

askadar

I’m trying to set up two USB 3 disks on a fresh FreeBSD 11.0 install as a mirrored zpool. One disk is a 3TB Toshiba, the other is a 3TB Seagate. Both drives can be mounted ok, but after some minutes of operation I see the following errors.

Attachments

aragats

askadar

askadar

No luck. I kept the disks busy by writing /dev/urandom and /dev/zero to a file in a loop. After some time I start to see these errors again:

ralphbsz

5 minutes every hour, idle otherwise). The number of USB errors being logged was very high, occasionally the errors would fail in retry and percolate through the file system to my backup application (which would crash, but I know how to handle that automatically), and rarely all of FreeBSD would hang or crash (this was 9.0). Because this was too much work to deal with, I switched to an eSATA connection instead, and since the problem has been at a much lower level (a few dozen messages per day in the log, no crashes). I suspect that what you’re seeing is USB-3 hardware issues, which the USB layer in the kernel and ZFS handle by disconnecting and reporting errors.

I know it would be a lot of work, but can you perhaps create a low-level benchmark (such as reading the disk with a random read program, without going through the ZFS file system), and which is capable of demonstrating the problem? Then start switching out components one at a time. The first step would be to replace FreeBSD with Linux (just boot from a Knoppix CD), and run exactly the same benchmark. If the problem goes away, then you already know who the culprit is. If the problem stays, then start replacing USB ports (temporarily get a PCI-card based USB interface), or cables, or the disk enclosures, or temporarily replace all of USB with eSATA or SAS.

Reactions: Brandon D

askadar

Ok, thanks for the suggestions. The machine is a Zotac ZBOX nano, so there is not much in terms of hardware that I can change. I can try Linux, but since I don’t have an optical drive to boot from and no USB thumb drive on hand, it will take some time.

Currently I’m testing the Seagate on a Mac laptop (i.e., different host, different OS) with a simple write loop. So far zero issues.

aragats

askadar

Reactions: grahamperrin@

askadar

In case anyone cares, here is the final resolution.

Under FreeBSD, on the Zotac ZBOX nano:

• The Toshiba drive definitely has trouble with energy savings mode. Once it powers down (after five minutes of inactivity), FreeBSD cannot wake it anymore and will log errors until the kernel gives up and destroys the peripheral.
• The Seagate drive works ok for several hours, but will log a few errors sporadically, until it will be removed from the system for no obvious reason.

Under Mac OS X, on a 2016 MacBook and a 2012 iMac:

• Both drives work just fine.

Under Ubuntu Linux 16.04 LTS, on the Zotac ZBOX nano:

• Both drives work just fine, even when using ZFS.
• (As a side benefit, Linux also supports the Intel wifi NIC out of the box, which FreeBSD does not recognize.)

The Toshiba drive, in particular, wakes up without issues under Mac OS X and Linux (I tested this with 10-minute sleeps for

Conclusion: the hard drives are ok, the ZBOX’s USB controller is ok, but FreeBSD (as of version 11.0) unfortunately does not yet support this platform in a stable way. I’ll (have to) stick with Linux for now. Thanks for all your suggestions and feedback.

Reactions: grahamperrin@

stast

Hello !
I have the same problem with MicroSD-reader (USB stick).
But there are a lot of TODOs before to solve
1) use USB-ports from back of PC instead of front — thin cables inside PC couldn’t be enough for large power required for your device.
2) check the USB cable — some USB-cables have only power pins, but not DATA. Thick and short cables are preffered for conntection external HDD with PC.
3) check that device is usable — on another computer width different OS. But remember that another OS can’t read some filesystems and that’s not a problem.

Ok, here is my case.
MicroSD-reader (USB stick), correct work with FreeBSD 10.3 and 11.0, but can’t read card with 12-Current.
Messages from log:

Another USB-flash reads OK on this 12-Current. So it’s software problem in FreeBSD 12-Current.
It’s look like that device can’t reply to some commands from USB host.
Here is the way to solve these problems (from https://wiki.freebsd.org/USB).
# usbconfig
ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA)
ugen4.1: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
ugen3.1: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA)
ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA)
ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE (0mA)
ugen4.2: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (100mA)

# usbconfig -u 4 -a 2 dump_device_desc
ugen4.2: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (100mA)

bLength = 0x0012
bDescriptorType = 0x0001
bcdUSB = 0x0200
bDeviceClass = 0x0000

bDeviceSubClass = 0x0000
bDeviceProtocol = 0x0000
bMaxPacketSize0 = 0x0040
idVendor = 0xaaaa
idProduct = 0x8816
bcdDevice = 0x1308
iManufacturer = 0x0001
iProduct = 0x0002
iSerialNumber = 0x0003
bNumConfigurations = 0x0001

So we know vendor id (0xaaaa) and product id (0x8816) now.
Add these ID to /sys/dev/usb/usbdevs:

diff -u /sys/dev/usb/usbdevs.orig /sys/dev/usb/usbdevs
— /sys/dev/usb/usbdevs.orig 2017-08-08 18:05:32.425254000 +0700
+++ /sys/dev/usb/usbdevs 2017-11-03 20:59:59.803530000 +0700
@@ -780,6 +780,7 @@
vendor MOSCHIP 0x9710 MosChip Semiconductor
vendor NETGEAR4 0x9846 Netgear
vendor MARVELL 0x9e88 Marvell Technology Group Ltd.
+vendor MXTRON 0xaaaa MXTronics
vendor 3COM3 0xa727 3Com
vendor CACE 0xcace CACE Technologies
vendor EVOLUTION 0xdeee Evolution Robotics products
@@ -2800,6 +2801,9 @@
/* Marvell Technology Group, Ltd. products */
product MARVELL SHEEVAPLUG 0x9e8f SheevaPlug serial interface
+/* Marvell Technology Group, Ltd. products */
+product MXTRON MXTRONUSB 0x8816 MXTronics MXT USB Device
+
/* Matrix Orbital products */
product MATRIXORBITAL FTDI_RANGE_0100 0x0100 FTDI compatible adapter
product MATRIXORBITAL FTDI_RANGE_0101 0x0101 FTDI compatible adapter

and some quirks for this device to /sys/dev/usb/quirk/usb_quirk.c:

— /sys/dev/usb/quirk/usb_quirk.c.orig 2017-08-08 18:04:36.692641000 +0700
+++ /sys/dev/usb/quirk/usb_quirk.c 2017-11-03 21:06:27.960989000 +0700
@@ -530,6 +530,7 @@
USB_QUIRK(FEIYA, DUMMY, 0x0000, 0xffff, UQ_MSC_NO_SYNC_CACHE, UQ_MATCH_VENDOR_ONLY),
USB_QUIRK(REALTEK, DUMMY, 0x0000, 0xffff, UQ_MSC_NO_SYNC_CACHE, UQ_MATCH_VENDOR_ONLY),
USB_QUIRK(INITIO, DUMMY, 0x0000, 0xffff, UQ_MSC_NO_SYNC_CACHE, UQ_MATCH_VENDOR_ONLY),
+ USB_QUIRK(MXTRON, MXTRONUSB, 0x0000, 0xffff, UQ_MSC_NO_SYNC_CACHE, UQ_MSC_NO_TEST_UNIT_READY, UQ_MATCH_VENDOR_ONLY),
/* DYMO LabelManager Pnp */
USB_QUIRK(DYMO, LABELMANAGERPNP, 0x0000, 0xffff, UQ_MSC_DYMO_EJECT),

Recompile and reinstall kernel (and reboot, surely), and your device are visible know without CCB errors.

You can do fdisk/newfs_msdos/etc with block device /dev/da0 now.

Источник

Hi. Yesterday I got this message on my freenas: https://imgur.com/a/dYpc2Ja And the nas was ekstreme slow, the Web GUI was slow, but worked a little until it did not respond anymore. Same with the SMB shares. So. I tried to reboot the server from the console, it did not make it because of a process that the reboot command was not able to kill, so i did it the hard way (power button).

Anyway, system up, all things look good. Running for about 12h now, with little use.

Also, this might be relevant:

CRITICAL: Aug. 11, 2018, 7:01 a.m. - The boot volume state is ONLINE: One or more devices are faulted in response to IO failures. WARNING: Aug. 6, 2018, 8:02 p.m. - smartd_daemon is not running. CRITICAL: Aug. 6, 2018, 8:02 p.m. - The capacity for the volume 'volum1' is currently at 90%, while the recommended value is below 80%.

But I have deleted some data of volume1 now:

WARNING: Aug. 11, 2018, 3:31 p.m. - smartd_daemon is not running. WARNING: Aug. 11, 2018, 3:46 p.m. - The capacity for the volume 'volum1' is currently at 88%, while the recommended value is below 80%.

My config:

FreeNAS-11.1-U5

1x4TB drive, 1x1TB drive, one volume on each drive, no raid. ZFS.

SanDisc Cruzer Blade 1.00 16GB boot drive

SuperMicro X9SCM-F

Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz

16GB ECC memory

I can se I have the same MB, almost same boot stick, and same errors as this guy: https://forums.freenas.org/index.php?threads/mystery-cam-status-ccb-request-completed-with-an-error-on-new-build-disappearing-after-testing.49756/

Can it be a defective USB drive?

Нигде не найду на форумах решения проблемы, поэтому создаю новую.

При подключении флешки не появляются устройства da0*, sda0* в папке /dev

В логе:

ugen1.2: <General> at usbus1

umass0: <General USB Flash Disk, class 0/0, rev 2.00/1.00, addr 1> on usbus1

umass0: SCSI over Bulk-Only; quirks = 0x0100

umass0:5:0:-1: Attached to scbus5

(probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0

(probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error

(probe0:umass-sim0:0:0:0): Retrying command

(probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0

(probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error

(probe0:umass-sim0:0:0:0): Retrying command

(probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0

(probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error

(probe0:umass-sim0:0:0:0): Retrying command

(probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0

(probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error

(probe0:umass-sim0:0:0:0): Retrying command

(probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 0 0 0 24 0

(probe0:umass-sim0:0:0:0): CAM status: CCB request completed with an error

(probe0:umass-sim0:0:0:0): Error 5, Retries exhausted

linux: pid 1844 (npviewer.bin): syscall pipe2 not implemented

root@freebsd:/usr # uname -a

FreeBSD freebsd 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012

root@farrell.cse.buffalo.edu

:/usr/obj/usr/src/sys/GENERIC amd64

На мамке usb 3.0. При попытке отключения в биосе dmesg вообще перестает что-либо выдавать при подключении флешки.

Помогите решить проблему, если можно поконкретнее, что делать. В freebsd еще не силен. Заранее спасибо.

FreeNAS server was randomly crashing:

(da0:umass-sim0:0:0:0): Retrying command
(da0:umass-sim0:0:0:0): WRITE(10). CDB: 2a 00 00 24 26 9d 00 00 10 00
(da0:umass-sim0:0:0:0): CAM status: CCB request completed with an error
(da0:umass-sim0:0:0:0): Error 5, Retries exhausted
root@freenas:/mnt/data #

The USB drive is causing this.

root@wine:~ # usbconfig
ugen0.1: <Intel EHCI root HUB> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
ugen1.1: <Intel EHCI root HUB> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
ugen1.2: <vendor 0x8087 product 0x0024> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
ugen0.2: <vendor 0x8087 product 0x0024> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
ugen0.3: <SanDisk Cruzer Blade> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (224mA)

root@wine:~ # usbconfig -u 0 -a 3 dump_device_desc
ugen0.3: <SanDisk Cruzer Blade> at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (224mA)

  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0210
  bDeviceClass = 0x0000  <Probed by interface class>
  bDeviceSubClass = 0x0000
  bDeviceProtocol = 0x0000
  bMaxPacketSize0 = 0x0040
  idVendor = 0x0781
  idProduct = 0x5567
  bcdDevice = 0x0100
  iManufacturer = 0x0001  <SanDisk>
  iProduct = 0x0002  <Cruzer Blade>
  iSerialNumber = 0x0003  <4C531001561109121142>
  bNumConfigurations = 0x0001

Switched to a different USB stick and the problem went away.

Lesson: Not all USB sticks are created equally.

Всем доброго времени!

Бьюсь с той же траблой. Сначала пробовал применить решение из 1-го поста, не получается:

mountroot> cd9660:/dev/cd0
Trying to mount root from cd9660:/dev/cd0 []...
g_vfs_done():cd0[READ(offset=32768, length=2048)]error = 6
Mounting from cd9660:/dev/cd0 failed with error 6.

Потом попробовал с конфигом загрузки. Жму ESC, когда появляется рожица дьяволенка, печатаю

начинается загрузка, опять та же самая 19-ая ошибка, но в конце еще такой аут:

mountroot> (probe:umass-sim0:0:0:0): INQUIRY. CDB: 12 0 0 1 0 0
(probe:umass-sim0:0:0:0): CAM status: CCB request completed with an error
(probe:umass-sim0:0:0:0): Retrying command

Установку произвожу с iLO, образ записан на диск. В принципе, могу попробовать непосредственно на серваке (имеется USB-привод), но думаю, ничего не измениться, т.к. через физический привод ставил версию 9.0 — ошибки были все те же (тогда я забил и поставил 8.3).
Есть предположение, что у фряхи, начиная с версий 9.0, непростые отношения с рейдами (на этом серваке RAID1 4 штуки), но как с этим жить — инфы не нарыл.

Что можно сделать?
Заранее спасибо за помощь.