ramiro

I am running 6.12.3 , i am running 6.12 since the RC release, could it maybe be a communcation problem between the cpu's (as far as i saw the qpi link also has error correction so it also shouldn't be a problem).

Shouldn't there atleast be an ecc error then , or can there be undetected memory errors with ecc ? The array still runs fine , actually ran 2 scrubs already because of the monthly scrub.

So i also ran a balance and it also had no errors , so i will i have to worry now that this can happen any time again ?

Hello I got a very weird problem yesterday , suddenly my raid10 with 6 Disks went read only with this error : Jul 24 23:07:09 ramiroserver dnsmasq[10431]: using nameserver 8.8.8.8#53 Jul 24 23:07:09 ramiroserver dnsmasq[10431]: using nameserver 2003:dc:2f25:200:6ef0:49ff:fe45:27eb#53 Jul 24 23:07:09 ramiroserver dnsmasq[10431]: using nameserver 2003:dc:2f12:fb01:a236:9fff:febe:59dc#53 Jul 24 23:12:45 ramiroserver kernel: BTRFS critical (device sdh1): corrupt leaf: block=28466229657600 slot=142 extent bytenr=22370527346688 len=131072 invalid extent refs, have 1 expect >= inline 4222615553 Jul 24 23:12:45 ramiroserver kernel: BTRFS info (device sdh1): leaf 28466229657600 gen 610063 total ptrs 208 free space 59 owner 2 Jul 24 23:12:45 ramiroserver kernel: #011item 0 key (22370491891712 168 65536) itemoff 16230 itemsize 53 Jul 24 23:12:45 ramiroserver kernel: #011#011extent refs 1 gen 365653 flags 1 Jul 24 23:12:45 ramiroserver kernel: #011#011extent refs 1 gen 552994 flags 1 Jul 24 23:12:45 ramiroserver kernel: #011#011ref#0: extent data backref root 5 objectid 9942256 offset 409495535616 count 1 Jul 24 23:12:45 ramiroserver kernel: #011item 207 key (22370586890240 168 282624) itemoff 5259 itemsize 53 Jul 24 23:12:45 ramiroserver kernel: #011#011extent refs 1 gen 554551 flags 1 Jul 24 23:12:45 ramiroserver kernel: #011#011ref#0: extent data backref root 5 objectid 9942256 offset 552465006592 count 1 Jul 24 23:12:45 ramiroserver kernel: BTRFS error (device sdh1): block=28466229657600 write time tree block corruption detected Jul 24 23:12:45 ramiroserver kernel: BTRFS: error (device sdh1) in btrfs_commit_transaction:2460: errno=-5 IO failure (Error while writing out transaction) Jul 24 23:12:45 ramiroserver kernel: BTRFS info (device sdh1: state E): forced readonly Jul 24 23:12:45 ramiroserver kernel: BTRFS warning (device sdh1: state E): Skipping commit of aborted transaction. Jul 24 23:12:45 ramiroserver kernel: BTRFS: error (device sdh1: state EA) in cleanup_transaction:1958: errno=-5 IO failure I took the array offline and ran btrfs check without repair and it showed that everything is fine , so i restarted the server and now the array is fully working , i ran a scrub today with repair option that came back without any errors : UUID: 2df74f3a-347d-4ae8-9f13-e760dc67014a Scrub started: Tue Jul 25 01:44:23 2023 Status: finished Duration: 11:32:36 Total to scrub: 15.90TiB Rate: 401.11MiB/s Error summary: no errors found I am running a dual 2011 system with ecc memory and had no error whatsoever before the btrfs error , the only problem is that due to the macvlan issue , i had 1 unclean reset a week before this , had the same thing 2 months ago thad corrupted my other raid1 array but that one did not came back after restart so i had to reformat it. I am a litte worried now if this problem will come back and what is the real issue ? Thank you

i have the same problem every 2-3 days nginx stops working and has this error : Jun 29 08:05:09 ramiroserver nginx: 2023/06/29 08:05:09 [error] 28347#28347: nchan: Out of shared memory while allocating channel /disks. Increase nchan_max_reserved_memory. Jun 29 08:05:09 ramiroserver nginx: 2023/06/29 08:05:09 [error] 28347#28347: *668759 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Jun 29 08:05:09 ramiroserver nginx: 2023/06/29 08:05:09 [crit] 28347#28347: ngx_slab_alloc() failed: no memory After nginx restart everything works again.

Hello, After upgrading from RC to 6.12.1 my nginx doesn't want to start by itself. Everything is running samba vm's dockers but not nginx , the weird thing is that i have to wait for the opnsense vm to start up then i can type nginx start and everything works before that just nothing happens and status shows not running. Could nginx be waiting for some kind of network initialization? There is also no error about nginx in the log. With 6.12 rc5 everything was fine but with 6.12.1 i have this issue. Attache my diagnostics ramiroserver-diagnostics-20230623-2200.zip

I looked into the code about the custom schedule scripts not starting after restart, i cannot see any function that creates them on reboot , could it be that it is not implented , or was i just blind ?

I figured out a solution so if anybody else also needs this here is what i did. I installed ipmitool with nerdtools. Then i created a script that at the start of the array initalizes the watchdog : #!/bin/bash modprobe ipmi_si modprobe ipmi_devintf /usr/bin/ipmitool raw 0x06 0x24 0x04 0x01 0x00 0x00 0x70 0x17 And another script that every minute runs this command #!/bin/bash /usr/bin/ipmitool mc watchdog reset

Has anybody else the problem that scripts with custom quene are not added to the /etc/cron.d/root file after a reboot ? I have to change something in the scripts and after i click apply they are back in the file.

Hello , I have a Z9PE-D16 running unraid , for some reason i don't know yet my systems freezes ~ once a month. I saw that my board has a watchdog that would at least minimalize the downtime , but when i enable it the system restarts after 10 min because unraid is not sending anything to it. As far as i found out i should use the iTCO_wdt modul but it is not included in unraid ? Has anybody running a watchdog with unraid ? I found something about watchdog in this release notes https://wiki.unraid.net/Manual/Release_Notes/Unraid_OS_6.9.1 but nothing how to use it. Thank you Ramiro

I attached my diagnostics. ramiroserver-diagnostics-20220709-1603.zip

All my Interfaces have a static IP address.

Hello , is still have this problem on 6.10.3 after restart host accest doesn't work, i have to stop the docker service disable host access then enable host acess and start the docker service. I am using a opnsense VM as my router so there is no network when unraid is startig but all the interfaces have a static address. This affects dockers that are not running on the main interface but are tryining to access a docker on the main interface(my Apache dockers are on vlan 20 , but my mysql docker is running on the host interface) .

Had this bug on the released 6.10 today , very annoying especialy if you don't know about it and are looking everywhere why its not working.

Thank you its working fine now.