JorgeB

Moderators
 View Profile  See their activity

  • Posts

    61446

  • Joined

  • Last visited

  • Days Won

    646

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Reboot to clear the logs, run the mover again and post new diags but without being anonymized, so we can see the file names.
  2. JorgeB
    That's not unexpected giving that the issue with the other server is the flash drive dropping after boot, IMHO your best bet is still playing with any USB settings in the BIOS.
  3. JorgeB
    Yes.
  4. JorgeB
    That seems very unlikely to me, my first guess would be a disk problem. Not sure what you mean, it's reporting 800KB/s, not MB/s.
  5. JorgeB
    It's possible but I would guess very unlikely, if you have multiple sticks try with just one, if the same try with a different one, that will basically rule out bad RAM.
  6. JorgeB
    Unfortunately there's nothing relevant logged.
  7. JorgeB
    For the future, you just need to run the command in one of the pool devices, since it's the same filesystem.
  8. JorgeB
    You can try this first to see if it helps with the PICe errors: https://forums.unraid.net/topic/118286-nvme-drives-throwing-errors-filling-logs-instantly-how-to-resolve/?do=findComment&comment=1165009
  9. JorgeB
    Syslog in the diags starts over after every boot, enable the syslog server and post that if it happens again, but if I understand correctly the server did shutdown on its own after a quick button press? That you mean it wasn't completely crashed.
  10. JorgeB
    It's also logged in the syslog as a disk problem, though the UNC @ LBA 0 doesn't make much sense, I would run an extended test on the disk.
  11. JorgeB
    Memtest is only definitive if it finds errors, if you have multiple sticks try with just one, if the same try with a different one, that will basically rule out bad RAM.
  12. JorgeB
    Please post the complete diagnostics.
  13. JorgeB
    Parity will not be accessed for any array reads, it will be access during a parity check or any array writes.
  14. JorgeB
    Don't really think so, controller is using the stock AHCI driver, I guess it could be a controller/board problem.
  15. JorgeB
    Server rebooting on its own, vs. crashing/hanging, is almost always a hardware problem, but it can be caused by different things, like PSU, RAM, board, etc.
  16. JorgeB
    It can start happening by just using a different Unraid release, or the same release with different hardware, several users had that issue come up after a change.
  17. JorgeB
    Yep.
  18. JorgeB
    Those should be OK, looks like result of macOS, but there is a problem with the flash drive: Apr 21 14:36:50 Tower emhttpd: Unregistered Flash device error (ENOFLASH4). There were similar reports before that were fixed by plying with the USB settings in the board BIOS, IIRC last one was fixed after enabling USB power delivery in S5 State, or something similar.
  19. JorgeB
    I would replace/swap the cables, if not done yet, but for now don't see a reason to suspect a device problem.
  20. JorgeB
    If you have multiple RAM sticks try with just one, if the same try with a different one, that will basically rule out bad RAM.
  21. JorgeB
    Unfortunately there's nothing relevant logged, I do see some errors related to a CD/DVD drive, but those should not cause the server to crash, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, 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
    Btrfs is detecting new data corruption, since memtest is only definitive if it finds errors, and since you have multiple sticks, fix the corrupt files and reset the stats and and try with just one stick of RAM, if the same try with a different one, that will basically rule out bad RAM.
  23. JorgeB
    Looks OK for now, no more ATA errors.
  24. JorgeB
    I thought it was only one of them, in that case much less likely that a disk is the problem, but don't really have other ideas, there's nothing out of the ordinary logged in the syslog, very strange issue.
  25. JorgeB
    If you mean the disk remaining disabled that is expected, SMART looks OK, re-sync parity.