Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,662

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Tools -> New Config -> Keep all assignments, then assign the new drive and check "parity is already valid" before starting the array.
  2. JorgeB
    See here for more info on this and some workarounds:
  3. JorgeB
    It's an Unraid/GUI bug, you can still do it manually using the console.
  4. JorgeB
    Forgot to mention, this is not a reason for a disk getting disable, I've been using several SMR disks in some of my servers, including 8 disks like yours (but the 4TB model) and never had any issues, other than the sometimes expected performance penalty.
  5. JorgeB
    No, disk 1 is using the onboard SATA controller, disk 3 is on an LSI. Replace SATA cable for disk1, also replace power cables, if not available swap power cable with another disk and see where the problem follow, for disk3 you can just swap cables with a different disk on the LSI. After booting search the syslog for mpt2sas, then click next until you find the line where it mentions the firmware.
  6. JorgeB
    Disk looks OK, syslog rotated so can't see the LSI firmware version, make sure they are on 20.00.07.00, then if the emulated disk is mounting correctly rebuild on top, good idea to replace/swap cables/slot to rule that out. P.S: lots of ATA errors on disk1, likely a power/connection issue.
  7. JorgeB
    See here, make sure it's using the correct "power supply idle" setting.
  8. JorgeB
    *Should*, difficult to have more than 1 bad DIMM at the same time, but of course not impossible.
  9. JorgeB
    It will keep running until you stop, if one pass found the error it should be enough, at least for now.
  10. JorgeB
    Timeout for VMs is set to 5 minutes but it wasn't enough, you can stop the array and time how long it takes and set that timeout accordingly, personally I always shutdown/hibernate all my VMs prior to rebooting.
  11. JorgeB
    Those are after rebooting.
  12. JorgeB
    Macvlan call traces are usually the result of having dockers with a custom IP address, more info below. https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/
  13. JorgeB
    If it didn't finish the clear it's fine, disk can still be unassigned from the array.
  14. JorgeB
    Try removing the gateway from eth2
  15. JorgeB
    OK, mentioned it because you said you did it manually, and that way it always needs renaming, also make sure you ran "make_bootable" as admin.
  16. JorgeB
    If you're booting UEFI you need to rename EFI- to EFI on the flash drive.
  17. JorgeB
    That's not how you rebuild on top, see below: https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself
  18. JorgeB
    Log doesn't cover it but those errors suggest one of the NVMe devices dropped offline at some point in the past, see here for better pool monitoring for the future. As for the current issue, reboot then immediately run a scrub to see if it can bring the other device up to date, if the fs goes read only again best bet is to backup and reformat.
  19. JorgeB
    Not needed.
  20. JorgeB
    When the array is not cleanly shutdown Unraid creates diags in the logs folder of the flash drive, post those, they might show what the problem is.
  21. JorgeB
    Yeah, I didn't mention it because it should be obvious, before attempting any more filesystem repairs you need to fix the RAM issue.
  22. JorgeB
    Controllers seem to be working fine, since they have a BIOS flashed see if the drives are detected there.
  23. JorgeB
    Please post the diagnostics: Tools -> Diagnostics
  24. JorgeB
    You're missing the trailing slash on source, that will create a new folder on dest with the "dest folder" name, i.e., /mnt/dest_disk/folder/folder/, trailing slash on dest is optional but to avoid confusion I recommend always using on both, e.g.: rsync -avX --remove-source-files /mnt/disk1/folder/ /mnt/disk2/folder/
  25. JorgeB
    Please post the diagnostics: Tools -> Diagnostics
×
×
  • Create New...