Jump to content

Ashe

Members
  • Posts

    515
  • Joined

  • Last visited

Posts posted by Ashe

  1. So I figured out what I needed to do to get each issue to display properly.  Each issue needs its own folder under the Magazine top folder.  That's the only way to get the program to autocreate a thumbnail for each issue.  So for me it looks like.
     

    /magazines/Wired_2017-04/2017-04 - Wired.pdf

    /magazines/Wired_2017-03/2017-04 - Wired.pdf

     

    The biggest downside is that it will end up being a huge number of folders with no real folder structure.  but the thumbnails all show up properly so i'm happy.  I was also able to change Lazy Librarian to auto create my folders this way.



    Yes that's it. Works great then but a bit annoying for folder organisation !
  2. On ‎15‎/‎03‎/‎2017 at 7:41 PM, boyer411 said:

     My main suggestion is change it so it shows each cover accurately.  Right now if I have 3 issues of a magazine, they all get the same cover, and its not necessarily the newest one.  Also a way to sort them would be nice. (Name, Issue Date, Date Added)  If not that, then do what mgworek said and only show the newest cover for a magazine and then once you select it, it shows each issue for that specific magazine.  

    I think this is because you have a sub-folder with a magazine title and then sub-sub-folders with each issue. If you have a sub-folder per magazine issue then it will display the cover for each one correctly.

     

    i.e. /magazines/customPC/issue1 - displays 1 cover for all versions

    /magazines/customPC-issue1 - displays correct cover

     

    EDIT: i'm not sure if this is the authors intent for the folders organisation, just how I have noticed it will work in order to display the correct images.

  3.  
    I am still having issues with pulling logs in the app. My password is set, I am running the most current versions of unRAID (not beta), ControlR plug-in, and Android app. 
     
    Any ideas?


    Stop and start the plugin on unraid.
    • Upvote 1
  4.  

    Linux 4.8.7-unRAID.

    1 failure since last login.

    Last was Wed Nov 16 20:36:51 2016 on /dev/pts/0.

    root@MediaOne:~# lscpu

    Architecture:          x86_64

    CPU op-mode(s):        32-bit, 64-bit

    Byte Order:            Little Endian

    CPU(s):                4

    On-line CPU(s) list:  0-3

    Thread(s) per core:    2

    Core(s) per socket:    2

    Socket(s):            1

    NUMA node(s):          1

    Vendor ID:            AuthenticAMD

    CPU family:            21

    Model:                48

    Model name:            AMD A8-7600 Radeon R7, 10 Compute Cores 4C+6G

    Stepping:              1

    CPU MHz:              1900.000

    CPU max MHz:          3100.0000

    CPU min MHz:          1400.0000

    BogoMIPS:              6386.11

    Virtualization:        AMD-V

    L1d cache:            16K

    L1i cache:            96K

    L2 cache:              2048K

    NUMA node0 CPU(s):    0-3

    Flags:                fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb bpext ptsc cpb hw_pstate vmmcall fsgsbase bmi1 xsaveopt arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold overflow_recov

    root@MediaOne:~#

  5. hard reboot done

     

    manual edit of xml to

     

      <topology sockets='1' cores='2' threads='1'/>

     

    results in a log of

     

    2016-11-16 14:22:27.648+0000: starting up libvirt version: 1.3.1, qemu version: 2.7.0, hostname: MediaOne

    LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name Windows10_S -S -machine pc-i440fx-2.5,accel=kvm,usb=off,mem-merge=off -cpu host -m 16384 -realtime mlock=on -smp 2,sockets=1,cores=2,threads=1 -uuid 0cc6ef55-6f27-50ee-c5c5-6a9cb077177c -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-Windows10_S/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device nec-usb-xhci,id=usb,bus=pci.0,addr=0x7 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 -drive file=/mnt/cache/domains/Windows10_S/vdisk1.img,format=raw,if=none,id=drive-virtio-disk2,cache=writeback -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk2,id=virtio-disk2,bootindex=1 -drive file=/mnt/cache/domains/Windows10_S/vdisk2.img,format=raw,if=none,idr=0x8 -device usb-host,hostbus=3,hostaddr=2,id=hostdev2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x9 -msg timestamp=on

    Domain id=2 is tainted: high-privileges

    Domain id=2 is tainted: host-cpu

    char device redirected to /dev/pts/1 (label charserial0)

     

    update of VM using the 'edit' menu and save (no changes made) results in xml being modified to

     

      <topology sockets='1' cores='1' threads='2'/>

     

    click start VM - immediate crash of unRAID - no GUI/telnet - hard reboot required.

     

    on RC3 the server would not lock up with the above configuration but i have not had a need to edit the VM so cannot confirm when this started to happen.

     

  6. LT should be able to set threads to 1 when AMD CPUs are detected.

     

    This code already exists in the current RC, but it doesn't actively scan existing VMs that were created PRIOR to that fix being put in place.  As such, you need to click "Edit" and then "Update" on each of your existing VMs before starting them in the new version.  This will remove any custom XML you've applied, but it will also fix the topology section of the XML to properly use cores, not threads.

     

    If anyone has an AMD system, please test this for us and reply back here with confirmation.

     

    Editing a Windows VM via the 'Edit' option selecting 2 cores (2 and 3) for assignment to the VM shows XML code of

     

      <topology sockets='1' cores='1' threads='2'/>

     

    Editing a Windows VM via the 'Edit' option selecting 1 core (3) for assignment to the VM shows XML code of

     

        <topology sockets='1' cores='1' threads='1'/>

     

    I was going to display the codes and show the difference when cores are manually edited, but after changing the VM back to 2 cores on the 'Edit' option and starting, my VM just crashed unRAID and as I was remoting in I now no longer have access. I will update when I have physical access to the server.

     

    As my post in the CPU KVM Bug thread, I am positive that this is the cause of my unRAID instability and the weekly crash of the system, but as I cannot get logs for it then I cant investigate further.

     

     

     

     

  7. Anyone with AMD hardware test this to see is the VM issues have been resolved?

     

    Sent from my SM-N910V using Tapatalk

     

    No change, running an AMD A8-7600 Radeon R7 on an A88XM-Plus MB with RC4

     

    XML is manually modified to the below which seems to suppress the errors

     

      <cpu mode='host-passthrough'>

        <topology sockets='1' cores='1' threads='2'/>

      </cpu>

     

    but log still shows

     

    2016-11-12T23:22:16.086993Z qemu-system-x86_64: AMD CPU doesn't support hyperthreading. Please configure -smp options properly.
  8. Docker log section requests plugin to be installed

    ...

     

    Yes, I think I need to reword the message a bit, because it's valid that any of the logs doesn't exist at all.

     

    ...

    And the VM section only shows the first booted VM, subsequent booting of VMs do not seem to register with the plugin

     

    Not sure what you mean by this. Can you please clarify ?

    All dockers have logs currently but the message doesn't show that

     

    For the VMs for example it shows my ubuntu VM log which is set to auto start, when I manually start up my win 10 after startup there is no shown log for the win 10 VM

  9. Not sure if this is addressed in the iOS update, but currently when changing the text size on the iPhone it loses my server settings and it has to be re-added

     

    I thought the same happend to me, but i was wrong.

    When you have changed the text size and return to the server list, then your server is gone. Then swipe down the screen to refresh and you server will be back.

     

     

    Sent from my iPhone using Tapatalk

     

    Quite correct, thanks for that.

  10. Don't quote me but I am sure lychee does the same as piwigo in terms of database and additional copy of photos. The alternative is to point your docker data to an array location but whether the software will pick up a direct write to the folder for new photos or only through the software, I don't know. It's a shame as both piwigo and lychee are very good

  11. Installed and working fine so far, no obvious failings. I agree with johnnies first comment for white/grey if no notices are available. I would also prefer the notifications to be aligned to the far right, no reason other than most OS's I am used to keep notifications aligned to an edge and it's more familiar.

  12. 2nd cron backup worked fine. The next issue I see is the multiple dated backups taking up considerable space. Will look at deleting after a set number or time period

    I was able to reduce my filesize by gzip.

     

    Dan, would be nice to add an automatic gzip to the backup file. Since my VM img is 100GB, the backup is also. After gzip, it reduced to 17GB......quite a difference.

     

    For simplicity I would prefer any compression to be optional but I could see it being a useful option for some

  13. 2nd cron backup worked fine. The next issue I see is the multiple dated backups taking up considerable space. Will look at deleting after a set number or time period

     

    Would you like to see only one maintained or a simple switch which allows you to choose how many you can keep?

     

    I think the switch would be the ideal version.

     

    Probably one for the roadmap (if at all) is selecting which vdisks are backed up if multiple are used for one VM. For example, I use a second vdisk on a Windows VM as a one drive disk as there is no one drive docker yet but I don't need that backed up as I sync it to my array and of course in the cloud

×
×
  • Create New...