limetech Posted September 9, 2015 Share Posted September 9, 2015 Download Clicking 'Check for Updates' on the Plugins page is the preferred way to upgrade. Note: If you are using plugins, please see this thread regarding plugin support. We were able to catch a test server with a webGui hang. It was a case where emhttp got stuck in a loop consuming 100% of CPU. We were able to figure out what was causing this and thus published this release with the fix. The *mvsas* parity sync slowdown issue is still under study - no fix for that in here. I am tinkering with the Release Notes format a bit - expect more tinkering moving forward. > unRAID Server OS Change Log Version 6.1.2 2015-09-08 </pre> <ul> emhttp: fix possible infinite loop if client closes HTTP connection during POST data transmission This should fix some instances of webGui hanging. emhttp: force close smb share connections if that share security mode or access list is changed Used to be that Windows would close SMB connections shortly after last I/O to a server. These days Windows likes to keep conections open. Consequently, changing a share security mode or user access list would appear to not take effect. This change fixes that behavior. linux: add kernel options: CONFIG_SCSI_MVSAS_TASKLET: Support for interrupt tasklet The was removed to test effect on mvsas slowdown issue. Since it did not fix the issue we are restoring it. slack: added a couple terminfo mappings (user request): xterm-color xterm-256color </ul> <h2>Version 6.1.1 2015-09-06</h2> <ul>emhttp: fix: for new installations: disk share export set to 'Auto', user share export set to 'Yes' docker: fix: create initial docker template repo emhttp: for new installations: disk spindown delay set to 0 (never spin down) linux: enable kernel options: CONFIG_BLK_DEV_NVME: NVM Express block device CONFIG_USB_ACM: USB Modem (CDC ACM) support linux: remove kernel options: CONFIG_SCSI_MVSAS_TASKLET: Support for interrupt tasklet linux: patch to ignore logging those useless and harmless msr errors that flood the syslog when running VMs qemu: ovmf: firmware Date: 20150904 qemu: remove unneeded UefiShell.iso file VM Manager: noVNC: performance improvements and enhancements </ul> <h2>Version 6.1.0 2015-08-31</h2> <ul>avahi: supress "Invalid response packet from host" messages btrfs-progs: version 4.1.2 docker: less verbose logging by default docker: version 1.7.1 emhttp: bridge forward delay configurable emhttp: disk share export Yes/No/Auto support emhttp: fix problem not able to start multiple btrfs scrubs emhttp: get rid of passing arbitrary commands in URL emhttp: let Pro start regardless of attached device count emhttp: let Trial support disks in any slots emhttp: properly handle non-rotational devices standby mode (ie, 'spindown') emhttp: properly handle requests from localhost (IP address 127.0.0.1) emhttp: require credentials on all accesses, not just webGui pages gnutls: 3.3.17.1 (SSA:2015-233-01) libvirt: version 1.2.18 linux: version 4.1.5 linux: support "Lite-On IT Corp. / Plextor M6e PCI Express SSD [Marvell 88SS9183] (rev 14)", see https://lkml.org/lkml/2015/2/2/226 mover: only move objects where "Use Cache" is set to "Yes" for a share ntp: enable by default ntp: 4.2.8p3 (SSA:2015-188-03) OpenELEC: added 6.0-beta3 image (beta3 includes hdmi sound fixes for nvidia cards and corrected 'addon_url' to allow plugins in Kodi once again) OpenELEC: use readonly for openelec disk image openssl: 1.0.1p (SSA:2015-190-01) php: enable pcntl php: version 5.4.44 samba: include linux "dot" objects in directory listings samba: version 4.1.19 slack: ca-certificates version 20150426 slack: check USB Flash device upon startup (set 6th field of fstab to 1) unRAIDServer.plg: improvements in unRAID-5 update: ping google instead of local gateway to determine if network up VM Manager: allow usb devices to be used that do not have a name/desciption VM Manager: Fix: OVMF+Q35 needs the bus set to 'usb' instead of 'ide' for CD-ROMs VM Manager: support OpenELEC template VM Manager: Updated noVNC (using latest as of 8/5/15, commit 8f3c0f6) webGui: Add APCUPS summary to dashboard page webGui: Add refresh button to Docker Scrub operation webGui: added "Hide dot files" control on SMB Settings page webGUI: added banner and user thumbnail image upload support webGui: additional options for text/graphical display of Used/Free. webGui: all '#command' and 'cmd' values must reference scripts within /usr/local/emhttp/ jail. webGui: Corrected: default settings were not applied for apcupsd webGui: disable Array Stop button when mover is running webGui: enhanced report generation webGui: feedback for kool kids webGui: fix issues with uploading thumbnails, banner webGui: fix docker update regression introduced in 6.1-rc1 webGui: fixed memory max display in dashboard webGui: fix notifications not initialized on reboot webGui: force browser reload of selected scripts and css files webGui: include linux "hidden" objects in directory listings webGui: install key: accept pre-keyserver links to key files webGui: integrate latest dynamix changes; many changes, refer to github webGui: Only show docker utilization when docker is enabled webGui: rearrange columns on Main page webGui: Replace alert-box for SweetAlert (enhanced messaging) webGui: use 'ftpusers' script to define ftp users webGui: use 'agent' script to control notification agents webGui: other misc. bug fixes and improvements </ul> <h2>Version 6.0.1 2015-06-26</h2> <ul>linux: enable kernel options: CONFIG_USB_PRINTER: USB Printer support CONFIG_USB_SERIAL_CP210X: USB CP210x family of UART Bridge Controllers openssl: 1.0.1o (SSA:2015-162-01) php: 5.4.41 (SSA:2015-162-02) unRAIDServer plugin (this file): be compatible with both unRAID-5 and unRAID-6 webGui: Docker: Fix: volume mappings with apostrophes not escaping correctly webGui: integrate online feedback wget: version 1.16.3 </ul> <h2>Version 6.0.0 2015-06-15</h2> <ul>docker: set default template repo webGui: other cosmetic changes </ul> <h2>Version 6.0-rc6a</h2> <ul>docker: fix bug in docker/daemon/container.go: /etc/resolv.conf permissions should be 0644 not 0600 webGui: add 'restart' to docker context menu </ul> <h2>Version 6.0-rc6</h2> <ul>dhcpcd: update to 6.8.1 dhcpcd: put dhcpcd in background if no carrier and/or no IP address after 60 seconds docker: trigger docker inotify watches on /etc/resolve.conf emhttp: fix cache devices getting unassigned when array slot count decreased slack: create informative /etc/issue file slack: maintain /etc/hostname file slack: added 'inet' command to /root - just a symlink to /etc/rc.d/rc.inet1 webGui: Info page memory display corrections; other misc. changes webGui: other misc changes (see github) </ul> <h2>Version 6.0-rc5</h2> <ul>bonding: fix to bring ethX i/f down before adding to bond; remove dhcp delay emhttp: fix disk/share status indicators emhttp: fix flash share comment not showing up, added flash share 'fsColor' emhttp: fix possible deadlock if http connection closed with output still pending emhttp: fix single-disk cache pool not mounting after format linux: enable kernel options: CONFIG_NFT_MASQ: Netfilter nf_tables masquerade support CONFIG_NFT_REDIR: Netfilter nf_tables redirect support CONFIG_NFT_MASQ_IPV4: IPv4 masquerading support for nf_tables CONFIG_NFT_REDIR_IPV4: IPv4 redirect support for nf_tables slack: fix ntp configuration handling syslinx: fix bug where Xen menu options are present in 'default' syslinux.cfg file webGui: added symlink to /usr/local/emhttp/plugins/dynamix/scripts/diagnostics in /usr/local/sbin webGui: file browswer: do not let user traverse up the tree beyond the mount point webGui: add rollover status indicator text for array status and user/disk share status webGui: add disclaimer to Diagnostics page (3rd party plugins may or may not expose personal information) webGui: custom user thumbnail/avatars support webGui: fix docker image file delete webGui: VM Manger changes (see github) </ul> <h2>Version 6.0-rc4</h2> <ul>btrfs-progs: update to 4.0.1 emhttp: fix bug where /mnt/user0 could be mounted when slot count decreased emhttp: do not count zero-size block devices against device limits emhttp: handle querystring variables with embedded single-quotes emhttp: added comment field for disk shares libvirt: patched rc.libvirt to eliminate bogus errors output to syslog libvirt: enabled virtual port capability linux: enable kernel options: CONFIG_MACVLAN: MAC-VLAN support CONFIG_MACVTAP: MAC-VLAN based tap driver CONFIG_NF_TABLES_BRIDGE: Ethernet Bridge nf_tables support CONFIG_NFT_BRIDGE_META: Netfilter nf_table bridge meta support CONFIG_BRIDGE_NF_EBTABLES: Ethernet Bridge tables (ebtables) support CONFIG_BRIDGE_EBT_*: (19 total Ethernet bridge tables) qemu: upgraded to SeaBIOS 1.8.1 shfs: add NOCOW share support unRAIDServer plugin: preserve only "previous" release; removing current release will restore previous release webGui: fix Active Directory export settings not being active webGui: let user configure share COW flag webGui: make apcupsd driver_loaded script executable webGui: VM Manager: added Force Stop context menu option when VM is paused webGui: VM Manager: Fix: raw disk size display and adjustment capabilities webGUI: Docker: Fix: correctly calculate total data pulled stat webGUI: Docker: permit image to exist on user share webGUI: create Disk Shares page under Shares, move disk share settings webGUI: correct handling of sinqle quotes in share names webGUI: other misc changes/bug fixes </ul> <h2>Version 6.0-rc3</h2> <ul>emhttp: fix Maintenance-mode array Start emhttp: properly output 'progress' strings output by emhttp_event scripts emhttp: let Pro start regardless of attached device count linux: update to 4.0.4 (btrfs fix from 4.0.3, spinlock fix from 4.0.4, btrfs balance patch) webGui: VM Manager bug fixes webGui: integrated improvements to apcupsd component </ul> <h2>Version 6.0-rc2</h2> <ul>emhttp: restore default number of array slots to 24 (from 5 introduced in -rc1) slack: add package: patch version 2.7.4 webGui: expunge all Xen "hooks" webGui: VM Manager bug fixes (refer to commit history on github) </ul> <h2>Version 6.0-rc1</h2> <ul>docker: update to 1.6.2 webGui: support replacement keys webGui: must be Stopped to change Identifcation settings </ul Quote Link to comment
CHBMB Posted September 9, 2015 Share Posted September 9, 2015 Thanks, seems to be working great here. Webui seems a bit more responsive than 6.1.1 but that may be me Quote Link to comment
mr-hexen Posted September 9, 2015 Share Posted September 9, 2015 emhttp: force close smb share connections if that share security mode or access list is changed Used to be that Windows would close SMB connections shortly after last I/O to a server. These days Windows likes to keep conections open. Consequently, changing a share security mode or user access list would appear to not take effect. This change fixes that behavior. What affect would this have on normal shutdowns? There are some reports from earlier releases where there are several SMBd processes with a webgui hang. Quote Link to comment
NotYetRated Posted September 9, 2015 Share Posted September 9, 2015 I appear to be stuck on "syncing"... plugin: updating: unRAIDServer.plg plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.1.2-x86_64.zip ... done plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.1.2-x86_64.md5 ... done Archive: /tmp/unRAIDServer.zip inflating: /tmp/unRAIDServer/bzimage inflating: /tmp/unRAIDServer/bzroot inflating: /tmp/unRAIDServer/changes.txt creating: /tmp/unRAIDServer/config/ extracting: /tmp/unRAIDServer/config/go inflating: /tmp/unRAIDServer/config/network.cfg inflating: /tmp/unRAIDServer/config/ident.cfg creating: /tmp/unRAIDServer/config/plugins/ creating: /tmp/unRAIDServer/config/plugins/dockerMan/ extracting: /tmp/unRAIDServer/config/plugins/dockerMan/template-repos inflating: /tmp/unRAIDServer/install.txt inflating: /tmp/unRAIDServer/license.txt inflating: /tmp/unRAIDServer/make_bootable.bat inflating: /tmp/unRAIDServer/make_bootable_mac inflating: /tmp/unRAIDServer/memtest creating: /tmp/unRAIDServer/syslinux/ inflating: /tmp/unRAIDServer/syslinux/menu.c32 inflating: /tmp/unRAIDServer/syslinux/ldlinux.c32 inflating: /tmp/unRAIDServer/syslinux/syslinux.cfg- inflating: /tmp/unRAIDServer/syslinux/mbr.bin inflating: /tmp/unRAIDServer/syslinux/mboot.c32 inflating: /tmp/unRAIDServer/syslinux/syslinux.cfg inflating: /tmp/unRAIDServer/syslinux/syslinux.exe inflating: /tmp/unRAIDServer/syslinux/syslinux inflating: /tmp/unRAIDServer/syslinux/libutil.c32 inflating: /tmp/unRAIDServer/syslinux/libcom32.c32 inflating: /tmp/unRAIDServer/syslinux/make_bootable_mac.sh syncing - please wait... Quote Link to comment
jonp Posted September 9, 2015 Share Posted September 9, 2015 emhttp: force close smb share connections if that share security mode or access list is changed Used to be that Windows would close SMB connections shortly after last I/O to a server. These days Windows likes to keep conections open. Consequently, changing a share security mode or user access list would appear to not take effect. This change fixes that behavior. What affect would this have on normal shutdowns? There are some reports from earlier releases where there are several SMBd processes with a webgui hang. I'm not sure, but can tell you this fix was designed to solve an unrelated issue. Basically if you created a share that was public, wrote some data to it over SMB, then changed it to private with read only access for guest accounts, you could still write to it from the device that you did before...without authenticating. This fixed that issue. Side affects could be maybe it does help with smbd processes hung, but that's just wishful thinking. Quote Link to comment
bonienl Posted September 9, 2015 Share Posted September 9, 2015 emhttp: force close smb share connections if that share security mode or access list is changed Used to be that Windows would close SMB connections shortly after last I/O to a server. These days Windows likes to keep conections open. Consequently, changing a share security mode or user access list would appear to not take effect. This change fixes that behavior. What affect would this have on normal shutdowns? There are some reports from earlier releases where there are several SMBd processes with a webgui hang. I'm not sure, but can tell you this fix was designed to solve an unrelated issue. Basically if you created a share that was public, wrote some data to it over SMB, then changed it to private with read only access for guest accounts, you could still write to it from the device that you did before...without authenticating. This fixed that issue. Side affects could be maybe it does help with smbd processes hung, but that's just wishful thinking. Perhaps the same forced teardown approach can be (is?) done when the array goes off-line ? Quote Link to comment
Pducharme Posted September 9, 2015 Share Posted September 9, 2015 Since I upgrade to 6.1.2, my server is not responding most of the time... I have to refresh a lot, my network connectivity is intermittent. I have a Bounding for the Ethernet (eth0 and eth1), active-backup. Now, I can't access the Server GUI most of the time. I'll try disabling the bounding to see if it helps... Quote Link to comment
Pducharme Posted September 9, 2015 Share Posted September 9, 2015 Strange, a reboot seems to did the trick... but first time I have this kind of issues. I hope it won't happens again. I'll report if I see it again. Quote Link to comment
jinjorge Posted September 10, 2015 Share Posted September 10, 2015 Installed v6.1.2 via the UI update option. After the rebooting, and not realizing that all disks had been spun down, I clicked on "Check Parity" button and the disks never spun back up. I had to cancel the parity check, spin up the drives then restart the parity check. Sep 9 21:47:19 solamente avahi-daemon[2883]: Service "solamente-AFP" (/services/afp.service) successfully established. Sep 9 22:02:16 solamente kernel: mdcmd (57): spindown 10 Sep 9 22:02:17 solamente kernel: mdcmd (58): spindown 11 Sep 9 22:02:18 solamente kernel: mdcmd (59): spindown 12 Sep 9 22:02:20 solamente kernel: mdcmd (60): spindown 0 Sep 9 22:02:21 solamente kernel: mdcmd (61): spindown 1 Sep 9 22:02:22 solamente kernel: mdcmd (62): spindown 2 Sep 9 22:02:22 solamente kernel: mdcmd (63): spindown 3 Sep 9 22:02:23 solamente kernel: mdcmd (64): spindown 4 Sep 9 22:02:24 solamente kernel: mdcmd (65): spindown 5 Sep 9 22:02:24 solamente kernel: mdcmd (66): spindown 6 Sep 9 22:02:25 solamente kernel: mdcmd (67): spindown 7 Sep 9 22:02:26 solamente kernel: mdcmd (68): spindown 8 Sep 9 22:02:26 solamente kernel: mdcmd (69): spindown 9 Sep 9 22:02:27 solamente kernel: mdcmd (70): spindown 13 Sep 9 22:31:18 solamente kernel: mdcmd (71): check CORRECT Sep 9 22:31:18 solamente kernel: md: recovery thread woken up ... Sep 9 22:31:18 solamente kernel: md: recovery thread checking parity... Sep 9 22:31:18 solamente kernel: md: using 1536k window, over a total of 3907018532 blocks. Sep 9 22:33:12 solamente kernel: mdcmd (72): nocheck Sep 9 22:33:53 solamente kernel: md: md_do_sync: got signal, exit... Sep 9 22:33:54 solamente kernel: md: recovery thread sync completion status: -4 Sep 9 22:34:57 solamente emhttp: Spinning up all drives... Sep 9 22:34:57 solamente kernel: mdcmd (73): spinup 0 Sep 9 22:34:57 solamente kernel: mdcmd (74): spinup 1 Sep 9 22:34:57 solamente kernel: mdcmd (75): spinup 2 Sep 9 22:34:57 solamente kernel: mdcmd (76): spinup 3 Sep 9 22:34:57 solamente kernel: mdcmd (77): spinup 4 Sep 9 22:34:57 solamente kernel: mdcmd (78): spinup 5 Sep 9 22:34:57 solamente kernel: mdcmd (79): spinup 6 Sep 9 22:34:57 solamente kernel: mdcmd (80): spinup 7 Sep 9 22:34:57 solamente kernel: mdcmd (81): spinup 8 Sep 9 22:34:57 solamente kernel: mdcmd (82): spinup 9 Sep 9 22:34:57 solamente kernel: mdcmd (83): spinup 10 Sep 9 22:34:57 solamente kernel: mdcmd (84): spinup 11 Sep 9 22:34:57 solamente kernel: mdcmd (85): spinup 12 Sep 9 22:34:57 solamente kernel: mdcmd (86): spinup 13 Sep 9 22:35:09 solamente kernel: mdcmd (87): check CORRECT Sep 9 22:35:09 solamente kernel: md: recovery thread woken up ... Sep 9 22:35:09 solamente kernel: md: recovery thread checking parity... Sep 9 22:35:09 solamente kernel: md: using 1536k window, over a total of 3907018532 blocks. Sep 9 22:36:16 solamente emhttp: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Quote Link to comment
garycase Posted September 10, 2015 Share Posted September 10, 2015 Updated with no problem -- running a parity check now. Just read the last post ... I'll see if I have the same issue after my parity check finishes (i.e. I'll spin the drives down; confirm they're still spun down; then click on the parity check button again). Quote Link to comment
jinjorge Posted September 10, 2015 Share Posted September 10, 2015 Updated with no problem -- running a parity check now. Just read the last post ... I'll see if I have the same issue after my parity check finishes (i.e. I'll spin the drives down; confirm they're still spun down; then click on the parity check button again). Let me know what you find. Thanks!! Quote Link to comment
htpcnewbie Posted September 10, 2015 Share Posted September 10, 2015 Couple of observations: 1. I have a SASLP-MV8 and the parity check was very slow on 6.1.1, about 16.5 hrs compared to 11.5 hrs on 6.0. With this update it is back up to ~ 11.5 hrs now. 2. With the disks spun down, starting parity checks shows temps as * while there seems to be progress on parity check (went up to 0.8%, 130MB/s). I was unsure what was going on and stopped it. I spun the disks up and running parity check again. Quote Link to comment
itimpi Posted September 10, 2015 Share Posted September 10, 2015 2. With the disks spun down, starting parity checks shows temps as * while there seems to be progress on parity check (went up to 0.8%, 130MB/s). I was unsure what was going on and stopped it. I spun the disks up and running parity check again. I suspect that this is because there is a delay in detecting changes to disk status. If left then it is likely that it would have auto-corrected itself. Quote Link to comment
RobJ Posted September 10, 2015 Share Posted September 10, 2015 Installed v6.1.2 via the UI update option. After the rebooting, and not realizing that all disks had been spun down, I clicked on "Check Parity" button and the disks never spun back up. I had to cancel the parity check, spin up the drives then restart the parity check. Can you clarify why you thought the disks never spun up for the parity check? Like itimpi, I believe they did spin up and the parity check was running, but the display was not updated yet. There are a number of cases where the displayed spin state and the true spin state become out of sync, and I suspect that with this release there are even more cases now. One small change that would help is keeping the display of reads and writes updated. Since they are 'in memory' quantities, accessing them shouldn't affect anything. And any change in them could trigger a re-sync of spin state (and temps display). And a user could see from the reads and writes that the drive IS spinning, active, and know to wait for the spin state to be updated too. Quote Link to comment
RobJ Posted September 10, 2015 Share Posted September 10, 2015 Couple of observations: 1. I have a SASLP-MV8 and the parity check was very slow on 6.1.1, about 16.5 hrs compared to 11.5 hrs on 6.0. With this update it is back up to ~ 11.5 hrs now. There are a couple of known issues currently affecting parity check performance. One is the SAS2LP issus which you don't have, but the other is the 'CPU bound' issue, where something pegs the CPU at 100% and every operation is severely impacted. I suspect that was the problem with your parity check speeds, and with the fix for that in this release, your parity checks have benefited. 2. With the disks spun down, starting parity checks shows temps as * while there seems to be progress on parity check (went up to 0.8%, 130MB/s). I was unsure what was going on and stopped it. I spun the disks up and running parity check again. I agree with itimpi, I think it is another case of out-of-sync display of spin state. The disks were spun up but the display was not yet updated. The action of spinning up the drives tells the display that they ARE spun up. Quote Link to comment
JorgeB Posted September 10, 2015 Share Posted September 10, 2015 Couple of observations: 1. I have a SASLP-MV8 and the parity check was very slow on 6.1.1, about 16.5 hrs compared to 11.5 hrs on 6.0. With this update it is back up to ~ 11.5 hrs now. There are a couple of known issues currently affecting parity check performance. One is the SAS2LP issus which you don't have, but the other is the 'CPU bound' issue, where something pegs the CPU at 100% and every operation is severely impacted. I suspect that was the problem with your parity check speeds, and with the fix for that in this release, your parity checks have benefited. Maybe because CONFIG_SCSI_MVSAS_TASKLET was disabled in 6.1.1 and re-enabled in 6.1.2, it didn’t make any obvious difference on the SAS2LP but it could degrade the SASLP performance. Quote Link to comment
limetech Posted September 10, 2015 Author Share Posted September 10, 2015 Couple of observations: 1. I have a SASLP-MV8 and the parity check was very slow on 6.1.1, about 16.5 hrs compared to 11.5 hrs on 6.0. With this update it is back up to ~ 11.5 hrs now. There are a couple of known issues currently affecting parity check performance. One is the SAS2LP issus which you don't have, but the other is the 'CPU bound' issue, where something pegs the CPU at 100% and every operation is severely impacted. I suspect that was the problem with your parity check speeds, and with the fix for that in this release, your parity checks have benefited. Maybe because CONFIG_SCSI_MVSAS_TASKLET was disabled in 6.1.1 and re-enabled in 6.1.2, it didn’t make any obvious difference on the SAS2LP but it could degrade the SASLP performance. Yup. Quote Link to comment
garycase Posted September 10, 2015 Share Posted September 10, 2015 ... I clicked on "Check Parity" button and the disks never spun back up. I had to cancel the parity check, spin up the drives then restart the parity check. I tested this and found the following ... If you spin all the disks down; then start a parity check, it APPEARS as if they're still spun down (i.e. no temperature shown on the Main screen) => but they ARE spinning, as the parity check proceeds just fine ... the rate is normal and the "Current Position" continues to advance until it's done. Although the temperatures aren't displayed, the drive symbol changes from the gray ball of a spun down disk to a green ball. And, interestingly, BOTH the SpinUp and SpinDown buttons are grayed out (i.e. not available) during the parity check. Another anomaly => at some point (I THINK it was when the parity check got past the size of my data drives and only the parity drive was involved in the test ... but I can't say for certain) the temperatures started being reported => I refreshed frequently during the first 25% or so of the check, and the temps were never displayed. But when I next refreshed the check was well past the size of the data drives [my test server has 2 80GB data drives and a 250GB parity] and the temperatures were displayed. However, both the SpinUp and SpinDown buttons remained grayed out and wouldn't do anything. When the parity check finished, the SpinUp and SpinDown buttons were available again. Quote Link to comment
bonienl Posted September 10, 2015 Share Posted September 10, 2015 When the parity check finished, the SpinUp and SpinDown buttons were available again. This behavior was introduced with Dynamix - as long as a parity operation is running the spin up/down buttons are disabled. There is no reference with the actual spin state of the drives. Quote Link to comment
garycase Posted September 10, 2015 Share Posted September 10, 2015 I thought that was likely the case. So the only issue with 6.1.2 is the lack of temperature display for the drives. Quote Link to comment
bonienl Posted September 10, 2015 Share Posted September 10, 2015 Wow, you are running version 6.2 already Quote Link to comment
JonathanM Posted September 10, 2015 Share Posted September 10, 2015 I thought that was likely the case. So the only issue with 6.2 is the lack of temperature display for the drives. So how are you liking the dual parity so far? Quote Link to comment
garycase Posted September 10, 2015 Share Posted September 10, 2015 Mistake fixed 8) [but I AM looking forward to dual parity ... hopefully in 6.2 ] Quote Link to comment
jinjorge Posted September 10, 2015 Share Posted September 10, 2015 Installed v6.1.2 via the UI update option. After the rebooting, and not realizing that all disks had been spun down, I clicked on "Check Parity" button and the disks never spun back up. I had to cancel the parity check, spin up the drives then restart the parity check. Can you clarify why you thought the disks never spun up for the parity check? Like itimpi, I believe they did spin up and the parity check was running, but the display was not updated yet. There are a number of cases where the displayed spin state and the true spin state become out of sync, and I suspect that with this release there are even more cases now. One small change that would help is keeping the display of reads and writes updated. Since they are 'in memory' quantities, accessing them shouldn't affect anything. And any change in them could trigger a re-sync of spin state (and temps display). And a user could see from the reads and writes that the drive IS spinning, active, and know to wait for the spin state to be updated too. In my case I don't think the disks were spun up because the time to complete the parity check kept going up and that's what made me stop the check. From what I can recall, I saw 359 days, then jumped up to 4000+ days < yup, crazy!! Quote Link to comment
garycase Posted September 10, 2015 Share Posted September 10, 2015 ... In my case I don't think the disks were spun up because the time to complete the parity check kept going up and that's what made me stop the check. From what I can recall, I saw 359 days, then jumped up to 4000+ days < yup, crazy!! Very interesting. You might try it again ... i.e. spin down all the drives; then click on the parity check button. See if the drive symbols change from a gray dot to a green dot (which indicates they're spun up). Quote Link to comment
Recommended Posts
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.