thanks for your feedback
eth1 is on a temporary useing pci-e NIC card, i prefer eth0 which is on bord.
another porblem is when i use eth1, i can not access apps market/ docker update/ plugin udate
I have plug on a cable on eth0. Under 6.10.3 eth0 was working, while under 6.11.5 eth0 wasnot working. I didn;t change any setting during the system update.
Hi guys,
when my unraid run under 6.10.3, the eth0, NIC in board, worked properly. I updated my Unraid to 6.11.5, eth0 can not get ip, and cable light on board is NOT flashing. Then, i roll-back to 6.10.3, the etho worked again.
Now i added one PCI-e NIC and can get IP address but cannot access to Community Applications .
Is there anything i can do with my Unraid setting?
home-diagnostics-20230411-1356.zip
Hi Simon
thanks for your advice.
i install the plugin. initially, it monitor nothing. I am afraid perhaps there is something wrong on my side. so i intentionally triggered one file reading and it was recorded by plugin sucessfully.
so something weird there. the process just take a peek on disks without any file reading so that make disks quit the spin down. like annoying kids, isn't it? 😅
Background:
Version 6.10.3 - plus; Test under Disable Docker and Vms
Issue:
My disks used to be able to auto spin down before. But after some setting changed(not sure), my disks never auto spin down, and they will "wake up" soon after I manually forced spin down.
Reason is that some process make reading on all my disks periodiccally at very small and same amount of data.
Inquiry:
1、Is there any method that I can use to find out which process involved in disks IO. I tried to search google, and it says "topio" command can make some helps. but this one is not included in Unraids system, neither yum installing.
2、Or, if someone can catch out suspicious process or piont out wrong setting based on my diagnostics file, i would really really appreciate.
home-diagnostics-20221114-1406.zip
This problem was solved by purchasing a basic license.
Thanks for Squid and itimpi's help, this issue confused me for weeks.
--------------------------------------------------original 'bug' report------------------------------------------
I found Vms unable start after reboot due to array is off-line, even though array auto start is enabled in disk settings. Such bug occur only when my Unraid failed to access network.
Reproduce the bug process:
1. Confirming that setting - disk settings- enable auto start is [YES]
2.Plug off network cable that used to connect webgui for management.
3.Turn on/reboot Unraid, booting as safe mode.
4.After noticed that ipv4 address is 'not set', plug on lane cable. Ifconfig cmmand suggest that Unraid get ipv4 address.
5. Connecting to management interface, the arrary status shows off-line
tower-diagnostics-20201202-1754.zip