Selfhosted

39919 readers

234 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Mirror seeing half the write IOPS on one disk than the other, is this normal? (discourse.practicalzfs.com)

submitted 1 month ago* (last edited 1 month ago) by lightrush@lemmy.ca to c/selfhosted@lemmy.world

15 comments fedilink hide all child comments

I'm syncoiding from my normal RAIDz2 to a backup mirror made of 2 disks. I looked at zpool iostat and I noticed that one of the disks consistently shows less than half the write IOPS of the other:

                                        capacity     operations     bandwidth 
pool                                  alloc   free   read  write   read  write
------------------------------------  -----  -----  -----  -----  -----  -----
storage-volume-backup                 5.03T  11.3T      0    867      0   330M
  mirror-0                            5.03T  11.3T      0    867      0   330M
    wwn-0x5000c500e8736faf                -      -      0    212      0   164M
    wwn-0x5000c500e8737337                -      -      0    654      0   165M

This is also evident in iostat:

     f/s f_await  aqu-sz  %util Device
    0.00    0.00    3.48  46.2% sda
    0.00    0.00    8.10  99.7% sdb

The difference is also evident in the temperatures of the disks. The busier disk is 4 degrees warmer than the other. The disks are identical on paper and bought at the same time.

Is this behaviour expected?

you are viewing a single comment's thread
view the rest of the comments

[–] themoonisacheese@sh.itjust.works 2 points 1 month ago (2 children)

It's a gigabyte ab350m gaming-3 rev 1.0. it boots grub fine but then crashes right after displaying "loading Linux 6.x", CPU led flashes then dram led stays on, I have to turn it off with the PSU switch.

Either it's a rev 1.0 bug which is a thing on those motherboards, or the CPU (or igpu) is defective.

https://superuser.com/questions/1854228/proxmox-doesnt-boot-after-cpu-change

I'm currently waiting on support from both the seller and gigabyte but I don't expect anything out of it, though I'm still yet to test it in a different motherboard.

[–] lightrush@lemmy.ca 1 points 1 month ago* (last edited 1 month ago)

Iiinteresting. I'm on the larger AB350-Gaming 3 and it's got REV: 1.0 printed on it. No problems with the 5950X so far. 🤐 Either sheer luck or there could have been updated units before they officially changed the rev marking.

[–] lightrush@lemmy.ca 1 points 1 month ago (1 children)

I think the board has reached the end of the road. 😅

[–] themoonisacheese@sh.itjust.works 1 points 3 weeks ago

Sorry I 'ever saw this, that sucks.

Turns out mine was broken too. I put the CPU in my gaming rig and it worked fine, so I bought a new motherboard and the problem is gone.