LeeBear

Members
  • Content Count

    20
  • Joined

  • Last visited

Community Reputation

0 Neutral

About LeeBear

  • Rank
    Junior Member
  1. I'm sure someone will correct me but if you don't want DSM to see the USB boot drive after it loads don't you just modify your boot img .cfg file and put the PID and VID of your USB device instead of the default one. The default for nanoboot is something like this: kernel zImage ihd_num=0 netif_num=1 syno_hw_version=DS3612xs sn=B3J4N01003 vid=0x0EA0 pid=0x2168 You can plug your USB drive in a windows machine and use device manager/view resource to get the VID and PID of the USB drive.
  2. The way Plex transcode is by default it will try and transcode 120 seconds of the video as fast as it can, that's why every CPU maxes out regardless of speed. Then it will throttle down and up as it tries to maintain that buffer. While transcoding is CPU intensive it's also I/O intensive as there are combination reads and writes, if you don't want your NAS services to be impacted during the transcode I suggest you put your apps/Plex Temp folders on separate spindles then your media. Personally I use an SSD for my apps/temp and keep my media/files on a separate volume.
  3. The general rule is for any .XXXX version updates you can't use the built in web GUI in DSM because we don't have a real Synology onboard Flash RAM to update. The update in the web GUI basically updates the onboard flash with the DSM .pat file, reboots, then updates the DSM partition on the hard drives. Since we obviously don't have the onboard flash RAM it will fail. We however emulate this process by replacing our boot device (IMG, ISO, USB) with the newer Nanoboot/Gnoboot version, essentially faking updating the Flash RAM. Then we used the upgrade/degrade function in the bootmenu to emu
  4. Ahh, another one bites the dust. I can't help you sorry, maybe someone else can. Warning for the future or other users: RDM does not pass SMART data along so XPenology can never know when a disk is failing. Set it up in ESXi or use passthrough. I have taken the disks and connected them directly to another PC. There's nothing wrong with them and the data is still there. I think this is a logical problem that somehow DSM has corrupted the partition table or something similar to that. We can argue all day about the use of RDM but Nindustries provides no real alternative as using an
  5. In hyper-V I suggest you use the ISO version of nanoboot instead of the IMG/VHD as the boot device. Just replace your IDE(0:0) boot hard drive with an IDE(0:0) CD/DVD, you won't have to do a reinstall or anything. DSM seems to always pick up the spare space in the boot drive that's why you are seeing the 2MB drive. With a CD/DVD it won't show up. If you need to modify the ISO image file you can use Winiso 5.3 it's free.
  6. In step 2 of my guide where you modify the IMG file so the boot drive doesn't show up you can also change the serial number there. There's a line that has SN= that's the serial number. Change to one you like but please backup your settings first in DSM as I believe you may lose some share permissions if you change SN as DSM now thinks it's a different unit.
  7. I have a similar setup to yours and noticed the same slower transfer speed in ESXi. I mentioned it in this thread http://xpenology.com/forum/viewtopic.php?f=2&t=3191. When I have time this weekend I will do some tests under ESXi and see if speed can improve. I think it's a driver issue (setting) with ESXi and I hope to figure it out as ESXi hosts is way easier to manage then Hyper-V Server.
  8. I'll try to answer your questions the best I can, since I am not an expert. Your first question regarding using virtual RDM and why I suggest using it instead of a virtual disk (vmdk). Besides getting better speed you get portability of your data. This means you can take your hard drives and put it in a real Synology DSM and your data will still work, or you can put the drives in a Hyper-V environment and your data will still be there. I have personally tested Hyper-V so I know it works. The reason it works is because if you use RDM you are letting the DiskStation software have direct acce
  9. Click on the + before Network Adapter to expand the advance settings.
  10. Is your VM setup to use "Legacy Network Adapter"? If that's the case that would explain your 10MB/s speed and not seeing the VMQ setting. If you use the regular "Network Adapter" you should see and extra "Hardware Acceleration" option like this: From my searching around VMQ can be beneficial in some configuration and in some usage scenario but in my particular system running Nanoboot it was causing problems.
  11. Poechi's link pretty much covers how to install Nanoboot on Hyper-V whether you are using Windows 8 w/Hyper-V, Windows Server w/Hyper-V, or pure Hyper-V server. The only difference is with Hyper-V server there is no GUI you have to set it up via the command line. Once it's setup though you can remotely manage the server using RSAT on a Windows 8 machine. This Guide here pretty much tells you how to do all the command line stuff so you can manage it using a GUI on another machine. Just remember Hyper-V Server 2012 requires Windows 8 or Windows 8.1 to manage, and Hyper-V Server 2012 R2 requires
  12. I wasn't getting great speed's with ESXi 5.5, it was erratic usually fluctuating between 20-80 MB/s using virtual RDM and E1000 network. I have a feeling it's the network drivers or some settings in it that wasn't correct. Anyways to test my theory I decided to duplicate the setup on Hyper-V Server 2012 R2... this was easy to do as I had my ESXi booted off a USB stick (but Datastore on an SSD) and Hyper-V booting off an SSD. Since I didn't use virtual drives for my data the only drive I had to convert to VHD format was my 32GB virtual drive for application. Once I created the Hyper-V VM and
  13. I tried and and trashed it after didn't finished indexing in 48h. And my collection was rather small at that time Nevertheless, let's stop whining and check what this man has to say about our proposals If you have "Generate media index files during scans" enabled it will take a long time (probably more then 48 hours depending on the type of machine you have. This is different then a regular library scan which downloads the movie info and cover art. The media index actually goes through each video and generates thumbnails at various times so on players that support it you will see t
  14. Are you saying you're only getting 10 mb/s = 1 MB/s transfer speed? That doesn't sound right. If you mean you are getting 10 MB/s transfer speed then check your network adapter setting it probably means it's set to 100 mb/s instead of Gigabit speed. Also in the virtual network adapter setting disable VMQ (Virtual Machine Queuing) it seems to slow down or make the network transfer erratic. I was getting around 25 MB/s with VMQ enable now I'm getting this: Not bad for 5400 rpm drives in SHR. I was never able to achieve that kind of speed when running ESXi (erratic 20-80 MB/s) which mad
  15. We need to know how your system is setup, especially the Physical Network Port. If you setup the port to only allow internal connections that will explain why you don't have internet access.