unRAID OS version 6.3.1 Stable Release Available


limetech

Recommended Posts

Upgraded from 6.2.4 to 6.3.1 and see today i can't create files that beginning with  "._" (dot and underscore) on Unraid Shares.

 

I see it first after a backup from Windows to Unraid with Syncbackfree => i have errors on every file beginnig with "._".

 

Is it a bug in 6.3.1 upgrade?

 

Thanks for help.

Fred.

 

That's another side effect of enabling OS X "vfs_fruit" optimizations.  We will provide a share-by-share control for this in 6.3.2.

Link to comment
  • Replies 174
  • Created
  • Last Reply

Top Posters In This Topic

I've lost audio on my 'Disney' VM - sure this coincided with the 6.3.1 update.

 

 

I've got a yellow exclamation against 'High Definition Audio Bus' in device manager.  No problems since day 1 with unRAID (September) with this VM before.

 

 

 

 

It's my primary card so I was going to see if stubbing it helped, but I can't get the device details even if I do

 

 

lspci -nn

 

 

as this is what I see:

01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] [1002:6779]
01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Caicos HDMI Audio [Radeon HD 6450 / 7450/8450/8490 OEM / R5 230/235/235
X OEM] [1002:a...

 

Hi DZMM,

 

I'm going to send you a PM in a minute here.  What I'd like to do is give you a coupon code for a free services session that you can schedule with us so I can take a closer look at your system using a remote connection.  We haven't experienced the issue you're having and so far, it appears you're the only one experiencing this, but I'd like to get hands on to experiment a bit further.

 

THIS. How do I like THIS post????

Link to comment

Upgraded from 6.2.4 to 6.3.1 and see today i can't create files that beginning with  "._" (dot and underscore) on Unraid Shares.

 

I see it first after a backup from Windows to Unraid with Syncbackfree => i have errors on every file beginnig with "._".

 

Is it a bug in 6.3.1 upgrade?

 

Thanks for help.

Fred.

 

That's another side effect of enabling OS X "vfs_fruit" optimizations.  We will provide a share-by-share control for this in 6.3.2.

Ok, good to know it's not a problem on my Server.  :)

Link to comment

After some digging up, I managed to "fix" it with manual adding "nordirplus" on nfs export options:

 

"/mnt/user/media" -async,no_subtree_check,fsid=100,nordirplus *(sec=sys,rw,insecure,anongid=100,anonuid=99,all_squash)

 

Where did you dig?

 

:P Was looking today to my browser history and can't find where. The fact is with disabling nfs3 READDIRPLUS resolves my issue. It was something related with kodi/xbmc nfs implementation on windows not supporting 64 inodes. Can't find the page I saw supporting it.

Link to comment

So just updated one tower from 6.2.4 to 6.3.1.

 

Everything went find except I no longer see all network interfaces.

 

Both servers have the onboard NIC, and then a quad port nic.

 

6.2.4 is still fine.

 

On 6.3.1 I see eth0, eth1, and then eth118.

 

I had to unplug the last two connections else I would drop pings.

 

I never had an issue before connecting 5 x 1 Gbe through the LAG on my switch.  I would see all 5 interfaces come up.

 

Working tower on 6.2.4:

 

root@Tower:~# dmesg | grep eth

[    9.573807] tg3 0000:08:00.0 eth0: Tigon3 [partno(BCM57781) rev 57785100] (PCI Express) MAC address bc:5f:f4:87:19:e6

[    9.573892] tg3 0000:08:00.0 eth0: attached PHY is 57765 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])

[    9.574016] tg3 0000:08:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]

[    9.574068] tg3 0000:08:00.0 eth0: dma_rwctrl[00000001] dma_mask[64-bit]

[    9.765278] igb 0000:03:00.0: eth1: (PCIe:2.5Gb/s:Width x4) 00:1b:21:42:8a:08

[    9.765340] igb 0000:03:00.0: eth1: PBA No: Unknown

[    9.953454] igb 0000:03:00.1: eth2: (PCIe:2.5Gb/s:Width x4) 00:1b:21:42:8a:09

[    9.953521] igb 0000:03:00.1: eth2: PBA No: Unknown

[  10.159261] igb 0000:04:00.0: eth3: (PCIe:2.5Gb/s:Width x4) 00:1b:21:42:8a:0c

[  10.159334] igb 0000:04:00.0: eth3: PBA No: Unknown

[  10.365182] igb 0000:04:00.1: eth4: (PCIe:2.5Gb/s:Width x4) 00:1b:21:42:8a:0d

[  10.365232] igb 0000:04:00.1: eth4: PBA No: Unknown

[  20.042353] tg3 0000:08:00.0 eth0: Tigon3 [partno(BCM57781) rev 57785100] (PCI Express) MAC address bc:5f:f4:87:19:e6

[  20.042358] tg3 0000:08:00.0 eth0: attached PHY is 57765 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])

[  20.042361] tg3 0000:08:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]

[  20.042364] tg3 0000:08:00.0 eth0: dma_rwctrl[00000001] dma_mask[64-bit]

[  20.252389] igb 0000:03:00.0: eth1: (PCIe:2.5Gb/s:Width x4) 00:1b:21:42:8a:08

[  20.252393] igb 0000:03:00.0: eth1: PBA No: Unknown

[  20.459400] igb 0000:03:00.1: eth2: (PCIe:2.5Gb/s:Width x4) 00:1b:21:42:8a:09

[  20.459404] igb 0000:03:00.1: eth2: PBA No: Unknown

[  20.656405] igb 0000:04:00.0: eth3: (PCIe:2.5Gb/s:Width x4) 00:1b:21:42:8a:0c

[  20.656409] igb 0000:04:00.0: eth3: PBA No: Unknown

[  20.853399] igb 0000:04:00.1: eth4: (PCIe:2.5Gb/s:Width x4) 00:1b:21:42:8a:0d

[  20.853403] igb 0000:04:00.1: eth4: PBA No: Unknown

[  21.518242] bond0: Enslaving eth0 as an active interface with a down link

[  21.769348] 8021q: adding VLAN 0 to HW filter on device eth1

[  21.769559] bond0: Enslaving eth1 as an active interface with a down link

[  22.022354] 8021q: adding VLAN 0 to HW filter on device eth2

[  22.022541] bond0: Enslaving eth2 as an active interface with a down link

[  22.275346] 8021q: adding VLAN 0 to HW filter on device eth3

[  22.275539] bond0: Enslaving eth3 as an active interface with a down link

[  22.528361] 8021q: adding VLAN 0 to HW filter on device eth4

[  22.528571] bond0: Enslaving eth4 as an active interface with a down link

[  24.232944] igb 0000:03:00.0 eth1: igb: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX

[  24.264441] bond0: link status definitely up for interface eth1, 1000 Mbps full duplex

[  24.366671] tg3 0000:08:00.0 eth0: Link is up at 1000 Mbps, full duplex

[  24.366679] tg3 0000:08:00.0 eth0: Flow control is off for TX and off for RX

[  24.366683] tg3 0000:08:00.0 eth0: EEE is enabled

[  24.457949] igb 0000:03:00.1 eth2: igb: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX

[  24.464455] bond0: link status definitely up for interface eth0, 1000 Mbps full duplex

[  24.464458] bond0: link status definitely up for interface eth2, 1000 Mbps full duplex

[  24.774960] igb 0000:04:00.0 eth3: igb: eth3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX

[  24.864470] bond0: link status definitely up for interface eth3, 1000 Mbps full duplex

[  25.026975] igb 0000:04:00.1 eth4: igb: eth4 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX

[  25.064480] bond0: link status definitely up for interface eth4, 1000 Mbps full duplex

[  34.874785] mdcmd (34): set md_write_method

 

 

Non working Tower on 6.3.1:

 

root@Tower2:~# dmesg | grep eth

[  12.685324] alx 0000:03:00.0 eth0: Qualcomm Atheros AR816x/AR817x Ethernet [e8:39:35:0e:06:41]

[  12.882026] e1000e 0000:06:00.0 eth1: (PCI Express:2.5GT/s:Width x4) e8:39:35:0e:06:41

[  12.882190] e1000e 0000:06:00.0 eth1: Intel® PRO/1000 Network Connection

[  12.882422] e1000e 0000:06:00.0 eth1: MAC: 0, PHY: 4, PBA No: D98771-010

[  13.049996] e1000e 0000:06:00.1 eth2: (PCI Express:2.5GT/s:Width x4) e8:39:35:0e:06:40

[  13.050160] e1000e 0000:06:00.1 eth2: Intel® PRO/1000 Network Connection

[  13.050391] e1000e 0000:06:00.1 eth2: MAC: 0, PHY: 4, PBA No: D98771-010

[  16.125588] alx 0000:03:00.0 eth0: Qualcomm Atheros AR816x/AR817x Ethernet [e8:39:35:0e:06:41]

[  16.313898] e1000e 0000:06:00.0 eth1: (PCI Express:2.5GT/s:Width x4) e8:39:35:0e:06:41

[  16.313911] e1000e 0000:06:00.0 eth1: Intel® PRO/1000 Network Connection

[  16.313989] e1000e 0000:06:00.0 eth1: MAC: 0, PHY: 4, PBA No: D98771-010

[  16.314664] e1000e 0000:06:00.0 eth118: renamed from eth1

[  16.489959] e1000e 0000:06:00.1 eth1: (PCI Express:2.5GT/s:Width x4) e8:39:35:0e:06:40

[  16.489963] e1000e 0000:06:00.1 eth1: Intel® PRO/1000 Network Connection

[  16.490040] e1000e 0000:06:00.1 eth1: MAC: 0, PHY: 4, PBA No: D98771-010

[  46.735221] bond0: Enslaving eth0 as an active interface with a down link

[  46.736114] alx 0000:03:00.0 eth0: NIC Up: 1 Gbps Full

[  46.996271] 8021q: adding VLAN 0 to HW filter on device eth1

[  46.996569] bond0: Enslaving eth1 as an active interface with a down link

[  46.998030] bond0: link status definitely up for interface eth0, 1000 Mbps full duplex

[  47.008680] e1000e 0000:06:00.1 eth1: changing MTU from 1500 to 9014

[  47.204165] alx 0000:03:00.0 eth0: NIC Up: 1 Gbps Full

[  47.211283] device eth0 entered promiscuous mode

[  47.211350] device eth1 entered promiscuous mode

[  49.720842] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

[  49.812009] bond0: link status definitely up for interface eth1, 1000 Mbps full duplex

[  106.966331] udevd[1459]: Error changing net interface name eth118 to eth0: File exists

[  131.519290] alx 0000:03:00.0 eth0: Link Down

[  131.553699] bond0: link status definitely down for interface eth0, disabling it

[  138.635053] alx 0000:03:00.0 eth0: NIC Up: 1 Gbps Full

[  138.729493] bond0: link status definitely up for interface eth0, 1000 Mbps full duplex

[  151.880355] mdcmd (34): set md_write_method

[  193.170137] device eth0 left promiscuous mode

[  193.170204] device eth1 left promiscuous mode

[  193.211403] bond0: Releasing backup interface eth0

[  193.211406] bond0: the permanent HWaddr of eth0 - e8:39:35:0e:06:41 - is still in use by bond0 - set the HWaddr of eth0 to a different address to avoid conflicts

[  193.225806] bond0: Releasing backup interface eth1

[  193.412912] e1000e: eth1 NIC Link is Down

[  193.413122] e1000e 0000:06:00.1 eth1: changing MTU from 9014 to 1500

[  193.650607] bond0: Enslaving eth0 as an active interface with a down link

[  193.651480] alx 0000:03:00.0 eth0: NIC Up: 1 Gbps Full

[  193.904120] 8021q: adding VLAN 0 to HW filter on device eth118

[  193.904438] bond0: Enslaving eth118 as an active interface with a down link

[  193.905864] bond0: link status definitely up for interface eth0, 1000 Mbps full duplex

[  194.160101] 8021q: adding VLAN 0 to HW filter on device eth1

[  194.160454] bond0: Enslaving eth1 as an active interface with a down link

[  194.173071] e1000e 0000:06:00.0 eth118: changing MTU from 1500 to 9014

[  194.367164] e1000e 0000:06:00.1 eth1: changing MTU from 1500 to 9014

[  194.559910] alx 0000:03:00.0 eth0: NIC Up: 1 Gbps Full

[  194.567501] device eth0 entered promiscuous mode

[  194.567586] device eth118 entered promiscuous mode

[  194.567601] device eth1 entered promiscuous mode

[  196.845673] e1000e: eth118 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

[  196.855830] bond0: link status definitely up for interface eth118, 1000 Mbps full duplex

[  197.060656] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

[  197.063839] bond0: link status definitely up for interface eth1, 1000 Mbps full duplex

[  222.386136] e1000e: eth118 NIC Link is Down

[  222.463073] bond0: link status definitely down for interface eth118, disabling it

[  230.686266] alx 0000:03:00.0 eth0: Link Down

[  230.702895] bond0: link status definitely down for interface eth0, disabling it

[  237.764696] e1000e: eth1 NIC Link is Down

[  237.774638] bond0: link status definitely down for interface eth1, disabling it

[  245.289946] alx 0000:03:00.0 eth0: NIC Up: 1 Gbps Full

[  245.366477] bond0: link status definitely up for interface eth0, 1000 Mbps full duplex

[  377.865520] e1000e: eth118 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

[  377.906686] bond0: link status definitely up for interface eth118, 1000 Mbps full duplex

[  410.712768] e1000e: eth118 NIC Link is Down

[  410.769687] bond0: link status definitely down for interface eth118, disabling it

[  415.221476] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

[  415.241635] bond0: link status definitely up for interface eth1, 1000 Mbps full duplex

[  416.348617] e1000e: eth1 NIC Link is Down

[  416.385529] bond0: link status definitely down for interface eth1, disabling it

[  419.081273] e1000e: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

[  419.089441] bond0: link status definitely up for interface eth1, 1000 Mbps full duplex

[  548.350670] e1000e: eth118 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

[  548.421823] bond0: link status definitely up for interface eth118, 1000 Mbps full duplex

 

thoughts?

 

Thanks!

 

 

Link to comment

My upgrade went smoothly. But now my server will become unresponsive every day or two. Lights are on, fans spinning, but no response to ping or web.

Install the Fix Common Problems plugin, and fix anything it notifies you about.  Then if the system still goes down, start the Troubleshooting mode of the plugin, so you'll have the latest syslog messages and diagnostics to post here, or better yet in a new support thread.  (Need help? Read me first!)

Link to comment

I am seeing this is my syslog.

 

Feb 15 20:49:00 uNAS shfs/user: err: get_key_info: get_message: /boot/config/._Plus.key (-3)

 

Is there an easy way to roll back to 6.3 from command line?

 

Copy the three bz* files from the previous folder back to the root.  (You will overwrite the three files that are there unless you rename them first-- not a bad idea by the way.)  But first, type diagnostics at the command prompt.  That will save the diagnostics file to your flash drive which you should upload to your earlier post.  Now reboot your server...

Link to comment

I am seeing this is my syslog.

 

Feb 15 20:49:00 uNAS shfs/user: err: get_key_info: get_message: /boot/config/._Plus.key (-3)

 

Is there an easy way to roll back to 6.3 from command line?

that error sounds as if there might be an issue reading the license file off the USB drive.  If so you may find that you get the same problem when you roll back to an earlier release.  It might be worth inserting the USB drive into a Windows/Mac system and let it check the USB drive.
Link to comment

I am seeing this is my syslog.

 

Feb 15 20:49:00 uNAS shfs/user: err: get_key_info: get_message: /boot/config/._Plus.key (-3)

 

Is there an easy way to roll back to 6.3 from command line?

 

Since the file starts with "._", I would assume that you have the real key in the file Plus.key, and that the USB drive was at some time plugged in to, or accessed by, a Mac. The ._filename contains the resource fork for the filename file.

 

In your case, the following most likely apply:

Plus.key - Real key.

._Plus.key - Resource fork, not a valid key, only used by Mac. Maybe unRAID should ignore ._*.key files?

Link to comment

I upgraded to 6.3.1 from 6.2.4 last week and got an error about too many profiles in my (dual) cache, ran a balance on the cache, then it seemed fine.

Today I opened my Movies share and saw only 4,300 folders out of 9,500 folders that I had, tried other samba clients and same there. I SSH'd in and all folders were there. Local Plex server docker saw all folders. The other Plex servers on the lan only saw 4,300. On Windows, if I manually traversed to one of the missing folders it worked!? After restarting unraid and clients and nothing helped I finally decided to downgrade back to 6.2.4, so I...

 

Stopped Array, copied /boot/previous/bz* to /boot and rebooted. Unraid came back up on 6.2.4 and all movies are back on samba share, woohoo.

Then realized Docker tab is missing completely from the GUI, so I..

Went to Settings, Docker, nuked docker image, Restored my Appdata using the awesome CommunityApplications Backup and rebooted

Now the Docker tab is back, but no dockers in there so I went to Apps, Previous Apps, and reinstalled all my dockers.

 

Have any of you guys seen this strange issue with samba shares or know of a fix?

 

Since I am paranoid, I ran this command in SSH to count directories to compare with the # of directories appearing in Windows from the share: {use your share path}

find /mnt/user/Movies/* -maxdepth 0 -type d | wc -l

 

I hope this info helps somebody else that's wondering where their stuff went

Link to comment

I upgraded from 6.2.4 to 6.3.1 and I've got a call trace in my log when I start now. I turned off docker and disabled all my plugins and I'm still seeing it. I've attached a diagnostics dump of the clean boot.

 

Referring to this?

Your BIOS is broken; DMAR reported at address fed91000 returns all ones!

 

Can you check if your m/b has new bios available?

Link to comment

I upgraded to 6.3.1 from 6.2.4 last week and got an error about too many profiles in my (dual) cache, ran a balance on the cache, then it seemed fine.

Today I opened my Movies share and saw only 4,300 folders out of 9,500 folders that I had, tried other samba clients and same there. I SSH'd in and all folders were there. Local Plex server docker saw all folders. The other Plex servers on the lan only saw 4,300. On Windows, if I manually traversed to one of the missing folders it worked!? After restarting unraid and clients and nothing helped I finally decided to downgrade back to 6.2.4, so I...

 

Stopped Array, copied /boot/previous/bz* to /boot and rebooted. Unraid came back up on 6.2.4 and all movies are back on samba share, woohoo.

Then realized Docker tab is missing completely from the GUI, so I..

Went to Settings, Docker, nuked docker image, Restored my Appdata using the awesome CommunityApplications Backup and rebooted

Now the Docker tab is back, but no dockers in there so I went to Apps, Previous Apps, and reinstalled all my dockers.

 

Have any of you guys seen this strange issue with samba shares or know of a fix?

 

Since I am paranoid, I ran this command in SSH to count directories to compare with the # of directories appearing in Windows from the share: {use your share path}

find /mnt/user/Movies/* -maxdepth 0 -type d | wc -l

 

I hope this info helps somebody else that's wondering where their stuff went

 

Why don't you install the Fix Common Problems plugin.  Run it once and see what it reports. 

Link to comment

Thanks for the tip, I tried the Fix Common Problems plugin, but nothing related to my issue. I noticed that samba was upgraded in new Unraid release, could this be a samba bug? I read that samba has issues with 32,000+ folders but I'm at 1/3 of that inode limit. Anyone else missing shared folders after upgrading?

Link to comment
  • 2 months later...

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.