Jump to content

JorgeB

Moderators
  • Posts

    67,831
  • Joined

  • Last visited

  • Days Won

    708

Everything posted by JorgeB

  1. Initially it's logged as a disk problem, but then it dropped offline together with disk4 and the cache device: Aug 31 20:52:03 AKserver kernel: ata8.00: disabled ... Aug 31 20:52:04 AKserver kernel: ata10.00: disabled ... Aug 31 20:52:04 AKserver kernel: ata9.00: disabled This suggests a power/connection problem, check/replace cables and post new diags after array start.
  2. It should be the same, disable the scheduled check and run a manual one next month, note that some of these type of errors, when they are controller related, have been known to only happen after a reboot, i.e., if you run two consecutive checks without rebooting there won't be any errors, if you reboot there will be.
  3. Unisntall the dynamix.s3.sleep plugin
  4. That's very weird, don't remember any similar issue reported before.
  5. If you shrink the array like that you will lose any data in the disabled disk, is that OK?
  6. That's fine in case a device fails/drops but raid1 won't help with this type of issue.
  7. If there's nothing logged you can increase Samba log level by going to Settings -> SMB -> SMB Extras and adding: log level = 3 logging = syslog Then check/post the syslog after it happens, note that Samba will get very chatty so it can fill it up after a few hours.
  8. Don't know those cables but disks 6 and 12 are connected to the onboard SATA, so not that kind of cables.
  9. I would try recreating the flash drive, copy the bare minimum from the old config, like disk assignments and pools, don't copy anything related to identification or passwords.
  10. At what position is the check? Disk 4 is showing one or more slow zones in the beginning.
  11. You are having issues with multiple disks, disk10 got disabled and disks 6 and 12 are generating a lot of ATA errors, check/replace cables and post new diags after array start.
  12. If I'm not mistaken the minimum SMB2 version supported by Samba is 2.02, you might need to use SMB1
  13. The license won't change anything regarding disk capacity/utilization, please post the diagnostics, there might be something visible there.
  14. Not seeing anything in the log indicating that the disk is mounted read-only, but not I'm familiar with hfs, since this is not an Unraid stock functionality please use the existing UD plugin support thread:
  15. Marvell controllers are not recommended, but the diags are just after rebooting, not seeing any disk/controller related issues so far.
  16. Looks more like a power/connection problem but since the disk dropped offline there's no SMART report, power down, check/replace cables, power back up and post new diags after array start.
  17. No need for a new config, just unassign both devices and start the array for Unraid to "forget" that pool, best to wipe the devices before assigning them to the other pools though, if they are SSDs you can do that with blkdiscard -f /dev/sdX or /dev/nvmeXn1
  18. Then it won't be that, does df report the same usage?
  19. Make sure the LSI is using the latest firmware, if needed you can use Unraid to update it.
  20. Cannot replicate this with v6.10.3, did you using the IP address to see if there's any difference?
×
×
  • Create New...