Odom

Members
  • Posts

    49
  • Joined

  • Last visited

Posts posted by Odom

  1. On 4/7/2021 at 2:07 AM, AC-Gamer said:

     

    This forum post is a bit different then what I'm looking for as it doesn't talk about the dell r710, should there be anything I need to watch out for when picking a LSI card? 

     

    In my build I had purchased an LSI 9201-16i card. I can't explain the technical details, I also asked around in this forum and wanted a card that could hook up  to 16 internal drives. At the time this was recommended, so I got it 😀

     

    My unRaid server is running 10x WD 14TB drives. Their designation is WDC_WD140EDFZ-11A0VA0. These a re all shucked drives from the WD My Book 14TB external storage. I purchased these drives whenever they were on sale on Amazon. They all work just fine in my server, I have no issues.

  2. I see what I did wrong.... On the New Config screen, I did select "Retain current assignments", but I forgot to check the box "Yes, I want to do this".....

    I now managed to go through the steps you outlined and Parity 2 is rebuilding:

     

    image.png.28a1186f319100658a1651bd5bc684ce.png

     

    Thank you very, very much for your help!! 😀

     

    Happy New Year to all!!

     

    Odom

  3. On 12/31/2020 at 2:26 PM, itimpi said:

    You would have to do another New Config to re-arrange the remaining drives.    Since the parity2 calculation takes into account drive position this would invalidate parity2.   Parity1 is unaffected by disk position - just that the same drives are involved.  I think the best way to do what you want would be:

    • do the New Config option with the option to retain current assignments
    • return to the Main tab and unassign parity2, and move disk12 to its new position (didk9?).   If any disks need moving between slots for any reason now is the time to do it.
    • tick the Parity is Valid checkbox and start the array to commit the assignments.    The array should mount all devices and will be protected by parity1
    • stop the array
    • assign parity2 again
    • start the array to rebuild parity2 with the new disk assignments.
    • (optional) run a non-correcting parity check.    If everything is good this will report zero errors.

    I tried following your procedure. In Step 2 I re-assigned all the drives so that the numbers would be sequential, and unassigned Parity 2:

    image.thumb.png.a5157976b8dc9ba3fa246ddfa492d29f.png

     

    However in Step 3 it doesn't allow me to start the array. I do not see the option "Parity is valid". Did I do something wrong?

     

  4. I finally got around to doing the procedure and my array is now rebuilding the parity information. I simply unassigned the drives I wanted to remove later, so my array now  looksl ike  this:

     

    image.png.ce9987827f835d27a6520562c9f3f77a.png   image.png.746f2f678fd31162a972666784380f46.png

     

    As you can see, some disk numbers are missing, as they are listed further down in the Unassigned Devices. Is this an issue?

    Once the parity is done, I plan to shut down the server and physically remove the 4 drives in the Unassigned Devices. At that point, and before I start the array back up, can I re-assign the drives to sequencial numbers? For example, switch Disk 5 to Disk 4, then Disk 6 to Disk 5, so that they are sequential numbers again. Or will the array do this automatically once I remove the older drives?

     

    Thank you all again for all your help so far, and I wish you all a Happy New Year!!

     

    Odom

     

  5. 3 minutes ago, jonathanm said:

    Yes.

     

    Are the drives you are planning to remove already empty?

    Yes, I used unBalance to skatter all the data from those two drives and confirmed via Krusader that nothing is on them. I also removed them from the Share Settings, so that nothing would be re-added to them.

     

    Thanks very much to the both of you, I'll go and try that then.

     

    Regards,

    Odom

     

  6. Hello,

     

    I would like to remove two disks in my array, in order to reduce the amount of disks used. I replaced some 6TB disks with 14TB ones, and now that I have more space I would like to remove two other 6TB disks. The goal is to reduce the number of disks in the case (and I don't need those disks anymore).

    I have 12 disks in my array, +2 parity drives

     

    On Reddit somebody pointed to this procedure on a related post:
    https://wiki.unraid.net/Shrink_array#Procedure

    Quote

    Procedure

    1. Make sure that the drive or drives you are removing have been removed from any inclusions or exclusions for all shares, including in the global share settings. Shares should be changed from the default of "All" to "Include". This include list should contain only the drives that will be retained.
    2. Make sure you have a copy of your array assignments, especially the parity drive. You may need this list if the "Retain current configuration" option doesn't work correctly
    3. Stop the array (if it is started)
    4. Go to Tools then New Config
    5. Click on the Retain current configuration box (says None at first), click on the box for All, then click on close
    6. Click on the box for Yes I want to do this, then click Apply then Done
    7. Return to the Main page, and check all assignments. If any are missing, correct them. Unassign the drive(s) you are removing. Double check all of the assignments, especially the parity drive(s)!
    8. Do not click the check box for Parity is already valid; make sure it is NOT checked; parity is not valid now and won't be until the parity build completes
    9. Start the array to commit the changes; system is usable now, but it will take a long time rebuilding parity

    ...copy-paste for ease...

     

    However, the person asking at the time had 1 parity drive, whereas I have 2 parity drives. Would the same procedure still apply?

  7. 9 hours ago, ich777 said:

    Ja und nein, ich kann dir auch textabschnitte senden, die helptext.txt ist der größte Brocken (ca 2.000 Zeilen und bin ca. bei Zeile 350).

    Das kannst Du gerne machen. Kannst Du sie mir über das Forum schicken, oder soll ich Dir meine Email Adresse per PN geben?

  8. A couple  of weeks ago I was watching a video of Linus Tech Tips and he used this case: Define 7 XL

    Define 7 XL Dark Tempered Glass

    Define 7 XL Light Tempered Glass

    That case not only looks amazing, but can fit up to 18 drives. It seems that every fan mount can also be used for mounting a drive. In Germany that case goes for about 200€. Looks much better and fits more drives than my crappy Rosewill R4000.

     

     

  9. So, quick feedback. I migrated to the new hardware, booted up and everything is fine. unRaid is really robust, love that thing :)

    Hit a minor snag, my Corsair radiator and the two fans are too big to screw into the central metal plate in my case. It is now wedged between the cables and the top lid.... For now it works, I'll think of something later.

     

    Many thanks for the help again :)

  10. I would prefer copper, I don't know my way around the ports and connections that the Mellanox ConnectX uses. I was planning on getting a 4 or 8 port Mikrotik GBe switch that uses RJ45. Thank you for the suggestion.

  11. Hello,

     

    I am looking to add a 10Gbe NIC to my unRaid Server. Is there maybe a list of recommended/compatible network cards, or an inofficial list where people write what they use and how it works? I tried the unRaid Wiki but nothing is mentioned there.

    I'm not looking for anything special, just to have a 10GBe NIC and be able to copy faster.

    Also, if I add another NIC to unRaid, do I have to do something to all the dockers? For instance, do I have to tell them to use the new NIC, or does that just work?

     

    Many thanks!

     

    Odom

     

  12. Hello,

     

    I upgraded my home PC and I want to use the old hardware to upgrade my unRaid build. I have been reading this foruma nd Reddit and just wanted to make sure I undestood the process correctly.

    I should take a screenshot of he drives setup, in case they don't get recognized in the proper assignments, and a USB backup. I have those.

    After this, I can simply swap out the motherboard, CPU and RAM.

    Then put in the USB stick, boot up, and that's it? Anything else I should pay attention to?

     

    My current and old unRaid is:

    Asus P6T Deluxe

    Core i7-950

    6GB RAM

    I would upgrade to:

    Asus Maximus VI Hero C2

    Core i7-4770K

    32GB RAM

     

    Many Thanks!!

  13. Thanks for finding that. In which log did you see this?

    Yes, the mainboard is quite old. It is an Asus P6T with an Intel Core i7-950. According to the Asus website, the latest firmware available is from 09/11/2010, I can give that a go.

    This is my first unRaid build and I didn't want to go all out with something brand new without having any experience with unRaid. Now that it is working quite well, I was planning to upgrade to one of the new AMDs and more cores and RAM.

    Thanks again for finding that!!

  14. Quick update,

    I noticed the parity check didn't run on the 1st November due to the Server being shut down during the scheduled time. In October it indicated 7 errors after the parity check completed, but everything was working fine until yesterday. I now started a parity check, but that will take about 17 hours.

  15. I noticed today that I can't make any file changes to my shares (read-write, create files, delete files, etc...). I had this once in the past and a reboot of my unRaid server solved it. This time I still have the issue after my reboot. I don't know how to troubleshoot this in unRaid. The top-right button that says Logs doesn't show me any issues.

     

    I have multiple shares that the account I am using has RW permissions on. I have a Windows 10 PC and 3 of those shares I mapped to a drive (ex: \\192.168.0.110\Software O:). Any changes I try and make in this and other shares I get Access Denied messages from Windows.

    I tried remapping the share in Windows with the user account and I still get the same error. If I go straight to the share (without having the drive mapped) I get the same message.

    Using Krusader I can make  any change I want.

    I have unRaid Version: 6.7.2 installed. Could someone point me in the right direction on how to start troubleshooting this? Maybe where I can find logs for authentication errors?

     

    Many thanks!!

  16. On 10/17/2019 at 9:32 PM, JT24 said:

    How did you end up going with this?

     

    On 10/18/2019 at 9:28 PM, jordanmw said:

    Also curious what you are doing for this- have you tried using RRTR?

    Sorry for the late reply. I ended up using Syncthing to synchronise the data. Qnap has an alternate inofficial appstore aclled Qnapclub (https://www.qnapclub.eu/en). They have instructions on their website on how to add it to your Qnap Apps app. From there you can install Syncthing.

    I did run into an issue though, Syncthing apparently doesn't work on Atom CPUs. Both my aprents and brother's Qnaps have a Celeron CPU and there I can install Syncthing. My parents-in-law have one with an Atom CPU and I can't get it installed there.

    I used Spaceinvader One's video on how to configure Syncthing, as the tool wasn't straightforward to me.

     

    • Like 1