Jump to content

JorgeB

Moderators
  • Posts

    67,594
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. If it fails grab diags in v6.9 before rebooting.
  2. Spin down is no longer handled by mdcmd but by emhttpd, not sure if there's a new command we can now use for spin up, I'm also interested in that.
  3. Unmontable/unassigned cache won't prevent array start, but difficult to say more without diags.
  4. Rebuilding won't fix the filesystem corruption. No, but you cancel the rebuild, run the file system check and then start over.
  5. Oops, wiki changed, basically, stop array, unassign that disk, start array, stop array, re-assign the disk, start array to begin rebuilding.
  6. https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive Make sure the emulated disk is mounting and contents look correct before rebuilding on top.
  7. Most likely all files are fine, but unless you have pre-existing checksums or are using btrfs no way to know for sure, you can however rebuild that disk to a spare one then compare the data with the old one.
  8. Yep, disks were detected about 10 minutes after boot, 🤷
  9. As expected disk4 is now mounting, if contents look correct you can rebuild on top of the old disk, also try to run xfs_repair again on disk3.
  10. Disk4 should mount, please post new diags after array start, for disk3 on the other hand you'll likely need to use the old disk, even if it's failing.
  11. https://forums.unraid.net/topic/43651-plug-in-unbalance/ After that's done post again for help with the new config.
  12. If the pool is using raid1 you can remove one device at a time.
  13. Disk3 is showing a pending sector, you should run an extended SMART test, disk4 looks OK. Also need to run a filesystem check on the emulated disks 3 and 4.
  14. Newer kernel can detect previously undetected corruption, you should backup your pool, re-format, then restore the data before or after upgrading back to v6.9
  15. Looks like a problem with the Intel SCU controller, please power/cycle the server and post new diags, after array start.
  16. You need to manually move the data from the 12Tb drive to others, you can also use Unbalance plugin, after it's done you need to do a new config.
  17. Yes, array devices can't be trimmed though, so write performance might degrade with time if heavily used.
  18. Don't see any errors, HBA is initializing correctly, do the disks show up if you go back to v6.8?
  19. Diags shows balance still running, did it finish now?
  20. Disk looks fine, looks more like a connection problem, try a different slot, but you'll need to rebuild it.
  21. UD doesn't allow degraded mounts, there are some recovery options here.
Ă—
Ă—
  • Create New...