Jump to content

archedraft

Community Developer
  • Posts

    2,070
  • Joined

  • Last visited

Posts posted by archedraft

  1.   [mention=78569]Schlichi[/mention] Mind linking to the USB PCI-E card you're using please?  Got one passed through, but it's not working in the VM...

     

     

    I just bought this last week for 10.13. It works; however, I have to plug the USB devices directly into it. I have 2 different USB hubs and for some reason High Sierra doesn’t recognize them? 10.11 works with both with out any issues so I have no idea what’s going on. Good news is the new PCIe card has 4 usb so plugging everything into it is fine. I really wish I knew why the hubs are not working (did 10.13 add some sort of hardware compatibility requirements or maybe a USB 3 controller has to has a USB 3 hub??).

     

    ORICO 4-Port USB3.0 PCI-E Expansion Card USB3.0 4 Port PCI Express to USB3.0 Host Controller Adapter Card with 30cm 15PIN SATA to Big 4PIN Power Cord Compatible with Windows,Vista,Linux and Mac OS http://www.newegg.com/Product/Product.aspx?Item=9SIA1DS1EA8223

     

    • Like 1
  2. Upgraded from latest RC. unRAID booted fine and all VMs and Dockers appeared to load when all of the sudden everything froze. Let it sit for 10 mins but it’s was completely unresponsive, not even CLI. Had to hard reset so no diags. Upon reboot my VMs did not auto start. Virtual Manager had set its self to not auto start and said the default ISO and VM storage paths did not exist. It was looking for the unRAID default paths which I removed many versions ago. Anyways, I set up my correct paths which were set that way in the last RC and started the VMs. unRAID has been up and working for the past 10 hours and everything appears to be good. Not sure what happened but my guess is the VM settings may have caused the original unresponsiveness. Anyways hope this may help [emoji4]

     

    As always, thanks LT for another great release with amazing features!

     

     

  3. I reported the same thing during 6.4rc9f.  Obviously it got missed on the todo list though

     

    https://forums.lime-technology.com/topic/60516-64rc9f-creating-wrong-shares-for-vm-system-if-spaces-in-path/

     

     

    Thanks, I’m glad I finally know what the culprit is! Drove me crazy for the longest time but with my limited time and the fact that I only ever reboot the server to get the latest update, I just dealt with deleting the new share.

  4. I have been having an issue with one of my Shares that has a space "arche backup". Upon every reboot a new share will get created called "arche". I delete the new share "arche" and it goes away until I reboot. This has been happening with all the 6.4 betas and I think the 6.3 series as well. I believe it has to due with the VM Manager settings. I had " Default VM storage path:",  "Default ISO storage path:", and "Default Windows VirtIO driver ISO (optional):" all set do different subfolders under "/mnt/user/arche backup/". I just changed all three to "/mnt/user/" and the "arche" folder no longer gets created upon a reboot.

  5.  
    Looks to me like one or both your VMs are not shutting down in the set 60 seconds, so it forces shutdown after that, do they shutdown if you the array?


    Well shoot. No there is one VM that will not shutdown with the “virsh shutdown” command. In the 6.3 versions I was using “user scripts” to send the “virsh destroy” command at array shutdown to fix this. Are you aware of a way to send this command right after the “reboot” gets triggered?
  6. I used to have a script that would check if the array was started and parity check was not running before backing up files. Using:

    #!/bin/bash
    
    var=/proc/mdcmd
    array=$(grep -Po '^mdState=\K\S+' $var)
    rsync=$(grep -Po '^mdResync=\K\S+' $var)
    
    if [[ $array == STARTED && $rsync -eq 0 ]]; then
        rysnc script
    fi

     

    I saw that from rc8 onwards the preferred method to read array status is by quering the var.ini and disks.ini files.

     

    so I updated the a test script to the following:

    #!/bin/bash
    
    var=/var/local/emhttp/var.ini
    array=$(grep -Po '^mdState=\K\S+' $var)
    rsync=$(grep -Po '^mdResync=\K\S+' $var)
    
    echo $array
    echo $rsync
    
    if [[ $array == STARTED ]];
    then
    	echo "ARRAY STARTED"
    else
    	echo "ARRARY NOT STARTED"
    fi
    
    if [[ $rsync -eq 0 ]];
    then
    	echo "RSYNC 0"
    else
    	echo "RSYNC Running"
    fi

    and my output is:

    "STARTED"
    "0"
    ARRARY NOT STARTED
    ./test: line 17: [[: "0": syntax error: operand expected (error token is ""0"")
    RSYNC Running

    Does anyone know why the if else logic is coming back false instead of true like the echo variables are stating?

  7. Does UD no longer support NTFS format? In the past I would take my backup hard drives out of the safe and plug it into unRAID via USB and then copy all the new content to the backup hard drives. I tired to do this today and got the following errors. I can plug them into a Windows computer and it reads the drive just fine. I am running 6.4.0-rc9f and UD version 2017.10.07

     

    unRAID Log

    Oct 21 08:42:22 Pithos kernel: usb 1-1.6: device descriptor read/64, error -71
    Oct 21 08:42:22 Pithos kernel: usb 1-1.6: device descriptor read/64, error -71
    Oct 21 08:42:23 Pithos kernel: usb 1-1.6: device descriptor read/64, error -71
    Oct 21 08:42:23 Pithos kernel: usb 1-1.6: device descriptor read/64, error -71
    Oct 21 08:42:23 Pithos kernel: usb 1-1.6: device not accepting address 31, error -71
    Oct 21 08:42:24 Pithos kernel: usb 1-1.6: device not accepting address 31, error -71
    Oct 21 08:42:24 Pithos kernel: usb 1-1.6: device descriptor read/64, error -71
    Oct 21 08:42:24 Pithos kernel: usb 1-1.6: device descriptor read/64, error -71
    Oct 21 08:42:24 Pithos kernel: usb 1-1.6: device descriptor read/64, error -71
    Oct 21 08:42:25 Pithos kernel: usb 1-1.6: device descriptor read/64, error -71
    Oct 21 08:42:25 Pithos kernel: usb 1-1.6: device not accepting address 34, error -71
    Oct 21 08:42:26 Pithos kernel: usb 1-1.6: device not accepting address 35, error -71

    UD Log

    Oct 21 08:39:11 Partition 'DATA BACKUP' could not be mounted...
    Oct 21 08:39:34 Disk with serial 'HGST_HTS725050A7E630_TF655AY9KGBT4L' is not set to auto mount and will not be mounted...
    Oct 21 08:40:13 benchmark: shell_exec(/usr/bin/timeout 20 /bin/df '/dev/sdj1' --output=used,source 2>/dev/null|/bin/grep -v 'Filesystem'|/bin/awk '{print $1}') took 30.533089s.
    Oct 21 08:40:13 Adding disk '/dev/sdj1'...
    Oct 21 08:40:13 Mount drive command: /sbin/mount -t ntfs -o auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdj1' '/mnt/disks/DATA_BACKUP'
    Oct 21 08:40:13 Mount failed with error: ntfs-3g: Failed to access volume '/dev/sdj1': No such file or directory
    
    Oct 21 08:40:13 Mounting ntfs drive read only.
    Oct 21 08:40:13 Mount drive ro command: /sbin/mount -t ntfs -ro auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdj1' '/mnt/disks/DATA_BACKUP'
    Oct 21 08:40:13 Mount of '/dev/sdj1' failed. Error message: ntfs-3g: Failed to access volume '/dev/sdj1': No such file or directory

     

  8. 25 minutes ago, gridrunner said:

     

    @archedraft Wow, the guy who originally brought us the OSX VM on unRAID, likes my video! :) 

    I haven't actually tried passing through my USB controller on High Sierra yet (as when I set it up there were no Nvidia web drivers for my GPU).

    But I will definitely try it this weekend now.

    My best guess is that because in this guide the XML is different to try to correct mouse tracking for the vnc. 

    The USB tablet is added

     

    The original guides were no where near as easy to install everything as your videos have become. It was really impressive to take the USB installer and covert that to an image file to install the macOS system. I really like how this install is becoming more vanilla than the older OS X systems.

     

    I attempted changing the XML as you suggested but still no luck. Let me know if you have success this weekend!

     

    Edit: If anyone is having issues getting the full macOS High Sierra installer downloaded and instead getting the 19.9 MB installer, I had to upgrade my Sierra (10.12) system to the latest Sierra version and then download macOS High Sierra to get the full ~5GB version.

  9. Awesome video on High Sierra @gridrunner! I actually haven't upgraded my OS X since Yosemite so I thought it was time. I do have a question, I got everything up and running with VNC. Then I went back and edited the XML to include my graphics card and USB controller. Graphics loaded fine but the USB mouse movement is crazy laggy. Have you run into this? I also tried Sierra (macOS 10.12) and after everything was installed and running fine, I added the USB controller and the mouse was also laggy. It was working fine on Yosemite under Seabios, so not sure if this is a newer mac symptom or possibly something to do with OMVF.

  10. 16 hours ago, kaiguy said:

    First RC for 6.4 I have tried. Upgraded from 6.3.5 stable without issue. Renamed EFI- to EFI, made appropriate changes in the BIOS, and all booted up perfectly the first time. WebGUI is super snappy (starting Dockers used to take a few seconds, now it's immediate)!

     

    Really great work, Limetech team!

     

    I just did the same as above and can confirm the same results. My Windows 10 VM has never started as quickly as it did today. I barely saw any of the startup screens. Great work everyone!

×
×
  • Create New...