Unraid OS version 6.6.1 available


limetech

Recommended Posts

18 minutes ago, Can0nfan said:

I think I finally figured out the issue here @limetech on my server 'unRAIDPro' that this user/ permissions issue was happening on.

my setup that i had this issue on was
unRAIDPlus VM with NFS mounts to unRAIDPro's /mnt/user/Media

unRAIDPlus unassigned devices SMB mount to unRAIDPro /mnt/user/Media

 

I unmounted the SMB from unassigned devices and mounted as NFS and I have a solid 6 hours of uptime (previous record was 2hrs 45min before the user folder permissions issue)

 

never had an issue access same share via SMB and NFS prior to 6.6 so looks like a new bug I will submit it as a bug report

 Seems good, I haven't NFS issue, my NFS share point exactly no SMB share enable.

Link to comment
8 minutes ago, Benson said:

 Seems good, I haven't NFS issue, my NFS share point exactly no SMB share enable.

yeah looks like others have found NFS itself is crashing. remove any SMB shares from unassigned devices if there is also a NFS mount to same share

 

i have to use SMB as NFS doesnt run well on all my clients. SMB does for those that NFS doesnt

Edited by Can0nfan
update info
Link to comment
5 minutes ago, Can0nfan said:

yeah looks like others have found NFS itself is crashing. looks like under Settings->NFS and setting Tunable (fuse_remember): to 0 should alleviate the issue

but also remove any SMB shares from unassigned devices if there is also a NFS mount to same share

Thsoe are Unraid user/disk share, not sure have different or not FYR.

Link to comment
4 hours ago, Benson said:

Thsoe are Unraid user/disk share, not sure have different or not FYR.

@limetech NFS is still crashing.....lasted 11hrs this time this is killing the user folder for some reason....i hope you and the team can find out whats causing this and get it fixed ASAP its very annoying


Sep 30 23:23:56 Thor kernel: ------------[ cut here ]------------
Sep 30 23:23:56 Thor kernel: nfsd: non-standard errno: -103
Sep 30 23:23:56 Thor kernel: WARNING: CPU: 1 PID: 6507 at fs/nfsd/nfsproc.c:817 nfserrno+0x44/0x4a [nfsd]
Sep 30 23:23:56 Thor kernel: Modules linked in: xt_nat macvlan xt_CHECKSUM iptable_mangle ipt_REJECT ebtable_filter ebtables ip6table_filter ip6_tables vhost_net tun vhost tap ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat arc4 ecb md4 sha512_ssse3 sha512_generic cmac cifs ccm xfs nfsd lockd grace sunrpc md_mod i915 i2c_algo_bit iosf_mbi drm_kms_helper drm intel_gtt agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd cryptd mpt3sas glue_helper alx intel_cstate intel_uncore intel_rapl_perf ahci raid_class libahci scsi_transport_sas mxm_wmi i2c_i801 mdio i2c_core video wmi mlx4_core backlight thermal
Sep 30 23:23:56 Thor kernel: button acpi_pad pcc_cpufreq fan
Sep 30 23:23:56 Thor kernel: CPU: 1 PID: 6507 Comm: nfsd Not tainted 4.18.10-unRAID #2
Sep 30 23:23:56 Thor kernel: Hardware name: MSI MS-7978/H170 GAMING M3 (MS-7978), BIOS C.B0 01/25/2018
Sep 30 23:23:56 Thor kernel: RIP: 0010:nfserrno+0x44/0x4a [nfsd]
Sep 30 23:23:56 Thor kernel: 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 9a 47 a0 c6 05 9c 06 01 00 01 e8 3b ed bd e0 <0f> 0b 89 d8 5b c3 48 83 ec 18 31 c9 ba ff 07 00 00 65 48 8b 04 25 
Sep 30 23:23:56 Thor kernel: RSP: 0018:ffffc9000377bdc0 EFLAGS: 00010282
Sep 30 23:23:56 Thor kernel: RAX: 0000000000000000 RBX: 0000000005000000 RCX: 0000000000000007
Sep 30 23:23:56 Thor kernel: RDX: 0000000000000000 RSI: ffff88086dc56470 RDI: ffff88086dc56470
Sep 30 23:23:56 Thor kernel: RBP: ffffc9000377be10 R08: 0000000000000003 R09: ffffffff8220d400
Sep 30 23:23:56 Thor kernel: R10: 0000000000000445 R11: 0000000000015a7c R12: ffff880845a49c08
Sep 30 23:23:56 Thor kernel: R13: 000000001373b000 R14: ffff880845a49d68 R15: 0000000000000005
Sep 30 23:23:56 Thor kernel: FS: 0000000000000000(0000) GS:ffff88086dc40000(0000) knlGS:0000000000000000
Sep 30 23:23:56 Thor kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Sep 30 23:23:56 Thor kernel: CR2: 000055d8c34aa2f8 CR3: 0000000001e0a002 CR4: 00000000003626e0
Sep 30 23:23:56 Thor kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Sep 30 23:23:56 Thor kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Sep 30 23:23:56 Thor kernel: Call Trace:
Sep 30 23:23:56 Thor kernel: nfsd_open+0x15e/0x17c [nfsd]
Sep 30 23:23:56 Thor kernel: nfsd_read+0x45/0xec [nfsd]
Sep 30 23:23:56 Thor kernel: nfsd3_proc_read+0x95/0xda [nfsd]
Sep 30 23:23:56 Thor kernel: nfsd_dispatch+0xb4/0x169 [nfsd]
Sep 30 23:23:56 Thor kernel: svc_process+0x4b5/0x666 [sunrpc]
Sep 30 23:23:56 Thor kernel: ? nfsd_destroy+0x48/0x48 [nfsd]
Sep 30 23:23:56 Thor kernel: nfsd+0xeb/0x142 [nfsd]
Sep 30 23:23:56 Thor kernel: kthread+0x10b/0x113
Sep 30 23:23:56 Thor kernel: ? kthread_flush_work_fn+0x9/0x9
Sep 30 23:23:56 Thor kernel: ret_from_fork+0x35/0x40
Sep 30 23:23:56 Thor kernel: ---[ end trace cd5759a6b02d0b74 ]---
Sep 30 23:44:16 Thor sshd[22182]: SSH: Server;Ltype: Version;Remote: 10.0.0.10-65250;Protocol: 2.0;Client: OpenSSH_7.7
Sep 30 23:44:16 Thor sshd[22182]: SSH: Server;Ltype: Kex;Remote: 10.0.0.10-65250;Enc: [email protected];MAC: <implicit>;Comp: none [preauth]
Sep 30 23:44:16 Thor sshd[22182]: SSH: Server;Ltype: Authname;Remote: 10.0.0.10-65250;Name: root [preauth]
Sep 30 23:44:20 Thor sshd[22182]: Accepted password for root from 10.0.0.10 port 65250 ssh2
Sep 30 23:46:53 Thor emhttpd: req (7): startState=STARTED&cmdStop=Stop&csrf_token=****************&csrf_token=****************
Sep 30 23:46:53 Thor emhttpd: Spinning up all drives...
Sep 30 23:46:53 Thor emhttpd: shcmd (151): /usr/sbin/hdparm -S0 /dev/sdo
Sep 30 23:46:53 Thor kernel: mdcmd (48): nocheck 
Sep 30 23:46:53 Thor kernel: md: nocheck_array: check not active
Sep 30 23:46:53 Thor kernel: mdcmd (49): spinup 0
Sep 30 23:46:53 Thor kernel: mdcmd (50): spinup 1
Sep 30 23:46:53 Thor kernel: mdcmd (51): spinup 2
Sep 30 23:46:53 Thor kernel: mdcmd (52): spinup 3
Sep 30 23:46:53 Thor kernel: mdcmd (53): spinup 4
Sep 30 23:46:53 Thor kernel: mdcmd (54): spinup 5
Sep 30 23:46:53 Thor kernel: mdcmd (55): spinup 6
Sep 30 23:46:53 Thor kernel: mdcmd (56): spinup 7
Sep 30 23:46:53 Thor kernel: mdcmd (57): spinup 8
Sep 30 23:46:53 Thor kernel: mdcmd (58): spinup 9
Sep 30 23:46:53 Thor kernel: mdcmd (59): spinup 10
Sep 30 23:46:53 Thor kernel: mdcmd (60): spinup 29
Sep 30 23:46:53 Thor root: 
Sep 30 23:46:53 Thor root: /dev/sdo:
Sep 30 23:46:53 Thor root: setting standby to 0 (off)
Sep 30 23:46:53 Thor emhttpd: shcmd (152): /usr/sbin/hdparm -S0 /dev/sdn
Sep 30 23:46:53 Thor root: 
Sep 30 23:46:53 Thor root: /dev/sdn:
Sep 30 23:46:53 Thor root: setting standby to 0 (off)
Sep 30 23:46:54 Thor emhttpd: Stopping services...
Sep 30 23:46:54 Thor emhttpd: shcmd (154): /etc/rc.d/rc.libvirt stop
Sep 30 23:46:54 Thor root: Domain e04658c0-5265-ce54-594e-60ed11278970 is being shutdown
Sep 30 23:46:54 Thor root: 

Link to comment

Not sure what happened, but went from 6.6 rc1 to 6.6.1 and it totally blew out my SSD drive. I had corruption errors out the gazoooo and many many many Read-only messages when I attempted to delete files. 

Luckily I was able to simply unassigned my SSD drive, fire up Unassigned Devices, format my drive to BTRS then bring it back online. 

I re-loaded a previous backup from Squids Backup/Restore app and did some App installing to get back to where I was. 

 

Normally on every update I manually shutdown all my dockers and then shut down the array then simply hit reboot or shutdown and watch the screen as it comes up. I'm guessing maybe the docker hung and went crazy on my files. 

 

I didn't save any logs or pull a diagnostic file. However who knows what happened, but just want others to know shut things down and play it smart and back things up before leaping each time. :D

Link to comment

Installed 6.6.1 no problems but I have my parity check set for once a year on the 1st. I set this because I had been adding larger drives the last few months and just rebuilding drives. My last drive rebuild was done on Sept. 29th  and once Oct. 1st came I noticed I was doing a parity check and yet the schedule still has my check at Jan. 1st. No big deal but don't want to torture my drives any more than necessary.

Just thought I would add this to the thread and see if any one else has had this happen.

  • Upvote 1
Link to comment

Another unscheduled parity check here w/6.6.1. I have it set Custom: 07:00, Wednesday of the first week in Mar, Jun, Sep, and Dec. It started up this morning at 7, which is all correct except for the month. I toggled a couple of the variables and re-Apply'd. (EDIT: I changed the time to 10:00, saved, and it just started up again at 10 even though it's still the wrong month. So it doesn't seem to be a saved data format issue.)

 

Aside from this, it's been very smooth sailing. The new UI looks great on a color calibrated display.

Edited by KernelG
Link to comment

Can't see it in this release, but can we have this hot-fix merged with the next release please?
Docker sometimes erroneously pick up extra parameters as a possible "Bash command execution or redirection", and prevents it from starting.
The hotfix Squid wrote corrects it.
 

 

Link to comment

Updated from 6.6 rc4 to 6.6.1 no problem. I have noticed a text problem on the upper top right where it say's "Uptime x minutes" the bottom 1/3rd is covered so you can't see it. Also on the Dashboard Apps section the second line of text on any apps that have more than one line is cutoff about 1/3rd on the bottom of second line of text. My monitor resolution is 4k. Thanks for all your hard work guy's!

Edited by jpowell8672
Added another fix needed
Link to comment
On 10/6/2018 at 11:20 PM, MadeOfCard said:

Is there any way to contribute to the front end? I would love to make this responsive.


Sent from my iPhone using Tapatalk

yeah, I was asking myself the same thing a while back.... I would love to contribute to this :)

 

btw, updated my server yesterday from 6.6. Everything is functioning as it was before (server, dockers, VMs, etc). Thanks!

Link to comment
52 minutes ago, majorspawn said:

is there any way to revert to the old gui look? im so use to the old one.....

Not unless you want to revert to the previous Unraid release?

 

you might want to check out the different themes?  The Azure one for instance is closer to the old style.

Link to comment
  • limetech unfeatured and unpinned this topic

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.