Jump to content

Joseph

Members
  • Posts

    444
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Joseph

  1. agreed. I'll give that a shot next time I can and let you know how it goes Agreed, but it wasn't like that until I prevented the disks from sleeping; but like you said, it could be a combo of things. TM backups are typically 7G+ and I don't have a clue why... wasn't like that on my old Mac when I had TM as a local drive. I haven't used TM in awhile stuff was moved around which could perhaps explain this 40G session, but the large backups in general are a mystery. I'll dig around and see what I can find. But it may, along with the other issues, require the use a few 'lifelines' to the unRAID community in other threads
  2. So, the backup box is back up. The 10Gbe cards I just installed don't seem to be making much of a difference, but perhaps it's just my perception. fwiw, I'm not using the cache drive or SSD for TM it's the only thing using the backup unit for now. (Results from the command are attached) 8.21 MB/s is terrible!! I have no idea what's going on. I stand by my original observation: SMB transfers are much faster after unchecking "Put hard disks to sleep when possible" in the Energy Saver settings than it used to be; but it seems I should be getting faster R/W speeds with the new 10GBe NICs, so I suspect the new NICs aren't configured properly... idk. ...guess that's a topic for another thread. ps. not sure why the error at the end of the log: error: Disk object invalid or unable to serialize Here's a screenshot of TM while running. It went from 1 hour to 2 hours remaining as I'm typing...wth 🙁 results.txt
  3. So far so good for several months now. I like the idea of establishing a baseline so we all know. Unfortunately, that command doesn't seem to be working. Could it be because the backup box turned off in order to do a HW upgrade? If that is the case, I'll let you know after I get it up and running and try the command again. fwiw, Production Box: A DnD transfer of a 9.6GB file from the Mac to the cache pool now takes about 2mins when it used to take hours (I should note, I've just upgraded to 10GBe, but haven't seen any noticeable improvement; which is another topic for discussion) a DnD transfer of an 8GB file from a VM which is stored on an SSD to the cache drive seems to be faster than the file transfer on the Mac. (see attached) Backup Box: If memory serves, it now takes TM about 30 mins to backup about 7GB or so, plus cleanup if any. (For whatever reason it's always backing up a minimum of about 7GB, which is annoying, but I digress). I'll double check that once I get the backup box back up and running, but it used to take hours, if not days in some cases to finish. The backup box is multi use, and I have VMs backing up crucial data from the production box to the backup throughout the day, so I'm sure that affects performance as well. Additional Thought(s): Does anyone actually trust the ability of TM on unRaid to be able to successfully complete a Bare Metal Restore? note: these screen captures show different files copied, but you get the idea:
  4. Hi. Unfortunately, it's a bit overkill for what I need. I run the backup box headless; so it's just for getting past POST/Bootup, and the occasional use of the localhost gui. Thanks for your suggestion though.
  5. Hi unRaiders, does anyone have an ancient VGA PCI or PCI-e x1 graphics card they no longer need? My backup unit's x4/8/16 slots are in use and the only port options I have left so I can add a monitor are either PCI or PCI-E x1. Many thanks!! Ps. I'm in the US.
  6. Interesting... I had the same problem.. seems the culprit was the NVIDA driver plugin that I had installed awhile back. Deleted that and now it's back.... hope this helps someone else.
  7. I had the same problem.. seems the culprit was an NVIDA driver plugin that was installed awhile back. Deleted that and now it's back.... hope this helps.
  8. Hope someone will help you find an answer to your question 1. How did you change 2 & 3? I didn't think it could be done. Thanks.
  9. FWIW, I had horrible SMB unRaid R/W speeds with my Mac workstations including Time Machine backups until I did this one weird trick... 🤣 ok, now that you fell for the click bait... after trying the various suggestions from others (I.e. turn off SMB signing, turn Case sensitivity on, forcing the min/max protocol to SMB2, etc.) nothing seemed to consistently work. However, someone suggested on the Mac unchecking "Put hard disks to sleep when possible" in the Energy Saver settings and then reboot. It seems to have 'fixed' the issue for me. Haven't had R/W problems since, even after upgrading to 6.9.0. Fwiw, Time Machine is still a bit slow, which is probably because it's setup as a direct write inside the array, but at least it's bearable for me now. At some point along the way I undid all the other suggestions. Maybe reenabling them would improve things more... IDK. Anyways, hope this helps.
  10. you bet... here's a dark mode" version; it has the same issues as the first one, but I hope you enjoy
  11. gotcha... sorry for the unnecessary post then. I looked around and didn't see anything directly addressing the 2nd part. my bad for not doing enough dd. Nevertheless, thanks for the clarification.
  12. After update to 6.9.0, unRaid states all drives have returned to normal utilization after update, even though they're full. Once all messages were cleared (1 for each drive) a view of the main page shows the correct usages and color (red) of each drive. However, the dashboard displays the correct usage, but the indicators are all in green. This has happened on both my production and backup boxes. Main Page Dashboard
  13. It's far from perfect, but here's a 'quick n dirty' one I did for you. I might get around to fixing it at some point.
  14. I did a quick search and couldn't find this banner, so I thought I'd make one. It's still Christmas, right?
  15. Wait a minute, Doc. Are you telling me that you built a massive storage array... out of a DeLorean?! Whoa, this is heavy. 😃
  16. Here it is, no? I think the format is Bus:Slot.Function; so in your scenario the issue is on Bus 05, Slot 00 with Function 1
  17. +1 for limit share size. 6.8 has an option for Time Machine, but it's help info is unclear if it is for any kind of user share or exclusively for TM.
  18. Noob here, so consider the source! 😬 I went thru a gauntlet of things that I tried (and mostly failed) in an attempt to migrate from the plug-in version of EMBY to the docker container. Another user posted some steps and I documented things that I thought worked, but mostly didn't. It starts around page 142 or 143. In the end, after updating unRIAD to 6.4 the process somehow became much simpler and magically worked. I wish I knew why, but on page 144 what seemed to have worked, at least back then anyway, was to make sure to set the mappings properly for the content/appdata/etc. Hope this helps... don't forget: backup, Backup, BACKUP!!!
  19. @johnnie.black Thanks for the quick reply! I'll set all values to default then... fwiw, I'm running 20 drives in the array (incl. dual parity), also raid 1 cache on my production box and a few devices outside the array, so it sounds like I might be pushing it? Lemmie know. Thanks!!
  20. Hey unRAIDers!! So, it's now, 2020; can anyone offer any advice as to whether or not the tunables script is to be trusted on unRAID v6.8.3? I was able to get the update from the link that @Squid provided working via cli (sort of) with errors; thanks to the post from @Marshalleq (example below): /usr/local/sbin/mdcmd: line 11: echo: write error: Invalid argument Test 1 - md_sync_window=384 - Completed in 601.464 seconds = 96.6 MB/s The final "Best Bang for the Buck" results show the following... On my production box (Supermicro [I suspect either] AOC-USAS-L8i, [or] AOC-USASLP-L8i) Current in disk.cfg | New Setting ----------------------------------------------- md_num_stripes="4096" | md_num_stripes="1536" md_write_limit="" | md_write_limit="768" md_sync_window="" | md_sync_window="640" Not Saved. Exiting. and my backup box (2 Dell H310s): Current in disk.cfg | New Setting ----------------------------------------------- md_num_stripes="4096" | md_num_stripes="1280" md_write_limit="" | md_write_limit="768" md_sync_window="" | md_sync_window="384" Type SAVE (uppercase) to modify disk.cfg Not Saved. Exiting. Any input, thoughts, etc. are much appreciated!! I feel like this is a message in a bottle, but I hope someone will respond soon. Thanks in advance!
  21. +1 for Emby; I don't do transcoding either and it works just fine when using Emby Theatre on my HTPC. Don't have much issue with it other than the occasional/rare docker crash where you just need to restart it. I also have a Plex subscription, but I don't use it for streaming video. I like the look/feel/metadata usage of Plex for audio; Emby for video.
  22. Cool! I know at some point after v6.5 or so, the banner format has changed so this one might be limited in its ability to scale. Anyways, I hope it works out.
  23. Take a look and see if these will work (my blank templates are offline at the moment, so the size may not be correct)
  24. Sure... I’ll be happy to take a stab at it tomorrow; if I can distract the Mrs. for a few minutes I’ll start on it tonight
×
×
  • Create New...