unRAID Server Release 6.2.0-beta18 Available


Recommended Posts

  • Replies 421
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

If you check your syslog  it mentions this error, I simply googled it..

 

Thanks, i found that part.

 

The scary bit is that the system was not even booted for a second before that entered the log. The boot that generated that log has remained on even now i have started a parity check and my vm is enabled.

 

I'm unsure where that is coming from but it doesn't seem to be the culprit but i will keep that in mind

The first timestamp in a syslog is unreliable.  Logged messages are being thrown at the syslog'ing tool before it's ready to save anything, not even file system support yet (not even in RAM).  So it has to buffer them until it can finally dump them, and when it does they all get the same timestamp, making it *look* like a bunch of things all happened in the same second.

 

The MCE reports 2 possible issues just as it's set up, but the system appears to work fine after that.  It does indicate something suspicious in the hardware.  Then there's a later MCE within the same second as this message -

vfio-pci 0000:0a:00.0: Invalid ROM contents

Not sure what that means, but that's your nVidia GTX 750 Ti card.  It doesn't like something about it, and probably isn't going to work right, if at all.

 

The actual MCE error reports is "mce: [Hardware Error]: Machine check events logged", implying there's a log somewhere.  Does anyone know where it is?  Could be very useful ...

 

Edit (cleaned up):

So i just managed a huge 40 minutes before the system locked up again. This time however it seems i have ssh access.

 

I have told a syslog to save and have told the system to shutdown.

I have attached the syslog but it does not seem to be complete as i am sure the crash was after that

 

I had another system lock-up around 4 minutes after the last log. i was unable to access ssh to do any log reporting at all.

 

I tried to gp back to 6.1.9 which lost my array settings. Upgraded again to the beta which got my array back and i am now trying again :) The joys of computers

 

There's a lot that's new to me in these 6.2 syslogs, so not high confidence in any comments I make.  There are some unusual issues with the devices (mouse, keyboard) plugged into the USB 3.0 ports.  Is it possible you have the ports also stubbed out for passthrough?  Two USB handlers and the nVidia card are being treated special in the PCI handling.

 

Your system is far from vanilla, rather close to the 'bleeding edge', lots of relatively new technology, BIOS, kernel, etc.  It's not surprising to see some issues, that hopefully will be better in the future with newer kernels, firmware, BIOS, drivers, and unRAID releases.

Link to comment

Hi RobJ

 

Thanks for your post!

 

For my USB 3 i have 2 usb 3 controllers that are stubbed on boot so i can see them in the vm screen (the 1 per vm). The other usb's are only passed via the  gui. Whilst writing this i had my system go down again (i was installing 2 new vm's and it had been up well over an hour)

 

This time i kept the system in commandline mode and have this on the screen

IMG_20160315_221419.jpg

IMG_20160315_221844.jpg

 

this is still getting updated and keeps saying the same sort of thing

 

I'm unable to see more as i have lost access by ssh etc. so i can't see more. I have never seem this sort of text on my screen before

 

I'm on the bleeding edge for sure so i think it may make me a good test to fix issues that may occur to "regular" users later on

 

Regards,

Jamie

Link to comment

Turn off Intel SpeedStep in the BIOS. "S3" is a power state, might have something to do with it.

 

Also, check for a BIOS update.

 

I have just turned off the Intel SpeedStep, and it seems a new BIOS was released in the last week or so so that is being installed now

 

Just to check, S3 isn't something that is an additional option to the SpeedStep is it?

 

Edit:

Intel speed step is off but the gui still reports: cpu frequency scaling governor as powersave

 

I have disabled all c states as well so there should be no motherboard powers aging kicking on. And I have double checked windows to ensure nothing is going to sleep.

 

It seems to be running better at the moment but only time will tell if those changes were what was needed

Link to comment

 

Is there any reason when creating a vdisk for a VM via the GUI that you are limited to raw and qcow2?  Could not any of the other KVM supported types be listed.  For instance I regularly use .vdi files which seem to provide a good compromise between space and performance and allow me to easily interchange the vdisk files with Virtualbox on my desktop PC.

There is also LVM :-)

 

Other vdisk types may be added in the future.  The reality is that just because KVM "supports" something, doesn't mean that it will necessarily work in all configurations.  We certainly don't want to get dragged down a path of supporting various vdisk types for performance and other issues when raw and qcow2 work well enough for most.

although I can understand there might be support issues if you offered alternative formats via the GUI I would be happy if after using Edit XML to set a VM to use a format such as .vdi subsequent use of the Edit option left such a change intact so I could use it for other settings.

I want edits to be saved too!
Link to comment

I'm trying to install either Ubuntu or Debian server, can't get past this screen, any advice?

 

Here is the XML:

 

<domain type='kvm'>
  <name>Ubuntu</name>
  <uuid>70152094-9d5e-b809-38b8-e1aa103cd8dc</uuid>
  <metadata>
    <vmtemplate xmlns="unraid" name="Ubuntu" icon="ubuntu.png" os="ubuntu"/>
  </metadata>
  <memory unit='KiB'>1048576</memory>
  <currentMemory unit='KiB'>1048576</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>1</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-q35-2.5'>hvm</type>
    <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/70152094-9d5e-b809-38b8-e1aa103cd8dc_VARS-pure-efi.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough'>
    <topology sockets='1' cores='1' threads='1'/>
  </cpu>
  <clock offset='utc'>
    <timer name='rtc' tickpolicy='catchup'/>
    <timer name='pit' tickpolicy='delay'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/local/sbin/qemu</emulator>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/mnt/user/VM/ubuntu-12.04.5-server-i386.iso'/>
      <target dev='hda' bus='sata'/>
      <readonly/>
      <boot order='2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci2'>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <controller type='sata' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pcie-root'/>
    <controller type='pci' index='1' model='dmi-to-pci-bridge'>
      <model name='i82801b11-bridge'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1e' function='0x0'/>
    </controller>
    <controller type='pci' index='2' model='pci-bridge'>
      <model name='pci-bridge'/>
      <target chassisNr='2'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x01' function='0x0'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:04:14:96'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x01' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target port='0'/>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <source mode='connect'/>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'/>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x03' function='0x0'/>
    </memballoon>
  </devices>
</domain>

 

I changed the ISO drive mount from IDE to SATA and that fixed it.

Link to comment

I just upgrad from 6.1 to 6.2beta18, but found below problem

 

1) Boot local GUI not work on Intel B85 motherboard (load bzroot-gui then return to boot menu again ), but no problem with other Z77 motherboard

 

label unRAID OS GUI Mode

  kernel /bzimage

  append initrd=/bzroot,/bzroot-gui

 

2) Above "Syslinux Configuration", press "Default" won't reset to default.

 

3) Spindown all harddisk, GUI show OK, but in fact those drive(s) still Spinup

 

4) "Disk setting" -> "Enable auto start : Yes", but won't auto start.

 

Thnaks

Link to comment

Auto start does not work because the system thinks Parity 2 is missing. Its a known issue and being worked on.

 

it's always worked for me with a single parity.

 

For me it doesn't work as my system skips the auto start due to not being verified quick enough by the unraid server. Using the boot gui I can login and navigate for 30 seconds before I have a valid license

 

Just another reason why it may not work for some. Again I am using single parity

Link to comment

I just upgrad from 6.1 to 6.2beta18, but found below problem

 

1) Boot local GUI not work on Intel B85 motherboard (load bzroot-gui then return to boot menu again ), but no problem with other Z77 motherboard

 

label unRAID OS GUI Mode

  kernel /bzimage

  append initrd=/bzroot,/bzroot-gui

 

2) Above "Syslinux Configuration", press "Default" won't reset to default.

 

3) Spindown all harddisk, GUI show OK, but in fact those drive(s) still Spinup

 

4) "Disk setting" -> "Enable auto start : Yes", but won't auto start.

 

Thnaks

 

For problem (3), seems hdparm just put the harddisk in standby, I try use "-Y" confirm can spindown

 

HDPARM

-y  Put drive in standby mode

-Y  Put drive to sleep

 

 

 

Link to comment

Quick update:

 

We solved the bug with NFS.  NFS is working as expected in the lab.  We also squashed the "parity is valid" Q sync errors that were reported and a number of GUI bugs with VM manager.  Thank you for reporting them.  There are some other issues still outstanding, but we hope to put out another release out soon with as many fixes as we can.

Link to comment

Nope, logs posted before are from a physical install with the usb stick originally on the esxi/internal USB port. Tried all the usb controllers and a different usb.

 

Very odd that no one else is reporting this particular issue and we haven't been able to recreate.  Can you check to see if your motherboard has a BIOS update?  There were some other users in this thread that I think mentioned disabling S3 sleep in the BIOS solved an issue for them.

 

6.2 includes a newer Linux kernel, which may be to blame, but hard to tell because we can't recreate and this is a scenario where no syslog can be collected.

Link to comment

All of a sudden starting getting the following in my log file - this happens with any drive that spins down - any idea on what to look for?

 

Mar 13 21:27:04 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:27:04 Tower kernel: mdcmd (74): spindown 8

 

Here is a force spindown command

 

Mar 13 21:40:28 Tower emhttp: Spinning down all drives...
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: mdcmd: write: No such device or address
Mar 13 21:40:28 Tower emhttp: shcmd (7072): /usr/sbin/hdparm -y /dev/sdd &> /dev/null
Mar 13 21:40:28 Tower kernel: mdcmd (76): spindown 0
Mar 13 21:40:28 Tower kernel: mdcmd (77): spindown 1
Mar 13 21:40:28 Tower kernel: mdcmd (78): spindown 2
Mar 13 21:40:28 Tower kernel: mdcmd (79): spindown 3
Mar 13 21:40:28 Tower kernel: mdcmd (80): spindown 4
Mar 13 21:40:28 Tower kernel: mdcmd (81): spindown 5
Mar 13 21:40:28 Tower kernel: mdcmd (82): spindown 6
Mar 13 21:40:28 Tower kernel: mdcmd (83): spindown 7
Mar 13 21:40:28 Tower kernel: mdcmd (84): spindown 8
Mar 13 21:40:28 Tower kernel: mdcmd (85): spindown 9
Mar 13 21:40:28 Tower kernel: mdcmd (86): spindown 10
Mar 13 21:40:28 Tower kernel: mdcmd (87): spindown 11
Mar 13 21:40:28 Tower kernel: mdcmd (88): spindown 12
Mar 13 21:40:28 Tower kernel: mdcmd (89): spindown 13
Mar 13 21:40:28 Tower kernel: mdcmd (90): spindown 14
Mar 13 21:40:28 Tower kernel: mdcmd (91): spindown 15
Mar 13 21:40:28 Tower kernel: mdcmd (92): spindown 16
Mar 13 21:40:29 Tower emhttp: shcmd (7073): /usr/sbin/hdparm -y /dev/sdc &> /dev/null

 

Thanks

Myk

 

I am receiving these as well when all disks are spun down

 

Same here.. loads of them..

 

I am having the same issue.  What type of drive controller card are you using here?

Link to comment

Yea something very wrong with samba i think, today i was working on my desktop and Windows File History tried to back up the file to my Backup share this worked on 6.1.9 just fine but on 6.2 Unraid webui is not responding and the Openelec VM crashed.

 

If i type in the share into windows explorer it causes the window to not respond i dont understand its as if Windows sees the shares but something is going very wrong and can't connect to it.

 

This time i can't even get the diagnostics

 

and again i can't get the system even to reboot in ssh have to manually power it down.

 

EDIT: some more information

 

Dockers are running during the problem BUT looks like no of them can see the array files, is this a file system problem?

 

EDIT:

so i sshed into Unraid to see if i can see the array files

 

/mnt/user - works, i can see all my share folders

/mnt/user/Tv Shows  works i can see all my tv show folders

/mnt/user/Tv shows/24 works i see the seasons folders

/mnt/user/Tv shows/24/Season 1  Nope when i get into it and type ls it just hangs nothing happens, whats going oN?

 

Edit: after going to eat and coming back Unraid webui responed :) i managed to get a diagnostic file then i checked if the smb shares are working they where up and loading but if i tried to open any file it froze up.

tower-diagnostics-20160316-1322.zip

Link to comment
Guest
This topic is now closed to further replies.