Difference between revisions of "UnRAID tips"

From Chuckipedia
Jump to: navigation, search
 
(One intermediate revision by the same user not shown)
Line 9: Line 9:
 
* ORICO 1106SS-V1-BK
 
* ORICO 1106SS-V1-BK
 
** "Cons: Not compatible with WD Red series HDD because of a design flaw." <ref>https://www.newegg.ca/Product/SingleProductReview.aspx?ReviewID=5119635</ref>
 
** "Cons: Not compatible with WD Red series HDD because of a design flaw." <ref>https://www.newegg.ca/Product/SingleProductReview.aspx?ReviewID=5119635</ref>
 +
 +
== Windows VM stuck at 800x600 resolution ==
 +
 +
* manually update graphics driver from virtio CD <ref>https://forums.unraid.net/topic/52909-windows-10-vm-quotnativequot-resolution-stucked-to-800x600-on-vnc-mode/</ref>
 +
  
 
== References ==
 
== References ==
  
 
<references />
 
<references />

Latest revision as of 22:00, 15 September 2022

host volume paths and the container paths[edit]

  • "The host path is (generally) your shares that you want to give the container access to. Best practice for containers dictates that if the container only needs access to a Downloads share, that you only create a mapping for the Downloads share."
    • eg. /mnt/user/Downloads
  • "On the container path side of things, you tell the container how it should "refer" to the host path. IE: If the container path is /Downloads, then whenever you tell the container to save something into /Downloads, docker will then "map" it and actually store it on your unRaid system at /mnt/user/Downloads." [1]

5.25" to 5X 3.5" Hard Drive Tray[edit]

  • ORICO 1106SS-V1-BK
    • "Cons: Not compatible with WD Red series HDD because of a design flaw." [2]

Windows VM stuck at 800x600 resolution[edit]

  • manually update graphics driver from virtio CD [3]


References[edit]