• Posts

  • Joined

  • Last visited


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

kjarri's Achievements


Newbie (1/14)



  1. Okay sorry for the misunderstanding. I stopped the Read check, switched out the old parity with the new parity and started again in maintenance mode. And started the parity sync. The hard drive is still active and operating normally for now. Lets see if the parity sync is able to finish.
  2. Okay, I tried to start it with the old parity drive but it warned me that it would wipe all data from it so I decided not to add it to the array for now, just started it in maintenance mode without parity. It seems that the drive started up so I started a Read check instead. That will take about half a day so hopefully that works. If that goes well I'm going to add the old parity drive, do the parity check and if that works do the parity drive switch again. Hopefully that works. Thanks for the help.
  3. I sadly don't have the logs. How ever I switched both the power cable and SATA cable with a working drive and that made no difference. How would I make unraid accept the old parity drive?
  4. Forgot to add the SMART report for the failed drive if you want to check on the failed drive Here is also what I got after Checking the file status on the drive: WDC_WD40EFRX-68N32N0_WD-WCC7K5EPUZ0S-20200609-2120.txt
  5. So I was upgrading my parity drive to a bigger one, from 4TB to 8TB. Everything was working well on the array before the upgrade. I shut down the server, took out the parity drive and replaced it with the new one and started the server. I chose the new parity drive for the server and started the rebuild. As soon as the rebuild started another HDD failed. I tried switching the parity drive back but the server would not take it because it thinks it is a new drive. (see screenshot) Is there anyway to make the server forcefully accept the old parity drive so I can switch the failed drive with a new one to rebuild it?
  6. Thank you so mutch, hopefully everything else goes well.
  7. Hi all, So my usb stick with the boot drive is dead. I have tried everything and it wont boot up. I don't have a Recent enough backup so I am not going to try that. Thats where a new drive comes in. I have flashed it and gotten the key file but I have read that you have to be careful selecting the correct Parity drive. I however am not sure witch one is my parity drive and was hoping for some help. Luckily I have a recent enough Diagnostics report for an unrelated issue and was hoping that somewhere there I could tie the parity drive to the serial number but I don't see where that is. Could someone help me identify my parity drive through this Diagnostics report? Thanks in advance heimanas-diagnostics-20191217-2329.zip
  8. Hey, I'm wondering if anyone else is having an issue with requested movies and tv shows are not shown as available under the requested tab. I found many people having the same issue like this one: https://github.com/tidusjar/Ombi/issues/2626 In the end they all end up with updating the locale with this command sudo localectl set-locale LANG=en_US.UTF-8 exept my locale is already registered in the docker terminal: ~# locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE=C LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= So I tried changing it to anything else with this command: LANG=en_IN.UTF-8 Then restarted the docker container. That did not work. So I tried updating the locale of my UnRAID mashine. That also did not work. So now I am at a loss because all articles and problems either lead to this fix. Has anyone experienced this or has an Idea about a fix? Running Unraid 6.7.1 and Ombi Latest
  9. Hello I am pretty new to unraid but I like to fool around with it, see what I can do. I have had no big issues, only a couple of minor bugs here and there but I was able to solve them one by one. The story starts today when I added a hard drive to my system. About an hour after I get a notification about a overheating problem on my hard drives. I thought it was because of the clearing process so I did not panic. Then when I got back I decidied to check the logs. There where millions of failed login attempts from ip adresses I did not know like: Jan 6 19:50:38 heimanas sshd[4431]: Failed password for root from port 52195 ssh2 Jan 6 19:50:38 heimanas in.telnetd[4501]: connect from ( Jan 6 19:50:38 heimanas sshd[4431]: Received disconnect from port 52195:11: [preauth] Jan 6 19:50:38 heimanas sshd[4431]: Disconnected from port 52195 [preauth] And also from a website that seemed to be comcast: Jan 6 19:52:23 heimanas login[5940]: invalid password for 'UNKNOWN' on '/dev/pts/3' from '173-10-58-34-Michigan.hfc.comcastbusiness.net So I blocked every port forward or anything simmular and I have had no incidents so far. I was wondering if there is anything I should do, report the IP adresses to some blacklist database or something or what to do to prevent this. I'll attach a part of the syslog, it was too large to upload. Thank you syslog.txt
  10. Thank you that worked. Was able to uninstall the plugin.
  11. Hey My unraid server all of a sudden wont work through my web browser. Neither can I connect to it via Plex. Everything else looks fine, I can putty in to it, I can browse all the files on all of the devices on the network and with no issues. I really need plex so if anyone has a suggestion I am up for it. I'll attach a link to the syslog from when I started it and when I wrote this. Thank you https://drive.google.com/file/d/0B7-BriBrM70zbWhNU3lGTkZRdDg/view?usp=sharing