S80_UK

Bought! (settings say version 1.9 (1) ) Thank you for this. This is a very nice effort, and I love the simplicity and clarity. I am not seeing motherboard and CPU temps for some reason, although they display fine in the web UI. I have Dynamix System Temperature already up and running (up to date), also running Unraid 6.8.3 currently. Drive temps report just fine on the Disks page, as do the UPS stats on the Dashboard. Let me know if you need any info. Thanks.

Also a shout out for the longevity of the Lexar Firelfy USB drives. I have three of them; they were one of the recommendations from Limetech when I started out. Both my main and backup servers still use them (4GB, both 10 years old). I would not assume that you need a new drive if the old one still works fine, although as mentioned above, transferring the license to a new USB drive is much simpler these days.

Thanks for the updates - I really appreciate the multi fans update in the System Temperature plugin.

I often get that using Chrome. I have no such issues with Firefox.

@olehj - Wow! That was quick! Thank you. I just updated, rescanned, etc. Yes, the false SSD identification is gone, and the Toshiba drives are showing the correct rotation rate info as well. Many thanks for that. For the other issue which was with the Toshiba HDWA130, I see that the "Model family" string in the SMART data is also shown as empty when I access that from the Dashboard. SInce the "Device model" string is present and since that also includes the manufacturer, I would say that's not an issue you can fix - the flaw is in the missing SMART data. So thanks again for the above fix.

Firstly, many thanks for this Plug-in. I only came across it a few days ago but I find it helpful and easy to set up. Just one minor observation I have a couple of Toshiba hard drives that are reported as being SSDs rather than regular hard drives. (Actually, I don't have any SSDs.) Toshiba model is reported correctly in the plug-in as HDWE150. It's a 5TB drive. unRaid reports the drive as TOSHIBA HDWE150 - a 7200 rpm drive. (info here if interested https://www.toshiba-storage.com/products/toshiba-internal-hard-drives-x300/) I also have a TOSHIBA HDWA130 (a 3TB drive) which is reported OK by the plug-in, but the manufacturer field is shown empty. Not sure it that's down to the drive or the plug-in. Obvioulsy these are not critical issues, and the plugin reports other aspects of the drives' data correctly. Please let me know if you need any further info. Thanks again. S80_UK.

You might think that... The thing about bad RAM is that you never know exactly how it may fail. It may be a single bit error at a single location. It may be an addressing fault (accessing the same physical bits at more than one location). It may be an error across a block of addresses. It may crash unRAID or it may remain invisible. The same goes for other operating sytems such as Windows. RAM can also go bad after months or years of rock-solid service. I would always recommend at least three complete passes of Memtest, and even then that may not catch everything. I would also recommend anyone to run it maybe once a year if they have some server down time.

I just use the built-in UPS tools in Unraid (and I use the Modbus method). Main server is set to master, the other is set to slave. Timings are set to ensure the slave will shut down first.

Ditto.

No... It's still working for temperatures and fans for me. Hardware as my sig.

Nice simple update from 6.8.0-rc9. My thanks to the Limetech team.

Thanks - I just picked up a secondhand unit last week. My unit is also the SMT1500I. I guess I got lucky with the build date. The updated software seems to read some of the voltages a bit differently (mains and battery) and includes a battery calibrate function which I did not find in the earlier firmware. My batteries were replaced only about a year ago, but I ran the calibrate anyway. It's a very nice UPS.

This worked for me too - BUT - I had to update the firmware on my UPS first. I have a Smart-UPS 1500 which was reporting firmware 8.3. There was no Modbus option in the advanced configuration menu until I updated to current firmware (version 9.4 as I write this). Download from Schneider's site here... https://www.apc.com/us/en/faqs/content/?id=FA281865 Note - you need to have the PC doing the update (and ideally its monitor) powered direct from the mains, since the UPS outputs will be turned off during the update process. It takes just two or three minutes. My screen was still on the UPS so I lost that during the update, and although I could see that it had completed on the UPS screen, I then had to manually re-enable the output on the UPS to get the screen back. 🙄

Thanks for creating this plugin. I have set up successfully and I'm currently part way through a check that I'm spreading across three nights. Looks good so far.

Obviously if there was no parity drive then parallel operations would be faster provided there was no overlap inthe drives being used by each of the move operations. Risk could be reduced by using something like the File Integrity Plugin and checking everything afterwards. Another considerationis backups - I wouldn't even attempt this without a backup of all files being moved. Parity or File Integrity can help you identify whether there have been problems with the move, but neither can fix the data if a file was lost or became corrupted for some reason.

In a system with a parity drive any moves involve reading and writing to the parity drive. I don't see a benefit in queuing and running multiple moves in parallel. In such a case, individual moves would then take longer, and since the parity drive would be modifying blocks of data possibly in very different locations, the added seek times on the parity drive would increase the total time to move all of the files quite significantly.

Off topic - it's about 30 years since I was designing hard disk controller hardware and writing test software for it. In those days you had to know how it all worked, otherwise it didn't work at all.

Yes, a slow down is normal - the actual speed will depend on the drive, but I have some older drives that go down to below 65MB/s towards the end of the disk. By convention disk drves access from the outer cylinders first. Since they are physically longer they have more sectors and since the rotation speed is fixed the data rate starts high and then reduces as the heads are moved in to the higher numbered cylinders.

Chances are is just the updated reporting since 6.4.1. Once acknowledged the error counts are known and are only flagged again if they go up. The errors that you're seeing now are most likely historic and nothing to worry about. See this thread and also the 6.4.1 release notes...

One of my pet hates where Microsoft are concerned. Every major Windows 10 update breaks a bunch of carefully crafted settings. Forgetting the power management options for some hardware in Device Manager is another area to watch out for.

2>&1 redicts the stderr output from rsync to the destination file rather than the regular stdout which by default is what would appear on the screen. See here https://superuser.com/questions/436586/why-redirect-output-to-21-and-12 The & at the end causes this command to be spawned as a separate task which will complete in the background. You can leave that off if you want to run in the foreground with the command prompt not returning until the end of the process. I'm still learning - I know just enough Linux to be dangerous!

Small question - complicated answer... I don't use Crashplan, so my method will not be exactly what you would need. What I have done in the past (before using this plugin) is to use rsync to generate a checksum of each file on the server and its backup and then compare them. You will either need to do something similar, or possibly have some other utility do a binary compare of all files in specified folders. That may not be so trivial if the backup is using Crashplan. If both sets of files are local, there are various utilities for comparying files at the binary level. Probably you can use diff at the command line, although occasionally I have even resorted to usng the DOS command line on a Windows PC... fc /b file1 file2 You would probably need to fetch the files or folders from Crashplan first so that you cuold then compare them locally. This is what I used in the past... My backups are on a second unRAID server, powered off for most of the time, but which runs the rsync daemon in the background when it is powered up. I have each disk drive on the main server backed up to a different share on the backup server. I don't map drives to drives, but drives to shares over the network. (Don't try mixing access to drives and shares on the same unRAID server, by the way - it can cause problems.) If I want to compare a disk1 on my main server against its backup, I run a command like this... rsync -rvnc --progress --delete --timeout=18000 /mnt/disk1/ BackupServer::mnt/user/Disk1-backup 2>&1 > /mnt/cache/Disk1_differences.txt & The -c option tells rsync to use checksums to determine whether to copy a file. It will do nothing if they are the same. In my case I also use the -n option so that nothing happens other than a report being produced. Note that the output of the command is directed into a file on my cache drive for later checking. Using the File Integrity plugin i will not need to do this in the future since the hashes for each file are stored in that file's extended attributes, and they will get updated on my backup server as well. That allows me to check both servers independently for errors of course.

True. I should have mentioned that.

The use is explained multiple times in this thread already. But briefly... You install the plugin and it generates additional data (hashes) that are mathematically derived from the contents of each file. The plugin monitors your server for added files and deliberate changes to files so that the hashes are kept up to date. You also set up a schedule that the plugin uses to determine when to check each file's contents against its hash. Typically you set up the schedule to split the checking to a few disks each time, depending on your system capabilities. If an error is found while checking then that file has become corrupted due to some unknown event (could be a disk problem, for example). Reporting includes notifications of checks, errors, etc. This software cannot tell you if a file is corrupted if you have not already installed it and generated the hashes, since that process requires you to have known good files. So it is too late for you to use it to find the files that have already been damaged by your power cut. By the way, that is a very unlikely event, unless the file was being modified at the time of the power failure. If you have a small UPS to protect your server that situation is easily avoided.

So is it finding some hashes that are not built? It seems very consistent, and FIP always tells me that all the hashes are up to date. Some of the disks where this writing while checking has happened have not had new files written to them in some months.