unRAID Server Release 6.0-rc3-x86_64 Available


Recommended Posts

I upgraded from b15 to RC3 shortly after it was released.  I'm (still) having various issues that have persisted since the update.  I was running b6 smoothly since it was released (months of uptime with no issues).  I've been busy so I haven't had time to post, but I'll collect what I can in my other post.  Some symptoms I'm seeing:

- webgui crashes

- btrfs checksum errors in docker.img

- segmentation faults

- at least 2 hard crashes, one of which was a kernel panic

 

I updated my post linked below for further analysis.

 

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

 

To follow up here, I discovered that my RAM was bad, and this is likely the cause of most of my issues (to be confirmed).

 

I regenerated my docker.img file and will keep an eye on checksum or any other issues.

Link to comment
  • Replies 446
  • Created
  • Last Reply

Top Posters In This Topic

3 more segfaults today.

 

May 27 13:32:45 unRAID kernel: python[28950]: segfault at 58 ip 000000000052c8d8 sp 00002ae4fab61a60 error 4 in python2.7[400000+2bd000]
May 27 14:13:01 unRAID kernel: python[2462]: segfault at 58 ip 000000000052c8d8 sp 00002b5012816220 error 4 in python2.7[400000+2bd000]
May 27 14:48:12 unRAID kernel: python[7489]: segfault at 58 ip 000000000052c8d8 sp 00002abd45e90b60 error 4 in python2.7[400000+2bd000]

 

Does this warrant a defect report?

 

John

Link to comment

3 more segfaults today and this time my couchpotato container was shutdown.

 

May 27 13:32:45 unRAID kernel: python[28950]: segfault at 58 ip 000000000052c8d8 sp 00002ae4fab61a60 error 4 in python2.7[400000+2bd000]
May 27 14:13:01 unRAID kernel: python[2462]: segfault at 58 ip 000000000052c8d8 sp 00002b5012816220 error 4 in python2.7[400000+2bd000]
May 27 14:48:12 unRAID kernel: python[7489]: segfault at 58 ip 000000000052c8d8 sp 00002abd45e90b60 error 4 in python2.7[400000+2bd000]

 

Does this warrant a defect report?

 

John

 

no, it's probably to do with kodi and not specifically unraid.

 

it's a patched version of kodi.

Link to comment

urbackup also generated some segfaults along with messing up the docker image.

FoldingAtHome also does it, but since it just carries on it's merry way regardless I've never been worried about it  (usually I get one per day from FAH)

 

May 27 02:46:10 Server_A kernel: FahCore_a4[14505]: segfault at 1ed519129f0 ip 000000000055651f sp 00002ae4104b7e80 error 4 in FahCore_a4[400000+5e9000]

Link to comment

As I reported during the betas (I believe b9), I just wanted to share that the "update Plugins" pop-up has two issues:

 

1) On iOS devices, the contents of this screen (i.e. during updates) roll past the bottom of the box, but the user cannot scroll down to see the results of the update.

2) Minor:  Capitalization of each word in "update Plugin" is weird (i.e. first word uncapitalized, second word capitalized).

 

Link to comment

Trying to setup a KVM for the first time...

 

I downloaded Linux Mint (both 64 and 32 bits just to see if that was the issue), but regardless of what I try, I get the following error:

 

Error creating VM: internal error: process exited while connecting to monitor: 2015-05-28T19:18:12.791976Z qemu-system-x86_64: -drive file=/mnt/user/VMs/LinuxMint/vdisk1.img,if=none,id=drive-virtio-disk1,format=raw,cache=none,aio=native: Could not find working O_DIRECT alignment. Try cache.direct=off.

 

Nothing Fancy in the setup:

- I've defined br0 under network settings

- I've created a share for the ISOs and a Share for the VMs

- I've assigned br0 in the VM Manager page

- Click "Add VM" and:

--- OS = Linux

--- Passthrough CPU

--- Using Core 0 and Core 1  (out of 4 cores)

--- Init Ram 512MB (out of 4GB)

--- Graphics Card = VNC  (it's a headless computer)

--- Soundcard None

--- USB devices None checked (option being UPS)

--- BIOS = SeaBIOS

--- Machine --> Tried both i440 and q35

 

Any tips?

 

 

Link to comment

Anyone ever see these kind of errors?

 

May 28 16:23:45 SUN emhttp: shareSize.3 not found

May 28 16:23:45 SUN emhttp: shareColor.4 not found

May 28 16:23:45 SUN emhttp: shareFree.4 not found

May 28 16:23:45 SUN emhttp: shareSize.4 not found

May 28 16:23:45 SUN emhttp: shareColor.5 not found

May 28 16:23:45 SUN emhttp: shareFree.5 not found

May 28 16:23:45 SUN emhttp: shareSize.5 not found

May 28 16:23:45 SUN emhttp: shareColor.6 not found

May 28 16:23:45 SUN emhttp: shareFree.6 not found

May 28 16:23:45 SUN emhttp: shareSize.6 not found

May 28 16:23:45 SUN emhttp: shareColor.7 not found

May 28 16:23:45 SUN emhttp: shareFree.7 not found

May 28 16:23:45 SUN emhttp: shareSize.7 not found

Link to comment

Anyone ever see these kind of errors?

 

May 28 16:23:45 SUN emhttp: shareSize.3 not found

May 28 16:23:45 SUN emhttp: shareColor.4 not found

May 28 16:23:45 SUN emhttp: shareFree.4 not found

May 28 16:23:45 SUN emhttp: shareSize.4 not found

May 28 16:23:45 SUN emhttp: shareColor.5 not found

May 28 16:23:45 SUN emhttp: shareFree.5 not found

May 28 16:23:45 SUN emhttp: shareSize.5 not found

May 28 16:23:45 SUN emhttp: shareColor.6 not found

May 28 16:23:45 SUN emhttp: shareFree.6 not found

May 28 16:23:45 SUN emhttp: shareSize.6 not found

May 28 16:23:45 SUN emhttp: shareColor.7 not found

May 28 16:23:45 SUN emhttp: shareFree.7 not found

May 28 16:23:45 SUN emhttp: shareSize.7 not found

 

Been changing your slot config?  That bug is fixed in next release.

Link to comment

Try removing th br0 in network settings. Apparently not needed for KVM.

 

But that would mean that I can't access the VM from the LAN... 

I'll try it, but that's no good..

 

I asked this question before and you can still access via lan. I'm doing it right now in fact.

 

http://lime-technology.com/forum/index.php?topic=39343.msg366969#msg366969

 

Interesting! 

 

Unfortunately I just tried (both the ISOs, as well as a vdi file converted qcow2) and they all give the same error...  I am guess the qcow2 file won't be smooth since it was created on a different machine all-together, but the fresh ISOs..

Link to comment

Anyone ever see these kind of errors?

 

May 28 16:23:45 SUN emhttp: shareSize.3 not found

May 28 16:23:45 SUN emhttp: shareColor.4 not found

May 28 16:23:45 SUN emhttp: shareFree.4 not found

May 28 16:23:45 SUN emhttp: shareSize.4 not found

May 28 16:23:45 SUN emhttp: shareColor.5 not found

May 28 16:23:45 SUN emhttp: shareFree.5 not found

May 28 16:23:45 SUN emhttp: shareSize.5 not found

May 28 16:23:45 SUN emhttp: shareColor.6 not found

May 28 16:23:45 SUN emhttp: shareFree.6 not found

May 28 16:23:45 SUN emhttp: shareSize.6 not found

May 28 16:23:45 SUN emhttp: shareColor.7 not found

May 28 16:23:45 SUN emhttp: shareFree.7 not found

May 28 16:23:45 SUN emhttp: shareSize.7 not found

 

Been changing your slot config?  That bug is fixed in next release.

 

Haven't changed any drives in or out for a long time.

Link to comment

Trying to setup a KVM for the first time...

 

I downloaded Linux Mint (both 64 and 32 bits just to see if that was the issue), but regardless of what I try, I get the following error:

 

Error creating VM: internal error: process exited while connecting to monitor: 2015-05-28T19:18:12.791976Z qemu-system-x86_64: -drive file=/mnt/user/VMs/LinuxMint/vdisk1.img,if=none,id=drive-virtio-disk1,format=raw,cache=none,aio=native: Could not find working O_DIRECT alignment. Try cache.direct=off.

 

Nothing Fancy in the setup:

- I've defined br0 under network settings

- I've created a share for the ISOs and a Share for the VMs

- I've assigned br0 in the VM Manager page

- Click "Add VM" and:

--- OS = Linux

--- Passthrough CPU

--- Using Core 0 and Core 1  (out of 4 cores)

--- Init Ram 512MB (out of 4GB)

--- Graphics Card = VNC  (it's a headless computer)

--- Soundcard None

--- USB devices None checked (option being UPS)

--- BIOS = SeaBIOS

--- Machine --> Tried both i440 and q35

 

Any tips?

This is a bug that will be fixed in an upcoming release that only affects users creating vdisks on non-btrfs formatted devices and when traversing through user shares. See this to fix:

 

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

Link to comment

Anyone ever see these kind of errors?

 

May 28 16:23:45 SUN emhttp: shareSize.3 not found

May 28 16:23:45 SUN emhttp: shareColor.4 not found

May 28 16:23:45 SUN emhttp: shareFree.4 not found

May 28 16:23:45 SUN emhttp: shareSize.4 not found

May 28 16:23:45 SUN emhttp: shareColor.5 not found

May 28 16:23:45 SUN emhttp: shareFree.5 not found

May 28 16:23:45 SUN emhttp: shareSize.5 not found

May 28 16:23:45 SUN emhttp: shareColor.6 not found

May 28 16:23:45 SUN emhttp: shareFree.6 not found

May 28 16:23:45 SUN emhttp: shareSize.6 not found

May 28 16:23:45 SUN emhttp: shareColor.7 not found

May 28 16:23:45 SUN emhttp: shareFree.7 not found

May 28 16:23:45 SUN emhttp: shareSize.7 not found

 

Been changing your slot config?  That bug is fixed in next release.

 

Haven't changed any drives in or out for a long time.

 

Same here - not changed any drive allocations  for months, but I get these messages in my logfile.

Link to comment

Anyone ever see these kind of errors?

 

May 28 16:23:45 SUN emhttp: shareSize.3 not found

May 28 16:23:45 SUN emhttp: shareColor.4 not found

May 28 16:23:45 SUN emhttp: shareFree.4 not found

May 28 16:23:45 SUN emhttp: shareSize.4 not found

May 28 16:23:45 SUN emhttp: shareColor.5 not found

May 28 16:23:45 SUN emhttp: shareFree.5 not found

May 28 16:23:45 SUN emhttp: shareSize.5 not found

May 28 16:23:45 SUN emhttp: shareColor.6 not found

May 28 16:23:45 SUN emhttp: shareFree.6 not found

May 28 16:23:45 SUN emhttp: shareSize.6 not found

May 28 16:23:45 SUN emhttp: shareColor.7 not found

May 28 16:23:45 SUN emhttp: shareFree.7 not found

May 28 16:23:45 SUN emhttp: shareSize.7 not found

 

Been changing your slot config?  That bug is fixed in next release.

 

Haven't changed any drives in or out for a long time.

 

I am also getting these and have not reconfigured my drives.

Link to comment

search for sharesize in my graylog server, shows 104 instances.

 

all of which are on or after 20/5/15

 

or 5/20/15 in merikan style.

 

is that rc3 release date ?

I've always preferred 2015-05-20 because it's sortable, most significant digits first, etc. Also less ambiguous since I don't think anyone ever swaps month and day in that format.

 

I have them in my log too. No change to disk configuration in months.

Link to comment

search for sharesize in my graylog server, shows 104 instances.

 

all of which are on or after 20/5/15

 

or 5/20/15 in merikan style.

 

is that rc3 release date ?

I've always preferred 2015-05-20 because it's sortable, most significant digits first, etc. Also less ambiguous since I don't think anyone ever swaps month and day in that format.

 

I have them in my log too. No change to disk configuration in months.

 

i'm not getting in to the whole, we are right to write the date dd/mm/yy thing and anyone else who does it differently is just plain wrong, lol.

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