Idaho121

I. Am. Dumb. Drives pushed fully into their slots. Everything's working now.

Ah, okay, good to know where to focus my troubleshooting. Thanks!

That rules one thing out, thank you! Poking around, a lot of people who had similar problems fixed them by changing PCI settings in their BIOS. See here and here, among others. Before I go messing around in there, does anyone have any sense as to what settings I might try? I'll start with the ones from the thread - do either seem like more likely culprits? (Also, just a side question - if I pull the two cards that have my internal HDs on them and boot, but I don't start the array, will that bork my build? With the external card and GPU, I only have 1 slot left over, and so I'd be juggling unless I just pull them until I get this working.)

SOLVED - I was dumb and didn't push the drives all the way into their slots. They don't sit flush with the front of the cage - they're in about .25". Hi all, I had a bunch of old drives that I pulled to put 14TB drives in my box, and I figured I might as well try to put them to use. So I picked up: An EMC KTN-STL3 This card These caddies (MoBo manual for reference) I threw my disks (shucked from EasyStores) into the caddies, put them in the EMC, put the LSI in my unRaid box in PCI_E6, and then connected them via this cable. The box turned on, but when I booted, nothing showed up. I looked in System Devices, and I didn't see the new card. I knew the PCI slot works because I had a GPU in there until I pulled it to make room (and switching my MSI to not look for it on boot). So I swapped the LSI I had in the PCI_E4 slot down to PCI_E6 and put the new card in PCI_E4. It showed up in my System Devices now, but it didn't show anything attached to it. I tried moving cables around into different slots in the EMC, but no dice. I had a second cable because Amazon was playing games with shipping, and swapping that out didn't help, either. Any ideas here on how to get the disks to show? They were all unRaid disks in their most recent lives. cybertron-diagnostics-20240420-2259.zip

Attached!cybertron-diagnostics-20231110-0759.zip

Hi all, Have a problem that started up a little while ago! Would love some help on getting it fixed. A couple weeks ago, while up and running, the Docker tab started saying that Docker failed to start. My apps were still working, though - I could watch Plex, for instance. When I tried to reboot the server, it hung on unmounting the cache drive and I needed to hard reset. Docker booted when the server booted up again, parity found 0 errors, and all was well. Then, it happened again. I deleted the Docker image and formed it again, but then the Docker shenanigans started again. I did a scrub of the drive and found 15 uncorrectable errors, and the logs said the following: I also had 3 types of errors, examples: I tried a few of the files and nothing appears to be wrong (wasn't expecting there to be). Also, last night, I received a note that the Docker image (set at 40GB) was almost full. When I ran Fix Common Problems, it said: Any help would be appreciated!

Thank you kindly!

Hi all, I was trying to upgrade my cache drive from a 1TB to a 2TB, but now that I've done so, my dockers are all missing. Process: Disabled dockers (and VMs, but I don't use that feature) Set everything to Cache Yes, then run mover. *I think this is where I messed up, as not everything was moved over. I poked around and it was the docker image, libvert folder, and a few folders in Plex metadata, which I didn't think would bork things Shut down, swap out drive Reboot, start array, format drive Set appdata/doman (which was missing)/system (and other shares) to Cache Prefer Run mover. *A few files for Krusader won't move back to the cache drive Enable docker Check docker - nothing shows up I've rebooted a few times, and started and restarted Docker. I've also tried to get the old cache drive to Mount using Unassigned Devices, but the Mount is greyed out. I'm guessing I need to move the files that didn't move from the old cache to the new one, but I can't figure out how to access that drive right now. Any help would be appreciated!

Everything was working fine until a few days ago. Then, Deluge stopped auto-loading/deleting torrent files from the relevant folder. Then, after I restarted to see if that would fix it, I can't get into the WebUI and I'm getting the following errors when loading: 2021-05-19 14:24:15 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'aes-128-cbc' to --data-ciphers or change --cipher 'aes-128-cbc' to --data-ciphers-fallback 'aes-128-cbc' to silence this warning. [warn] Unable to successfully download PIA json to generate token from URL 'https://privateinternetaccess.com/gtoken/generateToken' [info] 10 retries left [info] Retrying in 10 secs... I downloaded new files from PIA and have tried a few different of their endpoints that are on the list and that others who have had this issue noted as working. Any thoughts on what else to try? Thanks!

My dockers crashed, and I couldn't download logs (it would start but not complete), so I rebooted the system. A disk came up as being disabled and emulated. SMART report says that it hasn't failed, but I'm running another SMART test on it now. Dockers are working fine after the reboot. Logs attached - any ideas on what's wrong and what I should do? Thanks! cybertron-diagnostics-20210420-1837.zip

Getting some errors with YoutubeDLMaterial: ERROR: Error during parsing:Error: Command failed with exit code 1: /app/node_modules/youtube-dl/bin/youtube-dl --dump-json

Rebuilding, thanks!

Hey all, Was in the middle of upgrading my parity disk. I had unassigned the old one, assigned the new one, and rebuilt parity - that completed. Then, I unassigned a 4TB data drive, reassigned the old 10TB parity drive to that slot, and was rebuilding. All dockers off, nothing should have been writing to the array. Then, my power went out (it was past the 4TB mark on the rebuild, but I don't think that makes a difference). First step - order a new UPS, as the CyberPower one completely failed and went down with the power outage immediately. Check. Second step - This is where I'm uncertain. I think the right move is to boot up (array isn't set to auto start), unassign 10TB drive, reassign 4TB drive, rebuild parity, and then restart the process of swapping the drive, but I don't know for sure. Also, I know I'm dumb for this, but I didn't save a backup of anything before doing the rebuild. Thanks for any advice.

It'd be running Plex and Deluge (but Deluge writes to the Cache drive and I have Mover off until the rebuild is done), so should be good!

And I can write to the array while it's rebuilding parity?

I'd rather not have it offline as long as that process entails, so I'm all for an alternative. To be clear, process for this if I already have the new drive in the system, precleared, would be: 1) Turn off array 2) Unassign 10TB disk from parity 3) Assign 12TB disk to parity 4) Turn array back on 5) Let it rebuild 6) Once rebuilt, turn off array 7) Unassign 4TB drive 8 ) Assign 10TB drive to that drive 9) Turn array back on and let it rebuild ?

Before I upgrade my 10TB parity drive to 12TB and replace a 4TB drive with that 10TB drive, just want to make sure that this is still the proper procedure. It makes sense to me, but wanted to confirm before mucking with my drives!

Monitor just gave me the "Check cables, no signal" message. This is the first time it happened. I do have an SSD cache drive, so I'll get that set up - is that separate from the syslog server setup instructions you posted? And thanks, Johnnie - I'll check that out and work through any issues!

Hey all, I've got my server set up to shoot me a health check at midnight every night. Woke up this morning and didn't have it in my inbox. Ethernet lights were off on the mobo, but the rest of the machine was on and lit up. I couldn't access the drives via Windows or the web interface, so I tried plugging a monitor in. Nothing. After tinkering a bit more and not having any other ideas, I pulled the UPS plug from the wall to see if that would initiate a power down. The UPS ran out (slowly...which is good ANY other time), and when it shut down, so did the server, which tells me that they weren't communicating. Rebooted the system, everything working and a parity check started (and the disk I was preclearing I resumed). Does this sound like a crash/freeze on unRaid's part? I probably had 1-2 Plex streams going and was preclearing a disk, but nothing else should have been going on. Does this just sometimes happen, or should I dig in a bit more before it happens again? And, if so, can I get logs other than the ones from once I rebooted? I downloaded the logs (and would attach), but they're only from after the reboot. Thanks! cybertron-syslog-20200304-1316.zip

Completed without error. Raw Value for Raw read error rate is 212, up from where it was before by quite a bit. So buy a new drive, but don't lose sleep over this?

cybertron-diagnostics-20200101-1427.zip Here's the .zip!

Hey all, Just got some read errors on a drive when doing a monthly parity check. I paused the check - should I just let it resume? And should I take the server offline for now, or let it still run? Device is still showing normal operation. I'm assuming next steps are get a new drive, remove the old one, install the new one, and rebuild? Thanks! (Edited to add diag to initial post as per first response) cybertron-diagnostics-20200101-1427.zip

Hi all, Anyone have advice for physically moving my server to a new house? Going from NY to NJ, so not too far. I've got a Lian Li case with 14 drives in it. Definitely going to run a parity check ahead of the move, and pop the case to check wiring before booting up in new location, but I didn't know if there was anything else I should be aware of. Keep the drives in the cages, or remove and back? Any special way to wrap up the server that's particularly safe for the move? Thanks!

Alright, as I should have done earlier, I ran a full MemTest and found errors. Have filed for an RMA, I'll test the new RAM before I load the box up. So process from here - is this right? 1) Start server and array, save config file 2) Power down 3) Install new RAM 4) Run MemTest for a few days to be sure it's good 5) If it isn't, cry, then RMA again, repeating steps 2-5 until we're good 6) Restart server, start array 7) Run a non-correcting parity check. 8a) No errors, then this was just a RAM issue on the parity check 8b) If there are errors that are the same as my last check, run a correcting check 8c) If there are errors but they're different than my last check, run a new check to make sure I get the same errors 9) Once I get the same errors on consecutive checks, run a correcting check Am I missing anything, or getting anything wrong? Also, two other questions: 1) Should I be worried that I have corrupted files? I haven't noticed anything. I usually rip/record on one machine before moving it to my server. 2) Should I be worried about the drive with the read errors, or just have a backup ready to go because it'll fail eventually, but it's not a problem yet? Thanks, as always!

Circling back here because there were 7 errors found this month during the check. I will run the extended MemTest, as I should have done a month ago... However, I've had a drive with a low-but-stable Raw Read Error Rate number (was at 5). I just checked, and it's up to 10. I'm doing an extended SMART test now on it to see if that moves again. 1) Could this be what's causing the parity errors? 2) If so, do I replace the drive and then rebuild from the current parity, or should I run another parity check, correct, and then replace it/rebuild? 3) Do I have a couple of borked bits from when I corrected the 2 parity errors last time, or is it still RAM as the likely culprit and this is a separate issue? Thanks again, all!