Vr2Io

Members
  • Posts

    3614
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by Vr2Io

  1. Interesting product, the 6 NVMe version have dual LAN and more affordable. Asustor should make 12 / 6 LED visible, good for show off. ( actually this also useful ) A guy jeffgeerling have many great idea & build ( not for Unraid ), really like. https://www.jeffgeerling.com/blog/2023/building-tiny-6-drive-m2-nas-rock-5-model-b
  2. CPU seldom have problem. But both are fundamental component, so we must testing those first. Pls create memory test boot USB to test CPU / MB / Memory ( must use parallel CPU thread during test, if you got two pass then it is fine, no need 24hrs ) https://www.memtest86.com/ If all fine, then start Unraid and test docker service in /tmp to isolate any storage affect issue first. ( no need unplug any other hardware this moment )
  3. Try blkdiscard /dev/nvme1n1 ( double check the device name have change or not before command fire )
  4. OK. My different Unraid build haven't spindown issue, so I seldom go to safe mode to troubleshoot. But now, I found some abnormal on safe-mode, the disk actually will self spinup because system reading it, so pls don't test under safe mode. ** edit : periodic reads in safe mode should only happen on POOL DEVICES ** Pls try boot Unraid in normal with disable docker service and check does periodic read gone.
  5. For my understanding, if Unraid in safe mode, it won't mount any disk with filesystem ( so no docker could start too ), and why I ask does docker service in stop, because I found you set the docker img in array, this may cause periodic read in array. DOCKER_ENABLED="yes" DOCKER_IMAGE_FILE="/mnt/user/system/docker/docker.img" DOCKER_IMAGE_SIZE="100" DOCKER_APP_CONFIG_PATH="/mnt/user/appdata/"
  6. Got you have in safe mode Oct 5 23:38:38 Maverick root: unRAID Safe Mode (unraidsafemode) has been set But don't understand why system will mount disk with XFS filesystem. All my disk were BTRFS, but I haven't found will mount disk with file system in safe mode. I attach my diagnostic FYR b365-diagnostics-20231006-1158.zip Does your docker service show failed to start in safe mode ?
  7. As iowait upsurge, it may indicate something relate to storage issue. If all docker stop and just docker service start still cause the problem, it is odd ..... suggest try relocate docker storage to other storage device to try.
  8. Would you provide the diagnostics for above operation.
  9. You have sas-spindown.plg - 2022.08.02 and SAS disk, pls try uninstall / disable it, then go to safe mode, check does SATA or SAS disk have such periodic read.
  10. Add the device to HA docker. ( I only try HA docker to handle the dongle in early testing and I use Zigbee2mqtt currently, so it may have some different, anyway almost that way. Or you may ref. below youtube clip ) Depends on which type Sonoff dongle, integrations / config it with correct protocol ( ZNP / EZSP ).
  11. You should check each docker log to identify the stop reason.
  12. RTC real time clock wakeup can set by command, so you just need enable RTC wakeup in BIOS, then wake up on program time.
  13. 這裡出問題多, 與移除硬盤/轉接咭冇关. 重新製作 U 盤吧, 發張啟動時的圖片.
  14. There are some rack product have SAS / SATA, so no mess data and power cable. And price also affordable. For example, Gooxi RMC2125 just need usd520. ( Mfg price) Almost same even little bit more.
  15. For quick boot problem, if you change different port it will success boot in 1st time, but if reboot then problem will happen again.
  16. 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.
  17. 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 )
  18. Those should be network issue 1. Ensure MTU size match with your PC and Unraid 2. Provide ping -t router and Unraid IP result.
  19. 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
  20. 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
  21. 應該是因為 BIOS 開啟了 fast boot, 關閉它便可解決 其餘各種組合都沒有关系
  22. Although principle was simple, but actually was complicating things.
  23. 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.
  24. 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.