Jump to content

dlandon

Community Developer
  • Posts

    10,395
  • Joined

  • Last visited

  • Days Won

    20

Everything posted by dlandon

  1. This is what my testing showed. I'm not sure yet how I feel about how that works.
  2. What does the status show - click on the eye. Also download the preclear logs and post here.
  3. Try these commands and see if it stops the spin down noises: /usr/local/sbin/rc.unassigned spindown devX echo 'offline' > /sys/block/sdX/device/state echo '1' > /sys/block/sdX/device/delete If it makes noises with the spindown command, try the other commands without the spindown. When I tried this it spun down the USB device and then disconnected it from the server. The only way it could be reconnected was unplugging and then replugging. I never hear the sounds you are refering to, so I have no idea if this makes a difference.
  4. You have a huge amount of plugins including Nerd Pack that is loading a lot of packages. I recommend the following steps: Remove the Nerd Pack plugin and reboot. Try a preclear and see it it works properly. Reboot in safe mode and install the UD and UD Preclear packages. You'll need to install CA manually. Instructions are here: Try a preclear and see if it works.
  5. The spin down command is done by Unraid and is done my passing in the devX designation given to the UD disk. The devX designation can be used directly in the rc.unassigned script, or by using the alias. When using the alias, UD does a look up of the devX designation for Unraid and then issues the spin down command. The devX cannot be hard coded because it changes every time a disk is removed/installed. Complex or risky is not the issue. The issue is what makes sense for all situations. I can look at doing a spin down without needing an alias if that is your concern.
  6. No. UD disks follow the generic spin down timer. Over what tie frame were the writes? Possible if the VM does a lot of reads? Toggle to read/write rates and see if the VM is doing a lot of disk reading.
  7. Looks like a disk problem: Sep 3 11:06:38 Elmo kernel: ata6.00: exception Emask 0x10 SAct 0x1000000 SErr 0x280100 action 0x6 frozen Sep 3 11:06:38 Elmo kernel: ata6.00: irq_stat 0x08000000, interface fatal error Sep 3 11:06:38 Elmo kernel: ata6: SError: { UnrecovData 10B8B BadCRC } Sep 3 11:06:38 Elmo kernel: ata6.00: failed command: READ FPDMA QUEUED Sep 3 11:06:38 Elmo kernel: ata6.00: cmd 60/f8:c0:48:02:00/01:00:00:00:00/40 tag 24 ncq dma 258048 in Sep 3 11:06:38 Elmo kernel: res 50/00:f8:48:02:00/00:01:00:00:00/40 Emask 0x10 (ATA bus error) Sep 3 11:06:38 Elmo kernel: ata6.00: status: { DRDY } Sep 3 11:06:38 Elmo kernel: ata6: hard resetting link Sep 3 11:06:38 Elmo kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Sep 3 11:06:38 Elmo kernel: ata6.00: ATA Identify Device Log not supported ### [PREVIOUS LINE REPEATED 1 TIMES] ### Sep 3 11:06:38 Elmo kernel: ata6.00: configured for UDMA/133
  8. While this might not be your issue, remove the incompatible docker folder plugin and install the replacement that is compatible from CA.
  9. Unraid 6.11 will spin down SSDs to put them in a lower power state. If you don't want Unraid to spin them down, set your disks to never spin down, then set individual spin down times for the ones you want to spin down.
  10. The diskinfo_log you posted is from the old preclear disk plugin and doesn't apply to the UD Preclear. Post your diagnostics file.
  11. UD Preclear writes a disk signature and partition so that the disk is ready for Unraid. To format it for UD, you will need to clear the disk as you have shown above. You can then format the disk with UD.
  12. Unmounting the drive cleanly should be a safe way of removing it. The spindown is not a power off command. I've not seen any head clunking tbis with any of my drives. Have you tried the commands in the link you supplied to see if there is a difference in the head clunking? I suspect that the drive has an issue with parking the head cleanly.
  13. It’s a known issue and is being worked on.
  14. This has already been reported to LT and is being worked on.
  15. What does the status show Click on the eye icon. Download the preclear logs.
  16. Be sure the old preclear disk plugin is removed and reboot. Looks like some leftovers from the preclear disk remain.
  17. I don't think you'll get that. Ceck this link: http://www.infotinks.com/correlating-versions-samba-smbcifs/ Scroll down a bit abnd you'll see samba supports 2.02 and above.
  18. SMBv1 is controlled with the "Enable NetBIOS" setting. If set to "Yes" SMBv1 is enabled. If it is set to "No" it is disabled.
  19. Correct, it is not being supported or maintained. Understand that the 'fix' is not just to trick it to work with 6.11, all of the 6.10 packages need to be confirmed to be compatible with 6.11, or updated for 6.11. That's why the author has the pagkages on the flash drive organized by Unraid version. Part of the update to get it working on a new version of Unraid would be to confirm that all the packages put in the 6.11 folder would be compatible with 6.11. Don't fork the Nerd Pack Plugin unless you intend to invest the time to do this. If the plugin is distributed with a package that is not compatible with 6.11, you risk the potential of creating support issues for yourself and LT.
  20. Unassigned Devices Preclear uses tmux, not Unassigned Devices Plus.
  21. If it crashed when doing a parity check, you may have a power supply problem. Run a memory test. Try running it in safe mode and see if i crashes.
  22. Powertop has been removed because of reports of sata controller issues. The power savings are very minimal and it's not worth causing user's problems.
×
×
  • Create New...