Jump to content

Gobble45

Members
 View Profile  See their activity

  • Posts

    13

  • Joined

  • Last visited

 Content Type 

Posts posted by Gobble45

    Disk in parity slot is not biggest.

    in General Support

    Posted

    Hey guys,

     

    so just last week i grabbed myself a few new drives for my array.

     

    The existing array was made up of mostly 8TB Drives, with a few 3 & 4TB drives. I grabbed two 10TB drives with the intention of one being a second Parity drive, and the other being added to the main array.

    Adding the second parity drive was fine. Time consuming, but fine. However adding the second 10TB drive to the main array keeps giving me the error "Disk in parity slot is not biggest." when i try starting the array.

    I've tried preclearing the disk. I've tried investigating the actual size of disks using terminal commands etc., but i still cant determine why this is happening. I've attached diagnostics.

     

    Any help is appreciated

    tower-diagnostics-20220221-1211.zip

    unRaid Server is performing reboot/shutdown around the same time as a parity check starts

    in General Support

    Posted

    On 1/10/2021 at 7:40 PM, ChatNoir said:

    Hey,

    If it was me, I'd look at an hardware issue and I'd start with Power.

    I see that you have 18 drives in the array plus 1 parity drive and 1 cache SSD.

     

    Depending on your PSU / APC capacity and healt, that might be a lot, especially during parity check.

    Thanks!

     

    I replaced my UPS (APC 700) shortly after i posted the OP. The older 700VA unit was giving me battery errors when testing. Sadly my unraid issues persisted.

     

    Since then i have replaced the PSU in the unraid server with an 850W unit (vs the 750W previously in it).

     

    I can confirm upping the PSU has resolved my issue. :)

     

    Parity check is at 0.5% thus far and hasnt shut down the server (previously wouldnt even hit 0.0% lol)

    • Like 1

    unRaid Server is performing reboot/shutdown around the same time as a parity check starts

    in General Support

    Posted

    Hi all,

     

    I've been battling with this issue for about 2 months now. It seems that every sunday my unraid server shuts down and fails to reboot. For a while now i thought it was due to an overheating issue (summer here in Australia). After cleaning the server from all its dust, and checking server temps it appears this is not the issue.

     

    You see - the server turns on, loads up unRaid, and then shuts down.

    Through trial and error, i've found that by loading up unRaid into Safemode- the server will stay running. After  manually rebooting from Safemode back into normal mode, it runs fine. After this, the server will continue to run fine until the following Sunday.

     

    I've taken a look at the scheduler, and saw that both the Parity Check, and Mover were set to run on Sundays - thinking that both running at the same time might be causing conflicts, i moved the Mover schedule to run every Monday instead. This has made no changes to the issue.

     

    After noticing the date/time settings were wrong on my unRaid instance (timezone set to default, and not +10 for East Australia), the random shutdowns changed to be occurring early hours Sunday for me.

     

    I performed an OS update about 1 week ago (After last sunday's shutdown). However the issue has occurred again today.

     

    Looking at the system logs, there isn't enough information to work with as it only shows all events since i restarted the server.

     

    I'm honestly not sure where to go from here. Without Logs - im flying blind.

     

    Can anyone offer some other things i might try?

     

    I have attached diagnostics for review

    tower-diagnostics-20210110-1607.zip

    Replacement Drive also unmountable

    in General Support

    Posted

    Hey there,

     

    Few weeks back i was hit with an unfortunate case of 'Unmountable: no file system' on Disk 3. I decided to unmount the array, remove that drive from the array, restart the array, stop the array, remount that drive as disk 3, and restart the array.

    I've done this in the past to resolve issues, and when replacing drives.

     

    I've now replaced what i thought was a faulty drive, however disk 3 continues to throw this error and cause me grief.

     

    I have tried rebooting, restrating array without a disk 3 (relying on Parity), replacing the drive (disk3) outright with another harddrive. I've swapped the SATA cable it is using, and even swapped the SATAPOWER cable it is using.

     

    I've done some research, and found a few fixes that have worked for others, but i dont want to try anything without having someone look over my logs, just in case i break things further.

     

    I am not really sure how to proceed. Logs attached. Thanks in advance for any suggestions.

    tower-diagnostics-20190704-2351.zip

×
×
  • Create New...