elmuziko

Hi everyone. So I've had a bit of a nightmare with my Xpenology and would welcome any advise to get things up and running again. About 2 weeks ago my DSM wanted to data scrub. I left it going over night and the next day found errors. It transpired the system did an update during the scrub and rebooted itself. Sigh. I repaired the RAID, only it transpired a disk had become unhappy, so I bought a replacement. Whilst trying to track down which one was dead I noticed the SATA card on my windows 10 machine (I run Hyper-V) was using basic drivers, so I updated that and the drive re-appeared. Problem is when the disk reappeared, it screwed up the order of all the disks on my Hyper-V machine, so I had to remove them all, then re-add them. Now, 48 hours later (to the hour), my DSM is still sat at the error message below... re-scanning disks. I have 22TB of available space (SHR so I have redundancy too) so there's a part of me that believes (hopes) it's just doing a pre OS scan and making sure everything is healthy. But 48 hours seems a long time to be sat at this screen with no signs of any other services. It's not showing up on my router, short of this image I wouldn't think it was doing anything. Is it safe to turn off and on? Should i turn it off and on? Any help would be appreciated. Thanks

Afternoon all, Anyone have any ideas on how to bring a volume back to life after a crash during drive expansion? I'm using 5.2 on Hyper-V. I was adding a new hard drive, it got to about 10% then I lost power to the Hyper-V host. When my machine came back up it said it'd crashed. I didn't panic so much, it started an integrity check that took just over 24 hours. Once it completed it didn't come back to life. I took the extra disk out, tried again, nothing. When I reboot, I get: "The system has detected one or more crashed storage spaces. Please check the following expansion units and hard disks are connected properly and functioning normally: [Disk 5, Disk 8, Disk 10, Disk 11]. When I got into Storage Manager I get: "Unable to use this volume. The data in the volume may be crashed. Please try to back up the data before removing the volume." I literally have no idea where to start. When I use my own account to SSH into the box it drops off immediately. I enabled my admin account and can now get into the box via Putty. My folder structure still exits in Volume1/@eaDir, but it literally is just the folder structure. Any help would be massively appreciated. If there's any log files I need to provide, just say so! Edit: SUDO apparently isn't installed.

By the looks of things it seems I'm one of the few (maybe the only one?) that hasn't found Salah troll like at all. Uncouth perhaps, and hasn't figured out how to use edit rather than reply, but not a troll. This post suggests a method around the QuickConnect kick yes? Surely that's helpful? I use VPN myself so don't know if such a thing has actually happened. And even if said person is a Synology employee, wouldn't we want that kind of inside information on the board? To give us a heads up on the direction they're taking?

If you have a few pennies available to you, get a new router, one that supports VPN. I uses an ASUS myself, most of the options in there are easy to understand so you can make your network fairly hardy. As for Syno security, have a look at: https://www.synology.com/en-uk/knowledg ... nology_NAS Even with all that in mind I still wouldn't set your Syno up to face the internet (as in open ports on your firewall and be able to log in from the outside world). A few years back there was a nasty program called SynoLocker that smashed through DSM ransomware style. ( https://forum.synology.com/enu/viewtopic.php?t=88770 ) It's better not to take the risk and instead connect to your machine via a VPN. There's this to look at too. It won't do a thorough scan of your network but it'll graze over the top in the same way a none targeted hacker would looking for an easy catch : https://pentest-tools.com/

No, not really. The best responses on StackOverFlow are the ones that come with an explanation into what each step does. Perhaps the manner in which the question was asked may have come across rude but remember we all have a common goal on here, to further progress Xpenology. The ones that deserve so little of the developers time are the selfish a******* that come on here as just an IP address, download what they need and contribute naff all, not even a thank you. Anyone signing up to the forum to comment (short of the spammers!) at the very least recognises the hard work Trantor and co have put into getting this up and running, even if it's just to say "it don't work innit". But anyway... I certainly don't mean to sound argumentative so apologies if it comes across that way.

Wouldn't package updates or even DSM updates go via this?

Can You write a sort of howto? i think will be usefull Agreed. There was a guy on here, can't remember his name for the life of me, that spent a lot of time building his own website with tutorials and videos on how to get DSM 5 onto just about any machine you wanted. https://cyanlabs.net/tutorials/ Although it's probably going a little far asking for videos, fluent guides with easy to understand steps pave the way for more people to get involved.

Maybe that's because there is almost no documentation about how to make a bootloader. If there are some good docs on how to build an image, maybe more volunteers will show up. Uhm... That's not true. The current loaders are nothing more than Syno's own boot solution (which you can easily reverse engineer if you buy a syno product and take a look around its inside working), paired with Grub (which has plenty of documentation), and a custom solution to get around their protection (which again, if was documented, Syno would patch in no time). No offense, but being spoon-fed all the information is not the way to become a developer. I'd argue otherwise. My job is almost entirely PowerShell based and the only reason I'm any good at it is because of StackOverFlow, Technet and tearing other people's scripts to pieces. We all have to start somewhere; as a Hyper-V user I, and the many Hyper-V users on site, feel overlooked in our quest to get on DSM 6+. Having some documentation and how to guides to at least get acquainted would make heller difference. Also, I can't imagine a world where Syno aren't already aware of how their protection isn't broken. If notepad ++ can check changes between documents, you can be sure as s*** Syno have already tore Jun's loader to shreds and found every change down to the last byte. More importantly you'd want them to, so they can build a better and more protected system. Which again means more developers working against the product would make it easier to unlock the next release.

I have an all mighty custom built rig with Windows 10 pro on top, Hyper-V and DSM sitting inside. At it's very basic this allows me to run Kodi from Windows 10 which in turn accesses all media from DSM. I also have several VM's making up a domain for work related purposes. There's no reason why I have DSM at all, I don't really need it since Sab, Sick, PHP can run from Windows. But it's a force of habit and I like it.

Best of luck, there was a moment last week with two pages of SPAM. It was awful.

ESXi for support. I use Hyper-V but it's unloved and rarely updated. :unhappy face.

That's great medric! I could test, if needed +1 for testing. Can you share your findings too? The more people we have we the shared knowledge on how to do this, the better chance we have of getting a Hyper-V img out the door when DSM 6.x or 7x is released.

+1 for trying Hyper-V. DSM5 works perfect for me on Hyper-V, even though it initially complained about running at s*** network speeds

Are there any guides on how to inject drivers? I'm thinking why don't we just copy the ones from Sancombe's 5. img and put them into 6? It might be a simplistic way of looking at it, but surely it could work? Ah sorry, just read the above. We have to wait until Synology release the Kernal then..

I'm sure I saw someone mention in the Jun post about Synology promising to release the source code for version 6 when 6.1 comes out. I assume with it, we'll finally get some Hyper-V support on version 6? I'm still using 5.2, it works perfectly fine but always worry about security patches and that. My box isn't internet facing but I'm guessing that wouldn't stop anyone who knows what they're doing to get in via another route.

http://terfmop.co.uk/blog/2013/07/31/hp ... sata-port/ From the main screen go to ‘Chipset > Southbridge Configuration > SB SATA Configuration’ and make sure your settings are the same as below: OnChip SATA Channel = Enabled SATA PORTS 4/5 IDE mode = Disabled SATA EPS on all PORT = Enabled SATA Power on all PORT = Enabled Return to the main screen then go to ‘Advanced > IDE Configuration’ and again, make sure your settings are the same as below. Embedded SATA Link Rate = 3.0Gbps MAX The above was taken from viewtopic.php?f=2&t=1316&start=30#p6904

There's an ISO here: viewtopic.php?f=2&t=20216&p=77489&hilit=hyper#p77489 Sadly it won't get you anywhere in Hyper-V yet, the drivers aren't compiled. It just sits there not doing a great deal.

Thanks. Both XPEnoboot_DS3615xs_5.2-5967.1 and your VDK have two com ports, com 2 looks something like this on either; ID is the only thing changes. get-vm | ?{ $_.name -like "DSM*" } | foreach { $_.comport2 | fl * } VMCheckpointId : 00000000-0000-0000-0000-000000000000 VMCheckpointName : Path : DebuggerMode : Off Name : COM 2 Id : Microsoft:79F4A04C-0C0C-487A-83A4-2702C2229BD2\8E3A359F-559A-4B6A-98A9-1690A6100ED7\1 VMId : 79f4a04c-0c0c-487a-83a4-2702c2229bd2 VMName : XPEnoboot_DS3615xs_5.2-5967.1 VMSnapshotId : 00000000-0000-0000-0000-000000000000 VMSnapshotName : CimSession : CimSession: . ComputerName : SUPERWIN10 IsDeleted : False This is the info you get for the network adaptor, Again same for both. Get-VMNetworkAdapter "dsm 6" | fl * VMCheckpointId : 00000000-0000-0000-0000-000000000000 VMCheckpointName : ClusterMonitored : True MacAddress : 00155D00BD0D DynamicMacAddressEnabled : True AllowPacketDirect : False IsLegacy : False IsSynthetic : True IPAddresses : {} DeviceNaming : Off IovWeight : 0 IovQueuePairsRequested : 1 IovInterruptModeration : Default PacketDirectNumProcs : 0 PacketDirectModerationCount : 64 PacketDirectModerationInterval : 1000000 IovQueuePairsAssigned : 0 IovUsage : 0 VirtualFunction : MandatoryFeatureId : {} MandatoryFeatureName : {} PoolName : Connected : True SwitchName : Virtual Switch AdapterId : 6154E465-99CF-4EC9-88BB-034015ADB786 TestReplicaPoolName : TestReplicaSwitchName : StatusDescription : {No Contact} Status : {NoContact} IsManagementOs : False IsExternalAdapter : False Id : Microsoft:165311A2-F098-4448-BA9D-69A8E3071913\6154E465-99CF-4EC9-88BB-034015ADB786 SwitchId : d8efd56e-0c5c-4595-ad82-a98d7a8a609d AclList : {} ExtendedAclList : {} IsolationSetting : VMNetworkAdapterIsolationSetting RoutingDomainList : {} VlanSetting : VMNetworkAdapterVlanSetting BandwidthSetting : CurrentIsolationMode : Vlan MacAddressSpoofing : Off DhcpGuard : Off RouterGuard : Off PortMirroringMode : None IeeePriorityTag : Off VirtualSubnetId : 0 DynamicIPAddressLimit : 0 StormLimit : 0 AllowTeaming : Off FixSpeed10G : Off VMQWeight : 100 IPsecOffloadMaxSA : 512 VrssEnabled : False VrssEnabledRequested : True VmmqEnabled : False VmmqEnabledRequested : False VmmqQueuePairs : 0 VmmqQueuePairsRequested : 16 VmqUsage : 0 IPsecOffloadSAUsage : 0 VFDataPathActive : False VMQueue : BandwidthPercentage : 0 IsTemplate : False Name : Network Adapter VMId : 165311a2-f098-4448-ba9d-69a8e3071913 VMName : DSM 6 VMSnapshotId : 00000000-0000-0000-0000-000000000000 VMSnapshotName : CimSession : CimSession: . ComputerName : SUPERWIN10 IsDeleted : False So if it's a network driver issue, I'm guessing it's because the Hyper-V drivers haven't been injected into the current build? I found this site, http://windeploy.co.uk/blog/hyper-v/ext ... 2-drivers/ I don't know much about drivers windows drivers don't work with linux?

Had a quick google around and can't find a straight answer. I'm running a Windows 10 machine with Hyper-V on the top. The disks are set to offline in Win10 then as direct attached LUN's to my Xpenology VM. One or more disks keeps disappearing entirely. I've looked around and found it's likely to be as a result of Windows power options, it was set to hibernate a disk after 20 minutes. I've switched this to 0 so it should hopefully keep it in the system, but noticed there's a 20 minute setting in DSM. Can this be left on? Or should it be switched off? I'm running WD Reds so I know they have their own idle settings built in. Any advice would be appreciated.

Not true.. You have to use Powershell.. Look up the Get-VM and Get-VMComPort / Set-VMComPort for more options. I have tried both VM v1 and VM v2 with a COM port capture. It boots but the nic is missing. We need the hyper-v kernel components. You're right, but it's not in the settings menu by default when the VM is Gen2, that's what I meant. Yes, the NIC is missing.. I don't suppose you can share your ISO of DSM 6 can you? I tried using an IMG to ISO converter and it failed. I have no idea how to work under the bonnet of Xpenology but I'm pretty good at PowerShell so can hopefully work with people to get Hyper-V support up and running.

OK so I've had no luck wish ESXi 6, so gone back to version 5.5 Slightly more luck, the VM builds now but when I try to attach a RDM drive it says the file failed to lock. I have a VDMK of the machine within its own datastore\RDM\Drive.vmdk Is that normal behaviour? Or do I need the VMDK file else where? Ta

Evening all Hopefully someone can help me. I've got a new ESXi 6 set up. I used the guide here (viewtopic.php?f=15&t=5255) to set up the VM but used the latest VMDK image rather than build my own. I've managed to power the machine on and can get to the install so I know the image is OK, but when I try to add any raw drives it won't let me. I used Xpenology member Cyanlabs video guide ( ) on how to map RDM's. I have 2 WD3 TB drives each is it's own datastore with a folder called RDM inside, and a VMDK of what i assume is itself. When I go to add a disk the RDM option is greyed out. When I point to the VMDK file I get "Incompatible device backing #0" I read on the internet to go to settings and disable RdmFilter.HbaIsShared I get the same error. Any ideas?

So not easy then. Bugger. I'll have a go, hopefully won't be too tricky. Ta for the quick response.

How did you get on with this? I tried using the video guides at http://cyanlabs.net/tutorials/installin ... -hardware/ for version 6 yesterday but had no luck. Kept getting some weird errors.

[Foul language removed]! Can't expand unless the same size or bigger. Why the f*** doesn't it say that on the RAID calculator? I'd have built it with smallest first!