bottman

Can you enable Telnet and verify conenctivity still? Maybe run a 'top' command and see if the sshd is running. (you may also be able to see sshd in the resource monitor -> processes) Are you using putty or coming from a *nix and using built in ssh client? You may need to delete the keystore for this box. There is no way that I am aware of to roll back to Update3. Even if you did a clean install on your flash drive it would autodownload Update 4.

Funny... I recently migrated from Blueiris. Had used it for years. Loved some things... hated other things. The motion detect was always buggy to me and I got sick of running a dedicated box with a quad core @ 45-60% CPU usage when running a mere 6fps/camera. Consolidated by moving my 6 IP Cameras (5@720 & 1@1080) to synology. Then moved the 2x2TB HDD's over too. Only saw a 2% CPU load increase on Synology during live stream... Haven't looked back... Anyone want to buy a BlueIris License?! Kidding... I'll sell it to a Winders Friend. Best move by Synology... increasing default license count from 1 to 2. It gave me a chance to really test the unit and make purchases accordingly.

If you're bringing in existing Analog / CCTV Cameras into surveillance station I would go the route of an encoder. It would appear all of the Axis Encoders (Video Servers) are supported by the Surveillance Station.

I've found the most challenging part of using these cheap IP Cameras is what port they are using for ONVIF communication. Once you locate the port and configure Surveillance Station to use that port they should work. You may have to ask the seller if they know what port your camera is using. The six I have at my house are all using standard RTSP & RTP Ports but I found them using port 8899 for ONVIF. I have seen 8090 used on some cameras too.

Your system is showing an Intel i3 with only Two Cores because the Diskstation you are running is a DS3612xs which has a Dual Core i3 @3.1Ghz http://www.synology.com/en-global/produ ... c/DS3612xs if you shh into your box you can see all four cores are seen by DSM and are operational. ssh root@SYNOLOGY.IP.ADDRESS cat /proc/cpuinfo

Does the Surveillance Station Notify your DSM? ie: do you get an alert inside of DSM when there is motion? It's the 5th Icon from the top right inside of DSM. If you do get alerts inside of DSM. You could use "Notification Forwarder" from the community packages and PushOver [My Preference] to receive alerts. SS Detects Motion -> Sends Alert to DSM -> Notification Forwarder Parses Alert -> Sends Alert to PushOver -> PushOver Alerts your mobile device. With Pushover you can schedule alert times/quite times. So say from 0800-1700 M-F you want Alerts, but all other times you do not. That can be done. I am not sure why Push Notifications is not working. I am assuming it is one of many Syno---y features that is being blocked due to the fact that we are not running legitimate DSM and/or Serial#'s. Was Push being handled by SS or DSM? I use SS... but not PushNotifications. I even picked up a 4-pack to accomdate my 6 total IP Cameras after testing with SS for about a month. I was able to shutdown another PC-DVR box! I must say that I am impressed with the low CPU usage for 5 720p Cameras & 1 1080p Camera recording motion @ 10fps

Move to a new subject; not an issue with this guide. Let me know the post and I will see what we can do... First thought tho... 1+1 Does not always =2 !! http://packetpushers.net/the-scaling-limitations-of-etherchannel-or-why-11-does-not-equal-2/ Second thought is switch configuration and/or switch support for 802.3ad/LACP. Is your switch configured to see this as one bonded link and does your switch support it. If your switch is "unmanaged" it most likely does not support port agg. Either way... new subject or PM me!

To install Update 3 see the below post from another member. It is what I used to get Update 3 working [side note. WHen this guide was compiled there was only Update 2. If you follow the same instructions but see it jump over Update1 or Update2 you may want to download and NOT install Update3 and follow the below method)

Check with Sancomes Nanoboot for anything the communicty has injected... otherwise if you stick to what Syno--- supports... you cannot go wrong! http://www.synology.com/en-global/support/compatibility

This could be a hardware compatibility issue... Let me make sure I follow... you've got a HDD on a SATA Connetor that once had an optical drive? I would suggest speaking with other N54L Owners vs broadcasting that support request on an installation guide... Obviously you made it to the bottom of the rabbit hole since you are running DSM 5.0-4493 which is all this guide was slated to do. I personally wanted more HDD's than what the N54L would hold. I used to rock an older Intel SS4200e with its 4 bay max... I needed more!

The DS3612xs was the closest to my Hardware except the listing of 2 cores in the information center vs 4 cores on my Quad Core CPU. I also wanted SSD Cache (http://ukdl.synology.com/download/Docum ... _Paper.pdf) and support for 4 Gig Ports (only 3 Intel Gig ports installed now... two on Server board and a 3rd via PCI-Express which was used only to set up my LACP & VLAN on the two onboard). Nothing at my house needs more than a 2GB Interface. The only other 2GB interface I have is the uplink between my All GIG Cisco Catalyst Switch and my Cisco Catalyst 10/100 PoE Switch for Cameras & Access Points. Who knows... maybe 10Gb cards will drop as 40Gb comes around the corner! And dare I say 100?! I will say after "playing" with serial numbers... the serial number you input seems to possibly effect the Syno Model #. I tossed some garbage into an Dual Core Atom board and it said I had a RS2414+ (but that has an Atom CPU listed) Get some hardware and tinker... who cares what the output is... its not your main rig!

No problem. The Update 3 for 5.0-4493 CANNOT be done via update in DSM. There is a thread here that highlights accessing via secure shell (SSH) and installing Update 3. I will locate and post.

Is this Update 5.0 Update 1, Update 2 or Update 3?

First... I highly recommend a backup! Data & Config! From my understanding the configuration is kept on the drives. You should be able to follow the following guide with some amendments. http://www.synology.com/en-us/support/tutorials/484 More Specifically http://www.synology.com/en-us/support/t ... s/484#t2.2 Maybe someone more versed in this process can sound off. But I am assuming you have ESXi installed on different drives than the 3x4TB Drives? I am also assuming you mounted the drives in vSphere as "raw" drives. The exception being the drive or drives ESXi Hypervisor is installed on?

Message sent!

Message me... maybe we can try my work-around... http://xpenology.com/forum/viewtopic.php?f=2&t=3416&hilit=package+centre

I could thank dirty power initally for that... luckily it was something to do with the underground line coming into my home when it rained heavily. Couple of phone calls to utility company and a fresh ground at the street it was never a problem (added an APC SMT1500 for GP) How hot does your unit run? Have you exceeded your power supply? Does it auto-turn back on or are you having to turn it back on? Trying to identify power or hardware! It could be cooking itself, breaching thresholds and shutting itself down.

I believe that I have found a work-around for my own hardware/configuration... I am reluctant to post what I found and the fix there in... Not trying to get my work-around shut down by the syno-folks! Send me a message... you can join the guinea pig party! Same issue(s): Existing build running 4.2-3211 stopped seeing packages one day not too long ago with messages about connectivity. New Build/New Hardware running Nanoboot 5.0-4493(&4482): Tossed Network Error. Tried Serial # changes, virtualizing... denied! Applied my "work-around"... insta-packages! New & Old. I can understand their desire to prohibit access to their own internally developed applications... but the community?! Really?!

Thanks to all of the above and the members of the XPE community!

XPEnology DSM 5.0-4493 Update 4 (Most Current Stable DSM) Complete Bare Metal Guide ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Guide is depreciated since update 3 & 4. See below URL for an updated version of this guide with images http://node1.ignorelist.com/dokuwiki/do ... 4_hardware ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Thanks goes to all who contributed software, time, and a variety of posts that I used to compile this guide. This Guide was installed on x64 hardware using an x64 version of NanoBoot. You should have a running NAS <15 Minutes if you follow this guide. Please READ UP on NanoBoot, DSM 5.0-4493 and note if you're data is that critical... buy a Synology Box! Pre-req hardware: 1. Compatible Hardware [MoBo, Processor, NIC(s), HDD’s, Chipset, ect] 2. USB Drive (preferable not a cheaper unit) 8+GB Pre-req software: 1. Download SANCOME's Nanoboot (5.0.3.1) http://xpenology.com/forum/viewtopic.php?f=2&t=3052 [scroll down from first post and click the 'download mirror'] 2. Download DSM 5.0-4493 .pat File http://ukdl.synology.com/download/DSM/5.0/4493/DSM_DS3612xs_4493.pat 3. Download & Install win32diskimager http://sourceforge.net/projects/win32diskimager/ 4. Download & Install WinImage http://www.winimage.com/ 5. Download & install Synology Assistant http://global.download.synology.com/download/Tools/SynologyAssistant/4448/Windows/SynologyAssistantSetup-5.0-4448.exe Prep the USB Boot File: 1. Open nanoboot img file (NanoBoot-5.0.3.1-fat.img) with WinImage 2. Browse to “boot” -> “syslinux” -> & Extract “syslinux.cfg” to a working directory 3. Open syslinux with notepad++ (or other text editor--Notepad will work... NOT Wordpad!) --a. Locate default serial number (sn=B3J4N01003) and change it slightly… (I replaced the last 4 numbers with some random numbers and a letter in the beginning.) I am not 100% if this is to any benefit with Syno**** Service (Quick Connect), but I didn't want the same Serial# as others who opted not to change. --b. There should be 6 locations that “Find & Replace” Should find… and replace! 4. Save modified syslinux.cfg & inject syslinux back in overwriting changes 5. Save Nanoboot image file. Install the NanoBoot file onto flash drive: 1. Format USB Drive to FAT32 (quick format will be fine) 2. Open win32diskimager 3. Locate the file previously modified (NanoBoot-5.0.3.1.img) and write the image file to your USB Flash Drive. [Pay attention to the Drive you are writing to!) 4. Eject/Remove USB Drive and plug it into your BareMetal Server. Installing DSM: 1. Boot to USB Drive with AT LEAST one SATA Drive destined to be part of your XPEnology Build. (Change BIOS to boot USB Drive First!) 2. Wait for Nanoboot Screen 3. Choose “upgrade/degrade” 4. Choose the DSM version you wish to install (we are going current so 5.0-4493) 5. Wait for the OS to boot (you will see a prompt for DSM Login when completed booting) 6. Launch Synology Assistant (while on same LAN Subnet with DHCP enabled!) and wait until you see a Synology Server Populate with the serial number you modified in the above steps. 7. Right Click & Select Install --a. Browse to .pat file downloaded earlier [Official Synology .pat] --b. Input desired Servername, Username, Password & Check Create SHR After Installation [Any data on drives installed/mounted/plugged in will be destroyed!] --c. Grab a beer and wait until unit says it has finished installing DSM. System will reboot. Please be patient... 8. When you are looking at the "Finished" Wizard; Right Click on your NAS from the list and select “Connect” Update DSM to the most recent, secure from heart bleed & other exploits, version: 1. Open the control panel 2. Select “Update & Restore” 3. DO NOT CLICK UPDATE! 4. Select “Update Settings” --a. Select “Important updates only” --b. Uncheck “Check and download updates regularly” --c. Click Ok 5. Click Download “Update 2” Once it checks for updates 6. Click “Install” 7. Grab Another Beer and think of sharing some bitcoin wealth with those who helped! 8. Wait for reboot 9. Enjoy your Current DSM! I will get some screen shots & more details as I go along with my upgrade. I plan to wipe USB Drive & Hard Drive, try again, wipe, try again.. to make sure this is a solid process that can be replicated. This is my First post... & first Guide with XPEnology... more to come with images as I take my lab box to pseudo production... Since this is a BETA Build! I couldn't really find a solid "how-to" but was able to cruise enough forum posts and work off the knowledge used to get 4.2 going. Above is the output. Again, thank those who contributed... I just couldn't locate a solid guide and opted to take notes as I went about my install, then shared... I do want to point out to those fellow Linux users... unetbootin will work too for writing the image! My 4.2-3211 box ran off a unetbootin-ed image for over a year and thus far my Nanoboot with 5.0-4493 U2 has been through several boot cycles without any issues.