Jump to content

JorgeB

Moderators
  • Posts

    67,514
  • Joined

  • Last visited

  • Days Won

    707

Everything posted by JorgeB

  1. Correct, respect max speeds mentioned here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/?tab=comments#comment-819173
  2. Issues in multiple disks at the same time: Sep 11 02:54:30 Tower kernel: sd 9:0:7:0: Power-on or device reset occurred Sep 11 02:54:32 Tower kernel: sd 9:0:5:0: Power-on or device reset occurred Sep 11 02:54:35 Tower kernel: sd 9:0:6:0: Power-on or device reset occurred This suggest a power/cable issue, also good idea to update the LSI firmware since it's on a very old release: LSISAS2008: FWVersion(07.15.08.00) Current one is 20.00.07.00.
  3. Diags are after rebooting, please post new ones after the error.
  4. Download the beta zip and extract all the bz* files to the flash drive overwriting existing ones.
  5. It's likely checking for trim support, WD SMR drives report they do, if that's true plugin could check if the drive is non rotational instead.
  6. Spin down command Unraid uses doesn't work on SAS devices.
  7. IIRC that means the NVDATA is not from LSI, older releases could still proceed and correct it, maybe p7? Check here: https://wiki.unraid.net/Crossflashing_Controllers
  8. Yeah, I like AMD and just recently bough my first AMD CPU since the Athlon 64X2, but wish AMD did the same as Intel for RAM speeds, i.e. 10th gen Core CPUs support up to 2933MHz, doesn't matter if you have one or all DIMMs slots used, Ryzen 3rd gen supports "up to" 3200Mhz, most users then don't know that max speed is based on number of DIMMs/ranks used.
  9. It's possible, or the power supply isn't strong enough on the 12v line, could also be the board but I would consider that less likely.
  10. Disk looks fine, there were issues with multiple disks simultaneously, Intel SATA controllers are usually rock solid, so most likely either the board/controller is failing or you have a power problem.
  11. Unraid doesn't spin down SAS devices, not yet anyway, maybe in the future.
  12. Like mentioned it's normal on the SMART page, no idea where the plugin get its info from, best to ask on the appropriate support thread.
  13. Do you mean in the main page or SMART test page? It's normal on the SMART test page, on the main page I believe it should show correctly, but note that by default stats are only update every 30 minutes, that can be changed on disk settings.
  14. GUI SMART tests don't work on SAS drives, you can still run them manually. The lack of temperature issue is a smartctl problem/bug, it should be fixed on an upcoming release.
  15. Probably a controller with custom SMART data, but we can't say for sure without the diagnostics.
  16. Minimum free space for the Media share is set to 9TB.
  17. Then most likely previous sync errors were the result of an unclean shutdown.
  18. It didn't work because that is a RAID controller, even in HBA mode, it's not a true HBA, if you still want to use it you'd need to do a new config and re-assign all disks, note that if in the future you replace the controller with a different one you'll need to do the same, it would be best to use a true HBA, LSI preferred.
  19. You should contact support directly, or wait for @SpencerJto see this and help you.
  20. You can do it before or after, but to remove any current array drive you need to do a new config to reset the assignments, it won't delete any data, just make sure that after that you don't assign any data disk to the parity slot.
  21. Sep 9 19:57:24 PirateBay rc.docker: binhex-radarr: Error response from daemon: error while creating mount source path '/mnt/user/appdata/data/Media': mkdir /mnt/user/appdata/data/Media: no space left on device Problem is because Appdata share floor is set to 4TB. It's also set to split directories, make sure that's what you want, since appdata should usually only exist on one device, yours exists on cache, disk1 and disk2, good idea to consolidate that.
  22. SAS2LP used to wok great with v5, but since v6 many users start having problems with it (same for SASLP which uses the same driver), many times issues begin after an Unraid upgrade out of the blue, doesn't mean it's the problem, since it doesn't usually makes the server crash, but definitely not recommended. The last diags you posted are just after rebooting, so not much to see, if it keeps crashing, or you can make it crash, use this then post that syslog.
×
×
  • Create New...