b0fh

You're talking about virtualising an operating system designed to manage low level RAID. I personally would much prefer to run that on bare metal hardware. Sent from my iPad using Tapatalk NO - I am talking about a general purpose OS that in this case has been slightly customized to run Synology apps. The apps were written to run on Linux. The only thing that really gimps the packages is their own version of DRM (is that even the right word here?) so people cannot do exactly what the Xpenology project does. Don't assume that IoT devices or NAS devices run custom, purpose-built OS. They don't. They just use busybox, linux, whatever, that is already built and bolt on their customizations. Very little is custom OS anymore.

Designed to run on bare metal? As was unix, linux, freebsd, openbsd, solaris, whatever. However, they all work fine in VMs as well. Did you know a LOT of embedded systems are running inside of a VM of sorts? There is no magic about a VM that will make the linux the NAS is built on run like s**t. However, unsupported bare metal hardware will. There is that. If everyone relied solely on what software was "designed" to run on, we would all be limited to the very expensive hardware created by a certain three-letter named company and been happy with whatever they decided we needed. We would not have been okay to buy our own, different hardware, to run the software on because it wasn't designed to run on non-whatever company hardware.

If you used all of your disks to create the volume, then you can only have 1 volume. Think of a volume as a collection of hard drives rather than a share.

ESXi is very useful in masking problematic hardware (think NICs) from Xpenology as well. It makes the environement much more predictable and generic, thus allowing for better support.

You will need to move to 10gbps (or faster) interfaces for that then.

FWIW, I had a LUN do that, and that fix worked temporarily, but every reboot it would become unavailable again. It was a file-based LUN, so I ended up copying the data and deleting the LUN in order to address it. I've not used file-based LUN since, but I am not sure it was the culprit. I will try again sometime, but for now NFS is working out ok.

If I had to guess, I suspect they are somehow writing some header to the disk itself or something to that effect. It would likely be proprietary to Synology and they would likely not release the answer. You would have to inspect the disks individually to really find out - unless someone else he is in the know on it.

It also depends. If you have created a disk group, the order is not important I think. The disk group will handle everything. If you just created a volume, I am pretty sure you are asking for trouble unless you really plan (and practice the move with other drives first) well.

Am I missing something? Isn't this just mounting an SMB/CIFS share? smbmount?

No, not possible at this time. Probably never. Wrong architecture.

I think the bigger why that needs to be asked is why would you "waste" that server on DSM???

@neuro1 - here is a link: https://xpenology.com/forum/topic/5882-working-dsm-6/?do=findComment&comment=58433 Again, as I have not used it I have no idea whether it would work at all, but based on my reading it looks promising. This certainly won't make it more broke .

I have not played with DSM 6 at all yet, but I seem to recall a posting that indicated you have to modify a syno conf file to enable shr on DSM6. It was either this thread or the main 6.0.2 thread. Search the forum.

I have used it since my first build. I did not have to do anything special. Installed it, made sure it was set to non-raid BIOS, no issue.

Avoid hardware RAID whenever you can (generally speaking), especially with DSM.

It is probably not unique to Xpenology. Make sure you look for Synology help and even other NAS help. Looking around I found this link that *might* help: hxxps://community.roonlabs.com/t/window ... ology/5755

I will look when I am home, but that is all I could think of off the top of my head. Good luck!

Do you have network discovery turned on for the Windows 10 devices? When you view network, you might see a notification near the address bar. Also, do you have file sharing turned on for the network connection on the windows 10 devices?

Should be okay. Lose the optical drive. It cannot be used and may actually make things worse. Buy a good power supply. I would probably buy at least a 450w with that older hardware. Better to have a little headroom. I am using an E6850 cpu in one server and an AMD Phenom X2 in another, so older hardware is fine. I do not run any hardware intensive apps on them, though. It all seems to work well.

I was not calling you dumb. I said running a Raid 5 without a backup would be really dumb. It sounds like you have a backup(?), but that it is difficult to pull the data back down. Yes, the RAID 1 arrays are for the OS. I am not aware of any way you can boot to linux, modify the array, then reboot xpenology and have it magically work.

It sounds like you do not have a backup of your files that you can restore. I would strongly caution you against converting to RAID5 without a backup. RAID6 without a backup is silly, RAID5 without a backup is dumb. That being said, perhaps the data is not that important and doesn't warrant a backup. In either case, there is not a good way to convert R6 to R5 in synology (probably because they know it is dumb ). Sorry.

Of course, though, if Synology did not disclose the source but rather it was leaked unofficially, I would definitely not advertise that you have a copy.

Uh...what? If they are required to disclose the source to the public, and did so, re-disclosing the unmodified source and giving Synology credit is all that is needed (US law).

@Allgamer - looks like autocorrect may have got you. I assume you meant Marvell?

Hopefully Synology is doing some sort of verification that the file has not been tampered with, and modifying it may cause that to determine it is not a legitimate pat file. I am just guessing, though, and this may not be accurate.