Jump to content
limetech

unRAID OS version 6.3.1 Stable Release Available

175 posts in this topic Last Reply

Recommended Posts

Download

 

Clicking 'Check for Updates' on the Plugins page is the preferred way to upgrade.

 

This is mainly a bug fix release:

- permit NTLMv1 authentication to restore connectivity to private shares for older clients

- fix issue preventing new slot assignments

- other small fixes, see below.

 

Please also read the unRAID OS version 6 Upgrade Notes for answers to common issues that may arise following upgrade.

 


 

unRAID OS 6.3 is an extensive security and package update release.  In particular, we have made numerous changes to harden the unRAID OS webGui against XSS and CSRF vulnerabilities.

 

PREVIOUS unRAID OS RELEASES ARE VULNERABLE TO CSRF/XSS ATTACK AND WE STRONGLY RECOMMEND ALL USERS UPGRADE TO 6.3

 

Plugin Authors: as posted earlier, your plugin may not function properly depending how how POST requests are handled, see:

http://lime-technology.com/forum/index.php?topic=55986.0

 

Plugin Users: please post issues you find in the appropriate Plugin Support topic.

 

And to reiterate: true plugins (not Docker containers) run as the

root

user and have full access to everything on your server: Install 3rd party plugins at your own risk.

 

Bugs: As always, if you are reporting a bug new in this release, please attach your diagnostics.zip file downloaded via Tools/Diagnostics

 


 

unRAID Server OS Change Log
===========================

Version 6.3.1 2017-02-08
------------------------

Base distro:

- apcupsd: version 3.14.14 (rev2 -- added modbus usb support)
- gd: version 2.2.4 (CVE-2016-9317, CVE-2016-6912)
- libusb-compat: version 0.1.5
- qemu: version 2.7.1
- samba: version 4.5.5

Linux kernel:

- version 4.9.8

Management:

- emhttp: fixed spurious "ioctl(SIOCGIFHWADDR): Bad address" appearing on Console
- smb: permit NTLMv1 authentication
- webGui: Add lsusb info to diagnostics
- webGui: Fix regression assigning slots and devices
- webGui: Fix regression generating SMART files for diagnostics

Version 6.3.0 2017-02-02
------------------------

Management:

- emhttp: added 'svcs_restarting' event
- emhttp: include "vfs objects =" line for each share named in generated /etc/samba/smb-shared.conf file
- webGui: Fix regression changing display banner
- webGui: Fix regression with 'Compute All' on Share page

Version 6.3.0-rc9 2017-01-27
----------------------------

Base distro:

- add pv: version 1.6.0
- docker: version 1.12.6 (CVE-2016-9962)
- containerd: version 0.2.5
- glibc-zoneinfo: version 2016j
- gnutls: version 3.5.8 (CVE-2017-5334, CVE-2017-5335, CVE-2017-5336, CVE-2017-5337)
- libpng: version 1.6.27 (CVE-2016-10087)
- mozilla-firefox: version 51.0 (CVE-2017-5375, CVE-2017-5376, CVE-2017-5377, CVE-2017-5378, CVE-2017-5379, CVE-2017-5380, CVE-2017-5390, CVE-2017-5389, CVE-2017-5396, CVE-2017-5381, CVE-2017-5382, CVE-2017-5383, CVE-2017-5384, CVE-2017-5385, CVE-2017-5386, CVE-2017-5394, CVE-2017-5391, CVE-2017-5392, CVE-2017-5393, CVE-2017-5395, CVE-2017-5387, CVE-2017-5388, CVE-2017-5374, CVE-2017-5373)
- openssh: version 7.4p1 (CVE-2016-10009, CVE-2016-10010, CVE-2016-10011, CVE-2016-10012)
- php: version 7.0.15 (CVE-2016-10161, CVE-2016-10162, CVE-2017-5340, CVE-2016-7479, CVE-2016-10158, CVE-2016-10160, CVE-2016-10159)
- samba: version 4.5.3 (CVE-2016-2123, CVE-2016-2125, CVE-2016-2126)
- update hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt}

Linux kernel:

- version 4.9.6
- added CONFIG_DRM_I915: Intel 8xx/9xx/G3x/G4x/HD Graphics (but blacklisted to prevent auto-load)

Management:

- libvirt: disable nested virtualizaton by default
- shfs: correct return value of system.LOCATION extended attribute to eliminate bash "warning: command substitution: ignored null byte in input"
- webGui: Add BTRFS file system checking notifications
- webGui: Avoid wget to cache plugin files and postpone plugin updates
- webGui: Capitalize method name in plugin operations.
- webGui: Natural sorting of user share names
- webGui: Save docker, VM and libvirt logs as .txt files in diagnostics
- webGui: Disable filesystem selection when data-rebuild is pending
- webGui: Add cache pool BTRFS info (if existing) to diagnostics
- webGui: added new Europe/Saratov timezone
- webGui: additional XSS and CSRF hardening

Version 6.3.0-rc6 2016-12-07
----------------------------

Base distro:

- inotify-tools: version 3.14
- mozilla-firefox: version 50.0.2 (CVE-2016-9078, CVE-2016-9079)
- ntfs-3g: version 2016.2.22
- rsyslog: version 8.23.0

Linux kernel:

- version 4.8.12 (CVE-2016-8650)

Management:

- network: must set forwarding delay before setting stp 'on'; need 1 sec delay between stop/start in restart
- samba: move OS X "vfs_fruit" optimization from 'global' to individual share settings
- shutdown: increase default shutdown delay from 60 to 90 sec; eliminate extraneous console messages
- update: hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt} smartmontools/drivedb.h
- webGui: add Hibernate option to VM context menu

Version 6.3.0-rc5 2016-11-25
----------------------------

Base distro:

- bash: version 4.4.005
- grep: version 2.26 (rev2)
- kernel-firmware: version 20161118git
- libvirt: version 2.4.0
- mozilla-firefox: version 50.0
- ntp: version 4.2.8p9 (CVE-2016-9311, CVE-2016-9310, CVE-2016-7427, CVE-2016-7428, CVE-2016-9312, CVE-2016-7431, CVE-2016-7434, CVE-2016-7429, CVE-2016-7426, CVE-2016-7433)

Linux kernel:

- version 4.8.10 (CVE-2016-7039)

Management:

- add btrfs_check script to facilitate btrfs file system check
- bug fix: firefox correctly connects to emhttp port number
- samba: include OS X vfs_fruit optimizations by default
- shutdown: bug fix: overall shutdown timeout read from wrong cfg file
- shutdown: bug fix: saving shutdown timeout value
- shutdown: add config setting for overall VM shutdown timeout
- update: hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt} smartmontools/drivedb.h
- webGui: add filesystem Check for btrfs volumes in Maintenance mode
- webGui: add vm shutdown time-out option
- webGui: generate VM xml with cpu topology as single-threaded when host cpu is AMD
- webGui: special text aside new disks to clear
- webGui: split out Europe/Istanbul as its own timezone

Other:

- make_bootable_linux: use readlink instead of realpath since it is more compatible

Version 6.3.0-rc4 2016-11-11
----------------------------

Base distro:

- curl: version 7.51.0 (CVE-2016-8615, CVE-2016-8616, CVE-2016-8617, CVE-2016-8618, CVE-2016-8619, CVE-2016-8620, CVE-2016-8621, CVE-2016-8622, CVE-2016-8623, CVE-2016-8624, CVE-2016-8625)
- docker: version 1.12.3 (CVE-2016-8867)
- glibc-zoneinfo: version 2016i
- grep: version 2.26
- kernel-firmware: version 20161001git
- libusb: version 1.0.21
- libX11: version 1.6.4 (CVE-2016-7942, CVE-2016-7943)
- libXfixes: version 5.0.3 (CVE-2016-7944)
- libXi: version 1.7.8 (CVE-2016-7945, CVE-2016-7946)
- libXrandr: version 1.5.1 (CVE-2016-7947, CVE-2016-7948)
- libXrender: version 0.9.10 (CVE-2016-7949, CVE-2016-7950)
- libXtst: version 1.2.3 (CVE-2016-7951, CVE-2016-7952)
- libXv: version 1.0.11 (CVE-2016-5407)
- lvm2: version 2.02.166
- mozilla-firefox: version 49.0.2
- mpfr: version 3.1.5
- nano: version 2.7.1
- php: version 7.0.13
- samba: version 4.5.1

Linux kernel:

- version 4.8.7 (CVE-2016-7042, CVE-2016-8630, CVE-2016-8633)
- md/unraid version: 2.7.1
  - make the 'check' command "correct"/"nocorrect" argument case insensitive
  - mark superblock 'clean' upon initialization

Management:

- emhttp: add API command cmdStopMover and API status variable shareMoverActive (yes/no)
- emhttp: ensure disk shares have proper permissions set even if not being exported
- emhttp: fix detecton of unclean shutdown to trigger automatic parity check upon Start if necessary
- emhttp: fix mac address not set in avahi afp share advertisement (regression introduced in -rc2)
- emhttp: unmount docker/libvirt loopback if docker/libvirt fail to start properly
- mover: add start/stop/status subcommands (experimental)
- mover: dereference files on user shares to get st_dev/st_ino instead of from shfs stat structure
- shfs: eliminate 'use_ino' option dependency (fixes NFS issue on buggy clients)
- update: hwdata/{pci.ids,usb.ids,oui.txt,manuf.txt} smartmontools/drivedb.h
- webGui: combine PCI Devices and IOMMU Groups on Sysdev page; Sort IOMMU and USB Devices properly
- webGui: correct button positions on confirmation dialogs
- webGui: correct handling of unclean shutdown detection
- webGui: fixed device passthrough for Docker
- webGui: fixed Docker/VMs tab stay visible when array is stopped
- webGui: fixed some help text typos
- webGui: update to font-awesome 4.7.0

Version 6.3.0-rc3 2016-10-22
----------------------------

Linux kernel:

- version 4.8.4 (CVE-2016-5195)

Management:

- shutdown: additional logging in event of cmdStop timeout

Version 6.3.0-rc2 2016-10-19
----------------------------

Base distro:

- docker: version 1.12.2
- containerd: version 0.2.4
- runc: version 1.0.0_rc2
- libseccomp: version 2.3.1
- libvirt-php: 0.5.2 (+ latest from git)
- php: version 7.0.12
- usbredir: version 0.7.1
- spice: version 0.12.8
- spice-protocol: version 0.12.12
- imlib2: version 1.4.9
- gd: version 2.2.3
- rsyslog: version 8.22.0
- libfastjson: version 0.99.4
- reverted OVMF firmware back to the version in 6.2 due to user reported issues

Linux kernel:

- version 4.8.2
- r750: version 1.2.10-16_10_13
- md/unraid: kernel 4.8 API changes; support FUA and SYNC write operation flags

Management:

- bug fix: Samba listening on the wrong interface in a VLAN-enable config
- emhttp: added starting/stopping docker/libvirt events
- emhttp: removed 'reboot', 'shutdown', 'changeNetwork' API calls; eliminated emhttp-managed network vars
- shutdown: save diagnostics in event of cmdStop timeout
- vm manager: add 'virtio-win-0.1.126-2' and 'virtio-win-0.1.126-1' to VirtIO-ISOs list
- webGui: Added "Join" notification agent
- webGui: Add support for "Notify My Android" notifications
- webGui: Fixed: Windows unable to extract diagnostics zip file
- webGui: Increased password length to 128 characters
- webGui: Interactive Reboot and Shutdown directly invokes '/sbin/reboot' and '/sbin/poweroff'

Version 6.3.0-rc1 2016-10-05
----------------------------

Base distro (primary packages):

- btrfs-progs: version v4.7.2
- netatalk: version 3.1.10
- openssl: version 1.0.2j
- php: version 5.6.26
- qemu: version 2.7.0
- samba: version 4.5.0

Base distro (secondary packages):

- apcupsd: version 3.14.14
- bash: version 4.4.0
- curl: version 7.50.3
- diffutils: version 3.5
- e2fsprogs: version 1.43.3
- etc: version 14.2
- file: version 5.28
- fuse: version 2.9.7
- gawk: version 4.1.4
- gdbm: version 1.12
- glib2: version 2.46.2
- glibc: version 2.24
- glibc: version zoneinfo
- glibc-solibs: version 2.24
- gnutls: version 3.4.15
- jemalloc: version 4.2.1
- kmod: version 23
- libtasn1: version 4.9
- libxml2: version 2.9.4
- lvm2: version 2.02.161
- nano: version 2.7.0
- network-scripts: version 14.2
- nfs-utils: version 1.3.4
- openssl-solibs version: 1.0.2j
- pkgtools-14.2-noarch: version 13
- reiserfsprogs: version 3.6.25
- util-linux: version 2.28.2

Base distro (desktop GUI packages):

- freetype: version 2.6.5
- harfbuzz: version 1.3.0
- libXfont: version 1.5.2
- mesa: version 12.0.2
- mozilla-firefox: version 49.0.1
- xkeyboard-config: version 2.18
- xorg-server: version 1.18.4

Linux kernel:

- version 4.7.6
- aacraid: version 1.2.1-52011
- intel 10Gbit ethernet: revert to in-tree drivers
- r750: version 1.2.9-16_09_27
- md/unraid: Fix bug where case of no data disks improperly detected.

Management:

- bug fix: For file system type "auto", only attempt btrfs,xfs,reiserfs mounts.
- bug fix: For docker.img and libvirt.img, if path on /mnt/ check for mountpoint on any subdir component
- bug fix: During shutdown force continue if array stop taking too long.
- bug fix: Handle case in 'mover' where rsync may move a file but also return error status.
- webGui: Add "Shutdown time-out" control on Disk Settings page.
- webGui: bug fix: Cannot manually specify virtIO iso in VM settings
- webGui: other changes: refer to github commit log

Share this post


Link to post

I realise there were much more pressing problems in 6.3.0 that needed fixing, but this minor one is still present in 6.3.1.

 

confirm that & is no problem in folder names for the unraid share browser on 6.2.4 (have yet to upgrade).

 

examples:

/mnt/user/TV/TV-Food & Travel/

/mnt/user/Media/Certification & Test/Cisco

Share this post


Link to post

Reboot (webgui power button top right) at the end of the update process via Plug-ins, gives me text top left of page: 404 NOT FOUND.

 

I think I usually got a temp page with yellow band across the top?

Share this post


Link to post

Reboot (webgui power button top right) at the end of the update process via Plug-ins, gives me text top left of page: 404 NOT FOUND.

 

I think I usually got a temp page with yellow band across the top?

 

bonienl needs to update the system buttons plugin.

Share this post


Link to post

Just upgraded from 6.2.4 to 6.3.1, my VM now gets an 'Execution error'

 

internal error: process exited while connecting to monitor: 2017-02-08T23:57:09.643822Z qemu-system-x86_64: -machine pc-q35-2.3,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off: unsupported machine type
Use -machine help to list supported machines

 

Here is the XML file of it.

 

<domain type='kvm'>
  <name>ubuntu-server</name>
  <uuid>dccdd050-89bc-6f12-491b-86f2872ca517</uuid>
  <description>Ubuntu Server</description>
  <metadata/>
  <memory unit='KiB'>8388608</memory>
  <currentMemory unit='KiB'>8388608</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>2</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='1'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-q35-2.3'>hvm</type>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough'>
    <topology sockets='1' cores='2' 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/bin/qemu-system-x86_64</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/cache/virtual-machines/ubuntu-server/vdisk1.img'/>
      <target dev='hdb' bus='virtio'/>
      <boot order='1'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x04' function='0x0'/>
    </disk>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x02' function='0x0' multifunction='on'/>
    </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='0x03' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:a2:f3:28'/>
      <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'>
      <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='vmvga' vram='16384' heads='1' primary='yes'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x05' function='0x0'/>
    </memballoon>
  </devices>
</domain>

 

Any input would be greatly appreciated.

 

EDIT:

 

I'm an idiot for not reading the notes:

https://lime-technology.com/wiki/index.php/UnRAID_OS_version_6_Upgrade_Notes

 

Hopefully didn't waste anyones time here!

Share this post


Link to post

Just upgraded from 6.2.4 to 6.3.1, my VM now gets an 'Execution error'

...

 

Replace:

<os>
    <type arch='x86_64' machine='pc-q35-2.3'>hvm</type>
  </os>

 

with:

<os>
    <type arch='x86_64' machine='pc-q35-2.7'>hvm</type>
  </os>

Share this post


Link to post

Just upgraded from 6.2.4 to 6.3.1, my VM now gets an 'Execution error'

...

 

Replace:

<os>
    <type arch='x86_64' machine='pc-q35-2.3'>hvm</type>
  </os>

 

with:

<os>
    <type arch='x86_64' machine='pc-q35-2.7'>hvm</type>
  </os>

 

Just hit EDIT and then Save per the notes here:

https://lime-technology.com/wiki/index.php/UnRAID_OS_version_6_Upgrade_Notes

 

And things are working as expected (although it changed me to i440fx from q35, however I don't think that matters to me much).

 

Ogi

Share this post


Link to post

Just noticed that my spin-down button on the main screen now tries to spin down the cache drive? whereas this used to only do up-to but not including cache drive assignment.

 

Cheers,

Share this post


Link to post

i just upgraded from v6.2.4 and it looked like it went normally but when i looked at the logs i started seeing some floppy errors, kinda strange since i don't have any floppy drive in the system. i removed all the plugins and shutdown the plex docker but it still keeps putting the following very minute:

 

Feb 8 19:09:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:09:01 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:10:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:10:01 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:11:02 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:11:02 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:12:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:12:01 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:13:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:13:01 NAS kernel: floppy: error -5 while reading block 0

 

i have attached the syslog, any suggestions on how to fix?

 

thanks

James

nas-syslog-20170208-1915.zip

Share this post


Link to post

i just upgraded from v6.2.4 and it looked like it went normally but when i looked at the logs i started seeing some floppy errors, kinda strange since i don't have any floppy drive in the system. i removed all the plugins and shutdown the plex docker but it still keeps putting the following very minute:

 

Feb 8 19:09:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:09:01 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:10:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:10:01 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:11:02 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:11:02 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:12:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:12:01 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:13:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:13:01 NAS kernel: floppy: error -5 while reading block 0

 

i have attached the syslog, any suggestions on how to fix?

 

thanks

James

Are you running unRAID on bare metal or as a VM under another hypervisor?

 

Sent from my SM-G930P using Tapatalk

 

 

Share this post


Link to post

i just upgraded from v6.2.4 and it looked like it went normally but when i looked at the logs i started seeing some floppy errors, kinda strange since i don't have any floppy drive in the system. i removed all the plugins and shutdown the plex docker but it still keeps putting the following very minute:

 

Feb 8 19:09:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:09:01 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:10:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:10:01 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:11:02 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:11:02 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:12:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:12:01 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:13:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:13:01 NAS kernel: floppy: error -5 while reading block 0

 

i have attached the syslog, any suggestions on how to fix?

 

thanks

James

Are you running unRAID on bare metal or as a VM under another hypervisor?

 

Sent from my SM-G930P using Tapatalk

 

it is running as a vm under vmware esxi v6.

 

Share this post


Link to post

i just upgraded from v6.2.4 and it looked like it went normally but when i looked at the logs i started seeing some floppy errors, kinda strange since i don't have any floppy drive in the system. i removed all the plugins and shutdown the plex docker but it still keeps putting the following very minute:

 

Feb 8 19:09:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:09:01 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:10:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:10:01 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:11:02 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:11:02 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:12:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:12:01 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:13:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:13:01 NAS kernel: floppy: error -5 while reading block 0

 

i have attached the syslog, any suggestions on how to fix?

 

thanks

James

Are you running unRAID on bare metal or as a VM under another hypervisor?

 

Sent from my SM-G930P using Tapatalk

 

it is running as a vm under vmware esxi v6.

Then this is an issue with VMware presenting a virtual floppy disk. This doesn't appear on bare metal.

 

Sent from my SM-G930P using Tapatalk

 

 

Share this post


Link to post

Just updated to 6.3.1 and Docker is broken on my system:

 

  • Settings -> Docker, Enable Docker is set to Yes but Status still shows as Stopped.
  • Going to the Docker tab all I get is the header and tabs. Under that is completely white
  • Dashboard under Apps shows "No apps available to show"
  • Dashboard under System Status, Docker is shown as "Not available"

 

I downloaded 6.3.1 again and copied over to my boot thumbdrive and removed all plugins but no change in result.

 

Any ideas?

 

Share this post


Link to post

i just upgraded from v6.2.4 and it looked like it went normally but when i looked at the logs i started seeing some floppy errors, kinda strange since i don't have any floppy drive in the system. i removed all the plugins and shutdown the plex docker but it still keeps putting the following very minute:

 

Feb 8 19:09:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:09:01 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:10:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:10:01 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:11:02 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:11:02 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:12:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:12:01 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:13:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:13:01 NAS kernel: floppy: error -5 while reading block 0

 

i have attached the syslog, any suggestions on how to fix?

 

thanks

James

Are you running unRAID on bare metal or as a VM under another hypervisor?

 

Sent from my SM-G930P using Tapatalk

 

it is running as a vm under vmware esxi v6.

Then this is an issue with VMware presenting a virtual floppy disk. This doesn't appear on bare metal.

 

Sent from my SM-G930P using Tapatalk

 

this was never a problem with 6.2.4 and i just looked over the settings of the vm and there is no virtual floppy in any of the settings (see attached pic).

VM-Settings.jpg.163b577406ac18c4d02431b12d8a174c.jpg

Share this post


Link to post

i just upgraded from v6.2.4 and it looked like it went normally but when i looked at the logs i started seeing some floppy errors, kinda strange since i don't have any floppy drive in the system. i removed all the plugins and shutdown the plex docker but it still keeps putting the following very minute:

 

Feb 8 19:09:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:09:01 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:10:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:10:01 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:11:02 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:11:02 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:12:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:12:01 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:13:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:13:01 NAS kernel: floppy: error -5 while reading block 0

 

i have attached the syslog, any suggestions on how to fix?

 

thanks

James

Are you running unRAID on bare metal or as a VM under another hypervisor?

 

Sent from my SM-G930P using Tapatalk

 

it is running as a vm under vmware esxi v6.

Then this is an issue with VMware presenting a virtual floppy disk. This doesn't appear on bare metal.

 

Sent from my SM-G930P using Tapatalk

 

this was never a problem with 6.2.4 and i just looked over the settings of the vm and there is no virtual floppy in any of the settings (see attached pic).

 

Try removing the SIO Controller.  It's main function is to control the virtual floppy.

 

 

Share this post


Link to post

i just upgraded from v6.2.4 and it looked like it went normally but when i looked at the logs i started seeing some floppy errors, kinda strange since i don't have any floppy drive in the system. i removed all the plugins and shutdown the plex docker but it still keeps putting the following very minute:

 

Feb 8 19:09:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:09:01 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:10:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:10:01 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:11:02 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:11:02 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:12:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:12:01 NAS kernel: floppy: error -5 while reading block 0

Feb 8 19:13:01 NAS kernel: blk_update_request: I/O error, dev fd0, sector 0

Feb 8 19:13:01 NAS kernel: floppy: error -5 while reading block 0

 

i have attached the syslog, any suggestions on how to fix?

 

thanks

James

Are you running unRAID on bare metal or as a VM under another hypervisor?

 

Sent from my SM-G930P using Tapatalk

 

it is running as a vm under vmware esxi v6.

Then this is an issue with VMware presenting a virtual floppy disk. This doesn't appear on bare metal.

 

Sent from my SM-G930P using Tapatalk

 

this was never a problem with 6.2.4 and i just looked over the settings of the vm and there is no virtual floppy in any of the settings (see attached pic).

 

Try removing the SIO Controller.  It's main function is to control the virtual floppy.

 

i tried to remove that SIO controller but is not removable so after a little more digging i did find out that in the bios setting of the vm there was the floppy disk that was enabled so i disabled that and it is all good now. thanks for your help..

 

 

Share this post


Link to post

plugin: updating: unRAIDServer.plg

Warning: file_put_contents(): Only 0 of 1822 bytes written, possibly out of free disk space in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 297
plugin: unable to create file: /tmp/unRAIDServer.sh

 

I am getting this error

 

LUCrQqM.jpg

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.