TinyCore RedPill Loader Build Support Tool ( M-Shell )

[shibby]

On 5/8/2023 at 7:03 PM, maxime said:

I know, but I don't think it's a problem. 

 

i should be on DS923+ you will not have iGPU drivers ex. for Plex HW Transcodding. IMO for intel`s CPU (haswell or newer) the best choice is DS920+.

[cbook2334]

Thanks for answer.

File is now attached, hopefully you can read.

I am just wondering why there is a difference between the installation from end of April vs. the updated version.

[Peter Suh]

2 hours ago, cbook2334 said:

Thanks for answer.

File is now attached, hopefully you can read.

I am just wondering why there is a difference between the installation from end of April vs. the updated version.

 

 

To record custom.gz on the 1st partition, I improved and distributed it a while ago so that there is no shortage of capacity.

Try rebuilding the DVA1622 7.2 RC now.

Edited May 10, 2023 by Peter Suh

[cbook2334]

DVA1622 DMS 7.2 is running. Surveillance Station shows 0 licenses, but I think I read in the forum it is necessary to install an older version of the software.

Final questions (hopefully):

Should 7.1.1. work also now?

I read on the screen, start with no efi: is it better to use the mbr trcp-m-shell instead of the uefi?

Only two hdd-slots are available, although 4 sata-ports (918+ see all 4 ports); due to the fact, that DVA has only two slots?

 

Thanks a lot for your help, your installation tool is perfect for non-linux-users!

 

Kind regards

[Loredan]

27 минут назад, cbook2334 сказал:

DVA1622 DMS 7.2 is running. Surveillance Station shows 0 licenses

Check that the serial number is: 2260UBR######

[apriliars3]

Check that the serial number is: 2260UBR######

Why serial gen give 2260JBRxxyyzz for DVA3622 and not give new serial 2260UBRxxyyzz for DVA1622?

[Loredan]

4 минуты назад, apriliars3 сказал:

Why serial gen give 2260JBRxxyyzz for DVA3622 and not give new serial 2260UBRxxyyzz for DVA1622?

I do not know, this is a question for the authors of the bootloaders.

[cbook2334]

22 hours ago, Loredan said:

Check that the serial number is: 2260UBR######

Perfect, was the solution: Serial was 20C0SJR..., changed to UBR, 8 licenses with newest version of Surveillance Station. 

 

Maybe have a solution for this too? 

Only two hdd-slots are available, although 4 sata-ports (918+ see all 4 ports); due to the fact, that DVA has only two slots?

 

Thanks

[IG-88]

On 5/10/2023 at 3:18 AM, Peter Suh said:

bnx2x 10G nic requires firmware only on Apollo Lake/Gemini Lake platforms.

In other platforms, the module operates normally without firmware.

that one might be about if synology provides a "native" driver or not and what driver you provide instead in the loader for system not having it as native driver

like 3617 as example it comes ootb with bnx2x.ko ~1.7MB (that includes firmware and is made from external source - can bee seen when checking the version of that driver) if you compile a driver from the kernel (vanilla or syno's) it will usually be the way kernel.org dev's like it and thats firmware apart from the driver in a separate location, also fine that way as you will see a clean error message if that firmware file is not present (in contrary to my tn40xx.ko example below)

a bnx2x.ko driver without firmware might be ~900kB

synology does not provide the driver they use in there own kernel source repository's (like 7.0 if anyone wants to check) but if we would use exactly that driver version with the right compile switches it would be the same result for apollo-/geminilake

 

i used tehuti drivers from external source (tn40xx) and they came with just as skeleton and some unused calls in a *.h file for firmware and you would need to collect the firmware from different oem's to "complete" the drivers and have all the firmware inside the tn40xx.ko to make it work with all possible cards (mostly about different phy's as the "core" cpu is the same for all)

 

btw there can also be pitfalls for bnx2x "native" driver as if synology only includes firmware for cards they sell (officially supported), if that would be the case some people might have problems if they have a card that needs the not included firmware, i've seen that kind of problem with my own tn40xx.ko driver in the extra.lzma for 6.2.x - as far as i know it is not that case for syno's bnx2x driver, can't remember cases with 7.x that looked strange

bottom line is that if you trust syno's "native" drivers there can be cases where the driver matches but hardware is not usable as of missing components in the driver and the error message will not show anything about firmware

it will be difficult to check a if a binary driver really has all firmware files it should or can contain

 

as dsm itself does not have "modinfo" to check for dependencies (like firmware) it need to be done on the build system, if you check syno's bnx2x.ko there should be no firmware dependencies and if you check the one you made for apollo-/geminilake you should see something about firmware dependencies with modinfo

 

 

[lord_kimbou]

Hi! Yesterday and today I'm traying M-shell to migrate my two ARPL Vm from proxmox.. (ds3622)

Well.. With my principal vm, in Eudev I lost Hba card passthrough, and a scsi one disk "bypass" on this way (VirtIO SCSI or VirtIO SCSI single controller..):

Ej:

qm set 100 -scsi10 /dev/disk/by-id/ata-WDC_WD23FYYS-0W0B0_WD-WMAY015

 

With DDSML, Hba Card it's working (HBA 9500-16i), but I lose scsi disk "bypass"..

I don't know why, but It's like scsi bypass don't like, drivers Maybe???

Well... I return for now to ARPL.. But it's going in the good way! good job!!  

Edited May 14, 2023 by lord_kimbou

[shibby]

23 hours ago, lord_kimbou said:

but I lose scsi disk "bypass"..

 

WD23FYYS is a SATA drive so attach disk as -sata1 not -scsi10. For example my current configuration (3x SSD attached to VM)

 

sata0 is TCRP with M-Shell so SSD`d are attached as next one.

Edited May 15, 2023 by shibby

[lord_kimbou]

Mmmmmm...... You are right, it's a partial solution.. I don't remember very well why don't use this configuration.. Maybe the maximum sata's with this way only can be 8 hard drives?? And scsi don't have this limitation??

Well... I'm considering! Thanks!

[lord_kimbou]

AhhH!! @Peter Suh Sorryyyy I forget!! When change Keymap to qwerty "es" (spanish) when app reboot you lose all text menu, only can see rapid letters from menu!! And don't see anything from manual syno config!!

[Peter Suh]

[NOTICE]

 

The functionality of cgetty has been further developed.

Depending on the situation, if key-in is impossible, you cannot log in as root.

 

So I added more processing like below.

 

cat /var/log/linuxrc.syno.log > /dev/tty1

 

Even if keying is not possible, the log you see now is the last part of the result of the above command.

 

Capture the above contents to a developer capable of log analysis and request an error analysis.

 

The loader needs to be rebuilt for the Getty Console to look like the one below.

 

 

[Peter Suh]

[NOTICE]

 

Supports M Shell for TCRP , DSM 7.2-64561 official version.

 

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

 

If you enter the TCRP Loader Build menu, automatic updates will proceed as before.

 

The menu has 7.2-64561 instead of 7.2-64551 RC.

 

If today's update history appears during automatic update, it is a good change.

 

# Update : Add Support DSM 7.2-64561 Official Version
# 2023.05.23

 

 

Edited May 23, 2023 by Peter Suh

[Peter Suh]

(Warning) There is a problem with the mpt3sas driver (module). (ARPL, TCRP are the same)

 

Users who use the SAS controller Dell Perc H200, H310, etc. that use the module should not upgrade until the stabilization module is released.

 

I think pocopico should fix it again.

 

Tested on DS3622xs+ (Broadwellnk).

 

https://github.com/pocopico/redpill-modules/blob/master/broadwellnk-4.4.302/mpt3sas.ko

 

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

[Peter Suh]

My DS3622xs+ for backup, which I tried migrating from DSM 7.1.1-42962 to 7.2-64561, uses 3TB x 6 RAID6.
This is the 2nd XHenology in my bottom profile.
I am using a Dell Perc H310 and the error message below occurred in the mpt3sas.ko module and there was a file corruption message during DSM installation.

However, the DELL T1700 under the same conditions installed as a test
The migration from DSM 7.1.1-42962 to 7.2-64561 has just been processed successfully.

It may be a situation unrelated to mp3sas.ko.
In the module itself below, "Exec format error" occurs, but the actual module seems to have nothing to do with the operation.

If you need to use the mp3sas module once, it would be better to proceed after a little more stabilization review.

 

[linuxrc.syno.log]

modprobe: ERROR: could not insert 'mpt3sas': Exec format error
Found SAS Controller : pciid 1000d00000070  Required Extension : Searching for matching extension for mpt3sas

[messages]

May 23 13:43:13  kernel: [   12.141722] mpt3sas version 41.00.00.00 loaded
May 23 13:43:13  kernel: [   12.146377] mpt3sas 0000:06:00.0: can't disable ASPM; OS doesn't have ASPM control
May 23 13:43:13  kernel: [   12.154262] mpt2sas_cm0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (32877396 kB)
May 23 13:43:13  kernel: [   12.234637] mpt2sas_cm0: IOC Number : 0
May 23 13:43:13  kernel: [   12.238500] mpt2sas_cm0: CurrentHostPageSize is 0: Setting default host page size to 4k
May 23 13:43:13  kernel: [   12.246677] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 29
May 23 13:43:13  kernel: [   12.251761] mpt2sas_cm0: iomem(0x00000000f71c0000), mapped(0xffffc90000270000), size(16384)
May 23 13:43:13  kernel: [   12.260162] mpt2sas_cm0: ioport(0x000000000000c000), size(256)
May 23 13:43:13  kernel: [   12.337632] mpt2sas_cm0: IOC Number : 0
May 23 13:43:13  kernel: [   12.341492] mpt2sas_cm0: CurrentHostPageSize is 0: Setting default host page size to 4k
May 23 13:43:13  kernel: [   12.385631] mpt2sas_cm0: scatter gather: sge_in_main_msg(1), sge_per_chain(9), sge_per_io(128), chains_per_io(15)
May 23 13:43:13  kernel: [   12.396089] mpt2sas_cm0: request pool(0xffff8807eed80000) - dma(0x7eed80000): depth(3492), frame_size(128), pool_size(436 kB)
May 23 13:43:13  kernel: [   12.435892] mpt2sas_cm0: sense pool(0xffff8807eee00000) - dma(0x7eee00000): depth(3367), element_size(96), pool_size (315 kB)
May 23 13:43:13  kernel: [   12.447339] mpt2sas_cm0: reply pool(0xffff8807eee80000) - dma(0x7eee80000): depth(3556)frame_size(128), pool_size(444 kB)
May 23 13:43:13  kernel: [   12.458389] mpt2sas_cm0: config page(0xffff88081a397000) - dma(0x81a397000): size(512)
May 23 13:43:13  kernel: [   12.466352] mpt2sas_cm0: Allocated physical memory: size(7579 kB)
May 23 13:43:13  kernel: [   12.472483] mpt2sas_cm0: Current Controller Queue Depth(3364), Max Controller Queue Depth(3432)
May 23 13:43:13  kernel: [   12.540195] mpt2sas_cm0: LSISAS2004: FWVersion(20.00.07.00), ChipRevision(0x03)
May 23 13:43:13  kernel: [   12.547549] mpt2sas_cm0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ)
May 23 13:43:13  kernel: [   12.559581] mpt3sas 0000:06:00.0: Enabled Extended Tags as Controller Supports
May 23 13:43:13  kernel: [   12.566919] scsi host1: Fusion MPT SAS Host
May 23 13:43:13  kernel: [   12.571697] mpt2sas_cm0: sending port enable !!
May 23 13:43:13  kernel: [   12.577081] mpt2sas_cm0: hba_port entry: ffff8807f27efb40, port: 255 is added to hba_port list
May 23 13:43:13  kernel: [   12.588638] mpt2sas_cm0: host_add: handle(0x0001), sas_addr(0x500062b0002a5e9c), phys(8)
May 23 13:43:13  kernel: [   12.597822] mpt2sas_cm0: handle(0x9) sas_address(0x4433221102000000) port_type(0x1)
May 23 13:43:13  kernel: [   12.605835] mpt2sas_cm0: handle(0xa) sas_address(0x4433221103000000) port_type(0x1)
May 23 13:43:13  kernel: [   12.619625] mpt2sas_cm0: port enable: SUCCESS
May 23 13:43:13  kernel: [   12.627484] scsi 1:0:0:0: Direct-Access     TOSHIBA  DT01ABA100V              A8A0 PQ: 0 ANSI: 6
May 23 13:43:13  kernel: [   12.636874] scsi 1:0:0:0: SATA: handle(0x000a), sas_addr(0x4433221103000000), phy(3), device_name(0x5000039fdef391ca)
May 23 13:43:13  kernel: [   12.647545] scsi 1:0:0:0: enclosure logical id(0x500062b0002a5e9c), slot(0) 
May 23 13:43:13  kernel: [   12.654760] scsi 1:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
May 23 13:43:13  kernel: [   12.663779] scsi 1:0:0:0: serial_number(           306NEU7MS)
May 23 13:43:13  kernel: [   12.669566] scsi 1:0:0:0: qdepth(32), tagged(1), scsi_level(7), cmd_que(1)
May 23 13:43:13  kernel: [   12.678428]  end_device-1:0: mpt3sas_transport_port_add: added: handle(0x000a), sas_addr(0x4433221103000000)
May 23 13:43:13  kernel: [   12.678974] sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
May 23 13:43:13  kernel: [   12.678979] sd 1:0:0:0: [sdb] 4096-byte physical blocks
May 23 13:43:13  kernel: [   12.705595] scsi 1:0:1:0: Direct-Access     WDC      WD6400AAKS-00A7B0        3B01 PQ: 0 ANSI: 6
May 23 13:43:13  kernel: [   12.715176] scsi 1:0:1:0: SATA: handle(0x0009), sas_addr(0x4433221102000000), phy(2), device_name(0x50014ee1013c8ee4)
May 23 13:43:13  kernel: [   12.725849] scsi 1:0:1:0: enclosure logical id(0x500062b0002a5e9c), slot(1) 
May 23 13:43:13  kernel: [   12.733065] scsi 1:0:1:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
May 23 13:43:13  kernel: [   12.742270] scsi 1:0:1:0: serial_number(     WD-WCASY2130464)
May 23 13:43:13  kernel: [   12.748056] scsi 1:0:1:0: qdepth(32), tagged(1), scsi_level(7), cmd_que(1)
May 23 13:43:13  kernel: [   12.758325]  end_device-1:1: mpt3sas_transport_port_add: added: handle(0x0009), sas_addr(0x4433221102000000)
May 23 13:43:13  kernel: [   12.759061] sd 1:0:1:0: [sdc] 1250261615 512-byte logical blocks: (640 GB/596 GiB)
May 23 13:43:13  kernel: [   12.767536] sd 1:0:1:0: [sdc] Write Protect is off
May 23 13:43:13  kernel: [   12.767542] sd 1:0:1:0: [sdc] Mode Sense: 7f 00 10 08
May 23 13:43:13  kernel: [   12.769990] sd 1:0:1:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
May 23 13:43:13  kernel: [   12.800300]  sdc: sdc1 sdc2 sdc3
May 23 13:43:13  kernel: [   12.816535] sd 1:0:1:0: [sdc] Attached SCSI disk
May 23 13:43:13  kernel: [   12.928873] sd 1:0:0:0: [sdb] Write Protect is off
May 23 13:43:13  kernel: [   12.933710] sd 1:0:0:0: [sdb] Mode Sense: 7f 00 10 08
May 23 13:43:13  kernel: [   12.939893] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
May 23 13:43:13  kernel: [   13.207650]  sdb: sdb1 sdb2 sdb3
May 23 13:43:13  kernel: [   13.478296] sd 1:0:0:0: [sdb] Attached SCSI disk

 

[lord_kimbou]

4 hours ago, Peter Suh said:

[NOTICE]

 

Supports M Shell for TCRP , DSM 7.2-64561 official version.

 

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

 

If you enter the TCRP Loader Build menu, automatic updates will proceed as before.

 

The menu has 7.2-64561 instead of 7.2-64551 RC.

 

If today's update history appears during automatic update, it is a good change.

 

# Update : Add Support DSM 7.2-64561 Official Version
# 2023.05.23

 

 

Well.. I migrate one of my vm.. 7.2 It's working! But I'm not seeing any difference with 7.1 only "docker" it's now container manager.. I don't consider a great upgrade at first look..

Edited May 23, 2023 by lord_kimbou

[Peter Suh]

38 minutes ago, Peter Suh said:

My DS3622xs+ for backup, which I tried migrating from DSM 7.1.1-42962 to 7.2-64561, uses 3TB x 6 RAID6.
This is the 2nd XHenology in my bottom profile.
I am using a Dell Perc H310 and the error message below occurred in the mpt3sas.ko module and there was a file corruption message during DSM installation.

However, the DELL T1700 under the same conditions installed as a test
The migration from DSM 7.1.1-42962 to 7.2-64561 has just been processed successfully.

It may be a situation unrelated to mp3sas.ko.
In the module itself below, "Exec format error" occurs, but the actual module seems to have nothing to do with the operation.

If you need to use the mp3sas module once, it would be better to proceed after a little more stabilization review.

 

[linuxrc.syno.log]

modprobe: ERROR: could not insert 'mpt3sas': Exec format error
Found SAS Controller : pciid 1000d00000070  Required Extension : Searching for matching extension for mpt3sas

[messages]

May 23 13:43:13  kernel: [   12.141722] mpt3sas version 41.00.00.00 loaded
May 23 13:43:13  kernel: [   12.146377] mpt3sas 0000:06:00.0: can't disable ASPM; OS doesn't have ASPM control
May 23 13:43:13  kernel: [   12.154262] mpt2sas_cm0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (32877396 kB)
May 23 13:43:13  kernel: [   12.234637] mpt2sas_cm0: IOC Number : 0
May 23 13:43:13  kernel: [   12.238500] mpt2sas_cm0: CurrentHostPageSize is 0: Setting default host page size to 4k
May 23 13:43:13  kernel: [   12.246677] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 29
May 23 13:43:13  kernel: [   12.251761] mpt2sas_cm0: iomem(0x00000000f71c0000), mapped(0xffffc90000270000), size(16384)
May 23 13:43:13  kernel: [   12.260162] mpt2sas_cm0: ioport(0x000000000000c000), size(256)
May 23 13:43:13  kernel: [   12.337632] mpt2sas_cm0: IOC Number : 0
May 23 13:43:13  kernel: [   12.341492] mpt2sas_cm0: CurrentHostPageSize is 0: Setting default host page size to 4k
May 23 13:43:13  kernel: [   12.385631] mpt2sas_cm0: scatter gather: sge_in_main_msg(1), sge_per_chain(9), sge_per_io(128), chains_per_io(15)
May 23 13:43:13  kernel: [   12.396089] mpt2sas_cm0: request pool(0xffff8807eed80000) - dma(0x7eed80000): depth(3492), frame_size(128), pool_size(436 kB)
May 23 13:43:13  kernel: [   12.435892] mpt2sas_cm0: sense pool(0xffff8807eee00000) - dma(0x7eee00000): depth(3367), element_size(96), pool_size (315 kB)
May 23 13:43:13  kernel: [   12.447339] mpt2sas_cm0: reply pool(0xffff8807eee80000) - dma(0x7eee80000): depth(3556)frame_size(128), pool_size(444 kB)
May 23 13:43:13  kernel: [   12.458389] mpt2sas_cm0: config page(0xffff88081a397000) - dma(0x81a397000): size(512)
May 23 13:43:13  kernel: [   12.466352] mpt2sas_cm0: Allocated physical memory: size(7579 kB)
May 23 13:43:13  kernel: [   12.472483] mpt2sas_cm0: Current Controller Queue Depth(3364), Max Controller Queue Depth(3432)
May 23 13:43:13  kernel: [   12.540195] mpt2sas_cm0: LSISAS2004: FWVersion(20.00.07.00), ChipRevision(0x03)
May 23 13:43:13  kernel: [   12.547549] mpt2sas_cm0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ)
May 23 13:43:13  kernel: [   12.559581] mpt3sas 0000:06:00.0: Enabled Extended Tags as Controller Supports
May 23 13:43:13  kernel: [   12.566919] scsi host1: Fusion MPT SAS Host
May 23 13:43:13  kernel: [   12.571697] mpt2sas_cm0: sending port enable !!
May 23 13:43:13  kernel: [   12.577081] mpt2sas_cm0: hba_port entry: ffff8807f27efb40, port: 255 is added to hba_port list
May 23 13:43:13  kernel: [   12.588638] mpt2sas_cm0: host_add: handle(0x0001), sas_addr(0x500062b0002a5e9c), phys(8)
May 23 13:43:13  kernel: [   12.597822] mpt2sas_cm0: handle(0x9) sas_address(0x4433221102000000) port_type(0x1)
May 23 13:43:13  kernel: [   12.605835] mpt2sas_cm0: handle(0xa) sas_address(0x4433221103000000) port_type(0x1)
May 23 13:43:13  kernel: [   12.619625] mpt2sas_cm0: port enable: SUCCESS
May 23 13:43:13  kernel: [   12.627484] scsi 1:0:0:0: Direct-Access     TOSHIBA  DT01ABA100V              A8A0 PQ: 0 ANSI: 6
May 23 13:43:13  kernel: [   12.636874] scsi 1:0:0:0: SATA: handle(0x000a), sas_addr(0x4433221103000000), phy(3), device_name(0x5000039fdef391ca)
May 23 13:43:13  kernel: [   12.647545] scsi 1:0:0:0: enclosure logical id(0x500062b0002a5e9c), slot(0) 
May 23 13:43:13  kernel: [   12.654760] scsi 1:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
May 23 13:43:13  kernel: [   12.663779] scsi 1:0:0:0: serial_number(           306NEU7MS)
May 23 13:43:13  kernel: [   12.669566] scsi 1:0:0:0: qdepth(32), tagged(1), scsi_level(7), cmd_que(1)
May 23 13:43:13  kernel: [   12.678428]  end_device-1:0: mpt3sas_transport_port_add: added: handle(0x000a), sas_addr(0x4433221103000000)
May 23 13:43:13  kernel: [   12.678974] sd 1:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
May 23 13:43:13  kernel: [   12.678979] sd 1:0:0:0: [sdb] 4096-byte physical blocks
May 23 13:43:13  kernel: [   12.705595] scsi 1:0:1:0: Direct-Access     WDC      WD6400AAKS-00A7B0        3B01 PQ: 0 ANSI: 6
May 23 13:43:13  kernel: [   12.715176] scsi 1:0:1:0: SATA: handle(0x0009), sas_addr(0x4433221102000000), phy(2), device_name(0x50014ee1013c8ee4)
May 23 13:43:13  kernel: [   12.725849] scsi 1:0:1:0: enclosure logical id(0x500062b0002a5e9c), slot(1) 
May 23 13:43:13  kernel: [   12.733065] scsi 1:0:1:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
May 23 13:43:13  kernel: [   12.742270] scsi 1:0:1:0: serial_number(     WD-WCASY2130464)
May 23 13:43:13  kernel: [   12.748056] scsi 1:0:1:0: qdepth(32), tagged(1), scsi_level(7), cmd_que(1)
May 23 13:43:13  kernel: [   12.758325]  end_device-1:1: mpt3sas_transport_port_add: added: handle(0x0009), sas_addr(0x4433221102000000)
May 23 13:43:13  kernel: [   12.759061] sd 1:0:1:0: [sdc] 1250261615 512-byte logical blocks: (640 GB/596 GiB)
May 23 13:43:13  kernel: [   12.767536] sd 1:0:1:0: [sdc] Write Protect is off
May 23 13:43:13  kernel: [   12.767542] sd 1:0:1:0: [sdc] Mode Sense: 7f 00 10 08
May 23 13:43:13  kernel: [   12.769990] sd 1:0:1:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
May 23 13:43:13  kernel: [   12.800300]  sdc: sdc1 sdc2 sdc3
May 23 13:43:13  kernel: [   12.816535] sd 1:0:1:0: [sdc] Attached SCSI disk
May 23 13:43:13  kernel: [   12.928873] sd 1:0:0:0: [sdb] Write Protect is off
May 23 13:43:13  kernel: [   12.933710] sd 1:0:0:0: [sdb] Mode Sense: 7f 00 10 08
May 23 13:43:13  kernel: [   12.939893] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
May 23 13:43:13  kernel: [   13.207650]  sdb: sdb1 sdb2 sdb3
May 23 13:43:13  kernel: [   13.478296] sd 1:0:0:0: [sdb] Attached SCSI disk

 

 

There is nothing wrong with the mpt3sas module itself, and I was using Synol incorrectly.

https://kb.synology.com/en-us/DSM/tutorial/DSM_update_insufficient_system_capacity_for_update
-------------------------------------------------- ---------------------------------------------
Insufficient system capacity for update. What can I do?

 

Resolution

You are seeing this error because your system does not have sufficient capacity to unzip and install update files in the system partition. Please check the following list before attempting to update DSM or the firmware of your Synology drives again.

 

Store your data in the shared folders only

The output from terminal commands (e.g., creating files or folders within the system partition such as in /root or /opt, or executing your own binary files/scripts) may fill up the system partition and result in update failure. Please move such data to the shared folders and only store your data and command output inside them.

-------------------------------------------------- ---------------------------------------------

During DSM installation, I received a message that the system partition is running out of space.

The /root directory should always be left empty.

The GeekBench installation pack and folder remain the same as the last CPU performance test,
I don't know why the Synology backups are piling up here, but the backups were also taking up quite a bit of space.

I checked with du -h /root , cleaned up space and installed DSM 7.2-64561 successfully.

Rather than doing this and that by myself, it ended with a happening.

Edited May 23, 2023 by Peter Suh

[apriliars3]

3 hours ago, lord_kimbou said:

Well.. I migrate one of my vm.. 7.2 It's working! But I'm not seeing any difference with 7.1 only "docker" it's now container manager.. I don't consider a great upgrade at first look..

 

 

What’s New DSM 7.2

• Added support for WriteOnce shared folders. This feature is based on the Write Once, Read Many (WORM) technology and can be enabled to prevent files from being modified, deleted, or renamed for a specified period.
• Added support for volume encryption. All volume encryption keys are stored in the Encryption Key Vault, which can be set up on a local Synology NAS or via KMIP on a remote Synology NAS.
• Added more Synology NAS models to support M.2 NVMe SSD storage pools. (Additional info added for the new DSM 7.2-64216 Beta – this is the main difference between DSM 7.2-64216 Beta and DSM 7.2-64213 Beta).
• Added more SSD cache group management options, including changing the RAID type and replacing a drive.
• Added support for inline zero-block removal to increase the efficiency of data deduplication.
• Adjusted how drive information is presented in Storage Manager. Users can now quickly check the condition of their drives by looking at the “Drive Status” field.
• Users can now view the amount of used and free space for each storage pool and volume in Storage Manager.
• Added a warning notification for when the available shared folder quota is low.
• Supports deleting individual desktop notifications.
• Supports sending DSM notifications via additional webhook providers, including LINE and Microsoft Teams.
• Supports creating custom notification rules for system events, giving users greater control over what notifications to receive.
• Supports exporting a list of users and of groups.
• Added support for SAML to integrate DSM with external SSO servers.
• Added the option to allow non-admin users to safely eject USB devices.
• Users can now manually input the IP addresses or FQDNs of one or more domain controllers in the trusted domain. This allows Synology NAS to sync domain data directly with the specified domain controllers.
• Users can now enable Synology’s email server to send DSM notifications directly to their Synology Account.

[Orphée]

A part from new features, you should look at how many vulnerabilities have been fixed !

[Peter Suh]

[notification]

 

A new TCRP ADDON has been added.

 

https://github.com/PeterSuh-Q3/tcrp-addons/tree/main/reboottotcrp

 

When DSM is booted, it automatically registers a manual scheduler that modifies the default value of grub.cfg to enter "Tiny Core Image Build" on the next boot.

 

If this Addon is installed successfully,
As shown in the screenshot below, one scheduler will be automatically registered. (The loader must be newly built.)

 

Scripts in this scheduler only work if run manually.

 

The boot order of grub.cfg is fixed to "Tiny Core Image Build" at the end. (Jot with 4 menus is also supported.)

 

 

 

[maxime]

I'm sorry, where can I found a guide for TCRP ADDONS installation?

21 minutes ago, Peter Suh said:

[notification]

 

A new TCRP ADDON has been added.

 

https://github.com/PeterSuh-Q3/tcrp-addons/tree/main/reboottotcrp

 

 

 

 

[Peter Suh]

9 minutes ago, maxime said:

I'm sorry, where can I found a guide for TCRP ADDONS installation?

 

 

If you only rebuild the loader, it will be automatically mounted in the new loader.
The ability to add to an already installed DSM has not been developed yet.

[maxime]

OPSSS! This is the reason I couldn't find it! 😅
Thanks Peter!