Jump to content

JorgeB

Moderators
  • Posts

    67,831
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. If disk2 is mounting with UD you don't need XFS explorer, whatever that is.
  2. See if it advances, what's the current status? Is the disk still doing the noise?
  3. If I understand correcty you don't even see the Unraid boot menu? If yes press the board's boot menu key, IIRC it's F8 with MSI, and post a screenshot of the boot options.
  4. Time should not change with the server on, even with a bad CMOS battery, board might be going bad.
  5. Nothing obvious, let @Squidtake a look, might be a false positive.
  6. See if you can recover data form disk9 with ddrescue, then you'd do a new config with all the disks (including old disk2) and the clone from disk9, if successful.
  7. Once a disk gets disabled it needs to be rebuilt, just changing slots won't change anything, diags don't capture the disk getting disabled, so we cannot see what happened, but the disk looks healthy, if the the emulated disk is mounting and contents look correct you can rebuild on top, do it using a different slot to rule out that if it happens again to the same disk. https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself
  8. For disk2 it's probably best just to use the existing disk without rebuilding, but first check its state, unassign disk2 from the array, start the array, stop the array, disk2 will now be in the unassigned devices section, see if it mounts with the UD and contents look correct, UD also has a check filesystem option if needed.
  9. check filesystem was for disk2, or is disk9 not mounting again? But since we've now confirmed that disk9 is failing fixing the emulated disk might not be possible.
  10. P.S. for such a large array would definitely recommend dual parity, unless you have good backups.
  11. Disk9 is failing: === START OF READ SMART DATA SECTION === SMART Health Status: FAILURE PREDICTION THRESHOLD EXCEEDED That leaves you in a bad spot, is the currently assigned disk2 a spare or the old disk2? It looks healthy, if it's the old one you could re-enable it, would likely only lose any data written to it after it got disabled, if there was any. A for disk9 you can try ddrescue to recover as much as possible.
  12. It's not logged as a disk problem, suggest you replace both power and SATA cables to rule that out (or slot) and try again.
  13. v6.9.2 is over one year old now but if you want to go back more: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.8.3-x86_64.zip
  14. Stop the array, unassign both cache devices, start the array, stop the array, re-assign both cache devices, start the array, everything should be correct after that.
  15. The LSI HBA doesn't support trim, use the Intel SATA ports for the SSD instead, but change the mode to AHCI in the BIOS, it's set to IDE.
  16. Smartctl segfaulting is strange, could be a hardware issue, do you remember if the issues started after an Unraid release upgrade? If there's a known working release downgrade back to it, boot it safe mode, if the issues continue it's likely hardware.
  17. Why? Just needed to format the disk. No, a few sync errors after an unclean shutdown are normal, even expected, last check detected 0 errors so all is good now.
  18. See here: https://wiki.unraid.net/Manual/Security#Securing_webGui_connections_.28SSL.29 If it does not help edit config/ident.cfg on the flash drive and change USE_SSL from "auto/yes" to "no", then reboot.
×
×
  • Create New...