Richard Aarnink

Hi, before performing a major version upgrade I’d like to test and learn / experiment with new versions. I would like to step in directly when a new beta is started, like the beta series for version 7. the problem however is i would either need to boy a license or request a 30 day trail ket. The beta program runs much longer than 30 days which disqualifies this option. it would be great if the beta versions would not require a lisence key but have some other form of protection for misuse (as production environment). Perhaps put a fixed enddate and/or a max uptime of a couple of days. Maybe there are other options to consider. for me this would be great because it would help me test new versions before i actually upgrade my production environment without having to buy a license. regards Richard

I contacted the supplier which thankfully stated that i can return the board and there is no hurry. I also reached out to Biostar tech support and am waiting for a reply from them. Meanwhile i also bought a Silverstone sst ecs06 pci card which offers 6 sata ports and is based on the asm1166 chipset. In order to check the disks I connected the Toshiba drives to the Silverstone card. They work as expected. The Sandisk SSD and WD drives are connected to the Biostar Sata ports and unfortunately the WD drives started reporting the same errors. Connected both WD drives to the Silverstone sata ports and voila they work. It seems to me that either the board is defective or the sata ports are flaky. I will wait for Biostar to reply but if this takes to long i will return the board and get a other brand with 4 sata ports. this journey is not fun. I had a disabled drive in the array twice and a disk which cannot be mounted due to an unrecognized filesystem. fortunately i could recover the data. Now i am still waiting for one disk of which the data is being reconstructed. Scary times.

Hi, I tried different combinations, all 4 Toshiba MG07/M08 (14TB) SATA drivers do not work, not in SATA ports 1-4 nor in 5-8. Weird enough the WD Red Plus (4TB) do work in all ports. It is like the Toshiba and Biostar in this MB is a bad marriage. Also the 120GB SSD SanDisk SDSSDA120G caused problems. All drivers are recognised by the BIOS and in Unraid. It is when the drivers are mounted that the error messages appear. I have had enough, going to return this MB thanks for your help!

only for the ssd's and these were in the old system as well. i also upgraded to the Cooler Master GX III Gold 650W from the 550W Thermaltake I used before. also the drives work perfectly in the setup using a LSI PCI SAS-SATA card. Could it still be a power related issue?

Hi All, I need some help with my new setup, it is a biostar b760mx2-e pro d4 mainboard with an Intel 14500 CPU. Choose this MB because of the 8 SATA ports and now I am starting to get insane because of issues reporting in the logs. SATA ports 9, 11 and 12 are reporting issues: ata12.00: exception Emask 0x0 SAct 0x4000 SErr 0x0 action 0x6 frozen [ 141.546681] ata12.00: failed command: READ FPDMA QUEUED [ 141.546685] ata12.00: cmd 60/08:70:40:00:00/00:00:00:00:00/40 tag 14 ncq dma 4096 in res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 141.546701] ata12.00: status: { DRDY } I already tried different SATA cables and I am not sure what is causing the issue. The drives are used before I my previous build, in which I used a PCI LSI card to expand my SATA ports. As I was trying to minimize power consumption I tried without this card and use the 8 on board SATA ports. When I install this card and connect my drives the system is working just fine. In the BIOS the SATA ports are enabled and there are not much options the setup. Should I return the MB as this is simply defective or am I overlooking something ? I have included the Diagnostics file as well. richtech-diagnostics-20240826-2113.zip

@halorrr problem solved? My problem could be the IPVLan setting for Docker. I always used MACVLan. I installed 6.11.5 (which ran fine in the past) and first experienced the same crashes. I learned that new installs from 6.11.5 on have IPVLan as default, I changed it to MACVLan and now it is stable sofar.

Hi @halorrr, Just wanted to check, are you aware of the iGPU issue on 11th gen Intel CPU's on 6.12 ? https://docs.unraid.net/unraid-os/release-notes/6.12.0/#crashes-related-to-i915-driver I am not sure, but might it also be applicable to 12th gen, I cannot find any additional info.

Hi I am still struggling, the server ran 17 days without issues on 6.12.3. As I was on vacation, the WebGUI of Unraid was not used. When I got back and started using the WebGUI the server died in less then 2 days. I upgraded to 6.12.4 rc 18. It ran for 2,5 days and just died an hour ago. There are no nginx crashes in the syslog, only the “Stop running nchan processes“ message appears a couple of times. I am reverting back to 6.11.

@halorrr with the new USB Flas disk I am running 4 days now no problems. Will keep the system as-is for now as I am off on vacation in a couple of days. not all plugins are running, but the dockers and the vm for homeassistant is. I can provide more details if you need to have more info. in the logs I see Nginx crashes, but this seems to be a known issue. The system however is stable for now. So a fresh new usb stick, a new installation (no copying of files fron the old usb stick) seemed to solve the issue for me. regards Richard

@halorrr thank’s for letting me know. I created a new usb flashdrive using a samsung bar pro 32 gb and did not copy any files from the old usb device. Today I “downgraded” the cache drive to btrfs from zfs. This should enable me to downgrade if needed. the system is up for 1 day and 23 hrs now. Still on 6.12.3. I will keep you informed. in your case, if the downgrade to 6.11.5, which ran fine the past, still does not solve the problem, consider what us left to look at. 1. Any changes or upgrades to the BIOS? 2. The usb flash drive, is it still the same stick? Is it in an USB2 slot (USB3 causes problems in some cases) maybe do an extensive test using the tools from the ultimate boot usb https://www.pcwdld.com/ultimate-boot-cd-ubcd-review/

Hi , please provide additional information, you can start here. In this post provides help in troubleshooting and if you cannot solve your issue with these tips it also explains how to provide sufficient info to get help. Hopefully you are able to resolve your issues quickly.

I am starting to seeing a pattern @halorrr and @Hibiki Houjou and me are experiencing similar issues. The system freezes randomly, there is no change in the hardware. We are all on 6.12.2 or 6.12.3.

It seems you are having similar issues as @halorrr and myself. We are all on 6.12.3 and we experience system crashes, without anything in the log that is helpfull. I am investigating if the USB flash drive is to blame (as the hardware is not changed). Hopefully someone can help pinpoint the issue, find the root cause. I might return to 6.11 this weekend if we cannot make any progress.

I am still not out of the woods myself (if that is a saying). I replaced my flash drive with a Transcend jetflash 600 8gb. The system crashed within a couple of hours. i am unsure if the flashdrive is the issue. Now I am trying the Samsung Bar Pro 32 Gb. I use an usb2 port, no other devices are connected via usb2. I have created a complete new install and did not copy anything over from the original usb flash drive. currently there are no plugins active. The system is rebuilding parity now. I want to keep the system running a couple of days before i add plugins. I am curious whether this has solved it, but i am unsure. It certainly is not a good feeling that there is nothing in the logs.

Yesterday evening I noticed that unraid was reporting that the usb flash drive was disconnected. I found errors using dosfsck. I replaced the usb flash drive earlier this month, by a new Philips 32 gb one, when I upgraded to 6.12. I did this as the previous one was rather old. Now I know to keep away from the Philips branded 32 gb usb flash drives. @halorrr you might want to investigate the USB Flash drive as well the memory is not the culprit. The server is still running, no crashes. All plugins are enabled and runtime is 23 hrs.

@halorrr After 13hrs the system crashed again, so it seems I am in the same boat and we both are still having similar issues. I just started in safe mode. Now I am planning to wait at least 24hrs before I call it a victory and assume that the system is stable in safe mode. Currently Docker a minimum of docker containers (MQTT and Plex) and one VM (Home Assistant) are running. Do you have any updates?

Update 3: Currently running without these plugins: appdata.backup.plg dynamix.file.manager.plg dynamix.unraid.net.plg unassigned.devices.preclear.plg It is too early to tell if the one of these is causing the crashes. the system is running 2,5 hrs now. @halorrr do you have any updates ?

@halorrr thank you, when we combine our efforts we might find the rootcause faster. I have just rebooted the server with all plugins enabled except user.scripts and zfs.master as these are the plugins I installed last. Also updated NerdTools to 2023.07.18 as this update is now offered. I will keep you informed. update 1: running with all plugins except user.scripts and zfs.master for 5:30 hrs now. Keep you informed update 2: now after almost 9 hrs the system crashed. seems like user.scripts and zfs.master are not to blame now back to safe mode first. tomorrow I will continue the search

I am having the same problems over the last couple of days, no changes in hardware and it ran stable over months (I am not suspecting anything being wrong with the hardware) The system crashes to a point where it needs a hard reboot. My system is on 6.12.3, and yesterday it crashed 3 times. the numlock key on the attached keyboard does not work and the monitor produces a no signal message. It is clear that it is not only the webgui of unraid that has crashed. the only 2 lines of concern in the syslog (to me) are: docker0: port 1(vethc08d6dd) entered disabled state. --> it occurs a lot, i do not no if I need to be concerned and if so how to find the responsible docker container nginx: 2023/07/19 14:01:54 [alert] 6707#6707: worker process xxxx exited on signal 6 --> which as far as I have learned from other posts is only concerning webgui of unraid Yesterday evening I booted in safemode, with VM's and Dockers enabled (and minimal set running). This morning the system is still up. It is most likely at this point to look for issues in plugins. Below is the list of plugins installed on my system. Of these the ZFS master and User Scripts were installed last, the other 2 are updated. As there is nothing in the log files I think I need to try to find the rootcause by disabling the yellow marked plugins one-by-one. Is there a smarter (less timeconsuming) way? -rw------- 1 root root 3415 Feb 12 04:40 unbalance.plg -rw------- 1 root root 4861 Feb 16 20:26 intel-gpu-top.plg -rw------- 1 root root 5629 Mar 3 04:40 dynamix.system.temp.plg -rw------- 1 root root 7287 Mar 3 04:40 dynamix.system.stats.plg -rw------- 1 root root 4572 Mar 3 04:40 dynamix.system.info.plg -rw------- 1 root root 4765 Mar 3 04:40 dynamix.password.validator.plg -rw------- 1 root root 6376 Mar 3 04:40 dynamix.cache.dirs.plg -rw------- 1 root root 5349 Apr 16 07:21 unassigned.devices-plus.plg -rw------- 1 root root 24691 May 6 04:40 dynamix.unraid.net.plg -rw------- 1 root root 9094 May 20 13:27 unassigned.devices.preclear.plg -rw------- 1 root root 7486 Jun 1 20:30 dynamix.file.manager.plg -rw------- 1 root root 6302 Jun 8 12:13 NerdTools.plg -rw------- 1 root root 4520 Jun 12 19:07 open.files.plg -rw------- 1 root root 5129 Jul 4 06:40 ca.mover.tuning.plg -rw------- 1 root root 103495 Jul 4 12:41 community.applications.plg -rw------- 1 root root 9814 Jul 5 21:51 tips.and.tweaks.plg -rw------- 1 root root 7165 Jul 8 13:29 appdata.backup.plg -rw------- 1 root root 3974 Jul 16 15:05 zfs.master.plg -rw------- 1 root root 7360 Jul 16 15:12 user.scripts.plg -rw------- 1 root root 20839 Jul 16 21:55 fix.common.problems.plg -rw------- 1 root root 90705 Jul 16 21:55 unassigned.devices.plg syslog

Jun 6 19:05:13 RichTech emhttpd: Device inventory: Jun 6 19:05:13 RichTech emhttpd: TOSHIBA_MG08ACA14TE_61S0A02TFVJG (sdj) 512 27344764928 Jun 6 19:05:13 RichTech emhttpd: WDC_WD30EFRX-68AX9N0_WD-WMC1T0376287 (sdk) 512 5860533168 Jun 6 19:05:13 RichTech emhttpd: WDC_WD30EFRX-68AX9N0_WD-WMC1T0597412 (sdh) 512 5860533168 Jun 6 19:05:13 RichTech emhttpd: WDC_WD50EZRZ-00GZ5B1_WD-WX11D278Z7E7 (sdg) 512 9767541168 Jun 6 19:05:13 RichTech emhttpd: WDC_WD40EFZX-68AWUN0_WD-WX32D51EL0S9 (sdd) 512 7814037168 Jun 6 19:05:13 RichTech emhttpd: WDC_WD30EFRX-68EUZN0_WD-WCC4N4KZTCZ7 (sde) 512 5860533168 Jun 6 19:05:13 RichTech emhttpd: TOSHIBA_MG08ACA14TE_61S0A02FFVJG (sdb) 512 27344764928 Jun 6 19:05:13 RichTech emhttpd: SanDisk_SDSSDA120G_171548451903 (sdf) 512 234441648 Oh, my god, you are right, it is a very small difference which I have overlooked completely.

Hi, I purchaged 2 Toshiba MG08 enterprise capacity drives (14TB, model MG08ACA14TE (SATA). 1 is used as Parity the other as data disk (which replaces an older disk) in the Array. The prep went fine (pre-cleared) no issues. I tried to follow the @spaceinvaders tutorial for Shrinking the array to the letter, which is ok, until the point where I had to create a new config. To remeber which disk is in which slot, and which disk is the parity drive I made a picture as was also advised in the tutorial. When creating the new config I was confused when I saw the 2 Toshiba drives have the same serial number, as this is shown in the selector, I cannot tell which disk is the Parity and which is the Data disk. No issue for now, as both drives where new. But certainly a potential problem in the future. I checked the disk identity and I noticed that the "LU WWN device id" are different for both drives, however this is not shown in the selector when creating a new config. How should I select the proper parity disk in the future and tell both drives apart? Is it an idea to use the LU WWN device id field instead of the serial number in the drive selector, or am I doing something wrong? I run Unraid 6.10.2. Regards, Richard

Upgraded from 6.9.2 -> 6.10 without issues. only network stats plugins has issues, this is known see

Hi Peter, here in the Netherlands power outages are rare. A UPS seems overkill and I was looking for a cheap alternative. Scheduled poerdown from the terminal worked so i guess this is also good for the rare occasions i need to power down. Thanks anyway!

Hi, I have a request for the developer. I would like a plugin (button) which would enable me to shutdown and poweroff the server at a given date/time. Tomorrow morning maintenance is scheduled which means i will lose power. It would be great to have the option to schedule a shutdown in advance, as i am now worried that I oversleep. i tried to do this from the terminal with command shutdown -h 06:45 hope this works! regards Richard

Hi, I have a question on xdebug. I would like to debug my php google assistant project. I read multiple articles referring to using remote xdebug. As far as I understand now, this would require xdebug to be setup inside the docker container. php-xdebug would need to be installed etc. I would like to know if I can use xdebug inside the letsencrypt docker container. I like this container for its swift updates to keep me secure, and I know that acutally installing anything inside the container will break upon the next update. Therefore this question, is xdebug enabled (but hidden from the config) or can it be added in future? Or lastly is there another docker container which I should use if I intent to debug?