Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,771

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Drive is not even giving a valid SMART report, looks like disk problem.
  2. JorgeB
    Make sure UEFI boot is enable in Unraid, if the flash has a EFI- folder rename it to EFI
  3. JorgeB
    I assume you just need this device: lrwxrwxrwx 1 root root 13 Apr 23 14:06 nvme-TOSHIBA-RD400__664S107XTPGV -> ../../nvme1n1 lrwxrwxrwx 1 root root 15 Apr 23 14:06 nvme-TOSHIBA-RD400__664S107XTPGV-part1 -> ../../nvme1n1p1
  4. JorgeB
    Just upgraded one of my main servers from v6.9.2 to rc4 and one of the NVMe devices changed name and is "wrong", there's an extra underscore: No big deal I though, just reset the pool and it will use the new name, but it doesn't take, after resetting the pool and starting the array the device mounts but it continues to show the device as "new", note the blue icon: And after stopping the array: So I need to reset the pool every time I stop the array, this doesn't happen with the other NVMe devices and if I go back top v6.9.2 this NVMe device name goes back to how it was. tower1-diagnostics-20220423-1417.zip
  5. JorgeB
    Again there's something reading from disk3, writes with Unraid will be considerably slower any time there are writes to other disks or reads from the same disk it's writing to.
  6. JorgeB
    Next time please use the forum. Not seeing anything logged relevant to the crashing, could be hardware related, one thing you can try is to boot the server in safe mode with all docker/VMs disable, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one. As for the disks getting disabled see below:
  7. JorgeB
    Minimum free space is for user shares, not sure what that option is doing in the disk settings, likely a mistake.
  8. JorgeB
    There are writes going to two different disks.
  9. JorgeB
    Edit domain.cfg on the flash drive and change SERVICE="enable" to SERVICE="disable".
  10. JorgeB
    It will detect it but since each array disk is an individual filesystem it can't fix it, you can restore the affect file(s) from backups, it can detect and fix it for redundant pools. Like mentioned bitrot is way the down list of things to worry about, data corruption due to bad RAM or other hardware hardware issues, is much more common.
  11. JorgeB
    Disk looks healthy, looks like a power/connection problem.
  12. JorgeB
  13. JorgeB
    SMR drives can have slower writes with everything, including Unraid, though some drives perform better than others, I have some Seagate SMR drives that basically perform as CMR, WD and Toshiba SMR drives can be a lot slower, I have an SMR array where writes are as low as <5MB/s for a few minutes frequently.
  14. JorgeB
    @tucansamlike mentioned please don't post questions in the FAQ thread. Assuming you're on v6.9.2 there's v6.10.0-rc4 is available now, v6.10.0 should be available soon.
  15. JorgeB
    Make sure CSM boot is enable in the board BIOS, LSI BIOS won't show up with UEFI boot, HBA has a BIOS flashed so it should appear if booting CSM.
  16. JorgeB
    Disks 1 and 3 are SMR, try transferring to disk2, it should be faster.
  17. JorgeB
    ECC is always better for system stability/data integrity, not sure about ECC support with Ryzen, some conflicting reports from what I've read, I only use Intel hardware for Unraid so never really looked into it.
  18. JorgeB
    Nope, you can try googling it.
  19. JorgeB
  20. JorgeB
    Not since v6.9.x, driver doesn't build with newer kernel releases.
  21. JorgeB
    There's something reading from disk3, stop that activity to see if it helps.
  22. JorgeB
    Did you run memtest?
  23. JorgeB
    Depends on the flashed firmware, there's IT and RAID mode, though these usually still work even in RAID mode, but IT is still recommended.
  24. JorgeB
    Yes, assuming it's a HBA, not a RAID controller.
  25. JorgeB
    That controller uses SATA port multipliers, those are not recommended, you can cancel the rebuild, replace the controller then re-start rebuilding the disable disk.
×
×
  • Create New...