Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,603

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    It is, only the 32GB model, 16GB and smaller were discontinued.
  2. JorgeB
    Please post diagnostics.
  3. JorgeB
    Also mote that I misread the previous diags when I said Unraid was forcing the shutdown before the set timer, it wasn't, hence why changing the timeout from 100 to 150 solved the issue, it just needed more time.
  4. JorgeB
    Correct, you can balance to single mode to fully use both devices (without redundancy).
  5. JorgeB
    Not for now, Unraid assumes a pool is redundant, it doesn't check for the actual profile being used.
  6. JorgeB
    Problem starts with corruption being detect on the cache filesystem, docker issues after are a consequence of that, best to backup and re-format cache. Note if you need me to follow up please ping me again as I don't check this forum.
  7. JorgeB
    Yep.
  8. JorgeB
    Unlikely, you need to post the generated diags or we can't see the reason.
  9. JorgeB
    Delete and recreate the docker image: https://forums.unraid.net/topic/57181-docker-faq/?do=findComment&comment=564309
  10. JorgeB
    By default Unraid converts the pool to raid1 when you add a device, and raid1 will only use the capacity from the smallest device, if you want to expand the pool see here.
  11. JorgeB
    I only had one device corrupting data, and it was a Sandisk SSD after an error like that, if the scrub didn't find any errors it means the corrupt files were since deleted or replaced, but since you're using ECC RAM I suspect the SSD was the reason for the data corruption, so I would recommend replacing it.
  12. JorgeB
    Cache is showing errors, see below for more info. https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=700582
  13. JorgeB
    This was a hardware problem with the cache device, it dropped offline, so SMART report is empty, before that it was showing some data corruption, that could indicate a device problem, post a new SMART report and run a scrub.
  14. JorgeB
    Used 1st or 2nd option?
  15. JorgeB
    This means you need to run reiserfsck with the --rebuild-tree option, also good idea to convert all reiserfs disks to xfs, since reiserfs is not recommended for years now.
  16. JorgeB
    Also note that just rebooting should bring the data back, but you still need to fix the underlying issue or it will likely happen again. Errors on parity drive are logged like a disk problem, though SMART looks OK and it's using a Marvell controller, still should run an extended test, but the main problem was the onboard SATA controller, which is unfortunately quite common with some Ryzen boards, looks for a BIOS update, if that doesn't help and other than using a different board best bet is to use an add-on controller (non Marvell).
  17. JorgeB
    You can downgrade back to the release it was working with, this will also confirm it's not a hardware issue.
  18. JorgeB
    Problem with parity looks like a connection issue, replace both cables. Diags are spammed with the ATA errors about parity, if replacing the cables fixes that post new diags after to see about the read only drive.
  19. JorgeB
    Apr 16 04:50:08 Tower kernel: usb 4-3: USB disconnect, device number 2 USB problem, USB connections are notoriously unreliable, hence why we don't recommend using them for array or pool devices, you can try again in a different USB controller, or just remove the enclosure.
  20. JorgeB
    SMART looks fine, diagnostics before rebooting might give more clues.
  21. JorgeB
    The missing disks are connected to an LSI 9300-8i or similar, it should work fine with v6.9.x, I have some myself, to see the issue you'd need to upgrade again and post new diags from v6.9.
  22. JorgeB
    Without the KVM guest hibernate won't work, you should also test before rebooting, i.e., stop the array and time how long it takes for the VMs to shutdown and the array to stop.
  23. JorgeB
    You should stick with the max officially supported speed since some Ryzen servers are known to corrupt data when above max.
  24. JorgeB
    Apr 16 12:44:44 Tower root: Waiting on VMs to shutdown............................................................ Apr 16 12:44:44 Tower root: The following VMs are still running, forcing shutdown: webserver,Windows Server 2016
  25. JorgeB
    It's running at 3600 MT/s when the max officially supported speed for your config is 2667 MT/s.
×
×
  • Create New...