Jump to content

JonMikelV

Members
  • Content Count

    34
  • Joined

  • Last visited

Community Reputation

7 Neutral

About JonMikelV

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. JonMikelV

    Chrome OS

    I'm a glutton for punishment so looked anyway - I can't get past "Booting 'local image A'".
  2. JonMikelV

    Chrome OS

    Thanks for the link @sharpfork. I had read through that as well and decided it sounded like a lot more work than it probably needed to be - at least here 2 years later. 🙂 What I've tried so far is: - download the CloudReady image from https://www.neverware.com/freedownload - unzip the cloudready-free-74.4.57-32-bit.bin (or cloudready-free-74.4.58-64-bit.bin) file into my ISOs folder - Create a VM with: + Logical CPUs: 2 + Initial & Max Memoru: 2G [min. spec. for CloudReady] + Machine: Q35-2.1 + BIOS: OVMF + USB Controller: 3.0 (qemu XHCI) [boots faster than USB 2] + OS Install ISO: path to cloudready-free-74.4.58-64-bit.bin + OS Install CDRom Bus: USB + Primary vDisk Location: Auto [created as 16G drive - again min. spec. for CloudReady] + Primary vDisk Bus: SATA + Graphics Card: VNC + VNC Video Driver: Cirrus [If you left the default of QXL (best) I didn't see any of the boot screens mentioned below] + VNC Password: <blank> + VNC Keyboard: English-United States (en-us) + Sound Card: None + Network MAC: <whatever defaulted> + Network Bridget: br0 + USB Devices <none> + Other PIC Devices: <none> With those settings, I am able boot the VM and see: - the "TianoCore" logo screen for about 3 seconds - a blank screen for about 8 seconds - the CloudReady boot logo for about 1 second - the animated "Your system is repairing itself. Please wait." page for about 3 seconds - the whole process start over Eventually I have to force-stop the VM. Per the Neverware support pages, this sort of boot loop is usually indicative of unsupported hardware of some sort so I've decided there may be something about the specific hardware my Unraid is running on that CloudReady doesn't like. I might be wrong, but I haven't made time to play around with anything else (like the 27 partition process in the link you provided).
  3. JonMikelV

    Chrome OS

    I doubt you'll hear much about actual ChromeOS. As far as I know Google doesn't provide any self-install type options (such as an ISO). That being said, ChromeOS is Google's customized version of the open source ChromiumOS (just like the Chrome browser is Google's customized version of the the Chromium browser). And just like how there are other customized versions of the Chromium browser (such as Brave, among others) there are other customized versions of ChromiumOS. This website has a nice comparison of the most common ones: - https://www.electromaker.io/blog/article/flint-os-vs-chromium-os-vs-cloudready-which-chrome-os-is-best To summarize it - as of Jan. 2019: - ChromiumOS - 'the original', open source, not necessarily the most polished or feature packed, - FydeOS (formerly FlintOS) - many variants (such as for RaspberryPi), supports Android apps, etc. - CloudReady (also formerly FlintOS) - more enterprise focused, supports CloudReady Linux apps, etc. So you might want to do some searching for ChromiumOS, FydeOS, or CloudReady and consider trying one or more of those as VMs on your Unraid box. If you, come on back and share your own experiences and thoughts! 🙂
  4. I like shiny new things and haven't had any major issues with updates in the past so decided to try 6.6.7 -> 6.7.0 even though I'm not near the box right now.... Oops. 🙂 30 minutes later I'm still at the "System is rebooting" page and while the device replies to pings it won't accept (actively rejects?) connection requests to the GUI. I have SFTP access and one of my remotely visible auto-start Dockers is running but another isn't and my auto-start VMs aren't. I have remote access to other machines on that network and the Unraid SMB shares do seem to be visible. I'm fine waiting until I have physical access to the device but if people have suggestions for remotely (via SSH) debugging I could poke around a bit. 🙂 Edit: Thanks @moose, apparently it just got stuck shutting down - once I physically power cycled it everything (including the expected loss-of-power parity check) was fine - hello 6.7.0! 🙂
  5. I'm curious how you figured out what plugin was causing the unexpected spinups.
  6. I'm glad you figured it out! I hadn't answered because I've not used privoxy before. In case in run into the same issues you had, what was the variable you needed to add?
  7. I've found a few posts about running Streambaby (a Java based TiVo video streaming app) on unRAID but they seem to be so old they're running it ON unRAID, not in a Docker. I checked Apps (and DockerHub) for Streambaby but found nothing so I'm curious if it's possible to run Java (and subsequently Streambaby) in a Docker container along with why I might NOT want to do so. Thanks. Jon-Mikel
  8. Another apology for bringing this thing back from the dead, but I've poked around a bit and still am not finding anything that sounds like a "definitive answer". According to the UnRAID manual 6 section on "The Engine" it sounds like Copy-on-write being enabled (set to "Auto") is good for Docker containers because it lets them use the same base OS image until one of them needs to make a change to it, at which point a copy is made and the "customizing" container user the copy while all others continue to use the original I suspect it's DISABLED (set to "no") for the "domains" share (which is for holding saved VM instances) because of the overhead associated with making copies of the VM file (or changed blocks of the file) every time the guest OS makes changes to the disk image. But that's purely a guess.
  9. Errmm...probably fixing the typo I put in my post will do the trick (oops!) Try "virtio" instead of "vrtio".
  10. Did you ever come up with a Docker based solution to this? I'm looking to to do the same thing and I found some containers at DockerHub, but I don't know how much I should trust any of them... - https://hub.docker.com/r/maxhq/ipd/ - https://hub.docker.com/r/hongkongkiwi/icloud-photos-downloader/ - https://hub.docker.com/r/hxyio/icloudcals/
  11. If I'm understanding https://wiki.qemu.org/Documentation/9psetup correctly the "unRAID Mount tag" field just makes the tag (in your case "youtube") available to be mounted with a normal `mount` command such as: `sudo mount -t 9p -o trans=virtio youtube /mnt/youtube` Assuming `/mnt/youtube` existed the above command would mount your `youtube` host share location (in your case `/mnt/user/Downloads/youtube-dl/`) at `/mnt/youtube' in your VM. So "unRAID share" doesn't actually auto-mount anything - still need to set that up with fstab as usual.
  12. Definitely on 6.5.3 'cause I just updated 2 days before (I think from 6.5.1). I saw another post about 6.5.2 having some issue with losing container settings and the container needing to be re-installed, but I figured the container disappearing altogether was a different issue... I'm still not sure sure how containers so was slightly surprised when the re-installed one came up with my previous history, but I suppose that makes sense if the "deleted" container only deleted the image, not the settings OR it really wasn't deleted (just hidden or lost from the GUI somehow).
  13. It appears unRAID 6.5.3 ate my Krusader container (which I used yesterday without issue) when I tried renaming it from "binhex-krusader" to "Krusader-binhex" (note the capital K). When the Dockers window reloaded after the rename, the container was gone. I checked installed "Installed Apps" on the "Apps" page and it wasn't listed there either, but it did show up on "Previously Installed Applications". It's not a big loss - this container is easy to install and there's not much customization I do with it, but I thought I'd mention it in case it's a general issue that needs to be addressed.
  14. Got it. That line was in the syslog.1.txt file but apparently you need to already have "skillz" to know that it's the cause of the "Call traces" message. ?
  15. I get the Mojolicious Perl messages as well, but I assumed it only mattered for CONCURRENT indexing and that asynchronous ("single thread") processing would still happen just fine. Does this container HAVE a webui? I thought it was all just "set these variables & let it do it's command-line thing"...