Darksurf

Members
  • Posts

    156
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

1997 profile views

Darksurf's Achievements

Apprentice

Apprentice (3/14)

13

Reputation

  1. Unfortunately, no. The Dependency Hell threw a wrench in it. I've not tried since. Dealing with such deps on a static system is risky. This kind of power is really needed on the hypervisor side. You would also have to script/add/install all the deps and tool itself on every install due to the static nature of unraid (which is fair). That being said, if all the deps and the tool were installed from the beginning, this would be far less of a problem.
  2. @limetech I've found the exact issue! I've been experiencing the exact same issues on my desktop. While researching the issue I found someone else experiencing this in other distros too. In the persistent storage udev rules on how optical drives are handled, I've tweaked the udev rules as recommended here: https://forum.makemkv.com/forum/viewtopic.php?t=25357 My desktop is back to working as it should and no longer freeze/hangs on the external Bluray drives. This should also fix unraid too. TLDR: sr* lines in /lib/udev/60-persistent-storage.rules # probe filesystem metadata of optical drives which have a media inserted KERNEL=="sr*", ENV{DISK_EJECT_REQUEST}!="?*", ENV{ID_CDROM_MEDIA_TRACK_COUNT_DATA}=="?*", ENV{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}=="?*", \ IMPORT{builtin}="blkid --offset=$env{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}" # single-session CDs do not have ID_CDROM_MEDIA_SESSION_LAST_OFFSET KERNEL=="sr*", ENV{DISK_EJECT_REQUEST}!="?*", ENV{ID_CDROM_MEDIA_TRACK_COUNT_DATA}=="?*", ENV{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}=="", \ IMPORT{builtin}="blkid --noraid" becomes # probe filesystem metadata of optical drives which have a media inserted KERNEL=="sr*", ENV{DISK_EJECT_REQUEST}!="?*", ENV{ID_CDROM_MEDIA_TRACK_COUNT_DATA}=="?*", ENV{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}=="?*", \ GOTO="persistent_storage_end" # single-session CDs do not have ID_CDROM_MEDIA_SESSION_LAST_OFFSET KERNEL=="sr*", ENV{DISK_EJECT_REQUEST}!="?*", ENV{ID_CDROM_MEDIA_TRACK_COUNT_DATA}=="?*", ENV{ID_CDROM_MEDIA_SESSION_LAST_OFFSET}=="", \ GOTO="persistent_storage_end" My desktop is now able to view/play/rip blurays and dvds again. Evidently the IMPORT lines can cause hanging when certain video discs are placed in the drive. This explains why udevd hangs and begins killing /dev/sr0 when certain discs are inserted.
  3. OK, I've troubleshot this down to being mostly a problem with MakeMKV. Evidently it freaks out on certain discs it cannot read and it can cause MakeMKV to hang and/or become an unkillable ZOMBIE process. I thought being in an Unpriviledged Docker would at least allow me to kill off that docker to remove the process, but it appears that doesn't work. I do not get udev killing off my /dev/sr0 drive on my Manjaro desktop, but MakeMKV failing on specific unreadable discs still causes it to hang and turn into a zombie process just the same, unkillable by SIGKILL. Figured that piece of info could be valuable to devs. UPDATE: READ MY POST DOWN BELOW, SOLUTION HAS BEEN FOUND/SOLVED. ITS A UDEV RULE ISSUE!
  4. OK, I think I've found whats causing me grief since my upgrade from 6.9.2 . I use a docker that uses /dev/sr0 to rip blurays and dvd's for me. Sometimes I put in a disc and that docker hangs and locks up all other dockers, I get zombie processes I cannot SIGKILL, and I'm forced to reboot to clean it up and get the docker working again. What I've noticed is this: [ 324.178091] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 324.190405] sr 0:0:0:0: [sr0] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x03 driverbyte=DRIVER_OK cmd_age=30s [ 324.190410] sr 0:0:0:0: [sr0] tag#0 CDB: opcode=0x28 28 00 00 00 04 00 00 00 02 00 [ 324.190412] blk_update_request: I/O error, dev sr0, sector 4096 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [ 354.383938] usb 4-1: reset SuperSpeed USB device number 2 using xhci_hcd [ 473.812944] udevd[1688]: worker [27853] /devices/pci0000:00/0000:00:08.1/0000:03:00.3/usb4/4-1/4-1:1.0/host0/target0:0:0/0:0:0:0/block/sr0 timeout; kill it [ 473.812954] udevd[1688]: seq 11256 '/devices/pci0000:00/0000:00:08.1/0000:03:00.3/usb4/4-1/4-1:1.0/host0/target0:0:0/0:0:0:0/block/sr0' killed I've never seen udev do this before in 6.9.2 . Is this due to my new bluray drive, or is this due to 6.10.0-rc4 ? This is entirely new behavior to me. to generate diagnostics, I'm required to power off the bluray drive (/dev/sr0) to continue otherwise it hangs there. Anyone got any ideas? oceans-diagnostics-20220408-2342.zip
  5. I've been having issues with Dockers locking up lately. specifically a docker that I pass through /dev/sr0 for video ripping. while trying to pull diagnostics, it just hangs when it reaches /dev/sr0. Downloading... /boot/logs/oceans-diagnostics-20220404-1902.zip smartctl -x '/dev/sr0' 2>/dev/null|todos >'/oceans-diagnostics-20220404-1902/smart/HL-DT-ST_BD-RE_WH16NS60_210524880677-0-0-20220404-1902 (sr0).txt' after it hung here for quite some time, I was forced to turn the power off to /dev/sr0 so the diag collecting would complete. After turning off the USB Bluray drive, the docker was finally able to stop so something about passing a USB3 Bluray drive to a docker and the drive throwing errors was causing all of dockers to lock up, and hanging the diag log generation process.
  6. I’ve personally noticed that touches do not perfectly align to the webpage. Physical Tapping notification counts on the far right results in the touch event happening a little to the left of the touch missing the button you’re trying to touch. This is at least what’s happening on my iPhone 13 Pro.
  7. Thanks for the RC4 update! I’ve noticed lower RAM usage over RC3. I went from 6.9.2 to 6.10RC3 and immediately noticed issues. Sadly I did this as I was heading out the door for a week long trip so I didn’t have time to get diagnostics and troubleshoot. my machine runs a TR3970X w/ 64G of ECC RAM and consistently and floated around 80% RAM usage and wast stable. After RC3 update it immediately started shutting off one of my VMs due to being OOM. I run 2 VMs each with 20G of RAM and 10core/20threads . And the rest of the server ran on 12core/24threads with 24G of RAM. I’m going to retest this memory problem with RC4 and get diags if it occurs again, but so far so good. Fresh boot, all VMs are running which is a good sign and the RAM usage is lower this time. Wondering if the Nchan issue is related.
  8. I can't get the onlyoffice docker to work. its just a permanently loading bar. I only wanted to try this locally via local IP, but its stuck.
  9. I have linux VMs. They are actually build nodes used to build packages for a linux distribution. So my VMs accept jobs to compile and packages inside containers, upload said packages, then delete everything and start another job. I'm not sure if your suggestion works in this scenario does it?
  10. You might be able to perform a pull request to update the main project is you have through testing and proof of stability.
  11. It would be nice to have virt-sparsify to reduce VM disks size when they have zeros/unused space. https://libguestfs.org/virt-sparsify.1.html
  12. Is anyone else having issues with memory ballooning not working in VMs? I check my linux VMs and they have virtio_ballooning loaded, but their memory won't increase past initial size. I'm using an ASROCK Creator TRX40 w/ Ryzen Threadripper 3970X 64G DDR4. I'm using the rule initial memory is 1core=1G and Max is 1core=2G. I'm doing this on 3 VMs 8core, 8core, and 4core. None of which see their memory balloon while compiling software and they end up crashing with OOM errors. oceans-diagnostics-20210528-1427.zip
  13. That's awesome! It would be nice if we could get a lifespan meter somewhere in the open (it seems my method may be inaccurate and yours would be better). I want to make sure my server uptime doesn't take a bad turn when I need to order an SSD and it takes a week to get here. I'd like some pre-emptive warning/monitoring so I can plan accordingly rather than have items live on a shelf for years. Thanks for the correction! I'm learning something new everyday.
  14. I'm curious if it would be possible to store a MAX TBW for SSDs in the warranty information in the Identity drive info, then have a running comparison of what smartctl shows for nvme/ssds to show how close you are to reaching that maximum so someone would know to prepare for a replacement. You'll see after doing a smartctl -a /dev/nvme0n1 I have a "Data Units Written" of 9.67 TB. This unit has a MAX TBW of 1800. Now, this isn't my cache drive, this is my desktop. But if you're using an SSD as a cache drive, I'm sure you could see how the SSD would quickly deteriorate and fail. My cache SSD on my server is currently at 169TBW with a maximum of 530TBW before failure. Having this SSD lifespan viewable from the dashboard would be very helpful. My SSD in my server is only 1year old, but its used heavily for an open source project. jcfrosty@Zero ~ $ sudo smartctl -a /dev/nvme0n1 Password: smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.11.0-sabayon] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: Sabrent Rocket 4.0 1TB Serial Number: 03F10797054463199045 Firmware Version: EGFM11.1 PCI Vendor/Subsystem ID: 0x1987 IEEE OUI Identifier: 0x6479a7 Total NVM Capacity: 1,000,204,886,016 [1.00 TB] Unallocated NVM Capacity: 0 Controller ID: 1 Number of Namespaces: 1 Namespace 1 Size/Capacity: 1,000,204,886,016 [1.00 TB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64: 6479a7 2220653435 Local Time is: Sat Apr 17 11:32:39 2021 CDT Firmware Updates (0x12): 1 Slot, no Reset required Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test Optional NVM Commands (0x005d): Comp DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp Maximum Data Transfer Size: 512 Pages Warning Comp. Temp. Threshold: 70 Celsius Critical Comp. Temp. Threshold: 90 Celsius Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 10.73W - - 0 0 0 0 0 0 1 + 7.69W - - 1 1 1 1 0 0 2 + 6.18W - - 2 2 2 2 0 0 3 - 0.0490W - - 3 3 3 3 2000 2000 4 - 0.0018W - - 4 4 4 4 25000 25000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 2 1 - 4096 0 1 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature: 45 Celsius Available Spare: 100% Available Spare Threshold: 5% Percentage Used: 1% Data Units Read: 7,506,169 [3.84 TB] Data Units Written: 18,893,007 [9.67 TB] Host Read Commands: 56,347,067 Host Write Commands: 289,751,028 Controller Busy Time: 583 Power Cycles: 118 Power On Hours: 14,438 Unsafe Shutdowns: 55 Media and Data Integrity Errors: 0 Error Information Log Entries: 271 Warning Comp. Temperature Time: 0 Critical Comp. Temperature Time: 0 Error Information (NVMe Log 0x01, max 63 entries) No Errors Logged