Jump to content
limetech

Unraid OS version 6.6.0 available

269 posts in this topic Last Reply

Recommended Posts

A  minor problem:

 

I used to be able to add a drive to my vm using (see this existing/working VM)

VM_byid.PNG.57e2525b38c73d41f45ff4d9fe780222.PNG

 

With 6.6.0, I can't do that anymore?

VM_add_disc_byid.PNG.f21e2805ce8549355287e7ca03a1996e.PNG

 

I don't remember how I entered this ADATA SSD in this existing VM (did I just copy paste??), but it would be nice if /dev/disk/... would be browseable/selectable.

 

Share this post


Link to post
1 minute ago, Wimpie said:

I don't remember how I entered this ADATA SSD in this existing VM (did I just copy paste??), but it would be nice if /dev/disk/... would be browseable/selectable.

Click on the input box and type the location you wish to add.

Share this post


Link to post
3 minutes ago, bonienl said:

Click on the input box and type the location you wish to add.

So, basicly copy/paste.

 

Another very minor point: Text is cut of and unreadable (separate sub-folder and image will be created b????????)

text_cutoff.PNG.c5d23774e258fe1d4c0a5980d0ee2477.PNG

Edited by Wimpie

Share this post


Link to post

Yes, copy/paste will work but a "normal" selection should work too.

image.png.99d57d268b4df5c6dd4b3dc16438d69c.png

 

Btw /dev/disk is not a valid location

Edited by bonienl

Share this post


Link to post
18 minutes ago, bonienl said:

Btw /dev/disk is not a valid location

 

Now I'm very confused?!?

 

This is a working VM:

VM_byid.PNG.2427e8741504d97cf61d40fd0d361918.PNG

 

It's a VM  that has it's HD completly for itself (passthrough? or how is it called).

 

It works, and is referenced by id (to survive reboots, sda becomes otherwise maybe sdb).

 

Got it from maybe this thread: 

There are many more posts that say use /dev/disk/by-id/...

 

You are saying this is not more supported?

 

Edit: maybe I should have written /dev/disk/by-id/...?

Edit2: if  /dev/disk/by-id/... is valid, then the minor problem is that I would like it browseable/selectable..

Edited by Wimpie

Share this post


Link to post
1 minute ago, bonienl said:

With these settings you are exactly on a boundary and the browser "calculates" that both vertical and horizontal scroll bars are required.

In the stylesheet you can set the min-width to a little bit less, e.g. 1260 to allow "space" for the vertical scroll bar.

Note: this behavior doesn't happen on a true 1280 screen, but is due to the scaling you use.

Thanks - yep, know it's fine at 100%.  It's a Lenovo touchscreen that recommends 150% (otherwise things are too small to click).  Trying it at 100% for a while - very small on this screen with my eyes!  I've just not had a webapp require this much room until now.

 

Setting it to 1260 has sorted it for now.  However, the logic in the stylesheet is currently "if the max you can display is 1280, then that will be the minimum I will display" (as you know).  Ergo, as soon as you get a vertical scroll, you'll always get horizontal on smaller desktops, and all ave vertical.

Share this post


Link to post
24 minutes ago, Wimpie said:

You are saying this is not more supported?

Sorry for the miscommunication/misconception.

This is still supported as before, but the auto selection of the GUI allow references to /mnt/ only which is the usual place to store vdisks. It prevents the casual user of making the wrong selections.

Special locations can be typed or copied in, though I agree, passthrough disks should be selectable too.

Share this post


Link to post
3 hours ago, bonienl said:

There is one 'true' issue. People using NFS shares may experience connection problems

 

And I'm one of those people :(

 

Please let me know if you need details about my NFS server setup so I can help fix this problem.

 

Share this post


Link to post
7 pages of issues in 9 hours. I'll postpone this update if you don't mind.

 

Have you actually read all 7 pages. Not all is about issues. Everything is working fine here, and i’am running alot of dockers, plug-ins and VMs.

 

 

Sent from my iPhone using Tapatalk

Share this post


Link to post
6 minutes ago, perhansen said:

 


Have you actually read all 7 pages. Not all is about issues. Everything is working fine here, and iam running alot og dockers plug-ins and VMs.


Sent from my iPhone using Tapatalk

 

 

Me too 😃 I run 3 VM's with GPU passthrough simultaneously along with 11 dockers, and have 13 plugins installed. The plugins are from the well known and very active users here so I never have any trouble with them.

Edited by GHunter

Share this post


Link to post
 
Me too  I run 3 VM's with GPU passthrough simultaneously along with 11 dockers, and have 13 plugins installed. The plugins are from the well known and very active users here so I never have any trouble with them.


Good to hear mate. I’am counting 19 plugins, 10 dockers and 4 VMs, one with passthrough.
I’am keeping a close eye on my memory usage, because its increasing more and more, but with video-surveillance, plex and other stuff running at same time, i think its gonna be okay. I kinda like the new black / orange theme, it’s growing on me over time.


Sent from my iPhone using Tapatalk

Share this post


Link to post
11 hours ago, eschultz said:

Did you check to see if there was a BIOS upgrade for you motherboard?  If so there's a good chance it'll fix the passthrough issues.

Thanks for the suggestion.  I haven't tried that but I will.

Share this post


Link to post

I read through these posts and also checked other threads, and am unable to find reference to an issue I'm experiencing since the upgrade.

 

I'm very glad that CPU pinning got some spotlight (I had used it before), but with one Docker in particular (SABnzbd), I am unable to remove "cpuset-cpus" from the extra parameters. Whether I change that parameter or erase it, it remains the same when the Docker or the server is restarted. And I keep getting warnings about having pinned CPUs defined twice.

 

Can anyone point me in the right direction?

Edited by PhantamaroK

Share this post


Link to post

Updated to 6.6.0, now none of my VM works.

MacOS - no output to VNC

Windows 10 - started to boot, but than BSOD with error Disk not accessible

Windows 7 - BSOD 0x000000A5

Windows XP - infinite boot logo

I have no devices passthrough configured.

Share this post


Link to post

Installed it last night, and so far so good. No problems with the Win7 vm I use regularly as a WMC head. 

 

I'm looking forward to building my 2nd Unraid box in the spring! You guys should sell this code to Ronco. "Set it and forget it"

Share this post


Link to post

Upgraded from 6.5.3 to 6.6.0 and the webgui shows “502 Bad Gateway”.

PHP errors?

 

Edited by mAYH3M

Share this post


Link to post
2 hours ago, mAYH3M said:

Upgraded from 6.5.3 to 6.6.0 and the webgui shows “502 Bad Gateway”.

PHP errors?

 

Please test with system booted in safe mode

Share this post


Link to post
8 minutes ago, bonienl said:

Please test with system booted in safe mode

Works when booted into Safe Mode with GUI and no plugins.

 

Booting into just safe mode without GUI and plugins also works.

 

Went back to 6.5.3 and ran CA common problems and uninstalled the non compatible plugins .On upgrade it shows this error and webgui shows 502 error.

 

87524DAE-6BE2-4BCE-BD7F-15B53EC5ACA2.jpeg

Share this post


Link to post

Hi,

 

I have had this problem twice since 6.6.0. Volumes are inaccessible since. I have to reboot.

 

[241269.176121] ------------[ cut here ]------------
[241269.176123] nfsd: non-standard errno: -103
[241269.176155] WARNING: CPU: 5 PID: 12157 at fs/nfsd/nfsproc.c:817 nfserrno+0x44/0x4a [nfsd]
[241269.176156] Modules linked in: macvlan xt_CHECKSUM iptable_mangle ipt_REJECT xt_nat ebtable_filter ebtables ip6table_filter ip6_tables veth vhost_net tun vhost tap ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs nfsd lockd grace sunrpc md_mod it87 hwmon_vid bonding r8169 mii intel_powerclamp coretemp kvm_intel kvm crc32c_intel i2c_i801 i2c_core intel_cstate mxm_wmi intel_uncore i7core_edac ahci wmi libahci pata_jmicron button pcc_cpufreq acpi_cpufreq [last unloaded: mii]
[241269.176193] CPU: 5 PID: 12157 Comm: nfsd Tainted: G          I       4.18.8-unRAID #1
[241269.176194] Hardware name: Gigabyte Technology Co., Ltd. X58A-UD7/X58A-UD7, BIOS F2 11/10/2009
[241269.176198] RIP: 0010:nfserrno+0x44/0x4a [nfsd]
[241269.176199] Code: c0 48 83 f8 22 75 e2 80 3d b3 06 01 00 00 bb 00 00 00 05 75 17 89 fe 48 c7 c7 3b 0a 1d a0 c6 05 9c 06 01 00 01 e8 8a 7c e8 e0 <0f> 0b 89 d8 5b c3 48 83 ec 18 31 c9 ba ff 07 00 00 65 48 8b 04 25
[241269.176231] RSP: 0000:ffffc90001227df0 EFLAGS: 00010286
[241269.176233] RAX: 0000000000000000 RBX: 0000000005000000 RCX: 0000000000000007
[241269.176234] RDX: 0000000000000000 RSI: ffff880199356470 RDI: ffff880199356470
[241269.176235] RBP: ffffc90001227e40 R08: 0000000000000003 R09: ffffffff82215d00
[241269.176237] R10: 000000000000060f R11: 000000000001e35c R12: ffff8801943a3c08
[241269.176238] R13: ffffffffa01d06d0 R14: 000000000000001c R15: ffffffffa01d02a0
[241269.176240] FS:  0000000000000000(0000) GS:ffff880199340000(0000) knlGS:0000000000000000
[241269.176241] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[241269.176243] CR2: 000014a4eacd60b0 CR3: 00000000806f2000 CR4: 00000000000006e0
[241269.176244] Call Trace:
[241269.176250]  nfsd_open+0x15e/0x17c [nfsd]
[241269.176255]  nfsd_commit+0x5a/0xbf [nfsd]
[241269.176259]  nfsd3_proc_commit+0x65/0x69 [nfsd]
[241269.176263]  nfsd_dispatch+0xb4/0x169 [nfsd]
[241269.176275]  svc_process+0x4b5/0x666 [sunrpc]
[241269.176281]  ? nfsd_destroy+0x48/0x48 [nfsd]
[241269.176284]  nfsd+0xeb/0x142 [nfsd]
[241269.176288]  kthread+0x10b/0x113
[241269.176291]  ? kthread_flush_work_fn+0x9/0x9
[241269.176295]  ret_from_fork+0x35/0x40
[241269.176298] ---[ end trace d6f4f9a9f4819224 ]---

 

Share this post


Link to post
On 9/19/2018 at 8:35 PM, limetech said:
  • webgui: Show accumulated encryption status

Upgrade went perfectly smooth, but i can't seem to find where / what this mentioned change is.

 

EDIT: gotta revert the "perfectly smooth" part; experiencing similar errors as others where the NAS isn't reachable over the network after running fine for some time

Edited by grubFX
problems occurred: randomly not reachable until rebooted

Share this post


Link to post
On 9/23/2018 at 11:25 AM, bonienl said:

It does start faster due to docker containers now being started in the background, while the system is booting up. This would be specially noticeable when many containers with autostart are present.

 

Well certainly a welcome improvement!

 

Just need to sort out the way we login and it’s be a perfect package for me.

 

 

 

On 9/23/2018 at 11:24 AM, Cessquill said:

You're running pfSense? I'd be interested (in a separate thread) how you're getting on.  I've just set it up on a baremetal server - too inexperienced to risk putting it all in one box.

 

 

It’s been running absolutlely perfectly for over a year now. Bit of a pain loosing internet whilst the machine restarts but other than that 99.9% uptime.

 

Other than the BIOS update I did preventing my NIC from working in the server anymore it’s been flawless. Up to date quad NIC bought so should resolve that one tomorrow..!

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.