vanes

Отлично, продолжай в том же духе.

Hi guys, need some help. I set up zfs-zed using this post Zed is working fine, but now my syslog full of this: Mar 6 07:41:54 unRaid zed[3601]: Invoking "all-syslog.sh" eid=82 pid=25649 Mar 6 07:41:54 unRaid zed: eid=82 class=config_sync pool_guid=0xD30AFB4571F3B450 Mar 6 07:41:54 unRaid zed[3601]: Finished "all-syslog.sh" eid=82 pid=25649 exit=0 Mar 6 07:46:57 unRaid zed[3601]: Invoking "all-syslog.sh" eid=83 pid=29036 Mar 6 07:46:57 unRaid zed: eid=83 class=config_sync pool_guid=0xD30AFB4571F3B450 Mar 6 07:46:57 unRaid zed[3601]: Finished "all-syslog.sh" eid=83 pid=29036 exit=0 Mar 6 07:52:00 unRaid zed[3601]: Invoking "all-syslog.sh" eid=84 pid=32653 Mar 6 07:52:00 unRaid zed: eid=84 class=config_sync pool_guid=0xD30AFB4571F3B450 Mar 6 07:52:00 unRaid zed[3601]: Finished "all-syslog.sh" eid=84 pid=32653 exit=0 Mar 6 07:57:03 unRaid zed[3601]: Invoking "all-syslog.sh" eid=85 pid=4478 Mar 6 07:57:03 unRaid zed: eid=85 class=config_sync pool_guid=0xD30AFB4571F3B450 Mar 6 07:57:03 unRaid zed[3601]: Finished "all-syslog.sh" eid=85 pid=4478 exit=0 Mar 6 08:02:05 unRaid zed[3601]: Invoking "all-syslog.sh" eid=86 pid=8041 Mar 6 08:02:05 unRaid zed: eid=86 class=config_sync pool_guid=0xD30AFB4571F3B450 Mar 6 08:02:05 unRaid zed[3601]: Finished "all-syslog.sh" eid=86 pid=8041 exit=0 Mar 6 08:07:08 unRaid zed[3601]: Invoking "all-syslog.sh" eid=87 pid=10773 Mar 6 08:07:08 unRaid zed: eid=87 class=config_sync pool_guid=0xD30AFB4571F3B450 Mar 6 08:07:08 unRaid zed[3601]: Finished "all-syslog.sh" eid=87 pid=10773 exit=0 Mar 6 08:12:11 unRaid zed[3601]: Invoking "all-syslog.sh" eid=88 pid=13372 Mar 6 08:12:11 unRaid zed: eid=88 class=config_sync pool_guid=0xD30AFB4571F3B450 Mar 6 08:12:11 unRaid zed[3601]: Finished "all-syslog.sh" eid=88 pid=13372 exit=0 Please help to stop zed spam syslog.

@Jcloud, please tell us about the support of the v3 protocol with this container. https://storj.io/blog/2018/10/introducing-the-storj-v3-white-paper/

@jang430 you dont need new hardware you cpu has Intel® HD Graphics P630 https://ark.intel.com/products/97476/Intel-Xeon-Processor-E3-1225-v6-8M-Cache-3-30-GHz- it support 10-bit H.265 4K https://www.intel.ru/content/www/ru/ru/architecture-and-technology/hd-graphics/hd-graphics-performance-guide.html u need just to set-up unraid and plex/emby to use it Xeon silver 4108 is ~30% faster and have no iGpu. Did u set up iGpu transcoding or you dont use HD Graphics P630 at all?

run these inside nextcloud docker container: cd /config/www/nextcloud/ sudo -u abc php7 occ files:scan --all

Seems fixed, now i can edit that template. My test was to add new virtio drivers, press update - that worked, no problem Good job

Then if i try to edit this VM and press update button - nothing happens.

Hi guys, i have some problems editing my vm template via gui. I make changes, then press Apply, and nothing happens. Tried to add virtio iso to vm, tried to swich i440fx from 2.11 to 3.0. Nothing worked, no errors, just nothing happens.. here is XML and diag. Windows 10.xml unraid-diagnostics.zip PS: my 6.5.3 xml from backup 6.5.3 Windows 10.xml PPS: i did some tests. Backed-up 6,6 xml to file, then deleted vm template from gui, recreated vm with my img file. VM does not boot (drops into uefi shell). Then i returned back 6.6xml using gui. 6.6 Windows 10.xml VM booted normaly. Now i can edit XML in gui, but after any edit i cant boot my VM (drops to uefi shell). need help 😃 UPD: if i swich to xml view and edit i440fx-2.1.1 to i440fx-3.0 this works. If i change in gui it doesn`t UPD2: I found what drops to uefi shell. The reason of wrong .img format. I use qcow2, vm was created with qcow2, and every time i save (update) my template via gui unraid write RAW format in xml config and vm drops to uefi.

I did another parity check, finished with no errors. Everything works fine. I keep watching log. unraid-diagnostics-20180813-1734.zip

what kind of tests should I do? Reconnect cable? Replace cable?

Hi guys, i need some help. Some days ago i precleared then added old hitachi drive to my array, and now i see some errors during parity check. Parity is fine files are fine... Aug 13 00:32:49 unRaid kernel: ata6.00: exception Emask 0x0 SAct 0x8000000 SErr 0x0 action 0x6 frozen Aug 13 00:32:49 unRaid kernel: ata6.00: failed command: READ FPDMA QUEUED Aug 13 00:32:49 unRaid kernel: ata6.00: cmd 60/08:d8:c0:00:00/00:00:00:00:00/40 tag 27 ncq dma 4096 in Aug 13 00:32:49 unRaid kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Aug 13 00:32:49 unRaid kernel: ata6.00: status: { DRDY } Aug 13 00:32:49 unRaid kernel: ata6: hard resetting link Aug 13 00:32:49 unRaid kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Aug 13 00:32:49 unRaid kernel: ata6.00: configured for UDMA/133 Aug 13 00:32:49 unRaid kernel: ata6: EH complete Aug 13 00:37:51 unRaid kernel: ata6.00: exception Emask 0x0 SAct 0x400008 SErr 0x0 action 0x6 frozen Aug 13 00:37:51 unRaid kernel: ata6.00: failed command: READ FPDMA QUEUED Aug 13 00:37:51 unRaid kernel: ata6.00: cmd 60/00:18:78:22:79/02:00:07:00:00/40 tag 3 ncq dma 262144 in Aug 13 00:37:51 unRaid kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Aug 13 00:37:51 unRaid kernel: ata6.00: status: { DRDY } Aug 13 00:37:51 unRaid kernel: ata6.00: failed command: READ FPDMA QUEUED Aug 13 00:37:51 unRaid kernel: ata6.00: cmd 60/00:b0:78:20:79/02:00:07:00:00/40 tag 22 ncq dma 262144 in Aug 13 00:37:51 unRaid kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Aug 13 00:37:51 unRaid kernel: ata6.00: status: { DRDY } Aug 13 00:37:51 unRaid kernel: ata6: hard resetting link Aug 13 00:37:52 unRaid kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Aug 13 00:37:52 unRaid kernel: ata6.00: configured for UDMA/133 Aug 13 00:37:52 unRaid kernel: ata6: EH complete Aug 13 00:53:14 unRaid kernel: ata6.00: exception Emask 0x0 SAct 0x4 SErr 0x0 action 0x6 frozen Aug 13 00:53:14 unRaid kernel: ata6.00: failed command: READ FPDMA QUEUED Aug 13 00:53:14 unRaid kernel: ata6.00: cmd 60/00:10:98:44:2e/02:00:02:00:00/40 tag 2 ncq dma 262144 in Aug 13 00:53:14 unRaid kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Aug 13 00:53:14 unRaid kernel: ata6.00: status: { DRDY } Aug 13 00:53:14 unRaid kernel: ata6: hard resetting link Aug 13 00:53:15 unRaid kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Aug 13 00:53:15 unRaid kernel: ata6.00: configured for UDMA/133 Aug 13 00:53:15 unRaid kernel: ata6: EH complete Aug 13 00:56:17 unRaid kernel: ata6.00: exception Emask 0x0 SAct 0x800 SErr 0x0 action 0x6 frozen Aug 13 00:56:17 unRaid kernel: ata6.00: failed command: READ FPDMA QUEUED Aug 13 00:56:17 unRaid kernel: ata6.00: cmd 60/00:58:f0:7b:60/02:00:02:00:00/40 tag 11 ncq dma 262144 in Aug 13 00:56:17 unRaid kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Aug 13 00:56:17 unRaid kernel: ata6.00: status: { DRDY } Aug 13 00:56:17 unRaid kernel: ata6: hard resetting link Aug 13 00:56:18 unRaid kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Aug 13 00:56:18 unRaid kernel: ata6.00: configured for UDMA/133 Aug 13 00:56:18 unRaid kernel: ata6: EH complete Do I need to worry?

What board do you have? Did you tried this? if you don`t need i915, try to edit you syslinux append line like this: append nomodeset initrd=/bzroot

i915 is not loading by default! To activate it add this to go file if I turn i915 off, I cant use intel hd graphics for plex/emby hardware transcoding sorry for my English ?

I see most of unraid boot process till the i915 driver is loaded. Screen becomes black near the final part of the boot process... If I don't load i915 (modprobe i915) everything works fine.