Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,696

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    You need to format the array devices first, next to array start/stop button.
  2. JorgeB
    Syslog starts over after every reboot, so not much to see, if it keeps happening enable the syslog server and post that log after a crash.
  3. JorgeB
    You should be able to bind the device (hide it from Unraid) with the USB manager plugin, device you need to bind is this one:
  4. JorgeB
    Enable syslog server and post that log after a crash.
  5. JorgeB
    XFS partition *should* be easier to restore with testdisk, another option if parity is still valid, would be to rebuild each disk one at a time, Unraid would recreate the partitions, you can test by unassigning one of the data disks, start the array, the emulated disk should mount correctly and all data be there, if yes you can rebuild on top, then repeat for the other one.
  6. JorgeB
    Yes, I believe the board could at most drop the device, not generate a sector read error.
  7. JorgeB
    You can try isolating the device, like if it was being used by a VM, this way Unraid won't load a driver.
  8. JorgeB
    Oct 7 06:49:37 Tower kernel: blk_update_request: critical medium error, dev nvme0n1, sector 5125600 op 0x0:(READ) flags 0x1000 phys_seg 1 prio class 0 Oct 7 06:49:37 Tower kernel: BTRFS: error (device nvme0n1p1) in btrfs_recover_log_trees:6250: errno=-5 IO failure (Couldn't read tree log root.) Oct 7 06:49:37 Tower kernel: BTRFS: error (device nvme0n1p1) in btrfs_replay_log:2279: errno=-5 IO failure (Failed to recover log tree) 1st one is a hardware error, so yes, it looks like a device problem.
  9. JorgeB
    Please use the existing plugin support thread:
  10. JorgeB
    That doesn't sound right to me, I don't have a fan on mine, just a case fan providing some airflow around it.
  11. JorgeB
    This error is fatal, it means some writes were lost, usually data can be recovered with btrfs restore, 2nd option here.
  12. JorgeB
    Unraid only creates one partition, in this case it would be the first one, and it's a primary partition.
  13. JorgeB
    Please post the diagnostics (after array start)
  14. JorgeB
    Never measured but it can run a little hotter since the ROC is clocked higher and it uses a little more power.
  15. JorgeB
    It's a bug: Settings -> Global share settings -> Enable user shares.
  16. JorgeB
    It's a known issue that affects some, it might help if you disable NFS, if you don't need it or can use SMB instead.
  17. JorgeB
    Yes.
  18. JorgeB
    Did you do this?
  19. JorgeB
    Start here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173
  20. JorgeB
    You need to rebuild the disk or do a new config and re-sysnc/check parity, either way will take about the same amount of time.
  21. JorgeB
    If backplane and PSU are the only things that changed that's where you should begin, try with a different PSU first, if issues persist it's likely the backplane.
  22. JorgeB
    If you're on v6.9.x: Generate key: ssh-keygen NOTE: when generating the key use a blank password or it will ask for it anytime you use that key. Add the key to another server's authorized list: cat ~/.ssh/id_rsa.pub | ssh root@remote_host "mkdir -p ~/.ssh && cat >> ~/.ssh/authorized_keys"
  23. JorgeB
    Oct 5 09:17:04 moose-prime kernel: Sys_MemInfo+0x20/0x9b [corefreqk] Try uninstalling the corefreq plugin.
  24. JorgeB
    It can be transferred do another one: https://unraid.net/blog/top-support-and-forum-questions-answered
  25. JorgeB
    It's possible. You can't copy data in maintenance mode, start in normal mode and use your favorite tool do copy, you can use CLIi tools like cp or rsync, or tools with a GUI like midnight commander or the krusader docker.
×
×
  • Create New...