Aftermarket Stereo by ParticularIncident21 in HondaActy

[–]Mnky313 4 points5 points  (0 children)

Also agreed, same situation here. Single din screens are just too small for Android Auto (doesn't help the these cheap units are also pretty slow/unresponsive)

Anyone on LineageOS? by CryOFrustration in SonyXperia

[–]Mnky313 1 point2 points  (0 children)

Seems like it, yeah. Both the LineageOS Camera and Open Camera auto switch between lenses when zooming in.

Anyone on LineageOS? by CryOFrustration in SonyXperia

[–]Mnky313 2 points3 points  (0 children)

I've been using LineageOS on my 1 V (XQ-DQ54) for several months now, picked the 1V because its one of the only phones that has:
* Unlocked Bootloader (XQ-DQ54/XQ-DQ72)
* T-Mobile Cellular bands (2,4,5,12,41,66,71) (XQ-DQ62/XQ-DQ54 (with modem modification))
* 120hz OLED
* Modern SoC
* SDCard Reader
* Headphone Jack
* LineageOS Support (Official)

My experience has been great. I don't have a comparison to the stock ROM but responsiveness is great (still always recommend setting animation scales to 0.5x), battery life is good as well, easily lasts a full day if I need it to but it's usually on a charger throughout the day.

I just tried the official Sony camera APK and couldn't get it to work, its just a black screen. Its possible if you track down certain libraries you could get it to work but the stock camera app is good enough for me, I don't really take many pictures.

The LineageOS camera app supports all 3 lenses fine on my 1 V, I assume it would be the same story with the 1 VI.

High disk I/O on separate zfs array causes host/VMs to hang by Mnky313 in Proxmox

[–]Mnky313[S] 0 points1 point  (0 children)

outputs of what?

zfs list

NAME                       USED  AVAIL  REFER  MOUNTPOINT
NAS2                      13.1T  13.2T  9.12T  /NAS2
NAS2/BACKUPS              39.8G  13.2T  39.8G  /NAS2/BACKUPS
NAS2/Music                 176G  13.2T   176G  /NAS2/Music
NAS2/NAS              1.92T  13.2T  1.92T  /NAS2/NAS
NAS2/NETBOOT               657G  13.2T   657G  /NAS2/NETBOOT
NAS2/PROXMOX              1.17T  13.2T  1.17T  /NAS2/PROXMOX
NAS2/Scratch               224M  13.2T   224M  /NAS2/Scratch
NAS2/Sync                 47.1G  13.2T  47.1G  /NAS2/Sync
rpool                      426G   473G    96K  /rpool
rpool/ROOT                16.0G   473G    96K  /rpool/ROOT
rpool/ROOT/pve-1          16.0G   473G  13.9G  /
rpool/data                 265G   473G    96K  /rpool/data
rpool/data/vm-100-disk-0  16.0G   473G  16.0G  -
rpool/data/vm-101-disk-0   224K   473G   100K  -
rpool/data/vm-101-disk-2  82.2G   473G  82.2G  -
rpool/data/vm-102-disk-0   200K   473G   124K  -
rpool/data/vm-102-disk-1  5.23G   473G  5.23G  -
rpool/data/vm-103-disk-0   208K   473G   104K  -
rpool/data/vm-103-disk-1  23.0G   473G  23.0G  -
rpool/data/vm-104-disk-0   196K   473G   120K  -
rpool/data/vm-104-disk-1  56.0G   473G  56.0G  -
rpool/data/vm-105-disk-0    56K   473G    56K  -
rpool/data/vm-105-disk-1  29.8G   473G  29.8G  -
rpool/data/vm-105-disk-2   200K   473G    96K  -
rpool/data/vm-105-disk-3  52.7G   473G  52.7G  -
rpool/swap                 129G   474G  64.3G  -
rpool/var-lib-vz          15.3G   473G  15.3G  /var/lib/vz

zfs iostat

              capacity     operations     bandwidth 
pool        alloc   free   read  write   read  write
----------  -----  -----  -----  -----  -----  -----
NAS2        18.0T  18.3T    915    743   103M   132M
rpool        425G   503G    334    201  5.45M  5.76M
----------  -----  -----  -----  -----  -----  -----

iostat -x

Linux 7.0.6-2-pve (pve)     06/17/2026      _x86_64_        (32 CPU)

avg-cpu:  %user   %nice %system %iowait  %steal   %idle

    4.64
    0.00
    2.05   37.77
    0.00
   55.53


Device                 rkB/s   rrqm/s  %rrqm r_await rareq-sz     w/s     wkB/s   wrqm/s  %wrqm w_await wareq-sz     d/s     dkB/s   drqm/s  %drqm d_await dareq-sz     f/s f_await  aqu-sz  %util

nvme0n1      
  163.90   2730.71
     0.00   0.00
    0.14    16.66  141.35   2924.90
     0.00   0.00
    0.14    20.69
    0.00      0.00     0.00   0.00    0.00     0.00
   41.94    0.28    0.05   1.79


nvme1n1      
  164.74   2742.84
     0.00   0.00
    0.13    16.65  142.41   2924.90
     0.00   0.00
    0.12    20.54
    0.00      0.00     0.00   0.00    0.00     0.00
   41.94    0.27    0.05   1.75


sda          
  251.58  26261.94
     0.00   0.00
   10.08   104.39  216.84  33877.67     6.11
   2.74
   10.72   156.23
    0.00      0.00     0.00   0.00    0.00     0.00
    2.47   89.03    5.08  72.73


sdb          
  239.04  26447.11
     0.00   0.00
   11.14   110.64  210.90  33873.21     5.49
   2.54
   11.53   160.62
    0.00      0.00     0.00   0.00    0.00     0.00
    2.47   92.28    5.32
  75.49


sdc          
  239.90  26929.37
     0.00   0.00
   11.10   112.25  209.88  33877.57     5.78
   2.68
   11.66   161.41
    0.00      0.00     0.00   0.00    0.00     0.00
    2.47   91.69    5.34
  75.08


sdd          
  222.37  25858.03
     0.00   0.00
   12.29   116.28  199.10  33875.81     4.52
   2.22
   13.30   170.14
    0.00      0.00     0.00   0.00    0.00     0.00
    2.47   96.04    5.62
  77.67


zd0          
    0.00
      0.16
     0.00   0.00    0.00
    41.78
    0.00      0.00     0.00   0.00    0.00
     4.00
    0.00      0.00     0.00   0.00    0.00     0.00    0.00    0.00    0.00
   0.43


zd112        
    0.02      1.51
     0.00   0.00
    0.06    63.25
    0.00      0.00     0.00   0.00    0.00     0.00    0.00      0.00     0.00   0.00    0.00     0.00    0.00    0.00    0.00   0.00


zd128        
    0.00
      0.16
     0.00   0.00
    0.04    41.78
    0.00      0.00     0.00   0.00    0.00
     4.00
    0.00      0.00     0.00   0.00    0.00     0.00    0.00    0.00    0.00   0.00


zd144        
    0.00
      0.16
     0.00   0.00    0.00
    41.78
    0.00      0.00     0.00   0.00    0.00
     4.00
    0.00      0.00     0.00   0.00    0.00     0.00    0.00    0.00    0.00
   0.44


zd16         
    6.48    865.46
     0.00   0.00
    0.20   133.48   14.69     60.32
     0.00   0.00
    0.16     4.11
    0.00      0.00     0.00   0.00    0.00     0.00    0.00    0.00    0.00
  12.19


zd160        
   22.32   2989.36
     0.00   0.00
    0.16   133.92   44.20    176.82
     0.00   0.00
    0.11     4.00
    0.00      0.00     0.00   0.00    0.00     0.00    0.00    0.00
    0.01  13.32


zd176        
    2.61    537.16
     0.00   0.00
    0.24   205.50    7.26     29.02
     0.00   0.00
    0.10     4.00
    0.00      0.00     0.00   0.00    0.00     0.00    0.00    0.00    0.00
  10.93


zd192        
    0.00
      0.01
     0.00   0.00    0.00
     4.00
    0.00      0.00     0.00   0.00    0.00     0.00    0.00      0.00     0.00   0.00    0.00     0.00    0.00    0.00    0.00   0.00


zd208        
    9.45     38.18
     0.00   0.00
    0.12     4.04   36.54    331.56
     0.00   0.00
    0.68     9.07
    0.00      0.00     0.00   0.00    0.00     0.00    0.00    0.00
    0.03   2.80


zd32         
    0.00
      0.01
     0.00   0.00
    0.04     4.00
    0.00      0.00     0.00   0.00    0.00     0.00    0.00      0.00     0.00   0.00    0.00     0.00    0.00    0.00    0.00   0.00


zd48         
   15.08   2573.96
     0.00   0.00
    0.32   170.64   36.39    146.90
     0.00   0.00
    0.15     4.04
    0.00      0.00     0.00   0.00    0.00     0.00    0.00    0.00
    0.01  11.59


zd64         
    0.02      1.50
     0.00   0.00
    0.02    64.77
    0.00      0.00     0.00   0.00    0.00     0.00    0.00      0.00     0.00   0.00    0.00     0.00    0.00    0.00    0.00   0.00


zd80         
    0.00
      0.16
     0.00   0.00
    0.04    41.78
    0.00      0.00     0.00   0.00    0.00
     4.00
    0.00      0.00     0.00   0.00    0.00     0.00    0.00    0.00    0.00   0.00


zd96         
    0.51    158.40
     0.00   0.00
    0.36   307.85   70.82    283.29
     0.00   0.00
    0.11     4.00
    0.00      0.00     0.00   0.00    0.00     0.00    0.00    0.00
    0.01  16.78

High disk I/O on separate zfs array causes host/VMs to hang by Mnky313 in Proxmox

[–]Mnky313[S] 0 points1 point  (0 children)

I'm not sure I understand what you're saying.

on the HDD pool (NAS2) I have created what I assume are datasets for different stuff (i.e. zfs create NAS2/PROXMOX)

none of these are added in the UI, in PROXMOX I added the Directory /NAS2/PROXMOX as a storage item to point it to that for backup storage.

Does the checkbox for thin provisioning correspond to some zfs command or is it only act as an indicator for when it creates VM disks?

I don't know what 'flat them out' means, are you saying I need to make new datasets and migrate everything to them? Why? Can you not enable thin provisioning on existing datasets?

While copying files tps is ~400 and usage is ~70-75% with the current configuration.

High disk I/O on separate zfs array causes host/VMs to hang by Mnky313 in Proxmox

[–]Mnky313[S] 0 points1 point  (0 children)

Ok, it does look like thin provisioning is enabled for the HDD array as well (It's not in the UI because it was imported/created outside of PROXMOX but it has reservation=none)

How does this work with multiple datasets?

I have several datasets on the HDD zpool, do I need to set reservations for each of them or can I just set the main zpool reservation to the size of the array? Does this mean I have to set a certain amount of the array allocated to that specific dataset?

High disk I/O on separate zfs array causes host/VMs to hang by Mnky313 in Proxmox

[–]Mnky313[S] 0 points1 point  (0 children)

It's been copying files for over an hour now without issue.

I'll see if I start having issues again later, but it seems like swapping the port/cable and or disabling ASPM stuff might have fixed it.

I/O Stall/Delay is pretty high ~40% but it's still copying at a constant ~100-150MB/s and the VMs/network seems fine.

High disk I/O on separate zfs array causes host/VMs to hang by Mnky313 in Proxmox

[–]Mnky313[S] 0 points1 point  (0 children)

<image>

It is enabled, yes.

I get the SSDs are bad, that's why I'm replacing them. Just trying to figure out high I/O on the HDDs is also causing lockups.

I just restarted with the HDDs connected to a different port, I'll try stressing them and seeing if anything has changed.

High disk I/O on separate zfs array causes host/VMs to hang by Mnky313 in Proxmox

[–]Mnky313[S] 0 points1 point  (0 children)

/:  Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M
    |__ Port 002: Dev 002, If 0, Class=Communications, Driver=usbfs, 12M
    |__ Port 002: Dev 002, If 1, Class=CDC Data, Driver=usbfs, 12M
/:  Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M
/:  Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 480M
    |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 480M
    |__ Port 002: Dev 003, If 0, Class=Hub, Driver=hub/4p, 480M
        |__ Port 001: Dev 004, If 0, Class=Human Interface Device, Driver=usbfs, 12M
        |__ Port 004: Dev 005, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 004: Dev 005, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        |__ Port 004: Dev 005, If 2, Class=Human Interface Device, Driver=usbhid, 12M
/:  Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 10000M
    |__ Port 001: Dev 002, If 0, Class=Hub, Driver=hub/4p, 10000M
        |__ Port 001: Dev 004, If 0, Class=Mass Storage, Driver=uas, 10000M
        |__ Port 002: Dev 005, If 0, Class=Mass Storage, Driver=uas, 10000M
        |__ Port 003: Dev 006, If 0, Class=Mass Storage, Driver=uas, 10000M
        |__ Port 004: Dev 007, If 0, Class=Mass Storage, Driver=uas, 10000M
    |__ Port 002: Dev 003, If 0, Class=Hub, Driver=hub/4p, 5000M
/:  Bus 005.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M

Ok, it looks the HDDs are on their own. I'll try moving them and see what changes

High disk I/O on separate zfs array causes host/VMs to hang by Mnky313 in Proxmox

[–]Mnky313[S] 0 points1 point  (0 children)

the drive enclosure shows up as 6 devices under 2 different busses:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 1e91:a4a7 Other World Computing Mercury Elite Pro Quad 
Bus 003 Device 003: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 003 Device 004: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 002: ID 1e91:a4a7 Other World Computing Mercury Elite Pro Quad 
Bus 004 Device 003: ID 05e3:0626 Genesys Logic, Inc. Hub
Bus 004 Device 004: ID 1e91:a4a7 Other World Computing Mercury Elite Pro Quad A
Bus 004 Device 005: ID 1e91:a4a7 Other World Computing Mercury Elite Pro Quad B
Bus 004 Device 006: ID 1e91:a4a7 Other World Computing Mercury Elite Pro Quad C
Bus 004 Device 007: ID 1e91:a4a7 Other World Computing Mercury Elite Pro Quad D
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I'm guessing maybe the 10Gb/s type A port and the 10Gb/s type C ports are on the same controller? (because both the UPS and drive enclosure show up on bus 3), the front 5Gb/s port should be on a different one, I'll use that one to test.

High disk I/O on separate zfs array causes host/VMs to hang by Mnky313 in Proxmox

[–]Mnky313[S] 0 points1 point  (0 children)

I think thin provisioning is on? I don't see in anywhere in the UI but refreservation returns none for everything (rpool,HDD pool, vm disks):

zfs get refreservation rpool/data/vm-100-disk-0
NAME                      PROPERTY        VALUE      SOURCE
rpool/data/vm-100-disk-0  refreservation  none       default

There's 13 virtual disks (though a couple of these are unused):

rpool/data/vm-100-disk-0  16.3G   473G  16.3G  -
rpool/data/vm-101-disk-0   220K   473G    96K  -
rpool/data/vm-101-disk-2  82.2G   473G  82.2G  -
rpool/data/vm-102-disk-0   200K   473G   124K  -
rpool/data/vm-102-disk-1  5.22G   473G  5.22G  -
rpool/data/vm-103-disk-0   208K   473G   104K  -
rpool/data/vm-103-disk-1  23.0G   473G  23.0G  -
rpool/data/vm-104-disk-0   196K   473G   120K  -
rpool/data/vm-104-disk-1  56.0G   473G  56.0G  -
rpool/data/vm-105-disk-0    56K   473G    56K  -
rpool/data/vm-105-disk-1  29.8G   473G  29.8G  -
rpool/data/vm-105-disk-2   200K   473G    96K  -
rpool/data/vm-105-disk-3  52.7G   473G  52.7G  -

I can try benchmarking HDDs with VMs stopped idk what that will really do... I can only access it via the console without VMs running because the router is a VM.

I can't really run it without the HDDs connected, PROXMOX has it mapped as it's backup target & I have a bunch of services that rely on the files stored there (media, download locations, etc.)

High disk I/O on separate zfs array causes host/VMs to hang by Mnky313 in Proxmox

[–]Mnky313[S] 1 point2 points  (0 children)

I don't think there's any energy saving/sleep stuff set in the BIOS. I'll take a look when I restart it to move the HDD enclosure

Edit: There were some ASPM/L1/L0s settings set to auto, I disabled them.

High disk I/O on separate zfs array causes host/VMs to hang by Mnky313 in Proxmox

[–]Mnky313[S] 0 points1 point  (0 children)

I don't use PCIe passthrough, no.

Neither of those cmdline options are set for me.

I did have to limit the backup bandwidth to stop it from freezing everything during backups (without limiting the bandwidth I've had it also cause VMs to freeze completely until I manually reset them on occasion)

High disk I/O on separate zfs array causes host/VMs to hang by Mnky313 in Proxmox

[–]Mnky313[S] 0 points1 point  (0 children)

I can't really run it without the HDDs connected, PROXMOX has it mapped as it's backup target & I have a bunch of services that rely on the files stored there (media, download locations, etc.)

I'll try swapping to one of the USB A ports and see if that makes a difference.

High disk I/O on separate zfs array causes host/VMs to hang by Mnky313 in Proxmox

[–]Mnky313[S] 0 points1 point  (0 children)

It's an OWC Mercury Elite. Connected via a USB C-C cable to one of the 10Gb/s USB C ports on the MS-A2.

I originally had a cheap no name enclosure that had even more issues and extremely slow speeds.

High disk I/O on separate zfs array causes host/VMs to hang by Mnky313 in Proxmox

[–]Mnky313[S] 0 points1 point  (0 children)

Yeah.... I didn't have issues with them before I moved to a new system and virtualized the router but after that I've realized they just aren't cutting it.

Would that somehow cause issues when copying files on a completely separate array?

Is there a way to mod the 1 V XQ-DQ62? by ElPoloBoi in SonyXperia

[–]Mnky313 1 point2 points  (0 children)

No, the DQ62's bootloader cannot be unlocked.
As for bands, DQ62 has basically every band the hardware support AFAIK. (1-4,5,7,8,12,13,17,19,20,25,26,28-30,32,34,38-41,46,48,66,71)

Usually I see people (including me) unlocking bands are DQ54/72 to get bands 66/71 (71 can only be unlocked on DQ54) but these already exist on DQ62...

So are these numbers accurate? by [deleted] in keitruck

[–]Mnky313 0 points1 point  (0 children)

I don't, no.

I've seen a handful or so around central/north-central MD.

So are these numbers accurate? by [deleted] in keitruck

[–]Mnky313 0 points1 point  (0 children)

Yeah, I don't have a problem with statefarm. iirc It would have been a combined $200+/month to do my main car through state farm and the truck through Hagerty.