November 17, 20178 yr Upgrading: We have changed the way one checks for new unRAID OS releases. Please refer to Update OS below. Bugs: If you want to report an issue, please start a new topic in this board. This is a bug-fix/improvement release. Notable changes (-rc12a): None, just bug fixes, well updated linux kernel minor patch release Notable changes (-rc11i): Let's Encrypt SSL certificate renewal: if your certificate is within 30 days of expiration the Renew button on Settings/Identification/SSLCertificate Settings page will be enabled. LE certs have a lifetime of 90 days but it's free to renew. We are working on a configurable daemon to make this automatic. All encryption passphrase/keyfile handling is managed on the Main page. For now the Encryption Settings page is gone but will eventually return as a way of changing the default cipher settings. Also gone is the Restricted Start setting introduced in the last release (bad idea). Yet another attempt to reliably report NVMe temperatures. Notable changes (-rc10b): Finally looks like the AMD Ryzen GPU pass-through performance issue has been solved. We applied this patch and it does indeed appear to solve the problem. Fixed issue in the 'mover' where it wasn't handling split-levels correctly in moving files from cache to array. Further refinements in handling encryption keyfile. Added new config setting Settings/Disk Settings/Restricted Start [Yes/No]. When set to Yes, array will not Start if there are encrypted volumes and the encryption key is missing (this is the default). If set to No and encryption key is missing, array will Start but encrypted volumes will not be Mounted and also cannot be Formatted - any share data stored therein simply won't be available. After attempted array Start with missing/wrong keyfile, you can enter the passphrase/upload keyfile directly from Main page. If there are any encrypted volumes in your server, we recommend setting "Settings/Disk Settings/Enable auto start" to Yes. Following boot of course there will be no keyfile present so autostart will fail. But in this case s/w also now knows there are encrypted devices and you will see right on the Main page a place to enter the encryption passphrase or upload a keyfile. Numerous package updates, bug fixes and webGui enhancements. Notable changes (-rc9f): Improved handling of encryption passphrase/keyfile. When Starting array with encrypted volumes, you only need to enter the encryption passphrase once on the Encryption Settings page - no more confusing "passphrase confirmation". If no encrypted devices exist and you're trying to add some, then it will ask for passphrase confirmation. Introduce new Disk Setting called 'Restricted Start - Yes/No'. When set to 'Yes' then array will not Start if the encryption key is missing. If set to 'No' then array will Start (including autostart) but encrypted volumes will not be 'mounted', meaning shares and/or share data stored on them will not be accessible. The default (and normal) setting for this is 'Yes'. The Let's Encrypt SSL provisioning is only available when 'Use SSL/TLS' on Identification page is set to 'Auto'. Also, provisioning the cert no longer triggers complete restart of "services". If using 'https' all 'http' is redirected to 'https'. If not using 'https', all 'https' is redirected to 'http'. The result of this is you can always enter servername in browser address bar to get to webGui, for example "Tower/" or "Tower.local" should always get you to the webGui. In the case of SSL-enabled LE certificate, you will get redirected to the <hash>.unraid.net URL. Added an 'Update DNS' button on Identification page. If the IP address of your server changes and you're usng the LE certificate, you can click this button to tell unraid.net to update the DNS setting. We have set TTL to 60 seconds so it might take this long to see the update. Of course you have to already have the webGui open to do this. Finally fixed reporting of temperature for NVMe devices (hopefully). Updated OVMF firmware, tested with various OS types, seems to work. Other misc. fixes an improvements, refer to Changes below. We're at the end of life for linux kernel 4.12. Next release will move to 4.13 kernel. Secure Access (-rc8q): Probably some explanation is in order. The “major” feature we wanted to add into unRAID version 6.4 was block level device encryption. However to get there we realized there needs to exist a secure way of entering information such as passphrases. Hence phase 1 consisted of integrating nginx in order to leverage its support of SSL/TLS (https). Besides the benefit of https support, integration of nginx also lets us utilize websocket technology (which is an ongoing integration), and lets us greatly improve the overall responsiveness of the webGui. Phase 1 integration of nginx in unRAID only supports self-signed SSL certificates. While in general, this may be OK to provide encrypted connections between a browser and a server in a trusted LAN, relying on self-signed certs is not good practice and is theoretically vulnerable to MITM attacks. With this release we have completed Phase 2 of nginx https integration by providing the ability for our users to provision a free SSL Certficate from Let’s Encrypt. To obtain your certificate go to Settings/Identification, scroll to the bottom and click Provision. In one operation this will allocate your certificate, upload it to your server, and switch nginx to redirect all http to https. After clicking anywhere else in the webGui you should see a nice green lock icon in your browser address bar! The other thing you’ll notice in your address bar is a very funny looking URL consisting of a 40-hex-character subdomain of unraid.net. We have set up a LimeTech DNS server that will resolve that URL to your servers IP address on your local network. That FQDN is unique to your certificate. When your browser resolves that URL it is given your local IP address which it then uses to perform the https connection handshake. For this reason, we recommend that you give your server a static IP address because if the IP address changes, the browser will not be able to connect to your server. This is like locking your keys in the car! We plan on implementing a small daemon which wakes up upon such IP address change and tells the LimeTech DNS server to update its A-record, but this has not been done yet. NOTE: if you do lock your keys in the car, the coat-hanger fix to restore http access is to telnet/ssh into the server and type: rm /boot/config/ssl/certs/certificate_bundle.pem /etc/rc.d/rc.nginx reload (You might also have to clear your browser cache.) Following re-enable of http, you can again Provision a certificate which will update the DNS entry. Device block level encryption (-rc8q): We have implemented full-device encryption as follows. In unRAID, encryption is selected as another type of file system. For example, with array Stopped, click on a Device link and then click on File system type. Three new “types” are available: xfs – encrypted btrfs – encrypted reiserfs – encrypted [should we get rid of this one?] If you change the File system type to one of these and then Start the array you will notice the device appears Unmountable and the Format button is available. Formatting the device will result in creating an encrypted partition on that device with the specified file system type. ALL PREVIOUS DATA ON THAT DEVICE WILL BE DESTROYED. Hence it is not possible, in this release, to encrypt in-place. We plan to add a utility in a future release to accomplish this however. The other thing you’ll notice when you click Format is that it may fail because there is no encryption key. In this case, click on Settings/Encryption Settings and enter in a passphrase to be used to secure your encrypted devices. At present we let you enter either a passphrase or upload a file which contains your passphrase (or binary data). DO NOT FORGET YOUR PASSPHRASE OR LOSE YOUR KEYFILE. Once a partition is encrypted, if you forget your passphrase or lose your keyfile, your data is forever lost - unless you know someone very high up in the NSA Also note that array Autostart following server boot will not succeed if any devices are encrypted. This is because the keyfile (passphrase) is kept in RAM and thus lost upon reboot. This means that following system reboot you must log into the webGui, go to Tools/Encryption and enter your passphrase (or upload your keyfile). Yes this is a nuisance and we have a few ideas for automating this, but at least you now have secure https access! In the case of a btrfs cache pool, all devices comprising the pool will be encrypted. For this release, we highly recommend using encryption only on a test server with test data which has been backed up. We plan on many more refinements in future releases. 4Kn Device Support (-rc8q): Yeah should work now. Other notes (-rc8q): The /usr/local/sbin/emhttp line in your /boot/config/go file is no longer used to specify the ports where the webGui listens for connections. Instead you must configure these on the Identification page. Alternately if you need to set this up prior to server boot, you may add the port settings in /boot/config/ident.cfg. Please refer to /usr/local/sbin/emhttp script for more information if you care about this. It used to be that merely Starting the array would re-write a “unRAID standard partition layout”. This surprises some users because one would expect nothing to be written to a new device unless Format was invoked. This has been changed so that nothing is written to a device unless Format is invoked (except for Parity devices – those will still be written upon array Start if parity sync is indicated). Moving devices around between cache pool and array or unassigned is handled much better now. There are numerous webGui fixes and improvements. Upgraded linux kernel and several base packages. Where are releases -rc8a-rc8p you might ask? Those were non-public test releases. Credits (-rc8q): Thanks to @jonp for his work in securing us a Certifiate Authority (Let's Encrypt). Thanks to @eschultz for an incredible amount of work involved in setting up DNS servers and integrating with Let's Encrypt API, among other vital tasks in this release. Thanks to @bonienl for his continued dynamix amazing refinements and networking/IPv6 expertise. USB Flash boot device backup function (-rc7) Added "Flash backup" button on the flash device info page (Main/flash). Click this button to download a zip file with the entire contents of your USB Flash boot device. This zip file may be used to restore to a new unRAID USB Flash boot device either manually, or using our nifty new unRAID USB Creator tool. Linux 4.12 kernel (-rc7) - should provide better Ryzen support among other improvements. UEFI support (-rc5) It is now possible configure UEFI boot mode to boot unRAID OS. The make_bootable.bat (Windows), make_bootable_mac (MacOS) and make_bootable_linux (Linux) scripts will output a prompt: Permit UEFI boot mode [Y/N]: If answered with 'Y' a new directory is included on the USB flash boot device called 'EFI'. The presence of this directory along with its contents, and along with some additional linux kernel options permit UEFI boot. This is done in such a way that you could choose either BIOS (legacy) or UEFI to boot off your USB flash device (that is, even if you answer 'Y' here you can still configure your motherboard to use Legacy boot). If answered with 'N' the directory and contents are still created, but named 'EFI-' (a dash at the end). This will prevent UEFI firmware from considering this device. You can manually rename the 'EFI-' directory to 'EFI' and permit possible UEFI boot (and rename back to 'EFI-' to prevent it again). Note: Even if the 'EFI' directory exists, whether or not your motherboard actually uses UEFI to boot is determined by BIOS settings. In addition, some motherboards may present a strongly worded warning along the lines of "The system found unauthorized changes on the firmware, operating system or UEFI drivers." In this case look for a "Secure Boot" BIOS setting and change to "Other OS" or "Disable". If you update your server using Check for updates on the Plugin page, an 'EFI-' directory and files will be automatically created on your USB flash boot device. If you prepare a new USB flash using this release, the 'EFI-' directory and files will also be included. If you use the "manual" method of updating by copying the bz* files from the release zip, beware you will need to manually also copy over the 'EFI-' directory (and modify the first line of syslinux.cfg and copy it to 'EFI-/boot' directory). There is also a webGui setting to permit UEFI boot located on the 'flash' device information page in the 'Syslinux Configuration' section. Update OS (-rc5) Instead of bundling an "unRAID Server" plugin on the Plugins page, there is a new page on the Tools menu in the About section called 'Update OS'. Here you can check for a new unRAID OS release as well as switch between the latest release in the stable branch or the next branch. In addition there is a separate control on the Notification Settings page that configures whether or not to automatically check for updates. enabling https (-rc3) To enable https support it's necessary to edit your 'config/go' file on your USB flash boot device. Use the -p option to specify the port(s) and optionally include the -r option to redirect http request from your browser to using https. Here's the detailed usage: # Usage: # emhttp [-r] [-p port [,sslport]] [OPER] # OPER is start or stop. Default is start. # By default nginx will be setup to listen only at port 80 (http). # The -p option may be used to define different listening ports and/or setup nginx # to listen at a specified port for https. The -r option may be used to setup # nginx so that any http request is redirected to https (this requires that both # ports have been specified with -p option). For example, to have nginx listen # at both standard ports but redirect all http to https use: # emhttp -rp 80,443 # To listen at only port 443 use: # emhttp -p ,443 # Note: the stop operation is only "safe" if the array has already been stopped # (this will be fixed). Improved shfs/mover (-rc1) The LimeTech user share file system (shfs) has been improved in two areas. First, we now make use of FUSE read_buf/write_buf methods. This should result in significant throughput increases. Second, the mover script/move program no longer uses rsync to move files/directories between the cache pool and the parity array. Instead the move program invokes a new shfs ioctl() call. This should result in complete preservation of all metadata including atime and mtime. While this function has been fairly extensively tested, please keep an eye on mover activities - there shouldn't be any data loss, but it's a fairly significant code change. nginx http server (-rc1) We now use the nginx webserver as the front-end to the unRAID OS Management Utility (aka, webGui). The emhttp process has been changed to a daemon (emhttpd) listening at a unix socket. Incorporating nginx provides several features: Multi-threaded access, though emhttpd is still single-threaded. https (SSL) support. At present unRAID OS will generate a self-signed certificate. https works but you will get a scary warning from your browser about not being able to verify the certificate. No worries. nchan (websocket) support. We have only just begun the process of converting many of the browser javascript polling functions to an event-driven websocket paradigm. This opens the door for us to create something like a process manager where we can have several background operations in process, all monitored in real-time via webGui dashboard. IPv6 support (-rc1) We want to again, give a big "thank you" to bonienl who has greatly improved unRAID OS networking with the addition of IPv6 support. Give it a try and report any issues. Other (-rc1) Two new webGUI themes: Azure and Gray. Again, thanks to bonienl. Expanded driver support (QLogic) and more hardware monitoring support. Kernel modules and firmware are left on the Flash in a squashfs loopback and loaded into RAM on demand. Many more misc. improvements Version 6.4.0_rc12a 2017-11-17 Changes Linux kernel: version 4.13.13 (with kvm_svm_obey_guest_pat.patch: https://patchwork.kernel.org/patch/10027525/) nginx: Revert "redirect https requests to the domain name in unraid cert" Management: emhttp: if both SMART ID 190 (Airflow_Temperature_Cel) and 194 (Temperature_Celsius) present, prefer 194 webgui: Fix regression error in SMART acknowledgement on dashboard board webgui: Bring Encryption status on Dashboard page inline with Main page
November 17, 20178 yr 2 hours ago, limetech said: nginx: Revert "redirect https requests to the domain name in unraid cert" yes, this* is it. Edited November 18, 20178 yr by jbrodriguez
November 17, 20178 yr 13 minutes ago, limetech said: nginx: Revert "redirect https requests to the domain name in unraid cert" Thanks! My reverse proxy works again
November 17, 20178 yr RIP RC11iThanks LimeTech for moving on this so quickly! Sent from my iPhone using Tapatalk
November 17, 20178 yr Whatever you did to mitigate the other red herring SSD reading the wrong temp has borked the ones that already worked. Immediately on first reboot login, I get notifications that my cache pool is on fire. tower-diagnostics-20171117-1547.zip Edited November 17, 20178 yr by interwebtech added diags
November 17, 20178 yr Whatever you did to mitigate the other red herring SSD reading the wrong temp has borked the ones that already worked. Immediately on first reboot login, I get notifications that my cache pool is on fire. [emoji6] tower-diagnostics-20171117-1547.zipThis is why i suggested that they change it to a user selectable option. As there are too many scenarios now. UnRaid Admins should be able to select a non-default SMART attribute per driveSent from my iPhone using Tapatalk
November 18, 20178 yr Author 28 minutes ago, interwebtech said: Whatever you did to mitigate the other red herring SSD reading the wrong temp has borked the ones that already worked. Immediately on first reboot login, I get notifications that my cache pool is on fire. Thanks for posting your diags. In looking at the SMART data returned by your Samsung EVO SSD we see: smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.13.13-unRAID] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Samsung based SSDs Device Model: Samsung SSD 850 EVO 500GB Serial Number: S2RANX0J202265L LU WWN Device Id: 5 002538 d41b8633d Firmware Version: EMT02B6Q User Capacity: 500,107,862,016 bytes [500 GB] Sector Size: 512 bytes logical/physical Rotation Rate: Solid State Device Form Factor: 2.5 inches Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4c SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Fri Nov 17 15:47:16 2017 PST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 0) seconds. Offline data collection capabilities: (0x53) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 265) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 1 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 5030 12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 18 177 Wear_Leveling_Count 0x0013 097 097 000 Pre-fail Always - 51 179 Used_Rsvd_Blk_Cnt_Tot 0x0013 100 100 010 Pre-fail Always - 0 181 Program_Fail_Cnt_Total 0x0032 100 100 010 Old_age Always - 0 182 Erase_Fail_Count_Total 0x0032 100 100 010 Old_age Always - 0 183 Runtime_Bad_Block 0x0013 100 100 010 Pre-fail Always - 0 187 Uncorrectable_Error_Cnt 0x0032 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0032 072 053 000 Old_age Always - 28 195 ECC_Error_Rate 0x001a 200 200 000 Old_age Always - 0 199 CRC_Error_Count 0x003e 100 100 000 Old_age Always - 0 235 POR_Recovery_Count 0x0012 099 099 000 Old_age Always - 1 241 Total_LBAs_Written 0x0032 099 099 000 Old_age Always - 46524204568 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing 255 0 65535 Read_scanning was never started Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. As you can see, it reports temperature using attribute ID 190 (ID 194 is not present). From this wikipedia article we read: 190 0xBE Temperature Difference or Airflow Temperature Varies Value is equal to (100-temp. °C), allowing manufacturer to set a minimum threshold which corresponds to a maximum temperature. This also follows the convention of 100 being a best-case value and lower values being undesirable. However, some older drives may instead report raw Temperature (identical to 0xC2) or Temperature minus 50 here. This unRAID release is doing the above, subtracting ID 190 RAW VALUE from 100. But, looking up documentation from Samsung we read: 190 Airflow Temperature The current temperature of the area surrounding the NAND chips inside of the SSD This is an intolerable situation. 20 minutes ago, miniwalks said: This is why i suggested that they change it to a user selectable option. As there are too many scenarios now. UnRaid Admins should be able to select a non-default SMART attribute per drive Not going to do that. Something as simple as reading the Temperature should not have to involve user intervention, that's ridiculous. What we can do is this: If both ID 190 and 194 is present, use 194 If only 190 is present use 190 unmodified That might do it. Anyone reading this: please take a look at /var/emhttp/local/smart and look for your SSD device identifier as a file name (I think this only affects SSD/NVMEe) and let me know if above rule would work in your case. EDIT: in looking again at the SMART output, maybe it's correct: meaning your SSD is indeed at 72C - I say this because look at your "VALUE" column. Kinda makes sense.
November 18, 20178 yr My Samsung 850 Pro SSD has SMART #190 (with current value of 31) but not SMART #194. I agree that in this case the reading from #190 should be shown unmodified as the drive temp. Edited November 18, 20178 yr by ljm42
November 18, 20178 yr Author 5 minutes ago, ljm42 said: My Samsung 850 Pro SSD has SMART #190 (with value of 31) but not SMART #194. I agree that in this case the value of #190 should be shown unmodified as the drive temp. Ok but if you look at that PDF doc from Samsung, at the end is a screenshot labled "<Magician ver 1.0 for 845 DC PRO/EVO>" and there is shows "raw value" as 33 and "normalized value" as 67. That seems to imply the true temperature is 67 right?
November 18, 20178 yr Author 18 minutes ago, ljm42 said: My Samsung 850 Pro SSD has SMART #190 (with value of 31) but not SMART #194. I agree that in this case the value of #190 should be shown unmodified as the drive temp. If you're willing, maybe turn off your case fans, or hit it with a hair dryer for a few seconds and see if the temp goes up or down.
November 18, 20178 yr Not going to do that. Something as simple as reading the Temperature should not have to involve user intervention, that's ridiculous. What we can do is this: If both ID 190 and 194 is present, use 194 If only 190 is present use 190 unmodified That might do it. Anyone reading this: please take a look at /var/emhttp/local/smart and look for your SSD device identifier as a file name (I think this only affects SSD/NVMEe) and let me know if above rule would work in your case.I think this is a bit short-sighted, as there will be drives out there which only support attribute 231, or inverted 190 only, or worse 190 and 194, but 194 reports a bad/invalid value. It would be great to be able to select it as an override and resolve a lot of the temp reporting errors. I will go through my SSDs and log their details through when I have a chanceSent from my iPhone using Tapatalk
November 18, 20178 yr Author 1 minute ago, miniwalks said: It would be great to be able to select it as an override and resolve a lot of the temp reporting errors. It would be great if the manufacturers employed programmers who knew what they were doing.
November 18, 20178 yr Author 4 minutes ago, miniwalks said: there will be drives out there which only support attribute 231 We will never support such devices. The foot has to come down somewhere.
November 18, 20178 yr It would be great if the manufacturers employed programmers who knew what they were doing.It would, but then a lot of us wouldn’t be employed in the ICT SectorSMART is only a set of guidelines as opposed to being a mandatory framework for all manufacturers to build/program their drives by. Sent from my iPhone using Tapatalk
November 18, 20178 yr 44 minutes ago, limetech said: EDIT: in looking again at the SMART output, maybe it's correct: meaning your SSD is indeed at 72C - I say this because look at your "VALUE" column. Kinda makes sense. I lasered the outermost SSD and got a temp @84F which leads me to believe the inner temp could likely be 82.4F which lines up with the raw value of 28C. Edited November 18, 20178 yr by interwebtech
November 18, 20178 yr 19 minutes ago, limetech said: If you're willing, maybe turn off your case fans, or hit it with a hair dryer for a few seconds and see if the temp goes up or down. Good idea! This was the starting point: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 190 Airflow_Temperature_Cel 0x0032 069 069 050 Pre-fail Always - 31 I hit it with a hair dryer up to this point: 190 Airflow_Temperature_Cel 0x0032 061 057 000 Old_age Always - 39
November 18, 20178 yr Author 9 minutes ago, miniwalks said: SMART is only a set of guidelines as opposed to being a mandatory framework for all manufacturers to build/program their drives by. Absolutely not true. Maybe you can make this case in the pre-Internet age, but now? There is a wealth of "common practice" out there easily obtainable. It's sheer laziness or stupidity.
November 18, 20178 yr Author 4 minutes ago, ljm42 said: Good idea! This was the starting point: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 190 Airflow_Temperature_Cel 0x0032 069 069 050 Pre-fail Always - 31 I hit it with a hair dryer up to this point: 190 Airflow_Temperature_Cel 0x0032 061 057 000 Old_age Always - 39 lol so the temperature displayed by -rc12a went down when you heated up the device?
November 18, 20178 yr 5 minutes ago, limetech said: lol so the temperature displayed by -rc12a went down when you heated up the device? LOL yeah it would have, but I was looking at smartctl directly since it isn't cached. If I had looked at the UI I think it would have dropped from 69 to 61 as the drive heated up. Also... it turns out that smart values don't update in a VM very quickly. I was initially doing a smartctl on the vdisk from within the rc12a VM, and couldn't figure out why the temp wasn't changing while it was being blasted from the hair dryer. Then I ran smartctl on the 6.3.5 host and saw that it had jumped 8 degrees
November 18, 20178 yr Absolutely not true. Maybe you can make this case in the pre-Internet age, but now? There is a wealth of "common practice" out there easily obtainable. It's sheer laziness or stupidity.Common Practice != MandatoryYou seem to have missed the point where I’m agreeing with you and instead want to argue with me. [emoji1303]Sent from my iPhone using Tapatalk
November 18, 20178 yr Personally, I think smartctl should handle this discrepancy. In addition to reporting whatever the drive says in #190 or #194, they should create a new line for #TEMP that knows how to interpret what different drives are reporting and give the number everyone is actually looking for. All of the logic would be put into smartctl and everyone would benefit.
November 18, 20178 yr Author 18 minutes ago, miniwalks said: You seem to have missed the point where I’m agreeing with you and instead want to argue with me. Sorry, not arguing with you, just blowing off steam. For years SMART has always been a big pain, and there's a famous google study out that says SMART is basically useless as predicting device failure anyway.
November 18, 20178 yr Author 11 minutes ago, ljm42 said: Personally, I think smartctl should handle this discrepancy. In addition to reporting whatever the drive says in #190 or #194, they should create a new line for #TEMP that knows how to interpret what different drives are reporting and give the number everyone is actually looking for. All of the logic would be put into smartctl and everyone would benefit. Those guys who support smartctl want to implement "quirks" probably less than I want to. Probably we'll change code to implement my rule above and see what happens
November 18, 20178 yr I have the same issue, Samsung 850 Pro. So, just to clarify.... my 850 Pro is probably OK and not actually overheating all of the sudden... it never ran above 45ish prior to this update. Should I attempt to mitigate the error or wait until the update and just assume all is fine until then?
Archived
This topic is now archived and is closed to further replies.