Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,411

  • Joined

  • Last visited

  • Days Won

    705

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    It's already using latest firmware: Mar 8 08:15:24 NAStheRIPPER kernel: mpt2sas_cm0: LSISAS2116: FWVersion(20.00.07.00), ChipRevision(0x02), BiosVersion(07.39.02.00) BIOS version (or if there's one) it's not important for Unraid.
  2. JorgeB
    Both SMART tests completed successfully, when there are no pending sectors these errors can sometimes be intermittent, I suggest replacing/swapping cables on both disks (power and SATA cables) then try again, post new diags if there are more errors.
  3. JorgeB
    Parity disk appears to be failing, you can run an extended SMART test to confirm. This was before the period covered on the posted diags, but if there were read errors on the parity disk during another disk's rebuild that disk will now have some corrupt data.
  4. JorgeB
    If that's the writing part of preclear it's normal, when disks get these slow sectors the problem is on reads, writes usually work normally.
  5. JorgeB
    Yes.
  6. JorgeB
    No problem, I expect this to be fixed next release.
  7. JorgeB
    Unlikely to be the controller, or multiple disks would have been affected, problem looks like a connection issue, though some times a healthy looking disk still has issues, hence why I recommended swapping cables, if the same disk fails again after that it's likely a disk problem.
  8. JorgeB
    Since the pool was already converted it's not possible to maintain the old profile, that would only be possible if you hadn't started the array with a missing device.
  9. JorgeB
  10. JorgeB
    When adding an extra device two a single device pool it will always convert to raid1, you can then convert to raid0, after that it will stay raid0 even if you add more devices.
  11. JorgeB
    If rebuilding to the same disk recommend replacing/swapping cables, just to rule them out if it happens again to the same disk.
  12. JorgeB
    Do you mean raid1? Pool was converted to single profile because it was started with a single device, you can now add back the original device and it will be convert to raid1, but best to wipe old device before adding.
  13. JorgeB
    Instead of: /boot/your.script use bash /boot/your.script
  14. JorgeB
    No sorry, I don't use encryption, but just unassigning the cache devices is safe, you do need to have some attention when re-assigning them back, you first need to start the array without any device assigned to the pool to make Unraid "forget" current cache config, then stop array, reassign all cache devices and start array, there can never be a warning like "all data on this device will be delete at array start", existing pool will be imported.
  15. JorgeB
    In that case I believe you can't use UD.
  16. JorgeB
    You can now use the UD plugin for that.
  17. JorgeB
    Backup config folder, recreate flash, restore config folder.
  18. JorgeB
    Where are those folders? Those do not exist by default.
  19. JorgeB
    Start by redoing the flash drive.
  20. JorgeB
    Yep, missed that one.
  21. JorgeB
    Yes, they both should have the same filesystem, and neither has one, like the superblock was wiped.
  22. JorgeB
    Disk1 appears to be failing, you can run an extended SMART test.
  23. JorgeB
    Your cache pool is completely full, you need to free up some space, then recreate the docker image.
  24. JorgeB
    They should work in ethernet mode, they won't work in infiniband mode.
  25. JorgeB
    Yes to the first question, you could then pass-trough the NIC to the VM or select it as the virtual interface to use.
×
×
  • Create New...