Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

NorseRider

Members
  • Joined

  • Last visited

Everything posted by NorseRider

  1. Think its only new installs that are broken, the gui is a little off, the drop down to select themes are blank, and bing has moved their service to azure so not sure that works any longer, mapquest and google both want you to enter payment option but gives enough free credits that only a few geo request should be free.
  2. Dynamix Day Night seems to be broken. I fixed it by manually editing /boot/config/plugins/dynamix.day.night/dynamix.day.night.cfg with; lat="32.71533" lng="-117.15726" day="white" night="black" Anyone got a better fix maybe?
  3. I got the PermissionError: [Errno 13] Permission denied: '/home/libretranslate/.local/share' error after upgrading too. "chown -R 1032:1032 /mnt/user/appdata/libretranslate" solved it for me.
  4. Recreated the docker.img file on my apps pool instead. Previous apps made it a breeze to reinstall my docker apps. Thank you so much for your help Trurl, really appreciate it.
  5. Thank you so much for your reply. I will recreate and reinstall. What are the best settings for primary and secondary storage for system and domain? Should those shares be cache only? Thank you.
  6. This is my settings for system share, guessing i miss configured something there?]
  7. Not sure if there are still files on the array or not, maybe only folders as files show cache only.
  8. Disabled those settings and ran mover. Docker still won't start. Thank you so much for helping out. nassie-diagnostics-20250225-2031.zip
  9. Hi Trurl, Thank you for your reply, I really appreciate it. I have some Ollama and other AI containers that take a lot of space. Is there a better way to do it? Should I make the system share as dedicated as I did with appdata?
  10. Hi, I just upgraded to 7.0.1 and got this error. I updated to 7.0.0 a couple of weeks a go without any issue. I've tried downgrading to 7.0.0 again but docker still didn't want to start so upgraded to 7.0.1 again to fix forward. Not sure how to troubleshoot this, any help is appreciated. Feb 25 18:24:02 Nassie avahi-daemon[2113]: Got SIGHUP, reloading. Feb 25 18:24:02 Nassie unassigned.devices: Updating share settings... Feb 25 18:24:02 Nassie unassigned.devices: Share settings updated. Feb 25 18:24:03 Nassie emhttpd: shcmd (337): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 100 Feb 25 18:24:03 Nassie kernel: loop2: detected capacity change from 0 to 209715200 Feb 25 18:24:03 Nassie kernel: BTRFS: device fsid 78bb5bf8-dda0-4f88-bd7d-1bb567fafd86 devid 1 transid 973979 /dev/loop2 scanned by udevd (15759) Feb 25 18:24:03 Nassie kernel: BTRFS info (device loop2): first mount of filesystem 78bb5bf8-dda0-4f88-bd7d-1bb567fafd86 Feb 25 18:24:03 Nassie kernel: BTRFS info (device loop2): using crc32c (crc32c-intel) checksum algorithm Feb 25 18:24:03 Nassie kernel: BTRFS info (device loop2): using free space tree Feb 25 18:24:03 Nassie kernel: BTRFS error (device loop2): level verify failed on logical 14558167040 mirror 1 wanted 2 found 0 Feb 25 18:24:03 Nassie kernel: BTRFS error (device loop2): level verify failed on logical 14558167040 mirror 2 wanted 2 found 0 Feb 25 18:24:03 Nassie kernel: BTRFS error (device loop2): failed to load root extent Feb 25 18:24:03 Nassie kernel: BTRFS error (device loop2): open_ctree failed: -5 Feb 25 18:24:03 Nassie root: mount: /var/lib/docker: can't read superblock on /dev/loop2. Feb 25 18:24:03 Nassie root: dmesg(1) may have more information after failed mount system call. Feb 25 18:24:03 Nassie root: mount error nassie-diagnostics-20250225-1837.zip
  11. The disk3 that is missing now was previously in this enclosure. I put back in the enclosure when I ran out of space and restarted unbalance and about 5TB was written to it. I am going to try and re seat it and see if it comes back. I will update this post as I go. Thank you guys for all the help so far.
  12. Thank you very much trurl andJorgeB! I did New config with preserve all and the disks turned blue and I was able to start the array and most of the data is restored, but disk 3, the last disk added, is showing "unmountable unsupported or no file system". Should i 1. remove the disk from the array and do new config with only the 2 good drives, mount the last disk with unassigned devices and see if i can copy the data off the drive or 2. restart the array in maint mode and try xfs_repair? If xfs_repair would it be xfs_repair -v /dev/md3p1 nassie-diagnostics-20230828-1404.zip
  13. Hi trurl, Thank you for your reply. I was also confused why it would say emulated when I don't have a parity drive. New config should have "Preserve current assignments - ALL"? Long term goal is to build a new proper server and not use USB drives. I will skip parity until i build a real server.
  14. Hi guys, relatively new to Unraid but long time linux user. My server is an intel nuc and only 1 18TB usb drive in the array. I wanted to expand the storage so added another 18TB drive, this time in a mediasonic 4 bay usb enclosure. My thinking was to use unbalance to move the data from the usb drive to the new drive. I do use hardlinks so I did add the H flag to unbalance to preserve hardlinks but drive was close to full so ran out of space. So I added another 18TB drive to the mediasonic enclosure and started unbalance again. unbalance reported it finished the move over night. Next morning the last drive added is showing Device is disabled, contents emulated. I have reseated the drive with no luck. Currently the array says "Too many wrong and/or missing disks!" Attached are diagnostics from right after it happened, before reboot. Second diagnostic is from now. Running unraid Version: 6.12.3 I do not have a parity drive. The last 18TB drive was supposed to become the parity drive once data was moved correctly. Thanks in advance. nassie-diagnostics-20230828-0043.zip nassie-diagnostics-20230828-1140.zip

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.