RobJ

Just a brief examination, but you have 3 kernel issues just in the tail. That's obviously not good! 3 recommendations: - Your BIOS is fairly recent, but keep checking for newer ones - Make sure your BIOS is set to stock values, no overclocking or non-standard values - Upgrade to the latest unRAID, v6.3.0-rc6, it has a somewhat newer kernel

By this method, you've done the mechanics of the upgrade, but you haven't been introduced to all the changes and settings. For that, I still recommend reading the Upgrading to UnRAID v6 guide. You can skip down to the Boot and test section for some notes, but I'd still skim through the first parts, as there are some helpful notes scattered through it. Then read the following sections, especially about the Display settings. And turn on Notifications. I personally think that users that shortcutted the upgrade are left a bit high and dry, as there's a lot to learn about the new stuff in v6. The upgrade guide is a little dated though, written for v6.0, and we're now at v6.2, beta testing v6.3.

I have another idea for your consideration, a new mode of ransomware protection that may work better for some users and some situations. If you call the current method the bait file method or the honey pot method, this new one would be called the no-delete method or the home alarm system method. The user would enable and configure it for a list of shares, one or more shares to protect. Each share list should be named. You would then monitor ALL of the files in those shares for changes, by inotifywatches I suppose. If ANY file is deleted, you immediately lock down the system, the same way you do now if a bait file is messed with. Optionally, the user could also configure it to trigger on any file modification too, within that list of shares. They are always allowed to make file additions. By default, the protection is ON, armed. If the user wishes to work on one of these shares, modifying and deleting files, they must first request permission by one of several methods, which they configure, in effect the temporary disarming of the system, turning OFF the protection for the share list. 1. The 'please' file method - they configure an absolute path to a file of their choosing, not in the root, in order to make it difficult for hackers to find. If the file (in that exact path) exists, you disarm the system for that share list, and allow any file changes. Once they remove the file (or modify it in an agreed and configured way), then you rearm the system, disallowing all deletions, and optionally all modifications too. (I'm thinking it could be called the 'please' file, as it politely requests permission to edit files.) The user would be expected to make the appropriate macros or shortcuts that arm and disarm the system (create and remove the 'please' file, or edit it correctly). 2. If the requesting user has access to the unRAID server, then they could toggle a button in your plugin, to arm and disarm the appropriate share list. A nice enhancement would be an additional option to disarm for a configurable or user-entered time period (e.g. disarm for 30 minutes), which you would then manage - disarm then rearm after time interval completes. If no time period, then it's indefinite, and the user is expected to remember to toggle again to rearm the system. 3. Scheduled or scripted signaling - your plugin can monitor for a signal that includes the list name and the time interval wanted, then the plugin disarms and rearms automatically, according to the schedule or signal. This would be ideal for workstation backups. The scheduler or external script would initiate the disarming, their backup would execute, then the plugin would rearm the share list. 4. I'm sure others can think of other ways too, to securely notify the plugin, requesting permission to temporarily disarm the protected shares. I've looked at other anti-ransomware tools out there, and the sophisticated mechanisms they use to try and detect specific ransomware behaviors, and they can still allow a number of encryptions to happen before lockdown occurs. What I particularly like about this method is it's so simple, nothing at all sophisticated, yet could lock down with the loss of only one file, possibly 2 or 3 if the malware is working really fast before you disable their access. And instead of low level OS hooking, you're just letting the OS notify you of file changes. That's all you need (that and knowing the change is more than a file addition). Additional enhancements: - add optional password on toggle button, and script signal, and within 'please' file (so even if a ransomware is knowledgeable about this plugin, it's blocked by the unknown password and 'please' file) - allow relative paths within the share list, to limit even further the folders being protected, allowing very specific protections (e.g. limited relative paths: Movies/action, Finances/current/Joes taxes) One gotcha I could see is if a user included a share in more than one protected share list, then disarmed one but not both and deleted a file within that share. Seems a user responsibility issue to me. But since overlap seems likely to me in some situations, you may have to detect it and disallow the triggering in the overlapped and still armed share list. Possibly doable by reordering the list of share lists so that disarmed ones are checked first. Once you decide a deletion is allowed, then exit, so it isn't even checked in the armed list.

You've been awarded an unRAID Purple Heart!

That's something I'd like to know too. I suppose since this is Linux, you are expected to unmount the file system yourself, before detaching. And probably Linux GUI's (KDE, etc) provide a button or function that will execute the appropriate unmounts, comparable to 'safely remove'.

Those all look typical for a disconnection and a new connection. I don't think of these as hard errors, more as soft errors, a part of normal operation, detecting the loss of a device and the discovery of a new device. When the controller detects any physical change of readiness of a device on a port, it raises an exception, and the exception handler then initiates the normal procedures for detaching or initializing the device.

I think this should be a FAQ entry, if anyone is willing to write it ... There's some good info in this thread for it.

You're right, the option is different when it's done with assigned disks (no device) or after a new config (unassigned), so for this procedure since it's after a new config the correct option is "unassigned". Thanks for pointing it out. @Rob, I still can't edit the wiki, please correct that when you can. Thank you guys, changed it. I decided to keep both, with 'unassigned' first, in case an advanced user is 'adapting' the instructions to their particular use. Johnnie, I've posted about it here, no response yet.

Hot swapping does work on some controllers with some systems, so you can try it (with array stopped) and it *may* work for you. But personally, I'm with Gary, it's just safer to shut down.

Does anyone have any experience with this? I guess I need to update the firmware. Would this have an impact on the preclear process and producing the problem I experienced with the post-read? That's a rather old problem, but I'd take it serious. I don't recall any unRAID users reporting data corruption or loss from it, but certainly there were reports of such from elsewhere.

And yet its online Cops got me again! Can't get away with anything around here! I thought I could get away with it if it's not in the FAQ index yet, so it's not online there.

I found a segfault error in my syslog. How do I fix it? My system is crashing randomly, and/or I'm seeing a little data corruption. How do I fix it? How do I test my RAM, my system memory? * Segfaults - there are 2 primary reasons for segfaults - faulty memory chips and dependency issues. See below for methods to test your RAM. If your RAM is fine, then it's almost certainly a dependency issue - some software that you have added has a dependency that conflicts with either the core unRAID system or something else you have added. * Random crashes and data corruption - while there could be a number of causes for both of these, one primary cause and the easiest to test and fix is faulty RAM. Thoroughly test your memory using one or both of the following methods. The 3 symptoms above are the most common symptoms of bad RAM chips, but there are others too such as kernel OOPS and kernel panics and other syslog errors resulting in a 'Call Trace'. While there may be other causes for these, the first test you should always do (and the easiest!) is to thoroughly test your memory chips. The following 2 methods will test your RAM for problems, and report any errors found. IMPORTANT! Not one error is acceptable! If you run a Memtest for 12 hours and it only finds one problem, then you need to replace a RAM stick! You absolutely HAVE to be able to trust your memory. When you test memory, you expect 100% perfection, no matter how long you test! Note: there are 2 different Memtest programs, Memtest86 and Memtest86+. They look very much alike for good reason - they have the same base code! When the original development stopped in 2002, for about 2 years, an open source group created Memtest86+ from the code, and continued updating it until stopping in 2013, with v5.01 being their last release. The free open source Memtest86+ v5.01 is what is included with unRAID. PassMark Software bought the rights to the original code in 2013, and has been updating it ever since, as MemTest86, currently at v7.2. Many newer technologies and tests have been added, such as DDR4, extensive ECC testing, row hammer testing, and much more. The newer features do require UEFI support, and if not found, an older version will be booted instead. While it's now a commercial product, they have continued offering a free version, for personal use only, but it is not licensed for inclusion with the unRAID software distribution. Note 2: both methods assume you can view what is on the console of the unRAID server. That usually means an attached monitor and keyboard, but could also mean remote viewing through IPMI. There is NO WAY to run a memory test on a headless server (unless you can use IPMI). To run either method, you MUST find a way to view the console, and you need a keyboard to select the test. The PassMark Memtest can also use a mouse, so an attached mouse will be very helpful in Method 2. * Method 1 - using the built-in Memtest You MUST be able to see the console and use a keyboard to select Memtest from the boot menu. On booting your unRAID server, when the boot menu appears, select Memtest, and it will begin. It will run continuously until you reboot. * Method 2 - using the PassMark Memtest You MUST be able to see the console and use a keyboard to select Memtest(?). A mouse will also be very helpful, recommended. (download from PassMark, create bootable USB drive, configure UEFI settings to boot UEFI, boot, after completion restore UEFI settings) PassMark download PassMark installation help (work in progress) Bad memory defects will fail the tests on the very first Memtest pass. Once you see the first error, you can stop the test as there's no point in continuing. Unfortunately, other memory defects are much harder to find, marginal cells that appear to work fine *most* of the time. *Most* of the time is not good enough, they need to be perfect *all* of the time. So you will need to let the tests run a long time, waiting for that marginal cell to fail. Again, even one error means a bad memory stick. How long is long enough? I believe over night, or 12 hours is sufficient, but it's possible that in some circumstances, even longer may be needed. If you do get an error, then you will want to isolate which stick is bad and which ones are fine. That means alternately testing different combinations of sticks, or each stick individually. This is a work in progress, but almost ready to put online!

And how is this working for the sleep? (if there is a way) Thanks for a hint I'm sorry, I don't sleep! But hopefully, someone else can help ...

I tried to edit the wiki myself but can't, I always get I'm not logged in, this is what I wanted to edit: on step 12: "Go back to the Main page and click on the dropdown for the new drive (e.g. Disk 11) and unassign it (click on Unassigned???)" - that should be changed to (click on "no device"). And more importantly, after step 11 there should be a warning about the new config, something like this: "Doing a new config will reset the file system type for all disks to auto, while usually this is not a problem, especially with the latest unRAID, in some circumstances can lead to unmountable disk(s), if that happens you just need to select the correct file system for that disk(s), if in doubt ask for help." Done, and thanks! I've added your changes. Now we need to find out why you can't edit the wiki. I'll post a question about it in the moderator board, but you may want to ask LimeTech support yourself.

I have only found 4 SMART reports from either 8TB or 10TB Ironwolfs with enough working hours to get stable normalized values for (1)RRER (7)SER and (195)HER. It is still an small sample to make general assumptions but the data seem to support the hypothesis I posted here that SMART values for the Seagate 8TB drive ST8000DM002 (heavily tested by BackBlaze) could be used as a guide of "normal SMART values" for the new 8TB and 10TB Ironwolf series. The behaviour of Seek Error Rate seems typical for a Seagate drive: A worst value of 60 and a normalized value somewhere between 70 and 85. The Read Raw Error Rate also seem normal compared to the data I have so far. The (195) Hardware_ECC_recovered value is the one that I really want to figure out before I pull the trigger on the ironwolfs. Those values so close to zero worried me. However they seem to be normal for the Seagate ST8000DM002 and for the Ironwolfs I have seen so far. Good observations again, I agree with yours. I have to apologize for not responding to your first report! I spent a fair amount of time on it, a lot of data! You had some interesting observations, and I believe I saw one or two other things, but I ran out of time, then got busy with other stuff, then been dealing lately with more projects on a LIFO schedule, and by the time I tried to get back to your post, I'd forgotten everything. At some point, I'll go back and learn what I can from it, but I think you summarized the most important things. Just have to say though - great reporting!

After that very bad result, I'd say you would want at least 2 full perfect Preclears in a row, before I felt the drive could be trusted. This is one time when I would probably want to Preclear it 3 times, and expect perfection on all 3 (perfection meaning NO current pending sectors ever, and NO increases in reallocated sectors, and no other issues either). And that's just me! There are other users here that wouldn't even give it that much of a chance, would return it immediately for replacement, no more testing at all.

If you would like your thread removed, tag it with [Remove] or [Delete] in the Subject, and the entire thread will be removed.

For v6.2 users using P parity only you could make small changes to 4 steps to make it work, but it involves doing a new config and that can make it much more prone to a user making a mistake: 10. Stop the array; we are now going to swap their assignments; when stopped, click on Tools -> New Config -> on "Retain current configuration:" select "All", check "Yes I want to do this", click Apply, click Done; go back to the main page and click on the dropdown for the new drive (e.g. Disk 11) and unassign it; 11. Click on the dropdown for the other drive (e.g. Disk 10), the one being converted, and reassign it as the physical drive that was just added, the new drive that was empty; 12. Click on the dropdown for the slot of the new drive (e.g. Disk 11) and reassign it to the physical drive that was being converted (e.g. Disk 10); you have just swapped the 2 drives, which is fine as they are identical (except for file system format) 13. (as it was) 14. You should see all array disks with a blue icon, a warning that the parity disk will be erased, and a check box "Parity is already valid"; important click it before the Start button to start the array; it should start up without issue and look almost identical to what it looked like before the swap, with no parity check needed; however the XFS disk is now online and its files are now being shared as they normally would; check it all if you are in doubt I checked and I believe the procedure is correct but in case you decide to use it it should be double checked by someone else. Thank you, Johnnie! What I decided to do was copy the post to a wiki page -> File System Conversion Then I incorporated your steps, and added comments that it's only for 6.2 or later, if earlier go to my original post. I've modified my post to indicate it's only for 6.0 and 6.1, and if 6.2 go to the wiki page. I think that covers it. I also added a comment about dual parity. I've added links to my section on File Systems and whether to convert or not, but I hope to pull that stuff into the page, later. And I added a comment about it being untested yet, so I would really like to hear from anyone willing to try it! I'm sure it can be improved.

That's a really important issue, one I originally underestimated. I've added warning notes about it to my file system conversion post, at top and bottom in blue. I've tried to list the common 'agents of change', that HAVE to be stopped/disabled. I've also added a red note to it, to indicate that the swap trick doesn't work any more, as of 6.2, as johnnie.black has reminded me several times. This 6.2 change really disappointed me, as the swap trick made it so much easier. For 6.2, I need to replace steps 10 through 12, but I don't have a test system, to see what's on the screen and write new steps up. I haven't quite known what to do about it, so just left it alone for awhile. I'll try to move it to its own wiki page, where more users can edit and improve it. I can then generalize it, and add sections about the available file systems, and when and why you might want to convert a file system, or not. I do have a section about that -> File systems

I finally got around to this, and updated the Replace A Cache Drive page, with the suggestions and Squid's method (removed). I decided against mentioning hot-swap. I added the Appdata method as a variation of the Mover method, but since I don't have Appdata, I don't have the plugin and can't test the instructions. Hopefully someone will, and let me know of any improvements needed. (removed)

Collecting related posts (because different methods have helped different users) - * For login failures, especially with 6.3.0 * Another post from Tom, with a step by step procedure * Tom's post on managing credentials, and clearing them * Enabling older Samba authentication, also tips on debugging Samba connection issues * Posts about reverting to SMB 2.0.2 * How to downgrade SMB * Using 2 different Windows credentials for different shares * The Local Master plugin * Local Master, the LM plugin, and workgroup names - plus the followup 3 posts down (about workgroups and election) * Keeps asking "Enter Network Password" - suggests using guest with no password * Using the hosts file worked? * Registry fix to keep your Windows 10 box from becoming the master browser * Clear summary post, with comment about Win 10 updates * config/smb-extra.conf * Anonymous Login on Windows 7 - might work for other Windows versions too? * more to come, as we find them or they are reported to us ... (calling all fixes! anyone that knows of a helpful tip - please inform us!)

RAM and CPU are irrelevant here, it's I/O bound. Only the drive speeds, bus speeds, and time costs of the operations performed matter. Deletions are very slow on ReiserFS, not near as slow as the transfers, but another time cost. It would be faster not to use --delete, to re-format instead (not a huge time savings but a little). Also, I don't think using the --delete option will remove the folder structures. I would much prefer reformatting as the faster and cleaner way to delete all and start with a fresh clean file system. Plus it gives you the chance to visually compare the 2 drives before reformatting one, a sanity check, to make sure they look identical (the right drive was copied, the right command was typed, it really did complete, etc). disk1 -> disk6 (transfer and check) reformat disk1 disk6 -> disk1 (transfer and check) reformat disk6 You have chosen probably the longest possible way to do this, at every step. But it does preserve parity and safety and your configuration. But it just seems redundant to me, to copy it all twice.

Were you intending to attach the results of a Preclear? All I can see is the attributes of a brand new drive, still perfect.

This thread is reserved for guides and videos for unRAID. Please do not ask for support here, such requests and anything off-topic will be deleted or moved. Note: work in progress, incomplete, more to add, and the order of listing can be improved Note: periodically recheck the Spaceinvader One YouTube for any new videos Note: many videos aren't visible in the linked post if using https, must use http Note: any linked posts with embedded videos will be slow to load, allow your browser extra time! Their pages may also jump around some as they load. The unRAID community owes the authors below a huge debt of gratitude for the outstanding work here, especially to gridrunner! Please consider dropping them a note of appreciation, or more if they have a donation link! Guides and Videos for General unRAID Usage Getting Started Introducing unRAID OS 6 - Limetech video by jonp, intro to unRAID All about the Array, how data is written and how parity works in unRAID - an introductory video guide by gridrunner Getting Started with unRAID - Limetech guide, with videos, text, and screen shots Installing unRAID from Windows - Limetech video by jonp Installing unRAID from Mac OS X - Limetech video by jonp Configuring your BIOS settings - Limetech video by jonp Initial Setup - Limetech video by jonp Configuring Disk and User Shares - Limetech video by jonp Updating the unRAID OS Software - Limetech video by jonp Getting Started with unRAID - Limetech wiki How to install and configure some essential plugins for unRAID - video guide by gridrunner How to create custom unRAID banners and change the look of the webGUI - video guide by gridrunner General How to add a cache drive, replace a cache drive, and create a cache pool - video guide by gridrunner How and why to preclear your drives - video guide by gridrunner How to replace or upgrade a drive in your array - video guide by gridrunner How to setup and use rclone. Copy, sync, and encrypt files to the cloud. Even stream media - video guide by gridrunner NEW Troubleshooting Need help? Read me first! - PLEASE start here first! Troubleshooting - more troubleshooting help, with sections for older versions too Guides and Videos for Dockers in unRAID Getting Started All about Docker in unRAID - Docker Principles and Setup - video guide by gridrunner Using Dockers - Lime Technology Manual by jonp Get started with Docker - introductory guide by docker.com Docker Guide - older Limetech guide - but use Community Applications! Noobie docker setup guide - older guide by xxredxpandaxx, a little out-of-date General Docker Information The Complete unRAID Reverse Proxy, Duck DNS (dynamic DNS) and LetsEncrypt guide - guide by Fma965 Applications Plex: Guide to Moving Transcoding to RAM - guide by jonp How to install binhex's Deluge-vpn (bitTorrent docker with VPN) - video guide by gridrunner How to install/configure OpenVPN-AS for secure remote connections - video guide by gridrunner Hamachi Install using Community Apps (with template editing) - video guide by CHBMB, "Note: make sure you set highest resolution" How to install and configure a SABnzbd Docker container - video guide by gridrunner How to install SABnzbd and Sick Beard on unRAID with auto process scripts - guide by gridrunner How to install and configure a SickRage Docker container - video guide by gridrunner Setting up an ownCloud Docker on unRAID - video guide by xxredxpandaxx Guides and Videos for VM's in unRAID Getting Started An introduction to VM's, including BIOS settings and iommu groups - video guide by gridrunner A brief synopsis of virtualization terms and acronyms - basic introduction by jonp, "Note: old, may need updating" Enabling VM Management - Limetech video by jonp UnRAID 6/VM Management - Lime Technology Manual by jonp, "Note: Limetech guide to VM management" UnRAID 6/VM Guest Support - Lime Technology Manual by jonp, "Note: full Limetech guide to VM setup in unRAID; special section for OpenElec" General VM Information How to connect virt-manager to unRAID to help manage your VMs - video guide by gridrunner, "Note: read the thread" How to pass through an NVIDIA GPU as primary or only GPU in unRAID - video guide by gridrunner How to pass through hard drives, convert disks, and test Vdisk performance in unRAID VM's - video guide by gridrunner How to easily and safely pass through a USB controller - video guide by gridrunner, "Note: adds hotswapping to your VM's" Passthrough Entire PCI USB Controller - guide by archedraft How can I pass through a physical Network controller to a VM? - video guide by gridrunner Passing Through Network Controllers to unRAID 6 Virtual Machines - guide by jonp, "Note: may be old and obsolete?" Physical to Virtual Machine Conversion - Lime Technology Manual by jonp, "Note: Limetech guide to converting an existing OS to a VM" Performance Improvements in VMs by adjusting CPU pinning and assignment - guide by dlandon How to both manually and automatically backup your unRAID VMs - video guide by gridrunner How to install unRAID as a VM on another unRAID server - video guide by gridrunner Custom VM icons automatically downloaded and installed to unRAID - guide by gridrunner, "Note: scripts for downloading icons and banners for unRAID" Problems and solutions - installing nested VMs in KVM on unRAID - video guide by gridrunner How to remotely start, connect to, and even play a game, on a VM over the Internet - video guide by gridrunner How to passthrough and boot from an NVMe controller for bare metal performance in unRAID - video guide by gridrunner NEW How to easily pass through an Nvidia GPU as primary without dumping your own vbios! - video guide by gridrunner NEW Windows VM's Installing a Windows 10 VM on unRAID - Limetech video by jonp Windows 7 Media Center VM with Ceton Network Tuner to serve WMC Extenders - guide by dlandon Streaming Windows Virtual Desktops - Limetech video by jonp (VNC vs RDP) How to Convert a pre-built Windows VM from VMWare to unRAID KVM - Limetech video by jonp Mac VM's The newest, easiest and best way to install OS Sierra or El Capitan! - video guide by gridrunner Mac OSX 10.11 or 10.12 Sierra (seabios and OVMF/clover methods) - video guide by gridrunner Mac OS X 10.11 El Capitan – VM on unRAID - guide by archedraft How to upgrade your VM to OSX 10.12.4 - video guide by gridrunner NEW How to read the OSK key on an Apple - video guide by gridrunner Advanced OSX VM techniques in unRAID. Get everything working! - video guide by gridrunner Applications Gaming on a NAS? You better believe it! - Limetech Managing Game Libraries with User Shares - Limetech video by jonp How to install OpenELEC (Official) in a VM - video guide by johnodon How to install Lakka for the best retro gaming experience as VM - video guide by gridrunner Running "Tech and Me" ownCloud VM appliance on KVM on unRAID - guide by Pducharme Running a Raspberry PI as a VM on unRAID using Linux QEMU - video guide by gridrunner Install a custom LibreElec VM complete with Emulation Station - video guide by gridrunner Virtual Reality Passthrough VIVE & Oculus, 4 Gamers 1 CPU with NVIDIA Cards - guide by Baltostar, "Note: read the thread" Demonstrations 2 Gaming Rigs, 1 Tower - Virtualized Gaming Build Log - Limetech video, "unRAID Featured On LinusTechTips" 7 Gamers in 1 Tower – Behind the Scenes - with videos, Limetech and LinusTechTips 10gbps over SMB on a 45Drives Storinator - with video, Limetech and LinusTechTips 3 Gamers, 1 mATX Motherboard, 1 CPU and some benchmarks - video by gridrunner OS X on unRAID running on a MacBook pro! - video by gridrunner Physical vs. Virtual Machine - 3D Mark Benchmark Comparison - Limetech video unRAID Server OS 6.1 Overview - Limetech video by jonp unRAID Manuals unRAID Official Documentation - Limetech wiki, current unRAID manual UnRAID Manual for v6 - v6.0 unRAID manual Unofficial UnRAID Manual - the v4 manual plus user enhancements; includes the illustrated sections on share settings and 'split level' UnRAID Manual for v4 - very old! only for v4.7 or earlier unRAID FAQ's FAQ for unRAID v6 on the forums, general NAS questions, not for Dockers or VM's FAQ for unRAID v6 on the unRAID wiki - it has a tremendous amount of information, questions and answers about unRAID. It's being updated for v6, but much is still only for v4 and v5. Docker FAQ - concerning all things Docker, their setup, operation, management, and troubleshooting FAQ for binhex Docker containers - some of the questions and answers are of general interest, not just for binhex containers VM FAQ - a FAQ for VM's and all virtualization issues FAQ for unRAID v4 and v5 - old! not for v6 - add miscellaneous (Turbo Write? Tips and Tweaks? old build guides? Reiser-to-XFS conversion? maintenance guides?) - note: don't know where this all belongs - wiki page, stickied post in ?? board, somewhere else??

Is there a way to create a Windows shortcut for shutting down the unRAID server? On your Windows machine: - Install PuTTY first, it includes plink.exe - Create a batch file (store it anywhere you choose) containing the following line (replace password_here and server_IP_here): plink.exe -ssh -pw password_here root@server_IP_here poweroff e.g. plink.exe -ssh -pw 123456 [email protected] poweroff Note: with older versions of unRAID, use powerdown instead of poweroff - Create a shortcut on your Windows desktop that points to that batch file Clicking that shortcut should start the normal unRAID shutdown procedures.