Recommended Posts

What about a image to install without vmware??

 

 

Its easy. Install Trantor's 4.3 test build (with newer bzImage), then login into ssh and copy /proc/bus/pci into for example /root/pci and append content of my file /root/pci/devices-append to your /root/pci/devices. Then edit /etc/rc and insert mount --rbind /root/pci/ /proc/bus/pci/ after "export HOME PATH". Reboot and it should work.

 

Mmm, where do i find Trantor's 4.3 test build??

 

and where do i find "content of my (your) file"??

Share this post


Link to post
Share on other sites

Mmm, where do i find Trantor's 4.3 test build??

 

and where do i find "content of my (your) file"??

 

 

http://xpenology.trantor.be/unstable_4.3.7z

http://k3dt.eu/devices-append

 

mount with:

mount -t ext2 -o loop,offset=32256 synoboot-4.3-test.img /mnt/

replace zImage with http://xpenology.trantor.be/zImage-4.3b

unmount

boot.

Edited by Guest

Share this post


Link to post
Share on other sites

If you test/use this virtualized, you probably don't need raid so edit

/etc/synoinfo.conf
/etc.defaults/synoinfo.conf
and set supportraid="no"

before you create your volume of even before you install it from pat.

Share this post


Link to post
Share on other sites

What about a image to install without vmware??

 

 

Its easy. Install Trantor's 4.3 test build (with newer bzImage), then login into ssh and copy /proc/bus/pci into for example /root/pci and append content of my file /root/pci/devices-append to your /root/pci/devices. Then edit /etc/rc and insert mount --rbind /root/pci/ /proc/bus/pci/ after "export HOME PATH". Reboot and it should work.

 

I followed all the steps against a physical PC (not VM), which can install DSM 4.2 before, but the hard disk still not mounted. Is it expected? or the steps are only true for VM environment?

Share this post


Link to post
Share on other sites

First of all, thanks for the great work so far with 4.3!!!!

Is the solution from VeNoM and neXus ready for "production"?

 

@Trantor

Will you come with an 4.3 version?

 

Thanks in advance

Share this post


Link to post
Share on other sites

[   45.114468] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'scemd'
[   45.115700] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'scemd'
[  113.277926] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'login.cgi'
[  113.279200] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'login.cgi'
[  113.283929] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'login.cgi'
[  113.285184] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'login.cgi'
[  114.655547] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'dsmnotify.cgi'
[  114.656797] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'dsmnotify.cgi'
[  114.723382] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'storagehandler.'
[  114.724610] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'storagehandler.'
[  132.100215] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'storagehandler.'
[  132.101459] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'storagehandler.'
[  136.387838] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'storagehandler.'
[  136.389089] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'storagehandler.'
[  137.351953] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'storagehandler.'
[  137.353209] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'storagehandler.'
[  137.376302] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'storagehandler.'
[  137.377549] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'storagehandler.'
[  139.290178] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'storagehandler.'
[  139.291515] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'storagehandler.'
[  139.570685] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'storagehandler.'
[  139.575826] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'storagehandler.'
[  145.707498] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'dsmnotify.cgi'
[  145.708782] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'dsmnotify.cgi'
[  153.243617] DSMGENERIC: User space process accessing /proc/cpuinfo is 'SystemInfo.cgi'
[  160.756756] DSMGENERIC: User space process accessing /proc/cpuinfo is 'SystemInfo.cgi'
[  163.491981] DSMGENERIC: User space process accessing /proc/cpuinfo is 'SystemInfo.cgi'
[  166.174272] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'PkgSynoMan.cgi'
[  166.175557] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'PkgSynoMan.cgi'
[  166.179822] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'PkgSynoMan.cgi'
[  166.181071] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'PkgSynoMan.cgi'
[  166.830047] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'PkgMan.cgi'
[  166.831346] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'PkgMan.cgi'
[  169.865763] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'PkgMan.cgi'
[  169.867052] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'PkgMan.cgi'
[  176.148810] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'dsmnotify.cgi'
[  176.150087] DSMGENERIC: User space process accessing /proc/bus/pci/devices is 'dsmnotify.cgi'

 

Mine is almost ready. But I would not recommend using it in "production". Stick with 4.2, it's safer.

The 100% safe way to use 4.3 is to never update anything, including apps.

Share this post


Link to post
Share on other sites

@ VeNoM :

I'm wondering if you can test your build inside ESXi 5.1, having the VM configured with hard disk 2 as SCSI(0:0), controller SCSI Paravirtual?

Currently I'm struggling to get it work with Trantor's 4.2-3211-v1.2 build, but still no luck, even with new modules added to V1.2a beta1 :sad: .

The only version working this way in ESXi until now is "esxi_install_3202_v2" from jukolaut and odie82544.

 

PS: If you don't have this environment, I can offer you access to mine.

Thanks.

Share this post


Link to post
Share on other sites

It's runs for about 48h on my brand new N54L. Installed from PAT, update done to latest. USB device protected by sinology mechanism (I can also change my boot kernel / parameter within the running system without breaking anything). I don't have any bios bad checksum issue (but I didn't played with the scheduled function or WOL).

 

It works fine, but need more test. During my tests, I discover that other .cgi are doing some "device check test". When it occurs, you must recreate all block nodes described in /proc/partitions.

 

I aslo experience some issue, where the volume crashed (but goes back after reboot). Or some issue regarding the monitor status regarding the network device (fixed by a reboot too).

 

So it's not ready for production unless you are familiar with DSM internal to get through theses issues. I recommend stay on 4.2 for the moment.

Share this post


Link to post
Share on other sites

Do you think we will ever see a working 4.3?

 

Thanks for your hard work.

 

I can test on my HP N54L if you like?

Share this post


Link to post
Share on other sites

I personnality switched to OpenMediaVault. XPEnology is a great project, but I can't let a non-updated OS with security issues running on my network.

Share this post


Link to post
Share on other sites
I personnality switched to OpenMediaVault. XPEnology is a great project, but I can't let a non-updated OS with security issues running on my network.

If you use 4.2 you receive all patches and you con update like original DSM

Share this post


Link to post
Share on other sites
If you use 4.2 you receive all patches and you con update like original DSM

 

Do you mean patches for packages or patches for OS itself?

Share this post


Link to post
Share on other sites
If you use 4.2 you receive all patches and you con update like original DSM

 

Do you mean patches for packages or patches for OS itself?

If you dont update kernel, do you need to patch?

i dont want push you to use xpenology, i'm only do a chat :smile:

Share this post


Link to post
Share on other sites
i dont want push you to use xpenology, i'm only do a chat :smile:

 

Me too :smile: and i like xpenology.

 

I havn't even tried to update xpenology. I thought that it will be be fully updated from 4.2 to 4.3. Could you explain how to install just patches?

Share this post


Link to post
Share on other sites
i dont want push you to use xpenology, i'm only do a chat :smile:

 

Me too :smile: and i like xpenology.

 

I havn't even tried to update xpenology. I thought that it will be be fully updated from 4.2 to 4.3. Could you explain how to install just patches?

You cant update from 4.2 to 4.3 due to some security mechanism, but you can update 4.2 with recent patches for apps simply browse "app store" for synology, if there is new version of application, click update and that's it

kernel and core system can be updated only if synology make patches, if you have needed skills you can use croostools and source from open sources parts to make your own patches and , for example, add new driver on kernel tree, recompile and install on old kernel.

for wat i saw synology use dpkg system to update core system

Share this post


Link to post
Share on other sites
I personnality switched to OpenMediaVault. XPEnology is a great project, but I can't let a non-updated OS with security issues running on my network.

 

Interesting. Hadn't seen OpenMediaVault. I might be willing to switch but I have drives of different sizes and SHR is really a brilliant solution over RAID5. Also, I'm enjoying the surveillance station so I'm not sure how I would replace that if I ran OpenMediaVault. Run something like motion?

Share this post


Link to post
Share on other sites
I personnality switched to OpenMediaVault. XPEnology is a great project, but I can't let a non-updated OS with security issues running on my network.

 

Interesting. Hadn't seen OpenMediaVault. I might be willing to switch but I have drives of different sizes and SHR is really a brilliant solution over RAID5. Also, I'm enjoying the surveillance station so I'm not sure how I would replace that if I ran OpenMediaVault. Run something like motion?

Well, some people are currently developping a SnapRAID plugin that will allow you to use disks of different sizes, and protect only the FOLDERS you want to protect with single or double parity. That's kinda cool.

 

Regarding a surveillance solution, I know there's no plugin for that, but keep in mind that OpenMediaVault is basically a Debian system with a nice web-ui for management. I think you can find easily a surveillance software for linux. Give it a try with a virtualbox.

Share this post


Link to post
Share on other sites
Do you think we will ever see a working 4.3?

 

Thanks for your hard work.

 

I can test on my HP N54L if you like?

 

nope.. its been several months now im pretty much sure this is a R.I.P. eventually there's going to be version 4.4 and pretty much this will be an obsolete project. Great while it lasted.

Share this post


Link to post
Share on other sites

Dead? no. I'm running 4.3 files I provided with smallupdates applied. 20 users, 10TB of data, 5 IP cameras, Plex server, all works fine. It CAN be usable. But still waiting for VeNoM's release.

Share this post


Link to post
Share on other sites
Dead? no. I'm running 4.3 files I provided with smallupdates applied. 20 users, 10TB of data, 5 IP cameras, Plex server, all works fine. It CAN be usable. But still waiting for VeNoM's release.

 

dead to me and many others since nobody has released a working version (july / august!!!).. all we have is left overs from 6+ months ago thanks to traintor and anyone else that made it possible. I tried to have hope up until like September.. at this point fuk it id buy a synology box if i want something to work right. my test box is on and is left as a dummy storage unit. would be awesome by December someone comes out with 4.3. my real synology a 212j is still grabbing all the legit updates 4.3 3810 :smile:. Due to the slowdown of the project ive actually cancelled buying hardware, once something promising yet so disappointing. Hopefully someone can crack it like they did with OSX running on a dell. right dsdt and bingo who needs an imac.

 

as to you running 4.3 id be curious if the files are downloadable i turned my m8 onto this synology project and would love to update his.

Share this post


Link to post
Share on other sites

In fact my release works fine but I think I will keep it for me for several reasons :

 

1/ syno put some verification so they don't want the dsm been installable on a cheaper system.

2/ if it spread on the internet as a ready to use release, syno will certainly add more check in next release.

3/ all on this thread give enough information to create your own working system.

4/ I don't recommend dsm for kiddies as update could break the system

5/ the kernel modification need to be included if they update the kernel and I don't want to be the maintainer.

6/ it's easy to create a Trojan horse release, with backdor in it, that's why I create my own release from scratch. As it's a borderline project, I suggest to only install code you can trust.

 

 

So to sum up its great if you are familiar with Linux and understood all of the things in this thread. Dsm check can be defeated for the moment. I take responsibility on my own hardware if it failed, I never support this release for others.

 

For a production usage, you should consider using openmediavault/freenas/openfiller.

 

Maybe if I am in a good mood I will post my synoboot img used to install genuine pat files.

Share this post


Link to post
Share on other sites
In fact my release works fine but I think I will keep it for me for several reasons :

I absolutely agree!

Share this post


Link to post
Share on other sites
In fact my release works fine but I think I will keep it for me for several reasons :

 

1/ syno put some verification so they don't want the dsm been installable on a cheaper system.

2/ if it spread on the internet as a ready to use release, syno will certainly add more check in next release.

3/ all on this thread give enough information to create your own working system.

4/ I don't recommend dsm for kiddies as update could break the system

5/ the kernel modification need to be included if they update the kernel and I don't want to be the maintainer.

6/ it's easy to create a Trojan horse release, with backdor in it, that's why I create my own release from scratch. As it's a borderline project, I suggest to only install code you can trust.

 

 

So to sum up its great if you are familiar with Linux and understood all of the things in this thread. Dsm check can be defeated for the moment. I take responsibility on my own hardware if it failed, I never support this release for others.

 

For a production usage, you should consider using openmediavault/freenas/openfiller.

 

Maybe if I am in a good mood I will post my synoboot img used to install genuine pat files.

 

yeah my m8 loves to tinker, me I just stuck with the traintor. But youll never see me make one silly post about is it ready yet. Ive already chimed in and left it at that while others are crying wah wah wheres the update. My m8 was tinkering with it but couldnt get some things to work virtually but he sounded like he was close enough like you was but never that close.

Share this post


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.