[SOLVED] FreeNAS HBA passthrough working but...

P

Phuket My Mac

Member
Aug 4, 2019
12
1
8
44
Hello,

I have an HP Proliant ML350p Gen8 with an HP 220 HBA card (in IT mode bought from eBay) that I was apparently able to pass-through to the VM.
I did follow the Proxmox guide on how to pass-through a PCIE device to my FreeNAS VM and had to do some more work since HPE doesn't make your life easy as usual (as can be seen on this HPE note: https://support.hpe.com/hpsc/doc/public/display?docId=emr_na-c04781229)

Anyway, I got FreeNAS to boot and could see the card + drives so I thaught I was good.
But when it was time to create the RaidZ pool, I got an error with the dd command trying to clear the first 32k of the disk.
So trying to dd command manually, I am getting this:

root@freenas[~]# fdisk /dev/da0
fdisk: could not detect sector size

I have never tried to the card yet in a baremetal installation so I am kind of unsure still if it's a Proxmox setup issue or a card issue.
What else can I do on the Proxmox side to rule that out please?
 
Hardware passthrough is always tricky if the hardware does not play nice. I have no idea what you can try next, but I want to know if you need this? Why don't you use the pcie card in PVE directly with the built in ZFS?
 
Because FreeNAS is maintained nicely like a Linux distro would and so is reliable during OS and package upgrades.
I understand I can create a linux container using SMB but I am not an advanced user enough in my opinion to be able to maintain a file Server that will serve both Mac and Windows clients.

I'll try to access the disks through the PVE system and see how it works.
I will also try to passthrough my NMVE PCIE drive and see how it works.
 
So after exporting that same card under Debian 10, I am getting a similar issue.
Here are some logs from dmesg:

[ 1.552958] mpt2sas_cm0: Allocated physical memory: size(5502 kB)
[ 1.552961] mpt2sas_cm0: Current Controller Queue Depth(10104),Max Controller Queue Depth(10240)
[ 1.552961] mpt2sas_cm0: Scatter Gather Elements per IO(128)
[ 1.601128] mpt2sas_cm0: LSISAS2308: FWVersion(20.00.07.00), ChipRevision(0x05), BiosVersion(07.39.02.00)
[ 1.601129] mpt2sas_cm0: Protocol=(
[ 1.601130] Initiator
[ 1.601130] ,Target
[ 1.601131] ),
[ 1.601131] Capabilities=(
[ 1.601131] TLR
[ 1.601132] ,EEDP
[ 1.601132] ,Snapshot Buffer
[ 1.601132] ,Diag Trace Buffer
[ 1.601133] ,Task Set Full
[ 1.601133] ,NCQ
[ 1.601133] )
[ 1.601236] scsi host0: Fusion MPT SAS Host
[ 1.650048] mpt2sas_cm0: sending port enable !!
[ 1.653042] random: fast init done
[ 1.654714] mpt2sas_cm0: host_add: handle(0x0001), sas_addr(0x500605b005842a60), phys(8)
[ 1.668950] mpt2sas_cm0: port enable: SUCCESS
[ 1.671318] scsi 0:0:0:0: Direct-Access HITACHI HUC109060CSS600 A720 PQ: 0 ANSI: 6
[ 1.671322] scsi 0:0:0:0: SSP: handle(0x0009), sas_addr(0x5000cca070903559), phy(0), device_name(0x5000cca07090355b)
[ 1.671330] scsi 0:0:0:0: enclosure logical id (0x500605b005842a60), slot(3)
[ 1.675301] scsi 0:0:1:0: Direct-Access HITACHI HUC109060CSS600 A720 PQ: 0 ANSI: 6
[ 1.675304] scsi 0:0:1:0: SSP: handle(0x000a), sas_addr(0x5000cca07089fd19), phy(1), device_name(0x5000cca07089fd1b)
[ 1.675305] scsi 0:0:1:0: enclosure logical id (0x500605b005842a60), slot(2)
[ 1.679295] scsi 0:0:2:0: Direct-Access HITACHI HUC109060CSS600 A720 PQ: 0 ANSI: 6
[ 1.679299] scsi 0:0:2:0: SSP: handle(0x000b), sas_addr(0x5000cca07087a249), phy(2), device_name(0x5000cca07087a24b)
[ 1.679300] scsi 0:0:2:0: enclosure logical id (0x500605b005842a60), slot(1)
[ 1.685119] scsi 0:0:3:0: Direct-Access HITACHI HUC109060CSS600 A720 PQ: 0 ANSI: 6
[ 1.685123] scsi 0:0:3:0: SSP: handle(0x000c), sas_addr(0x5000cca07089ff8d), phy(3), device_name(0x5000cca07089ff8f)
[ 1.685124] scsi 0:0:3:0: enclosure logical id (0x500605b005842a60), slot(0)
[ 1.688523] scsi 0:0:4:0: Direct-Access HITACHI HUC109060CSS600 A720 PQ: 0 ANSI: 6
[ 1.688526] scsi 0:0:4:0: SSP: handle(0x000d), sas_addr(0x5000cca07087ac55), phy(4), device_name(0x5000cca07087ac57)
[ 1.688527] scsi 0:0:4:0: enclosure logical id (0x500605b005842a60), slot(7)
[ 1.695817] scsi 0:0:5:0: Direct-Access HITACHI HUC109060CSS600 A720 PQ: 0 ANSI: 6
[ 1.695820] scsi 0:0:5:0: SSP: handle(0x000e), sas_addr(0x5000cca0708a0079), phy(5), device_name(0x5000cca0708a007b)
[ 1.695821] scsi 0:0:5:0: enclosure logical id (0x500605b005842a60), slot(6)
[ 1.699863] scsi 0:0:6:0: Direct-Access HITACHI HUC109060CSS600 A720 PQ: 0 ANSI: 6
[ 1.699866] scsi 0:0:6:0: SSP: handle(0x000f), sas_addr(0x5000cca0708a0a99), phy(6), device_name(0x5000cca0708a0a9b)
[ 1.699867] scsi 0:0:6:0: enclosure logical id (0x500605b005842a60), slot(5)
[ 1.704782] scsi 0:0:7:0: Direct-Access HITACHI HUC109060CSS600 A720 PQ: 0 ANSI: 6
[ 1.704785] scsi 0:0:7:0: SSP: handle(0x0010), sas_addr(0x5000cca0709008bd), phy(7), device_name(0x5000cca0709008bf)
[ 1.704786] scsi 0:0:7:0: enclosure logical id (0x500605b005842a60), slot(4)
[ 1.711407] sd 0:0:0:0: [sdb] Unsupported sector size 520.
[ 1.712094] sd 0:0:0:0: [sdb] 0 512-byte logical blocks: (0 B/0 B)
[ 1.712095] sd 0:0:0:0: [sdb] 520-byte physical blocks
[ 1.712531] sd 0:0:0:0: [sdb] Write Protect is off
[ 1.712533] sd 0:0:0:0: [sdb] Mode Sense: f7 00 10 08
[ 1.712611] sd 0:0:1:0: [sdc] Unsupported sector size 520.
[ 1.712953] sd 0:0:1:0: [sdc] 0 512-byte logical blocks: (0 B/0 B)
[ 1.712954] sd 0:0:1:0: [sdc] 520-byte physical blocks
[ 1.713133] sd 0:0:0:0: [sdb] Write cache: disabled, read cache: enabled, supports DPO and FUA
[ 1.713214] sd 0:0:1:0: [sdc] Write Protect is off
[ 1.713216] sd 0:0:1:0: [sdc] Mode Sense: f7 00 10 08
[ 1.713543] sd 0:0:2:0: [sdd] Unsupported sector size 520.
[ 1.713588] sd 0:0:1:0: [sdc] Write cache: disabled, read cache: enabled, supports DPO and FUA
[ 1.713785] sd 0:0:3:0: [sde] Unsupported sector size 520.
[ 1.713819] sd 0:0:4:0: [sdf] Unsupported sector size 520.
[ 1.713893] sd 0:0:2:0: [sdd] 0 512-byte logical blocks: (0 B/0 B)
[ 1.713894] sd 0:0:2:0: [sdd] 520-byte physical blocks
[ 1.713902] sd 0:0:5:0: [sdg] Unsupported sector size 520.
[ 1.714038] sd 0:0:6:0: [sdh] Unsupported sector size 520.
[ 1.714159] sd 0:0:3:0: [sde] 0 512-byte logical blocks: (0 B/0 B)
[ 1.714160] sd 0:0:3:0: [sde] 520-byte physical blocks
[ 1.714167] sd 0:0:2:0: [sdd] Write Protect is off
[ 1.714168] sd 0:0:2:0: [sdd] Mode Sense: f7 00 10 08
[ 1.714169] sd 0:0:4:0: [sdf] 0 512-byte logical blocks: (0 B/0 B)
[ 1.714170] sd 0:0:4:0: [sdf] 520-byte physical blocks
[ 1.714176] sd 0:0:7:0: [sdi] Unsupported sector size 520.
[ 1.714269] sd 0:0:5:0: [sdg] 0 512-byte logical blocks: (0 B/0 B)
[ 1.714270] sd 0:0:5:0: [sdg] 520-byte physical blocks
[ 1.714371] sd 0:0:6:0: [sdh] 0 512-byte logical blocks: (0 B/0 B)
[ 1.714372] sd 0:0:6:0: [sdh] 520-byte physical blocks
[ 1.714421] sd 0:0:3:0: [sde] Write Protect is off
[ 1.714422] sd 0:0:3:0: [sde] Mode Sense: f7 00 10 08
[ 1.714440] sd 0:0:4:0: [sdf] Write Protect is off
[ 1.714441] sd 0:0:4:0: [sdf] Mode Sense: f7 00 10 08
[ 1.714490] sd 0:0:7:0: [sdi] 0 512-byte logical blocks: (0 B/0 B)
[ 1.714490] sd 0:0:7:0: [sdi] 520-byte physical blocks
[ 1.714511] sd 0:0:2:0: [sdd] Write cache: disabled, read cache: enabled, supports DPO and FUA
[ 1.714530] sd 0:0:5:0: [sdg] Write Protect is off
[ 1.714531] sd 0:0:5:0: [sdg] Mode Sense: f7 00 10 08
[ 1.714615] sd 0:0:6:0: [sdh] Write Protect is off
[ 1.714616] sd 0:0:6:0: [sdh] Mode Sense: f7 00 10 08
[ 1.714780] sd 0:0:3:0: [sde] Write cache: disabled, read cache: enabled, supports DPO and FUA
[ 1.714797] sd 0:0:4:0: [sdf] Write cache: disabled, read cache: enabled, supports DPO and FUA
[ 1.714807] sd 0:0:7:0: [sdi] Write Protect is off
[ 1.714808] sd 0:0:7:0: [sdi] Mode Sense: f7 00 10 08
[ 1.714954] sd 0:0:5:0: [sdg] Write cache: disabled, read cache: enabled, supports DPO and FUA
[ 1.714997] sd 0:0:6:0: [sdh] Write cache: disabled, read cache: enabled, supports DPO and FUA
[ 1.715222] sd 0:0:7:0: [sdi] Write cache: disabled, read cache: enabled, supports DPO and FUA
[ 1.716692] sd 0:0:0:0: [sdb] Unsupported sector size 520.
[ 1.716970] sd 0:0:1:0: [sdc] Unsupported sector size 520.
[ 1.717645] sd 0:0:2:0: [sdd] Unsupported sector size 520.
[ 1.717928] sd 0:0:3:0: [sde] Unsupported sector size 520.
[ 1.718364] sd 0:0:7:0: [sdi] Unsupported sector size 520.
[ 1.718509] sd 0:0:5:0: [sdg] Unsupported sector size 520.
[ 1.718654] sd 0:0:6:0: [sdh] Unsupported sector size 520.
[ 1.719389] sd 0:0:4:0: [sdf] Unsupported sector size 520.
[ 1.720622] sd 0:0:0:0: [sdb] Attached SCSI disk
[ 1.720918] sd 0:0:1:0: [sdc] Attached SCSI disk
[ 1.721153] sd 0:0:2:0: [sdd] Attached SCSI disk
[ 1.721393] sd 0:0:3:0: [sde] Attached SCSI disk
[ 1.721808] sd 0:0:7:0: [sdi] Attached SCSI disk
[ 1.722472] sd 0:0:5:0: [sdg] Attached SCSI disk
[ 1.722597] sd 0:0:6:0: [sdh] Attached SCSI disk
[ 1.723182] sd 0:0:4:0: [sdf] Attached SCSI disk
[ 6.128198] sd 1:0:0:0: Attached scsi generic sg0 type 0
[ 6.128935] sr 2:0:0:0: Attached scsi generic sg1 type 5
[ 6.128973] sd 0:0:0:0: Attached scsi generic sg2 type 0
[ 6.129000] sd 0:0:1:0: Attached scsi generic sg3 type 0
[ 6.129027] sd 0:0:2:0: Attached scsi generic sg4 type 0
[ 6.129052] sd 0:0:3:0: Attached scsi generic sg5 type 0
[ 6.129079] sd 0:0:4:0: Attached scsi generic sg6 type 0
[ 6.129104] sd 0:0:5:0: Attached scsi generic sg7 type 0
[ 6.129130] sd 0:0:6:0: Attached scsi generic sg8 type 0
[ 6.129155] sd 0:0:7:0: Attached scsi generic sg9 type 0
[ 2834.002656] sd 0:0:0:0: [sdb] Unsupported sector size 520.
[ 2836.785096] sd 0:0:1:0: [sdc] Unsupported sector size 520.
[ 2838.602652] sd 0:0:3:0: [sde] Unsupported sector size 520.
[ 2840.039604] sd 0:0:4:0: [sdf] Unsupported sector size 520.

The last 4 errors show up in dmesg when trying to fdisk those devices.
 
Well, accessing the card under proxmox directly result in the same behavior.
So either it's a card issue or a backplane issue I guess.

I would have to try with a different OS as well just in case but it doesn't seem to be related to Proxmox.
 
Great find! Thanks!

I didn't even tried to look those messages up as I was sure it was just the controller not being able to talk with the drives.
"noob" attitude here ;-)

I'll try again once formatted (which is going to take hours) and hopefully have success to use the HBA card passed through to the FreeNAS VM.

Thanks again for your time.
 
Glad it helped!
Please post if the conversion was successful - it would help others in a similar situation!
 
Glad it worked - please mark the thread as 'SOLVED'
Thanks!
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom