Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,871

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    It's a GUI issue, I can see in the diags that it's writing to parity, and nothing out of the ordinary logged so far.
  2. JorgeB
    Try booting in safe mode to rule out a plugin issue.
  3. JorgeB
    Unfortunately that's not the problem since that's an easy fix, quirk is needed when you only see one of the two devices, you are not seeing both, looks like the same issue as another user with a coupe of Crucial devices where they stopped reporting the brand/model, please post output from both v6.9.2 and v6.11.1 of: devadm info -q property -n /dev/nvme0n1 Output from one of the devices is enough, since they will be the same, expect the serial.
  4. JorgeB
    Nothing relevant logged, which is not that surprising since a reboot suggests a hardware or power problem.
  5. JorgeB
    In this case it won't make any difference, since you are using /mnt/cache it will always behave as cache=only
  6. JorgeB
    It's is compatible, it's not recommended to use them in the array, but you still can, just won't have trim support, no issues when using them in a pool. Depends on what you compare, if you mean the array that should be obvious since data is not stripped, Unraid pools can be as fast as Freenas, I get 1GB/s transferring to some of my pools. That suggests a hardware problem, obviously most users don't have that issue or the forum would be littered with complains.
  7. JorgeB
    It's a known issue it the Crucial MX500, recommend not monitoring that attribute.
  8. JorgeB
    Starting sector is correct but the partition is not using the full disk capacity, and Unraid requires that, it should be possible to resize or just create a new partition on top of that one with the same starting sector but using the full disk and if that is the only issue Unraid should then accept it, but it's not something I can try so cannot say for sure if it will work or not.
  9. JorgeB
    Easiest way is to use a new disk, let Unraid format it, then mount the old disk with UD and transfer the data, other option is to add parity and then rebuild one disk at a time, Unraid will recreate the partitions.
  10. JorgeB
    No, unless you assign them as parity, it won't touch data drives, though because they were on a raid controller there's a chance it won't like the partition layout, but it still won't delete anything.
  11. JorgeB
    Go to Tools and do a New Config.
  12. JorgeB
    That should be just a GUI issue, you can also post the diags to see if it's going OK.
  13. JorgeB
    According to the screenshot copy didn't complete, also note that you cannot change anything once it's done (or reboot the server), just press start to begin the rebuild.
  14. JorgeB
    When Unraid fails to do a clean shutdown it saves the diags in the flash drive /logs folder, post those, there might be some clues there.
  15. JorgeB
    Looks like this issue is limited to this model disk: TOSHIBA_MG05ACA800E Might be a firmware issue, since you only have a couple probably best to just leave them spun up for now.
  16. JorgeB
    See here for the power supply idle contol setting, if still relevant, but there have been a couple of Ryzen 7000 users reporting stability issues, so possibly the result of being a very new platform.
  17. JorgeB
    Oct 19 07:52:23 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan] Oct 19 07:52:23 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address and will end up crashing the server, upgrading to v6.10 or later and switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).
  18. JorgeB
    Because of the reboot there's not much to see, enable the syslog server and try again, but a reboot is usually a hardware issue (or it lost power).
  19. JorgeB
    Try switching to ipvlan (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).
  20. JorgeB
    I asked for the diags in your general support thread, please post them there.
  21. JorgeB
    Disks look OK, parity issue started right after spin up, but it spun up many times before, so maybe a one time thing, though if it happens again you might want to try disabling spin down, with SAS disks especially it's not always 100% supported.
  22. JorgeB
    Share floor is set to 4TB, since no disk has more than 4TB free you cannot write to it, just adjust that.
  23. JorgeB
    Installing dockers is fine, copying files I would avoid if possible.
  24. JorgeB
    Understood, but no idea what could cause that, I've never seen that issue and don't remember anyone else complaining of something similar. When you are doing that is everything accessing the same storage? (array or pool)
  25. JorgeB
    Not that one, the controller test.
×
×
  • Create New...