Jump to content
XPEnology Community

shibby

Member
 View Profile  See their activity

  • Posts

    155

  • Joined

  • Last visited

  • Days Won

    5

 Content Type 

Posts posted by shibby

    TinyCore RedPill Loader Build Support Tool ( M-Shell )

    in Software Modding

    Posted

    On 3/17/2024 at 7:03 AM, Peter Suh said:

    Perhaps you want to take the loader.img file that was created in the middle.

    Yep, this is exacly what i need :)

    At the moment i`m running DSM 6.2.3 for DS3615xs using Jun`s loader 1.3b.
    aa73b4d13e0fe91e30d2b63c1219ed5ed38e49f8.thumb.jpeg.60e463f52880da22af952b37c101519d.jpeg

    I am able to boot loader from USB drive by pressing "backup" button for 30 seconds on boot. This is a temporary solution. After all i want to flash loader permamently to ReadyNAS flash by "dd" command.

     

    I tried to boot your TCRP from USB drive and it works. I`ll try to compile redpill using M-Shell tools BUT after all i will not able to flash loader to internal flash memory 😕 Each time when i will restart ReadyNAS i will have to push "backup" button to start NAS from USB drive.

    TinyCore RedPill Loader Build Support Tool ( M-Shell )

    in Software Modding

    Posted

    @Peter Suh I want to run xpenology on my old Netgear Pro4 NAS with Intel Atom. I found tutorial how to do this using old 6.2.3 JUN`s Mod but i want to try to use latest DSM version :)

     

    To do this i need to compile redpill.img in "vanilla style" - meaning without TCRP (pure compile of redpill-load repository). I tried to do this using your repo, i changed some lines in build-loader.sh file but i got an error ".../img-mnt/part1/custom.gz, no left space on device"

     

    Can you help me?

    TinyCore RedPill Loader Build Support Tool ( M-Shell )

    in Software Modding

    Posted

    Sorry but this looks like "wound dressing" but not like a fix or solution. If i good understant, when NAS will be rebooted or has power failure then after boot VM will not start automatically. Then your addon will detect it in log and recreate folder`s path and permissions but until i will not manually start VM it will be off. This is not a solution.

     

    I still dont understand when this bug (problem with loading modules for SAN Manager) was appear. Is this was after added offline installer for M-Shell? I made some test and when i manually edit menu.sh file and force to update tag:v1.0.0.0 and then rebuild the loader then all works as intended (SAN Manager works, VMM is starting and i can run Virtual Machine without any issue.

     

    I really think you should come back to v1.0.0.0 as "prod" repository and working on "offline instalation" in "dev" repository.

    TinyCore RedPill Loader Build Support Tool ( M-Shell )

    in Software Modding

    Posted · Edited by shibby

    I`m using you M-Shell Tools from the beginning. At the moment i`m on 0.9.5.0 with latest DSM version installed and VMM works correct. So there is something wrong with M-Shell,  not with DSM. Maybe we should step back, back to 100% working M-Shell and then do updates step-by-step and try to find a moment when SAN/VMM has been broken.

    Two days ago i made an update from 7.1.1 to 7.2.1 of my friend Xpenology. He`s using VMM for Virtual Machine of Home Assistant. After upgrade he cannot run Home Assistant VM. This is a huge problem for him because the entire smart home installation is based on Home Assistant! and i cannot help him.

     

    I really want to see in M-Shell project two changes:
    - do not implement changes directly to "prod" repository. You should use "dev" and then pull changes to "prod". Users should be able to select with M-Shell repository they want to use

    - M-Shell versioning: do not update M-Shell automatically. If user want to use older version of M-Shell then they should be able to do this. Much more users need a working SAN/VMM instead of exsample "M-Shell offline instalation". If i am sure that specific version of M-Shell is working well then i should be able to use them. At the moment i cannot do this because M-Shell will be automatically updated.

    • Like 2

    TinyCore RedPill Loader Build Support Tool ( M-Shell )

    in Software Modding

    Posted · Edited by shibby

    @Peter Suh yesterday i upgraded Xpenology from 7.1.1 (Juns mod) to 7.2.1 using your latest tinycore-redpill-m-shell release and i found a HUGE issue - modules required by ScsiTarget (SAN Manager) are not loaded and Virtual Machine Manager service does not work.

    It`s easy to reproduce (on baremetal and proxmox):

    1) install fresh TCRP: i tested DS920+ and DS923+ with DDSML

    2) SAN Manager is installed by default (and it`s working) so install Virtual Machine Manager

    3) reboot Xpenology

    4) SAN Manager and VMM has warning (both are stopped and cannot be repaired)

     

    obraz.png.25e16a844f659cc48b1c90318d4d54ce.png

     

    In logs /var/log/iscsi.log we can find

    Quote

    2024-01-17T21:43:57+01:00 NAS-ITX synoiscsiep[15029]: iscsi_lun_service_start_all.cpp:90:SYNOiSCSILunServiceStartAllWithoutLock Mounting configfs on /config
    2024-01-17T21:43:57+01:00 NAS-ITX synoiscsiep[15029]: iscsi_lun_service_start_all.cpp:105:SYNOiSCSILunServiceStartAllWithoutLock mkdir(/config/target/core/iblock_0, 448), err=No such file or directory
    2024-01-17T21:43:57+01:00 NAS-ITX synoiscsiep[15029]: iscsi_start_all.cpp:22:SYNOiSCSIStartAllWithoutLock SYNOiSCSILunServiceStartAllWithoutLock(), err=Failed to create directory
    2024-01-17T21:43:57+01:00 NAS-ITX synoiscsiep[15029]: iscsi_start_all.cpp:115:SYNOiSCSIStartAll SYNOiSCSIStartAllWithoutLock(), err=Failed to create directory
    2024-01-17T21:43:57+01:00 NAS-ITX synoiscsiep[15032]: iscsi_lun_service_start_all.cpp:105:SYNOiSCSILunServiceStartAllWithoutLock mkdir(/config/target/core/iblock_0, 448), err=No such file or directory
    2024-01-17T21:43:57+01:00 NAS-ITX synoiscsiep[15032]: vhost_scsi_start_all.cpp:13:SYNOiSCSIVhostStartAllWithoutLock SYNOiSCSILunServiceStartAllWithoutLock(), err=Failed to create directory
    2024-01-17T21:43:57+01:00 NAS-ITX synoiscsiep[15032]: vhost_scsi_start_all.cpp:39:SYNOiSCSIVhostStartAll SYNOiSCSIVhostStartAllWithoutLock(), err=Failed to start service
    2024-01-17T21:43:59+01:00 NAS-ITX synoiscsiep[15035]: iscsi_lun_service_start_all.cpp:105:SYNOiSCSILunServiceStartAllWithoutLock mkdir(/config/target/core/iblock_0, 448), err=No such file or directory
    2024-01-17T21:43:59+01:00 NAS-ITX synoiscsiep[15035]: iscsi_lun_service_start_all.cpp:145:SYNOiSCSILunServiceStartAll SYNOiSCSILunServiceStartAllWithoutLock(), err=Failed to create directory
    2024-01-17T21:43:59+01:00 NAS-ITX synoiscsiep[15045]: iscsi_lun_service_start_all.cpp:105:SYNOiSCSILunServiceStartAllWithoutLock mkdir(/config/target/core/iblock_0, 448), err=No such file or directory
    2024-01-17T21:43:59+01:00 NAS-ITX synoiscsiep[15045]: iscsi_loopback_start_all.cpp:29:SYNOiSCSILoopbackStartAll SYNOiSCSILunServiceStartAllWithoutLock(), err=Failed to create directory
    2024-01-17T21:43:59+01:00 NAS-ITX synoiscsiep[15074]: iscsi_lun_service_start_all.cpp:105:SYNOiSCSILunServiceStartAllWithoutLock mkdir(/config/target/core/iblock_0, 448), err=No such file or directory
    2024-01-17T21:43:59+01:00 NAS-ITX synoiscsiep[15074]: fc_start_all.cpp:53:SYNOFCStartAll SYNOiSCSILunServiceStartAllWithoutLock(), err=Failed to create directory

     

    On working Synology NAS on logs i found:

    Quote

    2023-12-21T13:25:39+01:00 NAS-ITX synoiscsiep[12513]: iscsi_module_manage.cpp:56:insmod_if_module_file_exist Module 'target_core_mod' is loaded
    2023-12-21T13:25:39+01:00 NAS-ITX synoiscsiep[12513]: iscsi_module_manage.cpp:56:insmod_if_module_file_exist Module 'target_core_iblock' is loaded
    2023-12-21T13:25:39+01:00 NAS-ITX synoiscsiep[12513]: iscsi_module_manage.cpp:56:insmod_if_module_file_exist Module 'target_core_file' is loaded
    2023-12-21T13:25:39+01:00 NAS-ITX synoiscsiep[12513]: iscsi_module_manage.cpp:56:insmod_if_module_file_exist Module 'target_core_multi_file' is loaded
    2023-12-21T13:25:39+01:00 NAS-ITX synoiscsiep[12513]: iscsi_module_manage.cpp:56:insmod_if_module_file_exist Module 'target_core_ep' is loaded
    2023-12-21T13:25:39+01:00 NAS-ITX synoiscsiep[12513]: iscsi_module_manage.cpp:56:insmod_if_module_file_exist Module 'target_core_user' is loaded
    2023-12-21T13:25:39+01:00 NAS-ITX synoiscsiep[12513]: iscsi_lun_service_start_all.cpp:90:SYNOiSCSILunServiceStartAllWithoutLock Mounting configfs on /config
    2023-12-21T13:25:39+01:00 NAS-ITX kernel: target_core_file.c:152:fd_attach_hba RODSP plugin for fileio is enabled.
    2023-12-21T13:25:39+01:00 NAS-ITX kernel: target_core_file.c:159:fd_attach_hba ODX Token Manager is enabled.
    2023-12-21T13:25:39+01:00 NAS-ITX kernel: target_core_multi_file.c:91:fd_attach_hba RODSP plugin for multifile is enabled.
    2023-12-21T13:25:39+01:00 NAS-ITX kernel: target_core_ep.c:795:ep_attach_hba RODSP plugin for epio is enabled.
    2023-12-21T13:25:39+01:00 NAS-ITX kernel: target_core_ep.c:802:ep_attach_hba ODX Token Manager is enabled.
    2023-12-21T13:25:39+01:00 NAS-ITX synoiscsiep[12513]: iscsi_module_manage.cpp:56:insmod_if_module_file_exist Module 'iscsi_target_mod' is loaded
    2023-12-21T13:25:39+01:00 NAS-ITX synoiscsiep[12513]: iscsi_module_manage.cpp:56:insmod_if_module_file_exist Module 'tcm_loop' is loaded
    2023-12-21T13:25:39+01:00 NAS-ITX synoiscsiep[12513]: iscsi_start_all.cpp:89:SYNOiSCSIStartAllWithoutLock Successfully started iSCSI service.
    2023-12-21T13:25:39+01:00 NAS-ITX synoiscsiep[12531]: iscsi_module_manage.cpp:56:insmod_if_module_file_exist Module 'vhost' is loaded
    2023-12-21T13:25:39+01:00 NAS-ITX synoiscsiep[12531]: iscsi_module_manage.cpp:56:insmod_if_module_file_exist Module 'vhost_scsi' is loaded

     

    Those modules ARE NOT loaded right now. But when i load all those modules manually via "modprobe" then repair SAN Manager package and it works!! but only to the next reboot :(

     

    In /var/log/messages i  found

    Quote

    2024-01-17T21:43:36+01:00 NAS-ITX kernel: [   32.263150] scsi_mod: exports duplicate symbol __scsi_add_device (owned by kernel)
    2024-01-17T21:43:36+01:00 NAS-ITX kernel: [   32.477481] scsi_mod: exports duplicate symbol __scsi_add_device (owned by kernel)
    2024-01-17T21:43:36+01:00 NAS-ITX kernel: [   32.522720] scsi_mod: exports duplicate symbol __scsi_add_device (owned by kernel)
    2024-01-17T21:43:36+01:00 NAS-ITX kernel: [   32.598157] scsi_mod: exports duplicate symbol __scsi_add_device (owned by kernel)

     

    maybe this will be some clue

     

    Then i tried build redpill with selected EUDEV instead of DDSML but result was the same. With DDSML+EUDEV still the same.

     

    another thing which i didnt understand is why under proxmox, synology detect synoboot drive as first disk?? Should be 2 drives, not 3.

    obraz.png.37f04761375bcc762863de819b394bab.png

     

    obraz.png.6338c99bea2c9da64ebb1d827dff43dd.png

     

    on baremetal this issue is not appear

     

    Then i downloaded tinycore-m-shell 1.0.0.0, mounted as sata0, compiled DS920+ DDSML

    SAN Manager still doesn`t work BUT at least this fixed drive list (synoboot disk disappear from list)

     

    obraz.png.5f9a1ad8ec1904636b6447ce99033da3.png

    obraz.png.33657bb69592c71edc314f7da6ce3f16.png

     

    The last one what i did was compile DS923+ DDSML and migrate from DS920+. First boot after migration and SAN Manager works (VMM also)! but after reboot both failed.

     

    i gave up 😕

     

    • Thanks 1

    TinyCore RedPill Loader Build Support Tool ( M-Shell )

    in Software Modding

    Posted · Edited by shibby

    @Peter Suh i have another problem on DS3622xs+, this time is my 10GbE netcard - tn40xx driver. Fresh instalation using M-Shell and card is not detected - dmesg shows only:

    Quote

    [  132.060523] tn40xx low_mem_msg proc entry initialized
    [  132.060757] tn40xx low_mem_counter proc entry initialized
    [  132.060991] tn40xx debug_msg proc entry initialized
    [  132.061202] tn40xx: Tehuti Network Driver, 0.3.6.12.3

     

    but if i unload this module (modprobe -r tn40xx) and download this module

    https://github.com/PeterSuh-Q3/arpl-modules/blob/main/broadwellnk-4.4.302/tn40xx.ko

     

    and load (insmod <file> then card is shows up

    Quote

    [ 1392.085373] tn40xx: Tehuti Network Driver, 0.3.6.14
    [ 1392.085560] tn40xx: Supported phys : MV88X3120 MV88X3310 MV88E2010 QT2025 TLK10232 AQR105
    [ 1392.085967] tn40xx 0000:05:00.0: enabling device (0000 -> 0002)
    [ 1392.086292] tn40xx: srom 0x0 HWver 16 build 0 lane# 4 max_pl 0x0 mrrs 0x2
    [ 1392.299150] tn40xx: PHY detected on port 0 ID=2B09AB - MV88X3310 (A1) 10Gbps 10GBase-T
    [ 1392.299446] tn40xx: PHY type by svid 0 found 4
    [ 1395.367040] tn40xx: MV88X3310 firmware code is running
    [ 1395.367317] tn40xx: MV88X3310 FW version is 0.2.4.0
    [ 1395.555744] tn40xx: fw 0xe
    [ 1395.555860] tn40xx: eth1, Port A
    [ 1395.556001] tn40xx: 1 1fc9:4027:1432:8104
    [ 1395.556161] tn40xx: detected 1 cards, 1 loaded

     

    How can i include correct driver to TCRP?

    TinyCore RedPill Loader Build Support Tool ( M-Shell )

    in Software Modding

    Posted · Edited by shibby

    On 8/5/2023 at 3:32 PM, Peter Suh said:

    [HBA - H200, H310 recommended setting]

     

    DDSML, DS3622xs+, not EUDEV

     

    "DiskIdxMap": "1000",
    "SataPortMap": "12",
    "SasIdxMap: "0",
    "MaxDisks: "24"

    I built another baremetal with H310 IT-mode (latest DS3622xs+ with Friend). When i set as you mention then i see all 8 drives connected to H310 but i also have 2 drives connected to motherboard (sata1 and 2) and those 2 drives has not been detected.

     

    obraz.png.b02332193a8101479763549155c552fe.png

     

    In default configuration (DiskIdxMap=0, SasIdxMap=0 SataPortMap) 2 drives connected directly to motherboard are detected as bay 1 and 2 but not all drives connected to H310 are detected - it shows only 5 drives in bay 8,9,10,11,12 - it looks like channels are duplicated (channel A - 8,9,10,11 and channel B - 9,10,11,12).

    I tried a lot of "DiskIdxMap & SataPortMap" combinations and always some of drives has not been detected. I don`t understand "logic" of those two variables but FINALLY with:

    DiskIdxMap=0011

    SataPortMap=24

    SasIdxMap=0

    MaxDisks=24

     

    all drives has been detected - maybe not perfectly but it works!!
    1-2 bay - motherboards sata 1 and 2

    3 bay is empty?

    4-11 bay - 8 drives connected to H310

     

    BUT for test i connected another drive... to sata6 port on motherboard, then all H310`s drives disapper :D only sata1&2 has been showed. WTF...

     

    if I understand correctly SataPortMap=xyz means:

    - x - numer of sata port on 1st controller
    - y - numer of sata port on 2nd controller
    - z - numer of sata port on 3rd controller

    ...

    So in my example should be 68 (6 ports on internal controller and 8 ports on H310). But how to understand DiskIdxMap?? How should i set it?

     

     

×
×
  • Create New...