Recommended Posts

Hi Trantor, thanks for the update, and the greate work.

 

Can anyone tell me if ISCSI works or not for you in 4.3?

I can't get it to work, It worked great in 4.2

 

 

Sorry, when I mount iSCSI to VMware ESXi, it crashed.

 

so I downgrade to 4.2 too :razz:

 

 

I'm still having big issues with ISCSI target. When I create a Block level LUN, it carshes the target, and I can't connect from any iscsi initiator. When I try to remove the LUN, nothing happens, and everything hangs on on the NAS.

 

Is this something that could be looked into?

Link to post
Share on other sites
@venom

 

i'm tryin to update but it fails, i was able to do update one without issues, then i have to reload the entire system and since i have tried to update straight to update 2 without any luck , any suggestions?

 

thanks

 

You should wait to see if this update is safe for Trantor's build. If it's ok, then :

 

Go to update, click download. Then go to scheduled tasks and create a custom task :

sed 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info > /autoupd@te.info1
mv /autoupd@te.info1 /autoupd@te.info

Run this task. Then go to update and hit the update button.

Link to post
Share on other sites

It does not have to load further. Here is the point where you use your web browser to access the server and install the whole system.

Except of course if your NIC is not supported in the release, in which case you cannot make any network connection.

 

Intel PRO / 1000 MT Dual Port Server Adapter (OEM) PCI64 10/100 / 1000Mbps

and this will work?

Link to post
Share on other sites

Hi,

 

this is my output:

 

NAS> df -h

 

 

Filesystem Size Used Available Use% Mounted on

/dev/md0 2.3G 492.4M 1.8G 21% /

/dev/md0 2.3G 492.4M 1.8G 21% /proc/bus/pci

/tmp 7.8G 1.0M 7.8G 0% /tmp

/dev/vg1000/lv 4.5T 1.5T 3.0T 33% /volume1

 

 

NAS>

Link to post
Share on other sites

+1 Worked for me too. Thanks

Use this from task scheduler, manual run after download update, then update.

 

sed 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info > /autoupd@te.info1
mv /autoupd@te.info1 /autoupd@te.info

 

 

It works, thank you!

 

[attachment=0]5.png[/attachment]

Link to post
Share on other sites

Hello!

 

I have a problem to update in version 4.3 update 2.

 

After running script the update failed.

 

"Connection failed. Please check your internet connection."

 

can anyone help-me ?

 

 

i have 4.3 update 1 running in a ASROCK Q77 with CPU Intel 3220T and 3 disk 500Gb in raid5.

Link to post
Share on other sites
Can somebody with Trantor's build give me the output of df -h ?

 

Running Trantor's build 4.3 3810 Update 2, the output from my system is

 

ss4200> df -h

Filesystem Size Used Available Use% Mounted on

/dev/md0 2.3G 480.1M 1.8G 21% /

/dev/md0 2.3G 480.1M 1.8G 21% /proc/bus/pci

/tmp 1003.3M 328.0K 1003.0M 0% /tmp

/dev/md2 1.8T 334.2M 1.8T 0% /volume1

ss4200>

Link to post
Share on other sites

I've just noticed that my virgin media VMDG480 superhub is not in the pull down list of routers now

and when I try to set it up it stops at "Remove Port forwarding Rules" I never got this before.

 

Anyway to bypass or add the router? I did click on update routers but the VMDG480 is not there any more. It was ok on 4.2.

 

thanks

Link to post
Share on other sites
Hello!

 

I have a problem to update in version 4.3 update 2.

 

After running script the update failed.

 

"Connection failed. Please check your internet connection."

 

can anyone help-me ?

 

 

i have 4.3 update 1 running in a ASROCK Q77 with CPU Intel 3220T and 3 disk 500Gb in raid5.

 

I have the exact same issue. Does anyone have any suggestions for how to fix this? Thanks in advance.

Link to post
Share on other sites

I'm running 4.3-3810 with synoboot 1.1 beta 2 on my N36L MicroServer.

The initial install went fine, and everything appeared to work.

 

I then wanted to install update 2, and followed the procedure above.

Unfortunately, I failed to notice that overnight, update 3 had been released, and so I ended up installing that instead.

 

The procedure I followed was this:

 

1) Download update using the DSM Update tool.

2) Create task that contains the following code:

 

sed 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info > /autoupd@te.info1
mv /autoupd@te.info1 /autoupd@te.info

 

3) Run this task manually.

4) Logged in as root, and verified that autoupd@te.info was modified correctly (which it was).

5) Clicked update button in DSM update.

 

The MicroServer rebooted, but hung during bootup.

The last message before the hang is:

 

[ 0.288134] pci_root PNP0A08:00: ignoring host bridge window [mem 0x000d0000-0x000dffff] (conflicts with Adapter ROM [mem 0x000cf000-0x000d19ff])

 

The contents of the autoupd@te.info before modification were:

 

{"blNeedReboot":true,"buildnumber":3810,"configUpdate":true,"debDir":"/volume1//@smallupd@te_deb","flashupdateDeb":"flashupdate_4.3-3810-s2_all.deb","installDeb":["libsynocgi-bromolow-bin_4.3-3810-s1_all.deb","libdsm-bromolow-bin_4.3-3810-s1_all.deb","webapi-bromolow-bin_4.3-3810-s1_all.deb","webfm2-bromolow-bin_4.3-3810-s1_all.deb","dsm-bromolow-bin_4.3-3810-s1_all.deb","libsynosdk-bromolow-bin_4.3-3810-s1_all.deb","openssh-5.8p1-bromolow-bin_5.8p1-3810-s1_all.deb","synologrotated-bromolow-bin_4.3-3810-s2_all.deb","openssl-1.0.x-bromolow-bin_1.0.1e-3810-s2_all.deb","libsynosdk-bromolow-bin_4.3-3810-s2_all.deb","flashcache-bromolow-bin_1.0-3810-s2_all.deb","libsynoflashcache-bromolow-bin_4.3-3810-s2_all.deb","dsm-bromolow-bin_4.3-3810-s2_all.deb","synobackup-bromolow-bin_4.3-3810-s2_all.deb","lnxscemd-2.0-bromolow-bin_4.3-3810-s2_all.deb","samba-3.6.x-bromolow-bin_3.6.9-3810-s2_all.deb","openssh-5.8p1-bromolow-bin_5.8p1-3810-s2_all.deb","samba-3.6.x-bromolow-bin_3.6.9-3810-s3_all.deb","webfm2-bromolow-bin_4.3-3810-s3_all.deb","libsynosdk-bromolow-bin_4.3-3810-s3_all.deb","lnxsdk-bromolow-bin_4.3-3810-s3_all.deb","openssh-5.8p1-bromolow-bin_5.8p1-3810-s3_all.deb","dsm-bromolow-bin_4.3-3810-s3_all.deb","lunbackup-bromolow-bin_4.3-3810-s3_all.deb","synobackup-bromolow-bin_4.3-3810-s3_all.deb","apache-2.2.x-bromolow-bin_2.2.25-3810-s3_all.deb","apache-2.2.x-virtual-worker-bromolow-bin_2.2.25-3810-s3_all.deb","linux-3.x-bromolow-bin_4.3-3810-s3_all.deb"],"newSmallFixNumber":3,"smallupdateDeb":"smallupdate_4.3-3810-s3_all.deb","updateType":"smallupdate"}

 

and after were:

 

{"blNeedReboot":true,"buildnumber":3810,"configUpdate":true,"debDir":"/volume1//@smallupd@te_deb","flashupdateDeb1":"flashupdate_4.3-3810-s2_all.deb","installDeb":["libsynocgi-bromolow-bin_4.3-3810-s1_all.deb","libdsm-bromolow-bin_4.3-3810-s1_all.deb","webapi-bromolow-bin_4.3-3810-s1_all.deb","webfm2-bromolow-bin_4.3-3810-s1_all.deb","dsm-bromolow-bin_4.3-3810-s1_all.deb","libsynosdk-bromolow-bin_4.3-3810-s1_all.deb","openssh-5.8p1-bromolow-bin_5.8p1-3810-s1_all.deb","synologrotated-bromolow-bin_4.3-3810-s2_all.deb","openssl-1.0.x-bromolow-bin_1.0.1e-3810-s2_all.deb","libsynosdk-bromolow-bin_4.3-3810-s2_all.deb","flashcache-bromolow-bin_1.0-3810-s2_all.deb","libsynoflashcache-bromolow-bin_4.3-3810-s2_all.deb","dsm-bromolow-bin_4.3-3810-s2_all.deb","synobackup-bromolow-bin_4.3-3810-s2_all.deb","lnxscemd-2.0-bromolow-bin_4.3-3810-s2_all.deb","samba-3.6.x-bromolow-bin_3.6.9-3810-s2_all.deb","openssh-5.8p1-bromolow-bin_5.8p1-3810-s2_all.deb","samba-3.6.x-bromolow-bin_3.6.9-3810-s3_all.deb","webfm2-bromolow-bin_4.3-3810-s3_all.deb","libsynosdk-bromolow-bin_4.3-3810-s3_all.deb","lnxsdk-bromolow-bin_4.3-3810-s3_all.deb","openssh-5.8p1-bromolow-bin_5.8p1-3810-s3_all.deb","dsm-bromolow-bin_4.3-3810-s3_all.deb","lunbackup-bromolow-bin_4.3-3810-s3_all.deb","synobackup-bromolow-bin_4.3-3810-s3_all.deb","apache-2.2.x-bromolow-bin_2.2.25-3810-s3_all.deb","apache-2.2.x-virtual-worker-bromolow-bin_2.2.25-3810-s3_all.deb","linux-3.x-bromolow-bin_4.3-3810-s3_all.deb"],"newSmallFixNumber":3,"smallupdateDeb":"smallupdate_4.3-3810-s3_all.deb","updateType":"smallupdate"}

 

Would really appreciate some insight into what I did wrong.

 

I'm guessing that one of the changes in the update has broken XPenology (i.e. 1. Enhanced system security)

 

Any help would be greatly received.

 

Andy.

 

 

[EDIT]

 

I have now power cycled the server, and everything booted up and it running fine. Not sure what went wrong, but a cold restart has fixed the issue.

Update 3 now up and running, and all appears to be fine. :grin:

Edited by Guest
Link to post
Share on other sites

Hi guys

Very nice work....thanks everybody, and especially to Trantor...

 

Yesterday i have installed xpenology 4.3 r1.0 on my new Asus H87M-pro, for now i have checked:

 

USB3 OK

Sata3 OK

eSata3 OK

UPS OK

Standby, usb, eSata, Sata OK

WOL problem, does not work, ave ideas? (on MB have enable NIC S4 and switch for wol)

 

PS:

This motherboard with i7-4770T, and Ali Seasonic SS-400FL2 F3, power consumpion in idle (only usb boot, and one ssd) is 25 watt.

Operating with 4 hdu segate st3000dm001 the power c. is 55Watt, st-by hdu power c. is 31 Watt.

(when transcoding first film i measuring consumpion :smile: )

Link to post
Share on other sites
Try to remove files autoupd@te.info from the root folder (rm /autoupd@te.info* ) and follow instructions again:

Download DSM update, execute code below and finaly apply update.

sed 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info > /autoupd@te.info1
mv /autoupd@te.info1 /autoupd@te.info

 

 

i have the some problem. But after i remove /autopd@te.info and update again now running no problem. Thanks.

Link to post
Share on other sites

Firstly thanks to all who have made this possible.

Just upgraded 4.3 v2 to v3 by running task

sed 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info > /autoupd@te.info1

mv /autoupd@te.info1 /autoupd@te.info

 

and performing auto update....worked fine.

setup:

ZOTAC Atom Dual-Core 1.6GHz/MCP7A-ION/DVI&HDMI/A&V&GbE/Mini ITX Motherboard IONITX-G-E

2GB RAM

4x1TB Red WD 2.5"

Link to post
Share on other sites
  • 2 weeks later...
DSM 4.3 in VMWare ruins my Battlefield 3 gameplay... my game is lagging insanely !!

 

you can see the massive lag going on in this video (starts at 1:40)

 

I've installed the following Packages:

- Audio station

- Cloud station

- Download station

- GIT Server

- High Availabillity

- iTunes Server

- Java Manager

- Media Server

- Perl

- Photo Station

- phpMyAdmin

- Plex Media server

- Python

- Python 3

- SVN

- Video Station

- VPN Server

 

The VMWare client, runs on a different server on the LAN (not on my gaming computer).. so it's pretty severe that it can ruin the whole network !!

 

edit:

NONE of the above apps are configured, and only 2 GB images is served in PhotoStation.

 

I haven't tried shutting down apps one by one (yet) so i dont know if its a single app that is evil :twisted:

LOL sounds like you need a gigabit switch or a better internet connection or some troubleshooting skills. lag means your connection sucks albiet ping times or you being on wifli or your server is downloading too much pr0n

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.