BillyJ

Members
  • Posts

    113
  • Joined

  • Last visited

Posts posted by BillyJ

  1. On 6/19/2020 at 10:59 PM, xommit said:

    Not OK for me:

     

    
    <qemu:commandline>
        <qemu:arg value='-cpu'/>
        <qemu:arg value='-amd-stibp'/>
     </qemu:commandline>

    Execution error:

    internal error: qemu unexpectedly closed the monitor: 2020-06-19T12:55:42.118694Z qemu-system-x86_64: unable to find CPU model '-amd-stibp'

     

    OK for me:

     

    Before

    
    <cpu mode='host-passthrough' check='none'>
        <topology sockets='1' dies='1' cores='4' threads='2'/>
        <cache mode='passthrough'/>
        <feature policy='require' name='topoext'/>
    </cpu>

    After

    
    <cpu mode='host-model' check='none'>
        <topology sockets='1' dies='1' cores='4' threads='2'/>
        <feature policy='require' name='topoext'/>
    </cpu>

    Asus Strix X570-E Gaming + AMD Ryzen 3600

     

     

    Thanks, this worked a treat for my existing windows VMs after I moved from my Xeon setup to Ryzen 3900x / X570 Pro board. 

  2. Has anyone else had these messages when mover is run?

     

    Cannot stat file /proc/12396/fd/26: No such file or directory

     

     

    May 17 08:50:01 server-ramford kernel: mdcmd (60): spindown 5
    May 17 08:50:08 server-ramford kernel: mdcmd (61): spindown 4
    May 17 08:52:13 server-ramford kernel: mdcmd (62): spindown 1
    May 17 08:57:45 server-ramford kernel: mdcmd (63): spindown 0
    May 17 09:01:14 server-ramford emhttp: read_line: client closed the connection
    May 17 09:01:44 server-ramford emhttp: shcmd (43747): /usr/local/sbin/mover |& logger &
    May 17 09:01:44 server-ramford logger: mover started
    May 17 09:01:44 server-ramford logger: moving "TV"
    May 17 09:01:44 server-ramford logger: Cannot stat file /proc/12396/fd/26: No such file or directory
    May 17 09:01:44 server-ramford logger: Cannot stat file /proc/12396/fd/36: No such file or directory
    May 17 09:01:44 server-ramford logger: Cannot stat file /proc/12399/fd/11: No such file or directory
    May 17 09:01:44 server-ramford logger: Cannot stat file /proc/12399/fd/31: No such file or directory
    May 17 09:01:44 server-ramford logger: ./TV/ZZZ - S02E01 - SDTV.mp4
    May 17 09:01:44 server-ramford logger: .d..t...... ./
    May 17 09:01:44 server-ramford logger: .d..t...... TV/
    May 17 09:01:44 server-ramford logger: .d..t...... TV/ZZZ/
    May 17 09:01:44 server-ramford logger: .d..t...... TV/ZZZ/Season 2/
    May 17 09:01:44 server-ramford logger: >f+++++++++ TV/ZZZ/Season 2/ZZZ - S02E01 - SDTV.mp4
    May 17 09:01:48 server-ramford emhttp: /usr/bin/tail -n 42 -f /var/log/syslog 2>&1
    May 17 09:01:50 server-ramford logger: ./TV/ZZZ/Season 2
    May 17 09:01:50 server-ramford logger: .d..t...... TV/ZZZ/Season 2/
    May 17 09:01:50 server-ramford logger: ./TV/ZZZ
    May 17 09:01:50 server-ramford logger: .d..t...... TV/ZZZ/
    May 17 09:01:50 server-ramford logger: ./TV/
    May 17 09:01:50 server-ramford logger: .d..t...... TV/
    May 17 09:01:50 server-ramford logger: skipping "appdata"
    May 17 09:01:50 server-ramford logger: skipping "apps"
    May 17 09:01:50 server-ramford logger: mover finished

  3. Thanks!

    How hard would it be to build a docker for the nVR? I'm currently running it on a VM but thinking of trying to make one.

     

    Hi BillyJ, I just created a docker from scratch using the same phusion/baseimage 0.9.16.  When you first install it, you'll have to start it; it will create a system.properties file wherever you specified on the docker appdata folder.  You'll need to edit and add at the top : is_default=true

     

    After, you just restart the docker, you can access the initial wizard of the Unifi-video-controller.

     

    Awesome thanks!

  4. I don't know much about bonding and the same as you experienced times when I would not be able to connect to the webgui. This was usually down to the link aggregation on my switch not being done right most of the time.

     

    Right now I've settled for setting unRAID to 802.3ad(4). It can sustain a 113mb/s copy to a win 8 pc and 2 HD stream to plex on xbone. Until I bond the NIC's on the win8 PC I don't really know a way of testing the throughput.

     

    Yes i'd be very interested on some networking guru explaining a few more things about bonding or at least pointing to some generic linux bonding information on the net that would also apply to unRAID.

     

     

     

  5. Does it get stuck on a particular disk unmounting? Easiest way to check would be to just terminal in

    cd /mnt/user/

    ls

     

    and see which disk is still up, since it umounts from disk1 upwards in logical order. Or check the syslog and see which disk its hanging on. It could be a bad disk, or something running on that disk refusing to stop

     

    Thanks, will give it a shot next time.

     

    ps -elf | grep disk

    and

    ps -elf | grep user

     

    Will also give you info.

     

    For me in most cases it was cache_dirs taking longer then I had patience for to stop working...

     

    Thanks for this info, I have some bigger problems then the speed of the Unmount. Although I'm sure the last couple of unmounts that led me to post this may of in fact been the CPU stall issue.

     

  6. During the move from reiserfs to XFS my server suffered a CPU stall and a hard reset was the only option available.

     

    It was in the process of moving 2.7 TB worth of a Movies folder from Disk5 4TB (RESIER) to Disk6 3TB (XFS). I know it didn't complete the move, maybe 25% through. Used disk space is 2.90 TB.

     

    I kick off the move via Midnight Commander using the F6 function, I get prompted that the Target already exists. I choose Over all targets?  NONE.

     

    Now i've got 6TB (or close enough) to duplicate data and there is no way there is enough free space to continue.

     

    Does anyone have any ideas? Is the data in fact duplicate so i should be able to delete the Movies folder off my Disk6 and restart a complete move?

     

    Thanks

    Will

  7. Starting to tick me off a bit, so far I've moved 2 of my drives to XFS. Mover would have been moving the file to the new XFS disk.

     

    Should I put my cache back to BTRFS? It's currently XFS but I have seen in another post Tom suggesting the recommend v6 setup is BTRFS cache and XFS array.

     

     

     

    Feb 27 15:07:38 server-ramford login[763]: ROOT LOGIN  on '/dev/pts/5' from 'Medias-Mac-mini.willyweb.com.au'
    Feb 27 16:00:01 server-ramford logger: mover started
    Feb 27 16:00:01 server-ramford logger: moving "TV"
    Feb 27 16:00:01 server-ramford logger: ./TV/Vikings/Season 3/Vikings - S03E02 - The Wanderer HDTV-720p.mkv
    Feb 27 16:01:01 server-ramford kernel: INFO: rcu_sched self-detected stall on CPU { 7}  (t=6000 jiffies g=431630 c=431629 q=110233)
    Feb 27 16:01:01 server-ramford kernel: Task dump for CPU 7:
    Feb 27 16:01:01 server-ramford kernel: shfs            R  running task        0  4528      1 0x00000008
    Feb 27 16:01:01 server-ramford kernel: 0000000000000000 ffff88041fdc3da8 ffffffff8105e0b5 0000000000000007
    Feb 27 16:01:01 server-ramford kernel: 0000000000000007 ffff88041fdc3dc8 ffffffff81060780 0000000000000080
    Feb 27 16:01:01 server-ramford kernel: ffffffff81834400 ffff88041fdc3df8 ffffffff8107845f ffffffff81834400
    Feb 27 16:01:01 server-ramford kernel: Call Trace:
    Feb 27 16:01:01 server-ramford kernel: <IRQ>  [<ffffffff8105e0b5>] sched_show_task+0xbe/0xc3
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff81060780>] dump_cpu_task+0x35/0x39
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff8107845f>] rcu_dump_cpu_stacks+0x6a/0x8c
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff8107acb5>] rcu_check_callbacks+0x1db/0x4f9
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff81088601>] ? tick_sched_handle+0x34/0x34
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff8107ca53>] update_process_times+0x3a/0x64
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff810885ff>] tick_sched_handle+0x32/0x34
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff81088638>] tick_sched_timer+0x37/0x61
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff8107cf9b>] __run_hrtimer.isra.29+0x57/0xb0
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff8107d48a>] hrtimer_interrupt+0xd9/0x1c0
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff8102f72e>] local_apic_timer_interrupt+0x50/0x54
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff8102fb0b>] smp_apic_timer_interrupt+0x3c/0x4e
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff815fdf7d>] apic_timer_interrupt+0x6d/0x80
    Feb 27 16:01:01 server-ramford kernel: <EOI>  [<ffffffff8114c4bb>] ? __discard_prealloc+0x17/0xb3
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff8114c5bb>] reiserfs_discard_all_prealloc+0x44/0x4e
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff81168de0>] do_journal_end+0x4e7/0xc78
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff81169ad0>] journal_end+0xae/0xb6
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff8115a1c9>] reiserfs_dirty_inode+0x6c/0x7c
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff810478ac>] ? ns_capable+0x3a/0x4f
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff8111611c>] __mark_inode_dirty+0x30/0x1e1
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff81155f57>] reiserfs_setattr+0x262/0x297
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff810f95ae>] ? __sb_start_write+0x9a/0xce
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff81103706>] ? final_putname+0x30/0x34
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff8110d343>] notify_change+0x1dc/0x2d0
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff8110fecc>] ? __mnt_want_write+0x43/0x4a
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff8111a350>] utimes_common+0x114/0x174
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff8111a49b>] do_utimes+0xeb/0x125
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff8111a624>] SyS_futimesat+0x7f/0x9a
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff8111a653>] SyS_utimes+0x14/0x19
    Feb 27 16:01:01 server-ramford kernel: [<ffffffff815fd1a9>] system_call_fastpath+0x12/0x17
    

  8. Please start array in 'maintenance' mode, and click 'Check Filesystem' for each device.  Turn up any corruptions?

     

    reiserfsck -yq /dev/md1 2>&1
    reiserfsck 3.6.24
    
    Will read-only check consistency of the filesystem on /dev/md1
    Will put log info to 'stdout'
    ###########
    reiserfsck --check started at Thu Feb 26 13:07:15 2015
    ###########
    Replaying journal: Done.
    Reiserfs journal '/dev/md1' in blocks [18..8211]: 0 transactions replayed

     

    Is this the end? Or should I be waiting for more?

     

     

    Webgui is frozen on multiple machines, logged in via telnet and can see the process reiserfsck working away... I'll wait.

  9. Hi Guys, Seems to only occur when i invoke Mover and this writes to the log every 3 minutes.

    I can Telnet into server but webgui is unresponsive, dockers that are running come and go i.e. Plex will be browsable but then die somewhere in the 3 minute window.

     

    Only choice left is to login via IPMI and issue a power cycle.

     

    Any ideas? It seems to only have happened on Beta14..

     

    Thanks

    Will

     

    EDIT: I had just changed my cache from BTRFS to XFS after upgrade to B14.

     

     

    Feb 24 19:16:03 server-ramford emhttp: shcmd (10418): /usr/local/sbin/mover |& logger &
    Feb 24 19:16:03 server-ramford logger: mover started
    Feb 24 19:16:03 server-ramford logger: moving "Music Videos"
    Feb 24 19:16:03 server-ramford logger: ./Music Videos/METALLICA - Main feature.mp4
    Feb 24 19:17:03 server-ramford kernel: INFO: rcu_sched self-detected stall on CPU { 1}  (t=6000 jiffies g=2821570 c=2821569 q=29868)
    Feb 24 19:17:03 server-ramford kernel: Task dump for CPU 1:
    Feb 24 19:17:03 server-ramford kernel: shfs            R  running task        0  2081      1 0x00000008
    Feb 24 19:17:03 server-ramford kernel: 0000000000000000 ffff88041fc43da8 ffffffff8105e0b5 0000000000000001
    Feb 24 19:17:03 server-ramford kernel: 0000000000000001 ffff88041fc43dc8 ffffffff81060780 0000000000000002
    Feb 24 19:17:03 server-ramford kernel: ffffffff81834400 ffff88041fc43df8 ffffffff8107845f ffffffff81834400
    Feb 24 19:17:03 server-ramford kernel: Call Trace:
    Feb 24 19:17:03 server-ramford kernel: <IRQ>  [<ffffffff8105e0b5>] sched_show_task+0xbe/0xc3
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff81060780>] dump_cpu_task+0x35/0x39
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff8107845f>] rcu_dump_cpu_stacks+0x6a/0x8c
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff8107acb5>] rcu_check_callbacks+0x1db/0x4f9
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff81088601>] ? tick_sched_handle+0x34/0x34
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff8107ca53>] update_process_times+0x3a/0x64
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff810885ff>] tick_sched_handle+0x32/0x34
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff81088638>] tick_sched_timer+0x37/0x61
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff8107cf9b>] __run_hrtimer.isra.29+0x57/0xb0
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff8107d48a>] hrtimer_interrupt+0xd9/0x1c0
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff8102f72e>] local_apic_timer_interrupt+0x50/0x54
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff8102fb0b>] smp_apic_timer_interrupt+0x3c/0x4e
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff815fdf7d>] apic_timer_interrupt+0x6d/0x80
    Feb 24 19:17:03 server-ramford kernel: <EOI>  [<ffffffff8114c543>] ? __discard_prealloc+0x9f/0xb3
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff8114c5bb>] reiserfs_discard_all_prealloc+0x44/0x4e
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff81168de0>] do_journal_end+0x4e7/0xc78
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff81169ad0>] journal_end+0xae/0xb6
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff8115a1c9>] reiserfs_dirty_inode+0x6c/0x7c
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff810478ac>] ? ns_capable+0x3a/0x4f
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff8111611c>] __mark_inode_dirty+0x30/0x1e1
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff81155f57>] reiserfs_setattr+0x262/0x297
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff810f95ae>] ? __sb_start_write+0x9a/0xce
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff81103706>] ? final_putname+0x30/0x34
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff8110d343>] notify_change+0x1dc/0x2d0
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff8110fecc>] ? __mnt_want_write+0x43/0x4a
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff8111a350>] utimes_common+0x114/0x174
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff8111a49b>] do_utimes+0xeb/0x125
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff8111a624>] SyS_futimesat+0x7f/0x9a
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff8111a653>] SyS_utimes+0x14/0x19
    Feb 24 19:17:03 server-ramford kernel: [<ffffffff815fd1a9>] system_call_fastpath+0x12/0x17
    Feb 24 19:20:03 server-ramford kernel: INFO: rcu_sched self-detected stall on CPU { 1}  (t=24003 jiffies g=2821570 c=2821569 q=112021)
    

  10. Does it get stuck on a particular disk unmounting? Easiest way to check would be to just terminal in

    cd /mnt/user/

    ls

     

    and see which disk is still up, since it umounts from disk1 upwards in logical order. Or check the syslog and see which disk its hanging on. It could be a bad disk, or something running on that disk refusing to stop

     

    Thanks, will give it a shot next time.

     

     

  11. Are you using plugins?

     

    I was only using the APCUPS plugin but I have removed that since Beta14.

     

     

    Invoking the mover is not needed.. How do you shutdown or reboot ?  Thru the webinterface or from commandline... Or even (shudder to think) by pressing the button on your system ?

     

    I'd usually just click the move now button and wait till all the data is over to the array... Mostly though the web interface, I choose Stop array. After 5 or so minutes i had been known to use Terminal and remote in and use the reboot command.... failing that after 10 minutes  (maybe happens a few times a month) I would login to IPMP and click power cycle to force it.

     

     

     

     

     

  12. The amount of time to mount disks can very considerably depending on whether you did a successful tidy shutdown, and also with how much data you tend to write.  A forced close is VERY likely to lead to extended mount times as any transaction logs need to be replayed.

     

    The sync times on shutdown can also depend on whether you have been writing data to the array just before initiating the shutdown.    If you have then you have to wait while disks any buffers in RAM are flushed to disk.  The more RAM you have the longer this can take.  If the server has been idle for some time, then data is almost certainly already flushed, but you have to wait while disks are spun up so they can by synced.

     

    I had just moved 60GB of 2mb video files off the cache to the array, then proceeded to reboot. I always invoke mover before a shut down or reboot to clear the cache.

     

    With beta14 I've just formatted to XFS from BTRFS and it seems like stop and starts are close to about 10 seconds, I'll wait and see if this goes back up to 5 min when i kick off my NVR. I could have stuffed something up with the BTRFS pooling i attempted a while back.

     

    Thank you.

     

     

     

     

  13. I'm scared!

    Have i lost my docker.mg?

     

    "Your existing Docker image file needs to be recreated due to an issue from an earlier beta of unRAID 6. Failure to do so may result in your docker image suffering corruption at a later time. Please do this NOW!"

     

    A bit dramatic, right?

     

    Thanks for clarifying, i'll re-create the file again.

  14. I'm interested .

     

    unRAID: 6.0-beta9 Pro

    MB: Supermicro X10SL7-F 

    CPU: Intel Xeon E3 1230 v3

    RAM: Hynix HMT41GU7MFR8C-PB 8GB (2x8GB) 1600MHz ECC DDR3

    CACHE Drive: 120Gb + 180Gb Intel 520's Btrfs pool (300Gb Total)

    HDD: 6 x 4Tb WD SE's 3 x 3tb WD RED's

     

     

    Desired VM. Win 8.1

    Vpcus: 6

    RAM: 12GB

    Passthrough

    NIC: 1gb Intel® i210AT

    SATA Controller: 2x SATA (6Gbps),

    GPU: SAPPHIRE HD 7970 3GB GDDR5 or Nvidia GTS250

     

    I had previously tested various scenarios under XEN but keen on a switch to KVM I am in the process of building my desired  VM over the next few nights.