Jump to content

JorgeB

Moderators
  • Posts

    61,692
  • Joined

  • Last visited

  • Days Won

    650

Posts posted by JorgeB

  1. You have something creating this folder before the array starts:

     

    Apr 28 04:40:42 Node emhttpd: error: malloc_share_locations, 7199: Operation not supported (95): getxattr: /mnt/user/CommunityApplicationsAppdataBackup

     

    You need to correct that, or the shares won't then work correctly.

  2. 10 hours ago, couzin2000 said:

    Server back on, my array is completely different-- my disks were all mixed up and not able to start because somehow the parity disk had been moved to the data disks...???

    That suggests a flash drive problem.

     

    10 hours ago, couzin2000 said:

    Now, my array is in the same config, only the Parity drive is showing as a NEW DEVICE. It's exactly the same drive in the same spot! Am I going to lose everything here? the array doesn't want to start anymore because It's say "Too many wrong and/or missing disks!"

    If you have all the original disks assigned to the correct slots, you can do a new config and check "parity is already valid" before array start, then start array and you can try replacing the bad disk again.

     

  3. 13 hours ago, crittersfritters said:

    as it's not nearly old enough to be failing.

    Any hardware can fail at any time, even new one.

     

    13 hours ago, crittersfritters said:

    Assuming faulty hardware is not the root cause, what else could be causing complete shutdowns with no logging?

    If the server shutdowns, vs. crashing or hanging, first suspects would be CPU temp or bad PSU, could also be board related.

×
×
  • Create New...