FAQ for unRAID v6


Recommended Posts

This thread is reserved for Frequently Asked Questions, concerning unRAID as a NAS, its setup, operation, management, and troubleshooting.  Please do not ask for support here, such requests and anything off-topic will be deleted or moved, probably to the FAQ feedback topic.  If you wish to comment on the current FAQ posts, or have suggestions or requests for the FAQ, please put them in the FAQ feedback topic.  Thank you!

 

Index to common questions

  Some are from the wiki FAQ, some from this thread, and some from the LimeTech web site.  There are many more questions with answers on the wiki FAQ.


Getting Started

General Questions

Cache Drive/Pool

Plugins

Maintenance and Troubleshooting

 

 


 

unRAID FAQ's and Guides -

* Guides and Videos - comprehensive collection of all unRAID guides (please let us know if you find one that's missing)

* FAQ for unRAID v6 on the forums, general NAS questions, not for Dockers or VM's

* FAQ for unRAID v6 on the unRAID wiki - it has a tremendous amount of information, questions and answers about unRAID.  It's being updated for v6, but much is still only for v4 and v5.

* Docker FAQ - concerning all things Docker, their setup, operation, management, and troubleshooting

* FAQ for binhex Docker containers - some of the questions and answers are of general interest, not just for binhex containers

* VM FAQ - a FAQ for VM's and all virtualization issues

 

Know of a question that ought to be here?  Please suggest it in the FAQ feedback topic.

 

-------------------------------------------------------

Suggested format for FAQ entries - clearly shape the issue as a question or as a statement of the problem to solve, then fully answer it below, including any appropriate links to related info or videos.  Optionally, set the subject heading to be appropriate, perhaps the question itself.

 

While a moderator could cut and paste a FAQ entry here, only another moderator could edit it.  It's best therefore if only knowledgeable and experienced users create the FAQ posts, so they can be the ones to edit it later, as needed.  Later, the author may want to add new info to the post, or add links to new and helpful info.  And the post may need to be modified if a new unRAID release changes the behavior being discussed.

 

Moderators:  please feel free to edit this post.

  • Like 3
  • Upvote 2
Link to comment

Why am I unable to install plugins?

 

With some user's network setup (ISP, router, etc) you may need to manually set static DNS addresses so that unRaid can communicate with the outside world.

 

Go to Settings, Network Settings and enter in the appropriate addresses (You can always use Google's DNS server addresses which are 8.8.8.8 and 8.8.4.4)

 

In some cases, this may be caused by misconfiguration of your network bonding settings.  You can try deleting /config/network.cfg on the flash drive (to restore default settings), then reboot unRaid and try again

Link to comment

What counts as a drive against my license storage device limit?

 

Everything that is handled by Linux as a storage device (basically everything except for your boot flash drive).  This includes DVD / Bluray drives, card readers, external hard drives and the like.

 

If you exceed your device limit (whether assigned to the array or not), you will either have to remove those devices from your service, or upgrade your license.

 

Note that the Pro versions of unRAID have no device limits and only limit the amount of devices able to be actually assigned to the array.

  • Upvote 1
Link to comment

Why is my cache disk(s) unassigned after a reboot?

 

Some users have this issue when using Chrome to add cache disk(s), single cache disk or one or more disks from a cache pool don't stay assigned after a reboot, use IE or Firefox for this operation, use it for the complete procedure, assign cache disk(s), start array, stop array and reboot, your assignments should stick now.

 

If using a different browser doesn't work, boot unRAID in safe mode, assign your cache devices, start array, stop array and reboot in normal mode, assignments should now stick.

 

 

Edited by johnnie.black
  • Like 1
  • Upvote 3
Link to comment

Can I manually create and use multiple btrfs pools?

 

Multiple cache pools are supported since v6.9, but for some use cases this can still be useful, you can also use multiple btrfs pools with the help of the Unassigned Devices plugin.

 

There are some limitations and most operations creating and maintaining the pool will need to be made using the command line, so if you're not comfortable with that wait for LT to add the feature.

 

If you want to use the now, here's how:

 

-If you don't have yet install the Unassigned Devices plugin.

-Better to start with clean/wiped devices, so wipe them or delete any existing partitions.

-Using UD format the 1st device using btrfs, choose the mount point name and optionally activate auto mount and share

-Using UD mount the 1st device, for this example it will be mounted at /mnt/disks/yourpoolpath

-Using UD format the 2nd device using btrfs, no need to change the mount point name, and leave auto mount and share disable.

-Now on the console/SSH add the device to the pool by typing:

btrfs dev add -f /dev/sdX1 /mnt/disks/yourpoolpath

     Replace X with correct identifier, note the 1 in the end to specify the partition (for NVMe devices add p1, e.g. /dev/nvme0n1p1)

 

-Device will be added and you will see the extra space on the 1st disk free space graph, whole pool will be accessible in the original mount point, in this example:

/mnt/disks/yourpoolpath

-By default the disk is added in single profile mode, i.e., it will extend the existing volume, you can change that to other profiles, like raid0, raid1, etc, e.g., to change to raid1 type:

btrfs balance start -dconvert=raid1 -mconvert=raid1 /mnt/disks/yourpoolpath

     See here for the other available modes.

 

-If you want to add more devices to that pool just repeat the process above

 

Notes

 

-Only mount the first device with UD, all other members will mount together despite nothing being shown on UD's GUI, same to unmount, just unmount the 1st device to unmount the pool.

-It appears that if you mount the pool using the 1st device used/free space are correctly reported by UD, unlike if you mount using e.g. the 2nd device, still for some configurations the space might be incorrectly reported, you can always check it using the command line:

btrfs fi usage /mnt/disks/yourpoolpath

-You can have as many unassigned pools as you want, example how it looks on UD:

 

udpools.thumb.png.3c48824549c282ccf6562716e6736ff9.png

 

sdb+sdc+sdd+sde are part of a raid5 pool, sdf+sdg are part of raid1 pool, sdh+sdi+sdn+sdo+sdp are another raid5 pool, note that UD sorts the devices by identifier (sdX), so if sdp was part of the first pool it would still appear last, UD doesn't reorder the devices based on if they are part of a specific pool.

 

You can also see some of the limitations, i.e., no temperature is shown for the secondary pools members, though you can see temps for all devices on the dashboard page, still it allows to easily use multiple pools until LT adds multiple cache pools to Unraid.

 

Remove a device:

-to remove a device from a pool type (assuming there's enough free space):

btrfs dev del /dev/sdX1 /mnt/disks/yourpoolpath 

     Replace X with correct identifier, note the 1 in the end

 

Note that you can't go below the used profile minimum number of devices, i.e., you can't remove a device from a 2 device raid1 pool, you can convert it to single profile first and then remove the device, to convert to single use:

btrfs balance start -f -dconvert=single -mconvert=single /mnt/disks/yourpoolpath

Then remove the device normally like above.

 

Replace a device:

To replace a device from a pool (if you have enough ports to have both old and new devices connected simultaneously):

 

You need to partition the new device, to do that format it using the UD plugin, you can use any filesystem, then type:

btrfs replace start -f /dev/sdX1 /dev/sdY1 /mnt/disks/yourpoolpath

 

Replace X with source, Y with target, note the 1 in the end of both, you can check replacement progress with:

btrfs replace status /mnt/disks/yourpoolpath

 

If the new device is larger you need to resize it to use all available capacity, you can do that with:

btrfs fi resize X:max /mnt/disks/yourpoolpath

Replace X with the correct devid, you can find that with:

btrfs fi show /mnt/disks/yourpoolpath

 

 

Screenshot 2018-03-18 14.42.51.png

  • Like 6
  • Thanks 1
  • Upvote 3
Link to comment

Why is the webGUI not displaying any of my shares, but I can see them over the network?

 

Some of the commercial / free adblockers for Windows / (Mac?) are incorrectly flagging your unRaid server's GUI as an advertisement.  In your adblocker's settings, there should be an option to "white-list" your server.

  • Upvote 1
Link to comment

What is the Local Master in SMB and does it involve the Internet?

 

 

I answered a query recently and complied a response which is referenced here:

 

The next post suggested that the information be added to the WIKI.  I could see it going into the Networking section (#10) but I am unsure the way to do this.  Do you want to be the one controlling this since you are revising the entire FAQ?  I would be happy to rework this post and make it a bit more general if that would help. 

Edited by Frank1940
updated link
Link to comment
  • 2 weeks later...
  • 2 months later...

How do I add a device to create a redundant pool?

 

 

BTRFS

A few notes:

-unRAID v6.4.1 or above required.

-Current pool disk filesystem must be BTRFS, you cannot create a multi device pool from an XFS or ReiserFS single device pool.

-Always a good idea to backup anything important on the current pool in case something unexpected happens

-When first creating a pool with 2 or more devices initial profile used will be raid1, this can be changed later, since v6.12 you can choose the initial profile

-When a device is added to an existing pool the profile currently in use is maintained, e.g., if you have a two disk raid0 pool and add a third device it will become a three device raid0 pool in the end.

 

Procedure:

 

  • stop the array
  • change pool slots to 2 or more
  • assign new device(s) to the pool
  • start array - a balance will begin, the stop array button will be inhibited during the operation, this can take some time depending on how much data is on the pool and how fast your devices are, progress can also be seen by clicking on the first pool device and scrolling down to “btrfs balance status”
  • when balance is done or the stop array button is available the replacement is done, "btrfs balance status" should show "No balance found on '/mnt/<pool name>'", check also that "btrfs filesystem show" total devices are correct.

 

 

ZFS

A few notes:

-unRAID v6.12-rc2 or above required.

-Current pool disk filesystem must already be ZFS

-Always a good idea to backup anything important on the current pool in case something unexpected happens

-if the current pool is single device, in addition to adding just one device, you can also add two or three to create a 3-way or 4-way mirror.

-if the current pool is for example a 2-way mirror, you can add a single device to make a 3-way mirror and later add a 4th to make a 4-way mirror, if you add two devices to a 2-way mirror it will expand the pool by creating an additional vdev, becoming a two vdev 2-way mirror

-to expand an existing pool you need to add another vdev of the same width, e.g.:

     - two device 2-way mirror, you can 2 more devices, once that's done you can add 2 more, and so on

     - four device raidz1 pool, you can add 4 more devices, once that's done you can add 4 more, and so on

 

 

Procedure:

 

  • stop the array
  • change pool slots to 2 (or more)
  • assign new device(s) to the pool
  • start array - a resilver will begin, this can take some time depending on how much data is on the pool and how fast your devices are, progress can be seen by clicking on the first pool device and scrolling down to “pool status”
  • when the resilver is done confirm everything looks good by checking the "pool status" page.
  • Upvote 1
Link to comment

How do I remove a pool device?

 

BTRFS

A few notes:

-unRAID v6.4.1 or above required.

-Always a good idea to backup anything important on the current pool in case something unexpected happens

-You can only remove devices from redundant pools (raid1, raid5/6, raid10, etc) but make sure to only remove one device at a time, i.e., you cannot remove 2 devices at the same time from any kind of pool, you can remove them one at a time after waiting for each balance to finish (as long as there's enough free space on the remaining devices).

-You cannot remove devices past the minimum number required for the profile in use, e.g., 3 devices for raid1c3/raid5, 4 devices for raid6/raid10, etc, exception is removing a device from a two device raid1 pool, in this case Unraid converts the pool to single profile.

 

 

Procedure:

 

  • stop the array
  • unassign pool disk to remove
  • start the array (after checking the "Yes, I want to do this" box next to the start array button)
  • a balance and/or a device delete will begin depending on the profile used and number of pool members remaining, wait for pool activity to stop, the stop array button will be inhibited during the operation, this can take some time depending on how much data is on the pool and how fast your devices are.
  • when the pool activity stops or the stop array button is available the replacement is done.

 

ZFS

A few notes:

-unRAID v6.12-rc2 or above required.

-Always a good idea to backup anything important on the current pool in case something unexpected happens

-Currently you can only remove devices from 3 or 4-way mirrored pools (raid1) but make sure to only remove one device at a time, i.e., if you start with a 4-way mirror, you can remove two devices making it a 2-way mirror, but they must be removed one at a time.

-Currently removing a complete vdev from a mirrored pool is not supported, removing a mirror from a 2-way mirror will work but leave the mirror degraded, i.e., a new replacement device should then be added.

 

 

 

Procedure:

 

  • stop the array
  • unassign pool disk to remove
  • start the array (after checking the "Yes, I want to do this" box next to the start array button)
  • the removed device will be detached at array start.
  • check "pool status" page to confirm everything looks good

 

  • Upvote 3
Link to comment

How do I replace/upgrade a pool disk?

 

 

BTRFS

A few notes:

-unRAID v6.4.1 or above required, but it didn't work correctly with some releases, so make sure you are using v6.10.3 or later.

-Always a good idea to backup anything important on the current pool in case something unexpected happens

-On a multi device pool you can only replace/upgrade one device at a time.

-You cannot directly replace/upgrade a device from a non redundant multi device btrfs pool, e.g., from a raid0 pool.

-You cannot directly replace/upgrade a single device btrfs pool, this procedure can only be used to replace a device from a redundant multi device btrfs pool.

-You cannot directly replace an existing device with a smaller one, only one of the same or larger size, you can add one or more smaller devices to a pool and after it's done balancing stop the array and remove the larger device(s) (one at a time if more than one), obviously only possible if data still fits on the resulting smaller pool.

 

 

Procedure:

 

  • stop the array
  • if both devices are connected together: on the main page click on the pool device you want to replace/upgrade and select the new one from the drop down list (any data on the new device will be deleted)
  • if you can only connect the new device after removing the old one: shutdown the server, disconnect old device, connect the new one, turn the server on, on main the old device will show as missing, click on it and select the new device from the drop down list (any data on the new device will be deleted)
  • start the array
  • a btrfs device replace will begin, wait for pool activity to stop, the stop array button will be inhibited during the operation, this can take some time depending on how much data is on the pool and how fast your devices are.
  • when the pool activity stops or the stop array button is available the replacement is done.
  • if the new device is larger than the one being replaced you might need to stop/re-start the array once the replacement is done for the new capacity to be available.

 

 

ZFS

A few notes:

-if the pool was not created using the GUI, just imported, make sure the device assignments correspond the the zpool status order, or it will cause issues during a device replacement

-unRAID v6.12-rc2 or above required.

-Always a good idea to backup anything important on the current pool in case something unexpected happens

-Currently on a multi device pool you can only replace/upgrade one device at a time, even if the pool redundancy allows more.

-when upgrading devices, only when all the devices from that vdev have been replaced will you see the extra capacity available.

-You cannot directly replace/upgrade a device from a non redundant multi device zfs pool, e.g., from a raid0 pool.

-You cannot directly replace/upgrade a single device zfs pool, this procedure can only be used to replace a device from a redundant multi device zfs pool.

-You cannot directly replace an existing device with a smaller one, only one of the same or larger size.

 

 

Procedure if you can have both the old and new devices connected at the same time:

 

  • stop the array
  • on the main page click on the pool device you want to replace/upgrade and select the new one from the drop down list (any data on the new device will be deleted)
  • start the array
  • a 'zpool replace' will begin and the new device will be resilvered
  • progress can be seen by clicking on the first pool device and scrolling down to “pool status”
  • when done again check "pool status" page to confirm everything looks good

 

Procedure if you cannot have both the old and new devices connected at the same time:

 

  • stop the array
  • on the main page click on the pool device you want to replace/upgrade and unassign it, select 'no device'
  • start the array
  • that device will be offlined from the pool
  • shutdown the server
  • remove the old device, install the new device
  • turn on the server, if array auto-start is enabled stop the array
  • on the main page assign the new pool device
  • start the array
  • a 'zpool replace' will begin and the new device will be resilvered
  • progress can be seen by clicking on the first pool device and scrolling down to “pool status”
  • when done again check "pool status" page to confirm everything looks good

 

  • Like 4
  • Upvote 1
Link to comment

I have two different size cache devices, why is the reported space incorrect?

 

Old Unraid bug when using different size devices (fixed on v6.9-beta30), usable size in default 2 device pool RADI1 config is always equal to the smallest device.

 

Although free pool space is incorrectly reported the cache floor setting should still work normally (at least for unRAID v6.2 and above), i.e., set it according to the real usable space.

 

To see the usable space with 3 or more different size devices in any profile use the calculator below:

 

http://carfax.org.uk/btrfs-usage/

 

  • Upvote 1
Link to comment

Can I change my btrfs pool to RAID0 or other modes?

 

Yes, for now it can only be manually changed, new config will stick after a reboot, but note that changing the pool using the WebGUI, e.g., adding a device, will return cache pool to default RAID1 mode (note: starting with unRAID v6.3.3 cache pool profile in use will be maintained when a new device is added using the WebGUI, except when another device is added to a single device cache, in that case it will create a raid1 pool), you can add, replace or remove a device and maintain the profile in use following the appropriate procedure on the FAQ (remove only if it does not go below the minimum number of devices required for that specific profile).

 

It's normal to get a "Cache pool BTRFS too many profiles" warning during the conversion, just acknowledge it.

 

These are the available modes (enter these commands on the cache page balance window e click balance**, note if the command doesn't work type it instead of using copy/past from the forum, sometimes extra characters are pasted and the balance won't work)

 

** Since v6.8.3 you can chose the profile you want from the drop-down window and it's not possible to type a custom command:

image.png.e13bebb5fd4d9b566752a7fe9b44e9d4.png

 

 

All the command below can still be used on the console:

 

Single: requires 1 device only, it's also the only way of using all space from different size devices, btrfs's way of doing a JBOD spanned volume, no performance gains vs single disk or RAID1

 btrfs balance start -dconvert=single -mconvert=raid1 /mnt/cache
 

 

RAID0: requires 2 device, best performance, no redundancy, if used with different size devices only 2 x capacity of smallest device will be available, even if reported space is larger.

btrfs balance start -dconvert=raid0 -mconvert=raid1 /mnt/cache
RAID1: default, requires at least 2 devices, to use full capacity of a 2 device pool they all need to be the same size.

 

btrfs balance start -dconvert=raid1 -mconvert=raid1 /mnt/cache

 

RAID10: requires at least 4 devices, to use full capacity of a 4 device pool they all need to be the same size.

btrfs balance start -dconvert=raid10 -mconvert=raid10 /mnt/cache
 

 

RAID5/6 still has some issues and should be used with care, though most serious issues have been fixed on current kernel at this of this edit 4.14.x

 

RAID5: requires at least 3 devices.

btrfs balance start -dconvert=raid5 -mconvert=raid1 /mnt/cache
 

 

RAID6: requires at least 4 devices.

btrfs balance start -dconvert=raid6 -mconvert=raid1 /mnt/cache
Note about raid6**: because metadata is raid1 it can only handle 1 missing device, but it can still help with a URE on a second disk during a replace, since metadata uses a very small portion of the drive, you can use raid5/6 for metadata but it's currently not recommended because of the write hole issue, it can for example blowup the entire filesystem after an unclean shutdown.
 
** Starting with Unraid v6.9-beta1 btrfs includes support for raid1 with 3 and 4 copies, raid1c3 and raidc4, so you can use raid1c3 for metadata to have the same redundancy as raid6 for data (but note that the pool won't mount if you downgrade to an earlier release before converting back to a supported profile on the older kernel):
btrfs balance start -dconvert=raid6 -mconvert=raid1c3 /mnt/cache

 

 

Obs:

-d refers to the data, -m to the metadata, metadata should be left redundant, i.e., you can have a RAID0 pool with RAID1 metadata, metadata takes up very little space and the added protection can be valuable.

 

When changing pool mode confirm that when the balance is done data is all in the new selected mode, check "btrfs filesystem df"on the cache page, this is how a RAID10 pool should look like:

Quote

Data, RAID10: total=14.00GiB, used=9.85GiB

System, RAID10: total=224.00MiB, used=16.00KiB

Metadata, RAID10: total=2.19GiB, used=10.23MiB

GlobalReserve, single: total=16.00MiB, used=0.00B

 

If there is more than one data mode displayed, do the balance again with the mode you want, for some unRAID releases and the included btrfs-tools, eg, v6.1 and v6.2 it's normal needing to run the balance twice.

  • Like 5
Link to comment
  • 1 month later...

What is "Boot GUI mode", and how do I change to it?

 

Some users run unRAID as headless, and if you do, then this FAQ is not for you.  The Boot GUI is a GUI replacement for the text based terminal screen on the server console that we have always seen after boot, until now.  It provides the same unRAID screens on the server monitor that you normally get when you open your unRAID server from a browser on another desktop.

 

One important requirement - a mouse!  If you have never viewed a GUI on your server machine, then you may not have one attached, and any GUI requires a mouse.  Because support is built in, getting a mouse working should be easy, but may not be (and you may have to reboot).

 

To set the GUI mode, go to the Main screen and click on your unRAID flash disk (on the word 'Flash'), to open its settings page.  Go down to the Syslinux Configuration section.  This is a viewer and editor of your syslinux.cfg file, the file that controls the boot menu for your server.  After some preliminary general settings lines, you will see a series of sections that begin with label.  Each section controls a separate menu line on your boot menu.  In one of them is the line "menu default", which marks the menu item that will be performed if nothing is selected within the allotted time.

 

To change the default menu selection, simply move the "menu default" line into the section you want to be the default, then click Apply then Done.  Try it and see, you can always change it back.

 

One warning!  This uses Firefox as the browser to open the unRAID server management pages.  It's fine for that, but because it's a browser, it will be tempting to go on the Internet.  It is NOT configured to securely access the Internet!  Don't do it!  To be safe, use it only for managing your unRAID server.  (This author is not sure of the security implications and dangers here, and prefers to err on the side of safety.)

 

An example of a modified syslinux.cfg -

default /syslinux/menu.c32
menu title Lime Technology, Inc.
prompt 0
timeout 50
label unRAID OS
  kernel /bzimage
  append initrd=/bzroot vga=6
label unRAID OS GUI Mode
  menu default
  kernel /bzimage
  append initrd=/bzroot,/bzroot-gui vga=6
label unRAID OS Safe Mode (no plugins, no GUI)
  kernel /bzimage
  append initrd=/bzroot unraidsafemode vga=6
label Memtest86+
  kernel /memtest

  • Like 1
  • Thanks 1
Link to comment
  • 2 weeks later...

I have a new SAS drive.  How do I get unRAID to recognize and assign it?

Why can't unRAID find or add my SAS drive?

 

Assuming you are running unRAID 6.2, go to Settings -> Display Settings and change Display world-wide-name in device ID from Disabled to Automatic.  Click Apply then Done, and then go see if unRAID will let it be assigned!

Link to comment
  • 1 month later...

I set a share to private, created a user set read/write permissions to that share.  But on my windows 7 PC when i try to navigate to that share it's saying I don't have access when i put the user name and password. Did I miss anything?

 

Here is a explanation of what is happening from LimeTech:

 

Edited by Frank1940
updated linnk
Link to comment

I'm getting an error message " Failed to find user 'avahi' ".  What do I do?

Why after upgrading to a 6.2 version is my webGUI so slow?

Why is my webGUI taking so long between pages?

 

Symptoms:

- the error message "Failed to find user 'avahi'", usually in the syslog but may appear on the console too

- changing pages in the webGUI will take from 20 to 40 seconds per page

- some combination of the following sequence of lines appears over and over in the syslog:

Quote
Aug  5 13:52:02 DarkTower emhttp: shcmd (20782): /etc/rc.d/rc.avahidaemon start |& logger

Aug  5 13:52:02 DarkTower root: Starting Avahi mDNS/DNS-SD Daemon:  /usr/sbin/avahi-daemon -D

Aug  5 13:52:02 DarkTower avahi-daemon[20325]: Failed to find user 'avahi'.

Aug  5 13:52:22 DarkTower root: Timeout reached while wating for return value

Aug  5 13:52:22 DarkTower root: Could not receive return value from daemon process.

Aug  5 13:52:22 DarkTower emhttp: shcmd (20783): /etc/rc.d/rc.avahidnsconfd start |& logger

Aug  5 13:52:22 DarkTower root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon:  /usr/sbin/avahi-dnsconfd -D

Aug  5 13:52:22 DarkTower avahi-dnsconfd[20428]: connect(): No such file or directory

Aug  5 13:52:22 DarkTower avahi-dnsconfd[20428]: Failed to connect to the daemon. This probably means that you

Aug  5 13:52:22 DarkTower avahi-dnsconfd[20428]: didn't start avahi-daemon before avahi-dnsconfd.

 

For as yet unknown reasons, the internal 'avahi' user is missing from some users unRAID systems, and this avahi user has become more important for the proper functioning of the avahi daemons in 6.2 and later.  This missing user results in long timeouts while the avahi daemons try over and over to re-initialize.

 

The solution is to edit the passwd file on your boot flash disk ( /boot/config/passwd ), and add the following 2 lines to it:

avahi:x:61:214:Avahi Daemon User:/dev/null:/bin/false
avahi-autoipd:x:62:62:Avahi AutoIP Daemon User:/dev/null:/bin/false 
 

Then edit the shadow file on your boot flash disk ( /boot/config/shadow ), and add the following 2 lines to it:  (this may be needed for proper security)

avahi:!:14980:0:99999:7:::
avahi-autoipd:!:14980:0:99999:7::: 

 

You will need to use a Linux-aware editor to preserve correct Linux style line endings.  You can use the built-in mc or nano.  It's often easier to use copy and paste in Windows or Mac, just make sure you preserve the Linux style line endings.  You may have to reboot for it to take effect, or at least restart the array.  This post may be edited further as more info comes in.

Edited by RobJ
fix formatting for IPS
  • Upvote 1
Link to comment

How do I replace/upgrade my single cache device? (unRAID v6.2 and above only)

 

This procedure assumes that there are at least some dockers and/or VMs related files on the cache disk, some of these steps are unnecessary if there aren't.

  • Stop all running Dockers/VMs
  • Settings -> VM Manager: disable VMs and click apply
  • Settings -> Docker: disable Docker and click apply
  • For v6.11.5 or older: Click on Shares and change to "Yes" all cache shares with "Use cache disk:" set to "Only" or "Prefer"
  • For v6.12.0 or newer: Click on all shares that are using the pool you want to empty and change them to have the pool as primary storage, array as secondary storage and mover action set to move from pool to array
  • Check that there's enough free space on the array and invoke the mover by clicking "Move Now" on the Main page
  • When the mover finishes check that your cache is empty (any files on the cache root will not be moved as they are not part of any share)
  • Stop array, replace cache device, assign it, start array and format new cache device (if needed), check that it's using the filesystem you want
  • For v6.11.5 or older: Click on Shares and change to "Prefer" all shares that you want moved back to cache
  • For v6.12.0 or newer: Click on Shares and change the mover action to move from array to pool for all shares that you want moved back to cache
  • On the Main page click "Move Now"
  • When the mover finishes re-enable Docker and VMs
     

 

 

  • Like 21
  • Thanks 2
Link to comment
  • 4 weeks later...

I have software that requires using port 80.  How do I change the HTTP port that unRAID uses?

 

First, be certain that's what you really want, as changing the unRAID port should normally be a last resort.  It's usually much better to change the port your app needs instead.  Docker container ports can usually be remapped.

 

Currently, the only way is to edit your go file, and start emhttp with a different port.  The go file is at /boot/config/go if you are editing it in a terminal, at \\tower\flash\config\go if you are editing it from Windows (change 'tower' as needed).

 

Find this line in the go file:

  /usr/local/sbin/emhttp &

And change it to:

  /usr/local/sbin/emhttp  -p  ##  &

Where ## is the new port number you want to use to reach your unRAID server webGUI.

 

Then reboot the server.

 

Don't forget that you will also need to change the location in your browser!

 

Example:  set emhttp port to 8080

  /usr/local/sbin/emhttp -p 8080 &

Reboot your unRAID server, then browse to it on the new port

  http://tower:8080

Link to comment

Is there a way to create a Windows shortcut for shutting down the unRAID server?

 

On your Windows machine:

- Install PuTTY first, it includes plink.exe

- Create a batch file (store it anywhere you choose) containing the following line (replace password_here and server_IP_here):

    plink.exe  -ssh  -pw  password_here  root@server_IP_here  poweroff

    e.g. plink.exe -ssh -pw 123456 [email protected] poweroff

    Note: with older versions of unRAID, use powerdown instead of poweroff

- Create a shortcut on your Windows desktop that points to that batch file

 

Clicking that shortcut should start the normal unRAID shutdown procedures.

Edited by RobJ
add poweroff
Link to comment
  • 3 weeks later...

I found a segfault error in my syslog.  How do I fix it?

My system is crashing randomly, and/or I'm seeing a little data corruption.  How do I fix it?

How do I test my RAM, my system memory?

 

* Segfaults - there are 2 primary reasons for segfaults - faulty memory chips and dependency issues.  See below for methods to test your RAM.  If your RAM is fine, then it's almost certainly a dependency issue - some software that you have added has a dependency that conflicts with either the core unRAID system or something else you have added.

 

* Random crashes and data corruption - while there could be a number of causes for both of these, one primary cause and the easiest to test and fix is faulty RAM.  Thoroughly test your memory using one or both of the following methods.

 

The 3 symptoms above are the most common symptoms of bad RAM chips, but there are others too such as kernel OOPS and kernel panics and other syslog errors resulting in a 'Call Trace'.  While there may be other causes for these, the first test you should always do (and the easiest!) is to thoroughly test your memory chips.  The following 2 methods will test your RAM for problems, and report any errors found.  IMPORTANT!  Not one error is acceptable!  If you run a Memtest for 12 hours and it only finds one problem, then you need to replace a RAM stick!  You absolutely HAVE to be able to trust your memory.  When you test memory, you expect 100% perfection, no matter how long you test!

 

Note: there are 2 different Memtest programs, Memtest86 and Memtest86+.  They look very much alike for good reason - they have the same base code!  When the original development stopped in 2002, for about 2 years, an open source group created Memtest86+ from the code, and continued updating it until stopping in 2013, with v5.01 being their last release.  The free open source Memtest86+ v5.01 is what is included with unRAID.  PassMark Software bought the rights to the original code in 2013, and has been updating it ever since, as MemTest86, currently at v7.2.  Many newer technologies and tests have been added, such as DDR4, extensive ECC testing, row hammer testing, and much more.  The newer features do require UEFI support, and if not found, an older version will be booted instead.  While it's now a commercial product, they have continued offering a free version, for personal use only, but it is not licensed for inclusion with the unRAID software distribution.

 

Note 2: both methods assume you can view what is on the console of the unRAID server.  That usually means an attached monitor and keyboard, but could also mean remote viewing through IPMI.  There is NO WAY to run a memory test on a headless server (unless you can use IPMI).  To run either method, you MUST find a way to view the console, and you need a keyboard to select the test.  The PassMark Memtest can also use a mouse, so an attached mouse will be very helpful in Method 2.

 

* Method 1 - using the built-in Memtest

  • You MUST be able to see the console and use a keyboard to select Memtest from the boot menu.
  • On booting your unRAID server, when the boot menu appears, select Memtest, and it will begin.  It will run continuously until you reboot.

* Method 2 - using the PassMark Memtest

  • You MUST be able to see the console and use a keyboard to select Memtest(?).  A mouse will also be very helpful, recommended.
  • (download from PassMark, create bootable USB drive, configure UEFI settings to boot UEFI, boot, after completion restore UEFI settings)
  • PassMark download
  • PassMark installation help
  • (work in progress)

 

Bad memory defects will fail the tests on the very first Memtest pass.  Once you see the first error, you can stop the test as there's no point in continuing.  Unfortunately, other memory defects are much harder to find, marginal cells that appear to work fine *most* of the time.  *Most* of the time is not good enough, they need to be perfect *all* of the time.  So you will need to let the tests run a long time, waiting for that marginal cell to fail.  Again, even one error means a bad memory stick.  How long is long enough?  I believe over night, or 12 hours is sufficient, but it's possible that in some circumstances, even longer may be needed.

 

If you do get an error, then you will want to isolate which stick is bad and which ones are fine.  That means alternately testing different combinations of sticks, or each stick individually.

 

This is a work in progress, but almost ready to put online!

  • Upvote 1
Link to comment
  • trurl featured this topic

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.