limetech Posted November 30, 2010 Share Posted November 30, 2010 Download If no issues related to changes from 4.5.6 to 4.6-rc4 are reported by the end of this week, this will become release 4.6 "final". For -rc4: o 3rd Party Add-On Developers.. please ensure your existing add-ons work with this release. o Fixed issue with NFS where it's possible a client NFS-mount could refer to a different server resource as a result of configuration changes on the unRaid server. NOTE: if you are using NFS, I strongly suggest you un-mount any NFS client connections to your unRaid server before updating to this release. Following re-boot with this release, you will need to go to the Shares page and click 'Apply' for each User Share that you want exported via NFS. Subsequent client NFS mounts should be ok and be preserved across server config changes and re-boots. Following are the technical details: All NFS-exported shares will have an explicit 'fsid' value set. For disk shares, and the cache share, it's set as follows: for cache, fsid = 10 for diskN, fsid = 10+N (ie, for disk1 it's 11, for disk2 it's 12, etc.) For user shares, the first time a share is configured for NFS export, we assign an fsid to it (stored in the 'shareExportNfsFsid' variable in the user-share config file). The fsid's are assigned starting at 100. Once an fsid is assigned to a user share, that fsid stays with that share (but if the share is deleted and later re-created, it will get a different fsid). Also fsid's are never re-used. The next fsid to be assigned is kept in the 'shareNfsFsid' config variable in the 'share.cfg' file. unRAID Server 4.6-rc4 Release Notes =================================== Changes from 4.6-rc3 to 4.6-rc4 ------------------------------- Bug fixes: - Make 'Move now' button respect the 'Mover logging' setting. Other: - More backward compat. fixes (revert kernel to that used by 4.5.6). - Set explicit NFS 'fsid' assignment for disk shares, and make 'fsid' values persistent for user shares. Changes from 4.6-rc2 to 4.6-rc3 ------------------------------- Other: - More unRaid driver/3rd part add-on backward-compatibility fixes. - Update 'hdparm' to version 9.27 - Update 'smartmontools' to version 5.39.1 - Update 'memtest' to version 4.10 [Note: you will need to move the file 'memtest' from the zip file to the root of your Flash device] Changes from 4.6-rc1 to 4.6-rc2 ------------------------------- Other: - Restore "diskNumber" and "rdevNumber" driver vars. Changes from 4.5.6 to 4.6-rc1 ----------------------------- Bug fixes: - Fix for kernel oops of the following type: "Tower kernel: EIP is at md_cmd_proc_read+0x41/0x54 [md_mod]" Other: - Make unRaid driver "status" command a no-op and patch '/root/mdcmd' script to properly handle a "status" command for backward compatibility. - Restore backward-compatibility with 4.5.6 in regards to 3rd party add-ons. Changes from 4.5.5 to 4.5.6 --------------------------- Sorry, the 4.5.5 release package got built wrong which resulted in bugs listed below. Bug fixes: - Fixed problem with restoring timezone setting upon reboot. - Fixed missing reiserfsprogs. Changes from 4.5.4 to 4.5.5 --------------------------- Bug fixes: - Fixed 'Mover logging' control in webGui. Other: - Added better timezone support. - Increase supported array width from 20 to 21 drives. - Add 'Are you sure?' prompt to the 'initconfig' command. - Added IPMI support, I2C support, and Intel 82801 support. - During parity-check, the first 20 sync errors are output to the system log. - If directory named 'extra' exists in root of Flash, invoke 'installpkg' on all files found there before invoking the 'go' script. - Add 'removepkg' and 'explodepkg'. - Added 'bzip2'. - Upgrade reiserfsprogs to version 3.6.21 Changes from 4.5.3 to 4.5.4 --------------------------- Bug fixes: - Fix (another) problem where formatted data disks could appear 'unformatted' immediately following array start. This one was due to race condition where md devices could possibly not exist before management utility issues 'mount'. Other: - Generate additional logging information during 'mount'. - Added additional "safeguards" in the code handling 'format' operations. - Removed 'Restore' button from webGui, replacing with new shell command called 'initconfig'. - Updated mc (midnight-commander) utility to slackware's 2010-02-06 version. Changes from 4.5.2 to 4.5.3 --------------------------- Other: - Update linux kernel to 2.6.32.9 - Enable SMT (Hyperthreading) scheduler support in kernel. - Update linux udev subsystem to 1.41. - Fix problem reading USB Flash device model & serial number with some motherboads. - Added USB FTDI Single Port Serial Driver per user request. Changes from 4.5.1 to 4.5.2 --------------------------- Bug fixes: - Fix problem where device assignment via webGui could fail if device identifier is too long. Other: - Added SCST subsystem (see http://scst.sourceforge.net) in order to support Marvell 88SE63xx/64xx/68xx/94xx SAS controller-based cards. - Added 'COPYING' file in release that includes text of the GPL version 2. Changes from 4.5 to 4.5.1 ------------------------- Bug fixes: - Fix javascript bug checking valid settings on the Settings page. - Fix bug where a disk can appear 'Unformatted' immediately after array Start. - Change unmount polling rate from 1 second to 5 seconds when Stopping the array when external extensions still have a disk or use share mounted. Other: - Updated linux kernel to version 2.6.31.12 - Updated Samba to version 3.4.5 - Added Areca driver. - Added Marvell legacy PATA support. - Added USB printer support. Upgrade Instructions (Please Read Carefully) ============================================ In addition to below, if the Change log indicates 'memtest' version upgrade, please copy the following file from the new release to the root of your Flash device: memtest If you are currently running unRAID Server 4.2-beta1 or higher (including 4.2.x 'final'), please copy the following files from the new release to the root of your Flash device: bzimage bzroot If you are currently running unRAID server 4.0 or 4.1, please copy the following files from the new release to the root of your Flash device: bzimage bzroot syslinux.cfg menu.c32 memtest This can be done either by plugging the Flash into your PC or, by copying the files to the 'flash' share on your running server. The server must then be rebooted. If you are currently running unRAID Server 3.0-beta1 or higher, please follow these steps to upgrade: 1. Referring to the System Management Utility 'Main' page, make a note of each disks's model/serial number; you will need this information later. 2. Shut down your server, remove the Flash and plug it into your PC. 3. Right-click your Flash device listed under My Computer and select Properties. Make sure the volume label is set to "UNRAID" (without the quotes) and click OK. You do NOT need to format the Flash. 4. Copy the files from the new release to the root of your Flash device. 5. Right-click your Flash device listed under My Computer and select Eject. Remove the Flash, install in your server and power-up. 6. After your server has booted up, the System Management Utility 'Main' page will probably show no devices; this is OK, navigate to the 'Devices' page. Using the model/serial number information gathered in step 1, assign each of your hard drives to the correct disk slot. 7. Go back to the 'Main' page and your devices should appear correctly. You may now Start the array. Link to comment
peter_sm Posted November 30, 2010 Share Posted November 30, 2010 OK, updated, now when apply on a NFS share, the Unraid main page are not available more back to previous version..... No i can't find the prevision version... EDIT I saw this in my log file Nov 30 20:44:37 Tower emhttp: shareExportNfsFsid not found Link to comment
limetech Posted November 30, 2010 Author Share Posted November 30, 2010 OK, updated, now when apply on a NFS share, the Unraid main page are not available more back to previous version..... No i can't find the prevision version... EDIT I saw this in my log file Nov 30 20:44:37 Tower emhttp: shareExportNfsFsid not found You are clicking 'Apply' on stock unRaid webGui 'Shares' page? Link to comment
peter_sm Posted November 30, 2010 Share Posted November 30, 2010 Yes, after I added *(ro) and click apply, then i need to restart emhttp more in the log file Nov 30 21:08:54 Tower emhttp: shareExportNfsFsid not found Nov 30 21:08:54 Tower kernel: emhttp[19359]: segfault at 0 ip b74e241b sp bf83f540 error 4 in libc-2.7.so[b74b3000+146000] I also see this ,and I have never used this before ? Nov 30 21:15:07 Tower emhttp: shcmd (7): cp /var/spool/cron/crontabs/root- /var/spool/cron/crontabs/root Nov 30 21:15:07 Tower emhttp: shcmd (: echo '# Generated mover schedule:' >>/var/spool/cron/crontabs/root Nov 30 21:15:07 Tower emhttp: shcmd (9): echo '40 3 * * * /usr/local/sbin/mover 2>&1 | logger' >>/var/spool/cron/crontabs/root Syslog is attached syslog-2010-11-30.txt.zip Link to comment
limetech Posted November 30, 2010 Author Share Posted November 30, 2010 Yes, after I added *(ro) and click apply, then i need to restart emhttp more in the log file Nov 30 21:08:54 Tower emhttp: shareExportNfsFsid not found Nov 30 21:08:54 Tower kernel: emhttp[19359]: segfault at 0 ip b74e241b sp bf83f540 error 4 in libc-2.7.so[b74b3000+146000] I also see this ,and I have never used this before ? Nov 30 21:15:07 Tower emhttp: shcmd (7): cp /var/spool/cron/crontabs/root- /var/spool/cron/crontabs/root Nov 30 21:15:07 Tower emhttp: shcmd (: echo '# Generated mover schedule:' >>/var/spool/cron/crontabs/root Nov 30 21:15:07 Tower emhttp: shcmd (9): echo '40 3 * * * /usr/local/sbin/mover 2>&1 | logger' >>/var/spool/cron/crontabs/root Syslog is attached I don't see how this is possible. In the system log there are 5 of these messages at various times - is this a result of you trying to click 'Apply' for a user share 5 times? Link to comment
peter_sm Posted November 30, 2010 Share Posted November 30, 2010 Yes after I restart emhttp EDIT I'm on my MAC Link to comment
limetech Posted November 30, 2010 Author Share Posted November 30, 2010 I also see this ,and I have never used this before ? Nov 30 21:15:07 Tower emhttp: shcmd (7): cp /var/spool/cron/crontabs/root- /var/spool/cron/crontabs/root Nov 30 21:15:07 Tower emhttp: shcmd (: echo '# Generated mover schedule:' >>/var/spool/cron/crontabs/root Nov 30 21:15:07 Tower emhttp: shcmd (9): echo '40 3 * * * /usr/local/sbin/mover 2>&1 | logger' >>/var/spool/cron/crontabs/root Those are normal and always are generated if you have User Shares enabled. Link to comment
limetech Posted November 30, 2010 Author Share Posted November 30, 2010 Yes after I restart emhttp EDIT I'm on my MAC Hmm, maybe it's possible your browser is using a cached, stale copy of the 'share.htm' page. Can you please clear your browser cache, or maybe use different browser, and see if issue still happens? Link to comment
peter_sm Posted November 30, 2010 Share Posted November 30, 2010 It's the same, now I reboot my server -> add *(ro) for NFS -> apply - > and cant acess my server .... :-( Nov 30 21:42:37 Tower kernel: sd 9:0:0:0: [sdg] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB) Nov 30 21:42:37 Tower kernel: sd 9:0:0:0: [sdg] Write Protect is off Nov 30 21:42:37 Tower kernel: sd 9:0:0:0: [sdg] Mode Sense: 00 3a 00 00 Nov 30 21:42:37 Tower kernel: sd 9:0:0:0: [sdg] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Nov 30 21:42:37 Tower kernel: sdg: Nov 30 21:42:37 Tower kernel: scsi 10:0:0:0: Direct-Access ATA WDC WD15EADS-00R 01.0 PQ: 0 ANSI: 5 Nov 30 21:42:37 Tower kernel: sd 10:0:0:0: [sdh] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB) Nov 30 21:42:37 Tower kernel: sd 10:0:0:0: [sdh] Write Protect is off Nov 30 21:42:37 Tower kernel: sd 10:0:0:0: [sdh] Mode Sense: 00 3a 00 00 Nov 30 21:42:37 Tower kernel: sd 10:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Nov 30 21:42:37 Tower kernel: sdh: sdg1 Nov 30 21:42:37 Tower kernel: sd 9:0:0:0: [sdg] Attached SCSI disk Nov 30 21:42:37 Tower kernel: sdf1 Nov 30 21:42:37 Tower kernel: sd 8:0:0:0: [sdf] Attached SCSI disk Nov 30 21:42:37 Tower kernel: sde1 Nov 30 21:42:37 Tower kernel: sd 6:0:0:0: [sde] Attached SCSI disk Nov 30 21:42:37 Tower kernel: sdh1 Nov 30 21:42:37 Tower kernel: sd 10:0:0:0: [sdh] Attached SCSI disk Nov 30 21:42:37 Tower kernel: sdd1 Nov 30 21:42:37 Tower kernel: sd 5:0:0:0: [sdd] Attached SCSI disk Nov 30 21:42:37 Tower kernel: atiixp 0000:00:14.1: IDE controller (0x1002:0x439c rev 0x00) Nov 30 21:42:37 Tower kernel: ATIIXP_IDE 0000:00:14.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16 Nov 30 21:42:37 Tower kernel: atiixp 0000:00:14.1: not 100%% native mode: will probe irqs later Nov 30 21:42:37 Tower kernel: ide0: BM-DMA at 0xfa00-0xfa07 Nov 30 21:42:37 Tower kernel: atiixp 0000:00:14.1: simplex device: DMA disabled Nov 30 21:42:37 Tower kernel: ide1: DMA disabled Nov 30 21:42:37 Tower kernel: Probing IDE interface ide0... Nov 30 21:42:37 Tower kernel: scsi 0:0:0:0: Direct-Access SanDisk Cruzer 8.01 PQ: 0 ANSI: 0 CCS Nov 30 21:42:37 Tower kernel: sd 0:0:0:0: [sdi] 3907711 512-byte logical blocks: (2.00 GB/1.86 GiB) Nov 30 21:42:37 Tower kernel: sd 0:0:0:0: [sdi] Write Protect is off Nov 30 21:42:37 Tower kernel: sd 0:0:0:0: [sdi] Mode Sense: 45 00 00 08 Nov 30 21:42:37 Tower kernel: sd 0:0:0:0: [sdi] Assuming drive cache: write through Nov 30 21:42:37 Tower kernel: usb-storage: device scan complete Nov 30 21:42:37 Tower kernel: sd 0:0:0:0: [sdi] Assuming drive cache: write through Nov 30 21:42:37 Tower kernel: sdi: sdi1 Nov 30 21:42:37 Tower kernel: sd 0:0:0:0: [sdi] Assuming drive cache: write through Nov 30 21:42:37 Tower kernel: sd 0:0:0:0: [sdi] Attached SCSI removable disk Nov 30 21:42:37 Tower kernel: Probing IDE interface ide1... Nov 30 21:42:37 Tower kernel: ide1: no devices on the port Nov 30 21:42:37 Tower kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 Nov 30 21:42:37 Tower kernel: ide1 at 0x170-0x177,0x376 on irq 15 Nov 30 21:42:37 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig lo 127.0.0.1 Nov 30 21:42:37 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo Nov 30 21:42:37 Tower ifplugd(eth0)[1357]: ifplugd 0.28 initializing. Nov 30 21:42:37 Tower ifplugd(eth0)[1357]: Using interface eth0/00:24:1D:83:B5:1C with driver (version: 2.3LK-NAPI) Nov 30 21:42:37 Tower ifplugd(eth0)[1357]: Using detection mode: SIOCETHTOOL Nov 30 21:42:37 Tower ifplugd(eth0)[1357]: Initialization complete, link beat detected. Nov 30 21:42:37 Tower kernel: r8169: eth0: link up Nov 30 21:42:37 Tower kernel: r8169: eth0: link up Nov 30 21:42:37 Tower ifplugd(eth0)[1357]: Executing '/etc/ifplugd/ifplugd.action eth0 up'. Nov 30 21:42:37 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig eth0 hw ether 00:24:1D:83:B5:1C Nov 30 21:42:37 Tower logger: /etc/rc.d/rc.inet1: /sbin/ifconfig eth0 192.168.0.199 broadcast 192.168.0.255 netmask 255.255.255.0 Nov 30 21:42:37 Tower logger: /etc/rc.d/rc.inet1: /sbin/route add default gw 192.168.0.1 metric 1 Nov 30 21:42:37 Tower ntpd[1397]: ntpd [email protected] Wed Jan 14 23:46:25 UTC 2009 (1) Nov 30 21:42:37 Tower ifplugd(eth0)[1357]: client: Starting NTP daemon: /usr/sbin/ntpd -g Nov 30 21:42:37 Tower ntpd[1398]: precision = 1.000 usec Nov 30 21:42:37 Tower ntpd[1398]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 Nov 30 21:42:37 Tower ntpd[1398]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled Nov 30 21:42:37 Tower ntpd[1398]: Listening on interface #1 lo, 127.0.0.1#123 Enabled Nov 30 21:42:37 Tower ntpd[1398]: Listening on interface #2 eth0, 192.168.0.199#123 Enabled Nov 30 21:42:37 Tower ntpd[1398]: kernel time sync status 0040 Nov 30 21:42:37 Tower ntpd[1398]: frequency initialized 500.000 PPM from /etc/ntp/drift Nov 30 21:42:37 Tower ifplugd(eth0)[1357]: Program executed successfully. Nov 30 21:42:37 Tower rpc.statd[1412]: Version 1.1.4 Starting Nov 30 21:42:38 Tower in.telnetd[1457]: connect from 192.168.0.195 (192.168.0.195) Nov 30 21:42:42 Tower emhttp: unRAID System Management Utility version 4.6-rc4 Nov 30 21:42:42 Tower emhttp: Copyright (C) 2005-2010, Lime Technology, LLC Nov 30 21:42:42 Tower emhttp: Pro key detected, GUID: 0781-5406-1739-9011880382F2 Nov 30 21:42:42 Tower emhttp: shcmd (1): udevadm settle Nov 30 21:42:42 Tower emhttp: Device inventory: Nov 30 21:42:42 Tower emhttp: pci-0000:00:11.0-scsi-0:0:0:0 host5 (sdd) WDC_WD15EARS-00Z5B1_WD-WMAVU2990125 Nov 30 21:42:42 Tower emhttp: pci-0000:00:11.0-scsi-1:0:0:0 host6 (sde) WDC_WD10EADS-00L5B1_WD-WCAU4D312833 Nov 30 21:42:42 Tower emhttp: pci-0000:00:11.0-scsi-3:0:0:0 host8 (sdf) SAMSUNG_HD103UJ_S13PJ1KQ612827 Nov 30 21:42:42 Tower emhttp: pci-0000:00:11.0-scsi-4:0:0:0 host9 (sdg) WDC_WD15EADS-00S2B0_WD-WCAVY0802799 Nov 30 21:42:42 Tower emhttp: pci-0000:00:11.0-scsi-5:0:0:0 host10 (sdh) WDC_WD15EADS-00R6B0_WD-WCAVY0164770 Nov 30 21:42:42 Tower emhttp: pci-0000:02:00.0-scsi-1:0:0:0 host2 (sda) WDC_WD15EADS-00P8B0_WD-WMAVU0799207 Nov 30 21:42:42 Tower emhttp: pci-0000:02:00.0-scsi-2:0:0:0 host3 (sdb) WDC_WD10EACS-00ZJB0_WD-WCASJ1110243 Nov 30 21:42:42 Tower emhttp: pci-0000:02:00.0-scsi-3:0:0:0 host4 (sdc) WDC_WD6400AARS-00Y5B1_WD-WCAV5D365310 Nov 30 21:42:42 Tower emhttp: shcmd (2): modprobe -rw md-mod 2>&1 | logger Nov 30 21:42:42 Tower emhttp: shcmd (3): modprobe md-mod super=/boot/config/super.dat slots=8,96,8,112,8,0,8,64,0,0,8,80,8,32,8,16,8,48,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 2>&1 | logger Nov 30 21:42:42 Tower kernel: xor: automatically using best checksumming function: pIII_sse Nov 30 21:42:43 Tower kernel: pIII_sse : 11882.800 MB/sec Nov 30 21:42:43 Tower kernel: xor: using function: pIII_sse (11882.800 MB/sec) Nov 30 21:42:43 Tower emhttp: Spinning up all drives... Nov 30 21:42:43 Tower kernel: md: unRAID driver 1.1.0 installed Nov 30 21:42:43 Tower kernel: md: import disk0: [8,96] (sdg) WDC WD15EADS-00S WD-WCAVY0802799 offset: 63 size: 1465138552 Nov 30 21:42:43 Tower kernel: md: import disk1: [8,112] (sdh) WDC WD15EADS-00R WD-WCAVY0164770 offset: 63 size: 1465138552 Nov 30 21:42:43 Tower kernel: md: import disk2: [8,0] (sda) WDC WD15EADS-00P WD-WMAVU0799207 offset: 63 size: 1465138552 Nov 30 21:42:43 Tower kernel: md: import disk3: [8,64] (sde) WDC WD10EADS-00L WD-WCAU4D312833 offset: 63 size: 976762552 Nov 30 21:42:43 Tower kernel: md: import disk5: [8,80] (sdf) SAMSUNG HD103UJ S13PJ1KQ612827 offset: 63 size: 976761496 Nov 30 21:42:43 Tower kernel: md: import disk6: [8,32] (sdc) WDC WD6400AARS-0 WD-WCAV5D365310 offset: 63 size: 625131832 Nov 30 21:42:43 Tower kernel: md: import disk7: [8,16] (sdb) WDC WD10EACS-00Z WD-WCASJ1110243 offset: 63 size: 976762552 Nov 30 21:42:43 Tower kernel: md: import disk8: [8,48] (sdd) WDC WD15EARS-00Z WD-WMAVU2990125 offset: 63 size: 1465138552 Nov 30 21:42:43 Tower kernel: mdcmd (1): set md_num_stripes 1280 Nov 30 21:42:43 Tower kernel: mdcmd (2): set md_write_limit 768 Nov 30 21:42:43 Tower kernel: mdcmd (3): set md_sync_window 288 Nov 30 21:42:43 Tower kernel: mdcmd (4): set spinup_group 0 0 Nov 30 21:42:43 Tower kernel: mdcmd (5): set spinup_group 1 0 Nov 30 21:42:43 Tower kernel: mdcmd (6): set spinup_group 2 0 Nov 30 21:42:43 Tower kernel: mdcmd (7): set spinup_group 3 0 Nov 30 21:42:43 Tower kernel: mdcmd (: set spinup_group 5 0 Nov 30 21:42:43 Tower kernel: mdcmd (9): set spinup_group 6 0 Nov 30 21:42:43 Tower kernel: mdcmd (10): set spinup_group 7 0 Nov 30 21:42:43 Tower kernel: mdcmd (11): set spinup_group 8 0 Nov 30 21:42:43 Tower kernel: mdcmd (12): spinup 0 Nov 30 21:42:43 Tower kernel: mdcmd (13): spinup 1 Nov 30 21:42:43 Tower kernel: mdcmd (14): spinup 2 Nov 30 21:42:43 Tower kernel: mdcmd (15): spinup 3 Nov 30 21:42:43 Tower kernel: mdcmd (16): spinup 5 Nov 30 21:42:43 Tower kernel: mdcmd (17): spinup 6 Nov 30 21:42:43 Tower kernel: mdcmd (18): spinup 7 Nov 30 21:42:43 Tower kernel: mdcmd (19): spinup 8 Nov 30 21:42:43 Tower emhttp: shcmd (4): /usr/local/sbin/set_ncq sdg 1 >/dev/null Nov 30 21:42:43 Tower emhttp: shcmd (5): /usr/local/sbin/set_ncq sdh 1 >/dev/null Nov 30 21:42:43 Tower emhttp: shcmd (6): /usr/local/sbin/set_ncq sda 1 >/dev/null Nov 30 21:42:43 Tower emhttp: shcmd (7): /usr/local/sbin/set_ncq sde 1 >/dev/null Nov 30 21:42:43 Tower emhttp: shcmd (: /usr/local/sbin/set_ncq sdf 1 >/dev/null Nov 30 21:42:43 Tower emhttp: shcmd (9): /usr/local/sbin/set_ncq sdc 1 >/dev/null Nov 30 21:42:43 Tower emhttp: shcmd (10): /usr/local/sbin/set_ncq sdb 1 >/dev/null Nov 30 21:42:43 Tower emhttp: shcmd (11): /usr/local/sbin/set_ncq sdd 1 >/dev/null Nov 30 21:42:43 Tower kernel: mdcmd (20): start STOPPED Nov 30 21:42:43 Tower kernel: unraid: allocating 49080K for 1280 stripes (9 disks) Nov 30 21:42:43 Tower kernel: md1: running, size: 1465138552 blocks Nov 30 21:42:43 Tower kernel: md2: running, size: 1465138552 blocks Nov 30 21:42:43 Tower kernel: md3: running, size: 976762552 blocks Nov 30 21:42:43 Tower kernel: md5: running, size: 976761496 blocks Nov 30 21:42:43 Tower kernel: md6: running, size: 625131832 blocks Nov 30 21:42:43 Tower kernel: md7: running, size: 976762552 blocks Nov 30 21:42:43 Tower kernel: md8: running, size: 1465138552 blocks Nov 30 21:42:43 Tower emhttp: shcmd (12): udevadm settle Nov 30 21:42:43 Tower emhttp: shcmd (13): mkdir /mnt/disk3 Nov 30 21:42:43 Tower emhttp: shcmd (13): mkdir /mnt/disk2 Nov 30 21:42:43 Tower emhttp: shcmd (13): mkdir /mnt/disk8 Nov 30 21:42:43 Tower emhttp: shcmd (13): mkdir /mnt/disk1 Nov 30 21:42:43 Tower emhttp: shcmd (13): mkdir /mnt/disk6 Nov 30 21:42:43 Tower emhttp: shcmd (13): mkdir /mnt/disk7 Nov 30 21:42:43 Tower emhttp: shcmd (13): mkdir /mnt/disk5 Nov 30 21:42:43 Tower emhttp: shcmd (14): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md3 /mnt/disk3 2>&1 | logger Nov 30 21:42:43 Tower emhttp: shcmd (15): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md8 /mnt/disk8 2>&1 | logger Nov 30 21:42:43 Tower emhttp: shcmd (16): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md5 /mnt/disk5 2>&1 | logger Nov 30 21:42:43 Tower emhttp: shcmd (17): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md1 /mnt/disk1 2>&1 | logger Nov 30 21:42:43 Tower emhttp: shcmd (18): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md6 /mnt/disk6 2>&1 | logger Nov 30 21:42:43 Tower emhttp: shcmd (19): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md7 /mnt/disk7 2>&1 | logger Nov 30 21:42:43 Tower emhttp: shcmd (20): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md2 /mnt/disk2 2>&1 | logger Nov 30 21:42:43 Tower kernel: mdcmd (21): check Nov 30 21:42:43 Tower kernel: md: recovery thread woken up ... Nov 30 21:42:43 Tower kernel: md: recovery thread has nothing to resync Nov 30 21:42:43 Tower kernel: REISERFS (device md8): found reiserfs format "3.6" with standard journal Nov 30 21:42:43 Tower kernel: REISERFS (device md8): using ordered data mode Nov 30 21:42:43 Tower kernel: REISERFS (device md2): found reiserfs format "3.6" with standard journal Nov 30 21:42:43 Tower kernel: REISERFS (device md2): using ordered data mode Nov 30 21:42:43 Tower kernel: REISERFS (device md5): found reiserfs format "3.6" with standard journal Nov 30 21:42:43 Tower kernel: REISERFS (device md5): using ordered data mode Nov 30 21:42:43 Tower kernel: REISERFS (device md3): found reiserfs format "3.6" with standard journal Nov 30 21:42:43 Tower kernel: REISERFS (device md3): using ordered data mode Nov 30 21:42:43 Tower kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal Nov 30 21:42:43 Tower kernel: REISERFS (device md1): using ordered data mode Nov 30 21:42:43 Tower kernel: REISERFS (device md6): found reiserfs format "3.6" with standard journal Nov 30 21:42:43 Tower kernel: REISERFS (device md6): using ordered data mode Nov 30 21:42:43 Tower kernel: REISERFS (device md7): found reiserfs format "3.6" with standard journal Nov 30 21:42:43 Tower kernel: REISERFS (device md7): using ordered data mode Nov 30 21:42:43 Tower kernel: REISERFS (device md8): journal params: device md8, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Nov 30 21:42:43 Tower kernel: REISERFS (device md8): checking transaction log (md8) Nov 30 21:42:43 Tower kernel: REISERFS (device md2): journal params: device md2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Nov 30 21:42:43 Tower kernel: REISERFS (device md2): checking transaction log (md2) Nov 30 21:42:43 Tower kernel: REISERFS (device md5): journal params: device md5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Nov 30 21:42:43 Tower kernel: REISERFS (device md5): checking transaction log (md5) Nov 30 21:42:43 Tower kernel: REISERFS (device md3): journal params: device md3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Nov 30 21:42:43 Tower kernel: REISERFS (device md3): checking transaction log (md3) Nov 30 21:42:43 Tower kernel: REISERFS (device md1): journal params: device md1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Nov 30 21:42:43 Tower kernel: REISERFS (device md1): checking transaction log (md1) Nov 30 21:42:43 Tower kernel: REISERFS (device md6): journal params: device md6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Nov 30 21:42:43 Tower kernel: REISERFS (device md6): checking transaction log (md6) Nov 30 21:42:43 Tower kernel: REISERFS (device md7): journal params: device md7, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Nov 30 21:42:43 Tower kernel: REISERFS (device md7): checking transaction log (md7) Nov 30 21:42:43 Tower kernel: REISERFS (device md8): Using r5 hash to sort names Nov 30 21:42:43 Tower kernel: REISERFS (device md2): Using r5 hash to sort names Nov 30 21:42:43 Tower kernel: REISERFS (device md1): Using r5 hash to sort names Nov 30 21:42:43 Tower kernel: REISERFS (device md6): Using r5 hash to sort names Nov 30 21:42:43 Tower kernel: REISERFS (device md7): Using r5 hash to sort names Nov 30 21:42:43 Tower kernel: REISERFS (device md3): Using r5 hash to sort names Nov 30 21:42:44 Tower kernel: REISERFS (device md5): Using r5 hash to sort names Nov 30 21:42:44 Tower emhttp: shcmd (27): rm /etc/samba/smb-shares.conf >/dev/null 2>&1 Nov 30 21:42:44 Tower emhttp: _shcmd: shcmd (27): exit status: 1 Nov 30 21:42:44 Tower emhttp: shcmd (28): cp /etc/exports- /etc/exports Nov 30 21:42:44 Tower emhttp: shcmd (29): mkdir /mnt/user Nov 30 21:42:44 Tower emhttp: shcmd (30): /usr/local/sbin/shfs /mnt/user -o noatime,big_writes,allow_other,default_permissions Nov 30 21:42:44 Tower emhttp: shcmd (31): cp /var/spool/cron/crontabs/root- /var/spool/cron/crontabs/root Nov 30 21:42:44 Tower emhttp: shcmd (32): echo '# Generated mover schedule:' >>/var/spool/cron/crontabs/root Nov 30 21:42:44 Tower emhttp: shcmd (33): echo '40 3 * * * /usr/local/sbin/mover 2>&1 | logger' >>/var/spool/cron/crontabs/root Nov 30 21:42:44 Tower emhttp: shcmd (34): crontab /var/spool/cron/crontabs/root Nov 30 21:42:45 Tower shfs: duplicate object: /mnt/disk8/./.DS_Store Nov 30 21:42:45 Tower emhttp: shcmd (35): killall -HUP smbd Nov 30 21:42:45 Tower emhttp: shcmd (36): /etc/rc.d/rc.nfsd restart | logger Nov 30 21:42:47 Tower login[1458]: ROOT LOGIN on `pts/0' from `192.168.0.195' Nov 30 21:42:47 Tower apcupsd[1793]: apcupsd 3.14.3 (20 January 2008) slackware startup succeeded Nov 30 21:42:48 Tower apcupsd[1793]: NIS server startup succeeded Nov 30 21:42:51 Tower sshd[3694]: Server listening on 0.0.0.0 port 22. Nov 30 21:42:52 Tower init: Re-reading inittab Nov 30 21:42:54 Tower unmenu-status: Starting unmenu web-server Nov 30 21:43:19 Tower spinup[5950]: nohup: ignoring input Nov 30 21:43:24 Tower spin_disks[5961]: Started spinup_when_accessed.sh -m 192.168.0.197 Nov 30 21:43:24 Tower spin_disks: #============================ Spin-Disks ================================# Nov 30 21:43:24 Tower spinup[5950]: spin_disks: #============================ Spin-Disks ================================# Nov 30 21:43:24 Tower spinup[5950]: spin_disks: Invoked as: spinup_when_accessed.sh -m 192.168.0.197 Nov 30 21:43:24 Tower spin_disks: Invoked as: spinup_when_accessed.sh -m 192.168.0.197 Nov 30 21:43:24 Tower spinup[5950]: spin_disks: process ID 5965. Nov 30 21:43:24 Tower spin_disks: process ID 5965. Nov 30 21:43:24 Tower spinup[5950]: spin_disks: To terminate it, type: spinup_when_accessed.sh -q Nov 30 21:43:24 Tower spin_disks: To terminate it, type: spinup_when_accessed.sh -q Nov 30 21:43:24 Tower spinup[5950]: spin_disks: #============================ Spin-Disks ================================# Nov 30 21:43:24 Tower spin_disks: #============================ Spin-Disks ================================# Nov 30 21:43:27 Tower cache_dirs: ============================================== Nov 30 21:43:27 Tower cache_dirs: command-args=-w -B -i tvixhd1 Nov 30 21:43:27 Tower cache_dirs: vfs_cache_pressure=10 Nov 30 21:43:27 Tower cache_dirs: max_seconds=10, min_seconds=1 Nov 30 21:43:27 Tower cache_dirs: max_depth=9999 Nov 30 21:43:27 Tower cache_dirs: command=find -noleaf Nov 30 21:43:27 Tower cache_dirs: version=1.6.5 Nov 30 21:43:27 Tower cache_dirs: ---------- caching directories --------------- Nov 30 21:43:27 Tower cache_dirs: tvixhd1 Nov 30 21:43:27 Tower cache_dirs: ---------------------------------------------- Nov 30 21:43:27 Tower cache_dirs: cache_dirs process ID 6029 started, To terminate it, type: cache_dirs -q Nov 30 21:43:46 Tower emhttp: shareExportNfsFsid not found Nov 30 21:43:46 Tower kernel: emhttp[1460]: segfault at 0 ip b753d41b sp bf9e45d0 error 4 in libc-2.7.so[b750e000+146000] Link to comment
peter_sm Posted November 30, 2010 Share Posted November 30, 2010 I tryed to add a new share SAMBA and the NFS, its the same problem Nov 30 21:49:32 Tower emhttp: shcmd (14): mv '/mnt/user/Backup' '/mnt/user/Backup12' Nov 30 21:49:32 Tower emhttp: shcmd (15): mv '/boot/config/shares/Backup.cfg' '/boot/config/shares/Backup12.cfg' Nov 30 21:49:32 Tower emhttp: shcmd (16): rm /etc/samba/smb-shares.conf >/dev/null 2>&1 Nov 30 21:49:32 Tower emhttp: shcmd (17): cp /etc/exports- /etc/exports Nov 30 21:49:32 Tower shfs: duplicate object: /mnt/disk8/./.DS_Store Nov 30 21:49:32 Tower emhttp: shcmd (18): /etc/rc.d/rc.samba start | logger Nov 30 21:49:32 Tower logger: Starting Samba: /usr/sbin/nmbd -D Nov 30 21:49:32 Tower logger: /usr/sbin/smbd -D Nov 30 21:49:32 Tower emhttp: shcmd (19): /etc/rc.d/rc.nfsd start | logger Nov 30 21:49:41 Tower emhttp: shareExportNfsFsid not found Nov 30 21:49:41 Tower kernel: emhttp[8318]: segfault at 0 ip b747d41b sp bfa7c410 error 4 in libc-2.7.so[b744e000+146000] Link to comment
Meteorite Posted November 30, 2010 Share Posted November 30, 2010 could be a long shot but maybe the code doesn't check if 'shareExportNfsFsid' variable exist in the user-share config file and tries to change it (I know I happend to me when i was codeing and using ini files for a program I was working on) try to add it your self 'shareExportNfsFsid' variable in the user-share config file with a value of 100 (only for testing to see if you don't get the message after changeing the share again) Link to comment
peter_sm Posted November 30, 2010 Share Posted November 30, 2010 where is that file? and the exact name, cant find that filename EDIT Found a share.cfg file , added this line shareExportNfsFsid=100 The file looks like this shareFlash=eh^M shareDisk=eh^M shareDiskNfs=^M shareUser=e^M shareNfsFsid=100^M shareSecurity=user^M shareInitialOwner=Administrator^M shareInitialGroup="Domain Users"^M shareMoverSchedule="40 3 * * *"^M shareMoverLogging=yes^M shareCacheFloor=2000000^M shareExportNfsFsid=100^M restarted with same issue //Peter Link to comment
Meteorite Posted November 30, 2010 Share Posted November 30, 2010 where is that file? and the exact name, cant find that filename EDIT Found a share.cfg file , added this line shareExportNfsFsid=100 restarted with same issue //Peter tom says in the release notes that file contains The next fsid to be assigned is kept in the 'shareNfsFsid' config variable in the 'share.cfg' file so that is something else then shareExportNfsFsid but user-share config file toms speaks about should be at /flash/config/shares/sharename.cfg where sharename is you name you have given to a share Link to comment
peter_sm Posted November 30, 2010 Share Posted November 30, 2010 I'm back tomorrow, hope there is a solution then , have a nice day //Peter Link to comment
limetech Posted November 30, 2010 Author Share Posted November 30, 2010 Anyone else have this problem? Sorry I can not reproduce. peter_sm if you are still around - please click on the Shares page and use your browser to view the "page source" - this will be the HTML of the shares.htm page. Please select/copy/paste and post this - but this file will contain the names of all your user shares, so if you don't want that public, then send to me: [email protected] Link to comment
peter_sm Posted December 1, 2010 Share Posted December 1, 2010 Going to try more later today, but how can I reset all my shares, so I can start from scratc? //Peter Link to comment
peter_sm Posted December 1, 2010 Share Posted December 1, 2010 Tom, you have mail , attached is the share pages. //Peter Link to comment
peter_sm Posted December 1, 2010 Share Posted December 1, 2010 4.5.3 version works , now I going try try to upgrade again. //Peter Link to comment
peter_sm Posted December 1, 2010 Share Posted December 1, 2010 Tom have found the bug RC5 is on the way //Peter Link to comment
Recommended Posts