Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,675

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Disk dropped offline, looks more like a power/connection problem, replace cables or use a different slot and try again.
  2. JorgeB
    Like mentioned you should post the full diags, also was it working before and it started doing this without any change, or did it start after some hardware change or Unraid update? There have been other similar reports, with very different hardware, and since it's the Unraid driver crashing it might b a good idea to open a bug report.
  3. JorgeB
    It's normal to see some reads every few seconds from SMART, those don't prevent the drives from sleeping, writes are not normal.
  4. JorgeB
    Should be OK to ignore, looks like it's not being used by anything important.
  5. JorgeB
    Logs on bare metal are clear so far.
  6. JorgeB
    Then it's not a plugin problem, you can create new keys and make sure all is correctly configured, IIRC we already went through this with you in another thread.
  7. JorgeB
    Then don't knwon, sorry, except for a couple of SSDs I don't use SAS devices.
  8. JorgeB
    No, and it's not clear to me after reading your post if pass-wordless SSH started working in safe mode, did it?
  9. JorgeB
    See a lot of HBA issues, also some CPU, if you can it would be good to test bare metal first.
  10. JorgeB
    See if it's the same as this: https://forums.unraid.net/topic/110835-solved-help-with-a-sas-drive/?do=findComment&comment=1011689
  11. JorgeB
    Parity disk looks like a connection issues, replace cables, same for Cache1, disk3 might be failing, we'll see during the parity sync.
  12. JorgeB
    Something very weird happened, like mentioned I can't say what since the filesystem was gone at boot time, if it had been wiped by mistake the command above should have worked, but some data was lost, I remember that the Kingston SV300 is the only SSD that caused sync errors when used in the array after a reboot/power cycle, so it could be a device problem.
  13. JorgeB
    IIRC that is on purpose, if you pass a device my mistake (like the wrong disk controller) to a VM and it's set to autostart you can lose array access and not be able to easily fix it, this way you disable array auto start, star array and can then correct the XML.
  14. JorgeB
    Write performance with SMR drives can downgrade by a little or a lot, some models behave better than others, that one appears to be one of the worst, and not consistent, i.e., one disk can perform OK and another same of model can perform extremely bad.
  15. JorgeB
    Also check your spam folder, you should have received the invoice immediately.
  16. JorgeB
    I don't know what happened to that device but there's no valid filesystem there, so don't see how to recover.
  17. JorgeB
    These are SMR and write performance can downgrade, sometimes a lot.
  18. JorgeB
    Try downgrading back to v6.9.1, there are some known spin down issues with 6.9.2
  19. JorgeB
    See if this applies to you: 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/
  20. JorgeB
    Disk dropped offline so there's no SMART, check/replace cables and post new diags after powering back up.
  21. JorgeB
    Without nothing logged in the syslog it's usually hardware related, but one thing you can try it 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.
  22. JorgeB
    See if you can get a new one or not much we can see.
  23. JorgeB
    I can see what happened since after the reboot there wasn't a valid btrfs filesystem on that SSD, looks like it was wiped, you that's what happened you can try this, with the array stopped: btrfs-select-super -s 1 /dev/sdX1 Replace X with correct letter.
  24. JorgeB
    Don't think so, but ask in that thread, I don't have any of those disks.
  25. JorgeB
    First see if it starts working in safe mode.
×
×
  • Create New...