Jump to content
limetech

Unraid OS version 6.7.2 available

151 posts in this topic Last Reply

Recommended Posts

I apologize if I am completely missing them.  But are there any update notes anywhere to share what has been changed in 6.7.2?

Share this post


Link to post
On 6/25/2019 at 3:50 PM, limetech said:

Version 6.7.2 2019-06-25

Base distro:

  • kernel-firmware: version 20190620_7ae3a09
  • php version: 7.2.19 (restore sqlite support)
  • sqlite version: 3.28.0

Linux kernel:

  • version: 4.19.56

 

Share this post


Link to post
12 minutes ago, sekrit said:

I apologize if I am completely missing them.  But are there any update notes anywhere to share what has been changed in 6.7.2?

The first post of any thread where LimeTech announce a new release normally contains the release notes for that release.

Share this post


Link to post
On 7/8/2019 at 4:18 PM, chris1259 said:

Created a new v6.7.0, copied my config onto the USB, but all issues remain. The only plug-in that was upgraded since June 18th, 2019 was Community Applications and i doubt that's the issue. There must be a hardware issue with the machine. remove host keys from C:\\Users\\Administrator/.ssh/known_hosts and now i can connect to the web GUI and ssh to the machine again. I will report back next week if everything is still working.

After 6 days the server is still stable on v6.7.0. Something that i can't track down in v6.7.1 or v6.7.2, network related, broke for me.

Share this post


Link to post
1 hour ago, chris1259 said:

After 6 days the server is still stable on v6.7.0. Something that i can't track down in v6.7.1 or v6.7.2, network related, broke for me.

 

Make a copy of /config/network. cfg and then delete that file from the flash drive.  Now reboot the server.  

Share this post


Link to post

Hi I'm currently running issues with my unraid server where I'm having constant random reboot. Initially it would reboot once or twice a day. Lasting sometimes a day or even just a few hours.

 

I then tried disabling the Spectre/Meltdown Mitigations but it would still reboot, this time longer now, after about a week of running. Happened twice now.

 

I'm running both dockers and VMs, and tried to isolate my running VMs and shutdown the dockers but it would still reboot. Did a memtest but no errors was found.

 

Any other people having same issues?

Share this post


Link to post
7 hours ago, laurenceco said:

Hi I'm currently running issues with my unraid server where I'm having constant random reboot. Initially it would reboot once or twice a day. Lasting sometimes a day or even just a few hours.

 

I then tried disabling the Spectre/Meltdown Mitigations but it would still reboot, this time longer now, after about a week of running. Happened twice now.

 

I'm running both dockers and VMs, and tried to isolate my running VMs and shutdown the dockers but it would still reboot. Did a memtest but no errors was found.

 

Any other people having same issues?

Rebooting is almost certainly a hardware issue. Go to Tools-diagnostics and attach the complete Diagnostics zip file to your next post. 

Share this post


Link to post
18 hours ago, Frank1940 said:

 

Make a copy of /config/network. cfg and then delete that file from the flash drive.  Now reboot the server.  

Thanks. I will try that after i re-run the upgrade and report back the results.

Share this post


Link to post
3 hours ago, laurenceco said:

Hi attaching my diagnostics. Hopefully you can help and point to me which hardware is causing issues. Thanks.

tower-diagnostics-20190715-1248.zip 76.74 kB · 1 download

Enable the Syslog server to save the syslog to the flash drive (Settings Tab), then post the save syslog after it crashes again.

Share this post


Link to post
Posted (edited)

I upgraded to 6.7.2 from 6.6.6 about a week ago and all seems well. Before that I replaced the Marvell SATA controllers with an LSI Broadcom SAS HBA. Disk access times are better too.

 

I did have one anomaly. Sometime during the early morning I could not access shared from any computer on my network.  The webgui was still running but show zero CPU utilization.  I tried to shutdown,  but all I got were the standard shutdown warnings and nothing happened.  After about 45 minutes I forced it down and restarted.  

 

Everything came back up but it had to do a parity check. I've never had this happen before.

 

Dale

Edited by dchamb

Share this post


Link to post
3 hours ago, dchamb said:

I upgraded to 6.7.2 from 6.6.6 about a week ago and all seems well. Before that I replaced the Marvell SATA controllers with an LSI Broadcom SAS HBA. Disk access times are better too.

 

I did have one anomaly. Sometime during the early morning I could not access shared from any computer on my network.  The webgui was still running but show zero CPU utilization.  I tried to shutdown,  but all I got were the standard shutdown warnings and nothing happened.  After about 45 minutes I forced it down and restarted.  

 

Everything came back up but it had to do a parity check. I've never had this happen before.

 

Dale

IF this happens again, start a new thread in the "General Support" sub-forum.  Be sure to attempt to get a Diagnostics file     Tools     >>>>   Diagnostics    before you try a reboot.  I would tell you to start the  Syslog Server       Settings   >>>    Syslog Server     with the   'Mirror syslog to flash:'   setup but it can be hard on your flash drive unless you feel it might happen with a few days of today.

Share this post


Link to post
6 hours ago, Frank1940 said:

IF this happens again, start a new thread in the "General Support" sub-forum.  Be sure to attempt to get a Diagnostics file     Tools     >>>>   Diagnostics    before you try a reboot.  I would tell you to start the  Syslog Server       Settings   >>>    Syslog Server     with the   'Mirror syslog to flash:'   setup but it can be hard on your flash drive unless you feel it might happen with a few days of today.

That's the problem. This has been the only time it happened so I have no basis to determine when it might happen again. If it does, I believe there is close to a zero chance that getting a Diagnostics file saved since everything appeared to be down before the reboot. There was a syslog from before and after the crash though.

Share this post


Link to post
On 7/15/2019 at 11:22 PM, dchamb said:

That's the problem. This has been the only time it happened so I have no basis to determine when it might happen again. If it does, I believe there is close to a zero chance that getting a Diagnostics file saved since everything appeared to be down before the reboot. There was a syslog from before and after the crash though.

Turn on the Syslog server    Settings   >>> Syslog Server   and set it up to "Mirror syslog to flash:".   Turn on 'Help' for how to do this and the warnings.  

Share this post


Link to post

Frank1940,

 

Thanks! It is now set if this happens again. I've attached the syslog from the first and only time it failed. Not sure what to make of it except I see a general protection fault (which to me usually indicates a memory leak) and an error on the SSD drive, but nothing further shows up on the SSD. Ran SMART tests and it shows fine. 

 

Dale

tower-diagnostics-20190712-1413.zip

Share this post


Link to post
Posted (edited)

VM only shows up on passed GPU if Unraid has a fresh boot

 

Linux Mint 19.2

 

A reboot of VM causes the VM not to show up on pass thru GPU screen.

 

Unraid 6.7.2

 

I never had a problem with passing this GPU GT240 before.   Have not tried the current VM on a different version of Unraid to see if problem goes away.  I installed it fresh after I upgraded to Unraid 6.7.2.

 

Am going to try a different Linux to see if I have the same problem.

 

On another note I got my other Windows PC to work with Barrier and the VM to use just one mouse and keyboard.

 

 

 

VM XML and diag file in her along with log.

 


I tried ElementaryOS, it did the same thing once it installed and then wanted to reboot.  See the Unraid log during this:

Jul 27 15:57:57 UNRAID kernel: handlers:
Jul 27 15:57:57 UNRAID kernel: [<000000008309db2f>] vfio_intx_handler
Jul 27 15:57:57 UNRAID kernel: Disabling IRQ #16
Jul 27 15:57:58 UNRAID kernel: usb 8-2: reset full-speed USB device number 2 using xhci_hcd
Jul 27 15:57:58 UNRAID kernel: usb 8-2: reset full-speed USB device number 2 using xhci_hcd
Jul 27 15:57:59 UNRAID kernel: irq 16: nobody cared (try booting with the "irqpoll" option)
Jul 27 15:57:59 UNRAID kernel: CPU: 5 PID: 0 Comm: swapper/5 Not tainted 4.19.56-Unraid #1
Jul 27 15:57:59 UNRAID kernel: Hardware name: To be filled by O.E.M. To be filled by O.E.M./M5A97 R2.0, BIOS 2603 06/26/2015
Jul 27 15:57:59 UNRAID kernel: Call Trace:
Jul 27 15:57:59 UNRAID kernel: <IRQ>
Jul 27 15:57:59 UNRAID kernel: dump_stack+0x5d/0x79
Jul 27 15:57:59 UNRAID kernel: __report_bad_irq+0x32/0xac
Jul 27 15:57:59 UNRAID kernel: note_interrupt+0x1d3/0x224
Jul 27 15:57:59 UNRAID kernel: handle_irq_event_percpu+0x4c/0x6a
Jul 27 15:57:59 UNRAID kernel: handle_irq_event+0x33/0x51
Jul 27 15:57:59 UNRAID kernel: handle_fasteoi_irq+0x92/0x102
Jul 27 15:57:59 UNRAID kernel: handle_irq+0x1c/0x1f
Jul 27 15:57:59 UNRAID kernel: do_IRQ+0x43/0xc7
Jul 27 15:57:59 UNRAID kernel: common_interrupt+0xf/0xf
Jul 27 15:57:59 UNRAID kernel: </IRQ>
Jul 27 15:57:59 UNRAID kernel: RIP: 0010:native_safe_halt+0xe/0xf
Jul 27 15:57:59 UNRAID kernel: Code: 60 02 df f0 83 44 24 fc 00 48 8b 00 a8 08 74 0b 65 81 25 a7 fc 9b 7e ff ff ff 7f c3 e9 07 00 00 00 0f 00 2d ac 14 5b 00 fb f4 <c3> e9 07 00 00 00 0f 00 2d 9d 14 5b 00 f4 c3 e8 bb 36 a4 ff 65 8b
Jul 27 15:57:59 UNRAID kernel: RSP: 0018:ffffc900031bfe48 EFLAGS: 00000246 ORIG_RAX: ffffffffffffffdb
Jul 27 15:57:59 UNRAID kernel: RAX: 0000000080000000 RBX: ffff88882bbfa064 RCX: 000000000000001f
Jul 27 15:57:59 UNRAID kernel: RDX: ffff88882fb40000 RSI: ffffffff81e5cf40 RDI: ffff88882bbfa064
Jul 27 15:57:59 UNRAID kernel: RBP: 0000000000000001 R08: 0000000000000002 R09: 00000000000203c0
Jul 27 15:57:59 UNRAID kernel: R10: 0000000000000000 R11: 000004ae8c810dc6 R12: ffff88882bbfa000
Jul 27 15:57:59 UNRAID kernel: R13: 0000000000000001 R14: ffffffff81e5cfb8 R15: 0000000000000000
Jul 27 15:57:59 UNRAID kernel: acpi_safe_halt+0x15/0x1f
Jul 27 15:57:59 UNRAID kernel: acpi_idle_enter+0x1dd/0x21b
Jul 27 15:57:59 UNRAID kernel: cpuidle_enter_state+0xa1/0x141
Jul 27 15:57:59 UNRAID kernel: do_idle+0x192/0x20e
Jul 27 15:57:59 UNRAID kernel: cpu_startup_entry+0x6a/0x6c
Jul 27 15:57:59 UNRAID kernel: start_secondary+0x197/0x1b2
Jul 27 15:57:59 UNRAID kernel: secondary_startup_64+0xa4/0xb0
Jul 27 15:57:59 UNRAID kernel: handlers:
Jul 27 15:57:59 UNRAID kernel: [<000000008309db2f>] vfio_intx_handler
Jul 27 15:57:59 UNRAID kernel: Disabling IRQ #16
Jul 27 15:58:47 UNRAID kernel: usb 8-2: reset full-speed USB device number 2 using xhci_hcd
Jul 27 15:58:47 UNRAID kernel: usb 8-2: device firmware changed
Jul 27 15:58:47 UNRAID kernel: usb 8-2: USB disconnect, device number 2
Jul 27 15:58:47 UNRAID kernel: usb 8-2: new full-speed USB device number 3 using xhci_hcd
Jul 27 15:58:48 UNRAID kernel: logitech-djreceiver 0003:046D:C52B.0011: hiddev98,hidraw4: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:03:00.0-2/input2
Jul 27 15:58:50 UNRAID kernel: input: Logitech M215 2nd Gen as /devices/pci0000:00/0000:00:05.0/0000:03:00.0/usb8/8-2/8-2:1.2/0003:046D:C52B.0011/0003:046D:401B.0012/input/input20
Jul 27 15:58:50 UNRAID kernel: logitech-hidpp-device 0003:046D:401B.0012: input,hidraw5: USB HID v1.11 Mouse [Logitech M215 2nd Gen] on usb-0000:03:00.0-2:1
Jul 27 15:58:51 UNRAID kernel: input: Logitech K330 as /devices/pci0000:00/0000:00:05.0/0000:03:00.0/usb8/8-2/8-2:1.2/0003:046D:C52B.0011/0003:046D:4016.0013/input/input21
Jul 27 15:58:51 UNRAID kernel: logitech-hidpp-device 0003:046D:4016.0013: input,hidraw6: USB HID v1.11 Keyboard [Logitech K330] on usb-0000:03:00.0-2:2
Jul 27 16:00:21 UNRAID avahi-daemon[2987]: Interface vnet0.IPv6 no longer relevant for mDNS.
Jul 27 16:00:21 UNRAID avahi-daemon[2987]: Leaving mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe4d:2674.
Jul 27 16:00:21 UNRAID kernel: br0: port 2(vnet0) entered disabled state
Jul 27 16:00:21 UNRAID kernel: device vnet0 left promiscuous mode
Jul 27 16:00:21 UNRAID kernel: br0: port 2(vnet0) entered disabled state
Jul 27 16:00:21 UNRAID avahi-daemon[2987]: Withdrawing address record for fe80::fc54:ff:fe4d:2674 on vnet0.
Jul 27 16:00:21 UNRAID kernel: vfio-pci 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Jul 27 16:00:32 UNRAID kernel: vfio-pci 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Jul 27 16:00:32 UNRAID kernel: br0: port 2(vnet0) entered blocking state
Jul 27 16:00:32 UNRAID kernel: br0: port 2(vnet0) entered disabled state
Jul 27 16:00:32 UNRAID kernel: device vnet0 entered promiscuous mode
Jul 27 16:00:32 UNRAID kernel: br0: port 2(vnet0) entered blocking state
Jul 27 16:00:32 UNRAID kernel: br0: port 2(vnet0) entered forwarding state
Jul 27 16:00:34 UNRAID avahi-daemon[2987]: Joining mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe4d:2674.
Jul 27 16:00:34 UNRAID avahi-daemon[2987]: New relevant interface vnet0.IPv6 for mDNS.
Jul 27 16:00:34 UNRAID avahi-daemon[2987]: Registering new address record for fe80::fc54:ff:fe4d:2674 on vnet0.*.
Jul 27 16:00:34 UNRAID kernel: vfio-pci 0000:00:14.2: enabling device (0000 -> 0002)
Jul 27 16:00:34 UNRAID acpid: input device has been disconnected, fd 9
Jul 27 16:00:34 UNRAID kernel: usb 8-2: reset full-speed USB device number 3 using xhci_hcd
Jul 27 16:00:35 UNRAID kernel: usb 8-2: reset full-speed USB device number 3 using xhci_hcd
Jul 27 16:01:10 UNRAID avahi-daemon[2987]: Interface vnet0.IPv6 no longer relevant for mDNS.
Jul 27 16:01:10 UNRAID avahi-daemon[2987]: Leaving mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe4d:2674.
Jul 27 16:01:10 UNRAID kernel: br0: port 2(vnet0) entered disabled state
Jul 27 16:01:10 UNRAID kernel: device vnet0 left promiscuous mode
Jul 27 16:01:10 UNRAID kernel: br0: port 2(vnet0) entered disabled state
Jul 27 16:01:10 UNRAID avahi-daemon[2987]: Withdrawing address record for fe80::fc54:ff:fe4d:2674 on vnet0.
Jul 27 16:01:10 UNRAID kernel: logitech-djreceiver 0003:046D:C52B.0016: hiddev98,hidraw4: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:03:00.0-2/input2
Jul 27 16:01:11 UNRAID kernel: input: Logitech M215 2nd Gen as /devices/pci0000:00/0000:00:05.0/0000:03:00.0/usb8/8-2/8-2:1.2/0003:046D:C52B.0016/0003:046D:401B.0017/input/input22
Jul 27 16:01:11 UNRAID kernel: logitech-hidpp-device 0003:046D:401B.0017: input,hidraw5: USB HID v1.11 Mouse [Logitech M215 2nd Gen] on usb-0000:03:00.0-2:1
Jul 27 16:01:11 UNRAID kernel: vfio-pci 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Jul 27 16:01:12 UNRAID kernel: input: Logitech K330 as /devices/pci0000:00/0000:00:05.0/0000:03:00.0/usb8/8-2/8-2:1.2/0003:046D:C52B.0016/0003:046D:4016.0018/input/input23
Jul 27 16:01:12 UNRAID kernel: logitech-hidpp-device 0003:046D:4016.0018: input,hidraw6: USB HID v1.11 Keyboard [Logitech K330] on usb-0000:03:00.0-2:2
Jul 27 16:01:57 UNRAID kernel: vfio-pci 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Jul 27 16:01:57 UNRAID kernel: br0: port 2(vnet0) entered blocking state
Jul 27 16:01:57 UNRAID kernel: br0: port 2(vnet0) entered disabled state
Jul 27 16:01:57 UNRAID kernel: device vnet0 entered promiscuous mode
Jul 27 16:01:57 UNRAID kernel: br0: port 2(vnet0) entered blocking state
Jul 27 16:01:57 UNRAID kernel: br0: port 2(vnet0) entered forwarding state
Jul 27 16:01:57 UNRAID kernel: br0: port 2(vnet0) entered disabled state
Jul 27 16:01:57 UNRAID kernel: device vnet0 left promiscuous mode
Jul 27 16:01:57 UNRAID kernel: br0: port 2(vnet0) entered disabled state
Jul 27 16:01:58 UNRAID kernel: vfio-pci 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Jul 27 16:02:10 UNRAID kernel: vfio-pci 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
Jul 27 16:02:10 UNRAID kernel: br0: port 2(vnet0) entered blocking state
Jul 27 16:02:10 UNRAID kernel: br0: port 2(vnet0) entered disabled state
Jul 27 16:02:10 UNRAID kernel: device vnet0 entered promiscuous mode
Jul 27 16:02:10 UNRAID kernel: br0: port 2(vnet0) entered blocking state
Jul 27 16:02:10 UNRAID kernel: br0: port 2(vnet0) entered forwarding state
Jul 27 16:02:10 UNRAID dhcpcd[1679]: vnet0: new hardware address: fe:54:00:4d:26:74
Jul 27 16:02:11 UNRAID avahi-daemon[2987]: Joining mDNS multicast group on interface vnet0.IPv6 with address fe80::fc54:ff:fe4d:2674.
Jul 27 16:02:11 UNRAID avahi-daemon[2987]: New relevant interface vnet0.IPv6 for mDNS.
Jul 27 16:02:11 UNRAID avahi-daemon[2987]: Registering new address record for fe80::fc54:ff:fe4d:2674 on vnet0.*.
Jul 27 16:02:12 UNRAID kernel: vfio-pci 0000:00:14.2: enabling device (0000 -> 0002)
Jul 27 16:02:12 UNRAID acpid: input device has been disconnected, fd 9
Jul 27 16:02:12 UNRAID kernel: usb 8-2: reset full-speed USB device number 3 using xhci_hcd
Jul 27 16:02:13 UNRAID kernel: usb 8-2: reset full-speed USB device number 3 using xhci_hcd

 

unraid-diagnostics-20190727-2305.zip

Edited by Paul_Ber
Add some logs and diag files

Share this post


Link to post
6 hours ago, spamalam said:

Upgraded from 6.6.7 and I seem to have lost four disks.  Diagnostics attached.

beyonder-nas-diagnostics-20190730-0019.zip 211.03 kB · 3 downloads

Not seeing issues with a controllers, just looks like one is missing/not being detected, can you revert to 6.6.7 and confirm missing disks appear? If yes grab and post those diags.

Share this post


Link to post
On 7/14/2019 at 4:37 PM, Frank1940 said:

 

Make a copy of /config/network. cfg and then delete that file from the flash drive.  Now reboot the server.  

Renamed \\ServerName\flash\config\network.cfg to network.cfg.old, updated from v6.7.0 to v6.7.2 and rebooted. After 4 days it appears this has fixed the issue. If the issue returns i will report back. THANK YOU!

Share this post


Link to post

I recently upgraded from 6.5.3 to 6.7.2 and noticed that copying files from my cache drive (SSD) to the array has slowed down significantly. Previously I got transfer speeds of around 74 MB/s, now I'm getting 52 MB/s. I copy the files using Teracopy from my Win10 PC. This was very noticeable over a few file transfers.

 

To verify this, I copied a 6GB file under 6.7.2 and then downgraded back to 6.5.3 and copied the same file, and saw the speed difference. Is there anything I need to change under 6.7.2?

 

I've attached the diagnostic files under 6.7.2 and 6.5.3.

tower-diagnostics-6.7.2_Slow.zip tower-diagnostics-6.5.3_Fast.zip

Share this post


Link to post
7 minutes ago, sonofdbn said:

I recently upgraded from 6.5.3 to 6.7.2 and noticed that copying files from my cache drive (SSD) to the array has slowed down significantly. Previously I got transfer speeds of around 74 MB/s, now I'm getting 52 MB/s. I copy the files using Teracopy from my Win10 PC. This was very noticeable over a few file transfers.

 

To verify this, I copied a 6GB file under 6.7.2 and then downgraded back to 6.5.3 and copied the same file, and saw the speed difference. Is there anything I need to change under 6.7.2?

 

I've attached the diagnostic files under 6.7.2 and 6.5.3.

tower-diagnostics-6.7.2_Slow.zip 146.25 kB · 0 downloads tower-diagnostics-6.5.3_Fast.zip 145.36 kB · 0 downloads

There have been quite a few similar reports.    Hopefully LimeTech are looking into the cause so it gets fixed for a future release.

Share this post


Link to post
12 minutes ago, sonofdbn said:

I recently upgraded from 6.5.3 to 6.7.2 and noticed that copying files from my cache drive (SSD) to the array has slowed down significantly. Previously I got transfer speeds of around 74 MB/s, now I'm getting 52 MB/s. I copy the files using Teracopy from my Win10 PC. This was very noticeable over a few file transfers.

 

To verify this, I copied a 6GB file under 6.7.2 and then downgraded back to 6.5.3 and copied the same file, and saw the speed difference. Is there anything I need to change under 6.7.2?

 

I've attached the diagnostic files under 6.7.2 and 6.5.3.

tower-diagnostics-6.7.2_Slow.zip 146.25 kB · 0 downloads tower-diagnostics-6.5.3_Fast.zip 145.36 kB · 0 downloads

might be the same issue reported here:

https://forums.unraid.net/bug-reports/stable-releases/67x-very-slow-array-concurrent-performance-r605/

Share this post


Link to post
7 minutes ago, itimpi said:

There have been quite a few similar reports.    Hopefully LimeTech are looking into the cause so it gets fixed for a future release.

I missed those reports; at least it's not just me. I'll stay on 6.5.3 for now.

Share this post


Link to post
23 minutes ago, sonofdbn said:

I missed those reports; at least it's not just me. I'll stay on 6.5.3 for now.

You could go to 6.6.6.  Surprisingly, that was a really good release.

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.