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

[Druid]

Hi,

I've fixed my own problem: back tracked and un-remarked the:

rmdir /opt
[ -e /volume1/opt ] && mount -o bind /volume1/opt /opt

from rc.local all seems to be back in order though I haven't yet dared to try the restart - too many other things to do at the moment, will get around to it and post back here if problem persists.

Many,many thanks for all the help received

Jon

[maxxfi]

Ok, I see that in root filesystem (/) there is no /opt.

Then, run this command (when logged as root, of course):
"ln -s /volume1/opt /opt"
Check once again with "ls -al /" that this time /opt is included in the list
(it should appear with something like "opt -> /volume1/opt")
Then reboot once again.
If nothing else got messed up, ipkg should be active after the reboot.

[divxmaster]

Is it possible to upgrade my ds-106j to 3.1 (1631 or 1742)? I'm on 3.0 now. If so, what are the steps to be taken?

Thanks!!

[derky]

Apologies if this is a dumb question, but rather than mess about with vi to edit /etc.defaults/synoinfo.conf is it OK to cp the file to /volume1/public edit it on a windows machine and the cp it back, or is there a technical reason why this can't be done with this file. This is how I've edited system files in the past as I could never get to grips with vi at univeristy and that was 14 years ago now...

Thanks

[neilmcg]

Is it possible to upgrade my ds-106j to 3.1 (1631 or 1742)? I'm on 3.0 now. If so, what are the steps to be taken?

Thanks!!

Read this whole thread/topic - the answer to your question is yes and a solution is clearly laid out.

[derky]

OK, so I followed the instructions to get 2.3-1139 on my 106j (changed unique to 107, applied 1139, changed entries in synoinfo.conf, rebooted) and that's all up and running, and I want to move up to 3.0 next, but the assistant (and the status page in dsm) still shows the ds as a 106j and not a 107, is this correct?

I think I'm going to have to wipe the drive as my sys partition is to small for 3.0, but I though the assistant needs to see the ds as a 107 to install the correct firmware. Have I missed something?

[sesamestreet329]

Is it possible to upgrade my ds-106j to 3.1 (1631 or 1742)? I'm on 3.0 now. If so, what are the steps to be taken?

Thanks!!

Read this whole thread/topic - the answer to your question is yes and a solution is clearly laid out.

Hi,

Sorry that I might asking a question which was already be answered. Can anyone tell me again how to upgrade DS-106j to DMS 3.2 Beta or even 3.1 latest version? Does it use the same method as previous post of upgrade DSM 3.1 from DS-107 firmware?

Many Thanks

[neilmcg]

Is it possible to upgrade my ds-106j to 3.1 (1631 or 1742)? I'm on 3.0 now. If so, what are the steps to be taken?

Thanks!!

Read this whole thread/topic - the answer to your question is yes and a solution is clearly laid out.

Hi,

Sorry that I might asking a question which was already be answered. Can anyone tell me again how to upgrade DS-106j to DMS 3.2 Beta or even 3.1 latest version? Does it use the same method as previous post of upgrade DSM 3.1 from DS-107 firmware?

Many Thanks

Read the whole thread.
Change the identifier to 108j instead of 107

[goetz]

Hi,

..., but the assistant (and the status page in dsm) still shows the ds as a 106j and not a 107, is this correct?

I think I'm going to have to wipe the drive as my sys partition is to small for 3.0, but I though the assistant needs to see the ds as a 107 to install the correct firmware. Have I missed something?

did assistant list your DS as 106j for Servername and Model?
If your /etc.defaults/synoinfo.conf has

Code: Select all

unique="synology_powerpc_107"

all is OK.

Regards Goetz

[dennislundberg]

Hi

I just wanted to give some feedback on upgrading to DSM 3.0 without wiping the data from your disk. After reading the posts here I decided to have a go at upgrading my DS-106e.

To move the partitions on the disk I used free KDE Partition Manager 1.0.3 LiveCD which can be found at:
http://sourceforge.net/projects/partiti ... r-live-cd/

This went well, but it takes a lot of time. It took 6 hours for my 500GB disk. Unfortunately Partition Manager was not able to move the swap partition. It didn't recognize it as a proper Linux swap partition. So I had to use the commercial Acronis Disk Director Home for that step. Disk Director costs around 40 USD and is for Windows.

My 106e is now happily running 3.1-1613.

Thanks a lot for all the hints and tips in this thread that continues to breathe new life into an old piece of hardware.

[CCF]

Is it possible to upgrade my ds-106e to 3.1 (1631 or 1742)? I'm on 2.3 now. If so, what are the steps to be taken?

Thanks!!

[neilmcg]

Is it possible to upgrade my ds-106e to 3.1 (1631 or 1742)? I'm on 2.3 now. If so, what are the steps to be taken?

Thanks!!

The post before yours says "My 106e is now happily running 3.1-1613."

[sesamestreet329]

Hi,

Sorry that I might asking a question which was already be answered. Can anyone tell me again how to upgrade DS-106j to DMS 3.2 Beta or even 3.1 latest version? Does it use the same method as previous post of upgrade DSM 3.1 from DS-107 firmware?

Many Thanks[/quote]

Read the whole thread.
Change the identifier to 108j instead of 107[/quote]

Thanks neilmcg,

I have my 106j upgraded to 3.1-1748 now

[quondam]

Okay, I followed the steps by upgrading my DS106 to DS107 939, then DS107 1139. 1139 forced a reboot immediately after install, but everything came up fine and I was then able to install DS107 1613. This worked fine and I saw the 3.1 interface, but when I changed the synoinfo.conf details back as instructed and rebooted, the Status light started flashing. Running the Assistant found my device on the network, but the model number is now showing as DS107.

Trying to install the original DS106 959 PAT file fails at the Install DSM to hard drive stage (this is using the most recent version of Assistant), saying "An error occurred during installation. The telnet service of Diskstation is turned on for error determination.". When I connect to the device via Telnet, I get the error "sh: /usr/syno/bin/synoautoblock: not found" appearing at the top of the session, then a login prompt below. If I put root in as the user, it then asks for a password. I don't know what this is, and hitting Enter doesn't work, just giving me the above error again.

Trying to install the DS107 1139 PAT file I get an error message saying I need to install version 1613 or above.

Installing the DS107 1613 PAT file worked fine. The DS106 started up correctly, the DSM was accessible, I edited the /etc.defaults/synoinfo.conf file as instructed by goetz in his original post on Mar 09 2009, saved it, checked the changes had been made by opening it again, and then restarted the DS106 via SSH using the reboot command. When it started up, the same problem reoccurred - the orange status light was flashing and it shows up in the Assistant as a DS107. I reinstalled the DS107 1613 PAT file using the Assistant and everything is now working again but the synoinfo.conf details all correspond to the DS107 values rather than the DS106 values....

How do I resolve this problem?

Thanks,

quondam

[derky]

Hi,

..., but the assistant (and the status page in dsm) still shows the ds as a 106j and not a 107, is this correct?

I think I'm going to have to wipe the drive as my sys partition is to small for 3.0, but I though the assistant needs to see the ds as a 107 to install the correct firmware. Have I missed something?

did assistant list your DS as 106j for Servername and Model?
If your /etc.defaults/synoinfo.conf has

Code: Select all

unique="synology_powerpc_107"

all is OK.

Regards Goetz

Hi Goetz,

Yeah, that was the case, but in the end it turned out I had enough room to install 3.2 beta without wiping the drive after all, thanks for the reply though.

I'd say to anyone else wondering if they have enough space to intsall 3.0 upwards, when you use the df command to check partition sizes, use the -h option and it will report the partition sizes in GB rather than KB, so it's a bit more obvious what you are dealing with.