{5} Accepted, Active Tickets by Owner (Full Description) (48 matches)

We should have an initial setup wizard. This wizard would walk you through things like the windows setup wizard does. What time zone, IP info, passwords, etc. It should then generate the proper entries in all the database tables.

Hi.

I administer an environment in which I use FreeIPA v3 (aka Red Hat Identity Management) as my SSO solution. While most of my hosts are Linux, a few are Windows and Mac. I'm hoping to configure FreeNAS to authenticate CIFS to the LDAP + Kerberos exposed by FreeIPA, preferably without modifying the LDAP structure.

Here is some documentation from their side:

​https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html-single/Identity_Management_Guide/#cifs

Please consider this a feature and/or documentation request on how to authenticate FreeNAS (with CIFS) to FreeIPA v3.

Thanks, Joshua

FreeNAS-9.1.0-ALPHA-8c9ebb9-x64

If you edit settings for an existing jail from the left treemenu, the popup window where you enter the settings says EDIT or CANCEL instead of SAVE or CANCEL.

(Enhancement request to maximize zpool reliability/availability)

Automatic, periodic ZFS pool scrubbing with results collection, reporting, and alerts.

It would be great to have functionality in the GUI to streamline the setting of weekly or monthly zpool scrubs, collect and archive scrub results, and include the last few scrub results in periodic emails.

A reasonable default would be to set a weekly zpool scrub at e.g. 3am Sunday for all zpools upon creation.

Some background from the ZFS Best Practices wiki:

"Run zpool scrub on a regular basis to identify data integrity problems. If you have consumer-quality drives, consider a weekly scrubbing schedule. If you have datacenter-quality drives, consider a monthly scrubbing schedule. You should also run a scrub prior to replacing devices or temporarily reducing a pool's redundancy to ensure that all devices are currently operational."

-- ​http://www.solarisinternals.com/wiki/index.php/ZFS_Best_Practices_Guide

The implicit rationale for periodic scrubbing is to proactively detect bit errors and stay ahead of drive failures. Having recently completed a scrub maximizes the probability that the data you have on disk is correct, since if/when you enter degraded mode you can no longer correct latent errors.

I have been trying to find a solution on how to install VirtualBox? on a FreeNAS host. With memory so cheap, the power of a FreeNAS box should be enough for a couple of virtual servers.

The problem I have come across is the fact that FreeBSD jails share the kernel with the host and Virtualbox needs to load a module into the kernel.

I have found a possible solution for installing the kernel module on the host and then installing virtualbox inside a jail. This solution however assumes a full FreeBSD host where the ports tree can be used. ​http://forums.freebsd.org/showthread.php?t=21897

I quickly tried to install virtualbox-ose-kmod-legacy using pkg_add on the host, but I couldn't load it due to "KLD vboxnetflt.ko: depends on netgraph - not available or version missmatch". I haven't dug any deeper into this problem.

What I call for is support for software add-ons that require kernel modules to be loaded on the host.

Customer has requested that we add a way in the GUI to look at the last SMART run. There's a lot of data that gets output from smartctl; ultimately we need to just say pass/fail based on the following output:

# smartctl -l xselftest /dev/ada0
smartctl 5.42 2011-10-20 r3458 [FreeBSD 9.0-RC2 amd64] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF READ SMART DATA SECTION ===
SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     14392         -

smartctl -a prints out way too much output and a lot of it can be confusing to customers and home users.

Replace disk from GUI fails without explanation when using identical 2TB disk.

After doing replace disk from GUI, there is no apparent resilvering activity taking place or message in the GUI about the failure. After trying replace command from the command line, I got the error "disk is too small". When doing a gpart show, I discovered the problem was that 8.0.3-p1 created a 2GB swap partition as opposed to the 1GB swap partition that was created when I initially created my pool from the GUI in version 8.0. So it seems that the GUI needs to check existing swap partition size and makes sure it creates the new one consistent with the size on the other disks. I manually wiped the disk and recreated the partitions and did the replace from the command line using the same command that was issued from the GUI in the log file.

Here is the forum thread with log files etc.

​http://forums.freenas.org/showthread.php?5810-Replace-Disk-fails-from-GUI-in-8-0-3-p1&p=21033#post21033

Currently these fields (when modifying user, when setting up replication, etc.) will access the input without validation.

It would be nice if it can remove unneeded spaces/line feeds that renders the key unusable, or at least bail out. For instance, this:

""" 10.2.1.25 ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIb mlzdHAyNTYAAABBBAkEu2+8U+Vjf06RSDJKgLDhUYLJ3jy/NFqeIqQKYRKd5V63gRgw Gq4aBUcd57EpD5HH9twC6Wd2WRasICfmkDo= """

Should be changed to this:

""" 10.2.1.25 ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBAkEu2+8U+Vjf06RSDJKgLDhUYLJ3jy/NFqeIqQKYRKd5V63gRgwGq4aBUcd57EpD5HH9twC6Wd2WRasICfmkDo= """

If you try to share directory via CIFS and type nonexistent directory because you want to share volume subdirectory then your typed in directory is not created by GUI and sharing does not work.

Got the following errors when I tried to remove or offline the log device in the GUI.

Oct 25 10:11:42 sanbox manage.py: [middleware.exceptions:38] [MiddlewareError: Disk could not be removed: "cannot remove gptid/c769df18-1ea6-11e2-ac6c-005056ac0e70: no such device in pool, "]
Oct 25 10:12:19 sanbox notifier: swapoff: /dev/da1p1: Invalid argument
Oct 25 10:12:19 sanbox manage.py: [middleware.exceptions:38] [MiddlewareError: Disk could not be removed: "cannot remove gptid/c769df18-1ea6-11e2-ac6c-005056ac0e70: no such device in pool, "]
Oct 25 10:12:57 sanbox notifier: swapoff: /dev/da1p1: Invalid argument
Oct 25 10:12:57 sanbox manage.py: [middleware.exceptions:38] [MiddlewareError: Disk offline failed: "cannot offline gptid/c769df18-1ea6-11e2-ac6c-005056ac0e70: no such device in pool, "]

zpool status
  pool: san
 state: ONLINE
  scan: scrub repaired 0 in 0h36m with 0 errors on Thu Aug  9 02:33:18 2012
config:

        NAME                                          STATE     READ WRITE CKSUM
        san                                           ONLINE       0     0     0
          raidz1-0                                    ONLINE       0     0     0
            da2                                       ONLINE       0     0     0
            da6                                       ONLINE       0     0     0
            da3                                       ONLINE       0     0     0
            da4                                       ONLINE       0     0     0
            da5                                       ONLINE       0     0     0
        logs
          gptid/c769df18-1ea6-11e2-ac6c-005056ac0e70  ONLINE       0     0     0

errors: No known data errors

glabel status
                                      Name  Status  Components
                             ufs/FreeNASs3     N/A  da0s3
                             ufs/FreeNASs4     N/A  da0s4
                            ufs/FreeNASs1a     N/A  da0s1a
gptid/c769df18-1ea6-11e2-ac6c-005056ac0e70     N/A  da1p2
gptid/c7661b6a-1ea6-11e2-ac6c-005056ac0e70     N/A  da1p1

This worked at 1 point during the 8.3.x series but it's not working now for some reason. I may have changed someone that caused this but I believe I have a fairly clean setup at this point. The only thing I can think of is this time there was a reboot between adding & trying to remove the log and in the past there wasn't(don't ask why I keep add & removing the log unless you'd like more detail then this report probably needs).

I have a RAID-Z containing 7 devices and 1 hot spare. I physically remove one of the devices (da2 in this case) and the volume status shows the spare as status "null" although

zpool status

returns the correct state. This prevents me from replacing the failed drive with the spare from the GUI.

See attached screenshots.

This request is for the Web UI.

When checking on the status of a ZFS volume (zpool status) it should:

• show the status of the scrub (if there is one in progress)
• show the state of the spares

When viewing the disks in a ZFS volume (view disks):

• list spares in addition to the other disks in the pool

I upgraded from 8.0 to 8.0.2 today. I am running the latest version.

At this time I have to run 'zpool status volume_name' from the command line to find this information.

Thank you.

I think there should be an option to reset network settings and interfaces to factory default, out there in the console. This is needed when for whatever reason one is no longer able to access the FreeNAS machine over the network and a reconfiguration is appropriate to do via the console. So in short, the same as the current factory default, but only for the networking.

Here I like to describe a “MultiUser?-Like” UI

The Current Situation:

Currently it is only possible to login to the UI as “admin/root”. You have access to all settings.

What are Login-Modes?

Currently I have 3 different Login-Modes in mind.

Admin/root

The Admin have access to all Settings on the system.

Operator

The Operator-Mode hide all settings which are not essential for everyday-tasks. Usually there is no need to change network config, devices connected to a pool or basic settings of the services. (The Drive Caddy should do this without the need to access the UI) This Login-Mode provide only access to things like managing user permissions, creating and deleteing share or just check logs/status (perhaps an additionl Monitoring-Mode(readonly).

User

User usually only need access if they like to browse Files (a service is down and he like to download it via WebUI).also it would be nice if you can change passwords and personal informations.

Hi, I´m used to connect and transfer files via SSH, since it's much more secure than SSL/TLS.

When I SFTP connect with my login/password or auth keys there's no problem in seeing all NAS files because I'm it's owner, but when I decide to create a user for friends's SFTP access, I want them to be confined in their home directory.

I know there are some "extras" that can be configured in SSHD GUI for that, but they didn't worked for me, and I tought that feature could be configurable in the USER GUI, not whole SSHD GUI for all users.

I'm reporting on my actual 8.0.4, but it would be great to see this available on future versions, too.

AoE is a fast and lightweight layer 2 protocol that allows for access to SATA storage devices over Ethernet networks. It's very easy to configure and scales linearly. I have created a howto guide on the forums that shows users how to implement AoE support on FreeNAS via the Plugins/jails feature. ​http://forums.freenas.org/showthread.php?11446-HOWTO-AoE-(ATA-over-Ethernet)-setup-using-Plugins-jail&p=54166#post54166

I think that AoE support merits inclusion into FreeNAS as a core service. Please give it due consideration.

Deleting an iSCSI target with a volume that's currently in use warns the user that it's in use instead of providing a "are you sure you wish to delete this extent", kind of error. This is inconsistent with deleting volumes, ZFS volumes, and datasets, where the user is given an option to cascade delete all shares associated with the volume(s).

Procedure:

1. Go to "Storage" -> "Volumes" -> "Create Volume".
2. Add a volume of type "ZFS" named "test".
3. Go to "Create ZFS Volume".
4. Create a ZFS volume named "test2" using the "test" ZFS pool.
5. Go to "iSCSI" -> "Device Extent".
6. Add an extent named "test3", pointing to the ZFS volume "test2".
7. Go to "View all Volumes".
8. Try and delete "test2" (this will fail citing that the ZFS volume is in use by "test3").
9. Try and delete "test" zpool. Click "Yes" (this will succeed).

Expected result:

The user should be presented with a dialog asking if they wish to disable all services associated with the "test2" ZFS volume (i.e. the "test3" extent). If they press no, nothing should occur. Otherwise, it should cascade down and delete the iSCSI extent as well.

Actual result:

The user is blocked from deleting the iSCSI extent, but not when deleting the "test" ZFS pool.

Windows users can have spaces in their usernames. Unfortunately this doesn't work with the system crontab because spaces are used as field delimiters and the username isn't tokenized properly with either octal/hex escaped characters or by quoting the username (I tried). crontab -u 'DOMAIN\user name' -e works though.

Filed upstream here: ​http://www.freebsd.org/cgi/query-pr.cgi?pr=164808

Procedure:

1. Join machine to AD domain.
2. Create a user on the PDC called 'DOMAIN\user name'.
3. Attempt to create an cronjob that does 'echo hello > /tmp/iwuzhere' that runs every minute of every day.

Expected result:

• 'cat /tmp/iwuzhere' should say 'hello'.

Actual result:

• The command isn't executed.

It has been noted elsewhere that configuration changes to afpd alone cannot stop MacOS X clients from creating the necessary files and directories to support Finder activity.

To this end, it would be useful to 'veto' the files and directories thus created, to prevent them being seen from within the SMB view of the filesystem namespace. The visibility of these entries is completely benign, but may be confusing to users or filesystem backup tools.

This is possible with the current GUI, but the necessary directives and paths, have to be added (and vetted) manually.

I should like to see this added as an option in the GUI. I propose this as a new feature for the next release.

I was testing the MiniDLNA plugin in 8.2 BETA3, and found that I needed to move every media folder into one to make them all available in MiniDLNA.

Instead of "CHOOSE ONE FOLDER" for scanning, several folders should be configured. Wouldn't that be better?

Setting up timemachine shares would benefit from the availability (via the GUI) of the option "volsizelimit" for afpd. This would be useful either via a 'custom options' field for afp shares, or a proper option in the afpd settings.

This option is useful when announcing a single large share, where apples' timemachine will only "see" the disk as being of size "volsize". (A quota of 100G on a 1T share will let timemachine see the 1T and try to fill it up, which breaks things).

The volsize option allows for one large bonjour/avahi announce, instead of many (one per timemachine share). The reason for wanting only one avahi announce is that avahi will announce all shares using one packet. When adding more shares the announcents will no longer fit inside a single packet and avahi falls over with an error of: "avahi-daemon[53535]: Record too large, cannot send". For me things broke when announcing the 21st timemachine share...

Technical details: Option is used inside /usr/local/etc/Applevolumes.default

Example: "/mnt/store1/tm_onelarge" "tm_onelarge" options:usedots,nohex,upriv,tm dperm:0644 fperm:0755 ea:ad allow:@staff rwlist:@staff volsizelimit:524288

Using an Areca controller in JBOD mode you can obtain smart data using a command line like:

smartctl -a --device=areca,port# /dev/arcmsr0

However, it is not possible to monitor temperatures or SMART parameters using the SMART service as it is in 8.3.1-p2.

Hard drives passed through to the system are listed as daXX. The /conf/base/etc/rc.d/ix-smartd creates /usr/local/etc/smartd.conf and each line has the /dev/daXX line.

Naturally, i added the "--device=areca,1 /dev/arcmsr0" to the S.M.A.R.T extra options under the given disk(da0 for my test case). Unfortunately this has the result of creating a bad smartd.conf file and the GUI will return with the error "The service failed to restart." Examining the smartd.conf the issue appears to be that the line now reads:

/dev/da0 -n never -W 0,0,0 -m myemail@… --device=areca,1 /dev/arcmsr0

When the --device=areca,1 /dev/arcmsr0 is used along with the /dev/da0 then problems arise because the SMART service thinks you are trying to access 2 drives, /dev/da0 and the areca port 1 device.

This ticket is to request SMART support via the GUI be added for the Areca controller family.

The two ways I can think of for support to be added is to add something like a checkbox allowing you to disable the automatically generated device(/dev/da0 for my example) or add the appropriate code for the Areca controller support to /conf/base/etc/rc.d/ix-smartd. Both may be desirable for FreeNAS support since it allows other brands that have unique commands like Areca to be able to disable the automatic device creation.

The following is the output of the commands used to parse the ix-smartd and should provide developers with the appropriate info to get ix-smartd to properly parse Areca controllers:

camcontrol devlist -v

scbus0 on arcmsr0 bus 0:
<WDC WD20EARS-00S8B1 R001>         at scbus0 target 0 lun 0 (pass0,da0)
<WDC WD20EARS-00S8B1 R001>         at scbus0 target 0 lun 1 (pass1,da1)
<WDC WD20EARS-00S8B1 R001>         at scbus0 target 0 lun 2 (pass2,da2)
<WDC WD20EARS-00S8B1 R001>         at scbus0 target 0 lun 3 (pass3,da3)
<WDC WD20EARS-00S8B1 R001>         at scbus0 target 0 lun 4 (pass4,da4)
<WDC WD20EARS-00S8B1 R001>         at scbus0 target 0 lun 5 (pass5,da5)
<WDC WD20EARS-00S8B1 R001>         at scbus0 target 0 lun 6 (pass6,da6)
<WDC WD20EARS-00S8B1 R001>         at scbus0 target 0 lun 7 (pass7,da7)
<WDC WD20EARS-00S8B1 R001>         at scbus0 target 1 lun 0 (pass8,da8)
<WDC WD20EARS-00S8B1 R001>         at scbus0 target 1 lun 1 (pass9,da9)
<WDC WD30EZRX-00MMMB0 R001>        at scbus0 target 1 lun 2 (pass10,da10)
<WDC WD30EZRX-00MMMB0 R001>        at scbus0 target 1 lun 3 (pass11,da11)
<WDC WD30EZRX-00MMMB0 R001>        at scbus0 target 1 lun 4 (pass12,da12)
<WDC WD30EZRX-00MMMB0 R001>        at scbus0 target 1 lun 5 (pass13,da13)
<WDC WD30EZRX-00MMMB0 R001>        at scbus0 target 1 lun 6 (pass14,da14)
<WDC WD30EZRX-00MMMB0 R001>        at scbus0 target 1 lun 7 (pass15,da15)
<TOSHIBA MK1251GSY R001>           at scbus0 target 2 lun 0 (pass16,da16)
<WDC WD20EARS-00S8B1 R001>         at scbus0 target 2 lun 4 (pass17,da17)
<WDC WD20EARS-00S8B1 R001>         at scbus0 target 2 lun 5 (pass18,da18)
<WDC WD20EARS-00S8B1 R001>         at scbus0 target 2 lun 6 (pass19,da19)
<WDC WD20EARS-00S8B1 R001>         at scbus0 target 2 lun 7 (pass20,da20)
<Areca RAID controller R001>       at scbus0 target 16 lun 0 (pass21)
<>                                 at scbus0 target -1 lun -1 ()
scbus1 on ahcich0 bus 0:
<>                                 at scbus1 target -1 lun -1 ()
scbus2 on ahcich1 bus 0:
<>                                 at scbus2 target -1 lun -1 ()
scbus3 on ata2 bus 0:
<>                                 at scbus3 target -1 lun -1 ()
scbus4 on ahcich2 bus 0:
<WDC WD20EARS-00S8B1 80.00A80>     at scbus4 target 0 lun 0 (pass22,ada0)
<>                                 at scbus4 target -1 lun -1 ()
scbus5 on ahcich3 bus 0:
<WDC WD20EARS-00S8B1 80.00A80>     at scbus5 target 0 lun 0 (pass23,ada1)
<>                                 at scbus5 target -1 lun -1 ()
scbus6 on ahcich4 bus 0:
<WDC WD20EARS-00S8B1 80.00A80>     at scbus6 target 0 lun 0 (pass24,ada2)
<>                                 at scbus6 target -1 lun -1 ()
scbus7 on ahcich5 bus 0:
<WDC WD20EARS-00S8B1 80.00A80>     at scbus7 target 0 lun 0 (pass25,ada3)
<>                                 at scbus7 target -1 lun -1 ()
scbus8 on ahcich6 bus 0:
<>                                 at scbus8 target -1 lun -1 ()
scbus9 on ahcich7 bus 0:
<>                                 at scbus9 target -1 lun -1 ()
scbus10 on umass-sim0 bus 0:
<HP v125w PMAP>                    at scbus10 target 0 lun 0 (pass26,da21)
scbus-1 on xpt0 bus 0:
<>                                 at scbus-1 target -1 lun -1 (xpt0)

I'm sure its less than 10 lines of code to parse this as HP SMART Array, 3ware controllers, and several Highpoints are parsed via ix-smartd. If I can figure it out on my own I'll post the code.

I can provide SSH access to my server on request if necessary to close this ticket.

The values being set in milliseconds for any dynamic DNS service is crazy. This should be in a more appropriate value of hours. Many DNS services penalize you for updating too frequently.

Also the FreeNAS manual states this is a value in seconds, still too small a period of time for my taste.

I would recommend a minor change to the software... Check the current IP address and every period of time (determined by the user value) check to see if the IP address has changed. If it has changed force an update. And for the force update field, value in hours, it would force an update even if the IP address has not changed in order to keep the DNS service alive.

I like that there are some mouse overs, when you get the time adding mouse overs to everything would aid in user friendliness.

If this is a repeat ticket, I apologize, I didn't see one when I scanned the active tickets.

I have some suggestions on how to improve the Help panel:

Under "Documentation", add a link to the FreeBSD Man Pages ​http://www.freebsd.org/cgi/man.cgi

Add a "Professional Support" section linking to iXsystems.com/TrueNAS ("Professionally-Supported FreeNAS-Based Storage Appliance" or something to that effect)