Hostilian
-
Posts
318 -
Joined
-
Last visited
-
Days Won
3
Everything posted by Hostilian
-
Same here, really temping to upgrade. Might give it a go this evening. Are you running bare metal? Yep.. Bare metal on test box and also on main NAS.. I would just leave it, but the Virtualbox package (which I've tested on my test 6.1 box and it works great) is really tempting me to upgrade. Especially since 6.1 update 2. #H
-
Really tempted to upgrade my main NAS now.. It's backed up, so fingers crossed should be fine.. My test 6.1 'server' is running fine.. The main reason is that they've finally got Virtualbox to work as an installable Syno Package.. Any news on moving out of Alpha, or is there not enough data back in yet? #H
-
Yes, I even didn't know that it costs and for what it is necessary until everything didn't fly at all few weeks ago. Always the used real IP and also free DDNS from the third-party supplier. But not all have Real of IP. But here recently noticed that the supplier of DDNS gives a similar fukntion - OVH (is in the list in settings). QuickConnect is not simply DDNS, it's a reverse proxy for your NAS, hosted by Synology. It is a paid service, the price is included in the HW you buy. Since none of us are buying the hardware, we are not exactly eligible to use the services. And about that I agree with Polanskiman. You simply have to look for another reverse proxy service that works for you. Exactly, I really don't know why people think it's a good idea to use Synology's hosted service for a hacked Synology box.. It's the one thing that could force Synology to start making things difficult for these custom loaders.. ie, it's bloody daft and could plunge this site into dealing with accusations of 'piracy' rather than being the nice mod site that we all enjoy.. With the software and a custom build, you're not actually taking anything from them. Using QuickConnect, you are.. These forums need mods that remove this sort of crap - before the site gets a takedown notice.. #H
-
Yep, definitely.. Also, the forum is badly in need of moderation. It's frankly a bit of a mess.. Lots of off topic responses (that should be new topics) etc etc..
-
Working, surprisingly well... I'm just testing this on my Test Server (with update to 6.1 and new 1.02 Alpha loader) but bloody hell, it works! When the new loader comes out of Alpha, I'll be running this on my main NAS.. Active Directory; coming up! Many thanks! #H
-
That could also mean that 1.02 will be 6.1 sources based AND out of alpha But we'd definitely need a better organized thread, and definitely better organized releases (possibly even on Github?) Yep. This thread really is out of hand now. At the very least, and as I've suggested before, please start a new thread for 6.1.. Some sort of proper repository for the code would be great.. #H
-
Has anyone tried updating FROM 6.1, to the latest update from Synology (6.1 update 1), when using the Alpha loader? Any issues? Any news on the loader and when it might come out of Alpha? Thanks #H
-
yes，I tried it use all 4 onboard The problem still exists What speeds are you getting when SSD cache is turned off? I think PCIE x1 is limited to 500MB/s (assuming PCIE 2.0), which would be shared by all devices plugged into this Interface.. No idea what the overhead is but I'd be inclined to make sure the SSDs are plugged into your motherboard, where they can make full use of the SATA3 interfaces (600MB/sec each).. In fact, given the speed of PCIE x1, I probably wouldn't use it at all..
-
Thanks for the info.. I'm just using an old Dell desktop to test the release - which has definitely only got 2 Sata ports (and two drives connected) - so I guess it's going to be 2 anyway.. When I go to use it on my main NAS system - probably when it's out of Alpha - it's probably going to be slightly different (it has 6 sata ports).. My point, I guess, was that I don't think this sataportmap command was being used at all in the original grub.cfg. I couldnt see where the sata_args list was called, so I moved sataportmap from it and into the common_args list (I could see where this was called). The sataportmap setting was present in older versions of the grub.cfg and it was the cause of my previous issues in 6.0.1... #H
-
Jun I'm booting a BareMetal machine from a USB drive - it has two SATA disks present.. I was under the impression, from previous builds of your loader, that the SataPortMap command was required to set the number of Sata disks present in your machine.. This SataPortMap command was in the original 6.0.x loaders - and setting it correctly fixed this very same issue in 6.0.1 and 6.0.2.. (as per http://xpenology.com/forum/viewtopic.php?f=2&t=20216&start=20#p72953.) Whatever the case, moving it to the common_args line fixed the issue in 6.1 on my BareMetal machine with your Alpha loader!.. Thanks! #H
-
Update to 6.1 Update1 works fine too.. It did take a few minutes to come back online though.. More so, I'd say, than doing the actual upgrade to 6.1 itself.. Cheers, #Hostilian
-
Think I've spotted a potential little bug in the grub.cfg file (or in how it's applied).. set common_args_3615='syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3615xs vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet' set sata_args='sata_uid=1 sata_pcislot=1 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=2 SasIdxMap=0' If I leave SataPortMap=2 (I have 2 disks in my test box, so =2) in the set sata_args line, it doesnt work.. I get the old reported issues 'we've detected errors on disks 3,4,5 etc. However, If I move the command up into the common_args line....... set common_args_3615='syno_hdd_powerup_seq=0 SataPortMap=2 HddHotplug=0 syno_hw_version=DS3615xs vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet' set sata_args='sata_uid=1 sata_pcislot=1 synoboot_satadom=1 DiskIdxMap=0C SasIdxMap=0' ...It works! It boots fine and I get the 'Install' prompt - rather than a load of reported disk errors.. After applying the 6.1 PAT file and restarting, disks are fine, data is fine, it's now on 6.1.. So........ Might there be an issue with applying the sata_args? (Bare metal upgrade on an old Dell - for testing. 2x Sata disks) Cheers, #Hostilian
-
So I'm backing up, again, all my data on my 6.0.2 update 9 box.. My 'real' Syno box is ticking away on 6.1 nicely.. I'm not going anywhere near 6.1 on my custom, until I've tested it on my other test box - and the loader comes out of Alpha.. Good work as always guys.. One thing.. Might it be better to start a shiny new topic for 6.1 - rather than in this DSM 6.0.2 loader topic? Would keep things nice and organised - and avoid confusion between the versions, IMHO! #H
-
Update 9 works fine on my Synology 216j (I always do this before I do my custom NAS). Also worked fine on my custom NAS (4th Gen i3). It did take a bit longer to come back up after the reboot (maybe a few minutes) but come back it did.. Just sit back and chill.. Make sure you have a static IP address (and not a reserved, static one dished out by DHCP - just because you can).. #H
-
Try it with a 4 or 5GB file. I can copy 1.2GB files before the issue hits (1.2 would be done in about 10-12 seconds). Actually, since first checking this, I've spun up a Windows 2008R2 server on the same ESXi implementation. Same issue with very large files (transfer speed drops after a time).. So I'm going to test with a different NIC. edit.. Have tested this evening and tried disabling TOE in ESXi - and it made a difference (or so I thought) speeds only dropped slightly from 112MB/s to about 80 and then stayed there. I tried changing it back (enabling TOE) to see if it went back to the way it was before BUT it was the same again (about 80). Very odd but I guess I'm happy with performance (so far). I did upgrade to the latest build of ESXi yesterday - 6.0.0 Update 2 (Build 4510822) - but at the time it didnt make a difference.. #H
-
When I first started looking at this, tranferring a 5GB iso to the disk, it too about 8-10 seconds before tranfer speeds dropped from 112MB/s to 20-45MB/s. A few changes (mainly installing 9.4 of VMWare tools using the manual package installer) and this has gone up to about 30 odd seconds before it drops. That's 30 seconds+ of saturating the Gigabit link at about 112MB/sec.. Does anyone have the latest VMWare tools for ESXi 6 please? I think it's on version 10 or something. The SPK file I tried installing was open-vm-tools_bromolow-5.1_9.4.6-1770165-3.spk Progress, but I'm hoping the issue is drivers, rather than anything else. I have nothing else running on this ESXi box, it's solely to test DSM6.0. #H edit.. Found version open-vm-tools_bromolow-5.1_9.10.0-2476743-1.spk testing it now.
-
Very odd.. The only reason I asked the above question was because when I first, rather, the last time I built in ESXi, I was only getting 45MB/sec transfer rates.. I can't use RDM as I don't have a SAN and am not sure how I can make use of them (for the home user) when you're trying to create storage in the first place (the NAS).. So I'm basically using virtual disks on fairly old (250GB) disks that I had lying around - on old hardware (core2quad) - to test it. It starts off at about 112MB/sec then heads fairly quickly down to 30-45MB/sec I've tried installing the VMware tools Pat file (seems to improve things slightly - but just takes a bit longer for performance to drop). Write latency on my two disks on my test box is very high.. Up to 2000ms.. Cheers #H
-
Mind if I add to this - as I think it's related - but apologies for hijacking! On ESXi, what sort of transfer rates are people getting with DSM6.0 installed - for a single Gigabit link (across the LAN) for large files? Would be useful to know if there was any noticable difference in the RDM vs Controller the OP mentioned too! Basically, if the performance is up to scratch, I might consider moving from a Bare Metal install to a VM (with DSM on a VM).. Gives me more flexibility! Cheers, #H
-
Totally agree.. Use QC without a real Synology and Synology will be sure to make tweaks to their code that will close down (or severely limit) this little project.. ie.. Don't do it.. There are plenty of alternatives that won't screw this up for everyone.. #H
-
It's ok.. Got it working with (to my surprise) one of the addresses in the grub.cfg file (rather than the REAL MAC addresses of my cards). I've done some digging on WOL and am now enlightened. It previously was working only occasionally - but now I know the circumstances in which it won't work.. ie.. if I go into my BIOS for any reason. Cheers!
-
Hey, thanks! Yeah, I'm using a 3rd party tool.. Well, about 4 of them. I've tried two on my phone and the same number on my PC. I was hoping to have something I could have on my phone; so I could WoL over wifi - wherever I am in the house. As I said, it is working under certain circumstances, but not from a powered down state using the Synology console (so that's not much use). I'll give Synology assistant a try, but was hoping for something I didn't need to have to start my PC to use. I belive the new version of Synology for Android has introduced issues with WOL (typical). Perhaps someone could confirm? Thanks #H
-
Hi all, Probably best for a separate thread for this... Whilst WoL does work (under certain circumstances) to my custom NAS with DSM 6.0.2 8451, it is far from reliable. I've tried to follow the threads to determine the issue and the fix - but haven't got a working fix yet. Basically, if I power down my server from within Synology, then try to WOL the box, it doesn't work.. If I then power it on using the power button, check the BIOS and shut down the machine - I can WoL the box and it powers up normally.. I've set what I think to be correct in the BIOS - but no joy trying to Wake it up again (when it's shut down from Synology console).. I've tried adding the Powerdown sh script to the rc.d folder... edit. Motherboard is ASUS H87i-plus (wol doesnt work with the built in Intel card) but I've got a PCIe Intel card, which is the one that works fine. Both are bonded - LACP - and it's working fine. Any thoughts? #H
-
winscp is fine, but it maybe not easily be connected as root user. so you need change the above mount line as something like this, to give non-root use full access to the boot partition. mount -o umask=0 /dev/synoboot1 /mnt there are a few possible reasons cause it not got saved: 1. your boot disk is set to non-persistence 2. you did not properly umount the disk after editing. 3. vi is not really beginner friendly. WinSCP works fine for me as root.. Trick to get it working with root is to manually reset your root password using SSH before you try to connect with WinSCP as root.. Otherwise you get an access denied error. Much easier using WinSCP to browse through the files and even edit them! Think it's something like (and you probably need to run sudo -i first); synouser --setpw root PasswordHere #H
-
Ummm. Yeah I do.. Unless I'm misinterpreting what you're trying to do! Always a chance! I thought I'd suggested a method (maybe I dreamed it?). Yes, I've tested it and it works.. #H My pc restarts (win10) when I try to disconnect the vmdk, nothing saved; VMware® Workstation 12 Pro (12.5.0 build-4352439) Hmmm. I'm using Win10 and it's fine. Try closing all programs you can (that you aren't using) even on the taskbar.. I'm still on 12.1.1 pro.. Maybe try that version (12.5 is still relatively new)? I'd maybe try disabling your virusscanner for a minute or two - just in case.. #H
-
You MUST plug your drives into ports one, two, three and four on the motherboard.. That means looking at the motherboard and seeing where ports 1, 2, 3 and 4 are marked. If you have a gap where there is no drive, it isn't going to work.. Plus, set SataPortMap=4 in your grub.cfg (search this thread for info).. #H
