casperse

Members
  • Posts

    810
  • Joined

  • Last visited

Everything posted by casperse

  1. Reboot - start - stop - new diag done From live log window:
  2. When doing app data backup to separate file archieves, I cant find the USB flash backup anymore? Is this only included if I create one big archieve file?
  3. I really dont know what to do now? The server is running but I cant update any plugins see error message: The server is online and Unraid connect is working!? The old link from My servers" to the USB flash backup is gone? and I am afraid that the current backup is of the one that isnt working? (Is there more than 1 usb flash backup in the cloud?) The roollback dosent work.... Should I dismantle my server take out the USB and overwrite the files from a downloaded version of the older one? (This would be a pain, can I overwrite my usb while its running?) It seems like this upgrade and my attempts to rollback have put me in a bad situation, not sure the right way forward. Very old USB backup locally, and the cloud version (Cant find a way to download it, and it might be the one I am running with)
  4. Also I cant download my USB flash copy no button or link?
  5. OK I am seeing many issues - never seen anything like this before upgrade and roollback always? The notification messages is running in a loop (Even in private browser mode no cache)? Goes on forever - even acknowledge all messages have no effect Also I can install the folderview plugin again? And my other plugin for my drives is now showing wrong disc placement, and I cant update them? UPDATE I cant update any plugins anymore? (Internet is working fine and dockers are running) Can I do a manuall rollback with no physicall access to the USB? Rebooting the server have no affect?
  6. UPDATE: My folder plugin is gone and all the settings with it (Took Hous to set this up 😞 ) But other new plugin was not removed like the Plex monitor? Could this be the cause of the roollback failure?
  7. My server was unresponsive and I wanted to roollback to 6.12.3 but for some reason this dosent work? I have tried multiple times staring the server and doing roollback and reboot but it keeps me on 6.12.4 Logfile attached.
  8. Hi All I did my last upgrade through Unraid connect, this was great! because the server was in a different location. And I could login and start my array (Encrypted). Today I tried this again, and for some reason I cant connect to the server anymore? I did read the release notes and my LAN config is standard bridge with eth0 no special changes Just wanted to hear if anyone else experienced the same? Contemplating to cut the power (remotely) for a reboot 🙂 Cheers
  9. But is the DDR5 "real" ECC? my old ECC RAM for my Xeon CPU is listed as: Would these new DDR5 be same level of ECC RAM as the old orig. ones? Sorry my reason for asking is that I read somewhere that the level of ECC validation was different? Shouldn't it be multi-bit?
  10. NO recommendation on ECC RAM for the new 13Th Generation CPU's?
  11. Hi All I am looking into upgrading my UNRAID server but I cant really find out if the RAM I find is "True" ECC like the one I have in my current Intel’s Xeon E-2176G build? So far I have found the new 96G modules: Corsair Vengeance DDR5-5600 BK C40 DC - 96GB x 2 = 192G https://www.proshop.dk/RAM/Corsair-Vengeance-DDR5-5600-BK-C40-DC-96GB/3143077 OR Kingston FURY Beast - DDR5 - sæt - 64 GB: 2 x 32 GB - DIMM 288-PIN - 5200 MHz / PC5-41600 - CL38 - 1.25 V - ikke bufferet - on-die ECC https://www.computersalg.dk/i/8080944/kingston-fury-beast-ddr5-sæt-64-gb-2-x-32-gb-dimm-288-pin-5200-mhz-pc5-41600-cl38-1-25-v-ikke-bufferet-on-die-ecc?utm_source=pricerunner&utm_medium=911-it-elektronik-komponenter-ram&utm_campaign=kingston-technology&utm_content=0 I would appreciate any recommendation on what RAM to get? (ECC minimum 128G in 4 modules) As always thanks for your input the constructive feedback is the best about running UNRAID 🙂
  12. THANKS! @itimpi I think that I got e-mails bedfore when there was a new build released from Unraid? Anyway thanks for the heads-up! I will update it right away! As my header in this post says I also thought it was related to the latest Unraid build, never seen this before 🙂
  13. Hi All I had to cut the power yesterday, and now again I cant stop my server keep getting the: Jul 28 18:53:57 PLEXZONE emhttpd: shcmd (71069): umount /mnt/cache_appdata Jul 28 18:53:57 PLEXZONE root: umount: /mnt/cache_appdata: target is busy. Jul 28 18:53:57 PLEXZONE emhttpd: shcmd (71069): exit status: 32 Jul 28 18:53:57 PLEXZONE emhttpd: Retry unmounting disk share(s)... Jul 28 18:54:02 PLEXZONE emhttpd: Unmounting disks... Jul 28 18:54:02 PLEXZONE emhttpd: shcmd (71070): umount /mnt/cache_appdata Jul 28 18:54:02 PLEXZONE root: umount: /mnt/cache_appdata: target is busy. Jul 28 18:54:02 PLEXZONE emhttpd: shcmd (71070): exit status: 32 Jul 28 18:54:02 PLEXZONE emhttpd: Retry unmounting disk share(s)... Jul 28 18:54:07 PLEXZONE emhttpd: Unmounting disks... Jul 28 18:54:07 PLEXZONE emhttpd: shcmd (71071): umount /mnt/cache_appdata Jul 28 18:54:07 PLEXZONE root: umount: /mnt/cache_appdata: target is busy. Jul 28 18:54:07 PLEXZONE emhttpd: shcmd (71071): exit status: 32 Jul 28 18:54:07 PLEXZONE emhttpd: Retry unmounting disk share(s)... Jul 28 18:54:12 PLEXZONE emhttpd: Unmounting disks... Jul 28 18:54:12 PLEXZONE emhttpd: shcmd (71072): umount /mnt/cache_appdata Jul 28 18:54:12 PLEXZONE root: umount: /mnt/cache_appdata: target is busy. Jul 28 18:54:12 PLEXZONE emhttpd: shcmd (71072): exit status: 32 Jul 28 18:54:12 PLEXZONE emhttpd: Retry unmounting disk share(s)... Jul 28 18:54:17 PLEXZONE emhttpd: Unmounting disks... Jul 28 18:54:17 PLEXZONE emhttpd: shcmd (71073): umount /mnt/cache_appdata Jul 28 18:54:17 PLEXZONE root: umount: /mnt/cache_appdata: target is busy. Jul 28 18:54:17 PLEXZONE emhttpd: shcmd (71073): exit status: 32 Jul 28 18:54:17 PLEXZONE emhttpd: Retry unmounting disk share(s)... I did a Diagnostic file attached below, hope some one can help me? VM and dockers are stopped! I finally got it stopped using: umount -l /dev/loop2 But I would like to know the cause of this 🙂 plexzone-diagnostics-20230728-1855.zip
  14. For anyone who found this topic. I ended up configuring the UDM pro with WAN1 + WAN2 works great!
  15. Did you ever get a working solution? I have the same setup, 2 routers and same subnet with one router as DHCP for both. I then did two gateways one for each internet 192.168.0.1 (Master DHCP) and the other 192.168.0.2
  16. That's a valid point (According to the vendor it should support a normal PSU (Replacing the dual server PSU's) but not sure this is the case (They have been wrong before)
  17. Can someone please help me find the reason for why I keep getting the Out of memory? Do I need to do a reboot every time I get this or can I ignore it?
  18. Sure Thing! (I just believe its the same as the first one I posted?) diagnostics-20230626-2016.zip Got out of memory (64G ECC) I did another reboot and stopped different Dockers to see if that would help. But my Cache didnt return to normal size, anyway to find out what docker app filled up my cache drive? (I would really like to get that space back again) UPDATE: I had a full backup of my "appdata share" and after comparing all subfolders in size with the existing one. I found 414G of *.err data files under the maria db for nextcloud folder in the appdata , I used krusader to delete them all and re-start nextcloud. This solved the cache drive full issue for me. I have also stopped my paperless docker and some other ones and so far the memory is okay, and haven't seen any "memory full yet"? But its like stumbling in the dark.
  19. Sorry no it was less than 24 hours and now I get the "SIGKILL" again in the logs? CPU:
  20. I have TDAR installed but it has not ben running for a very long time (I like Unmanic better) I did think it was my Plex server but restarting it does nothing? I just did a reboot and everything runs great again! (Guess I have around 4 days before it starts again? 🙂 ) One Tell sign was starting to get warnings about my cache drive running full - log files but I dont know what is causing it? Everything worked fine on older releases, so something have changed? SIGKILL?
  21. I seem to have something like this also on 6.12.1 any idea on what to do?