[SOLVED] Error on TrueNAS vm after upgrade Proxmox from 7 to 8

[Tidbit8591]

Hi all,
I'm facing an error that don't allow me to access to TrueNAS VM. Prior to the upgrade I had this configuration:

• Single node with Proxmox 7
• Different VM for labs
• TrueNAS with an USB as primary disk for storage.

if I list the current USB devices I can see

root@proxmox:~# lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 003 Device 003: ID 0d8c:0014 C-Media Electronics, Inc. Audio Adapter (Unitek Y-247A)
Bus 003 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 152d:0567 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The USB device that is used by TrueNAS is the device with ID 152d:0567

As you can see below the USB is properly attached to the VM

root@proxmox:~# qm config 101
boot: order=scsi0
cores: 1
memory: 16384
meta: creation-qemu=6.1.0,ctime=1647853695
name: truenas
net0: rtl8139=BA:C4:E8:98:41:25,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: l26
scsi0: main-lvm:101/vm-101-disk-0.qcow2,size=32G
smbios1: uuid=ded32162-c111-4070-9d9e-d4828c1dd23c
sockets: 1
startup: order=3
tablet: 0
usb0: host=152d:0567
vmgenid: fe8f7e1b-9c18-426c-841e-7566c7b8aeb0

Now, if I try to boot the VM I recevied the following error:


The other VMs work properly, this is the only one that has this kind of error.

What can I do to recover the NAS?

 

[Pifouney]

in your usb material line, uncheck (if checked ) usb3. Was a problem for me that have doesn't have time to solve that. If this solve your problem, maybe try to updgrade your BIOS, then retry with checked usb3

 

[Tidbit8591]

in your usb material line, uncheck (if checked ) usb3. Was a problem for me that have doesn't have time to solve that. If this solve your problem, maybe try to updgrade your BIOS, then retry with checked usb3

it is already unchecked. I had another problem regarding the upgrading of the kernel. I have found another post reagarding the USB problem https://forum.proxmox.com/threads/k...controller-passthrough-in-a-weird-way.152508/ but, for what I tried, it is not the same problem.

Below the log from dmesg after plug the USB cable

[157817.852676] usb 2-2: USB disconnect, device number 5
[157837.436620] usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd
[157837.449873] usb 4-1: New USB device found, idVendor=152d, idProduct=0567, bcdDevice= 3.23
[157837.449888] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[157837.449895] usb 4-1: Product: USB to ATA/ATAPI Bridge
[157837.449902] usb 4-1: Manufacturer: JMicron
[157837.449908] usb 4-1: SerialNumber: 0123456789ABCDEF
[157837.454119] scsi host2: uas
[157837.454950] scsi 2:0:0:0: Direct-Access     JMicron  Generic DISK00   0103 PQ: 0 ANSI: 6
[157837.457986] sd 2:0:0:0: Attached scsi generic sg2 type 0
[157837.478372] sd 2:0:0:0: [sdc] 3906928640 512-byte logical blocks: (2.00 TB/1.82 TiB)
[157837.478385] sd 2:0:0:0: [sdc] 4096-byte physical blocks
[157837.478680] sd 2:0:0:0: [sdc] Write Protect is off
[157837.478690] sd 2:0:0:0: [sdc] Mode Sense: 4b 00 00 00
[157837.479016] sd 2:0:0:0: [sdc] Disabling FUA
[157837.479024] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[157837.479032] sd 2:0:0:0: [sdc] Preferred minimum I/O size 512 bytes not a multiple of physical block size (4096 bytes)
[157837.479040] sd 2:0:0:0: [sdc] Optimal transfer size 33553920 bytes not a multiple of physical block size (4096 bytes)
[157837.513032]  sdc: sdc1 sdc2
[157837.513555] sd 2:0:0:0: [sdc] Attached SCSI disk
[157838.136502] sd 2:0:0:0: [sdc] Synchronizing SCSI cache
[157838.259564] sd 2:0:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[157842.411745] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd

I'm not able to understand this log

 

[Tidbit8591]

Ok, I tried into another machine where I installed TrueNAS and attached the USB disk. Everything works fine. It recognizes the USB device and it shows the pool. So it is a proxmox 8.2.7.
Could it be a usb lib for the updated kernel? I've found that I have to turn off the parameter intel_iommu in the boot (https://forum.proxmox.com/threads/where-to-add-intel_iommu-on-and-iommu-pt.131592/#post-578296) but nothing happens.

I would like to restore my NAS properly. What can I do?

 

[Pifouney]

can you try on another USB port ? maybe a default on the actual port (usb is aggressive, and using a disk like this can break a usb port)

 

[Tidbit8591]

I tried all the four ports. Nothing has changed. I thought it was a problem regarding the power but the USB storage has already power adapter. I unchecked the USB 3.0 flag. Nothing.

 

[Pifouney]

ok
Did you tried to see your USB pool directly from pve host ? If not, stop before action your nas VM.
If you cannot see the zpool, it's a usb disk hardware problem

 

[Tidbit8591]

This is the dmesg log after I stopped the VM with TrueNAS. The pve shows correctly the device and the storage. However I don't want to mount on pve instance since I'm not about what could happen.



It is not a USB disk hardware problem because I created on VMWare on another PC an instance of TrueNAS. I attached, via passthrough the USB device, I imported the current pool in the USB disk and TrueNAS showed me all the partitions and the shared folders. It seems a kernel usb driver with Proxmox 8.7. I always had the version 7.2 and last week I decided to upgrade to version 8.7. I lost a VM (no problem, it was a testing environment) and now I'm facing this error with TrueNAS.

 

[Tidbit8591]

It seems Proxmox 8.7 doesn't passthrough USB to FreeBSD systems. I switched to another version of TrueNAS (SCALE in this scale, based on Linux) and now I can access to the storage.