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.

FrontierGamers

Members
  • Joined

  • Last visited

  1. I am trying to create a new cache pool formatted with btrfs. When I try to format the drives after starting the array, it doesn't work. Checking unRAID logs shows this: Mar 23 17:40:12 Tower kernel: mdcmd (44): nocheck pause Mar 23 17:40:12 Tower kernel: md: recovery thread: exit status: -4 Mar 23 17:40:13 Tower emhttpd: creating volume: newcache (btrfs) Mar 23 17:40:13 Tower emhttpd: writing MBR on device (nvme3n1) with partition 1 offset 2048 Mar 23 17:40:13 Tower emhttpd: shcmd (572798): sfdisk --quiet --label dos /dev/nvme3n1 <<< 'start=2048' Mar 23 17:40:13 Tower kernel: nvme3n1: p1 Mar 23 17:40:13 Tower kernel: nvme3n1: p1 Mar 23 17:40:13 Tower emhttpd: shcmd (572799): udevadm settle Mar 23 17:40:13 Tower emhttpd: shcmd (572800): /sbin/wipefs -af --lock /dev/nvme3n1p1 Mar 23 17:40:13 Tower root: wipefs: error: /dev/nvme3n1p1: probing initialization failed: No such device or address Mar 23 17:40:13 Tower emhttpd: shcmd (572800): exit status: 1 Mar 23 17:40:13 Tower emhttpd: shcmd (572801): /sbin/blkdiscard /dev/nvme3n1p1 Mar 23 17:40:13 Tower root: blkdiscard: cannot open /dev/nvme3n1p1: No such device or address Mar 23 17:40:13 Tower emhttpd: shcmd (572801): exit status: 1 Mar 23 17:40:13 Tower emhttpd: writing MBR on device (nvme0n1) with partition 1 offset 2048 Mar 23 17:40:13 Tower emhttpd: shcmd (572802): sfdisk --quiet --label dos /dev/nvme0n1 <<< 'start=2048' Mar 23 17:40:13 Tower kernel: nvme0n1: p1 Mar 23 17:40:13 Tower kernel: nvme0n1: p1 Mar 23 17:40:13 Tower emhttpd: shcmd (572803): udevadm settle Mar 23 17:40:13 Tower emhttpd: shcmd (572804): /sbin/wipefs -af --lock /dev/nvme0n1p1 Mar 23 17:40:13 Tower root: wipefs: error: /dev/nvme0n1p1: probing initialization failed: No such device or address Mar 23 17:40:13 Tower emhttpd: shcmd (572804): exit status: 1 Mar 23 17:40:13 Tower emhttpd: shcmd (572805): /sbin/blkdiscard /dev/nvme0n1p1 Mar 23 17:40:13 Tower root: blkdiscard: cannot open /dev/nvme0n1p1: No such device or address Mar 23 17:40:13 Tower emhttpd: shcmd (572805): exit status: 1 Mar 23 17:40:13 Tower emhttpd: /sbin/mkfs.btrfs -K -f -d raid1 -m raid1 /dev/nvme3n1p1 /dev/nvme0n1p1 Mar 23 17:40:13 Tower emhttpd: btrfs-progs v6.17 Mar 23 17:40:13 Tower emhttpd: See https://btrfs.readthedocs.io for more information. Mar 23 17:40:13 Tower emhttpd: mounting /mnt/newcache Mar 23 17:40:13 Tower emhttpd: shcmd (572806): mkdir -m 0666 -p /mnt/newcache Mar 23 17:40:13 Tower emhttpd: newcache: no pool uuid Mar 23 17:40:13 Tower emhttpd: shcmd (572807): rmdir /mnt/newcache Mar 23 17:40:13 Tower emhttpd: newcache: mount error: wrong or no file system Mar 23 17:40:14 Tower emhttpd: Restarting services... Mar 23 17:40:15 Tower emhttpd: shcmd (572810): /etc/rc.d/rc.samba reload Mar 23 17:40:15 Tower emhttpd: shcmd (572814): /etc/rc.d/rc.avahidaemon reload Mar 23 17:40:15 Tower avahi-daemon[2571]: Got SIGHUP, reloading. Mar 23 17:40:15 Tower kernel: mdcmd (45): check resume Mar 23 17:40:15 Tower kernel: md: recovery thread: recon P ...
  2. If you want to enable NVIDIA devices, make sure to add the environment variable: "NVIDIA_VISIBLE_DEVICES" and set it to "all" along with adding "--runtime=nvidia" as an Extra Parameter
  3. Needed to create a new pool instead of adding to an existing one. 🤦
  4. So, I started the array in maintenance mode and manually mounted my first cache drive in read only. It mounted fine, and all the files seem to be intact. However, restarting still won't mount the drive.
  5. Hello, I recently removed an nvme from my array and then added a new nvme to my cache pool as my second one. I followed the steps from here: https://docs.unraid.net/legacy/FAQ/shrink-array/ I moved the data from my drive 3 to drive 1 & 2, ran new config, turned off the PC, removed drive 3 and added the new nvme drive to the cache pool, rebooted, and started the array. After restarting, the main cache is now not mounting giving an error: Unsupported or no file system. Does anyone have any ideas on what I should do? I don't see how me turning it off, adding a new cache drive, and turning it back on and could make it unmountable... tower-diagnostics-20240302-0100.zip
  6. Adding the server through its IP address fixed the issue
  7. I cannot access the unraid server through my laptop, but I can access it through my phone. I am using WireGuard, and I can access my router through my laptop, but I cannot access the actual Unraid server. Any help?

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.