PhantamaroK

Members
  • Posts

    12
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

PhantamaroK's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I am using the X399 motherboard, and have updated to the latest BIOS. I have also disabled ASPM in the BIOS, and also added pci=nommconf to syslinux. I am still receiving these errors every second. Does anyone have any other ideas?
  2. I'm dealing with a new issue where every 8-24 hours my server just reboots. I mirrored the syslog to flash to help diagnose this, and have attached that syslog file along with the diagnostics file. But I don't really know what I'm looking at. Can anyone please help me out? 🙏 syslog diagnostics-20190330-1857.zip
  3. Initially, I tried through the webui. Afterward, it shows the attached message. The update does not work and the server goes into maintenance mode. Then I tried updating via the occ, and it showed the error in my initial post.
  4. I too ran into the recent issue where the Docker update outpaced the Nextcloud installation. However, I'm having a very difficult time upgrading from version 13 to version 14. I keep running into this error: Remove potentially over exposing share links Done 0/0 [>---------------------------] 0% An unhandled exception has been thrown: Error: Call to a member function getUsers() on null in /config/www/nextcloud/lib/private/Repair/RemoveLinkShares.php:218 Stack trace: #0 /config/www/nextcloud/lib/private/Repair/RemoveLinkShares.php(230): OC\Repair\RemoveLinkShares->repair(Object(OC\Repair)) #1 /config/www/nextcloud/lib/private/Repair.php(91): OC\Repair\RemoveLinkShares->run(Object(OC\Repair)) #2 /config/www/nextcloud/lib/private/Updater.php(265): OC\Repair->run() #3 /config/www/nextcloud/lib/private/Updater.php(121): OC\Updater->doUpgrade('14.0.12.0', '13.0.0.14') #4 /config/www/nextcloud/core/Command/Upgrade.php(258): OC\Updater->upgrade() #5 /config/www/nextcloud/3rdparty/symfony/console/Command/Command.php(251): OC\Core\Command\Upgrade->execute(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #6 /config/www/nextcloud/3rdparty/symfony/console/Application.php(946): Symfony\Component\Console\Command\Command->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #7 /config/www/nextcloud/3rdparty/symfony/console/Application.php(248): Symfony\Component\Console\Application->doRunCommand(Object(OC\Core\Command\Upgrade), Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #8 /config/www/nextcloud/3rdparty/symfony/console/Application.php(148): Symfony\Component\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #9 /config/www/nextcloud/lib/private/Console/Application.php(213): Symfony\Component\Console\Application->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput)) #10 /config/www/nextcloud/console.php(96): OC\Console\Application->run() #11 /config/www/nextcloud/occ(11): require_once('/config/www/nex...') Can anyone please help?
  5. I caught an error I made. As noted, I should have used: btrfs restore -vi /dev/mapper/nvme1n1p1 /mnt/user/recovery/ It now seems to be copying files!
  6. Thank you for your help. When I try: mount -t btrfs -o recovery,ro /dev/mapper/nvme1n1p1 /mnt/recovery/ I get: wrong fs type, bad option, bad superblock on /dev/mapper/nvme1n1p1, missing codepage or helper program, or other error. And when I try: btrfs restore -v /dev/nvme1n1p1 /mnt/user/recovery/ I get: No valid Btrfs found on /dev/nvme1n1p1 Could not open root, trying backup super No valid Btrfs found on /dev/nvme1n1p1 Could not open root, trying backup super No valid Btrfs found on /dev/nvme1n1p1 Could not open root, trying backup super Do you have any ideas on how to proceed? I feel like I might still have a command wrong.
  7. Many months ago, I had a power outage in my home, and when my server boot back up, its SSD cache was unmountable. I found out that Btrfs is very sensitive to sudden power outages, and got a second NVMe drive to add to the cache pool for redundancy. Losing the appdata folder really hurt, and I had to remake most of my Docker containers from scratch. Now, the same thing has happened again (power outage), and neither of the NVMe SSDs are mountable. I have scoured the forums, and all advice seemed to point here. I have followed all of those steps, and at each step, I see a message something to the effect of "no Btrfs filesystem found." Both drives were encrypted (via Cache Settings), which I assume interferes with the data recovery. Can any kind soul give me some guidance? I'm trying to do a restore from a cloud backup, but it's months old, is taking forever, and may ultimately fail. I would be beyond grateful if I could recover that appdata folder from either of my 2 drives (which should each have the data). I have not at any point reformatted the drives.
  8. I read through these posts and also checked other threads, and am unable to find reference to an issue I'm experiencing since the upgrade. I'm very glad that CPU pinning got some spotlight (I had used it before), but with one Docker in particular (SABnzbd), I am unable to remove "cpuset-cpus" from the extra parameters. Whether I change that parameter or erase it, it remains the same when the Docker or the server is restarted. And I keep getting warnings about having pinned CPUs defined twice. Can anyone point me in the right direction?
  9. I am using Piwigo with the videojs plugin. Some of its features require ffmpeg and mediainfo. How can I install these utilities on the Docker container, so that I may fully utilize this plugin? UPDATE: I think I sort of solved it. I SSHed into the server, then into the docker with: docker exec -it piwigo /bin/bash I installed the packages using apk: apk add ffmpeg apk add mediainfo It seems kinda dirty, but it works for now. I'm certainly interested in hearing best practices for this sort of thing.
  10. Did you ever find a solution to this?