Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,647

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    No, it just means you're running it with the no modify flash (-n), run it again without it.
  2. JorgeB
    You could use the user scripts plugin. That or copy it on top of the VM vdisk replacing it.
  3. JorgeB
    Reboot and try again, or do it on the console.
  4. JorgeB
    There's no GUI support for now, but you can do it manually or with a script, more info here: https://forums.unraid.net/topic/51703-vm-faq/?do=findComment&comment=523800
  5. JorgeB
    No, it would be slower since parity would need to be concurrently update for all. That's about the max speed you can get with gigabit. For large writes your array disks with turbo write enable should be able to keep up with gigabit, so better just transferring directly to the array.
  6. JorgeB
    First try to repair the filesystem on the emulated disk6, if it's successfully repaired and all data looks there you can rebuild on top, if not you can use a spare or do a new config instead.
  7. JorgeB
    Unraid already does something similar when you for example create a new pool, might be able to use the same thing: May 24 10:37:40 Tower11 emhttpd: shcmd (5636): mkdir -p /mnt/wd May 24 10:37:42 Tower11 emhttpd: shcmd (5637): blkid -t TYPE='xfs' /dev/sdw1 &> /dev/null May 24 10:37:42 Tower11 emhttpd: shcmd (5637): exit status: 2 May 24 10:37:42 Tower11 emhttpd: shcmd (5638): blkid -t TYPE='btrfs' /dev/sdw1 &> /dev/null May 24 10:37:42 Tower11 emhttpd: shcmd (5639): mount -t btrfs -o noatime,space_cache=v2 /dev/sdw1 /mnt/wd
  8. JorgeB
    That's a known issue when running full reiserfs filesystems, convert them all to xfs and it should help.
  9. JorgeB
    May 23 04:03:31 NNC kernel: BTRFS error (device sde1): block=112534290432 write time tree block corruption detected May 23 04:03:31 NNC kernel: BTRFS: error (device sde1) in btrfs_commit_transaction:2377: errno=-5 IO failure (Error while writing out transaction) May 23 04:03:31 NNC kernel: BTRFS info (device sde1): forced readonly Cache filesystem is corrupt, best bet is to backup and re-format cache.
  10. JorgeB
    The same is happening to other users with the same controller. Then you should improve the cooling, or they will also overheat when you need to run a scrub or some other high i/o operation.
  11. JorgeB
    I've not aware of spin down issues because of being a pool, I have several pools myself and they all spin down, are you using a different controller for the pool devices? You can also post the diags.
  12. JorgeB
    Iperf just tests the network bandwidth, no drives are involved, so still likely a network related issue.
  13. JorgeB
    Does the same happen if you boot in safe mode?
  14. JorgeB
    Just to expand if you were worried about the raw read and seek error rates those are normal with Seagate drives: https://forums.unraid.net/topic/86337-are-my-smart-reports-bad/?do=findComment&comment=800888
  15. JorgeB
    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/ P.S: also need to fix the filesystem on disk1.
  16. JorgeB
    File is corrupt, you need to delete or restore from backups, also good idea to run memtest.
  17. JorgeB
    This can indeed complicate thing, if the luks hears are damaged the filesystem can never mount, can't really help with encryption since I don't use it but there are some threads here about rebuilding the encryption headers, look for those.
  18. JorgeB
    If you mean a single transfer using both NICs it would need SMB multichannel working, and AFAIK no one has been able to make it work with multiple NICs and Unraid.
  19. JorgeB
    Docker/VMs are known to write constantly, though much better with v6.9.x, also helped if the SSD was reformatted with the new partition layout. This is basically meaningless, you can check SMART for the total TBW, then check 24H later to see if it is something to worry about.
  20. JorgeB
    Enable this then post that log after a crash.
  21. JorgeB
    Update to latest stable and if issues persist please post the diagnostics: Tools -> Diagnostics
  22. JorgeB
    It could, though don't remember spinning issues with WDs, but try disabling spin down to see if it changes anything.
  23. JorgeB
    There's nothing of concern on that screenshot.
  24. JorgeB
    Unlikely to be a connection problem since it's happening to only the 2 Intel SSDs of the same model, but not impossible, still suspect they don't like that controller.
  25. JorgeB
    Du isn't accurate with btrfs, for single device cache the GUI is always accurate, and it checks out with btrfs stats: Used: 78.92GiB Free (estimated): 106.69GiB (min: 106.69GiB) Free (statfs, df): 106.69GiB These are is GiB, GUI shows GB, so they are the same and something is using that space, if you're not sure what is you can move some files at time to the array to find out.
×
×
  • Create New...