zaker

Members
  • Posts

    37
  • Joined

  • Last visited

Retained

  • Member Title
    ZB

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

zaker's Achievements

Rookie

Rookie (2/14)

5

Reputation

1

Community Answers

  1. @JorgeB thanks. I knew it was sdd. sdd is my backup disk for my docker storage as well as crucial things on my unraid array should I manage to destroy it. I will indeed try a cable swap, although curiously it's been content since I powered it back on... Thanks for your nod to cables.
  2. I've been seeing issues with my setup. I'm thinking maybe my PSU is on its way out. Or possibly my battery backup. I attempted to grab it via syslog but that has been pretty fruitless so far. However, something strange...See the attached image of the boot messages sent to the monitor about the SATA devices. It seemed to struggle to get one to talk correctly. Eventually the thing booted and it reads fine atm. Thinking (hoping) a bad cable, SMART seems okay, but...anyone seen this before with some insight? Also sending diagnostics, just cause. backup-diagnostics-20231117-1805.zip
  3. manual update and error check on usb stick seems to have solved issues.
  4. I found the manual upgrade/downgrade procedure, I'll give that a go for 6.12.1 and see if it gets unstuck, otherwise I'll attempt a 6.11.something I guess.
  5. Like a hasty fool, I didn't notice I was getting a 6.x.0 release until it was too late, and I guess I'm paying the price. looking for help - guessing either a link to the manual upgrade process to get 6.12.1, or a specific pointer to the issue. I shut things down to troubleshoot local routing concerns, and it doesn't come back up now (no gui). Something goofed in the startup scripts, or so it appears. Here's the boot output: Updating hardware database index: /sbin/udevadm hudb --update Triggering udeu events: /bin/udevadm trigger --action=change Starting system message bus: rusr/bin/dbus-uuidgen --ensure : /usr/bit Starting elogind: /lib64/elogind/elogind --daemon Starting Internet super-server daemon: /usr/sin/inetd Starting OpenSSH SSH daemon: /usr/sbin/sshd Starting NTP daemon: rusr/sbin/ntpd -g -u ntp:ntp Starting ACPI daemon: rusr/sbin/acpid Enabled CPU frequency scaling governor: ondemand Updating MIME database: rusr/bin/update-mime-database /usr/share/mime Updating gdk-pixbuf. loaders: rusr/bin/update-gdk-pixbuf-loaders & Compiling Settings XML schema files: rusr/bin/glib-compile-schemas rusr/share/glib-2.0/schemas & Starting crond: /usr/sbin/crond Starting atd: /usr/sbin/atd -b 15 -1 1 nu: cannot stat rusr/local/bin/mover': No such file or directory sh: line 6: Device: command not found sh: line 7: Serial: command not found sh: line 8: LU: conmand not found sh: line 9: Firmware: command not found sh: line 10: User: conmand not found sh: line 11: Sector: command not found sh: line 12: Rotation: command not found sh: line 13: Form: command not found sh: line 14: Device: command not found sh: line 15: ATA: command not found sh: -c: line 16: syntax error near unexpected token '(' sh: -c: line 16: 'SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/S)' sh: line 6: Device: command not found sh: line ?: Serial: command not found sh: line 8: LU: command not found sh: line 9: Firmware: command not found sh: line 10: User: command not found sh: line 11: Sector: command not found sh: line 12: Rotation: command not found sh: line 13: Form: command not found sh: line 14: Device: command not found sh: line 15: ATA: command not found sh: -c: line 16: syntax error near unexpected token "(* sh: -c: line 16: "SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/S)* error: failed to connect to the hypervisor error: Operation not supported: Cannot use direct socket mode if no URI is se unRAID Server OS version: 6.12.0 Pu address: 192.168.1.50 1Pub address: not set backup login:
  6. First time seeing this warning. The machine is 4 years old now, the processor (Ryzen 3700x) is not as old though as the original was replaced under warranty just shy of 3 years when one of the memory controller's channels died.
  7. So says fix common problems plugin, but the directions to address it are stale. Anyway, herebackup-diagnostics-20230326-2209.zip's my diagnostics. Help appreciated.
  8. I just found this, so, sort of answering my own question here: https://docs.ibracorp.io/docker-compose/docker-compose-for-unraid I also found this, looks very promising: https://dev.to/felizk/remote-deploy-with-docker-compose-to-unraid-1dai
  9. Can anyone summarize what needs to be done to setup and use this, for someone who is familiar with unraid, and its use of docker, but maybe not well versed (yet) with docker compose? This would be super helpful. My case is that I have a docker-compose.yaml for a web app I've written that I'd like to host on my unraid, I don't yet have this plugin installed, and I dont want to go thru the slow process of publishing my work on github, creating an unraid app that gets full (but inadequate) support via the official route.... I wish I could sit here and digest ten long forumn pages, but...that's just not in the cards atm.
  10. I have a 3TB drive that is formatted btrfs TOSHIBA_DT01ACA300_Y5UNPWAGS (sde) dev 1 I mount it and then reboot. I hear the thing should automatically be mounted again. It isn't. I was thinking of moving one of my caches to be an unassigned device rather than a cache pool because I don't need its folders listed as shares. It is simply going to be a backup target exposed to a docker app. Logs are pretty clean. I have the requisite plugins. What am I missing here? backup-diagnostics-20220526-2219.zip
  11. All of a sudden, All Docker Containers show version 'not available'. Log shows this, very frequently: May 25 23:11:21 backup root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token What led to this, probably, was that I copied over the contents of a cache pool (1 3TB drive) to an unassigned 16TB drive, then took the array offline and reassigned the drive in the cache pool to that larger drive. (no I didn't use the user mount). The other thing I did was to set up to encrypt my drives, but then I stopped without actually encrypting anything once I realized that I didn't stand to gain anything assuming nobody has physical access to my box. Diagnostics attached backup-diagnostics-20220525-2316.zip
  12. Sounds like a workaround but not resolution. Did anything else present itself? I have an update ready and am nervous!
  13. I think this has to do with IoMmu https://docs.microsoft.com/en-us/windows-hardware/drivers/display/iommu-model still learning myself...
  14. I also see this very same message, in the very same place, at the end of login, with v6.9.2. Nevertheless I do have a VM that works. Perhaps it is not running optimal, who knows...