royeiror Posted December 7, 2022 Share #1351 Posted December 7, 2022 3 hours ago, gazzac72 said: have you tried doing hard reboot when you get that message i know i had that rebooted system and it was all working Meaning turning the PC off with the power button and restarting?, then yes. Quote Link to comment Share on other sites More sharing options...
gazzac72 Posted December 7, 2022 Share #1352 Posted December 7, 2022 Has anyone been testing the new DS923+ with the so called ability to use m.2 as storage pools i have tried everything even going as far as buying a m.2 that synology says they have tested and recommend for there machines i cannot for the life of me get it to work says device isn't compatible and all it will allow is to be used as a storage pool anyone else tested this machine ? Quote Link to comment Share on other sites More sharing options...
Orphée Posted December 7, 2022 Share #1353 Posted December 7, 2022 (edited) 2 hours ago, gazzac72 said: Has anyone been testing the new DS923+ with the so called ability to use m.2 as storage pools i have tried everything even going as far as buying a m.2 that synology says they have tested and recommend for there machines i cannot for the life of me get it to work says device isn't compatible and all it will allow is to be used as a storage pool anyone else tested this machine ? I'm not sure to understand what you are trying to say... "the so called ability to use m.2 as storage pools" "all it allow is to be used as a storage pool" Well, it seems it does what it says... no ? Edited December 7, 2022 by Orphée Quote Link to comment Share on other sites More sharing options...
gazzac72 Posted December 7, 2022 Share #1354 Posted December 7, 2022 3 minutes ago, Orphée said: I'm not sure to understand what you are trying to say... "the so called ability to use m.2 as storage pools" "all it allow is to be used as a storage pool" Well, it seems it does what it says... no ? no it doesnt it can only be used as cache and not nvme storage pool as it says on the synology website "2 x M.2NVMe cache & storage pool4" and like i said i can only get it to see as a cache drive it says not compatible even though the m.2 in it is recommended by them Quote Link to comment Share on other sites More sharing options...
Orphée Posted December 7, 2022 Share #1355 Posted December 7, 2022 You first said "storage pool" twice, so was quite unclear. But if you give /var/log/message logs and dmesg command result, it could help the guys who know a bit with coding. As NVMe storage pool never implemented earlier, it may be something to add/fix/address in redpill loader... 1 Quote Link to comment Share on other sites More sharing options...
Orphée Posted December 7, 2022 Share #1356 Posted December 7, 2022 (edited) Does someone know if we can emulate an NVMe disk for a VM on Proxmox when we don't have one ? if so, how ? By the way it seems you need to enable "Direct Boot" to true with DS923+ ARPL Loader on Proxmox (machine q35 with seabios). Without it I have a kernel panic. Edit 2 : actually it is not because of Direct boot. I have it randomly at VM start. I would say it does not kernel panic if I'm lucky, most of the time it does a KP. and sometimes it boots correctly. Edited December 7, 2022 by Orphée Quote Link to comment Share on other sites More sharing options...
vasiliy_gr Posted December 7, 2022 Share #1357 Posted December 7, 2022 1 hour ago, Orphée said: Edit 2 : actually it is not because of Direct boot. I have it randomly at VM start. I would say it does not kernel panic if I'm lucky, most of the time it does a KP. and sometimes it boots correctly. I also mentioned some random kernel panic. But not with Beta7 and NVMe, but with Beta6 and no NVMe. It is not most times there, but I evalute it as one occurence from four loadings. And their were four different NAS-es with Proxmox. Previously I used Beta3 and there did not see kernel panic at all (but I am not sure that it was impossible, may be I was lucky). When kernel panic occures I simply reboot VM with it (on Proxmox) - and everything ok after reboot. I do not know what is related for... Quote Link to comment Share on other sites More sharing options...
Orphée Posted December 7, 2022 Share #1358 Posted December 7, 2022 I'm using beta6 without any NVME yet Quote Link to comment Share on other sites More sharing options...
vasiliy_gr Posted December 7, 2022 Share #1359 Posted December 7, 2022 1 minute ago, Orphée said: I'm using beta6 without any NVME yet Ok. And I forget to mention - all my NAS-es use DS3612xs+ with DSM 7.1.1-42962u2. Quote Link to comment Share on other sites More sharing options...
fbelavenuto Posted December 7, 2022 Author Share #1360 Posted December 7, 2022 Hello guys, I've released ARPL v1.0-beta7. Some menu options from main menu have been moved into "Advanced Menu". I get all modules from beta3 (more stable) and put into this release. If you update the modules the beta3 modules will come. 3 Quote Link to comment Share on other sites More sharing options...
Orphée Posted December 7, 2022 Share #1361 Posted December 7, 2022 (edited) I've updated from beta 6 to beta 7 and it seems no more random freezes at start on DS923+ loader Edited December 7, 2022 by Orphée 1 Quote Link to comment Share on other sites More sharing options...
meduardp Posted December 7, 2022 Share #1362 Posted December 7, 2022 Hi benvenuto, Thank you very much for your great work. I have error when build the new loader for DS920+ on Proxmox VE 7.3 Can you check please? Thanks in advance. Скрытый текст Quote Link to comment Share on other sites More sharing options...
vasiliy_gr Posted December 7, 2022 Share #1363 Posted December 7, 2022 And what happend in Beta7 with reducelog addon? If I do "Update addons" after "Update arpl" with reboot between them - there is no reducelog. Also "Build the loader" produces error - it is needed to delete this addon before build. Anyway four upgrades from Beta6 to Beta7 - no kernel panic or so. Quote Link to comment Share on other sites More sharing options...
Orphée Posted December 8, 2022 Share #1364 Posted December 8, 2022 So I was able to emulate a fake NVMe disk on DS923+ loader with Proxmox : root@DS923plus:/var/log# grep -i nvme messages 2022-12-08T01:39:13+01:00 DS923plus synostorage[6243]: synostorage_int_disk.c:442 Disk [nvme0n1] info cache generated 2022-12-08T01:39:13+01:00 DS923plus synostorage[6299]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:39:13+01:00 DS923plus synostorage[6299]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:39:13+01:00 DS923plus synostorage[6299]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:39:13+01:00 DS923plus synostorage[6299]: nvme_log_get.c:58 fread failed 2022-12-08T01:39:13+01:00 DS923plus synostorage[6299]: smartctl/smartctl_nvme_self_test_read.c:150 Error: SYNONVMeLogGet (self-test-log) -1 2022-12-08T01:39:13+01:00 DS923plus synostorage[6299]: SMARTNvmeSelfTestLogRead 2022-12-08T01:39:13+01:00 DS923plus synostorage[6299]: smartctl/smartctl_test_status_get.c:53 SMARTSelfTestLogRead(/dev/nvme0n1) fail 2022-12-08T01:39:13+01:00 DS923plus synostorage[6299]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:39:13+01:00 DS923plus synostorage[6299]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:39:13+01:00 DS923plus synostorage[6299]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:39:13+01:00 DS923plus synostorage[6299]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:39:14+01:00 DS923plus synostorage[6299]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:39:14+01:00 DS923plus synostorage[6007]: SYSTEM: Last message 'nvme_disk_vender_get' repeated 3 times, suppressed by syslog-ng on DS923plus 2022-12-08T01:39:17+01:00 DS923plus synostgd-disk[9648]: nvme_log_get.c:58 fread failed 2022-12-08T01:39:17+01:00 DS923plus synostgd-disk[9648]: smartctl/smartctl_nvme_self_test_read.c:150 Error: SYNONVMeLogGet (self-test-log) -1 2022-12-08T01:39:17+01:00 DS923plus synostgd-disk[9648]: SMARTNvmeSelfTestLogRead 2022-12-08T01:39:17+01:00 DS923plus synostgd-disk[9648]: smartctl/smartctl_test_status_get.c:53 SMARTSelfTestLogRead(/dev/nvme0n1) fail 2022-12-08T01:39:19+01:00 DS923plus hotplugd[9872]: DEVNAME:nvme0n1 2022-12-08T01:39:19+01:00 DS923plus hotplugd[9872]: DEVPATH:nvme0n1 2022-12-08T01:39:19+01:00 DS923plus hotplugd[9872]: hotplugd.c:1322 ==== SSD cache [nvme0n1] hotswap [add] ==== 2022-12-08T01:39:19+01:00 DS923plus hotplugd[9872]: disk/disk_config_single.c:122 apply /usr/syno/bin/DiskApmSet.sh 255 /dev/nvme0n1 1>/dev/null 2>&1 2022-12-08T01:39:19+01:00 DS923plus hotplugd[9872]: disk/disk_config_single.c:122 apply /usr/syno/bin/syno_disk_ctl --ncq-on /dev/nvme0n1 1>/dev/null 2>&1 2022-12-08T01:39:19+01:00 DS923plus hotplugd[9872]: hotplugd.c:1355 ==== SSD cache [nvme0n1] Model: [QEMU NVMe Ctrl ] ==== 2022-12-08T01:39:19+01:00 DS923plus hotplugd[9872]: hotplugd.c:1356 ==== SSD cache [nvme0n1] Serial number: [nvme-1] ==== 2022-12-08T01:39:19+01:00 DS923plus hotplugd[9872]: hotplugd.c:1357 ==== SSD cache [nvme0n1] Firmware version: [7.1.0 ] ==== Disk id: 1, Disk path: /dev/nvme0n1 2022-12-08T01:39:21+01:00 DS923plus synostgdisk[11364]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:44:56+01:00 DS923plus synostorage[6237]: synostorage_int_disk.c:442 Disk [nvme0n1] info cache generated 2022-12-08T01:44:56+01:00 DS923plus synostorage[6324]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:44:56+01:00 DS923plus synostorage[6324]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:44:56+01:00 DS923plus synostorage[6324]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:44:56+01:00 DS923plus synostorage[6324]: nvme_log_get.c:58 fread failed 2022-12-08T01:44:56+01:00 DS923plus synostorage[6324]: smartctl/smartctl_nvme_self_test_read.c:150 Error: SYNONVMeLogGet (self-test-log) -1 2022-12-08T01:44:56+01:00 DS923plus synostorage[6324]: SMARTNvmeSelfTestLogRead 2022-12-08T01:44:56+01:00 DS923plus synostorage[6324]: smartctl/smartctl_test_status_get.c:53 SMARTSelfTestLogRead(/dev/nvme0n1) fail 2022-12-08T01:44:56+01:00 DS923plus synostorage[6324]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:44:56+01:00 DS923plus synostorage[6324]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:44:56+01:00 DS923plus synostorage[6324]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:44:56+01:00 DS923plus synostorage[5980]: SYSTEM: Last message 'nvme_disk_vender_get' repeated 3 times, suppressed by syslog-ng on DS923plus 2022-12-08T01:44:56+01:00 DS923plus synostorage[6324]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:44:56+01:00 DS923plus synostorage[6324]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:45:00+01:00 DS923plus synostgd-disk[10078]: nvme_log_get.c:58 fread failed 2022-12-08T01:45:00+01:00 DS923plus synostgd-disk[10078]: smartctl/smartctl_nvme_self_test_read.c:150 Error: SYNONVMeLogGet (self-test-log) -1 2022-12-08T01:45:00+01:00 DS923plus synostgd-disk[10078]: SMARTNvmeSelfTestLogRead 2022-12-08T01:45:00+01:00 DS923plus synostgd-disk[10078]: smartctl/smartctl_test_status_get.c:53 SMARTSelfTestLogRead(/dev/nvme0n1) fail 2022-12-08T01:45:01+01:00 DS923plus hotplugd[10265]: DEVNAME:nvme0n1 2022-12-08T01:45:01+01:00 DS923plus hotplugd[10265]: DEVPATH:nvme0n1 2022-12-08T01:45:01+01:00 DS923plus hotplugd[10265]: hotplugd.c:1322 ==== SSD cache [nvme0n1] hotswap [add] ==== 2022-12-08T01:45:01+01:00 DS923plus hotplugd[10265]: disk/disk_config_single.c:122 apply /usr/syno/bin/DiskApmSet.sh 255 /dev/nvme0n1 1>/dev/null 2>&1 2022-12-08T01:45:01+01:00 DS923plus hotplugd[10265]: disk/disk_config_single.c:122 apply /usr/syno/bin/syno_disk_ctl --ncq-on /dev/nvme0n1 1>/dev/null 2>&1 2022-12-08T01:45:01+01:00 DS923plus hotplugd[10265]: hotplugd.c:1355 ==== SSD cache [nvme0n1] Model: [QEMU NVMe Ctrl ] ==== 2022-12-08T01:45:01+01:00 DS923plus hotplugd[10265]: hotplugd.c:1356 ==== SSD cache [nvme0n1] Serial number: [nvme-1] ==== 2022-12-08T01:45:01+01:00 DS923plus hotplugd[10265]: hotplugd.c:1357 ==== SSD cache [nvme0n1] Firmware version: [7.1.0 ] ==== Disk id: 1, Disk path: /dev/nvme0n1 2022-12-08T01:45:03+01:00 DS923plus synostgdisk[11077]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 Tried support_disk_compatibility="yes" and support_disk_compatibility="no" Does not work. Maybe there is a new line "nvme kind" to find to bypass this compatibility check. It is available as a cache. Quote Link to comment Share on other sites More sharing options...
xpnas Posted December 8, 2022 Share #1365 Posted December 8, 2022 hello,guys. arpl-1.0-beta6 for ds920, cannot support lsi2308? I have added the arpl-addons/lsiutil/. After I installed it, it couldn't find the hard disk. Quote Link to comment Share on other sites More sharing options...
royeiror Posted December 8, 2022 Share #1366 Posted December 8, 2022 I managed to get to the installation using the 7 beta. But the 10 minutes timer runs out and the status under the Assistant stays migrateable. I feel very close, but there's something keeping me from booting. Is there a way to check a log or somesuch? Quote Link to comment Share on other sites More sharing options...
xtronets Posted December 8, 2022 Share #1367 Posted December 8, 2022 Is it possible to safely upgrade from DSM version 6.2.3-25426 Update 3 (Jun's loader 1.04b) to version 7.1 using this loader. If so I would ask for the procedure to follow. Quote Link to comment Share on other sites More sharing options...
h0va4 Posted December 8, 2022 Share #1368 Posted December 8, 2022 22 hours ago, Orphée said: So I was able to emulate a fake NVMe disk on DS923+ loader with Proxmox : root@DS923plus:/var/log# grep -i nvme messages 2022-12-08T01:39:13+01:00 DS923plus synostorage[6243]: synostorage_int_disk.c:442 Disk [nvme0n1] info cache generated 2022-12-08T01:39:13+01:00 DS923plus synostorage[6299]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:39:13+01:00 DS923plus synostorage[6299]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:39:13+01:00 DS923plus synostorage[6299]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:39:13+01:00 DS923plus synostorage[6299]: nvme_log_get.c:58 fread failed 2022-12-08T01:39:13+01:00 DS923plus synostorage[6299]: smartctl/smartctl_nvme_self_test_read.c:150 Error: SYNONVMeLogGet (self-test-log) -1 2022-12-08T01:39:13+01:00 DS923plus synostorage[6299]: SMARTNvmeSelfTestLogRead 2022-12-08T01:39:13+01:00 DS923plus synostorage[6299]: smartctl/smartctl_test_status_get.c:53 SMARTSelfTestLogRead(/dev/nvme0n1) fail 2022-12-08T01:39:13+01:00 DS923plus synostorage[6299]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:39:13+01:00 DS923plus synostorage[6299]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:39:13+01:00 DS923plus synostorage[6299]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:39:13+01:00 DS923plus synostorage[6299]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:39:14+01:00 DS923plus synostorage[6299]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:39:14+01:00 DS923plus synostorage[6007]: SYSTEM: Last message 'nvme_disk_vender_get' repeated 3 times, suppressed by syslog-ng on DS923plus 2022-12-08T01:39:17+01:00 DS923plus synostgd-disk[9648]: nvme_log_get.c:58 fread failed 2022-12-08T01:39:17+01:00 DS923plus synostgd-disk[9648]: smartctl/smartctl_nvme_self_test_read.c:150 Error: SYNONVMeLogGet (self-test-log) -1 2022-12-08T01:39:17+01:00 DS923plus synostgd-disk[9648]: SMARTNvmeSelfTestLogRead 2022-12-08T01:39:17+01:00 DS923plus synostgd-disk[9648]: smartctl/smartctl_test_status_get.c:53 SMARTSelfTestLogRead(/dev/nvme0n1) fail 2022-12-08T01:39:19+01:00 DS923plus hotplugd[9872]: DEVNAME:nvme0n1 2022-12-08T01:39:19+01:00 DS923plus hotplugd[9872]: DEVPATH:nvme0n1 2022-12-08T01:39:19+01:00 DS923plus hotplugd[9872]: hotplugd.c:1322 ==== SSD cache [nvme0n1] hotswap [add] ==== 2022-12-08T01:39:19+01:00 DS923plus hotplugd[9872]: disk/disk_config_single.c:122 apply /usr/syno/bin/DiskApmSet.sh 255 /dev/nvme0n1 1>/dev/null 2>&1 2022-12-08T01:39:19+01:00 DS923plus hotplugd[9872]: disk/disk_config_single.c:122 apply /usr/syno/bin/syno_disk_ctl --ncq-on /dev/nvme0n1 1>/dev/null 2>&1 2022-12-08T01:39:19+01:00 DS923plus hotplugd[9872]: hotplugd.c:1355 ==== SSD cache [nvme0n1] Model: [QEMU NVMe Ctrl ] ==== 2022-12-08T01:39:19+01:00 DS923plus hotplugd[9872]: hotplugd.c:1356 ==== SSD cache [nvme0n1] Serial number: [nvme-1] ==== 2022-12-08T01:39:19+01:00 DS923plus hotplugd[9872]: hotplugd.c:1357 ==== SSD cache [nvme0n1] Firmware version: [7.1.0 ] ==== Disk id: 1, Disk path: /dev/nvme0n1 2022-12-08T01:39:21+01:00 DS923plus synostgdisk[11364]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:44:56+01:00 DS923plus synostorage[6237]: synostorage_int_disk.c:442 Disk [nvme0n1] info cache generated 2022-12-08T01:44:56+01:00 DS923plus synostorage[6324]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:44:56+01:00 DS923plus synostorage[6324]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:44:56+01:00 DS923plus synostorage[6324]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:44:56+01:00 DS923plus synostorage[6324]: nvme_log_get.c:58 fread failed 2022-12-08T01:44:56+01:00 DS923plus synostorage[6324]: smartctl/smartctl_nvme_self_test_read.c:150 Error: SYNONVMeLogGet (self-test-log) -1 2022-12-08T01:44:56+01:00 DS923plus synostorage[6324]: SMARTNvmeSelfTestLogRead 2022-12-08T01:44:56+01:00 DS923plus synostorage[6324]: smartctl/smartctl_test_status_get.c:53 SMARTSelfTestLogRead(/dev/nvme0n1) fail 2022-12-08T01:44:56+01:00 DS923plus synostorage[6324]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:44:56+01:00 DS923plus synostorage[6324]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:44:56+01:00 DS923plus synostorage[6324]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:44:56+01:00 DS923plus synostorage[5980]: SYSTEM: Last message 'nvme_disk_vender_get' repeated 3 times, suppressed by syslog-ng on DS923plus 2022-12-08T01:44:56+01:00 DS923plus synostorage[6324]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:44:56+01:00 DS923plus synostorage[6324]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 2022-12-08T01:45:00+01:00 DS923plus synostgd-disk[10078]: nvme_log_get.c:58 fread failed 2022-12-08T01:45:00+01:00 DS923plus synostgd-disk[10078]: smartctl/smartctl_nvme_self_test_read.c:150 Error: SYNONVMeLogGet (self-test-log) -1 2022-12-08T01:45:00+01:00 DS923plus synostgd-disk[10078]: SMARTNvmeSelfTestLogRead 2022-12-08T01:45:00+01:00 DS923plus synostgd-disk[10078]: smartctl/smartctl_test_status_get.c:53 SMARTSelfTestLogRead(/dev/nvme0n1) fail 2022-12-08T01:45:01+01:00 DS923plus hotplugd[10265]: DEVNAME:nvme0n1 2022-12-08T01:45:01+01:00 DS923plus hotplugd[10265]: DEVPATH:nvme0n1 2022-12-08T01:45:01+01:00 DS923plus hotplugd[10265]: hotplugd.c:1322 ==== SSD cache [nvme0n1] hotswap [add] ==== 2022-12-08T01:45:01+01:00 DS923plus hotplugd[10265]: disk/disk_config_single.c:122 apply /usr/syno/bin/DiskApmSet.sh 255 /dev/nvme0n1 1>/dev/null 2>&1 2022-12-08T01:45:01+01:00 DS923plus hotplugd[10265]: disk/disk_config_single.c:122 apply /usr/syno/bin/syno_disk_ctl --ncq-on /dev/nvme0n1 1>/dev/null 2>&1 2022-12-08T01:45:01+01:00 DS923plus hotplugd[10265]: hotplugd.c:1355 ==== SSD cache [nvme0n1] Model: [QEMU NVMe Ctrl ] ==== 2022-12-08T01:45:01+01:00 DS923plus hotplugd[10265]: hotplugd.c:1356 ==== SSD cache [nvme0n1] Serial number: [nvme-1] ==== 2022-12-08T01:45:01+01:00 DS923plus hotplugd[10265]: hotplugd.c:1357 ==== SSD cache [nvme0n1] Firmware version: [7.1.0 ] ==== Disk id: 1, Disk path: /dev/nvme0n1 2022-12-08T01:45:03+01:00 DS923plus synostgdisk[11077]: nvme_disk_vender_get.c:47 Fail to get vendor name of 0x1b36 Tried support_disk_compatibility="yes" and support_disk_compatibility="no" Does not work. Maybe there is a new line "nvme kind" to find to bypass this compatibility check. It is available as a cache. Hello is ARPL the only way to update the user config file on hyper proxmox? I do not see any changes when doing the normal commands in TCRP 0.9.3.0 until I do the build command. See my question here: Quote Link to comment Share on other sites More sharing options...
frezeen Posted December 9, 2022 Share #1369 Posted December 9, 2022 pls can someone explain differences from modules and addons? Quote Link to comment Share on other sites More sharing options...
ngucy5767 Posted December 9, 2022 Share #1370 Posted December 9, 2022 Have any ppl was update 7.1.1 update-3 version? Quote Link to comment Share on other sites More sharing options...
gazzac72 Posted December 9, 2022 Share #1371 Posted December 9, 2022 (edited) I would wait with the release of 7.2 just round the corner not really worth it and talk is with 7.2 it will make all machines with m.2 instead of just cache they will also be usable as a storage pool. Edited December 9, 2022 by gazzac72 Quote Link to comment Share on other sites More sharing options...
AlexSoft_58 Posted December 9, 2022 Share #1372 Posted December 9, 2022 2 часа назад, ngucy5767 сказал: Have any ppl was update 7.1.1 update-3 version? Updated, no problems. 1 Quote Link to comment Share on other sites More sharing options...
AbuMoosa Posted December 9, 2022 Share #1373 Posted December 9, 2022 55 minutes ago, AlexSoft_58 said: Updated, no problems. What loader version your are on? Quote Link to comment Share on other sites More sharing options...
aportnov Posted December 9, 2022 Share #1374 Posted December 9, 2022 39 минут назад, AbuMoosa сказал: What loader version your are on? I confirm update 3 successfully. Loader version beta 7 ds3622 2 Quote Link to comment Share on other sites More sharing options...
AlexSoft_58 Posted December 9, 2022 Share #1375 Posted December 9, 2022 3 часа назад, AbuMoosa сказал: What loader version your are on? I don't remember exactly, one of the latest alpha versions 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.