Kung-Fubick

Members
  • Posts

    29
  • Joined

  • Last visited

Posts posted by Kung-Fubick

  1. My lingo might not be up to speed on the subject but I will try my best to explain. 
    By parity copying I meant the following:
    I had an array with 1 HDD in it that contains data.
    I stopped the array.
    I added a parity drive.
    Now when starting up the array the parity disk has to write to copy the original HDD data.

    Bought the disks from an old colleague, told me they were previously unused. (3 TB Seagate x2)

    I will attach new diagnostics, note that these are after stopping and starting the array. If this makes a difference I can try and run the parity check tomorrow again and then post diagnostics.

    nas-diagnostics-20210117-0015.zip

  2. Hi I am relatively new to Unraid and am currently trying out the trial version to see if I should get a license to use as a NAS as a few docker containers. I have tried starting my array of 2 disks several times at this point but the parity check (or parity copying) always fails at 70.2%. I found a few other threads that suggested changing the SATA port on the MB and changing the cables but even after doing so it seems like the disk still fails. I will attach logs in this post for anyone that could see if they  can find any information in them. But to my understanding the parity HDD is dead? I am going to try to run the Preclear disk Utility over night to see if it does anything different.

    I also have 2 simpler questions. 
    Does Unraid usually take a long time to reboot and it seems like it has an effect on the amount of time my BIOS takes to boot, is this normal? (probably takes 5 minutes in comparison to my workstation which usually takes 2 sec.)

    Had some trouble with the automatic formatter when starting the array. Had to use Fdisk in the terminal to change the partition type and then it could format and mouint the drives, is this intended?

    Thankful for any help,
    Kung-Fubick

    nas-syslog-20210116-2254.zip