Jump to content

JorgeB

Moderators
  • Posts

    64,886
  • Joined

  • Last visited

  • Days Won

    685

Community Answers

  1. JorgeB's post in Kernel panic crashes whole server was marked as the answer   
    Change to ipvlan or if you really need macvlan disable bridging.
  2. JorgeB's post in webui says my flash drive is corrupted - Your flash drive is corrupted or offline was marked as the answer   
    https://docs.unraid.net/unraid-os/manual/changing-the-flash-device/
  3. JorgeB's post in unraid randomly freezes was marked as the answer   
    That would suggest more a hardware issue, did you enable the syslog server to see if there's something there?
  4. JorgeB's post in Trying to transfer folder between two servers, local network... was marked as the answer   
    Can't help with SCP, but it might be easier to enable an SMB/NFS share in Openmediavault and then use UD to connect to it.
  5. JorgeB's post in Cannot Login to Unraid OS was marked as the answer   
    https://docs.unraid.net/unraid-os/manual/users/reset-password/
  6. JorgeB's post in Your server has run out of memory, and processes (potentially required) are being killed off was marked as the answer   
    https://forums.unraid.net/topic/113037-docker-advanced-view-reflect-memory-limit/?do=findComment&comment=1029211
     
    No ATA errors so far.
  7. JorgeB's post in Docker Service failed to start was marked as the answer   
    Try recreating the docker image:
     
    https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file
    Then:
    https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications
    Also see below if you have any custom docker networks:
    https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks
  8. JorgeB's post in Can’t create a striped or mirrored ZFS pool with Unraid 7 was marked as the answer   
    Known issue, fixed for beta.2, but it's only visual, it will still create a stripe or mirror if you apply that before formatting.
  9. JorgeB's post in Extremely slow parity check was marked as the answer   
    Errors continue, if you replaced both cables it could be a bad disk, you can swap cables with a different disk to make sure, see where the problem follows.
  10. JorgeB's post in Help on ASUS P5K bios boot was marked as the answer   
    The Sandisk should be the first option here:

     
    Then save setting and reboot
     
     
  11. JorgeB's post in log full spammed with read error during parity sync was marked as the answer   
    Syslog rotated, and is missing the start of the problem, type reboot in the CLI then post new diags after array start.
  12. JorgeB's post in Docker and VMs Won't Start was marked as the answer   
    Looks like there were some lost writes, likely to the underlying device.
     
    If the vdisk is OK, you should be able to use a new libvirt image, then create a VM with the same settings and point to the existing vdisk.
     
    Recommend keeping a backup of that file for the future.
  13. JorgeB's post in Empty file after errors in parity check was marked as the answer   
    There are errors in most disks, so Unraid cannot emulated them, reboot and post new diags after array start.
  14. JorgeB's post in FUSE By-Pass was marked as the answer   
    Yes.
  15. JorgeB's post in Parity 2 has read errors but pases short test was marked as the answer   
    If it's a refurb I do at least an extended SMART test or precelar to confirm it's good.
  16. JorgeB's post in Cache pool lost after power outage was marked as the answer   
    Add both pool devices to the pool and start the array, it should import the existing pool.
  17. JorgeB's post in My docker turns off was marked as the answer   
    Those SQUASHFS errors usually mean a flash drive problem.
  18. JorgeB's post in Sudden system crash by Windows VM was marked as the answer   
    Not really, that looks more related to the hardware you running, possibly some incompatibility with the kernel/KVM, I would recommend retesting once 7.0.0-beta is out, which should be very soon, that one will use a much more recent kernel.
     
  19. JorgeB's post in Deluge stopped working no torrents found? was marked as the answer   
    Look for the existing support thread, click on the container and then support.
  20. JorgeB's post in Very slow re-build - weird HDD behaviour was marked as the answer   
    SMART looks fine, so most likely power/connection issue, avoid splitters, especially if they are splitting one plug to more than 2 disks.
     
  21. JorgeB's post in Replace all disk in an array without loosing cache and settings was marked as the answer   
    Yes, but as mentioned you need to do a new config (Tools - New Config)
  22. JorgeB's post in No space left on device was marked as the answer   
    Floor for the TV share s set to about 1TB, you can lower that.
  23. JorgeB's post in Cache pool dissapered how to safely get it back? was marked as the answer   
    Unassign both pool devices, start array, stop array, this will reset the pool config, re-assign both pool devices, start array, existing pool should be normally imported, but if it doesn't mount post the diagnostics.
  24. JorgeB's post in Unraid not seeing my NVME drive after update (see it it BIOS) was marked as the answer   
    The NVMe device is bound to vfio-pci, unbind it, and also check that Asmedia controller, in case it's also bound by mistake:
     
    02:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [144d:a808]     Subsystem: Samsung Electronics Co Ltd SSD 970 EVO/PRO [144d:a801]     Kernel driver in use: vfio-pci     Kernel modules: nvme 03:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1061/ASM1062 Serial ATA Controller [1b21:0612] (rev 02)     Subsystem: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:1060]     Kernel driver in use: vfio-pci     Kernel modules: ahci  
  25. JorgeB's post in "Disk in parity slot is not biggest." when using SSD as parity was marked as the answer   
    It should use the lower starting sector if you manually create the partition first, to do that, unassing parity, type:
     
    sgdisk -o -a 8 -n 1:32K:0 /dev/sdX  
    Replace X with correct letter, reassign the device as parity and see if it's now accepted.
×
×
  • Create New...