s.Oliver

hey siwat, thanks for sharing this Adguard Home docker! i had PiHole running before, but this one has some nice features. two things popped up and i wanted to let you know about (docker has a dedicated IP): 1) the template shows 2 entries for the Web GUI (ports 6052 [it's under the Icon URL] and port 3000 [under the working directory setup]) – but none of them works. ONLY port 80 does. 2) whenever i try to connect to it via a fqdn (like adguard.mydomain.whatever) it only shows a blank page (this works for all my other dockers, so i could image, that some kind of verification in the background doesn't like it to be called by fqdn and not IP only). i'm on unRAID 6.6.7 right now. tell me, if i can help with testing. thanks again for your work! 😃

alright man thx. i'll try this once i'm ready for my new PROXMOX installation.

hmm… maybe i read the screenshots wrong... but i guess, because of no other specified bootable device (boot device 1 = cd-rom with empty 'tray', device 2 & 3 are set to nothing, or have non-bootable devices) PROXMOX is looking at it's usb devices (for this VM) and boots from it, if bootable?

you're using it this way? (no special prepared bootable image, pure unRAID usb-stick and it boots directly from that?)

well, i answered all of your questions actually when you do passthrough your hardware to unRAID (HBA, or SATA controllers, or whatever) then unRAID has full control of it's features – and yes, it spins down all HDDs, which are connected to these passthrough'ed hardware. and this includes things like hot-swap (if supported by your hardware) or other things. if done in the right way, your 2nd question could be answered with yes! unRAID see's the drives as they would be on bare metal booted hardware (because you passthrough the hardware, which your drives are connected to then). your 3rd question references to my hint using plopkexec to boot natively into your unRAID installation on a USB stick (this is needed, because the hypervisor can't boot any VM from a usb stick; so plopkexec is a super small VM on ISO and it's then boots unRAID from the USB stick in stage 2). this method allows for native unRAID setup (with your USB key), without any changes/modifications, whatsoever. and the bonus is, that you never need to think about it in the future. all changes which need to be written to the usb stick (where unRAID is installed on) are written to the stick (and not to the ISO in the other guys setup). so no worries in the future – and you could boot unRAID on bare metal (without modifications). probably soon i'll tweak my setup again to go this virtualization route – because now i need the features of Proxmox, but i can't loose my unRAID-server – so i'll redo all this on my newer rig. hope this helps for your decision making.

thx. alot for integrating my wish. now gimme some time to test/play with it will report back.

hi alturismo, haven't tested your xteve docker yet, but i guess i would need a kindly different solution anyway. so my setup uses tvheadend for aquirering tv-signal and creating the epg data (from it's own grabbers directly from the channel stream). so here i would have a need to use (the already generated) TVH EPG data for PLEX and then use xteve's magic to tune from PLEX into a TVH channel. do you see any way of achieving this?

well, i helped a friend to setup dual drive ripping... end of story was, to use this docker two times (with different names) und passthrough one drive to each. so they work as they should, both with proper speeds.

not sure if this it it, but somewhen in the RC cycle there was a change so that displays got black after awhile of uptime – it was intentional as protection against burn-in (i guess, or...). catched me once, but a keypress wakes the screen.

it definitely is and i'm already pre-clearing another big drive (with the new version) – looking pretty good here. a big, big thank you!

thx. for being open to ideas 🙂 i would vote for hourly writes. my pre-clears with newer drives take 32-40 hrs. and i don't trace the progress too often – so i wouldn't miss a time span of 30 mins. anyway.

thanks alot gfjardim for clearing things up a bit. respectfully a few notes/ideas below: my observation about the amount/count of writes is different than what you wrote. with every GUI update on the Main tab of unRAID i see a flip between the 256 Bytes and 4,x KBytes shown. the update is around every 5 secs so in average that would be around 5 KBytes written every 10 secs. = roughly 70 MB per 40 hour pre-clear. now, it might be that the GUI doesn't show real values... anyway, my concern isn't the rough amount of data written, but the continuously writing (the stick gets written to for lets say 40 hrs. without break) . from my understanding the USB sticks aren't made for that exact use case (usually you write a bunch of files, then they are maybe read again and stay for some time and after a while you delete a few, write a few and so on). i wouldn't count on that everybody does have absolute good quality sticks. and these sticks can get quite hot while in continuously use – might not help with long lasting usage. unRAID's concept is (and please correct me here) to write only absolutely necessary config changes back to the USB stick. all other stuff is in RAM. now i imagine, that you like to have this resume file for some reason. but, because of these really long pre-clear sessions couldn't it be optimized to be on a lesser often schedule? i imagine, that if for some reason the operation is stopped, it probably wouldn't be too bad to have a resume file state of half (or even a full) hour back then on the stick. so my idea would be: use temp storage (ram) location for these high frequency updates and do only copy/or write (newly) once in awhile to a (power loss safe) location on the USB stick. so it would help to dramatically reduce writes to the stick and still have the resume file safely on stick (albeit maybe – and only in case of bigger problems – not in it's latest up to date state). but would it hurt to loose maybe 30-60 min. of documented pre-clear state? and would this be the high priority case which needs to be covered? my unRAID runs pretty stable for long time periods. i only like to help to make it even better (and more safe). thanks again for your great work on this really appreciated plug-in/tool for unRAID.

nobody has seen this strange issue? i'm running on 6.7RC7 and did another test with the next drive to clear; exactly when i started the pre-clear job, these writes started immediately again. stopped the pre-clear job and so the writes to the flash drive stopped. so right now, i simply can't pre-clear anymore, without risking the health status of my flash drive. any help please?

hey there! started yesterday to preclear a new disk and after awhile i recognized that there are continuously writings to the flash drive. it is flipping between 256,0 B/s and 4,6 KB/s (sometimes up to 4,9 KB/s). toggling the display shows an already impressive number of 416870 writes (and 1269 reads). so i'm pretty confident, that these writes do come from the preclear plug-in. maybe it's writing some kind of status on and on to the flash drive? anyway, it's kinda of a killer feature edit: after the preclear was successfully completed, these writings stopped and everything is back to normal; but the counter shows an impressive 733000 writes to the usb-stick.

sure thing – you're welcome.

ok, seems i've found my issue why only one container worked versus the other. the one which wasn't working had not clicked the setting "Allow for updates from the Webserver" (in the preferences setting of MakeMKV). after fixing this it got enabled.

hmm... for how long you run this container already? maybe i should try to rename/delete it's appdata folder and re-run/-config the container. maybe it then would clear things out.

hey Djoss, the latest development of MakeMKV brings the LibreDrive feature. it seems, that it isn't present in your container, is that right? out of curiosity it checked that against saarg's MakeMKV-RDP container and there it is present and working. is there anything special we need to do to get it working in your container? thanks for your great container!

i know, just wanted to give my experiences back – so it may be of some help to others who are reading here. usually (within other rdp sessions i use) there's always a username/password combination as credentials used. thx. for looking it up.

hey saarg, just revived your container to check the new LibreDrive support with my drive – and it seems to be supported, great! it only has one option not enabled and that one is the unrestricted drive speed (or very similar called). but i guess this is feature might be coming in the future and needs to be implemented by the developers of MakeMKV. now your container offers an RDP session. i only ask myself which credentials to use for the connection (using none for user/password doesn't work). thx.

The last update fixed the Picons, thx.

me too. have seen it over the last 2 updates. everything seems to work as usual, but the release number is off.

maybe you change it in the XML? the screenshot speaks of PCI vs. PCIe (PCI Express). mine looks like this (no matter which index nr.): <controller type='pci' index='1' model='pcie-root-port'>

never seen, that unRAID detects are drive wrong.

strange, switched once more and now i do see these thin lines as bars as well. but then, i'm too hooked on the black theme (navi bars, condensed look), so went back. i wish i could get that line-look in the black theme 🙂