unRAID OS version 6.3.4 Stable Release Available


94 posts in this topic Last Reply

Recommended Posts

  • Replies 93
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Upgrade Instructions   Clicking 'Check for Updates' on the Plugins page is the preferred way to upgrade.  If the new version does not appear, you can manually update by selecting the Install

Yeah, I have the same problem.   ... Perhaps in 6.4

I think you may be getting mixed up with the 6.4 release that is expected to go into beta soon.

Posted Images

16 hours ago, FreeMan said:

My single SSD cache also disappeared after the reboot. Definitely not the first reboot after installing/assigning the drive.

 

Stopped the array, assigned it, restarted. All dockers have started and it appears that there are no further issues.

 

Thanks for continuing to improve and update! The only issues I've ever really had have been of my own making - unRAID has been rock solid.

 

 

This happened to my server as well - SSD Cache was unassigned after reboot and had to be manually assigned to restore proper VMs and Dockers.

Appears to be fine now - hopefully it will survive another reboot with the proper SSD assigned to the cache.

 

Link to post
On 5/18/2017 at 10:02 AM, master.h said:

I upgraded two systems this morning. My second system was running a VM, Plex, and Reslio-sync. I failed to realize that was about 98% RAM utilization, so when unraid attempted to extract the update after downloading, my system ran out of memory and crashed. Had to hard reboot. Second try I stopped the dockers ahead of time, then all went well. Maybe an FYI for those with smaller amounts of RAM installed.

 

I wonder if the unraidserver.plg can check for free ram before unpacking and post an alert if utilization is too high?

Link to post
1 hour ago, MrCrispy said:

I thought this release would have the fix for the single threaded GUI hang issue, it was said in one of the other threads.

I think you may be getting mixed up with the 6.4 release that is expected to go into beta soon.

Link to post

Immediately after upgrading and rebooting making no other changes my e1000 ethernet adapter has gone into a frenzy resetting itself.

 

"May 19 21:19:31 Tower kernel: e1000 0000:04:00.1 eth2: Detected Tx Unit Hang
May 19 21:19:31 Tower kernel:  Tx Queue             <0>
May 19 21:19:31 Tower kernel:  TDH                  <0>
May 19 21:19:31 Tower kernel:  TDT                  <1>
May 19 21:19:31 Tower kernel:  next_to_use          <1>
May 19 21:19:31 Tower kernel:  next_to_clean        <0>
May 19 21:19:31 Tower kernel: buffer_info[next_to_clean]
May 19 21:19:31 Tower kernel:  time_stamp           <1006fd4c8>
May 19 21:19:31 Tower kernel:  next_to_watch        <0>
May 19 21:19:31 Tower kernel:  jiffies              <1006fe200>
May 19 21:19:31 Tower kernel:  next_to_watch.status <0>
May 19 21:19:32 Tower dhcpcd[1703]: br2: probing for an IPv4LL address
May 19 21:19:33 Tower kernel: e1000 0000:04:00.1 eth2: Detected Tx Unit Hang
May 19 21:19:33 Tower kernel:  Tx Queue             <0>
May 19 21:19:33 Tower kernel:  TDH                  <0>
May 19 21:19:33 Tower kernel:  TDT                  <1>
May 19 21:19:33 Tower kernel:  next_to_use          <1>
May 19 21:19:33 Tower kernel:  next_to_clean        <0>
May 19 21:19:33 Tower kernel: buffer_info[next_to_clean]
May 19 21:19:33 Tower kernel:  time_stamp           <1006fd4c8>
May 19 21:19:33 Tower kernel:  next_to_watch        <0>
May 19 21:19:33 Tower kernel:  jiffies              <1006fea00>
May 19 21:19:33 Tower kernel:  next_to_watch.status <0>
May 19 21:19:35 Tower kernel: e1000 0000:04:00.1 eth2: Detected Tx Unit Hang
May 19 21:19:35 Tower kernel:  Tx Queue             <0>
May 19 21:19:35 Tower kernel:  TDH                  <0>
May 19 21:19:35 Tower kernel:  TDT                  <1>
May 19 21:19:35 Tower kernel:  next_to_use          <1>
May 19 21:19:35 Tower kernel:  next_to_clean        <0>
May 19 21:19:35 Tower kernel: buffer_info[next_to_clean]
May 19 21:19:35 Tower kernel:  time_stamp           <1006fd4c8>
May 19 21:19:35 Tower kernel:  next_to_watch        <0>
May 19 21:19:35 Tower kernel:  jiffies              <1006ff200>
May 19 21:19:35 Tower kernel:  next_to_watch.status <0>
May 19 21:19:37 Tower kernel: e1000 0000:04:00.1 eth2: Detected Tx Unit Hang
May 19 21:19:37 Tower kernel:  Tx Queue             <0>
May 19 21:19:37 Tower kernel:  TDH                  <0>
May 19 21:19:37 Tower kernel:  TDT                  <1>
May 19 21:19:37 Tower kernel:  next_to_use          <1>
May 19 21:19:37 Tower kernel:  next_to_clean        <0>
May 19 21:19:37 Tower kernel: buffer_info[next_to_clean]"

Link to post
7 minutes ago, engin33rh3r3 said:

Immediately after upgrading and rebooting making no other changes my e1000 ethernet adapter has gone into a frenzy resetting itself.

 

Reseat your card.

Link to post
57 minutes ago, bonienl said:

 

Reseat your card.

Reseating card allowed it to work again for about 30 minutes. Now it is back to doing it again..... Card was seated tightly and this server has been running fine for about a year with every other update except this one....

Link to post
6 minutes ago, engin33rh3r3 said:

Reseating card allowed it to work again for about 30 minutes. Now it is back to doing it again..... Card was seated tightly and this server has been running fine for about a year with every other update except this one....

 

AFAIK ethernet drivers in this version haven't changed.

 

I have two Intel e1000 ethernet adapters in my main system, both working fine.

 

Link to post
3 minutes ago, bonienl said:

 

AFAIK ethernet drivers in this version haven't changed.

 

I have two Intel e1000 ethernet adapters in my main system, both working fine.

 

 

Something obviously changed.... No other updates or changes were made to server in the past several days and it was fine to the very moment I performed the update... 

 

"May 19 19:44:09 Tower kernel: e1000: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
May 19 19:44:09 Tower kernel: br2: port 1(eth2) entered blocking state
May 19 19:44:09 Tower kernel: br2: port 1(eth2) entered forwarding state
May 19 19:44:09 Tower dhcpcd[1703]: br2: soliciting a DHCP lease
May 19 19:44:11 Tower kernel: e1000 0000:04:00.1 eth2: Detected Tx Unit Hang
May 19 19:44:11 Tower kernel:  Tx Queue             <0>
May 19 19:44:11 Tower kernel:  TDH                  <0>
May 19 19:44:11 Tower kernel:  TDT                  <1>
May 19 19:44:11 Tower kernel:  next_to_use          <1>
May 19 19:44:11 Tower kernel:  next_to_clean        <0>
May 19 19:44:11 Tower kernel: buffer_info[next_to_clean]
May 19 19:44:11 Tower kernel:  time_stamp           <10018941f>
May 19 19:44:11 Tower kernel:  next_to_watch        <0>
May 19 19:44:11 Tower kernel:  jiffies              <100189a40>
May 19 19:44:11 Tower kernel:  next_to_watch.status <0>
May 19 19:44:13 Tower kernel: e1000 0000:04:00.1 eth2: Detected Tx Unit Hang
May 19 19:44:13 Tower kernel:  Tx Queue             <0>
May 19 19:44:13 Tower kernel:  TDH                  <0>
May 19 19:44:13 Tower kernel:  TDT                  <1>
May 19 19:44:13 Tower kernel:  next_to_use          <1>
May 19 19:44:13 Tower kernel:  next_to_clean        <0>
May 19 19:44:13 Tower kernel: buffer_info[next_to_clean]
May 19 19:44:13 Tower kernel:  time_stamp           <10018941f>
May 19 19:44:13 Tower kernel:  next_to_watch        <0>
May 19 19:44:13 Tower kernel:  jiffies              <10018a240>
May 19 19:44:13 Tower kernel:  next_to_watch.status <0>
May 19 19:44:14 Tower dhcpcd[1703]: br2: probing for an IPv4LL address
May 19 19:44:14 Tower kernel: e1000 0000:04:00.1 eth2: Reset adapter
May 19 19:44:14 Tower kernel: br2: port 1(eth2) entered disabled state
May 19 19:44:15 Tower dhcpcd[1703]: br2: carrier lost
May 19 19:44:18 Tower dhcpcd[1703]: br2: carrier acquired
May 19 19:44:18 Tower kernel: e1000: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
May 19 19:44:18 Tower kernel: br2: port 1(eth2) entered blocking state
May 19 19:44:18 Tower kernel: br2: port 1(eth2) entered forwarding state
May 19 19:44:19 Tower dhcpcd[1703]: br2: soliciting a DHCP lease
May 19 19:44:20 Tower kernel: e1000 0000:04:00.1 eth2: Detected Tx Unit Hang
May 19 19:44:20 Tower kernel:  Tx Queue             <0>
May 19 19:44:20 Tower kernel:  TDH                  <0>
May 19 19:44:20 Tower kernel:  TDT                  <1>
May 19 19:44:20 Tower kernel:  next_to_use          <1>
May 19 19:44:20 Tower kernel:  next_to_clean        <0>
May 19 19:44:20 Tower kernel: buffer_info[next_to_clean]
May 19 19:44:20 Tower kernel:  time_stamp           <10018bab2>
May 19 19:44:20 Tower kernel:  next_to_watch        <0>
May 19 19:44:20 Tower kernel:  jiffies              <10018c000>
May 19 19:44:20 Tower kernel:  next_to_watch.status <0>
May 19 19:44:22 Tower kernel: e1000 0000:04:00.1 eth2: Detected Tx Unit Hang
May 19 19:44:22 Tower kernel:  Tx Queue             <0>
May 19 19:44:22 Tower kernel:  TDH                  <0>
May 19 19:44:22 Tower kernel:  TDT                  <1>
May 19 19:44:22 Tower kernel:  next_to_use          <1>
May 19 19:44:22 Tower kernel:  next_to_clean        <0>
May 19 19:44:22 Tower kernel: buffer_info[next_to_clean]
May 19 19:44:22 Tower kernel:  time_stamp           <10018bab2>
May 19 19:44:22 Tower kernel:  next_to_watch        <0>
May 19 19:44:22 Tower kernel:  jiffies              <10018c801>
May 19 19:44:22 Tower kernel:  next_to_watch.status <0>
May 19 19:44:24 Tower dhcpcd[1703]: br2: probing for an IPv4LL address
May 19 19:44:24 Tower kernel: e1000 0000:04:00.1 eth2: Reset adapter
May 19 19:44:24 Tower kernel: e1000: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
May 19 19:44:24 Tower kernel: e1000 0000:04:00.1 eth2: Detected Tx Unit Hang
May 19 19:44:24 Tower kernel:  Tx Queue             <0>
May 19 19:44:24 Tower kernel:  TDH                  <0>
May 19 19:44:24 Tower kernel:  TDT                  <1>
May 19 19:44:24 Tower kernel:  next_to_use          <1>
May 19 19:44:24 Tower kernel:  next_to_clean        <0>
May 19 19:44:24 Tower kernel: buffer_info[next_to_clean]
May 19 19:44:24 Tower kernel:  time_stamp           <10018bab2>
May 19 19:44:24 Tower kernel:  next_to_watch        <0>
May 19 19:44:24 Tower kernel:  jiffies              <10018d000>
May 19 19:44:24 Tower kernel:  next_to_watch.status <0>
May 19 19:44:24 Tower kernel: e1000: eth2 NIC Link is Down
May 19 19:44:24 Tower kernel: e1000 0000:04:00.1 eth2: Reset adapter
May 19 19:44:25 Tower kernel: br2: port 1(eth2) entered disabled state
May 19 19:44:26 Tower dhcpcd[1703]: br2: carrier lost
May 19 19:44:29 Tower dhcpcd[1703]: br2: carrier acquired
May 19 19:44:29 Tower kernel: e1000: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
May 19 19:44:29 Tower kernel: br2: port 1(eth2) entered blocking state
May 19 19:44:29 Tower kernel: br2: port 1(eth2) entered forwarding state
May 19 19:44:29 Tower dhcpcd[1703]: br2: soliciting a DHCP lease
May 19 19:44:31 Tower kernel: e1000 0000:04:00.1 eth2: Detected Tx Unit Hang
May 19 19:44:31 Tower kernel:  Tx Queue             <0>
May 19 19:44:31 Tower kernel:  TDH                  <0>
May 19 19:44:31 Tower kernel:  TDT                  <1>
May 19 19:44:31 Tower kernel:  next_to_use          <1>
May 19 19:44:31 Tower kernel:  next_to_clean        <0>
May 19 19:44:31 Tower kernel: buffer_info[next_to_clean]
May 19 19:44:31 Tower kernel:  time_stamp           <10018e28d>
May 19 19:44:31 Tower kernel:  next_to_watch        <0>
May 19 19:44:31 Tower kernel:  jiffies              <10018e840>
May 19 19:44:31 Tower kernel:  next_to_watch.status <0>
May 19 19:44:33 Tower kernel: e1000 0000:04:00.1 eth2: Detected Tx Unit Hang
May 19 19:44:33 Tower kernel:  Tx Queue             <0>
May 19 19:44:33 Tower kernel:  TDH                  <0>
May 19 19:44:33 Tower kernel:  TDT                  <1>
May 19 19:44:33 Tower kernel:  next_to_use          <1>
May 19 19:44:33 Tower kernel:  next_to_clean        <0>
May 19 19:44:33 Tower kernel: buffer_info[next_to_clean]
May 19 19:44:33 Tower kernel:  time_stamp           <10018e28d>
May 19 19:44:33 Tower kernel:  next_to_watch        <0>
May 19 19:44:33 Tower kernel:  jiffies              <10018f040>
May 19 19:44:33 Tower kernel:  next_to_watch.status <0>
May 19 19:44:34 Tower dhcpcd[1703]: br2: probing for an IPv4LL address
May 19 19:44:35 Tower kernel: e1000 0000:04:00.1 eth2: Detected Tx Unit Hang
May 19 19:44:35 Tower kernel:  Tx Queue             <0>
May 19 19:44:35 Tower kernel:  TDH                  <0>
May 19 19:44:35 Tower kernel:  TDT                  <1>
May 19 19:44:35 Tower kernel:  next_to_use          <1>
May 19 19:44:35 Tower kernel:  next_to_clean        <0>
May 19 19:44:35 Tower kernel: buffer_info[next_to_clean]
May 19 19:44:35 Tower kernel:  time_stamp           <10018e28d>
May 19 19:44:35 Tower kernel:  next_to_watch        <0>
May 19 19:44:35 Tower kernel:  jiffies              <10018f840>
May 19 19:44:35 Tower kernel:  next_to_watch.status <0>
May 19 19:44:37 Tower kernel: e1000 0000:04:00.1 eth2: Detected Tx Unit Hang
May 19 19:44:37 Tower kernel:  Tx Queue             <0>
May 19 19:44:37 Tower kernel:  TDH                  <0>
May 19 19:44:37 Tower kernel:  TDT                  <1>
May 19 19:44:37 Tower kernel:  next_to_use          <1>
May 19 19:44:37 Tower kernel:  next_to_clean        <0>
May 19 19:44:37 Tower kernel: buffer_info[next_to_clean]
May 19 19:44:37 Tower kernel:  time_stamp           <10018e28d>
May 19 19:44:37 Tower kernel:  next_to_watch        <0>
May 19 19:44:37 Tower kernel:  jiffies              <100190040>
May 19 19:44:37 Tower kernel:  next_to_watch.status <0>
May 19 19:44:39 Tower kernel: e1000 0000:04:00.1 eth2: Detected Tx Unit Hang
May 19 19:44:39 Tower kernel:  Tx Queue             <0>
May 19 19:44:39 Tower kernel:  TDH                  <0>
May 19 19:44:39 Tower kernel:  TDT                  <1>
May 19 19:44:39 Tower kernel:  next_to_use          <1>
May 19 19:44:39 Tower kernel:  next_to_clean        <0>
May 19 19:44:39 Tower kernel: buffer_info[next_to_clean]
May 19 19:44:39 Tower kernel:  time_stamp           <10018e28d>
May 19 19:44:39 Tower kernel:  next_to_watch        <0>
May 19 19:44:39 Tower kernel:  jiffies              <100190840>
May 19 19:44:39 Tower kernel:  next_to_watch.status <0>
May 19 19:44:39 Tower kernel: e1000 0000:04:00.1 eth2: Reset adapter
May 19 19:44:39 Tower kernel: br2: port 1(eth2) entered disabled state

"

Link to post
7 hours ago, Zangief said:

On upgrading from 6.3.3 to 6.3.4 my parity 2 disk reported;

 

"Warning - reported uncorrect" on SMART
 
After rebooting.

 

Look at the SMART data for the drive and see if any parameters are out-of-tolerance.

Link to post

... I presume you know this; but to get the SMART status just go to the Dashboard tab; then click the icon on the "SMART Status" line for the disk you want the data for; and select "Attributes".   Then just scroll down to see the detailed attributes.

 

Link to post
18 minutes ago, garycase said:

... I presume you know this; but to get the SMART status just go to the Dashboard tab; then click the icon on the "SMART Status" line for the disk you want the data for; and select "Attributes".   Then just scroll down to see the detailed attributes.

 

 

... Or on the 'Main' tab, click on the name of the disk that you are interested in reviewing under the 'Device' column and look for 'Attributes'.

Link to post
4 hours ago, garycase said:

 

Look at the SMART data for the drive and see if any parameters are out-of-tolerance.

Yes, see screenshot. This occurred as a result of the upgrade. And not sure whether it matters but the hard drive is 3 weeks old from new and pre-cleared fine. Working faultlessly until the upgrade to 6.3.4 and then restarted the array with this warning

 

pcggf4v.png

Edited by Zangief
Link to post
10 minutes ago, johnnie.black said:

 

Upgrade won't change SMART attributes, it's a coincidence.

No it is not. Sorry. The odds of it happening within 30 secs of an upgrade.... Not a chance in a billion.

Its more likely you just don't know the answer and this is an easy guess.

lets see if anyone else reports any faults...

Edited by Zangief
Link to post

johnnie.black is the most knowledgeable person around here when it comes to disks and disk behaviour, he is not making a guess.

 

The upgrade procedure writes new files to the flash device, flushes memory to disk, and restarts your system with the new files from the flash device.

You might have had a lingering problem on the disk and the forced reboot of your system after the upgrade made it visible.


 

Link to post
3 minutes ago, bonienl said:

johnnie.black is the most knowledgeable person around here when it comes to disks and disk behaviour, he is not making a guess.

 

The upgrade procedure writes new files to the flash device, flushes memory to disk, and restarts your system with the new files from the flash device.

You might have had a lingering problem on the disk and the forced reboot of your system after the upgrade made it visible.


 

Ok. Sounds very plausible. It doesnt seem to be causing any further issues at any rate. However worthwhile reporting it anyway. Thanks

Edited by Zangief
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.