martva

These is a package called openvmtools. But I think is only if your installation houses the storage for datastores. https://www.noobunbox.net/synology/inst ... -xpenology

I get the console login. And I can type stuff. Because I wanted for the admin user to become available again in de gui, I issued the resetuser=admin during boot. This should reset the admin password to default, which is nothing (emtpy). But it also has reset the root user to something. It does not accept root/ (Permission Denied). The gui still says that I don't have permission to login. For none of my users. On the console I tried several options: root/password, root/admin, root/root, etc. None of them work. If someone has another option, I would really like to hear it. Strangely enough, the box is still accessible through NFS, SMB, AFP. Also all services running (sickbeard, sabnzb, couchpotato, crashplan, btsync) all work fine. So back to my question. Can I setup a xpenology with a new disk and after this add the old volume as a new one?

So yesterday I did a downgrade from 5022-U4 > 5022 to see what happens. Guess what! It didn't work Then I thought I'd reset the admin to default. I shouldn't have done that. Apart from the services (AFP/SMB/NFS). I'm totally locked out now. I'm not able to login via the GUI, SSH or the console. My current setup uses 3x 3TB disks in SHR. Does anybody know if I can do a new setup on a single disk (without the 3x 3TB plugged in) and insert the 3x 3TB disks after the setup is complete to access my data as volume2 or something like that. thx.

Nobody?

Hi all, I noticed yesterday that I was not able to login to my xpenology anymore. Problem: When logging into the webinterface on ip:5001 (like I always do) i'm getting the message that I'm not aloud to login. Like I'm blocked!? This should not be possible, because I whitelisted my internal IP adresses. Trying to login via ssh I get: ssh_exchange_identification: read: Connection reset by peer Services are working as expected. I still can use things like AFP, and SMB with the the admin user. Data looks good. All synology services do not work like Filestation, VideoDS, etc. I can still login with root via the console. When I installed my setup I started off with gnoboot, and upgrade my installation through nanoboot and now XPEnoboot 5.1-5022.3. When I was running nanoboot with dsm 5.0-4933 I implemented some basic security features like disabling the default admin user and creating a new one. And 2-step authentication. Now I'm running 5.1 5022.4. Now first off I want to disable the 2-step authentication. But I'm unable to find the right config file for this. Also I want to delete my last installed app properly. I installed AdvancedPowerManager. After which the problems started, but not right away. I wonder if this app can cause this behaviour? Can some post me the standard ssh_config file of the synology setup. Looking at mine /etc/ssh/ssh_config I can see everything commented out. Maybe I'm looking in the wrong place. Like I said, it looks like it only effects the synology part of the system. Do any of you guys run into something like this? Things I like to get fixed: - Restoring access of the 'admin' user. Can this be through the console. In the release notes of xpenoboot 5022.2 I found that you can add the resetuser=admin parameter during boot to reset the password, but does this also re-enable the admin user? Probably not. - Removing the 2-step auth. Google Authenticator. Where is the 16-digit file located. I know it was in the location /usr/syno/etc/preference//google_authenticator in version 4.3 of synology, but there is no preference folder located. - Removing the Advanced Power Manager app. Can I remove this by issuing an rm -rf /volume1/@appstore/AdvancedPowerManager ? But Do I need to delete some rc file somewhere else? Thx in advance!

Can you enlighten me one the part on how removing the USB drive will cause the HDDs to spin down? I don't get it...

Jman420, Are you saying you are already testing a working build of XPEnoboot for 5.1? Donation is coming your way!

Hail the Kings! With the release, please let us know where we can donate some $$$

Any tried the new upgrades yet? 5.1-5004.2 http://tweakers.net/downloads/33876/syn ... 50042.html

I think spectre verified the above... @Sancome. Would be happy to donate for the solution...

*Website reported an error* Double post

Hi Mentat, You need to reboot and choose the upgrade line in the bootmenu. Change the version number to 5.0-4528 This is no patch, like all 4493-UPDATEX, but an upgrade. So basically: 1. Reboot xpenology 2. in menu chose install/upgrade 3. click tab 4. change to upgrade=5.0-4528 Or option 2: Flash the USB drive with the boot image from http://www.xpenology.nl/boot-images/. For baremetal: http://www.xpenology.nl/xpenology-downloads/?myvar=1456 1. Boot xpenology 2. in menu chose install/upgrade From a laptop start the synology assistant and upgrade to 4528. Be sure to select keep files and settings.

Euhm Greg, Your release notes are for 4493-7...? See my post. I posted the same around the same time, but with the right release notes.

Synology release a new update today (or at least I was reminded by my setup). Anyone already tried updating to this version? Or can some test it on a test VM? Currently I'm running DSM5.0-4493-7. It looks like you need to upgrade your setup. I can't seem to find any bromolow patch.

Versio 5.0.2.2 is not the newest Nanoboot.. First download the new version from http://www.xpenology.nl/boot-images/ or from the developer. http://www.colafile.com/u/sancome I'm using Time Machine and AFP protocol with my mac and I don't have any problems. On what hardware are you running?

Check here: http://ukdl.synology.com/download/criti ... ck/4493-7/ These are the incremental updates. If i'm not mistaken this is the one you need: http://ukdl.synology.com/download/criti ... 3612xs.pat Don't download the rs* versions. These are for rackstation. Xpenology is build upon the DS3612xs.

its from DSM5.1 release notes. in my case the problem is that after using this procedure cat /proc/mdstat is showing that that md0 and md1 are build on sdX and i dont know how to change it or just delete md0 and md1 manually. Only thing is that the "Synology Hybrid RAID is no longer supported" remark in the release notes are ONLY for these systems. Also in the release notes: Storage Manager (for RS10613xs+, RS3413xs+, RS3614xs, RS3614RPxs, RS3614xs+ only) -You can now create volumes up to 200 TB large. -You can create RAID groups and RAID arrays. A RAID Group for Multiple Volumes or iSCSI LUNs (Block-Level) that use RAID 5 or RAID 6 may contain multiple RAID Arrays. -Synology Hybrid RAID is no longer supported. Full release notes: https://www.synology.com/en-global/support/beta_dsm_5_1

So I've updated the from U4 to U7. Rebooted and found I had no volume nor disks anymore. Did a shutdown -h now through ssh and manually turn my N54L back on again. When it came up, I had a volume, but still no disks. Another reboot fixed all problems. Volume and Disks were back and healthy. Permissions and ownerships were still in place.

Only these boxes suffer from the shellshock bug. 15-series: DS415+ 14-series: RS3614xs+, RS2414+, RS2414RP+, RS814+, RS814RP+, RS3614xs, RS3614RPxs 13-series: DS2413+, DS713+, RS10613xs+, RS3413xs+, DS1813+, DS1513+ 12-series: DS712+, DS1512+, DS1812+, DS3612xs, RS3412xs, RS3412RPxs, DS412+, RS812+, RS812RP+, RS2212+, RS2212RP+ 11-series: DS3611xs, RS3411xs, RS3411RPxs, DS2411+, RS2211+, RS2211RP+, DS1511+, DS411+II, DS411+ 10-series: DS1010+, RS810+, RS810RP+, DS710+ So only the beefcake models.

Did you have any issues with permissions, loss of volume and disk, like with update 5?

And is anything visible during boot? Like when booting after update 4? Or in the logging?

I know nothing about sancome but his work can be found originally at http://www.colafile.com/u/sancome. nanoboot.tk was his gift for europeans as colafile was slow as hell due to the fact it was hosted (somewhere far away) on the Asian continent. It looks like the site of sancome has moved to: http://nanoboot.eu.org/

What bootloader are you using. I'm still on Nanoboot 5.0.2.3 and it is booting 5.0 4493-4. Just curious what bootloader you are using.

I bought a Neo coolcam nip-02 (http://www.tinydeal.com/coolcam-nip-02-300k-pixels-14-cmos-05-lux-wifi-ip-camera-p-83335.html). By default it is not supported, but after using the (http://mysynology.nl/alternatieve-ip-camera-gebruiken-i-c-m-surveillance-station/ (google translate for other languages)) user defined option within surveilance station it works like a charm. But do not expect much from the image quality. It has a purple tone and it is only a 300K pixel ccd. And when installing I had some difficulties changing the default username and password. I had to reset it several times. Apperently it only supports alpha numeric charaters. No special charaters like *#!, etc.

Hi and welcome to the forum, I'm using the N54L, but for now only with one drive. A WD red of 3TB. It is configured as a SHR. In the control panel the option is set to spin down the HDD which it does according to the logs. Information Systeem 2014/07/17 06:41:24 SYSTEM Internal disks woke up from hibernation. Information Systeem 2014/07/17 05:51:36 SYSTEM Internal disks woke up from hibernation. Information Systeem 2014/07/17 05:21:24 SYSTEM Internal disks woke up from hibernation. Information Systeem 2014/07/17 04:41:22 SYSTEM Internal disks woke up from hibernation. Information Systeem 2014/07/17 03:51:42 SYSTEM Internal disks woke up from hibernation. Information Systeem 2014/07/17 03:21:17 SYSTEM Internal disks woke up from hibernation. Information Systeem 2014/07/17 02:41:18 SYSTEM Internal disks woke up from hibernation. Information Systeem 2014/07/17 01:51:42 SYSTEM Internal disks woke up from hibernation. Information Systeem 2014/07/17 01:21:17 SYSTEM Internal disks woke up from hibernation. Information Systeem 2014/07/17 00:41:19 SYSTEM Internal disks woke up from hibernation. Information Systeem 2014/07/17 00:26:30 SYSTEM Internal disks woke up from hibernation. Information Systeem 2014/07/16 23:51:37 SYSTEM Internal disks woke up from hibernation. Information Systeem 2014/07/16 23:21:15 SYSTEM Internal disks woke up from hibernation. Information Systeem 2014/07/16 22:41:13 SYSTEM Internal disks woke up from hibernation. Information Systeem 2014/07/16 21:51:42 SYSTEM Internal disks woke up from hibernation. Information Systeem 2014/07/16 21:21:13 SYSTEM Internal disks woke up from hibernation. Information Systeem 2014/07/16 20:41:14 SYSTEM Internal disks woke up from hibernation. Spin-down is set to 10 minutes inactivity. As you can see the system will do something every 40 minutes or so. Maybe it is my sickbeard running in the background. I still need to finetune this. Reckon putting the drive in RAID1 will give a similar output. As long as there is no IO, the disks will go into hybernation.