Jump to content

trurl

Moderators
  • Posts

    43,974
  • Joined

  • Last visited

  • Days Won

    137

Posts posted by trurl

  1. 17 minutes ago, michaelhthomas said:

    the only errors I see in the syslog appear to be related to a corrupted docker image?

    You must have overlooked all these:

    May 13 08:21:13 Gringotts kernel: md: disk1 read error, sector=2312
    May 13 08:21:13 Gringotts kernel: md: disk2 read error, sector=2312
    May 13 08:21:13 Gringotts kernel: md: disk3 read error, sector=2312
    

    And lots more before and after.

     

    Since multiple disks are involved, probably a power or controller issue.

     

    Any power splitters?

  2. The config folder from your flash backup has all of your configuration when the backup was made. You can copy that config folder to a new install. See if you can still use the same flash so you won't have to transfer the license. 

     

    You should consider getting UPS for your server. 

  3. 1 minute ago, Boy Kai said:

    Disk 8 and Disk 12 are still showing red Xs

    Repairing the filesystem will not fix that. But it will allow you to rebuild a mountable filesystem now.

     

    Looks like repair didn't create any lost+found, and the emulated disks are mounted with plenty of data.

     

    You can rebuild both at the same time.

     

    https://docs.unraid.net/unraid-os/manual/storage-management/#rebuilding-a-drive-onto-itself

  4. Corrupt docker.img. Seems unlikely that you would have filled it though. Have you done memtest? If not, you might do that before anything else just in case. You never want to run any computer unless memory is working perfectly.

     

    You will have to delete, recreate, reinstall docker, but we will get to that later.

     

    Your appdata and system shares have files on the array.

     

    Ideally, appdata, domains, system shares would have all files on cache or other fast pool, with nothing on the array, so Dockers/VMs will perform better, and so array disks can spin down since these files are always open.

     

    Nothing can move or delete open files, so you will have to disable Docker and VM Manager in Settings before you can work with these.

     

    Then set these shares to Primary:cache; Secondary:array; Mover action:array->cache.

     

    Then run Mover, wait for it to finish, and post new diagnostics.

  5. 1 hour ago, BubbaLight11 said:

    I'm not 100% sure what I'm being asked to do.

    The link is about changes to make in your BIOS to make your Ryzen server more stable.

     

    Do you know how to access your BIOS?

×
×
  • Create New...