Jump to content
XPEnology Community

Recommended Posts

Posted

Hi,

 

same Problem here.

 

DSM start and logon works perfect but no HDD´s inside.

 

At the end of my Nanoboot start i got the following massage.

 

Post init

init: Unable to mount /dev filesystem: No such device

 

ty for helping or ideas

Posted
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.

This kind of scared me in the patch notes. Did they drop support for the DS3612xs and that's why they didn't mention it? You can't convert to SHR2 from SHR so if this affects xpenology a lot of people will displeased. And that's really understating it.

I won't risk the update, yet.

Posted

i also downloaded the iso from xpenology.nl but i can`t get the iso booting...

 

But when it does i think you have to choose upgrade in the menu and then update from the webpage

Posted

Can someone rename this thread title to BETA as it's misleading people (well those that can't be bothered to read the thread).

 

BETA BETA BETA BETA BETA..............................

Posted
Renamed.

 

Just installed this Beta to my Thecus N2560 (turned to DS214play).

It's funny that Security Advisor said my system is security compromised (modified) :wink:

 

 

Does this mean that a working version of xpenology DSM 5.1 is already on the way ?

Posted

Installed this in a VM this morning & as others have said the volumes are unmounted, I'm also getting the following notification error: "System internal service [apparmor] failed to start'. I'm happy to do some diagnostic work for Trantor / Sancome or anyone else for that matter if it will help.

Posted

Wait.. correct me if I'm wrong but you can't just update DOT or major revisions of DSM since the kernel is updated as well. The only reason this still works is because community folks have packaged this up to support other devices and defeat DSM protection. They actually have to bring over the modules from older versions of DSM to defeat the security protection. What you guys are seeing is the security protection unmount your filesystems. You won't be able to fix this yourself.

Posted

turning apparmor off:

support_apparmor="no" in /etc/synoinfo.conf and /etc.defaults/synoinfo.conf

 

(the startup script in init actually checks the config in etc.defaults)

 

This only eliminates apparmor, I am still looking at what goes wrong with the volumes - cat /proc/mdstat only shows md0 & md1 but md2 (where volume1 normally is) is lost after the reboot post installing. i.e. mdstat shows all 3 md after the install but before the reboot.

Posted
Better to bother now, then after the release did not actually need to rush.

Whats the rush? Will sky fail over if XPEnology is not updated to the latest version on the release day?

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.

×
×
  • Create New...