JorgeB

Moderators
  • Posts

    37988
  • Joined

  • Last visited

  • Days Won

    442

Community Answers

  1. JorgeB's post in GTX650ti code 43 with Windows 10 was marked as the answer   
    @songI can replicate your issue with a GTX670, works fine with v6.9 and get code 43 after updating to v6.10, I found that this works for me, please try it, edit the XML and in the features section, below </hyperv> add this:
     
    <kvm> <hidden state='on'/> </kvm>  
    Note that if you have "fast startup" enabled in Windows, and it's enabled by default, first boot after the change will still have the problem, you need to re-start the VM (not shutdown and turn on again).
     
    P.S. besides the code 43 issue I also had to dump the VBIOS to use the GTX670 with v6.10, but that's a different issue since there's no display output without it.
  2. JorgeB's post in (SOLVED) (6.10.1 -> 6.10.2) Unraid refuses to start after update was marked as the answer   
    Based on the dates those diags look old, if Unraid is not finishing boot start by trying to boot in safe mode, if still the same try with a new trial flash drive, just to see if it boots.
  3. JorgeB's post in Cache pool BTRFS missing device(s) was marked as the answer   
    Cache device dropped offline:
     
    Jun 23 07:43:03 ForwardUntoDawn kernel: ata2.00: failed to IDENTIFY (I/O error, err_mask=0x100) Jun 23 07:43:03 ForwardUntoDawn kernel: ata2.00: revalidation failed (errno=-5) Jun 23 07:43:09 ForwardUntoDawn kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jun 23 07:43:09 ForwardUntoDawn kernel: ata2.00: failed to IDENTIFY (I/O error, err_mask=0x100) Jun 23 07:43:09 ForwardUntoDawn kernel: ata2.00: revalidation failed (errno=-5) Jun 23 07:43:09 ForwardUntoDawn kernel: ata2.00: disabled  
    Then it came back with another identifier, suggest you shut down, check/replace cables, power back up and the device should be correctly assigned, if yes just start the array, if not start it without that device assigned, then stop, re-assign it and start again.
     
  4. JorgeB's post in [6.10.3] Cache SSDs "overheating?" issue was marked as the answer   
    It's a problem with that device and newer kernels:
     
    https://us.community.samsung.com/t5/Monitors-and-Memory/SSD-980-heat-spikes-to-84-C-183-F/td-p/2002779
     
     
  5. JorgeB's post in HELP: BTRFS Cache Unmountable: Invalid pool config was marked as the answer   
    You just need to unassign them all, them when the disks are re-formatted xfs (or btrsf encrypted) just re-assign all the pool devices and start the array, it will import the existing pool.
  6. JorgeB's post in Some or All files unprotected - Yes I have done the basics. was marked as the answer   
    Any shares that have data on a single device pool will appear as unprotected, since there's no redundancy, that's normal.
  7. JorgeB's post in HDD Errors on 11 drives was marked as the answer   
    It does look like the exact same issue, which is strange since so far it's only been found on mostly HP and similar servers from the same era, your hardware is completely different, suggest either disabling VT-d or updating to v6.10.3-rc1 which I'm confident fixes this issue, since you have array auto start disabled you can safely boot the server and update, then reboot, start the array and post new diags (same if you just prefer disabling vt-d for now).
  8. JorgeB's post in Can't get HDD to be recognized was marked as the answer   
    Looks like a bad device:
     
    device Test Unit Ready [medium or hardware error (serious)]  
  9. JorgeB's post in Upgraded to 6.10.3, one disk now says "not installed", worked fine before, reverted to 6.9.2, still says that. was marked as the answer   
    That's inevitable if you start the array with a missing disk, in normal or maintenance mode.

  10. JorgeB's post in Unsure how to proceed with multiple failed/failing drive replacements was marked as the answer   
    If there's no old parity2 and assuming old disk2 is also dead your best bet it to try and copy everything you can from the emulate disk2, this way you'll now what data fails to copy, you could also clone old parity with ddrescue then rebuild, but that way no way of knowing the affected files on the rebuilt disk, unless you have pre-existing checksums for all files.
  11. JorgeB's post in Unraid stop responding after a while, kernel panic? was marked as the answer   
    That looks related to the macvlan issue:
     
    See if this applies to you, if yes, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info.:
    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/
     
     
  12. JorgeB's post in Unraid won't boot after update was marked as the answer   
    If it boots in safe mode it suggests a plugin problem, remove/rename plugins then install one or a few at a time until you find the culprit.
  13. JorgeB's post in cache disk Partition format : MBR: 1MiB-aligned was marked as the answer   
    Any SSD, doesn't matter if it's in the array or in a pool, will be 1MiB aligned, this is done for performance and write amplification issues.
  14. JorgeB's post in Docker Service failed to start. was marked as the answer   
    Docker image is corrupt, delete and re-create.
  15. JorgeB's post in Fastest way to replace parities and 2 other drives? was marked as the answer   
    You could upgrade the two parity disks at the same time then upgrade the two data disks also together, just two rebuilds total, of course there's also more risk than doing one at a time, recommendation will depend on the backup situation, etc.
  16. JorgeB's post in One data disk has red cross, all disks showing again in unassigned devices, most data folders blank was marked as the answer   
    Run it again with the --rebuild-tree flag, note that it will take a few hours.
  17. JorgeB's post in Upgrade 6.9 > 6.10 Login issue was marked as the answer   
    Do the recovery password procedure anyway, it should ask you to create one after that:
     
    https://wiki.unraid.net/Manual/Troubleshooting#Lost_root_Password
  18. JorgeB's post in Cache Pool disk 1 of 2 (BTRFS R0) Won't Assign without Wipe was marked as the answer   
    If Docker/VM services are using the cache pool disable them, unassign all cache devices, start array to make Unraid "forget" current cache config, stop array, reassign all cache devices (there can't be an "All existing data on this device will be OVERWRITTEN when array is Started" warning for any cache device), re-enable Docker/VMs if needed, start array.
  19. JorgeB's post in new build - NVME drive not appearing anywhere (expecting it in unassigned devices) was marked as the answer   
    Jun 15 15:17:32 Cygnus kernel: ahci 0000:00:17.0: Found 1 remapped NVMe devices. Jun 15 15:17:32 Cygnus kernel: ahci 0000:00:17.0: Switch your BIOS from RAID to AHCI mode to use them.  
  20. JorgeB's post in Server inaccessible after upgrading to 6.10.3 and after rollback to 6.9.2 was marked as the answer   
    Nothing obvious to me, I would suggest enabling DHCP, that way we can better see if it's communicating with the router.
  21. JorgeB's post in Are these drives really failed? was marked as the answer   
    Both passed so they should be OK for now, suggest swapping cables/slots with another drives to rule that out and re-use them.
  22. JorgeB's post in [Unraid V6.9.2] SAS drives smart monitoring was marked as the answer   
    I believe it's planned, but don't know an ETA.
  23. JorgeB's post in Address not set was marked as the answer   
    You have link on eth1 but not on eth0, either swap the LAN cable to the other NIC or boot using GUI mode and go to Settings -> Network Settings -> Interface rules and make eth1 eth0
  24. JorgeB's post in Freeze and crash during parity-check was marked as the answer   
    Unraid driver is still crashing, unclear to me from your first post if it now also crashes with v6.8 or v6.9? if you see this same issue with different Unraid releases, I would really suspect a hardware problem.
  25. JorgeB's post in (SOLVED) unRAID crashes randomly, can't find cause was marked as the answer   
    May 5 10:26:53 LuNAS kernel: ? Sys_DumpTask+0xe9/0xf1 [corefreqk] May 5 10:26:53 LuNAS kernel: Cycle_AMD_Family_17h+0x31b/0xb37 [corefreqk]  
    Unisntall the corefreq plugin.