Build my own DSM 2.2-0959 for DS-106, update: 2.3, 3.0, 3.1

[goetz]

Hi,

...
I notice that on the German forum (thanks to Google Translate) you said you'd used the scemd from the beta. Is that just a case of extracting the scemd file from the beta pat and copying it over the one on the DS with 1922 installed?

Is it all working OK for you now and hibernating OK too?

Thanks

yes, extract scemd from beta pat file. Maybe you have to kill running scemd before copying.
I'm running Surveillance Station so there is no hibernation.

Regards Goetz

[w00dst0ck]

Is that just a case of extracting the scemd file from the beta pat and copying it over the one on the DS with 1922 installed?

Thats the way I've done it. Extracted it with 7zip and copied with sftp. After 'chmod a+x' I've done a reboot of the DS106e.

Is it all working OK for you now and hibernating OK too?Thanks

The messages about unexpected LED behavior stopped and the LED status seems OK.
Because this unit is sleeping about a year in the cabinet I don't know if the hibernation is working correctly before.

[derky]

Is that just a case of extracting the scemd file from the beta pat and copying it over the one on the DS with 1922 installed?

Thats the way I've done it. Extracted it with 7zip and copied with sftp. After 'chmod a+x' I've done a reboot of the DS106e.

Is it all working OK for you now and hibernating OK too?Thanks

The messages about unexpected LED behavior stopped and the LED status seems OK.
Because this unit is sleeping about a year in the cabinet I don't know if the hibernation is working correctly before.

Thanks, managed to copy the scemd over, but unfortunately the hibernate doesn't seem to work correctly, don't think it's spun down at all since the upgrade

[divxmaster]

hi, have the same message about 'modules/led.c:82 unexpected LED behavior' in /var/log/messages on my upgraded 106e and 106j to 3.2-1922

From which beta .pat do I have to extract the scemd file and where do I have to place it? Thanks!

[goetz]

Hi,
use this one. Replace /usr/syno/bin/scemd.

Regards Goetz

[divxmaster]

Thank you Goetz! Will try it!

[ronparchita]

Many thanks to you, really.

Please, I'd like to know if upgrade 106j to 3.2-1922 make it compatible with LION

Thank you

[ronparchita]

Hello,

I had a problem with that :
Install DSM 2.3-1139 on DS-106, DS-106e, DS-106j
viewtopic.php?p=89779#p89779
As root, I used vi to modify 106J to 107 and :w and :q
But after, updating, for three times, I had the message "fichier de mise à jour incompatible"
it means "compatibility problem"
Please, Any idea
Many Thanks

EDIT

Really sorry

It's my fault I used firmware of the 107+
Now Version firmware is DSM 2.3-1139

[gsxr750]

need a bit of help if possible

have 106e and have 3.22 running have done all the tuts and seams to run ok
but want to get my esata drive hooked up
have copied the files required into /usr/syno/hotswap .etc
when i plug a disk in it can see it but does not recognise the format. tried a new disk and told it to format
but returns an error is disk connected properly or something like that
any ideas ?

[ronparchita]

Thanks to you, you are very good

I am in this way "build my own 106J etc."

Please look at the new status

Nom de modèle DS107
Mémoire physique totale 32 Mo
Version firmware DSM 2.3-1139
Heure du système Sat Oct 29 14:28:56 2011
Durée de fonctionnement 1 jour(s) 15 heure(s) 25 minute(s) 38 seconde(s)
Volume 1 0.3/363.8 Go


Temperature 58°C /138 F

Now I have to change DS 107 To DS 106J and everything like this :

"install 1139 for DS-107 with DSM. After that edit /etc.defaults/synoinfo.conf

upnpmodelname="DS107" --> "DS106j"
supportsystemperature="yes" --> "no"
showtempdesc="yes" --> "no"
synobios="ds107" -->"ds106"
supportdomain="yes" --> "no" (optional)
supportfanctrl="yes" --> "no"
support_auto_poweron="yes" --> "no"
supportSATA="yes" --> "no"
support_mtd_serial="yes" --> "no"
surveillance_camera_max="2" --> "1"
esatadiskname="hdc" --> delete "

Here it's the problem

After typing ssh root@192.168.0.5 and giving my password
and typing vi /etc.defaults/synoinfo.conf

that appears :

unique="synology_powerpc_107"
company_title="Synology"

# system options
timezone="Pacific"
language="def"
maillang="enu"
codepage="enu"
defquota="5"
defshare="public"
defgroup="users"
defright="writeable"
eventsmtp=""
eventmail1=""
eventmail2=""
eventauth="no"
eventuser=""
eventpass=""
configured="no"
admin_port="5000"
secure_admin_port="5001"
pswdprotect="no"
supportweb="yes"
- /etc.defaults/synoinfo.conf 1/168 0%

It's not what I expected.
Please could you help me ?

Many thanks

[ronparchita]

Hi,
if rootfs is about 2450000 1k Blocks all OK and you can upgrade to 3.0

Please how many to upgrade to 3.2 ?

Is there a way to resize with MacInstosch

Many thanks

[gsxr750]

hi and thanks to all who contribute to this thread

is there a way to downgrade as i am unable to get esata working on 3.2 1944
i wish to return to being a 106e if possible ?
regards

[axel.azerty]

Following all the procedures described on this forum and on http://www.timo.dk/wp/2011/08/07/upgrad ... to-to-3-1/, I upgraded my DS-106e to DSM 3.2-1955 (for the DS-108j).

After reboot, everything seems to works, except /var/log/messages written every 4 seconds with "modules/led.c:82 unexpected LED behavior".

To solve this problem, with 3.2-1955, replacing /usr/syno/bin/scemd by the /usr/syno/bin/scemd from 3.2-1869 (beta) is not enough.
I tried to replace /lib/modules/synobios.o too, with the version from 3.2-1869 (beta) and this solved the LED problem.

Note: I didn't tried hibernation or eSATA. I don't know if these features are still working with this files.

[robotica]

Great Guide Goetze!

I succesfully upgrade my DS-106 to 3.1. Only problem left is that I can't install the packages (slimserver/ssod) for my Squeezebox.

Anyone a solution for this?

TIA

[ilanix]

Hi,
i was running 3.2-1955 on a DS-106 set as a DS108j.
To be ready for the upcomming beta 4.0 i changed the model to DS-109j.
After reboot the system crashed and couldn't find a DSM.
Reinstallation failed because i get the message that the installation file is incompattable with the system model.
Synology assistent still sees it as a DS-108j with 3.2-1955 but nor the file for the 108j or the 109j will install. I've tried a new harddisk but that failed also.
Telnet and SSH don't work either.
Should i wait for the new beta or did i brick it?

Pffft: fixed it by editting it back to 108j in notepad on my pc using ext2 volume manager

Still wondering why this happened.
Anyone?