[SOLVED] rpool, 2xSSD, RAID-1, USB UNITEK Y-3027 problem

M

mpobieda

Member
Aug 3, 2022
17
0
6
Hi
There is a problem with TRIM on the UNITEK Y-3027.
https://www.unitek-products.com/pro...-dual-bay-station-with-offline-clone-function
The disks are working fairly efficiently, but I am having trouble executing the TRIM command.

-------------------------------------------------------------

On the SSD connected to the Y-3027, the command returns an error:
root@pve:~# zpool trim rpool
cannot trim: no devices in pool support trim operations

--------------------------------------------------------------

On the SSD connected to the motherboard, the command runs correctly:
root@pve:~# zpool trim rpool

Aug 03 02:12:30 pve zed [2790]: eid=7 class=trim_start pool='rpool' vdev=ata-TEAM_T253X6001T_TPBF2110150060100657-part3 vdev_state=ONLINE
Aug 03 02:12:30 pve zed [2787]: eid=6 class=trim_start pool='rpool' vdev=ata-TEAM_T253X6001T_TPBF2110150060100054-part3 vdev_state=ONLINE
Aug 03 02:12:34 pve zed [9306]: eid=10 class=trim_finish pool='rpool' vdev=ata-TEAM_T253X6001T_TPBF2110150060100054-part3 vdev_state=ONLINE
Aug 03 02:12:34 pve zed [9344]: eid=12 class=trim_finish pool='rpool' vdev=ata-TEAM_T253X6001T_TPBF2110150060100657-part3 vdev_state=ONLINE

-------------------------------------------------------------

You can do something?
Thank you in advance.
 
mpobieda said:
You can do something?
Click to expand...

If the controller (in the docking station) does not (properly) support trim, no.

You could contact the manufacturer. Maybe they can do something with an firmware update. But support regarding such things is often bad.

Anyway not really an Proxmox-related topic.
 
First, I wrote to the producer.
He boasted that he supports TRIM.
I did tests and it turns out that TRIM does not support.
I am in contact with the producer.
I asked on the proxmox forum, because maybe one of you has already dealt with this problem.
 
mpobieda said:
I asked on the proxmox forum, because maybe one of you has already dealt with this problem.
Click to expand...
Not on that problem but I can say that I tried USB zpools over USB 3.1 and 3.2 and it was not fast due to a variable latency that yields in sluggishness. I did not try TRIM.
 
Response from the manufacturer Y-3027:
We are afraid it is because Proxmox Virtual Environment do not support to perform TRIM after drive station transferring.
The manufacturer's support has performed the TRIM handling tests, I am attaching a photo.

LnxBil: I tested on USB 3.1 ports and pendrives, but the transfers were very small, around 60MB/s.

On the Y-3027 docking station, even with Barracuda HDDs, transfers are very good, around 110MB/s. I wanted to use the docking station only for the Proxmox system, and virtual machines on SSDs in RAID-1 on SATA controllers of the motherboard.
 

Attachments

  • Bez tytułu.jpg
    Bez tytułu.jpg
    254.2 KB · Views: 10
Last edited:
mpobieda said:
60Mbps.
Click to expand...
Do you men Mbps or MB/s (difference is factor 8)?

mpobieda said:
The manufacturer's support has performed the TRIM handling tests, I am attaching a photo
Click to expand...
They should you the default windows trimming with PowerShell in order see if it works. I can also write a program that states that it works. We need independend data:

Code: 
Optimize-Volume -DriveLetter E -ReTrim -Verbose
 
Okay, thank you. The MB/s is not a good indicator for latency, therefore we use IOPS for those things. But 60 MB/s for an SSD is not very much.
 
These drives with 60MB/s are ordinary flash drives USB-A 3.0. It was just an experimental test.
Of course, it uses 500MB/s SSD disks.
 
Do you have an idea how to solve this problem?
/dev/sda - SSD 1T teamgroup CX2 (plugged into SATA on the motherboard)
/dev/sdb - SSD 1T teamgroup CX2 (connected to USB 3.0, UNITEK Y-3027)

==========================================================================
root@pve:/dev/disk/by-path# ls -l /dev/disk/by-path/
total 0
lrwxrwxrwx 1 root root 9 Aug 4 03:42 pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:0 -> ../../sdb
lrwxrwxrwx 1 root root 10 Aug 4 03:42 pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:0-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Aug 4 03:42 pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:0-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 10 Aug 4 03:42 pci-0000:00:14.0-usb-0:1:1.0-scsi-0:0:0:0-part3 -> ../../sdb3
lrwxrwxrwx 1 root root 9 Aug 4 03:02 pci-0000:00:17.0-ata-3 -> ../../sda
lrwxrwxrwx 1 root root 9 Aug 4 03:02 pci-0000:00:17.0-ata-3.0 -> ../../sda
lrwxrwxrwx 1 root root 10 Aug 4 03:02 pci-0000:00:17.0-ata-3.0-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Aug 4 03:02 pci-0000:00:17.0-ata-3.0-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Aug 4 03:02 pci-0000:00:17.0-ata-3.0-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Aug 4 03:02 pci-0000:00:17.0-ata-3-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Aug 4 03:02 pci-0000:00:17.0-ata-3-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Aug 4 03:02 pci-0000:00:17.0-ata-3-part3 -> ../../sda3
root@pve:/dev/disk/by-path#

===========================================================================

root@pve:~# find /sys/ -name provisioning_mode -exec grep -H . {} + | sort
/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1/2-1:1.0/host4/target4:0:0/4:0:0:0/scsi_disk/4:0:0:0/provisioning_mode:full
/sys/devices/pci0000:00/0000:00:17.0/ata3/host2/target2:0:0/2:0:0:0/scsi_disk/2:0:0:0/provisioning_mode:writesame_16
root@pve:~#

===========================================================================

root@pve:~# sg_vpd -a /dev/sdb
Supported VPD pages VPD page:
Supported VPD pages [sv]
Unit serial number [sn]
Device identification [di]
Block limits (SBC) [bl]

Unit serial number VPD page:
Unit serial number: 00000000000000000000

Device Identification VPD page:
Addressed logical unit:
designator type: NAA, code set: Binary
0x5000000000000001

Block limits VPD page (SBC):
Write same non-zero (WSNZ): 0
Maximum compare and write length: 0 blocks [Command not implemented]
Optimal transfer length granularity: 1 blocks
Maximum transfer length: 65535 blocks
Optimal transfer length: 65535 blocks
Maximum prefetch transfer length: 65535 blocks
Maximum unmap LBA count: 0 [Unmap command not implemented]
Maximum unmap block descriptor count: 0 [Unmap command not implemented]
Optimal unmap granularity: 0 blocks [not reported]
Unmap granularity alignment valid: false
Unmap granularity alignment: 0 [invalid]
Maximum write same length: 0 blocks [not reported]
Maximum atomic transfer length: 0 blocks [not reported]
Atomic alignment: 0 [unaligned atomic writes permitted]
Atomic transfer length granularity: 0 [no granularity requirement
Maximum atomic transfer length with atomic boundary: 0 blocks [not reported]
Maximum atomic boundary size: 0 blocks [can only write atomic 1 block]
root@pve:~#
root@pve:~#
root@pve:~#
root@pve:~# sg_vpd -a /dev/sda
Supported VPD pages VPD page:
Supported VPD pages [sv]
Unit serial number [sn]
Device identification [di]
ATA information (SAT) [ai]
Block limits (SBC) [bl]
Block device characteristics (SBC) [bdc]
Logical block provisioning (SBC) [lbpv]

Unit serial number VPD page:
Unit serial number: TPBF2110150060100054

Device Identification VPD page:
Addressed logical unit:
designator type: vendor specific [0x0], code set: ASCII
vendor specific: TPBF2110150060100054
designator type: T10 vendor identification, code set: ASCII
vendor id: ATA
vendor specific: TEAM T253X6001T TPBF2110150060100054
designator type: NAA, code set: Binary
<< unexpected NAA [0x0] >>
00 00 00 00 00 00 00 00

ATA information VPD page:
SAT Vendor identification: linux
SAT Product identification: libata
SAT Product revision level: 3.00
Device signature indicates SATA transport
Command code: 0xec
ATA command IDENTIFY DEVICE response summary:
model: TEAM T253X6001T
serial number: TPBF2110150060100054
firmware revision: SBFMJ1.3

Block limits VPD page (SBC):
Write same non-zero (WSNZ): 0
Maximum compare and write length: 0 blocks [Command not implemented]
Optimal transfer length granularity: 1 blocks
Maximum transfer length: 0 blocks [not reported]
Optimal transfer length: 0 blocks [not reported]
Maximum prefetch transfer length: 0 blocks [ignored]
Maximum unmap LBA count: 0 [Unmap command not implemented]
Maximum unmap block descriptor count: 0 [Unmap command not implemented]
Optimal unmap granularity: 1 blocks
Unmap granularity alignment valid: false
Unmap granularity alignment: 0 [invalid]
Maximum write same length: 0x3fffc0 blocks
Maximum atomic transfer length: 0 blocks [not reported]
Atomic alignment: 0 [unaligned atomic writes permitted]
Atomic transfer length granularity: 0 [no granularity requirement
Maximum atomic transfer length with atomic boundary: 0 blocks [not reported]
Maximum atomic boundary size: 0 blocks [can only write atomic 1 block]

Block device characteristics VPD page (SBC):
Non-rotating medium (e.g. solid state)
Product type: Not specified
WABEREQ=0
WACEREQ=0
Nominal form factor: 2.5 inch
MACT=0
ZONED=0
RBWZ=0
BOCS=0
FUAB=0
VBULS=0
DEPOPULATION_TIME=0 (seconds)

Logical block provisioning VPD page (SBC):
Unmap command supported (LBPU): 0
Write same (16) with unmap bit supported (LBPWS): 1
Write same (10) with unmap bit supported (LBPWS10): 0
Logical block provisioning read zeros (LBPRZ): 0
Anchored LBAs supported (ANC_SUP): 0
Threshold exponent: 0 [threshold sets not supported]
Descriptor present (DP): 0
Minimum percentage: 0 [not reported]
Provisioning type: 0 (not known or fully provisioned)
Threshold percentage: 0 [percentages not supported]
root@pve:~#
 
Problem solved !!!
I changed UNITEK Y-3027 to UNITEK Y-3026.
UNITEK Y-3026 supports scsi (UASP) interface.
Thanks for your interest, gentlemen.

root@pve:~# zpool status -vt rpool
pool: rpool
state: ONLINE
scan: resilvered 6.45G in 00:01:25 with 0 errors on Thu Aug 4 13:22:50 2022
remove: Removal of vdev 4 copied 168M in 0h0m, completed on Sun Jul 31 19:50:30 2022
27.2K memory used for removed device mappings
config:

NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
ata-TEAM_T253X6001T_TPBF2110150060100054-part3 ONLINE 0 0 0 (100% trimmed, completed at Thu 04 Aug 2022 01:18:51 PM CEST)
ata-TEAM_T253X6001T_TPBF2110150060100657-part3 ONLINE 0 0 0 (untrimmed)

errors: No known data errors
root@pve:~# zpool trim rpool
root@pve:~# zpool status -vt rpool
pool: rpool
state: ONLINE
scan: resilvered 6.45G in 00:01:25 with 0 errors on Thu Aug 4 13:22:50 2022
remove: Removal of vdev 4 copied 168M in 0h0m, completed on Sun Jul 31 19:50:30 2022
27.2K memory used for removed device mappings
config:

NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
ata-TEAM_T253X6001T_TPBF2110150060100054-part3 ONLINE 0 0 0 (10% trimmed, started at Thu 04 Aug 2022 01:23:18 PM CEST)
ata-TEAM_T253X6001T_TPBF2110150060100657-part3 ONLINE 0 0 0 (9% trimmed, started at Thu 04 Aug 2022 01:23:18 PM CEST)

errors: No known data errors
root@pve:~# zpool status -vt rpool
pool: rpool
state: ONLINE
scan: resilvered 6.45G in 00:01:25 with 0 errors on Thu Aug 4 13:22:50 2022
remove: Removal of vdev 4 copied 168M in 0h0m, completed on Sun Jul 31 19:50:30 2022
27.2K memory used for removed device mappings
config:

NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
ata-TEAM_T253X6001T_TPBF2110150060100054-part3 ONLINE 0 0 0 (26% trimmed, started at Thu 04 Aug 2022 01:23:18 PM CEST)
ata-TEAM_T253X6001T_TPBF2110150060100657-part3 ONLINE 0 0 0 (25% trimmed, started at Thu 04 Aug 2022 01:23:18 PM CEST)

errors: No known data errors
root@pve:~#
root@pve:~# zpool status -vt rpool
pool: rpool
state: ONLINE
scan: resilvered 6.45G in 00:01:25 with 0 errors on Thu Aug 4 13:22:50 2022
remove: Removal of vdev 4 copied 168M in 0h0m, completed on Sun Jul 31 19:50:30 2022
27.2K memory used for removed device mappings
config:

NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
ata-TEAM_T253X6001T_TPBF2110150060100054-part3 ONLINE 0 0 0 (100% trimmed, completed at Thu 04 Aug 2022 01:23:29 PM CEST)
ata-TEAM_T253X6001T_TPBF2110150060100657-part3 ONLINE 0 0 0 (100% trimmed, completed at Thu 04 Aug 2022 01:23:30 PM CEST)

errors: No known data errors
root@pve:~#
 
You must log in or register to reply here.
Top Bottom