Jump to content

JorgeB

Moderators
  • Posts

    67,530
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. You can use the mover to do that, instructions are on beta29 release notes.
  2. Could be a failing temp sensor, but that's not common, if you have one you can measure the temp with an infrared thermometer and compare to the reported temp.
  3. You should create a bug report.
  4. Looks like a connection/power problem, issues were affecting disk1 and 4 at the same time, do they share anything like a power cable/splitter? As for the emulated disk you can try to repair the filesystem, if all OK you can rebuild on top but by the looks of the xfs_repair output, probably best to just re-sync parity (after confirming the old disk is mounting correctly with UD for example).
  5. Very unlikely that the C-state setting has any impact on sync errors, though it can help if the server crashed when idle.
  6. Likely a router issue, or it's not updated yet.
  7. That's the same thing, when you run a filesystem check on the GUI it runs xfs_repair (for xfs formatted disks).
  8. Run without -n and if it asks for it use -L
  9. It's OK to do it now, it's not a heavy operation.
  10. Never tried but almost certain it won't. Yes, Unraid requires each device to have a unique identification, doesn't matter where you're going to assign it.
  11. Use a different slot if available. https://wiki.unraid.net/Troubleshooting#Re-enable_the_drive
  12. Not that I known of, only by using different models, and some times even different models can have the same identification string, since one Chinese factory can make them for various brands.
  13. Diags are after rebooting so we can't see what happened, disk look fine, replace/swap cables to rule them out and rebuild. Also, the docker image is corrupt and needs to be recreated, and like trurl mentioned make sure you enable system notifications.
  14. For the csrf errors see here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/?tab=comments#comment-545988
  15. Yes, I forgot about that, remembered right after posting, just tested and it's fixed.
  16. I tried to earlier but there's no option to erase an array device now, so I assumed you removed that functionality for now.
  17. If there is one it will be a top level folder on that disk, also a user share.
  18. Check filesystem on disk1: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui
  19. There are some recovery options here, if it doesn't work you'll need to re-format and restore from backups.
×
×
  • Create New...