Vr2Io

For quick boot problem, if you change different port it will success boot in 1st time, but if reboot then problem will happen again.

If you boot into Windows should fine should fine. Few days ago I try update the ME firmware on Asus mobo, the program always prompt "check MEI driver" and not continue, so I use command prompt to update then it work. I always use NVMe to PCIe adapter to boot up different OS because fact plug in / out.

To be honest, symptoms still match fast boot issue. I really hope LT can overcome this problem. If you confirm BIOS setting really save, then I would suggest you update Intel ME firmware Version 16.1.27.2176v2_S, but this seems need update under Windows ( may need manual command )

Those should be network issue 1. Ensure MTU size match with your PC and Unraid 2. Provide ping -t router and Unraid IP result.

You may try connect this disk to onboard SATA controller / H240 to test any different. Or it may be the case due to SMR disk busy on writing ( due to rewriting shingled track ) out of 4s timeout, you will found reset on every 10s. You also can test does same problem on read operation. ( rest enough time first ) i.e dd if=/dev/sdo of=/dev/null bs=1M count=10k Sep 21 20:18:23 Tower kernel: sd 8:0:2:0: [sdo] tag#313 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=4s Sep 21 20:18:37 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:42 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:18:47 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:18:52 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:18:57 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:02 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred Sep 21 20:19:07 Tower kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Sep 21 20:19:12 Tower kernel: sd 8:0:2:0: Power-on or device reset occurred

Below disk which connect to LSI controller. [8:0:2:0] disk ATA ST8000DM004-2U91 SED1 /dev/sdo /dev/sg15 state=running queue_depth=32 scsi_level=6 type=0 device_blocked=0 timeout=30 dir: /sys/bus/scsi/devices/8:0:2:0 [/sys/devices/pci0000:00/0000:00:1c.4/0000:07:00.0/host8/port-8:2/end_device-8:2/target8:0:2/8:0:2:0] Keep track does SMART data also count up. 0x06 ===== = = === == Transport Statistics (rev 1) == 0x06 0x008 4 61 --- Number of Hardware Resets 0x06 0x010 4 40 --- Number of ASR Events 0x06 0x018 4 0 --- Number of Interface CRC Errors |||_ C monitored condition met ||__ D supports DSN |___ N normalized value

應該是因為 BIOS 開啟了 fast boot, 關閉它便可解決 其餘各種組合都沒有关系

Although principle was simple, but actually was complicating things.

There are two method for your PC to connect different network 1. Assume your PC was on desktop, buy a small VLAN switch sit near the PC, trunk all network to that switch and assign different switch port map to different network. Then plug the PC LAN cable to different port for access different network. 2. Almost same as 1, but use WiFi, some Router / AP support different SSID with different VLAN, then by connect different SSID to access different network. Or you can trunk ( VLAN ) all network to Unraid, i.e. VLAN 1, 2, 3 4, then Unraid have brX.1 , brX.2 , brX.3 , brX.4, config the VM virtual NIC to connect those bridge to access different network.

I never success use Connect service since day one and troubleshoot several time still no go. But today, I figure out it should because my Unraid account wasn't Google ( hotmail.com ) and my Chrome browser always login with google account. Then this will conflict each other ( the odd thing is even use Edge browser still same ) After I create an Unraid account by same Google email then login with this, all Connect service work. But now I have two Unraid account, one for forum and a new account for Connect, for me this fine currently. But how @limetech would help user if they want combine two be one.

The diagram show vlan4000 was vtnet1 ( confuse it is br0.4000 ) which other two was vtnet0. When I check back diagnostic, both eth0 and eth1 was bond, so all that should be conflict each other.

You need ensure pfsense have a work DHCP on vlan.4000 vlan 4000 seems not a usual no., pls also try some less then 1000, in this case, even there are no hardware switch inside. https://community.cisco.com/t5/switching/which-series-switch-supports-vlan-up-to-4000/td-p/2063058

You solve by yourself 👍

Check DNS first, likely DNS resolve issue.

Minor bug on 6.12.4 ? I perform read check ( no parity ) on array, it report duration 9hr+ but actually finish within an hour.

Awesome script, will try later. 👍

Yes Yes, for my understanding, NTFS can't handle extend attributes in usual way, but I may be wrong. I mean not recommend use Windows to handle those backup / hash job .... doing all in one environment will less headaches. Almost all my data store in Unraid and let it handle all job. Some storage set also in different file system, i.e. BTRFS and ZFS, I think this will improve resilience. DFI store hash in two way, extend attributes and plain text file, if you want process file other then array, you can ** edit export text file, change the path content ** then DFI UI also serve as usual, but actually file were in different path. This also my early method to handle verify / import / export for file which outside array, After you learn command line, then you can write some script to handle all job.

You can ref. below post to use command line to perform different operation. You can hash the destination file ( after writing finish to media and flush the ram cache ) base on the hash record, so no need hash the source again. I won't use Windows to hold data file, source and backup hold in Unraid, all in same environment will be best efficiency.

This may have issue, but I use Windows at all, so no problem. Yes Haven't any homebridge stuff, but homeassistance VM / docker work well.

Why don't as most people doing, get the router to connect ISP.

I have similar issue, my server was a 3U 16 bay hot swap rack, and two group in 8 disks each (1-8) (9-16) For temperature issue, due to some reason I can't lower the temperature too much by air conditioner, so I arrange disk in below order ( my rack was stand-up by turn 90 degree ) 1 9 5 13 2 10 6 14 3 11 7 15 4 12 8 16 When I work on disk 1-8, then I will plug out 9-16, as result much better air flow for 1-8, if I work on 9-16, then swap out 1-8 on same way. For UPS part, the new replace battery just serve me two months then one battery got failure (48v in 12v x4), the battery haven't indicate the problem until electricity really interrupt happen. Anyway, I still working on modifying the UPS to use 24v and redesign whole UPS system, I prefer buying two bigger battery instead four smaller battery, this use almost same room size in battery cage, and should increase battery reliability.

Seems to be problem on 10G switch, it doesn't connect to your existing network. As port was up so I don't think it is 10G nic problem.

Change back the 10g nic to Eth0 and reboot, keep use static IP first and try again. Setting both nic to same subnet will have "odd" behaviour.

Suggest restore all from zip/backup file to try any different.

No data lost. But why don't restore all from zip file, instead config folder only. If USB have change, it should ask to confirm licence migrate to new USB.