Jump to content
limetech

Unraid OS version 6.7 available

320 posts in this topic Last Reply

Recommended Posts

2 hours ago, Keyko said:

The last release had a problem and with parity check CRC Error appeared in SMART. (CRC Error grew on parity ssd )

Not sure what you mean here?  It was only in the latest releases that Unraid started reporting CRC errors by default so in earlier releases most users were not aware they wee happening unless they explicitly looked for them.

 

Very occasional CRC errors are not a problem, but if they are occurring regularly then there is some sort of hardware issue (typically cable related).   In theory CRC errors by themselves do not produce data loss as the system will retry a transfer if a CRC error is reported and if the retries succeed then the data is safe.  However  even then this will adversely performance as the system can take seconds to finish retrying after a CRC error.  The other issue that some people do not realise is that CRC errors never get reset to zero - they can only either remain stable or continue to increase.

Share this post


Link to post
40 minutes ago, itimpi said:

The other issue that some people do not realise is that CRC errors never get reset to zero - they can only either remain stable or continue to increase

Also, you can acknowledge CRC errors by clicking on them in the Dashboard and you will not be notified again unless they increase.

 

None of this is a problem with a release. It is a hardware problem, often not serious, but still worthy of attention.

Share this post


Link to post
Posted (edited)

...upgraded from 6.5.3.

Array and services are working fine, however waking up via WOL from sleep does not work anymore.

The server goes to sleep fine, but refuses to react to a WOL request from outside, which worked perfectly for the last 300+days of uptime.

 

Is there anything that I missed?

 

Edit2: just checked and the NIC seems to be powered down completely upon sleep...no lights visible from the outside at the connector

 

Edit: Here`s the part of the syslog:

After successful parity check, initiated by the upgrade, the server goes into suspend...after manually pushing the power button, it comes up fine...however, not with an external WOL request

May 19 01:10:19 tank kernel: md: sync done. time=32387sec
May 19 01:10:19 tank kernel: md: recovery thread: exit status: 0
May 19 01:40:20 tank kernel: mdcmd (65): spindown 0
May 19 01:40:21 tank kernel: mdcmd (66): spindown 1
May 19 01:40:21 tank kernel: mdcmd (67): spindown 2
May 19 01:40:22 tank kernel: mdcmd (68): spindown 3
May 19 01:40:22 tank kernel: mdcmd (69): spindown 4
May 19 01:40:22 tank kernel: mdcmd (70): spindown 6
May 19 01:40:23 tank kernel: mdcmd (71): spindown 7
May 19 01:40:24 tank kernel: mdcmd (72): spindown 8
May 19 01:40:25 tank kernel: mdcmd (73): spindown 9
May 19 01:40:25 tank kernel: mdcmd (74): spindown 29
May 19 02:27:22 tank kernel: mdcmd (75): spindown 5
May 19 02:34:53 tank kernel: mdcmd (76): spindown 1
May 19 04:34:55 tank kernel: mdcmd (77): spindown 8
May 19 04:34:56 tank kernel: mdcmd (78): spindown 1
May 19 04:37:13 tank kernel: PM: suspend entry (deep)
May 19 04:37:13 tank kernel: PM: Syncing filesystems ... done.
May 19 11:42:56 tank kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
May 19 11:42:56 tank kernel: OOM killer disabled.
May 19 11:42:56 tank kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
May 19 11:42:56 tank kernel: Suspending console(s) (use no_console_suspend to debug)
May 19 11:42:56 tank kernel: sd 4:0:0:0: [sdm] Synchronizing SCSI cache
May 19 11:42:56 tank kernel: sd 3:0:10:0: [sdl] Synchronizing SCSI cache
May 19 11:42:56 tank kernel: sd 4:0:0:0: [sdm] Stopping disk
May 19 11:42:56 tank kernel: sd 3:0:9:0: [sdk] Synchronizing SCSI cache
May 19 11:42:56 tank kernel: sd 3:0:8:0: [sdj] Synchronizing SCSI cache
May 19 11:42:56 tank kernel: sd 3:0:7:0: [sdi] Synchronizing SCSI cache
May 19 11:42:56 tank kernel: sd 3:0:6:0: [sdh] Synchronizing SCSI cache
May 19 11:42:56 tank kernel: sd 3:0:5:0: [sdg] Synchronizing SCSI cache
May 19 11:42:56 tank kernel: sd 3:0:4:0: [sdf] Synchronizing SCSI cache
May 19 11:42:56 tank kernel: sd 3:0:3:0: [sde] Synchronizing SCSI cache
May 19 11:42:56 tank kernel: sd 3:0:2:0: [sdd] Synchronizing SCSI cache
May 19 11:42:56 tank kernel: sd 3:0:1:0: [sdc] Synchronizing SCSI cache
May 19 11:42:56 tank kernel: sd 3:0:0:0: [sdb] Synchronizing SCSI cache
May 19 11:42:56 tank kernel: mpt2sas_cm0: pdev=0x00000000654ee482, slot=0000:02:00.0, entering operating state [D3]
May 19 11:42:56 tank kernel: mpt2sas_cm0: sending message unit reset !!
May 19 11:42:56 tank kernel: mpt2sas_cm0: message unit reset: SUCCESS
May 19 11:42:56 tank kernel: ACPI: Preparing to enter system sleep state S3
May 19 11:42:56 tank kernel: PM: Saving platform NVS memory
May 19 11:42:56 tank kernel: Disabling non-boot CPUs ...
May 19 11:42:56 tank kernel: smpboot: CPU 1 is now offline
May 19 11:42:56 tank kernel: smpboot: CPU 2 is now offline
May 19 11:42:56 tank kernel: smpboot: CPU 3 is now offline
May 19 11:42:56 tank kernel: ACPI: Low-level resume complete
May 19 11:42:56 tank kernel: PM: Restoring platform NVS memory
May 19 11:42:56 tank kernel: PCI-DMA: Resuming GART IOMMU
May 19 11:42:56 tank kernel: PCI-DMA: Restoring GART aperture settings
May 19 11:42:56 tank kernel: LVT offset 0 assigned for vector 0x400
May 19 11:42:56 tank kernel: microcode: CPU0: new patch_level=0x06000852
May 19 11:42:56 tank kernel: Enabling non-boot CPUs ...
May 19 11:42:56 tank kernel: x86: Booting SMP configuration:
May 19 11:42:56 tank kernel: smpboot: Booting Node 0 Processor 1 APIC 0x11
May 19 11:42:56 tank kernel: cache: parent cpu1 should not be sleeping
May 19 11:42:56 tank kernel: microcode: CPU1: patch_level=0x06000852
May 19 11:42:56 tank kernel: CPU1 is up

 

Edited by Ford Prefect
added syslog messages

Share this post


Link to post

I noticed a small annoyance with 6.7; It says Other when it should say DDR3.

image.thumb.png.69be666670dd925b0e13fae5889fea66.png

Share this post


Link to post
3 hours ago, Mex said:

I noticed a small annoyance with 6.7; It says Other when it should say DDR3.

image.thumb.png.69be666670dd925b0e13fae5889fea66.png

Looks to be a problem with how it is reading your hardware:

 

1443533792_ScreenShot2019-05-19at11_28_21AM.png.64309bbb704731a483aa6a2bb6fa89aa.png103205653_ScreenShot2019-05-19at11_27_41AM.png.d81a6975eb198a275c63ac5ac92af5aa.png

Share this post


Link to post

I found a resolution to the issue I posted here and earlier in this thread

 

if DEBUG is set to "yes" in the domain.cfg then the VMs UI will choke and appears to load forever. Changing this to "no" solved the issue. Still not really sure how that was ever set to "yes" in the first place though... just thought I would share in case anyone else runs into this.

Share this post


Link to post

Upgraded two servers from V6.6.7, went very smoothly, especially compared to 6.5 -> 6.6 in my case. Really like the new dashboard, looks great!

 

Zero issues so far, been running stable for a few days. I still have the following error message in the syslog, but as it doesn't seem cause problems, I have given up trying to look for a fix:

 

kernel: i40e 0000:b5:00.0: Error I40E_AQ_RC_EINVAL adding RX filters on PF, promiscuous mode forced on

 

Share this post


Link to post

Upgraded this morning.  Completely flawless and took all of 5 minutes.

 

My compliments!

Share this post


Link to post

I just upgraded. During the reboot the machine had problems during the BIOS boot and I had to turn it off again. 6.7.0 then reported one disk as "Unmountable: No file system". I am not sure if this is a 6.7.0 problem or maybe a hardware glitch. I have reported it here:

 

Share this post


Link to post

Unfortunately, upgrading from 6.6.7 to 6.7 grenades my unRAID.

In reference to the system in my signature named Yokohama Server, after updating I got something similar to...

 

DMAR:[DMA Read] Request device [04:00.0] fault addr

DMAR:[fault reason 06] PTE Read access is not set

can't find bond device.

 

It assigns the server a completely out of range IP, and the webui isn't even available via the GUI boot option's localhost. Thinking this is an issue with IOMMU based off previous posts, I decided to try rebooting with VT-d disabled in BIOS. Server came right up, no errors in the logs, no issues at all (aside from not being able to passthrough devices to my VMs). I checked with MSI, and they haven't released a new BIOS for this MB since 2018 (already on the current version).

 

I require passthrough on this server, so have had to revert back to 6.6.7

Share this post


Link to post

The upgrade went well on both of my servers. I love that all my Macs are running Time Machine now via SMB.

 

Only (minor) issue is around my APC (APC Smart-UPS SC, 450VA). Some data is missing on the Weg GUI where Grafana/InfluxDB Docker is showing all information available. Please see my screen shots.

Bildschirmfoto 2019-05-21 um 16.51.12.jpg

Bildschirmfoto 2019-05-21 um 16.51.35.jpg

Bildschirmfoto 2019-05-21 um 16.52.08.jpg

Share this post


Link to post

I upgraded from 6.6.7 to 6.7 at the same time I made some other changes, and the system would reliably stop responding within 1 to 8 hours.   One of the other changes was replacing a failing drive and rebuilding the array, so I eventually backed out every other change but that one.  Each time I would bring up the server, it would try and rebuild the replaced drive, but stop responding before it completed.  It wasn't crashing, as the lights were still on, but there was no disk activity.  I tried to rebuild the drive at least 8 times on 6.7, but it never completed.  I finally rolled back to 6.6.7 last night and the rebuild completed and the server is running normally.  There were never any errors reported on 6.7 and one of the rebuilds was with all plugins disabled.  It passed Memtest multiple times, and the VM and docker apps were not running during the rebuild.

 

Here's the build details, the hardware isn't especially new:

 

M/B: ASRock - 970 Extreme4

CPU: AMD FX-8320E

RAM: 16GB DDR3 1600

Case: Norco 4224

Controllers: LSI SAS1068E & SAS2008

Drives: 16 data + dual parity, cache + 2 outside array for docker / vm

Apps: MythTV VM and Plex docker

NICs: onboard  Realtek RTL8111E +  PCIe BCM5721 (bonded), and PCI Intel PRO/1000 (vm)

 

I waited before rolling back as I had initially added another SAS1068E that might be bad and accidentally reset the BIOS settings, but the system hangs continued after correcting both of those.

 

Share this post


Link to post

Well, after reading this thread... I knew I had a Marvell controller on my board, but couldn't recall if any of my drives were using it.

 

So I did

ls -al /sys/block/sd*
lrwxrwxrwx 1 root root 0 May 21 12:17 /sys/block/sda -> ../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/host0/target0:0:0/0:0:0:0/block/sda/
lrwxrwxrwx 1 root root 0 May 21 12:17 /sys/block/sdb -> ../devices/pci0000:00/0000:00:1f.2/ata1/host1/target1:0:0/1:0:0:0/block/sdb/
lrwxrwxrwx 1 root root 0 May 21 12:17 /sys/block/sdc -> ../devices/pci0000:00/0000:00:1f.2/ata2/host2/target2:0:0/2:0:0:0/block/sdc/
lrwxrwxrwx 1 root root 0 May 21 12:17 /sys/block/sdd -> ../devices/pci0000:00/0000:00:1f.2/ata3/host3/target3:0:0/3:0:0:0/block/sdd/
lrwxrwxrwx 1 root root 0 May 21 12:17 /sys/block/sde -> ../devices/pci0000:00/0000:00:1f.2/ata4/host4/target4:0:0/4:0:0:0/block/sde/
lrwxrwxrwx 1 root root 0 May 21 12:17 /sys/block/sdf -> ../devices/pci0000:00/0000:00:1f.2/ata5/host5/target5:0:0/5:0:0:0/block/sdf/
lrwxrwxrwx 1 root root 0 May 21 12:17 /sys/block/sdg -> ../devices/pci0000:00/0000:00:1f.2/ata6/host6/target6:0:0/6:0:0:0/block/sdg/

 

and then I checked which controller they were on:

lspci | grep 1f.2
00:1f.2 SATA controller: Intel Corporation C600/X79 series chipset 6-Port SATA AHCI Controller (rev 06)

looks like I must have known about Marvell issues before, as all my drives are on the Intel controller.  I then proceeded with the upgrade from 6.6.7 to 6.7.0 and everything went smoothly.  Very nice interface enhancements.  Thank you LimeTech.

Share this post


Link to post
On 5/11/2019 at 7:14 AM, limetech said:

You can plug your USB flash device into a PC and then make a backup (just drag contents to a temp folder on your desktop).

Next use the USB Creator Tool to re-install Unraid OS on your flash.  You can put the last version you were running, or try 6.7 again.

Then copy the contents of your 'config' folder backup to the USB flash 'config' folder.  If you had any custom 'syslinux' settings, you could restore that too.

Eject flash, reboot server and 'should work' 👍

 

After the update I couldn't connect to the webUI, even in GUI mode I had no connection to localhost!

But after this reinstall it worked

Share this post


Link to post

Updated three servers, no issues. New BIND method working seemingly perfectly vs stubbing.

Share this post


Link to post
6 hours ago, jbartlett said:

Updated three servers, no issues. New BIND method working seemingly perfectly vs stubbing.

You going to add to your Alpha runbook? 🙂

Share this post


Link to post

Upgraded from 6.6.1 to 6.7 and haven't noticed any major issues. I did notice one minor UI issue, with the name of the HomeBridgewithwebGUI name being partially covered.

 

 

unraid_667_main_docker_overlap.png

Share this post


Link to post
2 hours ago, RParkerMU said:

the HomeBridgewithwebGUI name being partially covered.

 

It's an unusually long name. Can't you simply edit it to make it shorter? "HomeBridge-GUI" would surely fit.

Share this post


Link to post
Posted (edited)
3 hours ago, RParkerMU said:

Upgraded from 6.6.1 to 6.7 and haven't noticed any major issues. I did notice one minor UI issue, with the name of the HomeBridgewithwebGUI name being partially covered.

 

 

unraid_667_main_docker_overlap.png

Real long names are now being truncated to avoid overlapping. It's in the change log:

 

webgui: Dashboard: fixed wrapping of long lines

webgui: Dashboard: wrap long descriptions

image.png.0f1dda98dcf9a7bf0d4a929289389043.png

Edited by cybrnook

Share this post


Link to post
Posted (edited)

Upgraded all three of my servers and there is only one small hiccup.

Generally speaking, the upgrades were done in under five minutes and worked flawlessly!

I really like the new GUI's!!! 👏

 

****************************************************

Moved To General Support

 

As for the hiccup...

I have this video card in Server ONE: IOMMU group 45:[1002:94c3] 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO]

In Server TWO I have: [102b:0532]05:03.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 (rev 0a).

I also use this four-port KVM from Rosewill https://www.amazon.com/gp/product/B004B0H5R6/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

 

I used to be able to cycle through the three servers displays no problem, if and only if, the server was being displayed on the monitor during boot. So, boot server with display running/selected, no problems. Now though, if I try to cycle through the displays, they are gone. Again, boot and you have video: so, boot server ONE with display, good video. Change to server TWO, boot with display, good video. Go back to server ONE and video is gone, try to move back to server TWO, video now gone, same for Server THREE. (Also, if I just turn the monitor off, the same thing happens, video is gone regardless of server selected)

 

Interestingly, this used to only be an issue with server ONE and was simply an annoyance; just never got around to bringing it up here. Now though, this presents a problem as I have had times where the web GUI stopped responding and that keyboard and display saved my bacon.

 

I am only at the discovery stage, so if anyone has troubleshooting ideas, let me know; I would appreciate it.

*********************************************************

 

GREAT job on the new release!!! Kudos LimeTech Team! 👍

Edited by TechMed
Moved Issue To General Support

Share this post


Link to post

I just successfully upgraded from 6.6.7 to 6.7 with 3 vm's with multiple NIC's passed-through and approx 20 dockers. THANK YOU!

Sent from my SM-N960U using Tapatalk

Share this post


Link to post
Posted (edited)
On 5/23/2019 at 7:09 AM, TechMed said:

Upgraded all three of my servers and there is only one small hiccup.

Generally speaking, the upgrades were done in under five minutes and worked flawlessly!

I really like the new GUI's!!! 👏

 

As for the hiccup...

I have this video card in Server ONE: IOMMU group 45:[1002:94c3] 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO]

In Server TWO I have: [102b:0532]05:03.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 (rev 0a).

I also use this four-port KVM from Rosewill https://www.amazon.com/gp/product/B004B0H5R6/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1

 

I used to be able to cycle through the three servers displays no problem, if and only if, the server was being displayed on the monitor during boot. So, boot server with display running/selected, no problems. Now though, if I try to cycle through the displays, they are gone. Again, boot and you have video: so, boot server ONE with display, good video. Change to server TWO, boot with display, good video. Go back to server ONE and video is gone, try to move back to server TWO, video now gone, same for Server THREE. (Also, if I just turn the monitor off, the same thing happens, video is gone regardless of server selected)

 

Interestingly, this used to only be an issue with server ONE and was simply an annoyance; just never got around to bringing it up here. Now though, this presents a problem as I have had times where the web GUI stopped responding and that keyboard and display saved my bacon.

 

I am only at the discovery stage, so if anyone has troubleshooting ideas, let me know; I would appreciate it.

 

GREAT job on the new release!!! Kudos LimeTech Team! 👍

not sure if this it it, but somewhen in the RC cycle there was a change so that displays got black after awhile of uptime – it was intentional as protection against burn-in (i guess, or...). catched me once, but a keypress wakes the screen.

Edited by s.Oliver

Share this post


Link to post

Geeez!

Well for heaven's sake... why didn't I think of that?

Worked like a charm!

Thanks!

Have a great weekend!

Share this post


Link to post

I upgraded from 6.6.7 to 6.7 and now the docker doesn’t update, it can’t find a network, it wants me to change the DNS of the router to 8.8.8.8 when ever I roll it back to 6.6.7 it works perfectly with my routers config, someone said the problem was with the network.cfg file where do I find this to alter it so I can actually update to 6.7 help please

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.