TinyCore RedPill Loader Build Support Tool ( M-Shell )

[Peter Suh]

There is a phenomenon in which the san manager repair service runs too early and ends without being able to work properly.

 

There was a delay of about 3 minutes.

 

It seems that SAN MANAGER loading will be normal only after all other packages are loaded and uploaded.

 

You may need to wait for about 3 minutes after logging in for recovery, so please wait long enough.

[Peter Suh]

12 hours ago, Peter Suh said:

There is a phenomenon in which the san manager repair service runs too early and ends without being able to work properly.

 

There was a delay of about 3 minutes.

 

It seems that SAN MANAGER loading will be normal only after all other packages are loaded and uploaded.

 

You may need to wait for about 3 minutes after logging in for recovery, so please wait long enough.

 

Below, the delay for restarting the SAN MANAGER (ScsiTarget) was adjusted from 3 minutes to 1 minute.

 

synopkg start ScsiTarget

 

The error icon appears briefly within a minute, and appears to appear roughly at the same time as other packages are loading.

[shibby]

@Peter Suh do you have an idea why was this issue appear and which commit broke it?

[Peter Suh]

7 hours ago, shibby said:

@Peter Suh do you have an idea why was this issue appear and which commit broke it?

 

I have found this in two cases so far.

1. When MAC spoofing is processed while DSM has completed booting

2. When the system partition is damaged due to the sudden loss of one of the RAID disks in SA6400 (this is a case that often happens, but was a bit unexpected).

[Tibag]

On 1/15/2024 at 4:49 PM, Tibag said:

Looks like the above is a red herring - I fixed it anyway. 

 

I am trying to understand why storage manager doesn't look happy:

 

Does that "Invalid serial number" ring a bell? 

 

 

Hi all,

 

I haven't managed to progress much with the above. My Storage Manager package still refuses to load. Any suggestions on how to fix it?

[Peter Suh]

45 minutes ago, Tibag said:

 

Hi all,

 

I haven't managed to progress much with the above. My Storage Manager package still refuses to load. Any suggestions on how to fix it?

 

We mentioned the addition of an improved addon on the previous page.

https://xpenology.com/forum/topic/61839-tinycore-redpill-loader-build-support-tool-m-shell/?do=findComment&comment=455313

To use this new addon you will need to rebuild your loader.

[Tibag]

4 hours ago, Peter Suh said:

 

We mentioned the addition of an improved addon on the previous page.

https://xpenology.com/forum/topic/61839-tinycore-redpill-loader-build-support-tool-m-shell/?do=findComment&comment=455313

To use this new addon you will need to rebuild your loader.

 

I tried it and it definitely fixed the SAN Manager package. Thanks!

 

Nevertheless, my Storage Manager still doesn't start. 

[ansh]

Hi

Why do disks start with DISK 2?

DELL PowerEdge R530 - Intel(R) Xeon(R)CPUE5-2623 v4 2.60GH, RAM 32Gb ECC DDR4 2133Mhz, HDD SAS 5.4TB x 8pices (), Integrated RAID Dell PERC H730P mini RAID5 38.2TB

Sata controller disabled BIOS.

CPU. MEM:

Intel(R) Xeon(R) CPU E5-2623 u4 2.60GHz (8 Thread(s)1, 31.3G Memory

DMI: Dell Inc. PowerEdge R530 0CH?X8, BIOS 2.5.4 08.17/2017 SAS RAID HBAs Count : 1 , NICs Count

Systen is running in Legacy b boot mode

Setting MAC Address from D0:94:66:10:EB:30 to D0:94:66:10:EB:30 on eth0 (tg3) Setting MAC Address from D0:91:66:10:EB:31 to D0:94:66:10::EB:31 on eth1 (tg3)

Setting MAC Address from D0:94:66:10:EB:32 to D0:94:66:10:EB:32 on eth2 (tg3) Setting MAC Address from D0:34:66:10:EB:33 to D0:94:66:10:EB:33 on eth3 (tg3) IP Address :192.168.40.55, Network Interface Card : eth0 (14e4:165f1 (tg3) IP Address : Network Interface Card : eth1 L11e4:165f1 (tg3) IP Address : , Network Interface Card : eth2 [14e4:165f] (tg3) IP Address : Network Interface C Card : eth3 (14e4:165f1 (tg3) Detecting upgrade : Ramdisk OK ? zlmage OK ? Detecting Internet -> OX!

Checking for latest friend -> ox, latest

zimage : /mnt tcrp/zImagedum initrd : /mnt/tcrp/initrd-dsm, Module Processing Method : DDSML cndline : withefi earlyprintk syno_hw_version=D33622xs+ consoie=ttyS0,115200n8 nctif_num=1 pid=0xc95a carlycon=uart8250,io,0x3f8 ,115200n8 syno_part_thaw 1 SasIdxMap mac2=XXXXXXXXX mac3=XXXXXXXXXX mac1=XXXXXXXX mac1=XXXXXXXXX sn=XXXXXXXXX vi d-0x125f clevator=clevator logleve1=15 HddHotplug=0 DiskIdxMap=00 syno_hdd_detect-0 vender_format_version=2 syno_hdd_powerup_seq =0 log_buf_len=32M root=/dev/md0 SataPortMap=1 skip_vender_mac_interfaces=0,1,2,3,4,5,6,7 panic=5

 

:/$ lspci -tvnnq
-+-[0001:0c]---00.0  Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller [1b4b:9235]
 +-[0001:09]---00.0  Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller [1b4b:9235]
 +-[0000:ff]-+-0b.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 [8086:6f81]
 |           +-0b.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 [8086:6f36]
 |           +-0b.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link 0/1 [8086:6f37]
 |           +-0b.3  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R3 QPI Link Debug [8086:6f76]
 |           +-0c.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe0]
 |           +-0c.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe1]
 |           +-0c.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe2]
 |           +-0c.3  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6fe3]
 |           +-0f.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6ff8]
 |           +-0f.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6ff9]
 |           +-0f.4  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6ffc]
 |           +-0f.5  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6ffd]
 |           +-0f.6  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Caching Agent [8086:6ffe]
 |           +-10.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R2PCIe Agent [8086:6f1d]
 |           +-10.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D R2PCIe Agent [8086:6f34]
 |           +-10.5  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox [8086:6f1e]
 |           +-10.6  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox [8086:6f7d]
 |           +-10.7  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Ubox [8086:6f1f]
 |           +-12.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Home Agent 0 [8086:6fa0]
 |           +-12.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Home Agent 0 [8086:6f30]
 |           +-12.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Home Agent 0 Debug [8086:6f70]
 |           +-13.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Target Address/Thermal/RAS [8086:6fa8]
 |           +-13.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Target Address/Thermal/RAS [8086:6f71]
 |           +-13.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder [8086:6faa]
 |           +-13.3  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder [8086:6fab]
 |           +-13.4  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder [8086:6fac]
 |           +-13.5  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel Target Address Decoder [8086:6fad]
 |           +-13.6  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Broadcast [8086:6fae]
 |           +-13.7  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Global Broadcast [8086:6faf]
 |           +-14.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 0 Thermal Control [8086:6fb0]
 |           +-14.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 1 Thermal Control [8086:6fb1]
 |           +-14.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 0 Error [8086:6fb2]
 |           +-14.3  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 1 Error [8086:6fb3]
 |           +-14.4  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface [8086:6fbc]
 |           +-14.5  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface [8086:6fbd]
 |           +-14.6  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface [8086:6fbe]
 |           +-14.7  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 0/1 Interface [8086:6fbf]
 |           +-15.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 2 Thermal Control [8086:6fb4]
 |           +-15.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 3 Thermal Control [8086:6fb5]
 |           +-15.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 2 Error [8086:6fb6]
 |           +-15.3  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 0 - Channel 3 Error [8086:6fb7]
 |           +-16.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Target Address/Thermal/RAS [8086:6f68]
 |           +-16.6  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Broadcast [8086:6f6e]
 |           +-16.7  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Global Broadcast [8086:6f6f]
 |           +-17.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Memory Controller 1 - Channel 0 Thermal Control [8086:6fd0]
 |           +-17.4  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface [8086:6fb8]
 |           +-17.5  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface [8086:6fb9]
 |           +-17.6  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface [8086:6fba]
 |           +-17.7  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DDRIO Channel 2/3 Interface [8086:6fbb]
 |           +-1e.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit [8086:6f98]
 |           +-1e.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit [8086:6f99]
 |           +-1e.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit [8086:6f9a]
 |           +-1e.3  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit [8086:6fc0]
 |           +-1e.4  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit [8086:6f9c]
 |           +-1f.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit [8086:6f88]
 |           \-1f.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Power Control Unit [8086:6f8a]
 \-[0000:00]-+-00.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D DMI2 [8086:6f00]
             +-01.0-[01]----00.0  Broadcom / LSI MegaRAID SAS-3 3108 [Invader] [1000:005d]
             +-02.0-[04]--
             +-02.2-[05]--
             +-03.0-[06]--
             +-05.0  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D Map/VTd_Misc/System Management [8086:6f28]
             +-05.1  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO Hot Plug [8086:6f29]
             +-05.2  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D IIO RAS/Control Status/Global Errors [8086:6f2a]
             +-05.4  Intel Corporation Xeon E7 v4/Xeon E5 v4/Xeon E3 v4/Xeon D I/O APIC [8086:6f2c]
             +-11.0  Intel Corporation C610/X99 series chipset SPSR [8086:8d7c]
             +-16.0  Intel Corporation C610/X99 series chipset MEI Controller #1 [8086:8d3a]
             +-16.1  Intel Corporation C610/X99 series chipset MEI Controller #2 [8086:8d3b]
             +-1a.0  Intel Corporation C610/X99 series chipset USB Enhanced Host Controller #2 [8086:8d2d]
             +-1c.0-[07]--
             +-1c.1-[08-0c]----00.0-[09-0c]----00.0-[0a-0b]----00.0-[0b]----00.0  Matrox Electronics Systems Ltd. G200eR2 [102b:0534]
             +-1c.2-[02]--+-00.0  Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe [14e4:165f]
             |            \-00.1  Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe [14e4:165f]
             +-1c.3-[03]--+-00.0  Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe [14e4:165f]
             |            \-00.1  Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe [14e4:165f]
             +-1c.4-[0d]--
             +-1d.0  Intel Corporation C610/X99 series chipset USB Enhanced Host Controller #1 [8086:8d26]
             \-1f.0  Intel Corporation C610/X99 series chipset LPC Controller [8086:8d44]
pcilib: Cannot write to /var/services/homes/adminmiuz/.pciids-cache: No such file or directory

 

:/$ dmesg | grep sd
[   11.767550] sd 0:0:0:0: [synoboot] 7892087 512-byte logical blocks: (4.04 GB/3.76 GiB)
[   11.768419] sd 0:0:0:0: [synoboot] Write Protect is off
[   11.768424] sd 0:0:0:0: [synoboot] Mode Sense: 00 00 00 00
[   11.769322] sd 0:0:0:0: [synoboot] Asking for cache data failed
[   11.769325] sd 0:0:0:0: [synoboot] Assuming drive cache: write through
[   11.952672] sd 0:0:0:0: [synoboot] Attached SCSI removable disk
[   14.353790] sd 1:2:0:0: [sdb] 11719933952 512-byte logical blocks: (6.00 TB/5.46 TiB)
[   14.354419] sd 1:2:1:0: [sdc] 11719933952 512-byte logical blocks: (6.00 TB/5.46 TiB)
[   14.354422] sd 1:2:1:0: [sdc] 4096-byte physical blocks
[   14.354473] sd 1:2:1:0: [sdc] Write Protect is off
[   14.354476] sd 1:2:1:0: [sdc] Mode Sense: 1f 00 00 08
[   14.354510] sd 1:2:1:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[   14.355377]  sdc: sdc1 sdc2
[   14.355812] sd 1:2:2:0: [sdd] 11719933952 512-byte logical blocks: (6.00 TB/5.46 TiB)
[   14.355814] sd 1:2:2:0: [sdd] 4096-byte physical blocks
[   14.355878] sd 1:2:1:0: [sdc] Attached SCSI disk
[   14.355915] sd 1:2:2:0: [sdd] Write Protect is off
[   14.355919] sd 1:2:2:0: [sdd] Mode Sense: 1f 00 00 08
[   14.355954] sd 1:2:2:0: [sdd] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[   14.356639]  sdd: sdd1 sdd2
[   14.357024] sd 1:2:2:0: [sdd] Attached SCSI disk
[   14.357893] sd 1:2:3:0: [sde] 11719933952 512-byte logical blocks: (6.00 TB/5.46 TiB)
[   14.357896] sd 1:2:3:0: [sde] 4096-byte physical blocks
[   14.357956] sd 1:2:3:0: [sde] Write Protect is off
[   14.357959] sd 1:2:3:0: [sde] Mode Sense: 1f 00 00 08
[   14.357994] sd 1:2:3:0: [sde] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[   14.358677]  sde: sde1 sde2
[   14.359065] sd 1:2:3:0: [sde] Attached SCSI disk
[   14.361523] sd 1:2:4:0: [sdf] 11719933952 512-byte logical blocks: (6.00 TB/5.46 TiB)
[   14.361526] sd 1:2:4:0: [sdf] 4096-byte physical blocks
[   14.361587] sd 1:2:4:0: [sdf] Write Protect is off
[   14.361590] sd 1:2:4:0: [sdf] Mode Sense: 1f 00 00 08
[   14.361624] sd 1:2:4:0: [sdf] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[   14.362322]  sdf: sdf1 sdf2
[   14.362711] sd 1:2:4:0: [sdf] Attached SCSI disk
[   14.366053] sd 1:2:5:0: [sdg] 11719933952 512-byte logical blocks: (6.00 TB/5.46 TiB)
[   14.366056] sd 1:2:5:0: [sdg] 4096-byte physical blocks
[   14.366134] sd 1:2:5:0: [sdg] Write Protect is off
[   14.366138] sd 1:2:5:0: [sdg] Mode Sense: 1f 00 00 08
[   14.366172] sd 1:2:5:0: [sdg] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[   14.366932]  sdg: sdg1 sdg2
[   14.367325] sd 1:2:5:0: [sdg] Attached SCSI disk
[   14.374469] sd 1:2:6:0: [sdh] 11719933952 512-byte logical blocks: (6.00 TB/5.46 TiB)
[   14.374472] sd 1:2:6:0: [sdh] 4096-byte physical blocks
[   14.374556] sd 1:2:6:0: [sdh] Write Protect is off
[   14.374560] sd 1:2:6:0: [sdh] Mode Sense: 1f 00 00 08
[   14.374593] sd 1:2:6:0: [sdh] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[   14.375296]  sdh: sdh1 sdh2
[   14.375691] sd 1:2:6:0: [sdh] Attached SCSI disk
[   14.382469] sd 1:2:7:0: [sdi] 11719933952 512-byte logical blocks: (6.00 TB/5.46 TiB)
[   14.382472] sd 1:2:7:0: [sdi] 4096-byte physical blocks
[   14.382546] sd 1:2:7:0: [sdi] Write Protect is off
[   14.382549] sd 1:2:7:0: [sdi] Mode Sense: 1f 00 00 08
[   14.382588] sd 1:2:7:0: [sdi] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[   14.383235]  sdi: sdi1 sdi2
[   14.383642] sd 1:2:7:0: [sdi] Attached SCSI disk
[   15.954331] sd 1:2:0:0: [sdb] 4096-byte physical blocks
[   15.960230] sd 1:2:0:0: [sdb] Write Protect is off
[   15.965584] sd 1:2:0:0: [sdb] Mode Sense: 1f 00 00 08
[   15.971289] sd 1:2:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[   15.983796]  sdb: sdb1 sdb2
[   15.987251] sd 1:2:0:0: [sdb] Attached SCSI disk
[   22.764073] md: bind<sdc1>
[   22.767495] md: bind<sdd1>
[   22.772053] md: bind<sde1>
[   22.776698] md: bind<sdf1>
[   22.781232] md: bind<sdg1>
[   22.785764] md: bind<sdh1>
[   22.790296] md: bind<sdi1>
[   22.793810] md: bind<sdb1>
[   34.588715] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   34.596211] sd 1:2:0:0: Attached scsi generic sg1 type 0
[   34.603659] sd 1:2:1:0: Attached scsi generic sg2 type 0
[   34.611141] sd 1:2:2:0: Attached scsi generic sg3 type 0
[   34.618615] sd 1:2:3:0: Attached scsi generic sg4 type 0
[   34.626091] sd 1:2:4:0: Attached scsi generic sg5 type 0
[   34.633572] sd 1:2:5:0: Attached scsi generic sg6 type 0
[   34.641052] sd 1:2:6:0: Attached scsi generic sg7 type 0
[   34.648536] sd 1:2:7:0: Attached scsi generic sg8 type 0
[   37.007477] md: bind<sdc2>
[   37.011370] md: bind<sdd2>
[   37.014802] md: bind<sde2>
[   37.017959] md: bind<sdf2>
[   37.021123] md: bind<sdg2>
[   37.024294] md: bind<sdh2>
[   37.027458] md: bind<sdi2>
[   37.058846] md: bind<sdb2>

 

 

[ansh]

15 часов назад, ansh сказал:

Hi

Why do disks start with DISK 2?

DELL PowerEdge R530 - Intel(R) Xeon(R)CPUE5-2623 v4 2.60GH, RAM 32Gb ECC DDR4 2133Mhz, HDD SAS 5.4TB x 8pices (), Integrated RAID Dell PERC H730P mini RAID5 38.2TB

Sata controller disabled BIOS.

 

 

In DSM SSH

:/$ ls -lh /sys/block/sd*
lrwxrwxrwx 1 root root 0 Jan 23 18:05 /sys/block/sdb -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/target1:2:0/1:2:0:0/block/sdb
lrwxrwxrwx 1 root root 0 Jan 23 18:05 /sys/block/sdc -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/target1:2:1/1:2:1:0/block/sdc
lrwxrwxrwx 1 root root 0 Jan 23 18:05 /sys/block/sdd -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/target1:2:2/1:2:2:0/block/sdd
lrwxrwxrwx 1 root root 0 Jan 23 18:05 /sys/block/sde -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/target1:2:3/1:2:3:0/block/sde
lrwxrwxrwx 1 root root 0 Jan 23 18:05 /sys/block/sdf -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/target1:2:4/1:2:4:0/block/sdf
lrwxrwxrwx 1 root root 0 Jan 23 18:05 /sys/block/sdg -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/target1:2:5/1:2:5:0/block/sdg
lrwxrwxrwx 1 root root 0 Jan 23 18:05 /sys/block/sdh -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/target1:2:6/1:2:6:0/block/sdh
lrwxrwxrwx 1 root root 0 Jan 23 18:05 /sys/block/sdi -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/target1:2:7/1:2:7:0/block/sdi

 

Edited January 24 by ansh

[Peter Suh]

4 hours ago, ansh said:

 

In DSM SSH

:/$ ls -lh /sys/block/sd*
lrwxrwxrwx 1 root root 0 Jan 23 18:05 /sys/block/sdb -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/target1:2:0/1:2:0:0/block/sdb
lrwxrwxrwx 1 root root 0 Jan 23 18:05 /sys/block/sdc -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/target1:2:1/1:2:1:0/block/sdc
lrwxrwxrwx 1 root root 0 Jan 23 18:05 /sys/block/sdd -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/target1:2:2/1:2:2:0/block/sdd
lrwxrwxrwx 1 root root 0 Jan 23 18:05 /sys/block/sde -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/target1:2:3/1:2:3:0/block/sde
lrwxrwxrwx 1 root root 0 Jan 23 18:05 /sys/block/sdf -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/target1:2:4/1:2:4:0/block/sdf
lrwxrwxrwx 1 root root 0 Jan 23 18:05 /sys/block/sdg -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/target1:2:5/1:2:5:0/block/sdg
lrwxrwxrwx 1 root root 0 Jan 23 18:05 /sys/block/sdh -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/target1:2:6/1:2:6:0/block/sdh
lrwxrwxrwx 1 root root 0 Jan 23 18:05 /sys/block/sdi -> ../devices/pci0000:00/0000:00:01.0/0000:01:00.0/host1/target1:2:7/1:2:7:0/block/sdi

 

 

[HBA Recommended settings from flyride]

 

Not EUDEV , Use Only DDSML (If you use TCRP-mshell )

 

"SataPortMap": "12",

"DiskIdxMap": "1000",

"SasIdxMap: "0"

 

"MaxDisks: "24"

[ansh]

3 часа назад, Peter Suh сказал:

 

[HBA Recommended settings from flyride]

 

Not EUDEV , Use Only DDSML (If you use TCRP-mshell )

 

"SataPortMap": "12",

"DiskIdxMap": "1000",

"SasIdxMap: "0"

 

"MaxDisks: "24"

 

 

Thanks. Reinstalled DSM completely with parameters set to SataPortMap": "12", "DiskIdxMap": "1000", "SasIdxMap: "0", "MaxDisks: "24", but the result is the same.(

 

 

[Orphée]

@ansh if your NAS works just fine, don't bother with disk order, it is useless.

 

In my opinion it should be faked/removed as long as it works... it would avoid this kind of requests.

[use-nas]

New installation

Constant update cycle :((

[ansh]

3 часа назад, use-nas сказал:

New installation

Constant update cycle :((

It was so. After formatting all the drives, we were able to install DSM.

[ansh]

13 часов назад, Orphée сказал:

@ansh if your NAS works just fine, don't bother with disk order, it is useless.

I would like to figure it out... It’s strange why the settings SataPortMap": "12", "DiskIdxMap": "1000", "SasIdxMap: "0" do not work?

[Orphée]

31 minutes ago, ansh said:

I would like to figure it out... It’s strange why the settings SataPortMap": "12", "DiskIdxMap": "1000", "SasIdxMap: "0" do not work?

Lot of guys before you requested same thing with HBA cards.

Using random values will not help.

You have to understand how SataPortMap / DiskIdxMap works, and how it can match your particular setup.

and even with this, there is a high chance you never "figure it out".

 

If it works, just get over it.

Otherwise, just use search function about "HBA" cards... have fun.

Edited January 25 by Orphée

[ansh]

9 минут назад, Orphée сказал:

You have to understand how SataPortMap / DiskIdxMap works

I figured out how SataPortMap / DiskIdxMap works, but when I change these parameters, there are no changes in the DSM interface. The first disk is always empty...(

 

I set the values but no change...(

"SataPortMap": "",

"DiskIdxMap": "0С00",

"SasIdxMap: "0xffffffff"

[Peter Suh]

7 hours ago, use-nas said:

New installation

Constant update cycle :((

 

 

It looks like your user_config.json file has become corrupted for some reason.

The location of the corrupted file is /mnt/tcrp/user_config.json on this Friend boot kernel.

You will probably see files close to size 0.

If you have repeated several loader builds, you may have multiple backups as shown below.

During this backup, you can also restore from the file containing your settings using the cp command.

I think we need to improve one more feature of the Friend kernel.

In case of a corrupted user_config.json like yours, I will modify it to stop booting and guide you.

 

[use-nas]

[Tibag]

On 1/20/2024 at 8:50 PM, Tibag said:

 

I tried it and it definitely fixed the SAN Manager package. Thanks!

 

Nevertheless, my Storage Manager still doesn't start. 

 

I am still unable to find how to fix my Storage Manager. I can't seem to find anyone in the same situation as me. I strongly suspect it's because my volume1 doesn't mount anymore. So, not the right forum but I know we have experienced people here, do you know how to either force a remount of volume1 or even completely destroy it? At that stage I don't care about the data I had on it really. 

[Orphée]

1 hour ago, Tibag said:

 

I am still unable to find how to fix my Storage Manager. I can't seem to find anyone in the same situation as me. I strongly suspect it's because my volume1 doesn't mount anymore. So, not the right forum but I know we have experienced people here, do you know how to either force a remount of volume1 or even completely destroy it? At that stage I don't care about the data I had on it really. 

Did you try to force a DSM re-install ? (junior mode if I'm not wrong ?)

[Tibag]

44 minutes ago, Orphée said:

Did you try to force a DSM re-install ? (junior mode if I'm not wrong ?)

 

I suppose I could boot with only the "broken" disk (volume1 not mounting), reinstall and add back volume2? 

[Tibag]

So I actually tried to boot with the latest loader by just keeping my disk 0 (SATA 1:0, meant to be that volume 1) without any disk. When I try to recover it I get the "No drives detected in DS3622xs+". I feel like this is the source of all my issues. Does anyone know how to solve? 

 

In Junior UI I can see from dmesg:

Quote

[    6.124089] ata32: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[    6.124148] ata32.00: ATA-6: VMware Virtual SATA Hard Drive, 00000001, max UDMA/100
[    6.124168] ata32.00: 5860533168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    6.124188] ata32.00: SN:11000000000000000001
[    6.124268] ata32.00: configured for UDMA/100
[    6.124296] ata32.00: Find SSD disks. [VMware Virtual SATA Hard Drive]
[    6.124372] I/O scheduler elevator not found
[    6.124531] scsi 31:0:0:0: Direct-Access     VMware   Virtual SATA Hard Drive  0001 PQ: 0 ANSI: 5
[    6.124878] sd 31:0:0:0: [sdaf] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB)
[    6.125011] sd 31:0:0:0: [sdaf] Write Protect is off
[    6.125071] sd 31:0:0:0: [sdaf] Mode Sense: 00 3a 00 00
[    6.125187] sd 31:0:0:0: [sdaf] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    6.126275]  sdaf: sdaf1 sdaf2 sdaf5
[    6.126830] sd 31:0:0:0: [sdaf] Attached SCSI disk

 

and

 

Quote

SynologyNAS> fdisk -l 
Disk /dev/synoboot: 4096 MB, 4294967296 bytes, 8388608 sectors
522 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device       Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/synoboot1 *  0,32,33     9,78,5            2048     149503     147456 72.0M 83 Linux
/dev/synoboot2    9,78,6      18,188,42       149504     301055     151552 74.0M 83 Linux
/dev/synoboot3    18,188,43   522,42,32       301056    8388607    8087552 3949M 83 Linux
fdisk: device has more than 2^32 sectors, can't use all of them
Disk /dev/sdaf: 2048 GB, 2199023255040 bytes, 4294967295 sectors
267349 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device   Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sdaf1    0,0,1       1023,254,63          1 4294967295 4294967295 2047G ee EFI GPT

 

I am just no sure a re-install would work. 

[Tibag]

So I tried to rebuilt the loader with only my working disks... When it came back DSM was only suggesting to be reinstalled. So I let it go, hoping it would fix my Storage Manager. It came back, I restored my settings, and when opening the Storage Manager... it's still hanging! Sounds like I will never see my Storage Manager again. 

 

EDIT: in the end I gave up on it and proceeded with the upgrade of the version to the latest and... tada! Storage Manager is now fixed. 

Edited January 26 by Tibag

[blamaster]

Hi,

 

can someone help me with the m shell ?

 

I was previously using the pocopicos tcrp (TCRP JOT mode)

 

Now i wanted to use m-shell to build a new loader to perform an dsm upgrade.

 

So far i managed to install the m shell with the following command (from tinycore ssh session)

 

curl -L "https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/my.sh.gz" --output my.sh.gz
tar -zxvf my.sh.gz; 

 

After running the ./menu.sh script for the first time it updated tinycore to v14 and rebooted two times.

 

Now if i try to open the m-shell (./menu.sh) again the following log messages appear but the mshell is not loading.

 

Quote

Checking Internet Access -> OK
Checking if a newer mshell version exists on the repo -> Version is current
Loader sources already downloaded, pulling latest
Already up to date.
check update for tinycore 14.0...
tcrp-addons already downloaded!
current ucode = de_DE
current tz = DE
Inject urxvt menu.sh into /home/tc/.xsession.
LANG=de_DE.UTF-8
LC_CTYPE="de_DE.UTF-8"
LC_NUMERIC="de_DE.UTF-8"
LC_TIME="de_DE.UTF-8"
LC_COLLATE="de_DE.UTF-8"
LC_MONETARY="de_DE.UTF-8"
LC_MESSAGES="de_DE.UTF-8"
LC_PAPER="de_DE.UTF-8"
LC_NAME="de_DE.UTF-8"
LC_ADDRESS="de_DE.UTF-8"
LC_TELEPHONE="de_DE.UTF-8"
LC_MEASUREMENT="de_DE.UTF-8"
LC_IDENTIFICATION="de_DE.UTF-8"
LC_ALL=de_DE.UTF-8
 :  :
^[[?1049h^[[22;0;0t^[[1;24r^[(B^[[m^[[4l^[[?7h^[[?1h^[=^[[?1006;1000h^[[39;49m^[[?1h^[=^[[?1006;1000l^[[39;49m^[(B^[[m^[[24;1H^[[?1049l^[[23;0;0t^M^[[?1l^[>^[[H^[[2J^[[3JCall ^[[1;32m./menu.sh^[[0m to return to menu

 

Any idea why the mshell wont start ?