Closed sunhater closed 1 year ago
yes i know but i was asking him to add a update all button so u dont have to the 4 tasks separately, is nice u can do it separately but it would be nice to have a update all option.
Beta 12 still has the same problem, cannot boot with more than 2 HHDs. A full update was done.
Please try my customized arpl called arc and report back. if it is possible please send us a screenshot from systeminfo in arc menu.
@fbelavenuto can you add this to your kernel defconfig to fix the tmpfs mode bug in serial log?
CONFIG_TMPFS=y CONFIG_SYSFS=y CONFIG_SYSFS_DEPRECATED=y
We need all 3 lines.
I have installed ARC 23.01.18, and it's working fine. I can now see 3 HHDs,
@fbelavenuto can you add this to your kernel defconfig to fix the tmpfs mode bug in serial log?
CONFIG_TMPFS=y CONFIG_SYSFS=y CONFIG_SYSFS_DEPRECATED=y
We need all 3 lines.
I'll check! Thanks again
@fbelavenuto can you add this to your kernel defconfig to fix the tmpfs mode bug in serial log? CONFIG_TMPFS=y CONFIG_SYSFS=y CONFIG_SYSFS_DEPRECATED=y We need all 3 lines.
I'll check! Thanks again
this in kernel defconfig and the eudev together, were the 2 things i found in serial output and if you look above, it is working. so i think if you add these line, you will have fixed it.
without this i had a problem to mount the tmpfs in early boot:
`Booting...
[ 3.860907] tmpfs: Unknown parameter 'mode' mount: mounting [ 3.861205] tmpfs: Unknown parameter 'mode' tmpfs on /dev/shm failed: Invali[ 3.862190] tmpfs: Unknown parameter 'mode' d argument mount: mounting tmpfs on /tmp failed: Invalid argument mount: mounting tmpfs on /run failed: Invalid argument Starting syslogd: OK Starting acpid: OK Starting klogd: OK Running sysctl: OK Populating /dev using udev: done`
@AuxXxilium u have a fork of this project?
@AuxXxilium u have a fork of this project?
yes, in my github. you can try it, it's a bit different but same base.
i know @fbelavenuto is adding the workarounds, so you can also wait for his release.
not trying to be rude but why two of the same product? why not work together ?
not trying to be rude but why two of the same product? why not work together ?
it's not the same. ;) i go another way.
care to explain ? also should i tried arc or arc automated? what are the difference?
care to explain ? also should i tried arc or arc automated? what are the difference?
one of them: you found the option arc patch? you did an installation with it? you found out that all services are working? second: some more addons ...
@AuxXxilium ok am gonna give it a try to arc automated
@AuxXxilium ok am gonna give it a try to arc automated
you should use arc - if you have access to the machine.
honestly i still dont know the difference between the two and yes i do have access to the machine but getting display out is a pain
honestly i still dont know the difference between the two and yes i do have access to the machine but getting display out is a pain
look in description:
arc: Arc is a new customized Redpill Loader for DSM 7 (Xpenology) with enhanced Hardwaresupport, Addons and semi-automated Installation. User interaction required and more customization options.
automated: Arc Automated is a new customized Redpill Loader for DSM 7 (Xpenology) with enhanced Hardwaresupport, Addons and full-automated Installation. No user interaction required and no customization options.
ohh i see, which one has more stuff? and why did u asked me if i had access to the machine ?
User interaction required and more customization options.
the automated is doing everything on his own. so you have to boot it and wait. the arc has menu for user interaction like arpl.
ok i understand, well am gonna play with both on virtualbox and report back, as to how does it differ from this project, what do u mean to went another way ?
ok i understand, well am gonna play with both on virtualbox and report back, as to how does it differ from this project, what do u mean to went another way ?
take a look and you will find it out. like i said: "you found the option arc patch? you did an installation with it? you found out that all services are working?" is the biggest win.
"you found the option arc patch?" am not sure what that means?
"you did an installation with it?" not yet
"you found out that all services are working?" idk yet
"you found the option arc patch?" am not sure what that means? "you did an installation with it?" not yet "you found out that all services are working?" idk yet
try it out and you will see. ;)
lol ok, thanks
@fbelavenuto this should fix it: AuxXxilium/arc-addons@f152d1a
@fbelavenuto can you add this to your kernel defconfig to fix the tmpfs mode bug in serial log?
CONFIG_TMPFS=y CONFIG_SYSFS=y CONFIG_SYSFS_DEPRECATED=y
We need all 3 lines.
How exactly to use arc-addons? I tried to replace the whole addons folder. Every .addon
file seams to be a .tar.gz
archive. I unziped the files to relevant folders (e.g. 9p.addon
to addons/9p
). Then I built the loader without any issues. But still cannot boot with more than 2 drives.
Do I need to compile a kernel with these 3 lines? Where is defconfig?
wait for faio please. or use the latest version from him. he added all patches yesterday.
How exactly to use arc-addons? I tried to replace the whole addons folder. Every
.addon
file seams to be a.tar.gz
archive. I unziped the files to relevant folders (e.g.9p.addon
toaddons/9p
). Then I built the loader without any issues. But still cannot boot with more than 2 drives.
Hi, please, can you try the inverse? Use arc loader with arpl addons. I couldn't reproduce this problem here
@fbelavenuto i recompile it on my system and give it a look - i saw in logs that tmpfs cant mount. wait for my update. ;)
i'm not able to fix arpl with my changes, something other is causing this bug. i used my lkms, addons and defconfig for kernel
@fbelavenuto @AuxXxilium I tested the latest version,arpl beta13 and arc v23.01.21a Start after configuration,it stop booting in the same place.
can you try 23.01.20? this one was stable and i have multi reports that it is working.
edit: i tried latest arc 23.01.21a in different systems, all is working.
@fbelavenuto @AuxXxilium i will be able to test on my system bare metal in a few days time, i have an AMD Ryzen 3 PRO 3200GE w/ Radeon Vega Graphics and a lsi2008 lsi card in it mode. also how come i cant get it working on bare metal but yes under a type 1 hypervisor?
@AuxXxilium v23.01.20 Cannot boot. v23.01.20-dev Can be used,it is no problem,can creat SHR. Later I found out,it cannot select powersched ,This causes it to fail to start.
v23.01.21a Can be used,addons must use default options (acpid & misc)
I'm very excited to let you know that beta 13 has fixed the issue with the two drives.
Thank you for you afford
@fbelavenuto after hours of trying and looking in all logs, i found this:
START /linuxrc.syno
START /linuxrc.syno.impl
[ 2.566767] random: nonblocking pool is initialized
addons.sh called with params early
acpid: cannot open input layer
acpid: inotify_add_watch() failed: No such file or directory (2)
acpid: starting up with netlink and the input layer
acpid: 1 rule loaded
acpid: waiting for events: event logging is off
it's the only bug that is shown in serial output.
@AuxXxilium so is your implementation of this working or not ? (i havent been able to try it yet)
@AuxXxilium so is your implementation of this working or not ? (i havent been able to try it yet)
i have no problems in 3 different machines here. native and vm tested. so don't know
@AuxXxilium so is your implementation of this working or not ? (i havent been able to try it yet)
i have no problems in 3 different machines here. native and vm tested. so don't know
fair enough i cant test now but i will as soon i have a chance.
@AuxXxilium so is your implementation of this working or not ? (i havent been able to try it yet)
i have no problems in 3 different machines here. native and vm tested. so don't know
fair enough i cant test now but i will as soon i have a chance.
no problem. the only issue i can find in arpl and arc is the mentioned above with acpid
"acpid" what is this used for?
"acpid" what is this used for?
acpid2 is a flexible and extensible daemon for delivering ACPI events. When an event occurs, it executes programs to handle the event. These events are triggered by certain actions, such as:
Pressing special keys, including the Power/Sleep/Suspend button Closing a notebook lid (Un)Plugging an AC power adapter from a notebook (Un)Plugging phone jack etc.
gotcha, i havent got to that point so that is why i dont know
gotcha, i havent got to that point so that is why i dont know
if you want, remove the acpid addon and try again, for 1 in my community it was working. but he lost the powerbutton. dsm is booting without any issue.
gotcha, i havent got to that point so that is why i dont know
if you want, remove the acpid addon and try again, for 1 in my community it was working. but he lost the powerbutton. dsm is booting without any issue.
huh, u lost me there.
@fbelavenuto after hours of trying and looking in all logs, i found this:
START /linuxrc.syno START /linuxrc.syno.impl [ 2.566767] random: nonblocking pool is initialized addons.sh called with params early acpid: cannot open input layer acpid: inotify_add_watch() failed: No such file or directory (2) acpid: starting up with netlink and the input layer acpid: 1 rule loaded acpid: waiting for events: event logging is off
it's the only bug that is shown in serial output.
I am starting acpid during "junior mode" to allow the machine to be turned off by the button, so I don't believe this is the problem. When starting the DSM itself, I remove acpid from memory to allow systemd to start within the DSM end system.
i know how it works, but we found out that the acpid is causing a boot stuck on baremetal supermicro boards. without using acpid everything is fine. with the old compressed version it will also work. with the new one it stuck in early boot. i tried it on vm to get a serial log and found the line above.
i know how it works, but we found out that the acpid is causing a boot stuck on baremetal supermicro boards. without using acpid everything is fine. with the old compressed version it will also work. with the new one it stuck in early boot. i tried it on vm to get a serial log and found the line above.
Ok, I'll remove from junior
@fbelavenuto The new version was tested(arpl-addons2.44),it‘s stopped at same place.
Still the same issue with arpl-1.0beta13. With arc-v23.01.23 cannot boot with any number of drives. Cannot boot with zero drives as well.
Please, test with this image: https://github.com/fbelavenuto/arpl/releases/tag/test1-morethan2disks Do not update nothing!
Please, test with this image: https://github.com/fbelavenuto/arpl/releases/tag/test1-morethan2disks Do not update nothing!
Now I can boot with 3 drives, but no more.
I'm trying to boot DSM 7.1 on real hardware with 6 SATA ports. ASRock Z370M-ITX/ac. It boots without any problem when one or two drives only are connected no matter where the drives are connected. But when I connect more than two drives, the DSM won't boot (I wait more than hour without ping). I have additional SATA card that supports 6 more drives. "Show SATA(s) # ports and drives" recognises all connected drives (both on motherboard and sata card). My goal is to boot with 10 connected drives but for now it's impossible. I tried with DS3615xs, DS3617xs and DS3622xs+ without success. Is there any boot log to figure out what is happening?