Jump to content

JorgeB

Moderators
  • Posts

    67,858
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. If there's no other way to access the server you'll need to force it.
  2. Only if you saved them before rebooting, after rebooting the syslog is lost, you can see if you can get parity to come back online, check/replace/swap cables or you can do a new config to re-enable disk6 and hope the disk is really OK.
  3. Enable the syslog server and post that together with the complete diagnostics after it happens again.
  4. Default mode is raid1, mirror, it can be changed. Reconnect the other device and post new diags before array start.
  5. I've seen various diags with the same problem, not sure why it's only some though.
  6. In the diags, more than one place, loads.txt it's the easiest to check.
  7. You cannot replace disk6 without parity, though the disk appears to be OK, do you have the pre-reboot diags?
  8. Try booting in safe mode, if the same blacklist the i915 GPU.
  9. Yep, looks like it's Plex scanning for media: nobody 26599 36.3 0.0 117064 59060 ? DNl 08:38 0:17 \_ /usr/lib/plexmediaserver/Plex Media Scanner -- It's now reading disk10 @ 120MB/s
  10. Auto in this case means yes, it's enabled for everything.
  11. AFAIK there never was a driver for the Matrox GPUs, maybe it would help if there was one now?
  12. Something was reading from disk10 at 100MB/s+ when the diags were saved, that will slow down the parity check.
  13. It might be worth doing it, not sure if they work with NVMe devices, never tried, but it should at least with v6.11+, I remember there were some changes about NVMe devices.
  14. With nocow it will disable cow for any data written to that share. Like any other file, any blocks are written to both devices. xfs or btrs nocow might perform a little better, but xfs is single device only and btrfs nocow as mentioned should be avoided, note that a mirror is for redundancy, you still need backups of anything important.
  15. File system corruption can happen especially after an unclean shutdown or when a disk gets disabled, it's kind of an unclean shutdown for the filesystem, but usually a filesystem check fixes it.
  16. It is logged as disk problem initially, but SMART looks OK, swap power cable/slot with another disk so see if the clicking stops, if not it's likely a disk problem.
  17. Best to ask in the plugin support thread, but you should just need to indicate the remote path, e.g., /mnt/remotes/name_of_share
  18. Yes, as long as you are using a redundant pool, and the default is redundant (raid1). Nocow should be set to auto, if it's set to no, there won't be checksums and if a device drops and then reconnects it might result in data corruption, since btrfs has no way of knowing which device has the correct data, more info here.
  19. A rebuilt disk will show exactly hat was on the emulated one, please post the diagnostics.
  20. Not with that firmware, some older releases did, though only for SSDs with determinist read zeros after trim support.
  21. Please update to latest Unraid since it includes much newer xfs progrs and try running xfs_repair again on disk2.
×
×
  • Create New...