Jump to content

JorgeB

Moderators
  • Posts

    67,416
  • Joined

  • Last visited

  • Days Won

    705

Everything posted by JorgeB

  1. shfs segfaulted, rebooting should bring all shares online, segfault was likely cause by the mover trying to move plex appdata, appdata should not be moved.
  2. Array should start normally, assuming no RAID controllers, VMs might need adjustment especially if passing-through any hardware.
  3. Like mentioned Marvell controllers are not recommended, but for this specif issue this sometimes help, or completly disable IOMMU (vt-d).
  4. Please post new diags grabbed while mover is running, enabling mover logging first might also help.
  5. You can only do this if you do a new config first.
  6. Scrub only checks the data, not the filesystem consistency, you can check that with btrfs check (but never use repair mode unless you know what you're doing)
  7. Loos more like a controller/connection issue, if you haven't yet replace both cables (power + SATA), if still the same and although Marvell controllers are not recommended try connecting the new disk there, to see if it's the same thing
  8. Some RAID controlellers can still pass individual devices, but when IT mode is available it's always best to use it with Unraid.
  9. If it's XFS it won't mount at the same time as the new drive due to a duplicate UUID, if that's the problem it can be changed with UD, diags would confirm.
  10. Problems with the SATA controller, this is rather common with Ryzem boards, there was a recent report that v6.9-beta fixed the issue, but might not be the same for all boards, BIOS update might also help.
  11. I don't understand, did the clean reboot fix it or not? And if not best to post on the plugin support thread.
  12. The parity disk, it still needs to be valid if in the future you add new larger disks.
  13. The problem is likely this: Apr 5 01:18:26 GANNAS emhttpd: unclean shutdown detected At first boot an unclean shutdown was detected, do a clean reboot and try again.
  14. SATA controller problem, this is fairly common with Ryzen boards, according to a recent report upgrading to v6.9-beta1 which includes a much more recent kernel fixed it.
  15. As for a recommended HBA, any LSI with a SAS2008/2308/3008/3408 chipset in IT mode, e.g., 9201-8i, 9211-8i, 9207-8i, 9300-8i, 9400-8i, etc and clones, like the Dell H200/H310 and IBM M1015, these latter ones need to be crossflashed. Controllers test thread is here.
  16. Do you have any old diagnostics saved or posted on the forum? Are you using single or dual parity?
  17. Yes, just make sure the controller is flashed to LSI IT mode.
  18. SMART tests confirm disk2 is failing and needs to be replaced, since there's no data you can just rebuild to a new disk, or do a new config with a new disk2 and re-sync parity. Syslog is cleared after a reboot, this might help if it happens again.
  19. No, but it doesn't try to load a pool member, which your device is.
  20. Does it have the latest firmware installed? Not many users with MegaRAID controllers, so not much experience with their errors.
  21. It just works, assuming using onboard ports or HBAs, some RAID controllers might detect the disks differently.
  22. No, just that the devices are new. If you are sure of the assignments, especially parity, you can enter the old passphrase twice and check "parity is already valid", then start array.
  23. There's a missing device: Apr 4 16:57:41 unraid kernel: BTRFS error (device sdi1): devid 2 uuid 18f07b0e-c359-4209-9561-aa7f3470d5d6 is missing Depending on which profile the pool was using, i.e., if it was redundant, it might mount in degraded mode, Unraid should try that if you set cache slots to >1. If that doesn't work there are some recovery options here.
×
×
  • Create New...