limetech

unRAID OS version 6.3.2 Stable Release Available

186 posts in this topic

Posted (edited)

15 hours ago, Frank1940 said:

 

....


2017 Mar 12 15:09:01|25998|115.4 MB/s|0|0

Did you by any chance terminate it before it completed?

By all appearances the parity check ran through to completion, I did not interrupt it as far as I know. The box was idle and all drives spun-down prior to applying the update the day after the last parity check. The 6.1.9 UI showed the expected message. <shrug>  The format of the log entries appears to be the same too. It will parity check again on Sunday. I'll keep an eye on it and go from there, lol.

 

Thanks for your reply!

 

Edited by BoHiCa
0

Share this post


Link to post
Share on other sites
On 3/9/2017 at 9:11 AM, thither said:

Just to confirm, I also see these same checksums on my Asus Z170 board, and my syslinux.cfg is the same as the one @JonUKRed posted above (and I'm also not able to boot into non-GUI mode). Don't have time for a BIOS upgrade now but I'll try it sometime in the next few days and report back.

 

Ok, so I updated my firmware BIOS to version 7.30 and was able to boot up normally in non-GUI mode again. Not sure what the deal is, but everything seems to be kosher now. Thanks for the advice! (Also I have an ASRock board, not an Asus one, just for the record.)

0

Share this post


Link to post
Share on other sites

Posted (edited)

On 3/2/2017 at 10:17 PM, richardsim7 said:

I did a quick search but couldn't find anything:

 

I upgraded from 6.2.4 to 6.3.2, and now my Windows 10 VM won't boot. SeaBIOS just says "No bootable device"

 

Any ideas?

nas-diagnostics-20170302-2017.zip

 

Did anyone figure this one out? I updated and am having the same problem.

If there is no workaround, how do I rollback to working version again?

 

 

ErrorWarningSystemArrayLogin


2017-03-19 16:31:39.625+0000: starting up libvirt version: 2.4.0, qemu version: 2.7.1, hostname: Megathron
LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name guest=Hyperion,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-Hyperion/master-key.aes -machine pc-i440fx-2.5,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -m 24576 -realtime mlock=off -smp 6,sockets=1,cores=3,threads=2 -uuid 9366709d-341c-8d6c-8a46-49a67ce382bd -display none -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-1-Hyperion/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -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/user/VDisks/Hyperion/vdisk1.img,format=raw,if=none,id=drive-virtio-disk2,cache=writeback -device virtio-blk-pci,scsi=ofcharchannel0,id=channel0,name=org.qemu.guest_agent.0 -device vfio-pci,host=01:00.0,id=hostdev0,x-vga=on,bus=pci.0,addr=0x8 -device vfio-pci,host=01:00.1,id=hostdev1,bus=pci.0,addr=0x9 -device vfio-pci,host=02:00.0,id=hostdev2,bus=pci.0,addr=0xa -device usb-host,hostbus=1,hostaddr=2,id=hostdev3,bus=usb.0,port=1 -device usb-host,hostbus=1,hostaddr=3,id=hostdev4,bus=usb.0,port=2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0xb -msg timestamp=on
Domain id=1 is tainted: high-privileges
Domain id=1 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)
2017-03-19T16:31:42.749032Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,id=hostdev2,bus=pci.0,addr=0xa: Failed to mmap 0000:02:00.0 BAR 2. Performance may be slow
2017-03-19T16:31:42.806343Z qemu-system-x86_64: warning: Unknown firmware file in legacy mode: etc/msr_feature_control
2017-03-19T16:32:31.627414Z qemu-system-x86_64: terminating on signal 15 from pid 4933
2017-03-19 16:32:33.228+0000: shutting down, reason=destroyed

 

EDIT: I figured it out! I had to disable the passthrough for my PCIE USB card.

Any ideas how could I get the PCIE passhtrough working again, sucks using Windows VM without one?

 

ie. how do I fix this: " 2017-03-19T17:00:39.411645Z qemu-system-x86_64: -device vfio-pci,host=02:00.0,id=hostdev2,bus=pci.0,addr=0xa: Failed to mmap 0000:02:00.0 BAR 2. Performance may be slow ?

 

megathron-diagnostics-20170319-1847.zip

Edited by Lake-end
0

Share this post


Link to post
Share on other sites
On 3/14/2017 at 1:04 PM, BoHiCa said:

By all appearances the parity check ran through to completion, I did not interrupt it as far as I know. The box was idle and all drives spun-down prior to applying the update the day after the last parity check. The 6.1.9 UI showed the expected message. <shrug>  The format of the log entries appears to be the same too. It will parity check again on Sunday. I'll keep an eye on it and go from there, lol.

 

Thanks for your reply!

 

It was definitely a change to the format of the line-data in ./config/parity-checks.log

 

Feb 26 18:09:40|76178|26.3 MB/s|0
Mar  5 18:09:14|76152|26.3 MB/s|0
Mar 12 19:09:49|76188|26.3 MB/s|0
2017 Mar 19 23:18:21|94700|21.1 MB/s|0|0

The first 3 lines are from 6.1.9, and the last is from 6.3.2.  I took a bit of a haircut on the parity check speed with the version bump! Zoinks!  My PCIe bus is saturated with so many drives on the under-powered motherboard (It's one of the Intel Atom boards), so that's likely the fastest it will get until I can migrate to better hardware with more individual lanes for each SATA device.

 

Mystery solved!

 

0

Share this post


Link to post
Share on other sites
26 minutes ago, Zonediver said:

Where can i open this Parity-Window?

Thanks :)

Main - Array Operation - History button

1

Share this post


Link to post
Share on other sites
2 minutes ago, trurl said:

Main - Array Operation - History button

Thanks trurl - i never saw this button - i am blind :P

Thanks again for your help :)

0

Share this post


Link to post
Share on other sites

upgraded one of my hp servers to 6.3.2.

 

Core numbering is wrong (as shown in the other thread.)

 

cpu 0 <===> cpu 16
cpu 2 <===> cpu 18
cpu 4 <===> cpu 20
cpu 6 <===> cpu 22
cpu 8 <===> cpu 24
cpu 10 <===> cpu 26
cpu 12 <===> cpu 28
cpu 14 <===> cpu 30

 

New vm errors popping up

 

smbus: error: Unexpected recv start condition in state 3
smbus: error: Unexpected read in state -1
smbus: error: Unexpected NACK in state -1
smbus: error: Unexpected NACK in state -1

 

Server ate the cache drive twice. had to format each time.

 

Also received "call traces" notification twice on an array drive with an ok smart report, and forced to format it once.

 

also now getting the following 

 

NMI: PCI system error (SERR) for reason a1 on CPU 0.

probably related to an P410i onboard that has failed but not being used. i keep forgetting to disable it in the bios but no communication runs through it to drives.

 

Looks like i'm rolling back to 6.2.4 since the core renumbering actually has another problem. You can't assign the renumbered cores properly in a vm. If you give it cores 4,6 it puts both cores on a single lower core instead. And you can't assign cores over the recognized number, so half the cores can not be accessed by a vm even if you skip core numbers to address renumbering problem. So yeah, half the performance possible.

 

 

 

brahms3-diagnostics-20170323-1534.zip

0

Share this post


Link to post
Share on other sites
5 hours ago, 1812 said:

upgraded one of my hp servers to 6.3.2.

 

This is a known bios issue with HP Proliant:

 

 

0

Share this post


Link to post
Share on other sites
15 hours ago, limetech said:

 

This is a known bios issue with HP Proliant:

 

 

 

 

I posted in that thread 10 days ago, including providing diagnostics before the upgrade to 6.3.2 and after for comparison. One of the other folks having problems who posted is on 2010 bios. This server is on 2015. Does the mean that  anyone using a proliant is stuck at 6.2.4 if they want full server functionality? Because everything seemed to work just fine then.

 

 

edit

rolled back to 6.2.4, disabled the P410i and switched to backup bios (2010) and all problems went away.

Edited by 1812
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

Copyright © 2005-2017 Lime Technology, Inc. unRAID® is a registered trademark of Lime Technology, Inc.