Recommended Posts

Hi,

i can share my experience with 4.3. I am running intel board D945GCLF2 with Atom 330 and trantor's repack 4.2 working like charm. On another testboard (same as primary) tried first installed 4.2, then created volume1, everything works. Then i installed 4.3, and like others reporting, disk and usb stick are gone. But volume1 is steel there and i am able to write on it, install packages.

Some more logs from console:

DiskStation> cat /proc/partitions

major minor #blocks name

8 0 78150744 sda

8 1 2490240 sda1

8 2 2097152 sda2

8 3 1 sda3

8 5 73417024 sda5

9 0 2490176 md0

9 1 2097088 md1

9 2 73415872 md2

253 0 73412608 dm-0

65 64 7897088 sdu

65 65 16033 sdu1

 

DiskStation> parted -l

Model: ATA ST980811AS (scsi)

Disk /dev/hda: 80.0GB

Sector size (logical/physical): 512B/512B

Partition Table: msdos

Disk Flags:

 

Number Start End Size Type File system Flags

1 131kB 2550MB 2550MB primary raid

2 2550MB 4698MB 2147MB primary raid

3 4832MB 80.0GB 75.2GB extended lba

5 4840MB 80.0GB 75.2GB logical raid

 

 

Model: Linux Software RAID Array (md)

Disk /dev/md0: 2550MB

Sector size (logical/physical): 512B/512B

Partition Table: loop

Disk Flags:

 

Number Start End Size File system Flags

1 0.00B 2550MB 2550MB ext4

 

 

Model: Linux Software RAID Array (md)

Disk /dev/md1: 2147MB

Sector size (logical/physical): 512B/512B

Partition Table: loop

Disk Flags:

 

Number Start End Size File system Flags

1 0.00B 2147MB 2147MB linux-swap(v1)

 

 

Error: /dev/md2: unrecognised disk label

Model: Linux Software RAID Array (md)

Disk /dev/md2: 75.2GB

Sector size (logical/physical): 512B/512B

Partition Table: unknown

Disk Flags:

 

If you guys need more information or to make some test let me know :grin:

Link to post
Share on other sites
Hi,

i can share my experience with 4.3. I am running intel board D945GCLF2 with Atom 330 and trantor's repack 4.2 working like charm. On another testboard (same as primary) tried first installed 4.2, then created volume1, everything works. Then i installed 4.3, and like others reporting, disk and usb stick are gone. But volume1 is steel there and i am able to write on it, install packages.

If you guys need more information or to make some test let me know :grin:

 

Volume will be gone after reboot.

Did you try it?

Link to post
Share on other sites
copy their version to /lib/modules, restart, same issue

 

Their synobios.ko is for model DS411, DS710, DS1511, DS2411, DS712.... but not for DS3612.

 

What is the key difference of the firmwares? What features will be missing from a 1511 build?

 

I don't really know the differences but when I disassemble the module I only see models mention above.

When I do this on "our" synobios I see DS3612, RS3413, RS10613...

 

 

EDIT : After successfully boot the 4.3 russian build (with recompiled kernel) on my test computer , same issue... :sad:

Link to post
Share on other sites

The check is most likely implemented by using the buildin serial controller that is connected to the onboard sensors.

-> http://smallhacks.wordpress.com/2012/04 ... -devttys1/

If so then we need to create some kind of emulator service to fake any responses on the com port.

 

I will try to test this by relaying the ESX com port to a read diskstation and see what happens.

Link to post
Share on other sites
Looking forward to see a stable version 4.3 :wink:

 

Hum bad news about that. As you know they implement some security/check system during boot AND in webman.

 

I successfully identify the cgi that unmout disk/volume, replace them with 4.2 version. Manually create disk nod.

After that disk is detected and I can create volume. Try to run Package Manager and boom disk/volume unmouted. Replace cgi files... but return error when installing package :sad:

I think other files are patched with this security/check system. Maybe we need to disassemble these files to see how to fix this.

 

Of course all of this is pointless because after reboot volume/disk are unmounted.

Still no clue for fixing this at boot.

Link to post
Share on other sites

I only need some more free time :/ (too busy at work). It's like looking for a needle in a haystack. Stay tuned.

 

I was curious about "dnsdsm" which contains CA certificate.

 

openssl x509 -text -in /usr/syno/etc.defaults/dnsdsm returns:

 

Certificate:
   Data:
       Version: 3 (0x2)
       Serial Number:
           86:3d:37:01:51:85:ea:3c
       Signature Algorithm: sha1WithRSAEncryption
       Issuer: C=TW, ST=Taiwan, L=Taipei, O=Synology Inc, OU=SPG
       Validity
           Not Before: Jun 11 02:29:56 2013 GMT
           Not After : Jul 11 02:29:56 2013 GMT
       Subject: C=TW, ST=Taiwan, L=Taipei, O=Synology Inc, OU=SPG
       Subject Public Key Info:
           Public Key Algorithm: rsaEncryption
           RSA Public Key: (2048 bit)
               Modulus (2048 bit):
                   00:c4:91:4a:1b:cd:d6:6d:b1:c7:2f:12:85:33:8c:
                   68:56:9d:62:62:ec:29:a7:4a:4d:17:4c:bf:6e:b3:
                   50:b0:d1:04:ab:f6:aa:1a:0c:ce:e3:c4:43:06:6f:
                   75:f6:6b:d5:82:ab:73:04:f3:3f:68:f7:c9:66:fc:
                   da:1b:56:c8:ca:1d:e4:a0:1b:4f:10:8a:eb:25:2c:
                   37:85:b6:0b:59:b4:dc:0f:03:fe:fc:2c:02:19:82:
                   af:aa:ea:ac:12:8e:f8:73:9c:9d:0b:32:4c:66:77:
                   d1:fa:75:95:06:36:d6:02:5f:0b:15:b7:c0:b9:e0:
                   39:f8:1b:6f:8c:6a:df:e0:d7:bb:97:56:5c:d6:82:
                   cd:90:dc:95:c3:1d:d0:ed:60:21:c0:1a:78:b8:9f:
                   51:a1:60:9b:03:7f:e5:cb:ab:7d:d4:f5:eb:db:3e:
                   ff:89:1b:f2:b3:5c:4b:90:8c:aa:f5:0d:f5:8d:fc:
                   fc:ee:33:d3:da:fb:52:02:50:9a:d9:c7:0f:93:cf:
                   3f:c3:49:47:94:a2:80:fb:f8:56:c2:12:0a:d9:65:
                   bb:93:25:73:1f:f6:99:89:8f:ee:2e:4c:f9:2b:40:
                   b4:d2:3d:38:48:29:79:a4:1e:7d:73:63:d4:58:f6:
                   c0:81:f5:b1:c9:c0:79:ed:0b:ec:52:83:b1:c0:fe:
                   02:d7
               Exponent: 65537 (0x10001)
       X509v3 extensions:
           X509v3 Subject Key Identifier:
               0B:9E:30:4B:24:B5:B0:A8:49:BE:A6:EE:14:E4:6D:E4:ED:72:28:A9
           X509v3 Authority Key Identifier:
               keyid:0B:9E:30:4B:24:B5:B0:A8:49:BE:A6:EE:14:E4:6D:E4:ED:72:28:A9

           X509v3 Basic Constraints:
               CA:TRUE
   Signature Algorithm: sha1WithRSAEncryption
       b5:db:dd:79:61:e7:38:28:3d:c2:c6:4a:e0:d6:29:7f:d8:62:
       8d:64:83:25:75:5e:a2:6b:c5:09:90:09:ac:f9:26:f1:83:bc:
       7d:3d:d2:98:ea:62:45:0e:e1:96:36:27:ea:2d:68:34:ce:0f:
       4c:1a:87:81:ad:11:10:1f:05:22:b9:71:d5:d5:92:c6:ce:59:
       6d:87:01:70:51:87:b1:d0:6e:9e:d3:e6:4d:78:f0:73:2f:30:
       20:2e:f7:a6:24:97:37:c1:6c:2f:63:f9:2a:1d:27:72:5b:11:
       14:ea:60:a5:e1:3f:b1:dd:70:be:ac:33:82:d7:89:57:30:9f:
       ee:83:47:46:15:05:fb:67:92:ca:d1:76:19:ed:55:12:5f:7d:
       01:43:f0:c5:8e:ff:fb:88:74:20:d6:75:67:46:97:6d:79:e6:
       bc:7a:0c:35:3f:71:ef:5c:fb:e4:49:e2:ed:92:14:9b:48:31:
       00:0d:39:55:63:d0:93:be:5a:84:44:b0:a9:4b:c6:3e:c1:7b:
       43:91:5a:d2:23:da:29:4c:06:fa:15:89:7a:f5:e7:58:df:6b:
       e1:82:f9:a6:ed:10:eb:b9:77:d6:a5:91:0b:cd:e2:a9:a4:d3:
       8c:4b:1a:42:7b:11:0c:f1:d5:04:9a:72:cb:a4:23:67:09:fb:
       1c:2b:8d:cc

 

and this is strange.. certificate valid only for 1 month? For what is this good? o_O

 

grep -r "dnsdsm" /lib finds:

/lib/libsynocgi.so:/usr/syno/etc.defaults/dnsdsm

/lib/libdsm.so.4:/usr/syno/etc.defaults/dnsdsm

/lib/libdsm.so:/usr/syno/etc.defaults/dnsdsm

/lib/libsynocgi.so.4:/usr/syno/etc.defaults/dnsdsm

 

grep -r "/dev/sd*" /lib finds same files. Thats VERY interesting.. Now analyzing files with IDA PRO.

Edited by Guest
Link to post
Share on other sites

Anybody can look at file "storagehandler.cgi"? File is packed/protected :/ We need to unpack it for analyzing with dissasambler.

 

EDIT: I have core-dumped storagehandler.cgi then:

 

DiskStation> cat /volume1/@storagehandler..core | grep sd
libsynosdk.so.4
SLIBSpaceSsdCacheConfCheck
���������E�D�M��L$�$�sd
sysdef
sd%c
support_ssd_cache
support_generic_ssd
buzzer_ssd_cache_fail
update_ssd_support_list
strict_ssd_policy
umount_ssd
/tmp/space/ssd_trimming
ssd_trim
isSsd
ssd_%d
%s:%d Fail to get ssd cache size. [0x%04X %s:%d]
%s:%d Fail to get ssd cache needed memory. [0x%04X %s:%d]
/usr/syno/etc.defaults/dnsdsm
/dev/sd*
sd_cache
sd��:
libsynosdk.so.4
/usr/syno/etc.defaults/dnsdsm
/dev/sd*
/lib/libsynosdk.so.4
libsynosdk.so.4
libsynosdk.so.4
%s --sdk-mod-ver
/usr/syno/etc.defaults/dnsdsm
/dev/sd*
../sysdeps/unix/sysv/linux/dl-origin.c
../sysdeps/generic/dl-sysdep.c
../sysdeps/unix/sysv/linux/getcwd.c

 

Same interesting strings :grin:

 

edit2 got it..

http://www.k3dt.eu/storagehandler_cgi_ida.png

 

(same check is inside libdsm.so and libsynocgi.so) now we need bypass this check against pci/devices OR unpack storagehandler.cgi and patch all files.

 

/usr/syno/etc.defaults/dnsdsm
/dev/sd*

 

edit3:

yes.. it must check something with /proc/bus/pci/devices

DiskStation> grep -rE "/proc/bus/pci/devices|/dev/sd|dnsdsm" /volume1/@storagehandler..core
/usr/syno/etc.defaults/dnsdsm
/proc/bus/pci/devices
/dev/sd*
/usr/syno/etc.defaults/dnsdsm
/proc/bus/pci/devices
/dev/sd*
/usr/syno/etc.defaults/dnsdsm
/proc/bus/pci/devices
/dev/sd*
DiskStation>

DiskStation> grep -rE "/proc/bus/pci/devices|/dev/sd|dnsdsm" /lib/
/lib/libsynocgi.so:/usr/syno/etc.defaults/dnsdsm
/lib/libsynocgi.so:/proc/bus/pci/devices
/lib/libsynocgi.so:/dev/sd*
/lib/libdsm.so.4:/usr/syno/etc.defaults/dnsdsm
/lib/libdsm.so.4:/proc/bus/pci/devices
/lib/libdsm.so.4:/dev/sd*
/lib/libdsm.so:/usr/syno/etc.defaults/dnsdsm
/lib/libdsm.so:/proc/bus/pci/devices
/lib/libdsm.so:/dev/sd*

Edited by Guest
Link to post
Share on other sites

In libsynocgi.so

 

CGI Decrypt failed. &__cIpHeRtOkEn= /usr/syno/etc.defaults/dnsdsm /proc/self/comm /proc/bus/pci/devices bromolow /dev/sd* /dev/sas* synology_bromolow_3611xs synology_bromolow_3612xs synology_bromolow_rs3411rpxs synology_bromolow_rs3411xs synology_bromolow_rs3412rpxs synology_bromolow_rs3412xs synology_bromolow_rs3413xs+ synology_bromolow_rs10613xs+ synology_cedarview_412+ synology_cedarview_713+ synology_cedarview_1512+ synology_cedarview_1513+ synology_cedarview_1812+ synology_cedarview_1813+ synology_cedarview_2413+ synology_cedarview_rs812+ synology_cedarview_rs812rp+ synology_cedarview_rs2212+ synology_cedarview_rs2212rp+ synology_cedarview_rs2414+ synology_cedarview_rs2414rp+ synology_x86_411+ synology_x86_411+II synology_x86_710+ synology_x86_712+ synology_x86_1010+ synology_x86_1511+ synology_x86_2411+ synology_x86_rs810+ synology_x86_rs810rp+ synology_x86_rs2211+ synology_x86_rs2211rp+ synology_evansport_214+ synology_evansport_114+ 0200 111d806e pcieport 0310 0318 0320 0328 0400 11ab7042 sata_mv 0500 0600 0700 0800 0a00 808610d3 e1000e 0b00 0c00 0d00 0100 10000072 mpt2sas 0300 10953531 sata_sil24 10953132 80861533 igb 1b6f7023 etxhci_hcd 10b58603 0708 0710 0900 0308 1b4b9235 ahci 0a08 0a10 00d0 80862937 uhci_hcd 00d1 80862938 00d2 80862939 00d7 8086293c ehci_hcd 00e8 80862934 00e9 80862935 00ea 80862936 00ef 8086293a 00fa 80862922 00c8 808610e5 0160 80862e6e e1000 /usr/syno/bin/findhostd /usr/syno/bin/scemd /lib/libdsm.so /lib/libsynocgi.so   /usr/syno/synoman/webman/modules/StorageManager/storagehandler.cgi  /usr/syno/synoman/webman/modules/StorageManager/volumehandler.cgi   /usr/syno/synoman/webman/modules/PkgManApp/PkgMan.cgi   /usr/syno/synoman/webman/modules/PkgManApp/PkgSynoMan.cgi   /usr/syno/synoman/webman/modules/DSMNotify/dsmnotify.cgi 

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.