Automated RedPill Loader (ARPL)

[Orphée]

4 hours ago, AlexSoft_58 said:

Good afternoon, I need your help, literally 4 months ago active backup for business It worked correctly, after all the updates, it stopped working to the current version, Machine DVA3221. Namely, the storage was gone, although all rights to the folder are present. Tried to reinstall, it didn't work. Accordingly, I can not create a backup task. The destination for the backup is not displayed. Thanks for the answer. To the developers of the bootloader, BOW.

Softwares issues are not related to the loader.

Active backup for business needs a true real SN/Mac pair if I'm not wrong.

Maybe you created your tasks with a old software/DSM version and I'm the mean time Synology added some validation checks...

[IG-88]

i've run into a problem with the recent version of the loader, on start the 1st partition is filled up with log's until no space is left and then dsm shuts down and if i check the loader the 50MB partition has no space left

any options to disable the log duplication to the 1st partition?

 

exit: i increase the size of the 1st partition and it now cant fill it up (it ends with 57MB on the former 50MB), but still the system shuts down the moment its ready (i can see it already in synology assistant)

beside digging into the system partitions log i can use the log on usb

 

edit2: that seems to be the part where it goes wrong and all is shut down

"platform error"? might be anything wrong with the shimming and emulation?

its 7.1.1 U4 and it was running fine for about 4 weeks, only thing to mention is that i took out the 2nd nic 2 day ago

yesterday loaders 1st partition was broken (log file problem from above) and file system was damaged, i replaced it yesterday with a new one and, re-entered sn and mac's and did the option to recover a installed system from the advanced menu

 

edit3: i set up a new usb flash drive from scratch, removed 2nd nic and it did not find my already installed system to uses its configuration, it did a complete new install, so all configuration incl. packages are gone (as i have a backup a will try a configuration restore later), data volume is still there (as it should be), it wanted to do a scrubbing

not sure if i will stay with dva1622 after this, its also i little bit concerning to read this (how far will they go in "punish" mode?)

https://xpenology.com/forum/topic/68080-synology-backdoor/

 

journalctl

 

...
Mar 25 09:58:42 TheBox systemd[1]: Started SSDP service.
Mar 25 09:58:42 TheBox synosystemctl[17042]: systemd_restart.cpp:24 synosystemd: [ssdp] try-restarted.
Mar 25 09:58:42 TheBox synow3tool[17286]: Start Nginx Server in Normal Mode ......
Mar 25 09:58:42 TheBox systemd[1]: Reloaded Nginx.
Mar 25 09:58:43 TheBox index.cgi[16670]: external/external_microp_id_check.c:56 Fail to open synobios
Mar 25 09:58:43 TheBox root[17323]: platform error
Mar 25 09:58:43 TheBox index.cgi[16670]: open synobios error, error=(6)No such device or address
Mar 25 09:58:43 TheBox index.cgi[16670]: system_sys_init.c:81 synopoweroff: SYNOHWExternalControl[SYNO_SYS_SHUTDOWN] failed
Mar 25 09:58:43 TheBox index.cgi[16670]: feasibility_check.cpp:110 FeasibilityCheck: [Info] Start feasibility check [poweroff] with type [critical].
Mar 25 09:58:43 TheBox index.cgi[16670]: feasibility_check.cpp:129 FeasibilityCheck: [Info] [0] of feasibility check [poweroff] failed.
Mar 25 09:58:43 TheBox index.cgi[16670]: system_poweroff_pre_hook.c:22 synopoweroff: Begin SYNOPowerOffPreHook action.
Mar 25 09:58:43 TheBox index.cgi[16670]: plugin_action.c:317 synoplugin: [16670][PRE][poweroff][MAIN] Scripts=[CacheAdvisorPoweroffPlugin.sh,esynoscheduler-event-poweroff.sh]; Args=[POWEROFF_TYPE=poweroff]
Mar 25 09:58:43 TheBox index.cgi[17333]: plugin_action.c:319 synoplugin: [16670][PRE][poweroff][CacheAdvisorPoweroffPlugin.sh][17333] ExitCode: 0
Mar 25 09:58:43 TheBox index.cgi[17333]: plugin_action.c:319 synoplugin: [16670][PRE][poweroff][CacheAdvisorPoweroffPlugin.sh][17333] Runtime: 0.007s
Mar 25 09:58:43 TheBox index.cgi[17334]: plugin_action.c:319 synoplugin: [16670][PRE][poweroff][esynoscheduler-event-poweroff.sh][17334] ExitCode: 0
Mar 25 09:58:43 TheBox index.cgi[17334]: plugin_action.c:319 synoplugin: [16670][PRE][poweroff][esynoscheduler-event-poweroff.sh][17334] Runtime: 0.088s
Mar 25 09:58:43 TheBox index.cgi[16670]: plugin_action.c:317 synoplugin: [16670][PRE][poweroff][MAIN] Runtime: 0.089s
Mar 25 09:58:43 TheBox index.cgi[16670]: system_poweroff_pre_hook.c:27 synopoweroff: Finish SYNOPowerOffPreHook action.
Mar 25 09:58:43 TheBox index.cgi[16670]: feasibility_check.cpp:110 FeasibilityCheck: [Info] Start feasibility check [poweroff] with type [critical].
Mar 25 09:58:43 TheBox index.cgi[16670]: feasibility_check.cpp:129 FeasibilityCheck: [Info] [0] of feasibility check [poweroff] failed.
Mar 25 09:58:43 TheBox index.cgi[16670]: system_sys_init.c:133 synopoweroff: System is going to [poweroff]
Mar 25 09:58:43 TheBox systemd[1]: Stopped syno-mkdhparam.service.
Mar 25 09:58:43 TheBox systemd[1]: Stopping syno-mkdhparam.service...
Mar 25 09:58:43 TheBox systemd[1]: Removed slice system-getty.slice.
Mar 25 09:58:43 TheBox systemd[1]: Stopping system-getty.slice.
Mar 25 09:58:43 TheBox systemd[1]: Removed slice system-serial\x2dgetty.slice.
...

 

 

Spoiler

...

2023-03-25T09:58:22+01:00 TheBox synoiscsiep[12854]: iscsi_start_all.cpp:90:SYNOiSCSIStartAllWithoutLock Successfully started iSCSI service.
2023-03-25T09:58:22+01:00 TheBox kernel: [   68.044522] workqueue: max_active 1024 requested for vhost_scsi is out of range, clamping between 1 and 512
Internal disk info:
01: /dev/sata1    (BTTV4242074Y100FGN)
02: /dev/sata2    (ZR60PD25)
2023-03-25T09:58:22+01:00 TheBox synocheckhotspare[13134]: synocheckhotspare.c:223 [INFO] No hotspare config, skip hotspare config check. [0x2000 virtual_space_layer_get.c:96]
2023-03-25T09:58:22+01:00 TheBox notification_utils[13288]: notification_utils.cpp:526 open /dev/synobios error!
2023-03-25T09:58:22+01:00 TheBox notification_utils[13360]: notification_utils.cpp:526 open /dev/synobios error!
2023-03-25T09:58:22+01:00 TheBox notification_utils[13530]: notification_utils.cpp:526 open /dev/synobios error!
2023-03-25T09:58:22+01:00 TheBox notification_utils[13531]: notification_utils.cpp:526 open /dev/synobios error!
2023-03-25T09:58:23+01:00 TheBox notification_utils[13944]: notification_utils.cpp:526 open /dev/synobios error!
2023-03-25T09:58:23+01:00 TheBox notification_utils[14104]: notification_utils.cpp:526 open /dev/synobios error!
2023-03-25T09:58:23+01:00 TheBox notification_utils[14141]: notification_utils.cpp:526 open /dev/synobios error!
2023-03-25T09:58:23+01:00 TheBox notification_utils[14272]: notification_utils.cpp:526 open /dev/synobios error!
2023-03-25T09:58:25+01:00 TheBox fileindeX[14652]: fileindex.cpp:763 (UpdateLogLocation) fileindex update log location
2023-03-25T09:58:25+01:00 TheBox fileindeX[14652]: fileindex.cpp:767 (UpdateLogLocation) ignored volume: []
2023-03-25T09:58:25+01:00 TheBox fileindeX[14652]: fileindex.cpp:440 (PickDir) enum [volume1]
2023-03-25T09:58:25+01:00 TheBox fileindeX[14652]: fileindex.cpp:440 (PickDir) enum [volume2]
2023-03-25T09:58:25+01:00 TheBox fileindeX[14652]: fileindex.cpp:770 (UpdateLogLocation) picked new log dir [/volume1/@SynoFinder-log]
2023-03-25T09:58:25+01:00 TheBox fileindeX[14652]: fileindex.cpp:725 (MoveOldLogLocationLink) Old log dir link does not exist [/var/log/SynoFinder]
2023-03-25T09:58:25+01:00 TheBox fileindeX[14652]: fileindex.cpp:525 (relocateTo) link exists [/var/packages/SynoFinder/var/log] -> [/volume1/@SynoFinder-log]
2023-03-25T09:58:25+01:00 TheBox updater[14803]: utils.cpp:508 (RunAvailableUpdaters) Run SUS available updates
2023-03-25T09:58:25+01:00 TheBox updater[14803]: utils.cpp:527 (RunAvailableUpdaters) Run SUS mandatory updates
2023-03-25T09:58:25+01:00 TheBox root[14943]: == DSM 7.1.1 42962-4 finished boot up ==
2023-03-25T09:58:25+01:00 TheBox fileindeX[14983]: fileindex.cpp:786 (UpdateEtcLocation) fileindex update etc location
2023-03-25T09:58:25+01:00 TheBox fileindeX[14983]: fileindex.cpp:790 (UpdateEtcLocation) ignored volume: []
2023-03-25T09:58:25+01:00 TheBox fileindeX[14983]: fileindex.cpp:440 (PickDir) enum [volume1]
2023-03-25T09:58:25+01:00 TheBox fileindeX[14983]: fileindex.cpp:440 (PickDir) enum [volume2]
2023-03-25T09:58:25+01:00 TheBox fileindeX[14983]: fileindex.cpp:793 (UpdateEtcLocation) picked new etc dir [/volume1/@SynoFinder-etc-volume]
2023-03-25T09:58:25+01:00 TheBox fileindeX[14983]: fileindex.cpp:525 (relocateTo) link exists [/var/packages/SynoFinder/etc/etc-volume] -> [/volume1/@SynoFinder-etc-volume]
2023-03-25T09:58:25+01:00 TheBox synofinderdb[14986]: synofinderdb.cpp:101 (main) synofinderdb tool desc: update synofinder.db
2023-03-25T09:58:42+01:00 TheBox ipv4_change_hook_event[16994]: eth1 none->169.254.9.74
2023-03-25T09:58:43+01:00 TheBox root[17323]: platform error
2023-03-25T09:58:43+01:00 TheBox synodisklatencyd[12989]: synodisklatencyd.cpp:753 Stop disk latency monitor daemon by SIGTERM
2023-03-25T09:58:43+01:00 TheBox synoexternal[17378]: open synobios error, error=(6)No such device or address
2023-03-25T09:58:43+01:00 TheBox dhcp-client[17607]: stopped on eth0
2023-03-25T09:58:43+01:00 TheBox dhcp-client[17666]: stopped on eth2
2023-03-25T09:58:43+01:00 TheBox dhcp-client[17661]: stopped on eth1
2023-03-25T09:58:45+01:00 TheBox kernel: [   89.217215] Module [xt_ipvs] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   89.226296] Module [ip_vs_rr] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   89.247277] Module [ip_vs] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   89.277171] Module [xt_mark] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   89.288122] Module [iptable_mangle] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   89.309149] Module [br_netfilter] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   89.323157] Module [macvlan] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   89.334138] Module [bridge] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   89.374309] Module [stp] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   89.388218] Module [aufs] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   89.411123] Module [veth] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   89.425831] Module [nf_conntrack_ipv6] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   89.479388] Module [ip6table_filter] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   89.496278] Module [ip6_tables] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   89.522806] Module [xt_REDIRECT] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   89.537488] Module [xt_nat] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   89.552988] Module [nf_nat_redirect] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   89.569053] Module [xt_recent] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   89.587126] Module [xt_iprange] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   89.598112] Module [xt_limit] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   89.609106] Module [xt_state] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   89.619990] Module [xt_tcpudp] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   89.631972] Module [xt_multiport] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   89.645985] Module [xt_LOG] is removed.
2023-03-25T09:58:45+01:00 TheBox synopkgctl[18411]: /run/synoscgi-fastapi.sock APIRunner.cpp:1843 recv broken
2023-03-25T09:58:45+01:00 TheBox synopkgctl[18415]: sock_connect.cpp:49 (18415, 0) Failed to connect server [err: No such file or directory]
2023-03-25T09:58:45+01:00 TheBox synopkgctl[18415]: /run/synoscgi-fastapi.sock APIRunner.cpp:1837 connection broken
2023-03-25T09:58:45+01:00 TheBox synopkgctl[18419]: /run/synoscgi-fastapi.sock APIRunner.cpp:1843 recv broken
2023-03-25T09:58:45+01:00 TheBox synopkgctl[18414]: sock_connect.cpp:49 (18414, 0) Failed to connect server [err: No such file or directory]
2023-03-25T09:58:45+01:00 TheBox synopkgctl[18414]: /run/synoscgi-fastapi.sock APIRunner.cpp:1837 connection broken
2023-03-25T09:58:45+01:00 TheBox synoiscsiep[18612]: iscsi_stop_all.cpp:68:SYNOiSCSIStopAllWithoutLock Successfully stopped iSCSI service.
2023-03-25T09:58:45+01:00 TheBox synoiscsiep[18612]: iscsi_stop_all.cpp:68:SYNOiSCSIStopAllWithoutLock Successfully stopped iSCSI service.
2023-03-25T09:58:45+01:00 TheBox kernel: [   90.019366] Module [iscsi_target_mod] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   90.041943] FAT-fs (synoboot1): FAT: nls_disk load default table

2023-03-25T09:58:45+01:00 TheBox kernel: [   90.042104] Module [tcm_loop] is removed.
2023-03-25T09:58:45+01:00 TheBox synopkgctl[18414]: sock_connect.cpp:49 (18414, 0) Failed to connect server [err: No such file or directory]
2023-03-25T09:58:45+01:00 TheBox synopkgctl[18414]: /run/synoscgi-fastapi.sock APIRunner.cpp:1837 connection broken
2023-03-25T09:58:45+01:00 TheBox synopkgctl[18411]: sock_connect.cpp:49 (18411, 0) Failed to connect server [err: No such file or directory]
2023-03-25T09:58:45+01:00 TheBox synopkgctl[18411]: /run/synoscgi-fastapi.sock APIRunner.cpp:1837 connection broken
2023-03-25T09:58:45+01:00 TheBox kernel: [   90.055592] FAT-fs (synoboot1): FAT: nls_io load default table

2023-03-25T09:58:45+01:00 TheBox kernel: [   90.061338] Module [udf] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   90.083181] Module [vhost_scsi] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   90.094197] Module [isofs] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   90.107061] Module [vhost] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   90.120939] Module [target_core_user] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   90.136024] Module [target_core_ep] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   90.153984] Module [target_core_multi_file] is removed.
2023-03-25T09:58:45+01:00 TheBox kernel: [   90.174302] Module [target_core_file] is removed.
2023-03-25T09:58:46+01:00 TheBox kernel: [   90.193092] Module [target_core_iblock] is removed.
2023-03-25T09:58:46+01:00 TheBox synopkgctl[18419]: sock_connect.cpp:49 (18419, 0) Failed to connect server [err: No such file or directory]
2023-03-25T09:58:46+01:00 TheBox synopkgctl[18419]: /run/synoscgi-fastapi.sock APIRunner.cpp:1837 connection broken
2023-03-25T09:58:46+01:00 TheBox kernel: [   90.214074] Module [target_core_mod] is removed.
2023-03-25T09:58:46+01:00 TheBox kernel: [   90.231079] Module [syno_extent_pool] is removed.
2023-03-25T09:58:46+01:00 TheBox kernel: [   90.253096] Module [rodsp_ep] is removed.
2023-03-25T09:58:46+01:00 TheBox synopkgctl[18415]: sock_connect.cpp:49 (18415, 0) Failed to connect server [err: No such file or directory]
2023-03-25T09:58:46+01:00 TheBox synopkgctl[18415]: /run/synoscgi-fastapi.sock APIRunner.cpp:1837 connection broken
2023-03-25T09:58:46+01:00 TheBox root[18896]: Check device busy: error, refer: /var/log/DeviceBusyList
2023-03-25T09:58:46+01:00 TheBox syno-coredump-store.sh[18967]: Set coredump path to [/var/crash]
2023-03-25T09:58:46+01:00 TheBox synoiscsihook[18951]: iscsi_stop_all.cpp:68:SYNOiSCSIStopAllWithoutLock Successfully stopped iSCSI service.
2023-03-25T09:58:47+01:00 TheBox umount[19011]: Kill the process "notification_se" with /volume1/@appstore/SynologyApplicationService/tools/notification_send.
2023-03-25T09:58:47+01:00 TheBox umount[19011]: Kill the process "pgbouncer" with /volume1/@appstore/SynologyApplicationService/daemon/pgbouncer.
2023-03-25T09:58:47+01:00 TheBox umount[19011]: Kill the process "node" with /volume1/@appstore/Node.js_v18/usr/local/bin/node.
2023-03-25T09:58:47+01:00 TheBox umount[19011]: Kill the process "session_watcher" with /volume1/@appstore/SynologyApplicationService/daemon-tasks/session_watcher.
2023-03-25T09:58:47+01:00 TheBox umount[19011]: Kill the process "session_watcher" with /volume1/@appstore/SynologyApplicationService/daemon-tasks/session_watcher.

 

Edited March 25, 2023 by IG-88

[andrey9492]

On 3/23/2023 at 8:52 PM, IG-88 said:

4.4.59+ is dsm 6.2

maybe you installed a package that copied the old driver, there is no information what dsm type you installed or what hardware you used and if it was a fresh install or a update

nct6775 files in the loaders \modules\ directory are all ok

check /lib/modules/udpates/ for old files that might need to be deleted

 

you can also extract the right files manually from the loaders 3rd partition in modules are the tgz files for the platforms, depends on what you installed , 918+ would be apollolake

 

 

Yea, i realized my mistake a couple of minutes after writing that post, that module was the one i had compiled in the past and it was still present in the "Task Schedule" post upgrade.

I've used the 920+ geminilake package (Asrock J5005 board) that has a NCT6796D chip. This one is not present in the drivers int 4.4.180+, currently my attempts to compile them are leading to kernel panics.

Will update the post with the drivers when i have a functioning one.

 

[sandro_66]

Good afternoon, dear friends and colleagues of Xpenology! I have an ARPL 1.0 beta DVA1622 bootloader installed on a laptop with only 1 SSD. To expand the storage, I plan to connect external hard drives with additional power via USB3.0. Unfortunately, they are normally defined in the system as USB devices and their functionality is very limited compared to internal SATA HDDs (you cannot record video from Surveillance Station, and so on). I need these USB drives to be "hardware" detected in the system as internal SATA drives, including after rebooting the system and turning it off. As far as I understand, ARPL automatically assigns disks, and to be honest, I don’t really understand how to write commands like SataPortMap, DiskMap (and, as I understand it, they don’t work in ARPL, although I may be wrong). Please tell me, friends, how can I solve my problem. Thanks a lot for any help!

[cpresco]

On 3/24/2023 at 6:38 PM, IG-88 said:

not sure if i will stay with dva1622 after this, its also i little bit concerning to read this (how far will they go in "punish" mode?)

https://xpenology.com/forum/topic/68080-synology-backdoor/

 

Yeah... this doesn't look great.

[Sharkboy]

Is that possible to upgrade serial number from synology ssh. I try to restart syno, and connect to http://syno:7681/ but after 3 second it close connection and start booting syno OS. i dont have enought time to change serial

[Orphée]

1 hour ago, Sharkboy said:

Is that possible to upgrade serial number from synology ssh. I try to restart syno, and connect to http://syno:7681/ but after 3 second it close connection and start booting syno OS. i dont have enought time to change serial

you have to select "configure loader" at when boot menu appears... then you will be able to freely re-configure serial and build loader again.

[gregos]

Hello Guys!

I need some help, as i can not login to DSM because of the 2Fa issue. I was trying many different methods as workaround, but still no luck. I was coming from tcrp 0.8.0.0 loader DSM 7.1.1-42661 to ARPL latest and DSM 7.1.1-42962. Everything went fine with the update (almost), now i could login to DSM GUI, if i wouldn't face this  problem. I tried to SSH into the NAS, but it's not enabled, and i did not find any solution to enable it. I don't have any other admin account without 2 factor authentication.

I found the live linux way solution, but i couldn't mount system partition, i have no idea why. (i was trying to find the 2Fa file mentioned by someone on this forum).

I'm not familiar with linux commands ,also i'm not an IT expert, but i really want to save my settings / files. (Synology Drive client and mapped network drives are fine - which were logged in prior to update). Do any of you have any idea how to save it? Thank you!

[Jerode]

I apologize in advance for my bad English.

Dear IG-88, the ARPL bootloader has a fairly small set of drivers for peripherals, I saw your topic on the forum "Driver extension jun 1.02b/DSM6.1.x for 3615xs / 3617xs / 916+" in which you posted an extended package of drivers for various peripheral devices. If you don't mind, please build drivers for external SATA controllers based on Marvell 923x and AS Media 106x, 116x chips for ARPL bootloader

[The Chief]

2 часа назад, Jerode сказал:

AS Media 106x

ASMedia 106x (1063 at least) works in current ARPL version for me (2-port mini-pcie).

[gregos]

11 hours ago, gregos said:

Hello Guys!

I need some help, as i can not login to DSM because of the 2Fa issue. I was trying many different methods as workaround, but still no luck. I was coming from tcrp 0.8.0.0 loader DSM 7.1.1-42661 to ARPL latest and DSM 7.1.1-42962. Everything went fine with the update (almost), now i could login to DSM GUI, if i wouldn't face this  problem. I tried to SSH into the NAS, but it's not enabled, and i did not find any solution to enable it. I don't have any other admin account without 2 factor authentication.

I found the live linux way solution, but i couldn't mount system partition, i have no idea why. (i was trying to find the 2Fa file mentioned by someone on this forum).

I'm not familiar with linux commands ,also i'm not an IT expert, but i really want to save my settings / files. (Synology Drive client and mapped network drives are fine - which were logged in prior to update). Do any of you have any idea how to save it? Thank you!

Is there any way to reset login creditanials (like on a physical synology NAS reset Method 1) from command prompt (when loader is booted "root@arpl" or if i go to configure loader option, and then ssh into there ? Or there's no way doing that. If thats possible, can you please tell me how? Thanks

[Sanya_13]

Hello guys,

 

I`ve installed lastest DSM(DSM 7.1.1-42962 Update 4) using ARPL on my proxmox, everything works fine, but I noticed daily warnings about improper shutdown in DSM logs:

"System booted up from an improper shutdown".

I get them at least one a day at random time. I decided to reboot VM automatically every night at 3 AM, hopping it will decrease amount of errors, but no help.

For example tonight I got improper shutdown at 04:44 AM, after 1h 44 minutes. I checked proxmox logs, there was zero load on the system. No errors in proxmox logs. Other proxmox VM runing fine. 

I connected to DSM via SSH and checked different logs in /var/logs/ and didn`t find any errors before the 04:44 AM. Looks like somebody did a hard reset. 

 

Please advice. Maybe I looked wrong log files? Are there any logs for ARPL kernel? I checked /var/log/kern.log in DSM and no errors. 

Thank you! 

Edited March 30, 2023 by Sanya_13

[Gosha1991]

 

Good afternoon. Installed bootloader arpl v.1.0 beta 10a. Can I upgrade from DSM 7.1.1-42962 Update 3 to DSM 7.1.1-42962 Update 4? Or will there be any problems?

Please excuse my english.

Edited March 30, 2023 by Gosha1991

[dj_nsk]

2 часа назад, Gosha1991 сказал:

 

Good afternoon. Installed bootloader arpl v.1.0 beta 10a. Can I upgrade from DSM 7.1.1-42962 Update 3 to DSM 7.1.1-42962 Update 4? Or will there be any problems?

Please excuse my english.

Yes, You can!  

[Jerode]

Gosha1991 you can ask your question here in this thread of the Russian-speaking forum link (as I understand it, Russian is your native language)

[Black6spdZ]

Also seeing the 3-drive issue and improper shutdown message as others above.. v1.1-b2a 3622+ on Haswell i5-4690S / 16GB "tried LSI 9308-IT and Asmedia 1068 in addition to one other SSD connected to onboard SATA

[carbon6600]

Hello, I have proxmox, how to add virtio or iscsi disk

 

 

 

How to fix it?



 

Edited March 31, 2023 by carbon6600

[lord_kimbou]

19 hours ago, carbon6600 said:

Hello, I have proxmox, how to add virtio or iscsi disk

 

 

 

How to fix it?



 

 

I don't Know, If the problem become from Aprl Update or Virtio Scsi proxmox update (proxmox 7.4-3), but I can't add scsi hard disk either.. My Vm recognize when boot on bios, but I can't see on Aprl.. It's a problem for me too....

Edited April 1, 2023 by lord_kimbou

[tyhgpa]

Hello.
Succesfull setup.
Intel Pentium G4560T
Gigabyte GA-H110TN-GSM PLUS (rev. 1.0)

2x4GB DDR4 2400MHz
3TB WD Purple

internal usb card reader as boot device

THX A LOT

 

Edited April 1, 2023 by tyhgpa

[sonic9]

Le 30/03/2023 à 08:30, Sanya_13 a dit :

Hello guys,

 

I`ve installed lastest DSM(DSM 7.1.1-42962 Update 4) using ARPL on my proxmox, everything works fine, but I noticed daily warnings about improper shutdown in DSM logs:

"System booted up from an improper shutdown".

I get them at least one a day at random time. I decided to reboot VM automatically every night at 3 AM, hopping it will decrease amount of errors, but no help.

For example tonight I got improper shutdown at 04:44 AM, after 1h 44 minutes. I checked proxmox logs, there was zero load on the system. No errors in proxmox logs. Other proxmox VM runing fine. 

I connected to DSM via SSH and checked different logs in /var/logs/ and didn`t find any errors before the 04:44 AM. Looks like somebody did a hard reset. 

 

Please advice. Maybe I looked wrong log files? Are there any logs for ARPL kernel? I checked /var/log/kern.log in DSM and no errors. 

Thank you! 

What CPU in proxmox host ? What vCPU set in VM ?

[Andrushencia]

@fbelavenutoI have machine with r8101 ethernet can you support it?

[Peter Suh]

9 minutes ago, Andrushencia said:

@fbelavenutoI have machine with r8101 ethernet can you support it?

 

 

There is no news that fabio has been on vacation for over two weeks.
My successor to fabio's arpl-modules repo
M SHELL for TCRP is ready for r8101.

 

https://github.com/PeterSuh-Q3/arpl-modules/tree/main/broadwellnk-4.4.180

 

https://github.com/PeterSuh-Q3/tinycore-redpill/releases/tag/v0.9.4.3-1

 

Edited April 1, 2023 by Peter Suh

[bloodilo]

Hi guys! I have a small issue and can’t find a solution for it. As I not really new to XPenology and was able to solve all the issues before by myself I assume I understand something wrong. It would be great if You can point me to the solution if such exist. The point is just got new Asrock J5040 Mobo and were able to upgrade my NAS from Asrock j3455 ARPL 918+ DSM 7.1 to Asrock j5040 ARPL 920+ DSM 7.1. Everything works fine except info about CPU model in system info. I see Celeron J4125 there instead Pentium J5040. Not a big issue, but it would be nice to see right info shown. Is where is a solution for it?

[abced]

 

2 minutes ago, bloodilo said:

Hi guys! I have a small issue and can’t find a solution for it. As I not really new to XPenology and was able to solve all the issues before by myself I assume I understand something wrong. It would be great if You can point me to the solution if such exist. The point is just got new Asrock J5040 Mobo and were able to upgrade my NAS from Asrock j3455 ARPL 918+ DSM 7.1 to Asrock j5040 ARPL 920+ DSM 7.1. Everything works fine except info about CPU model in system info. I see Celeron J4125 there instead Pentium J5040. Not a big issue, but it would be nice to see right info shown. Is where is a solution for it?

Activate the cpuinfo addon.

[bloodilo]

9 minutes ago, abced said:

 

Activate the cpuinfo addon.

Wow! Works like a charm! Thanks a lot!

 

Unfortunately I didn’t see any tips about addons as meet ARPL for the first time, so I have no clue about it. Is there any topic I can read about it or possible You can tell me what addons are required for my Mobo?