NathanR
Members
-
Joined
-
Last visited
Everything posted by NathanR
-
128 GiB DDR5 Single-bit ECC
-
TL;DR Share must be cache primary [secondary doesn't matter] when doing top level manual splitting via rootshare I don't know where to put this. But just spent all day trying to figure this out with LLMs and finally fixed it myself because they kept thinking this was a minimum space or mounting issue (it isn't). Moved my music from array to cache drive with unbalanced. Found out I couldn't write to music (disk space full). Spent entire day circling trying random commands. Finally just set my Media share to cache first (as my other share was working). Worked first try. Dang.
-
So you cleared a 16TB disk for ~20hrs without the CLI terminal closing? I would think a disclaimer stating that the dd command doesn't run in background would be useful. I would wonder why mine didn't clear at full speed. You can't imagine any improvements to the documentation at all?
-
Ahh yes, I misunderstood/dumb moment. Duh, it has to write parity during writing zeros to drive; It's just after that I can remove it and force a "parity is valid checkbox". Anyways, I'm content with my setup. But that documentation and/or feature should be looked at. I can do it on my second server if it helps troubleshoot this issue (does anyone want to look at this further?). Thanks!
-
Welp. Array finally stopped. ...and I decided to rip the band aid off. Tools > New Config > [I should have preserved the cache assignment] apply. After re-arranging my drives to make my OCD happy. Started array in maintenance mode, it found the encrypted xfs/zfs drives. Then stop & start in normal mode. It is now doing a parity-sync on both parity drives.
-
Welp, tried stopping the array. It's stuck doing whatever it is doing. Should I remove the temp drive1? umount /mnt/disk1 rm /tmp/xmini.img
-
I shutdown any dockers using the array. Not sure what else would be writing to any array disks. When I turn off the zero write (tried yesterday) the write speed doesn't change and array goes to idle. Whole point was to not write parity. It looks like it's re-writing parity anyways (just super slowly). Maybe I just cancel and remove the disk and move on, hah.
-
storinator-diagnostics-20250915-1228.zip Thanks for taking a looksee
-
Thanks, seems like Tmux was already installed. Any idea why progress is so slow? I did this to not risk loosing parity. Though I suppose with two parity drives I can pull remove one disk at a time and keep parity regardless.
-
You can expand the zfs pool I have not tried it or know anything about it other than it was released and possible.
-
Agreed. However that is not the case as all my other dockers backup properly. (I did not show that screenshot, but I have tried multiple source types in the settings box. Even going so far to list every plex sub-directory. All yield the same result.) It’s a weird bug. No worries here. I’ll probably move to zfs snapshots at some point and won’t worry about this. @KluthR no worries, I’m not asking you to change anything. I figured it out by reading other messages in this thread. Thank you :)
-
I followed the steps in the docs https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array-configuration/#removing-disks However, I want to clear my dual 16TB drives regardless of CLI closing. Should I use: nohup dd bs=1M if=/dev/zero of=/dev/mdXp1 status=progress
-
I understand this plugin to be frozen and only bugfixes moving forward. I am not requesting a bugfix or anything. Just a note to others. Thank you for the time and effort you have given the community. Plex backup isn't working for me. "plex does not have any volume to back up! Skipping. Please consider ignoring this container." I think the issue is this: "/mnt/cache/appdata/plex" is showing as external somehow. Weird. I will look at debug logs next. Also groups, you simply make one by typing text in the group field and hitting save. Current help text doesn't make a ton of sense. Hope that helps others.
-
Okay so zfs encrypted with a short passphrase (as a test) worked. Not sure what I did differently today vs last night? I restarted unraid this morning. Edit: Using a full-long passphrase worked. I guess a restart fixed it? Dunno. Was loosing hair last night. Now for some speed tests :)
-
Well... zfs unencrypted just worked. I simply formatted it a second time. (I have done this before with encrypted deployment). I will delete and try again.
-
Trying to setup new Cache pool with 3x 4TB NVMe Drives in a ZFS Z1 Encrypted setup. Edit: Version 7.1.4 I used this guide: https://forums.unraid.net/topic/170102-how-exactly-do-i-encrypt-replacement-cache-disks It goes through all the motions, but then says "Unmountable: wrong or no file system". I have used both zfs encryped and zfs unencrypted without success. I'm not sure what else to do. Similar Topics: https://forums.unraid.net/topic/193174-unmountable-error-with-zfs-nvme-cache-was-working-for-months-without-issue-no-recent-config-changes/#comment-1575896 https://forums.unraid.net/topic/193154-please-help-zfs-cache-pool-unmountable-wrong-or-no-file-system/#comment-1575827 https://forums.unraid.net/topic/193154-please-help-zfs-cache-pool-unmountable-wrong-or-no-file-system/#comment-1575732 https://forums.unraid.net/topic/145331-how-to-encrypt-existing-zfs-drivepool-containing-snapshots/#comment-1307830 https://forums.unraid.net/topic/178927-unmountable-unsupported-or-no-file-system-for-cache-after-powerfailure/#comment-1483183 https://forums.unraid.net/topic/155608-cannot-create-a-functioning-zfs-array/#comment-1378343 https://forums.unraid.net/topic/143628-unmountable-volume-not-encrypted/#comment-1295119
-
Continued from my previous build. I have successfully implemented the new CPU/Mobo setup. Figuring out the fans and IPMI and bios and such was a slight pain. But I got it. I can now use all CPU cores without everything yelling at me. I was able to setup plex encoding easily enough. Added a second NIC to my HA VMs (that was harder then it should have been). Using DAC for 10G via a Intel X520 card with failover to the 1G NIC. Still haven't been able to figure out why the Google Coral USB 3.0 device won't recognize in my HA VM, but it's been some time; I'll revisit that soon. Server draws 70w at idle, I'm sure I could get that down more, but I haven't played with any power saving settings. Mostly been building out a better Unifi network and smart home things and power systems than focusing on the server. (It works!) yayPower outage caused my server to shutdown gracefully. I turned it on normally (via IPMI) and this shows up. Docker & VM don't work (obviously). Not sure if safe to update to latest release or not? I have backups on the array so I can fix it worst case scenario. I put the array in maintenance mode and don't get any errors/warnings. Cache is in BTRFS mirror mode. Scrub didn't show anything. Filesystem check didn't show anything. I haven't updated because I plan in moving to an intel build for Intel quicksync, but haven't had time. Just left it running for last 6 months, haha Note: I did submit a bug report via the official GUI. But figured I could get the answer to upgrade here in the forums quicker. May 10 13:41:34 Storinator kernel: loop2: detected capacity change from 0 to 62914560 May 10 13:41:34 Storinator kernel: BTRFS: device fsid 3a50e386-e261-4e10-8246-1e28523bd03e devid 1 transid 1511578 /dev/loop2 scanned by mount (30967) May 10 13:41:34 Storinator kernel: BTRFS info (device loop2): using free space tree May 10 13:41:34 Storinator kernel: BTRFS info (device loop2): has skinny extents May 10 13:41:35 Storinator kernel: BTRFS info (device loop2): start tree-log replay May 10 13:41:35 Storinator kernel: lo_write_bvec: 4 callbacks suppressed May 10 13:41:35 Storinator kernel: loop: Write error at byte offset 307904512, length 4096. May 10 13:41:35 Storinator kernel: I/O error, dev loop2, sector 601376 op 0x1:(WRITE) flags 0x1800 phys_seg 1 prio class 0 May 10 13:41:35 Storinator kernel: btrfs_dev_stat_print_on_error: 4 callbacks suppressed May 10 13:41:35 Storinator kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 May 10 13:41:35 Storinator kernel: loop: Write error at byte offset 39469056, length 4096. May 10 13:41:35 Storinator kernel: I/O error, dev loop2, sector 77088 op 0x1:(WRITE) flags 0x1800 phys_seg 1 prio class 0 May 10 13:41:35 Storinator kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0 May 10 13:41:35 Storinator kernel: loop: Write error at byte offset 307855360, length 4096. May 10 13:41:35 Storinator kernel: I/O error, dev loop2, sector 601280 op 0x1:(WRITE) flags 0x1800 phys_seg 2 prio class 0 May 10 13:41:35 Storinator kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0 May 10 13:41:35 Storinator kernel: loop: Write error at byte offset 39419904, length 4096. May 10 13:41:35 Storinator kernel: I/O error, dev loop2, sector 76992 op 0x1:(WRITE) flags 0x1800 phys_seg 2 prio class 0 May 10 13:41:35 Storinator kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 4, rd 0, flush 0, corrupt 0, gen 0 May 10 13:41:35 Storinator kernel: loop: Write error at byte offset 307445760, length 4096. May 10 13:41:35 Storinator kernel: I/O error, dev loop2, sector 600480 op 0x1:(WRITE) flags 0x1800 phys_seg 1 prio class 0 May 10 13:41:35 Storinator kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 5, rd 0, flush 0, corrupt 0, gen 0 May 10 13:41:35 Storinator kernel: loop: Write error at byte offset 39010304, length 4096. May 10 13:41:35 Storinator kernel: I/O error, dev loop2, sector 76192 op 0x1:(WRITE) flags 0x1800 phys_seg 1 prio class 0 May 10 13:41:35 Storinator kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 6, rd 0, flush 0, corrupt 0, gen 0 May 10 13:41:35 Storinator kernel: loop: Write error at byte offset 309346304, length 4096. May 10 13:41:35 Storinator kernel: I/O error, dev loop2, sector 604192 op 0x1:(WRITE) flags 0x1800 phys_seg 1 prio class 0 May 10 13:41:35 Storinator kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 7, rd 0, flush 0, corrupt 0, gen 0 May 10 13:41:35 Storinator kernel: loop: Write error at byte offset 40910848, length 4096. May 10 13:41:35 Storinator kernel: I/O error, dev loop2, sector 79904 op 0x1:(WRITE) flags 0x1800 phys_seg 1 prio class 0 May 10 13:41:35 Storinator kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 8, rd 0, flush 0, corrupt 0, gen 0 May 10 13:41:35 Storinator kernel: loop: Write error at byte offset 308871168, length 4096. May 10 13:41:35 Storinator kernel: I/O error, dev loop2, sector 603264 op 0x1:(WRITE) flags 0x1800 phys_seg 1 prio class 0 May 10 13:41:35 Storinator kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 9, rd 0, flush 0, corrupt 0, gen 0 May 10 13:41:35 Storinator kernel: loop: Write error at byte offset 40435712, length 4096. May 10 13:41:35 Storinator kernel: I/O error, dev loop2, sector 78976 op 0x1:(WRITE) flags 0x1800 phys_seg 1 prio class 0 May 10 13:41:35 Storinator kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 10, rd 0, flush 0, corrupt 0, gen 0 May 10 13:41:35 Storinator kernel: BTRFS: error (device loop2) in btrfs_commit_transaction:2418: errno=-5 IO failure (Error while writing out transaction) May 10 13:41:35 Storinator kernel: BTRFS warning (device loop2: state E): Skipping commit of aborted transaction. May 10 13:41:35 Storinator kernel: BTRFS: error (device loop2: state EA) in cleanup_transaction:1982: errno=-5 IO failure May 10 13:41:35 Storinator kernel: BTRFS: error (device loop2: state EA) in btrfs_replay_log:2500: errno=-5 IO failure (Failed to recover log tree) May 10 13:41:35 Storinator root: mount: /var/lib/docker: can't read superblock on /dev/loop2. May 10 13:41:35 Storinator root: dmesg(1) may have more information after failed mount system call. May 10 13:41:35 Storinator root: mount error May 10 13:41:35 Storinator kernel: BTRFS error (device loop2: state EA): open_ctree failed Model: Custom M/B: ASRockRack X570D4U-2L2T Version - s/n: 208002330000188 BIOS: American Megatrends International, LLC. Version P1.40. Dated: 05/19/2021 CPU: AMD Ryzen 9 5900X 12-Core @ 3700 MHz HVM: Enabled IOMMU: Enabled Cache: 768 KiB, 6 MB, 64 MB Memory: 64 GiB DDR4 Multi-bit ECC (max. installable capacity 128 GiB) Network: bond0: fault-tolerance (active-backup), mtu 1500 Kernel: Linux 5.19.17-Unraid x86_64 OpenSSL: 1.1.1s storinator-diagnostics-20240510-1346.zipThanks for this, works perfectly!Been running 6.11.5 for a while now. Current uptime is 2 months 22 days. Can't remember the last thing I did that required me to reboot it. I remember now, added a USB 3.0 card so I could pass-through for my W10 VM so I could run LOR for my Christmas lights. No crashes. Been very happy. Future Wishes: VM cloning, backup, snapshot, etc. Rebuild server with 13900K, X13SAE-F, 128GB ECC quicksync (GPU) encoding for plex more USB Plugins: Community CA Backup / Restore Appdata Dynamix Auto Fan Control Dynamix File Manager Dynamix System Statics Dynamix System Temperature Network UPS Tools (NUT) Unassigned Devices Unassigned Devices Plus Unassigned Devices Preclear Unraid Connect User Scripts Docker: blueiris (not on) DiskSpeed (not on) docker-diag-tools (not on) ESPHome glances Grafana-Unraid-Stack (not on) luckyBackup (not on) MongoDB (not on) OpenProject Phoronix-Test-Suite (not on) plex qbitorrent (not on) syslog-ng (not on) unifi-controller UniFi-Protect-Backup UptimeKuma VMs Dev-Home Assistant Home Assistant W10-SVR Win10 (not on) Decided to make a development home assistant VM to play around with things and not break my house. Process still works in Feb of 2024 Download Home Assistant .qcow2 file Copy to Array somehow Shared folder Upload via Dynamix File Manager app Create VM (linux) 32GB HDD Delete the vdisk vdisk1.img /mnt/user/domains/Dev-Home Assistant/vdisk1.img Run the convert command qemu-img convert -p -f qcow2 -O raw -o preallocation=off "/mnt/user/domains/Dev-Home Assistant/haos_ova-11.4.qcow2" "/mnt/user/domains/Dev-Home Assistant/vdisk1.img Boot the VM Launch VNC Get IP Login Woot/FINSo I don't know why people do what they do. What I can say is it is unlikely to matter what the mobo says it can support TDP wise. Rationale for the above statement: 1) 125W TDP is just a classification, real metrics will change depending on workload 2) Average power draw will be ~114w. Sauce: https://www.techpowerup.com/review/intel-core-i9-13900k/22.html 3) 8-pin CPU connector can deliver 235w so the mobo isn't power limited. Sauce: https://www.overclock.net/threads/gpu-and-cpu-power-connections.1773088/ 4) Power Components will work until their thermal limits are exceeded. Meaning the mosfets will deliver more current (power) than they are designed for until they reach thermal limiting. Sauce: https://www.infineon.com/dgdl/ir3550.pdf?fileId=5546d462533600a4015355cd7c831761 (note, this is a generic VRM, I do not know what VRM the X13 uses) 4A) servers usually have forced air cooling...thus the thermal headroom on the heatsink is very little because it is expected there will be hundreds of CFM moving across the mobo... Home server will cause thermal bottle-necks. 5) Bench/Stress peak power ratings are often meaningless, (albeit fun, interesting, useful to find the limits) for what we would typically use the 13900k For (server, docker, VM, storage) X13SAE-F mini-review/writeup https://www.servethehome.com/supermicro-x13sae-f-intel-w680-motherboard-mini-review/3/ Thank you! This is awesome. You probably saved me 20+hrs of work. I am considering moving my 5900X build to intel for two reasons. 1) iGPU for PLEX transcoding (my parents, wife-parents, sister, etc. all need things transcoded; only direct play is in-house to my NVIDIA shield) 2) lower power consumption (more efficient processors for dockers & server VMs) Build I'm considering: Mobo: MBD-X13SAE-F-O 64GB: MEM-DR532MD-EU48 13700k or 13900K Re-use everything else from my 5900X buildThank you for this! For some reason a recent Uptime Kuma or Unifi Controller update broke them talking to eachother for webpage status. Found-out the docker host connection was now added. Woot!
Is it safe to delete the old 2FA setup (Inc Backups?)That makes sense. I was trying so hard to figure out how to do it. This was the key. Perfect link'd article! Let me try it when I get home tonight and see how I fair Yes, I think this will be more intuitive (to my brain).
