Anzeigen der neuesten Beiträge
0 Mitglieder und 1 Gast betrachten dieses Thema.
Upgrade Notes============= - Before upgrade you must always backup your configuration file, your system disk and all your data (if possible). - DO NOT use firmware upgrade if your installed FreeNAS revision is lower than 0.7(4975). Firmware upgrade from any version < 0.7(4975) is not recommended. The safest way to upgrade from any version < 0.7(4975), to 0.7.1, is to boot the LiveCD and use the upgrade options. - WARNING: If you try to do a firmware upgrade from a version < 0.7(4975), the process might fail with Broken Pipe or Mount / Umount related errors. Testing shows these symptoms occur frequently. If you encounter any of them during an attempted, unrecommended upgrade the only solution is to re-install from scratch, this will delete all data on the OS disk.Downgrade Notes=============== - Downgrading from 0.7.1 to any version less than 0.7(5001) is not recommended. - If you try downgrade to a version < 0.7(5001), the partitions may break or be corrupted leaving the system unusable and possibly destroying data stored on the OS drive.Other Notes=========== - The addition of new software makes the OS almost 1MB bigger.
FreeNAS 0.7.2 SabandaSunday, 17 October 2010 build 5462Majors changes: * Upgrade to FreeBSD 7.3-p3. * Upgrade unison to 2.32.52. * Upgrade bsnmp-ucd to 0.3.2. * Upgrade e2fsprogs to 1.41.12. * Upgrade smartmontools to 5.40. * Upgrade php5 to 5.2.14. * Upgrade transmission to 2.10. * Upgrade samba to 3.5.5. * Increase image size to 72MB, mfsroot to 180MB. * Increase default install size embedded to 120MB, full to 380MB. * Increase default swap size to 256MB. * Ireasnce memory disk for firmware upgrade to 128MB. * Create 4KB aligned data partition on the boot disk. * Upgrade arcconf to 6.40.18530. * Upgrade cdialog to 1.1.20100428. * Set kern.hz=100 when running on virtual machine and kern.hz>100. * Add virtual machine guest support (open-vm-tools/vbox-additions). * Upgrade inadyn-mt to 02.18.36. * Upgrade bash to 4.1.007. * Upgrade istgt to 20100707. * Upgrade msmtp to 1.4.20. * Upgrade nano to 2.2.4. * Upgrade gzip to 1.4. * Upgrade tftp-hpa to 5.0. * Introduce iSCSI boot/install feature (isboot 0.1.3). * Upgrade 3ware driver to 9.5.3. * Upgrade proftpd to 1.3.3b. * Upgrade lighttpd to 1.4.28.Minors changes: * Add Czech and Slovak translations. * Add multiple CPUs usage. * Add AIO WebGUI for CIFS/SMB service. * Remove /var/tmp symbolic link. * Support Advanced Format 4KB sector. (UFS/GPT data partition only) * Set fsck enable by default at Disks|Mount Point|Add. * Set kern.geom.debugflags when formating. * Modify Tuning values. * Add ability to disable File Manager. * Make three backups of configuration when writing new one. * Add amdtemp module. (FR 2992462) * Add ability to probe on-die digital thermal sensor. * Enable disk quotas of kernel option. * Remove a useless partition. * Add ability to mount 'a' partition on MBR/UFS. * Add variables to change upload directory of lighttpd. * Disable fsck on MBR/UFS mount point due to 4KB alignment. You needre-enable it after upgrading. * Add wireless firmware modules. * Add logical block length for iSCSI target. * Add ability to disable/enable for iSCSI target. * Add unused extents to the list in iSCSI target edit mode. * Add kernel module directory (/boot/modules). * Set Large read/write by default (Services|CIFS/SMB|Settings). * Add crypto accelerator driver (hifn, safe, ubsec). * Move upload directory to /var/tmp/ftmp from /ftmp. * Change iSCSI initial parameter. * Add new parameter of istgt 20100522. * Add minimum set of zfskerntune feature. * Add Hyper-V reboot issue patch. * Add ZFS pool with 4KB sector support. * Add ZFS cache and log device support. * Improve parameters for Samba 3.5.x. * Improve Active Directory support.Bug fixes: * Fix wrong validation when WINS is enabled. * Fix missing /var/tmp in full installation. * Fix upload fail when firmware upgrade. * Fix AIO checkbox is not disabled if samba is disabled. * Fix fail to update index.php if some value is undefined. * Fix control of Ctrl+Alt+Del if console menu is disabled (BR 2976816). * Fix the document link on Services|Rsync|Server|Settings (BR 2997828). * Fix fail to connect SSH if ActiveDirectory is enabled (BR 2821715, 2898371). * Fix UPS support for Megatec USB UPSs fails (BR 3079159).Permanent restrictions: * It is not possible to format a SoftRAID disk with MSDOS FAT16/32. * It is not possible to encrypt a disk partition, only complete disks are supported. * Enable 'polling' on interfaces used by a LAGG interface will make it inoperable.Known bugs: * If DHCP for IPv4 is used, the IPv6 statically configured DNS server will beoverriden by the IPv4 DNS server.NEED TESTING: * IPv6: auto mode * All services using IPv6 address (NFS, FTP, etc…) * Netatalk VFS Samba module (automatically enabled when Netatalk starts) crashessamba when accessing to share * Need to write an online-test procedureHelp needed: * Need help for adding LDAP authentication feature:Main services can be easily authenticated using PAM-LDAP, but is harder for Samba.
Release Notes for FreeNAS 8.0 Release Candidate 2---------------------------------------------------Release Candidate 2 contains fixes for issues that were encountered in RC1. Itdoes not contain the list of new functionality that was scheduled for RC2, butit contains enough fixes that it was a significant improvement over RC1.FreeNAS 8 should be installed to a USB stick or Compact Flash device. Itrequires a device of at least 1 GB in size. In a departure from FreeNAS 0.7releases, the OS drive can not be used as a component for a volume, nor canit be partitioned for sharing.New in this RC:GUI Firmware upgrades are supported, but do to a bug in the interaction betweenFreeBSD, lighttpd, and python they work intermittantly. There is a work-aroundwhich wasn't implemented in time for RC2. The procedure involves runningcommands from the CLI shell.# mount -uw /# echo 'server.network-backend = "writev"' >> \ /usr/local/etc/lighttpd/lighttpd.conf# mount -r /# /usr/local/etc/rc.d/lighttpd restartThe upgrade procedure takes advantage of nanobsd by writing the OS to the"inactive" slice. If you are running off slice 1 the firmawre will be writtento slice 2, and vice versa. The boot label is automatically updated, but during the initial boot the slice can be choosen manually, allowing for aneasy reversal of an undesirable upgrade.To use the GUI upgrade feature, first configure a storage volume. This isused for temporary storage space of the image. The temporary location isselected from system -> settings -> temporary directory. Once that isconfigured, select the Firmware Update tab. Browse to the firmware on yourmachine and choose it. Currently there are two firmwares available:http://sourceforge.net/projects/freenas/files/FreeNAS-8/FreeNAS-8.0-RC2-i386.xz/download SHA256 ff31a6e69244d264e1f5e2a395e36aa308256ebfce708112ae22adbd2de2e083http://sourceforge.net/projects/freenas/files/FreeNAS-8/FreeNAS-8.0-RC2-amd64.xz/download SHA256 29a131e11e4df9ae1a15d45bbd157ca672acc707d3eb98ae71a56ba175e1093dEnter the correct SHA256 hash, and upload the firmware. It will report successon completion, go ahead and reboot the FreeNAS box at that point and it willboot off the new firmware.Upgrading via the install iso is still supported, simply boot off the new ISOand select your boot device from the menu. If you are upgrading from asnapshot older than RC1 this is the only supported upgrade method.The bugs in the FTP configuration are sorted out. The GUI will nowgenerate valid configurations or refuse to save invalid values with anappropriate error message.The system now will send email about LSI RAID controller events if the emailservice is properly configured.Configuration bugs in the AFP service have been squashed, although there arestill mixed reports concerning AFP.Errata:Volumes created with previous snapshots, betas, or builds from the sourceforgerepo contained a bug in their GPT labeling scheme. This labelling can resultin reduced performance when the underlying device is a hardware RAID 5 or 6array. It is recommended that if the underlying storage device is a hardwareRAID controller using RAID 5/6/50/60 that volumes be deleted and recreated.The iSCSI service can generate broken configs for some scenarios. These willget fixed as feedback is received, as the number of initiators and their variousconfigurations creates a large matrix of possibilities. The initiators that arefairly well tested are the MS Software initiator, the VMware ESXi 4.x initiator,and the FreeBSD initiator.Link Aggregations, also know as LACP/LAGG/interface bonding, require a rebootto take effect. This is not enforced by the GUI or by the CLI. Furthermorethere is no way to create a Link Aggregation from the CLI, so the initial setupis at best non-intuitive. From the CLI you can configure a physical interfaceso that the web GUI can be accessed, then from the web GUI a Link Aggregationcan be created, then the physical interface can be deleted, the box rebooted,and then from the CLI the link aggregation can be selected for configuration.Once it is configured the box should be rebooted a final time.Replacing failed drives in arrays isn't possible through the GUI, and dueto the drives being GPT labeled replacing them via the CLI isn't easy either,nor is the replacement procedure documented at this moment. While thedocumentation will be available very shortly, the real solution will be viathe GUI.The GUI is still HTTP only. That will be rectified shortly, but for themoment accessing the GUI over a hostile network (such as the internet) isnot a good idea.Some Mac users are reporting substandard CIFS write speeds. The exactconditions for this are unknown.UPGRADES FROM FREENAS 0.7x ARE STILL UNSUPPORTEDThe system has no way to import configuration settings from 0.7 versionsof FreeNAS, nor is there any sort of volume importer yet that will preservedata on existing volumes. Attempting to upgrade from 0.7 will result in theloss of your configuration, your data, or quite likely, both.IMPORTING EXISTING STORAGE VOLUMES IS UNSUPPORTEDWe will get that working very shortly, for now, don't feed disks with datayou care about to FreeNAS 8Usability of this Release Candidate:At this point the feature set of FreeNAS 8 is complete enough to perform filesharing tasks via NFS or Samba, using local users, AD, or LDAP, as well asallowing the system to operate as an iSCSI target. The base technology ofFreeBSD, ZFS, Samba, and NFS is very stable and very well tested. While thereisn't an upgrade path from other storage solutions, including previous FreeNAS0.7 releases, the system is suitable for new deployments provided thefeatureset is a good match for the requirements.A note about versions:There's been a huge jump in version numbers. The intention is to have theversion number reflect the base version of FreeBSD used. This RC is basedon FreeBSD 8.2, but this version of FreeNAS is called 8.0 as there are futureplans to add functionality that will get the versions caught up. OnceFreeNAS 8.2 is out, a suffix will be added, such as 8.2.1, 8.2.2, etc.A note about filesystem technologies:While this system does support UFS based volumes, such as gmirror, gstripe,graid3, the primary focus is on ZFS. Many of the features are provided viaZFS datasets, such as the ability to share subsets of volumes via CIFS.This delta is likely to increase over time, the compelling reasons to useZFS are likely to increase as well. It is highly recommended to use ZFSfor new volumes, even if the underlying device is a volume exported by ahardware RAID controller.