Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,812

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Use a molex to SATA adapter, connect the missing disk(s) to the onboard SATA ports and check if the disks are detected in the BIOS.
  2. JorgeB
    Please don't start multiple threads for the same issue, already replied in your other thread, lest continue there.
  3. JorgeB
    Lots of uncorrectable errors, run another one and post the diags after it's done.
  4. JorgeB
    The NVMe device is failing and needs to be replaced. Not really surprising considering the total writes, wow! Data Units Written: 6,252,778,690 [3.20 PB]
  5. JorgeB
    No btrfs filesystems are being detected on boot suggesting they are not connected or were wiped, you only have an NVMe device assigned as cache, was that a previous cache device? Any more previous cache devices still connected?
  6. JorgeB
    Yes, that will show the profiles in use, both data and metadata should only be using one profile, and both raid1 in this case. The old device was still part of the pool, doesn't really matter if there's data there or not to remove the device, except for the time it will take, for a more detailed view you can use in the console: btrfs fi usage -T /mnt/cache
  7. JorgeB
    Nvidia 600 and 700 series models usually need an extra setting to work with v6.10.x, see below: https://forums.unraid.net/topic/124890-gtx650ti-code-43-with-windows-10/?do=findComment&comment=1139615
  8. JorgeB
    Yes, Settings -> Network Settings -> IPv4 address assignment -> Static then set the IP
  9. JorgeB
    Use syslog server.
  10. JorgeB

    docker errors

    JorgeB replied to atakan's topic in Docker Engine

    Then it suggests a plugin is the problem, remove them and start installing them one by one to see if you can find the culprit.
  11. JorgeB
    Not possible, but these addresses can change if you change/add/remove any harware, it's done by editing the VM config, in the end, it should be under "other PCI devices", just unselect it with the VM stopped, e.g.:
  12. JorgeB
    Controller is OK, only the LSI HBA is being used. Initial issue appears to have been a power problem, multiple disks dropped at the same time. Disk10 does appear to be showing some issues, run a long test and even if it passes any more read errors I would recommend replacing it.
  13. JorgeB
    Docker image is corrupt, you need to delete and re-create, before doing that run a scrub on the pool and make sure all errors are corrected, no signs of a device problem that I can see, at least in these diags.
  14. JorgeB
    Docker image is corrupt, but since the log rotated and we can't see the initial boot please reboot and post new diags after array start.
  15. JorgeB
    You're passing-through this controller to your VM: 08:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] Kernel driver in use: vfio-pci Kernel modules: ahci So when the VM starts any disk connect there will be inaccessible.
  16. JorgeB
    Jul 29 23:33:35 megatron kernel: nvme nvme1: globally duplicate IDs for nsid 1 Looks like this kernel issue: https://bugs.archlinux.org/task/74916
  17. JorgeB
    That suggests a hardware issue, PSU or board would be the main suspects, could also be the UPS if you have one.
  18. JorgeB
    Usually you just need to set the share minimum free space, it should be set to twice the largest file you expect to copy to that share.
  19. JorgeB
    No, but you only posted the diags after rebooting, check the syslog server for a shutdown event, or post that after the next one.
  20. JorgeB
    Pool is using the default raid1 profile, you can remove the other device, and it will be quick since it's empty.
  21. JorgeB
    Device Model: ST4000VN000-1H4168 Serial Number: Z303VK8Z SMART test failed, disk should be replaced. Device Model: ST4000VN000-1H4168 Serial Number: Z3034J5D OK for now. Device Model: ST16000NE000-2RW103 Serial Number: ZL269LBE Wait for the extended test to finish and check the result, but it should pass.
  22. JorgeB
    Not sure you can close that window, you can run xfs_repair manually on the console if it keeps crashing: xfs_repair -v /dev/sdn1
  23. JorgeB
    Need to run the fix option.
  24. JorgeB
    Try checking the filesystem on sdn using UD, click on the checkmark left side of the partition.
  25. JorgeB
    Post new diags after the mount attempt. Possibly, if it really was parity and if you know if it was parity or parity2.
×
×
  • Create New...