xDmOx

UPDATE 2: Running the following terminal command: xfs_repair -n /dev/sdq Outputs this: Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... .....<> ..... found candidate secondary superblock unable to verify superblock continuing... .....<> ..... It just keeps going and going.... Stopping it and running: fdisk -l /dev/sdq fdisk -l /dev/sdq Disk /dev/sdq: 238.47 GiB, 256060514304 bytes, 500118192 sectors Disk model: LITEONIT LMT-256 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Not sure what to do now as this looks like there is no partition table here... hmmm When I try and mount the cache drive - I get his error: /dev# mount dev/sdq /mnt/tmp mount: /mnt/tmp: special device dev/sdq does not exist. dmesg(1) may have more information after failed mount system call.

UPDATE: I found for following when reviewing the SYSLOG Nov 29 20:16:05 ServerName emhttpd: mounting /mnt/cache Nov 29 20:16:05 ServerName emhttpd: shcmd (200): mkdir -p /mnt/cache Nov 29 20:16:05 ServerName emhttpd: shcmd (201): mount -t xfs -o noatime,nouuid /dev/sdq1 /mnt/cache Nov 29 20:16:05 ServerName kernel: /dev/sdq1: Can't open blockdev Nov 29 20:16:05 ServerName root: mount: /mnt/cache: special device /dev/sdq1 does not exist. Nov 29 20:16:05 ServerName root: dmesg(1) may have more information after failed mount system call. Nov 29 20:16:05 ServerName emhttpd: shcmd (201): exit status: 32 Nov 29 20:16:05 ServerName emhttpd: /mnt/cache mount error: Unsupported or no file system running dmesg - I see this jump out at me: /dev/sdq1: Can't open blockdev [ 3279.911117] mdcmd (36): nocheck cancel

Hey gang - Happy Holidays! My Cache SSD drive just popped this error and it persists after a reboot and shutdown - "UNMOUNTABLE - UNSUPPORTED OR NO FILESYSTEM" -SMART check comes back OK with no issues -In Maintenance Mode - I'm unable to run XFS-Repair under the Cache Settings tab for the drive (see error below) /dev/sdq1: No such file or directory fatal error -- couldn't initialize XFS library - Looking at the bottom of the syslog.txt - I see this error Nov 29 20:38:32 ServerName ool www[5102]: /usr/local/emhttp/plugins/dynamix/scripts/xfs_check 'start' '/dev/sdq1' 'LITEONIT_LMT-256L9M-11_MSATA_256GB_TW0N42H7550854713641' '-n' Nov 29 20:40:44 ServerName kernel: /dev/sdq1: Can't open blockdev Please help and thank you! origaminet-diagnostics-20231129-2051.zip

Self Resolved Issue: Looking at the TMM logs, I was getting a Java Heap OutofMemory error due to the large size of my library Fix Guide: https://gitlab.com/tinyMediaManager/tinyMediaManager/-/issues/1912 Additional Important Info: Changing the allocated memory from 512MB to 8192MB resolved the issue along with this info below. DO NOT use TextEdit in MacOS to create the launcher-extra.yml file. Even if you correct the file extension it creates hidden garbage text at the beginning of the file that makes it unreadable to TMM upon launching the application - thus it creates a new default file and ignoring yours and keeps re-launching / crashing I used Microsoft Visual Studio Code to generate a clean launcher-extra.yml file and everything was fixed from there. Hope this helps some one else down the road.

Still not working with the extra memory file in place. Same error.

Might have found a solution for my own error - looks like a Java Heap Out of Memory error: https://www.tinymediamanager.org/help/faq#java-heap-space-errors

The new 4.3.9 update applied successfully, but now I can't get tinymediamanager to load. It's just sitting there stuck on the loading UI screen. Is it possible to rollback the version to 4.3.8.2 until this is resolved? Here is the error message from the logs: Xvnc TigerVNC 1.11.0 - built 2022-01-26 17:59 Copyright (C) 1999-2020 TigerVNC Team and many others (see README.rst) See https://www.tigervnc.org for information on TigerVNC. Underlying X server release 12011000, The X.Org Foundation Sun Mar 19 13:47:59 2023 vncext: VNC extension running! vncext: Listening for VNC connections on all interface(s), port 5900 vncext: created VNC server for screen 0 Listening on http://:4000 Openbox-Message: Unable to find a valid menu file "/var/lib/openbox/debian-menu.xml" : not foundenbox/autostart: 1: tint2: Using glib slice allocator (default). Run tint2 with environment variable G_SLICE=always-malloc in case of strange behavior or crashes tint2: xRandr: Found crtc's: 1 tint2: xRandr: Linking output VNC-0 with crtc 0, resolution 1024x768, DPI 96 tint2: No XSETTINGS manager, tint2 uses config option 'launcher_icon_theme'. tint2: Loading config file: /app/.config/tint2/tint2rc tint2: real transparency off.... depth: 24 tint2: panel items: T tint2: nb monitors 1, nb monitors used 1, nb desktops 4 tint2: panel 1 uses scale 1 ERROR: openbox-xdg-autostart requires PyXDG to be installed tint2: pixmap background detection failed tint2: Kernel uevent interface initialized... tint2: pixmap background detection failed Connections: accepted: 127.0.0.1::37780 SConnection: Client needs protocol version 3.8 SConnection: Client requests security type VncAuth(2) 2023-03-19 13:48:00,764 INFO success: x11 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-03-19 13:48:00,764 INFO success: x11 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-03-19 13:48:00,764 INFO success: app entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-03-19 13:48:00,764 INFO success: app entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-03-19 13:48:00,764 INFO success: easy-novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-03-19 13:48:00,764 INFO success: easy-novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-03-19 13:48:00,765 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2023-03-19 13:48:00,765 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) Sun Mar 19 13:48:02 2023 VNCSConnST: Server default pixel format depth 24 (32bpp) little-endian rgb888 VNCSConnST: Client pixel format depth 24 (32bpp) little-endian rgb888 ComparingUpdateTracker: 0 pixels in / 0 pixels out ComparingUpdateTracker: (1:-nan ratio) /build/tint2-gOW2dq/tint2-16.7/src/util/signals.c 161: triggering tint2 restart, reason: configuration change in the root window tint2: /build/tint2-gOW2dq/tint2-16.7/src/main.c 782: restarting tint2... tint2: xRandr: Found crtc's: 1 tint2: xRandr: Linking output VNC-0 with crtc 0, resolution 3440x1222, DPI 96 tint2: No XSETTINGS manager, tint2 uses config option 'launcher_icon_theme'. tint2: Loading config file: /app/.config/tint2/tint2rc tint2: real transparency off.... depth: 24 tint2: panel items: T tint2: nb monitors 1, nb monitors used 1, nb desktops 4 tint2: panel 1 uses scale 1 tint2: pixmap background detection failed tint2: Kernel uevent interface initialized... tint2: pixmap background detection failed Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Timer-4" Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Timer-5" Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "TimerQueue" Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Timer-10" Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Timer-3" Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "idle-timeout-task" Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Timer-9" Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Timer-8" Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Timer-2" Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Timer-6" Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Timer-7" Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Timer-1" Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "main" Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "AWT-Shutdown" Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "process reaper" Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "ForkJoinPool.commonPool-worker-14"

Same here! The ITE-IT87 Driver install fixed my fan detection for my motherboard: Gigabyte X99P-SLI-CF. Many thanks for the Developer - XOXO!

That is a valid point. Hmmm. If anything - Maybe I'll replace the fans on the existing ones I have to improve cooling, noise levels, and get a new fan in there.

Thanks for the feedback @Whaler_99 and @kizer! Such a tricky situation. I love my 5-in-3 Icy Docks with trays, but wanted to try something new. The loose fit with the hard drives in trayless cages seem to be the common complaint and drive vibration being a concern. Hmmm. Such a tough call before grabbing 4 for a new case build out.

Has anyone tried the newer iStar ISTAR BPN-DE350HD 5-in-3 cages yet? I'm curious on the build quality and if the fans needs to be replaced. Appreciate any feedback before buying 4 of these. I've been using Icy Dock for YEARS now, but wanted to try something new (more silent, better cooling, etc.)

Spotted this Antec 1200 (Refurbished) - I can't vouch for the vendor: https://www.priceblaze.com/CAP1200V3-Antec-Power-Supply?ref=gshp I was interested in an Antec 1200 myself, but it's just way too heavy of a case for me. Good luck!

Many thanks for the information @BlinkerFluidand @ChatNoir!

Hello fellow Data Horders! I had a question about Server Rack Mounts as I'm looking at building out a new setup for my UnRAID server and have been looking at these 24 hard drive bay cases like as seen here: https://www.amazon.com/Norco-Mount-Hot-Swappable-Server-RPC-4224/dp/B00BQY3916 Questions: 1.) Is it possible to have multiple Server Rack Mounts connected to a single instance of UnRAID? I know there is currently a 30 drive limited under the Pro license, but I'm thinking for down the road should this limit be increased. 2.) If it is possible to connect multiple racks, how would this be accomplished? 3.) Any recommended brands for a 24-bay hard drive Server Rack mount case? 4.) Any other gotchas I should be aware of from switching from a mid tower case to a server rack mount setup? Thank you for any assistance you can provide! Cheers!

Hello @paloooz! Some quick questions - I'm looking at doing a rebuild of my server for increased hard drive storage and was curious what the drive capacity of yours is. Also, are you using hard drive cages? What's holding your hard drives in this setup! Thank you for any info you can provide! Cheers! UPDATE: I may have answered my own question looking at these: https://www.amazon.com/Rosewill-Rackmount-Computer-Pre-Installed-RSV-R4000/dp/B00N9CXGSO?th=1

So you can't have spaces in the path name? That makes no sense at all since all my other Dockers have no issues with spaces. I've been at this for hours and stuck with this error message: Warning: SimpleXMLElement::addChild(): unterminated entity reference Comics =/= eComics =/ in /usr/local/emhttp/plugins/dynamix.docker.manager/include/CreateDocker.php on line 211 Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="ubooquity" --net="bridge" -e TZ="America/Los_Angeles" -e HOST_OS="unRAID" -e "MAXMEM"="512" -e "PUID"="99" -e "PGID"="100" -p 2202:2202/tcp -p 2203:2203/tcp -v "":"/books":ro -v "":"/comics":ro -v "/mnt/user/appdata/ubooquity":"/config":rw linuxserver/ubooquity /usr/bin/docker: Error response from daemon: Invalid volume spec ":/comics:ro": Invalid volume specification: ':/comics:ro'. See '/usr/bin/docker run --help'. The command failed.

This plugin saved my ass!!! THANK YOU! THANK YOU! OMG THANK YOU!!!!