Mentat
Member-
Posts
119 -
Joined
-
Last visited
-
Days Won
1
Everything posted by Mentat
-
I cannot even use the keyboard, as I get a USBHid error http://i.imgur.com/ZPrRCnJ.jpg
-
Not working for me... 1. Boot on Install/Upgrade mod 2. Connect via Telnet as user root and password from here 3. Modified the etc.default/VERSION file as in the first post. 4. Synology Assist is still detecting version 6!
-
HVEC transcoding is working with Plex on my HP Microserver Gen8. You need a good processor (intel).
-
The problem is that on HP Gen8, with a changed CPU (55w), it still reads 40% in DSM and iLo! The command above, returns for me cat /sys/bus/platform/devices/coretemp.0/temp1_input 34000
-
Trial of Nanoboot (4493) - 5.0.3.1
Mentat replied to vtrchan's topic in DSM 5.2 and earlier (Legacy)
On a brand new installation, I get: error 16 inconsistent filesystem structure on nanoboot 5.0.3.2 It cannot be detected by Syno Assist. ==== Later edit microSD (boot device) was corrupted. Fixed -
I do not want to stream, I want to see on my iPhhone
-
I use the latest working version of Xpenology 5.0. My problem is that starting with IOS 8, I cannot use DS Video for IOS on my IPhone. I can connect and select the movie, but I cannot play anything. The function worked on 4.3 and IOS 7, but now everything is broken. I long suspected that the missing VLC from the IOS is the culprit, but for a short period, IOS 8.0 worked, but now... with the latest upgrade to DS Video for IOS, it's not working again! I get Error Unknown Error. (code:0) Video Station 1.4-0667 For you it's working?
-
Trial of Nanoboot (4493) - 5.0.3.1
Mentat replied to vtrchan's topic in DSM 5.2 and earlier (Legacy)
Latest update was tricky - lost all user permissions - Crashplan does not start, and this is a problem - DS Cam on my IOS 8.0.2 does not work. I do not know if it's Synology problm or IOS Problem... - Cloud Client has problems on Mac OS X. -
Trial of Nanoboot (4493) - 5.0.3.1
Mentat replied to vtrchan's topic in DSM 5.2 and earlier (Legacy)
Where did you get Nanoboot 5.0.3.2 ? On first boot, did you use upgrade from older versions (5.0.3.1)? -
Trial of Nanoboot (4493) - 5.0.3.1
Mentat replied to vtrchan's topic in DSM 5.2 and earlier (Legacy)
Thank you for user = root tip! It starts now! -
Trial of Nanoboot (4493) - 5.0.3.1
Mentat replied to vtrchan's topic in DSM 5.2 and earlier (Legacy)
"Fixed" the problem file was a huge mkv movie. It's working with normal h264 movies. Another big and new problem is that I cannot start MariaDB, I get I've tried to edit my.cnf and to add # , but is not working. I also tried to create http user, but is not possible. See instructions here. MariaDB it worked well in my Virtualbox installation and I never used MySQL on Synology, so there is no upgrade for any DB, but it's an upgrade from 4.3 -
Trial of Nanoboot (4493) - 5.0.3.1
Mentat replied to vtrchan's topic in DSM 5.2 and earlier (Legacy)
Big problem of me on my HP Gen 8 server. Ive updated from 4.3 to the latest DSM 5. All ok, except DS Video from my iPhone. It can list the video, but cannot play them! Without this, I lose 50% of my xpenology -
1. I do not think there is a limitation relative to the disk drives. 2. All the USB ports are working and can be used to transfer to/from an external storage device. 3. I do not know how will see an optical unit, I'll try in 2 days.
-
Ok. I fond it https://www.synology.com/en-global/rele ... /RS3413xs+
-
Where is that? My DMS wants to upgrade to 5.0!
-
I do not get it... I read that: OpenSSL versions 1.0.1 through 1.0.1f (inclusive) are vulnerable to this attack. On my Synology, using ssh, I've run: Synology2> openssl OpenSSL> version OpenSSL 0.9.8v 19 Apr 2012 It should not be vulnerable!
-
Is there any way to protect Synology administration panel with an htaccess ?
-
XPEnology DS3612xs DSM 5.0-4418 (BETA)
Mentat replied to Trantor's topic in DSM 5.2 and earlier (Legacy)
I've tried to upgrade to the latest version using the usual method. ((Virtual Box test) Download only the upgrade, run the task and manual upgrade. It gets an error to the second step. There is a temporary directory access error(2) during update