interwebtech Posted February 25, 2015 Share Posted February 25, 2015 updated to 14a, no problems to report. I am getting 3 SMART notifications popup, 1 green, 2 orange. I'm not clear what the two orange are trying to tell me. These two drives are oldish 2TB drives scavenged from previous storage solution (e-sata RAID boxes). They are slated to be replaced as soon as current 6TB gets filled up. unRAID Disk 10 SMART health [188]: 24-02-2015 22:12 Warning [TOWER] - command timeout is 1 ST32000542AS_6XW026QQ (sdo) × unRAID Disk 11 SMART health [188]: 24-02-2015 22:12 Warning [TOWER] - command timeout is 65537 ST32000542AS_6XW00VCD (sdn) Quote Link to comment
PeterB Posted February 25, 2015 Share Posted February 25, 2015 Similar experience here, with erroneous display of drive status. I was restoring my 'cache only' shares, which had been moved to disk1, running mc in an ssh session. Having already copied 1GB of data to the cache drive, I refreshed the 'Cache Devices' tab via the browser reload button. Cache drive is still shown with a grey blob, but I can see the physical light for the drive flickering like mad. unRAID GUI is definitely lying! Quote Link to comment
HellDiverUK Posted February 25, 2015 Share Posted February 25, 2015 As of beta14, pointing to a docker image through a user share is not supported. Please update your docker image location field to point to the actual disk device used for your docker image file (e.g. /mnt/cache/docker.img or /mnt/disk#/docker.img; substitute # for the actual disk number that the image is on). I have Docker on a SNAP mounted disk - does this affect me? It's at /mnt/disk/docker/docker.img Quote Link to comment
cirkator Posted February 25, 2015 Share Posted February 25, 2015 Want to add a question regarding SNAP. My docker.img is on a ext4 formated SNAP mounted drive. Will I have to recreate my docker.img? Quote Link to comment
itimpi Posted February 25, 2015 Share Posted February 25, 2015 Similar experience here, with erroneous display of drive status. I was restoring my 'cache only' shares, which had been moved to disk1, running mc in an ssh session. Having already copied 1GB of data to the cache drive, I refreshed the 'Cache Devices' tab via the browser reload button. Cache drive is still shown with a grey blob, but I can see the physical light for the drive flickering like mad. unRAID GUI is definitely lying! I wonder if this is related to the change to the Tunable (poll_attributes): value under Settings->Disk settings having its default value increased to reduce smartctl invocation frequency to improve disk performance? Perhaps the GUI does not get its value updated until this timer expires? If so then there needs to be a way to get the values 'now' when the GUI needs it. I guess one way to check is to wait long enough for that timer to expire and then see if the GUI now reflects the settings. One can also experiment with reducing the value from the default to see if that helps? Quote Link to comment
itimpi Posted February 25, 2015 Share Posted February 25, 2015 I notice that I am getting notifications of a parity disk error on a system that does not have a parity disk assigned! Surely this should not happen? Quote Link to comment
PeterB Posted February 25, 2015 Share Posted February 25, 2015 I wonder if this is related to the change to the Tunable (poll_attributes): value under Settings->Disk settings having its default value increased to reduce smartctl invocation frequency to improve disk performance? Perhaps the GUI does not get its value updated until this timer expires? Perhaps. Even as my copy finished, the cache drive was still shown as not spinning. However, a little while later, I noted that the cache had acquired a green blob. I do not believe that anything else should have been accessing the cache. Quote Link to comment
limetech Posted February 25, 2015 Author Share Posted February 25, 2015 The spinning status got broken and the notifications are a bit chatty... -beta14b on the way. Quote Link to comment
sparklyballs Posted February 25, 2015 Share Posted February 25, 2015 The spinning status got broken and the notifications are a bit chatty... -beta14b on the way. betas are getting like buses lol. wait all day for one and then 3 come along at once. Quote Link to comment
SSD Posted February 25, 2015 Share Posted February 25, 2015 The spinning status got broken and the notifications are a bit chatty... -beta14b on the way. betas are getting like buses lol. wait all day for one and then 3 come along at once. This is not so unusual. There are frequently quick runs of betas while issues are resolved. Once at the end of such a cycle, a "stable beta" emerges. It is not usual to see such a stable beta to remain for a long period of time while the next set of enhancements are completed and the cycle begins again. I believe that you will see the next stable beta quickly give rise to short set of RCs (release candidates) and then a final release. I know that Limetech highly values the beta testers that help run unRAID through its paces. It is impossible for them to test with the diversity of hardware, software and use cases that even a small set of beta testers can generate. Quote Link to comment
Frank1940 Posted February 25, 2015 Share Posted February 25, 2015 Same here. I think that its a rather innovative solution to the spin down problem But in my case, no amount of refreshing (or clearing browser cache and refreshing) would show the disk as being spun up. I tried adding poll_spindown="10" to disk.cfg, but the file is overwritten every reboot. Now it is showing disk 1 as spunup but the syslog is showing it as spun down. After I examining the server, I reasonably convinced that the drive is spundown. This appears to be confirmed in the portion of syslog below: Feb 24 18:38:30 Rose emhttp: shcmd (31): :>/etc/samba/smb-shares.conf Feb 24 18:38:30 Rose avahi-daemon[2427]: Files changed, reloading. Feb 24 18:38:30 Rose emhttp: Restart SMB... Feb 24 18:38:30 Rose emhttp: shcmd (32): killall -HUP smbd Feb 24 18:38:30 Rose emhttp: shcmd (33): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service Feb 24 18:38:30 Rose avahi-daemon[2427]: Files changed, reloading. Feb 24 18:38:30 Rose avahi-daemon[2427]: Service group file /services/smb.service changed, reloading. Feb 24 18:38:30 Rose emhttp: shcmd (34): pidof rpc.mountd &> /dev/null Feb 24 18:38:30 Rose emhttp: shcmd (35): /etc/rc.d/rc.atalk status Feb 24 18:38:30 Rose rc.unRAID[2579][2580]: Processing /etc/rc.d/rc.unRAID.d/ start scripts. Feb 24 18:38:30 Rose avahi-daemon[2427]: Service "Rose" (/services/ssh.service) successfully established. Feb 24 18:38:30 Rose avahi-daemon[2427]: Service "Rose" (/services/sftp-ssh.service) successfully established. Feb 24 18:38:31 Rose avahi-daemon[2427]: Service "Rose" (/services/smb.service) successfully established. Feb 24 18:39:38 Rose php: /usr/local/sbin/notify cron-init Feb 24 19:08:30 Rose kernel: mdcmd (35): spindown 0 Feb 24 19:08:38 Rose kernel: mdcmd (36): spindown 1 Feb 24 19:08:39 Rose kernel: mdcmd (37): spindown 2 Feb 24 22:37:36 Rose kernel: mdcmd (38): spindown 2 Feb 24 22:39:28 Rose kernel: mdcmd (39): spindown 1 I have attached the complete syslog for analysis if needed. OK, this morning when I got up, it was apparent that I made an error when I said (Last night) Disk 1 was actually spun down! (The syslog-- see quoted text -- said it was and I could not feel any vibration to indicate that it was spinning.) The status E-mail (sent a little after midnight) said it was spun up with a temperature of 32C. The temperature last night around 10:00 was 34C. The GUI this morning showed a temperature of 30C. So unless the GUI is generating random number that make sense, Disk 1 is ACTUALLY spinning! This is the first time that I have had a Disk not spin down. I have attached a screen capture and a new syslog. EDIT: It did spin down manually. syslog.txt Quote Link to comment
sparklyballs Posted February 25, 2015 Share Posted February 25, 2015 The spinning status got broken and the notifications are a bit chatty... -beta14b on the way. betas are getting like buses lol. wait all day for one and then 3 come along at once. This is not so unusual. There are frequently quick runs of betas while issues are resolved. Once at the end of such a cycle, a "stable beta" emerges. It is not usual to see such a stable beta to remain for a long period of time while the next set of enhancements are completed and the cycle begins again. I believe that you will see the next stable beta quickly give rise to short set of RCs (release candidates) and then a final release. I know that Limetech highly values the beta testers that help run unRAID through its paces. It is impossible for them to test with the diversity of hardware, software and use cases that even a small set of beta testers can generate. it wasn't a criticism, just an awful attempt at a witticism. Quote Link to comment
jonp Posted February 25, 2015 Share Posted February 25, 2015 As of beta14, pointing to a docker image through a user share is not supported. Please update your docker image location field to point to the actual disk device used for your docker image file (e.g. /mnt/cache/docker.img or /mnt/disk#/docker.img; substitute # for the actual disk number that the image is on). I have Docker on a SNAP mounted disk - does this affect me? It's at /mnt/disk/docker/docker.img Want to add a question regarding SNAP. My docker.img is on a ext4 formated SNAP mounted drive. Will I have to recreate my docker.img? Please read the bottom part of the OP where my comments are listed. This question is addressed therein. Quote Link to comment
WeeboTech Posted February 25, 2015 Share Posted February 25, 2015 Noticed the following this morning. Alerts on temperature. In gui I have temperature monitor set to Celsius warning 45 critical 55 7:20 am Event: unRAID Status Subject: Notice [uNRAIDB] - array health report [FAIL] Description: Array has 7 disks (including parity) Importance: alert Parity - HGST_HDN726060ALE610_NAG1DEKP (sdi) - active 97° (disk is overheated) [NOK] Disk 1 - ST3000DM001-1CH166_W1F1GTFJ (sdc) - active 86° (disk is overheated) [NOK] Disk 2 - ST3000DM001-1CH166_Z1F2WFKV (sdf) - active 88° (disk is overheated) [NOK] Disk 3 - ST4000VN000-1H4168_S3012W7N (sdg) - active 86° (disk is overheated) [NOK] Disk 4 - HGST_HDN726060ALE610_NAG1D7TP (sdj) - active 95° (disk is overheated) [NOK] Disk 5 - ST6000DX000-1H217Z_Z4D0EE7M (sdd) - active 97° (disk is overheated) [NOK] Disk 6 - ST6000DX000-1H217Z_Z4D0EEDV (sde) - active 99° (disk is overheated) [NOK] Feb 25 07:35:38 unRAIDb kernel: mdcmd (28): spindown 0 Feb 25 07:35:38 unRAIDb kernel: mdcmd (29): spindown 1 Feb 25 07:35:38 unRAIDb kernel: mdcmd (30): spindown 2 Feb 25 07:35:39 unRAIDb kernel: mdcmd (31): spindown 3 Feb 25 07:35:39 unRAIDb kernel: mdcmd (32): spindown 4 Feb 25 07:35:39 unRAIDb kernel: mdcmd (33): spindown 5 Feb 25 07:35:40 unRAIDb kernel: mdcmd (34): spindown 6 7:36am Event: unRAID inactive array Subject: Notice [uNRAIDB] - array turned inactive Description: Array has 0 active disks Importance: normal 8:20am Event: unRAID Status Subject: Notice [uNRAIDB] - array health report [FAIL] Description: Array has 7 disks (including parity) Importance: alert Parity - HGST_HDN726060ALE610_NAG1DEKP (sdi) - standby (disk is overheated) [NOK] Disk 1 - ST3000DM001-1CH166_W1F1GTFJ (sdc) - standby (disk is overheated) [NOK] Disk 2 - ST3000DM001-1CH166_Z1F2WFKV (sdf) - standby (disk is overheated) [NOK] Disk 3 - ST4000VN000-1H4168_S3012W7N (sdg) - standby (disk is overheated) [NOK] Disk 4 - HGST_HDN726060ALE610_NAG1D7TP (sdj) - standby (disk is overheated) [NOK] Disk 5 - ST6000DX000-1H217Z_Z4D0EE7M (sdd) - standby (disk is overheated) [NOK] Disk 6 - ST6000DX000-1H217Z_Z4D0EEDV (sde) - standby (disk is overheated) [NOK] I would like to add, I noticed the dash board smart indication shows 0 reallocated sectors which is good, I would ask that pending sectors also be visible in that pop up. re-allocated sectors are sectors that have already been taken care of by a read error/wrote reallocate. When these numbers grow rapidly or are of high value there's an issue. Pending sectors are just as important if not more. Since reallocated sectors are taken care of, they are not as critical to a rebuild. Chances of a rebuild failing with a pending sector are high. You only need one that the drive cannot deal with accurately via retries. During my double drive failure there was only 1 pending sector preventing the rebuild from occurring. So I would ask that this count be exposed in the same popup text. Quote Link to comment
HellDiverUK Posted February 25, 2015 Share Posted February 25, 2015 Green Thumbs up SMART should display temp. Only reallocated sectors if it's orange or red. None of my drives have bad sectors, but I'd like to know the temp without having to go in to the array page. Yes, I know temp isn't displayed when the drive is spun down, but at least when it is up temp is more useful to me than bad sectors. If a drive has bad sectors, it's outta there. Quote Link to comment
WeeboTech Posted February 25, 2015 Share Posted February 25, 2015 Green Thumbs up SMART should display temp. Only reallocated sectors if it's orange or red. None of my drives have bad sectors, but I'd like to know the temp without having to go in to the array page. Yes, I know temp isn't displayed when the drive is spun down, but at least when it is up temp is more useful to me than bad sectors. If a drive has bad sectors, it's outta there. I don't see any reason why all three of these values could not be displayed in that popup. However there is a heat alarm section, Perhaps utilize that area with a thumb and pop up value. Quote Link to comment
CHBMB Posted February 25, 2015 Share Posted February 25, 2015 At some point it would appear my drive that wouldn't spin down, has decided to behave itself.... I have no idea why?? Quote Link to comment
trurl Posted February 25, 2015 Share Posted February 25, 2015 Noticed the following this morning. Alerts on temperature. In gui I have temperature monitor set to Celsius warning 45 critical 55 7:20 am Event: unRAID Status Subject: Notice [uNRAIDB] - array health report [FAIL] Description: Array has 7 disks (including parity) Importance: alert Parity - HGST_HDN726060ALE610_NAG1DEKP (sdi) - active 97° (disk is overheated) [NOK] Disk 1 - ST3000DM001-1CH166_W1F1GTFJ (sdc) - active 86° (disk is overheated) [NOK] Disk 2 - ST3000DM001-1CH166_Z1F2WFKV (sdf) - active 88° (disk is overheated) [NOK] Disk 3 - ST4000VN000-1H4168_S3012W7N (sdg) - active 86° (disk is overheated) [NOK] Disk 4 - HGST_HDN726060ALE610_NAG1D7TP (sdj) - active 95° (disk is overheated) [NOK] Disk 5 - ST6000DX000-1H217Z_Z4D0EE7M (sdd) - active 97° (disk is overheated) [NOK] Disk 6 - ST6000DX000-1H217Z_Z4D0EEDV (sde) - active 99° (disk is overheated) [NOK] Feb 25 07:35:38 unRAIDb kernel: mdcmd (28): spindown 0 Feb 25 07:35:38 unRAIDb kernel: mdcmd (29): spindown 1 Feb 25 07:35:38 unRAIDb kernel: mdcmd (30): spindown 2 Feb 25 07:35:39 unRAIDb kernel: mdcmd (31): spindown 3 Feb 25 07:35:39 unRAIDb kernel: mdcmd (32): spindown 4 Feb 25 07:35:39 unRAIDb kernel: mdcmd (33): spindown 5 Feb 25 07:35:40 unRAIDb kernel: mdcmd (34): spindown 6 7:36am Event: unRAID inactive array Subject: Notice [uNRAIDB] - array turned inactive Description: Array has 0 active disks Importance: normal 8:20am Event: unRAID Status Subject: Notice [uNRAIDB] - array health report [FAIL] Description: Array has 7 disks (including parity) Importance: alert Parity - HGST_HDN726060ALE610_NAG1DEKP (sdi) - standby (disk is overheated) [NOK] Disk 1 - ST3000DM001-1CH166_W1F1GTFJ (sdc) - standby (disk is overheated) [NOK] Disk 2 - ST3000DM001-1CH166_Z1F2WFKV (sdf) - standby (disk is overheated) [NOK] Disk 3 - ST4000VN000-1H4168_S3012W7N (sdg) - standby (disk is overheated) [NOK] Disk 4 - HGST_HDN726060ALE610_NAG1D7TP (sdj) - standby (disk is overheated) [NOK] Disk 5 - ST6000DX000-1H217Z_Z4D0EE7M (sdd) - standby (disk is overheated) [NOK] Disk 6 - ST6000DX000-1H217Z_Z4D0EEDV (sde) - standby (disk is overheated) [NOK] I would like to add, I noticed the dash board smart indication shows 0 reallocated sectors which is good, I would ask that pending sectors also be visible in that pop up. re-allocated sectors are sectors that have already been taken care of by a read error/wrote reallocate. When these numbers grow rapidly or are of high value there's an issue. Pending sectors are just as important if not more. Since reallocated sectors are taken care of, they are not as critical to a rebuild. Chances of a rebuild failing with a pending sector are high. You only need one that the drive cannot deal with accurately via retries. During my double drive failure there was only 1 pending sector preventing the rebuild from occurring. So I would ask that this count be exposed in the same popup text. Don't know about the temps. I have the same settings and it seems to be working OK for me. As for the SMART stuff, see here Also, some of this can be configured in Notification Settings, Advanced View. Quote Link to comment
GHunter Posted February 25, 2015 Share Posted February 25, 2015 My update to beta 14a went fine. My drives are spinning down normally too. I'm having some webGUI issues where it seems to hang. I think it might be related to setting the page update frequency to real time under the display settings but I haven't done enough testing with it to be sure. webGUI doesn't seem to be hanging with the page update frequency set to disabled. I'll have to test more. I'm also seeing the status on the main page and dashboard page as spun down when it is really spun up. I noticed this with page update frequency set to disabled. I need to test more on this too. One other thing I have been seeing (since beta 13?) is my notification email for "array is active" is missing disk 1 and 2. This is consistent where this email never has disk 1 and 2 included in it. Here is the contents of the email and syslog attached: Event: unRAID active array Subject: Notice [FILESVR] - array is active Description: Array has 9 active disks (including parity & cache) Importance: normal Parity disk - ST3000DM001-1CH166_W1F1WJCM (sdb) (30 C) Disk 3 - ST3000DM001-1ER166_W500JBH3 (sdf) (27 C) Disk 4 - WDC_WD20EARS-00MVWB0_WD-WMAZA3888280 (sdg) (26 C) Disk 5 - ST3000DM001-1CH166_Z1F4AP89 (sdl) (29 C) Disk 6 - ST3000DM001-1ER166_Z5007S1K (sdk) (28 C) Disk 7 - ST3000DM001-1CH166_W1F1WJ9Y (sdj) (30 C) Disk 8 - ST3000DM001-1CH166_W1F1WHCQ (sdi) (29 C) Disk 9 - WDC_WD20EARS-00MVWB0_WD-WCAZA4999014 (sdm) (23 C) Cache disk - WDC_WD6400AAKS-00A7B0_WD-WMASY1070643 (sdc) (32 C) Gary syslog.zip Quote Link to comment
bonienl Posted February 25, 2015 Share Posted February 25, 2015 One other thing I have been seeing (since beta 13?) is my notification email for "array is active" is missing disk 1 and 2. This is consistent where this email never has disk 1 and 2 included in it. Here is the contents of the email and syslog attached: Found the bug and corrected it ! Thanks for testing. Quote Link to comment
heffe2001 Posted February 25, 2015 Share Posted February 25, 2015 Have an issue with one of my drives (non-array drive used for KVM vm files). It's showing temperatures way higher than anything could possible be: It's currently showing the drive at 30064771073c, a bit hotter than I would expect anything in a PC to be, and be able to survive for more than a nanosecond, lol. When I bring up smartctl stats on the drive, I have one temp celcius that shows (I'm thinking correctly) 26c (ID# 194), and another further down that shows the bad number above (ID#231). Is Unraid just pulling out the last Temperature_Celcius number that smartctl prints and using that for the drive, or is it polling for a specific id# smart stat? I've also had a few issues with docker hanging the webui, and it's pretty repeatable on my system. It involves being inside a running docker container with the 'docker exec -it CONT# bash' command. If you're in a docker with that in a shell/console, and through the webui shut it down, it makes the UI almost completely unresponsive, if you do get it to respond, the docker in question is stuck between running and not (you get bumped out of the docker container, and the console-level docker controls won't let you stop/start or access it at all), and the unraid Docker UI shows it still running, but you can't stop or start it. A server restart is required to get it running/responding again. I don't think this is so much an issue with Unraid as it is docker in general, but it may be something to look into. Don't have any logs for this one, but on my system it's pretty easily repeatable, so I can provide them if need-be. Quote Link to comment
limetech Posted February 25, 2015 Author Share Posted February 25, 2015 Have an issue with one of my drives (non-array drive used for KVM vm files). It's showing temperatures way higher than anything could possible be: Have you considered moving your server off of the surface of the sun? Barring that, please post the output of 'smartctl -A /dev/<name>' Quote Link to comment
heffe2001 Posted February 25, 2015 Share Posted February 25, 2015 Definitely got a laugh out of the first part of that reply, lol. root@media01:~# smartctl -A /dev/sdk smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.18.5-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x0032 095 095 050 Old_age Always - 236317571 5 Reallocated_Sector_Ct 0x0033 100 100 003 Pre-fail Always - 0 9 Power_On_Hours 0x0032 095 095 000 Old_age Always - 5036 (97 92 0) 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 13 171 Unknown_Attribute 0x000a 100 100 000 Old_age Always - 0 172 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 174 Unknown_Attribute 0x0030 000 000 000 Old_age Offline - 6 177 Wear_Leveling_Count 0x0000 000 000 000 Old_age Offline - 166 181 Program_Fail_Cnt_Total 0x000a 100 100 000 Old_age Always - 0 182 Erase_Fail_Count_Total 0x0032 100 100 000 Old_age Always - 0 187 Reported_Uncorrect 0x0012 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0000 026 036 000 Old_age Offline - 26 (Min/Max 17/36) 194 Temperature_Celsius 0x0022 026 036 000 Old_age Always - 26 (Min/Max 17/36) 195 Hardware_ECC_Recovered 0x001c 120 120 000 Old_age Offline - 236317571 196 Reallocated_Event_Count 0x0033 100 100 003 Pre-fail Always - 0 201 Unknown_SSD_Attribute 0x001c 120 120 000 Old_age Offline - 236317571 204 Soft_ECC_Correction 0x001c 120 120 000 Old_age Offline - 236317571 230 Unknown_SSD_Attribute 0x0013 100 100 000 Pre-fail Always - 100 231 Temperature_Celsius 0x0013 098 098 010 Pre-fail Always - 30064771073 233 Media_Wearout_Indicator 0x0032 000 000 000 Old_age Always - 32168 234 Unknown_Attribute 0x0032 000 000 000 Old_age Always - 3797 241 Total_LBAs_Written 0x0032 000 000 000 Old_age Always - 3797 242 Total_LBAs_Read 0x0032 000 000 000 Old_age Always - 740 root@media01:~# smartctl -i /dev/sdk smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.18.5-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: MKNSSDCR480GB-7 Serial Number: MK140624AS1435904 LU WWN Device Id: 0 000120 000000000 Firmware Version: 580ABBF0 User Capacity: 480,103,981,056 bytes [480 GB] Sector Size: 512 bytes logical/physical Rotation Rate: Solid State Device Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ATA8-ACS, ACS-2 T13/2015-D revision 3 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Wed Feb 25 18:36:44 2015 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled Quote Link to comment
BobPhoenix Posted February 26, 2015 Share Posted February 26, 2015 Mushkin SSD correct? I've got one that doesn't report valid temps either. I ignore temps (on my Windows OSs don't have any SSDs on unRAID) on SSDs for that reason since it appears some don't report temps correctly. If unRAID could determine spinner or SSD then I think it should just ignore anything returned for a temp on an SSD. Quote Link to comment
GHunter Posted February 26, 2015 Share Posted February 26, 2015 One other thing I have been seeing (since beta 13?) is my notification email for "array is active" is missing disk 1 and 2. This is consistent where this email never has disk 1 and 2 included in it. Here is the contents of the email and syslog attached: Found the bug and corrected it ! Thanks for testing. Thanks. This issue is fixed in beta 14b. Gary 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.