RobertP

Screen shot was from right after 2 data drives failed - before I started rebuild. Parity 2 failed soon as I started rebuild, so screen shot is from before parity 2 death.

You can tell which smart report is for what using the sdg and sdh. I started the preclear testing on them for the same reason I moved parity drive 2 while system was still in an unstable state - 'cause I was not thinking! I agree, it was a bad decision. Hind sight is a wonderful thing . . . At the time, I was sure the drives truly were bad and just wanted to confirm it via some testing before I tried getting any type of warrantee replacement - I did not figure any data could be pulled off of them nor did I think they would even function anymore. I guess the serial # is not that critical/confidential? Would it be better if I re-attached the reports w/o the blanked serial numbers? Any security concerns w that? Remember, I just did the diag today - after the "bad" drives have been pulled and replace by new drives (new drives that have not yet been "rebuilt" with the data due to the parity 2 issue). So far the pre-clear on the "bad" drives (on my other unRAID system) have not reported any errors, but they are only in stage 2 (it takes a LLLOOONNNGGG time to preclear drives that big!). Thanks for trying to help me figure out what is going on with this system.

Not sure how accurate the diag will be, I've stopped and restarted system several times since the first issue. I've also already pulled out the 2 "bad" drives and inserted two new ones in prep for doing the rebuild. I have already begun a PRE-CLEAR test on the two "bad" drives via my other unRAID system (so far no issues). Attached is a screen shot taken after the 2 drives "failed" and before the parity 2 failed, the SMART reports from the two data drives, and the DIAG from this system. ur1-smart-20220922-1149-ST16000NM001G-2KK103_ZxxxxxxL (sdg).txt ur1-smart-20220922-1155-ST16000NM001G-2KK103_Zxxxxxx (sdh).txt ur1-wopr-diagnostics-20220926-1656.zip

1) I have an 11 drive array, 2 are parity disks. 2 drives died when I kicked in Mover. I shut down, pulled them out, put in replacements. Foolishly at the same time I moved my parity 2 drive to a different slot. Powered up - the two data drives still show need for rebuild of course. I started a rebuild and immediately parity 2 status changed to a red X. I immediately canceled the rebuild, shut down, moved Parity 2 back to its old slot - still shows red X. I've shut down and tried moving parity 2 to other slots, but no luck. No visible damage to plug. I've run quick smart test on parity 2 and is "passes with no errors", but still shows a red X. I think my only choice is to replace parity 2 and rebuild my server from scratch - but wondering if anyone has suggestions on "reviving" a drive? (I can dream, can't I??) Luckily this server is used to hold backups of my computers and my other unRAID, so TECHNICALLY nothing was lost (other than historical recoveries!), but DARN IT! Any suggestions on the best way to rebuild it from scratch but to remain all the share names? Any easy way to save the data on the other drives that are not bad? Isn't there a Windows tool that will read Linix/Unix drives, so I could plug them into my computer and copy off the data? 2) I have an what feels like unusual number of drive failures in this system - sporadic. I suspect bad SATA card or cables (or maybe some of the 5-unit drive cages). I've tried unplugging and replugging cables and card - but failures continue. I put the "bad" drives in my other system and do a pre-clear and the preclear completes OK!?!? What should I do to make sure they really are OK? Could a bad (or underpowered) power supply cause this also? Not sure how to test the power supply. (On a side note - this system used to get kinda hot, but I've added additional fans and now the drives stay in the normal range. Maybe the previous overheating caused pre-mature drive failures? They never got in the ganger temp, just in warning temp zone.) Thanks, Bob Smart report -parity 2 drive - 20220926-1324.txt

That is good news. Thank you! I saw the iperf referenced for rc4 in JorgeB Posted August 25 reply to 8/24/2022 at 5:54 PM, venicenerd

I am a total newb when it comes to unRAID OS configuration - if it isn't in the APPS tab for install, I'm lost. But, if I understand previous msgs correctly: When I open Nerd Tools plugin, the only 2 items I see set to ON are IPERF and PERL (and I don't recall what tools needed these two items! Probably due to a Space Invader's video!!). Both of those will be included in the final unRAID 6.11, so I need to do NOTHING, correct? Once 6.11 is released and I upgrade, Nerd Tools will auto-de-install and those two items will automatically be there via the unRAID OS - right? Thanks, Bob

YEA - thank you! That did it for me (using binhex-krusader)

How can I get the 6.8 version back? I did not see the "do not install for 6.8" note on the recent update (that is for the 6.9 rc), so I updated to the 6.9 version in error. I've now removed that 6.9rc version, but do not see the 6.8 version (or ANY version) available any more.

Sadly I've already rebooted it. Is there anything I can look at? (It will run its normal monthly check on the evening of the 1st, or I could kick one off manually - either one should do fixes if that box is checked - correct?) If unclean Shutdown parity check does NOT honor that check box (I think that's what you are suggesting TRURL), then having that message display the appropriate thing (FIXED or NOT FIXED) is even more important!

I'd like to suggest a minor change to the Parity check msg that displays at the end of a parity check. If errors are found, add the words FIXED or NOT FIXED to the msg. (reasoning: I accidently killed my UPS while MOVER was running - which of course shut down my unRAID server. Upon power up, it went into parity check. Resulting msg was: Notice - xxxx - Parity check finished (2095 errors). There was no mention in the msg if the errors were fixed or not. Yes, I DO have the box checked to fix errors - but my point is this msg gave no indications if fixes had been applied.) Thanks.

The old Pentium D ran Windows 7 just fine. It was blazing fast when I bought it just FIFTEEN years ago! lol! 'course Windows 10 on that system was another story! When I decided to add some shared drives to the family network, figured since I had that old beast laying around, why not use it as an unRAID server. Works FAIRly well, but as I said I hope to upgrade it early next year. thanks for your assistance - I'm guessing the upgrade will resolve my ControlR issues.

No beta. I'm running 6.8.3 on both servers. Server shows things like 84 F, 91 F, etc. But in the TEMP column on the DISKS tab on my Android, it is showing 29, 33, and etc. I do not see anything on the plug-in showing TEMP settings. Remember that I still have that issue where it says STOPPED on both servers and WOL no longer works on either server. But despite the STOPPED msg on the servers, my Android phone and tablet DO read both of the unRAID servers. I've tried turning off the UPS status as you suggested, but same issue. Not sure if the temp issue showed up at the same time as the UPS status issue and WOL issue. Oh - interesting - my original unRAID is once again showing RUNNING! And the temp of that server on my Android IS in F. But for a while that one also began showing STOPPED and WOL stopped working. Have not tried WOL for a while. Remember that my "newer" unRAID server is running on an old Dell Pentium-D system - so that may have something to do with my issues (can't even run VM's on that box! I'm hoping to upgrade it this spring . . . maybe!) Not sure if you recall - I was having WOL issues with my "newer" unRAID (on Pentium-D), but my older unRAID was working fine. We discussed it, and during our exchanges (if I remember correctly), the older server also began having issues with saying STOPPED. But now (at this MOMENT in time!), the older one is showing RUNNING and the temp on my cell are correct for that server. (The "older" server uses a Xeon E3-1230 CPU.) I have the SYSTEM TEMP plugin installed on both servers. I had forgotten that on the "new (Pentium-D)" one it says "no drivers" when I click DETECT for the SYSTEM TEMP. But on the "old (Xeon)" one, it uses CORETEMP driver. So it could easily be that the Pentium-D one just doesn't have the proper temp sensors . . . So the server does not show SYSTEM temp, but that also makes me wonder if it is showing the DRIVE temp correctly! Yet another reason I should really upgrade the motherboard/CPU/etc on that system!

Temp on unRAID server is in Fahrenheit. Temp on IR Control on Android is in Celsius. Can't figure out how to change Android to show temp in Fahrenheit. I've looked in settings.

/sbin/apcaccess APC : 001,036,0881 DATE : 2020-07-11 18:56:29 -0400 HOSTNAME : UR2-Tower VERSION : 3.14.14 (31 May 2016) slackware UPSNAME : UR2-Tower CABLE : USB Cable DRIVER : USB UPS Driver UPSMODE : Stand Alone STARTTIME: 2020-07-11 18:40:25 -0400 MODEL : Back-UPS NS 900M STATUS : ONLINE LINEV : 120.0 Volts LOADPCT : 40.0 Percent BCHARGE : 100.0 Percent TIMELEFT : 14.9 Minutes MBATTCHG : 20 Percent MINTIMEL : 5 Minutes MAXTIME : 0 Seconds SENSE : Medium LOTRANS : 92.0 Volts HITRANS : 139.0 Volts ALARMDEL : 30 Seconds BATTV : 13.6 Volts LASTXFER : Unacceptable line voltage changes NUMXFERS : 0 TONBATT : 0 Seconds CUMONBATT: 0 Seconds XOFFBATT : N/A SELFTEST : NO STATFLAG : 0x05000008 SERIALNO : 4B1826P30593 BATTDATE : 2018-06-28 NOMINV : 120 Volts NOMBATTV : 12.0 Volts NOMPOWER : 480 Watts FIRMWARE : 932.a7 .D USB FW:a7 END APC : 2020-07-11 18:56:29 -0400 I did swap UPS between server 1 and 2 . . . Trying to recall if that's about the time this problem started. Don't remember for sure. After above, ControlR still says STOPPED on server 2. By the way - now my tablet also does not see the POWER ON option when unRAID 2 is off. POWER ON is grayed out on both phone and tablet now - I noticed that before I issued the above. I tried turning off the UPS in ControlR - UR2 still said STOPPED. I shut down both unraids, my phone, and my tablet. Both phone and tablet still have POWER ON grayed out for UR2. Powered up both unRAID servers manually. UR1 still says RUNNING under ControlR, and UR2 still says STOPPED. And, even though UR2 says STOPPED, I CAN use ControlR on both phone and tablet to get status info on BOTH unRAID servers. (And I can issue a POWER OFF from either phone or tablet to shut down the servers.)

# /usr/local/emhttp/plugins/controlr/controlr -port 2378 -certdir '/boot/config/ssl/certs' -showups I: 2020/07/09 19:03:11 app.go:58: controlr v2020.05.09|2.19.0 starting ... I: 2020/07/09 19:03:11 app.go:66: No config file specified. Using app defaults ... I: 2020/07/09 19:03:11 app.go:266: cert: found UR2-Tower_unraid_bundle.pem I: 2020/07/09 19:03:11 app.go:171: host(http://192.168.1.128:80) I: 2020/07/09 19:03:11 core.go:81: starting service Core ... I: 2020/07/09 19:03:11 core.go:304: Created system sensor ... I: 2020/07/09 19:03:11 core.go:325: Created apc ups ... 2020/07/09 19:03:11 Unable to wait for process to finish: exit status 1 It still said STOPPED. I tried rebooting unRAID #2, but it still says STOPPED.

No POWER ON option for unRAID server #2 when using my Android phone, but my Android tablet does have POWER ON option for that server.: On my Android phone I can see both unRAID servers and, if the unRAID servers are on, I can get info from them using ControlR. But if they are powered off, server 2 is all grayed out in ControlR on my phone. That is, the POWER ON is not blue and I thus I can not issue a WOL command to start it remotely. On my Android tablet I can also see both unRAID servers and, if they are on, I can also get info from them. On the tablet, if the unRAID servers are off, BOTH of the servers offer the POWER ON option. On the phone, I’ve tried removing the server and re-adding it (added it manually using IP address). Made no difference, POWER ON remains gray. On the unRAID servers I’ve checked various different server settings but have not found anything that seems to be different. One thing I just noticed – on unRAID 1, when I go into SETTINGS and select ControlR, the top left line is in green and says “Open Web UI(v2.19.0)”, and on the top right the STATUS is RUNNING. On unRAID 2 the top left line is orange and says “ControlR v2.19.0” and the top right the STATUS says STOPPED. But if the server is running I CAN still get info via BOTH the phone and table for server 2 even when the STATUS says STOPPED, and I can not find out how to change the status to RUNNING. Both unRAID servers list port 2378 in the ControlR setup. Both unRAID servers are running version 6.8.3. WOL used to work on my phone, but it does not work now. I did recently enable DEVELOPERS OPTION on the phone (so I could get “scrcpy” to work - totally unrelated to unRAID), but I’m pretty sure the WOL on the 2nd unRAID was not working on the phone before I enabled Developer Options. UnRAID 2 is an older PC, its BIOS does not support VMs so I do have VM Manager set to NO on that server. Powering both of the unRAID servers DOWN works on both tablet and phone. I should mention that I have NOT actually enabled WOL on server 1 – can’t find the right setting in BIOS yet. But even without that, ControlR has always “offered” the POWER ON option for both servers. And, as mentioned, the POWER ON for server 2 does work via tablet, but not via phone. Phone: Galaxy A10e (SM-A102U) Android version 9 Tablet: Galaxy Tab S4 (SM-T830) Android version 10 Thanks, Bob

I would also like to see more options in the color schemes. The alternating line shading is difficult for me (white/almost_white or black/almost_black is not enough contrast for my eyes to follow them across the screen.)

On the MAIN tab, Array devices section: Can the Parity drives be moved so they show up AFTER the drives (but before the “total” ARRAY OF x DEVICES)? (Either make this a default or maybe make it a user choice on what order things are listed?) WHY? When I GLANCE at the screen, I see DISK 2 is the THIRD line – then I look along the right edge and glance at the USED/FREE indicators and I look for the THIRD entry, but I really want the SECOND entry. Yea, yea, I know – if I were to follow the shading across I’d look at the correct USED/FREE bars, but for some reason my mind doesn’t do this when I do a quick glance. If they were re-arranged in this sequence: disk 1 disk 2 disk x parity (parity 2) total In this setup, third drive in the list on the left would be the third USED/FREE bar on the right. In addition, there would be a “natural” break in the USED/FREE bars for the drives and for the total. I know this is minor (and kinda nit-picky/personal), but it would (in my mind) make the screen more intuitive. And I think others may also find this easier to view. (It would also help if the alternating shading was less subtle. The white/almost_white and the black/almost_black just isn’t enough of a difference to my eyes.)

I also would like to see some type of progress indication for Mover. Either a bar, or as % complete, or an ESTIMATE TIME TO COMPLETE.

Check out this youtube link from the excellent "Spaceinvader One" unRAID tutorial videos.

Thank you. The only problem - at the start of a backup (or video record), there is no way to be SURE what size the file will be. One can make an educated guess, but can't be sure. If I set it to my guesstimated biggest size, some of my FULL backups are more than 1TB so the cache would NEVER get used for any backups. I guess, since I usually just do DIFFERENTIAL backups, I can set the cache "minimum free" size to a "typical large DIFF file size" - and if I do a full backup, then turn off cache for that share for that backup run (hoping I remember to do that! lol ). Thanks for the info on how unRAID will react. That's kinda what I expected would happen, just wanted to verify.

I have just installed a 1TB ssd cache drive. I use my unRAID system to mostly store backups, which can get large for some of my drives. If I have my user share set up to use cache, and the backup program starts out using the cache drive when it first begins the backup, what happens if the file ends up being too big to fit on the cache drive? Does it get split between cache and the share (and eventually all moved to the share), or does it get moved to the share "mid-stream" during the backup, or does unRAID just throw up its hands and say "no-can-do" and thus the backup program aborts the backup? I realize this may partially depend on how my backup program responds, but I'm wondering how unRAID acts in that situation? Similar situation could happen if recording a huge video file on a cache that is already mostly full - what happens to that recording file at the "cache full" moment? Obviously at the start of the backup (or video recording), the file size is unknown so it would start writing the file to the cache, but what happens when the cache fills up during a mid-file creation? (This could happen if a SINGLE backup file is too big for the cache, or it could happen if doing multiple backups (and thus multiple files) and the cache fills up during the creation of the third or fourth file.) Thanks, Bob

lol - yes, I clicked APPLY. But that is a good question to ask. BUT - problem solved! The SSD is a 1TB drive. With the system files on it, there was about 980GB or so free. Because I use my unRAID as a place to store my backups, and because some of those backups can be quite large, I had that share set to MOST-FREE and, ****more importantly**** I had the Minimum free space set to 1TB. Since the cache would not hold 1TB, it apparently went straight to the share. I dropped the minimum free space down to 800GB and now it is using the cache! Be interesting to see if this speeds up my next weekly backups next weekend!

Nope - I've got my user share "UR-BU-i7" set to USE CACHE of YES. I've got my SETTINGS, USE CACHE DISK set to YES. Doesn't matter if I do a backup to that share, or if I manually copy a small file (3KB) or few big files (four 1GB files), nothing goes to cache. I've tried copying to the "root" of "UR-BU-i7" and I've tried copying to a folder under that. Nothing happens to cache. After I do the copy, on the MAIN tab I click on the VIEW icon to the far right of the CACHE device - the files I copied are not showing up. Also, the cache's USED and FREE space is not changing. Copying the same files to a user share that is set to USE CACHE of NO - the copy speed is the same. Do I need to MANUALLY create a "UR-BU-i7" on the cache first? (If yes, then HOW?) As I said, I was able to MOVE the appdata and system folder to the cache using mover ("use cache" is set to PREFER for them).

I added an 1 TB SSD cache drive (previously I had no cache drive), but it is not being used. It IS functional, I’ve moved “appdata” and “system” over to it, so I know the drive is OK. Side note question – why is it recommended to put appdata and system on the cache drive? I did a pre-clear, then assigned it as cache drive and did a format. I’ve moved 2 folders to the cache drive (per SpaceInvader One’s instructions - https://www.youtube.com/watch?v=ij8AOEF1pTU ). I did NOT move domains ‘cause I don’t do much with VMs and don’t really want the couple VMs that I’ve played with to be consuming a big chunk of the cache drive. The main thing this unRAID server is for is holding backup images of various different computers around the house – and those backup images can be big so I want the cache “wide open”. I’ve set one of my user shares to “Use Cache” setting of YES. I’ve gone into the main SETTINGS tab, GLOBAL SHARE SETTINGS and set the USE CACHE DISK to YES. I’ve played around with a few different sizes on the “Min free space” – right now it is set to 1MB But when I run a backup that uses that share, the backup does not get sent to the cache drive first. I’ve also tried manually copying some files of various different sizes to that share – the cache drive is not getting used. The copies go straight to the user share. Since adding the cache drive, I've seen no speed gain in the copies, and after the copy if I look at MAIN, Cache, VIEW it does not show anything there (other than the 2 folders I manually moved). I click MOVE NOW and it is done in a second. What is this newbie missing? ur1-tower-diagnostics-20200217-0028.zip