• Posts

  • Joined

  • Last visited

  • Days Won


Community Answers

  1. JorgeB's post in unRAID Becomes Unresponsive was marked as the answer   
    See here:
  2. JorgeB's post in disk issue was marked as the answer   
    Looks like an issue with the Intel SCU controller, unless all the disks using it share a power splitter or something, if you have another controller to connect those devices I would try it.
  3. JorgeB's post in Unmountable: Unsupported partition layout was marked as the answer   
    When you add a new disk to the array, it will be cleared, but not formatted, that would have to be done by you after the clearing was done.
    In doubt you can use the trial version of UFS explorer to scan the disk and confirm if there's any data there, I would bet there won't be, then, and since the disk is now disabled, to "fix" the array rebuild the disk and format, format button is next to array stop button.
  4. JorgeB's post in Unraid 6.12.8 - Permit exclusive shares was marked as the answer   
  5. JorgeB's post in After messing with network things I shouldn't have, I lost access to my server was marked as the answer   
    Delete/rename /boot/config/network.cfg to go back to default DHCP and reboot.
  6. JorgeB's post in Parity Disk Rebuild – Troubling Syslog Messages was marked as the answer   
    I think it was because of this:
    Apr 8 08:53:34 Tower7 root: Creating new GPT entries in memory. Apr 8 08:53:34 Tower7 root: Warning: The kernel is still using the old partition table. Apr 8 08:53:34 Tower7 root: The new table will be used at the next reboot or after you Apr 8 08:53:34 Tower7 root: run partprobe(8) or kpartx(8) Apr 8 08:53:34 Tower7 root: The operation has completed successfully. Apr 8 08:53:34 Tower7 emhttpd: re-reading (sdj) partition table Apr 8 08:53:34 Tower7 emhttpd: error: mkmbr, 2196: Device or resource busy (16): ioctl BLKRRPART: /dev/sdj  
    When the disk was initially partitioned it was busy, so possibly because of that it tried again after the resume, I'm just guessing since it's the first time I see this, the second partitioning attempt, not the disk busy issue, that has been happening for some time, hopefully it won't anymore with v6.13, since there were some changes done to try and prevent that.
    I would be extremely surprised if parity wasn't valid, just re-partitioning the disk should not cause any changes to the parity info, but you can start a check and let it run for a few minutes, if the no errors are found immediately it should all be fine.
  7. JorgeB's post in Unraid GUI becoming unresponsive, can't ping to ssh was marked as the answer   
    There's a macvlan related call trace, these will usually end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)), then reboot.
  8. JorgeB's post in Can't get parity drive up and running was marked as the answer   
    Apr 8 13:36:40 EmbyServer kernel: XFS (md3p1): Corruption detected. Unmount and run xfs_repair Apr 8 13:36:40 EmbyServer kernel: XFS (md3p1): log has mismatched uuid - can't recover  
    Check filesystem on that disk, run it without -n and if it asks for -L use it.
  9. JorgeB's post in zfs failed to create special file was marked as the answer   
    If you want to make some tests, your example works for be if the pool is first created with -O normalization=formC -O utf8only=on, e.g.:
    zpool create -f -o ashift=12 -O normalization=formC -O utf8only=on cache /dev/sdf1  
    Unfortunately this cannot be changed later, so the filesystem would need to be recreated manually, also not sure if it would cause other issue, but don't think so.
  10. JorgeB's post in Items moved to array but still on cache drive? was marked as the answer   
    See here first:
  11. JorgeB's post in Weird. GPU was there and now it's gone was marked as the answer   
    No AMD GPU is being detected by Linux, this is not a software problem, I see only a Nvidia GPU, try re-seating it or using a different PCIe slot.
  12. JorgeB's post in Server going haywire after cleaning was marked as the answer   
    Still constant errors, swap cables/slots with two other disks and see where the problem follows.
  13. JorgeB's post in Parity Swap did not work - (IO errors?) was marked as the answer   
    Constant errors with new parity disk, if they are still showing check/replace cables and post new diags.
  14. JorgeB's post in Migrated to new server hardware and unraid is broken in many ways. help! was marked as the answer   
    That looks more like a network issue, you can try using a new flash drive with a stock Unraid install to see if it /config related, if it's the same it's the network, if it works it's /config
  15. JorgeB's post in Dashboard dont load HTTP Error 500 after updated to 6.12.9 was marked as the answer   
    I would leave it for now, if it happens again try disabling it.
  16. JorgeB's post in New drive giving errors and disabled after a month of running perfectly was marked as the answer   
    SMART looks perfect, nothing suggesting it's a disk problem, so power/connection would be the main suspects, the log snippet you posted also doesn't point to a disk problem.
  17. JorgeB's post in Disk died overnight? was marked as the answer   
    ATA errors followed the disk, and it's still not giving a valid SMART report, so it should be replaced, emulated disk1 is now mounting so you just need to do a standard rebuild with a new disk.
  18. JorgeB's post in Failed to Add Device, too many devices on boot up - issues with shutting down was marked as the answer   
    That's an LSI BIOS error, nothing to do with Unraid, you can try disabling of even erasing the LSI BIOS, it's not needed.
  19. JorgeB's post in Wrong Pool State cache - invalid config was marked as the answer   
    Try this:
    with the array running type
    zfs detach cache 8514342029840584511 then stop the array
    unassign the cache pool device
    start array
    stop array
    set cache pool slots to 1
    re-assign the nvme device
    start array
    post new diags.
  20. JorgeB's post in 2 Previously failed drives showing as Unmountable: Unsupported or no file system but were used in parity synch was marked as the answer   
    Check filesystem on both disks, run it without -n, and if it asks for -L use it.
  21. JorgeB's post in Super-slow parity check - <350kbs was marked as the answer   
    Check/replace cables for disks 9 and 13
  22. JorgeB's post in Deactivation of unraid was marked as the answer
  23. JorgeB's post in Device is disabled, contents emulated...Afraid to touch anything was marked as the answer   
    Emulated disk is mounting, you have already replaced cables you can rebuild on top.

  24. JorgeB's post in Give license to another user was marked as the answer   
    I believe that if the license is not yet active it won't be a problem, your friend should be able to activate it using his email address.
  25. JorgeB's post in Out of memory errors was marked as the answer   
    This was using a lot of RAM:
    Killed process 3997 (Plex DLNA Serve)   
    Make sure you are not transcoding to RAM, or limit its usage.