Franks4fingers

Members
  • Content Count

    26
  • Joined

  • Last visited

Everything posted by Franks4fingers

  1. All good.......it was just a thought to try and prevent people getting annoyed with others who have possibly missed something in the preceding pages. There are a lot of eyes awaiting the beta release. Me included!
  2. Hey all This thread is indeed HUUUUGE and to read through the lot (which I have done as I have been following since its inception), is a massively tall order. Would there be any value in having a separate, locked thread (apart from the key contributors), whereby some of the gold nuggets of info could be documented and referenced for everyone who may have arrived to the party quite late??? Just a thought and happy to be shot down if it's not a beneficial thing to look at. Cheers and keep up the outstanding work to those with the skills to do so.
  3. Did you upgrade from a previous version of 6.* or a fresh install straight to 7? What steps did you follow to get to 7 (whichever way you achieved that)?
  4. Whilst you mention this fixed things up for ESXi, does anyone know if its a similar process / requirement for Proxmox? I am going to be using Proxmox for the first time (ever) on a test PC that I have so knowing the key pieces would be great. Great work from all involved in getting things this far
  5. Can I ask what you are backing up to, how you are backing it up and is it everything on your NAS including (potentially) music, movies, pics, TV etc etc or just the main OS install and associated config?
  6. I am looking to given Proxmox a run out and jump from baremetal to virtual. This will be my first foray into running Xpenology on virtual. Does anyone have any links to good tutorials that can be followed on the best options to use for configuring things from the outset?
  7. "it means the boot device is not properly mounted. in that case you should share again the boot device, config, check pid/vid and grub config, etc." So basically its a case of trial and error with a USB stick and then re-burning the image and then trying a different USB port each time perhaps?
  8. @pocopicoIt looks like I do not have synoboot in the directory structure. Any ideas how I rectify that?
  9. Got there in the end. Just working out the rest now....Linux isn't my strong point.
  10. @pocopico - I can telnet to the box and have managed to get in with root. I will see what I can find.
  11. I used USB Device View from the Xpenology Tool V1.4.2 toolbox. I also looked in the properties via my Surface and the only difference I see is that the VID there is all upper case......does that make a difference given USB Device View gives it in lower case? This is my grub.cfg as well that is on the only available partition that Windows can see now the img has been burnt. # GRUB 2 config file terminal_output console if serial --unit=0 --speed=115200; then terminal_input --append serial_com0 terminal_output --append seria
  12. Using putty I am able to telnet to the diskstation and I am prompted for a username and password. Anyone know what the default is for telnet?
  13. I have checked and re-checked, used a different USB key and changed the PID / VID based on what that reported and it still hits 56% and then bombs out.
  14. I am still plagued with the issue of hitting 56% and then the install bombing out with the error message of: Failed to Install DSM. Failed to install the file. The file is probably corrupted. I have tried a different USB key and changed over the PID and VID accordingly to see if that made a difference but no joy. Does it make a difference if I choose UEFI boot or Legacy Boot within the BIOS? Are there any other specific BIOS settings that could be causing the continual failure and could be worth changing? When I now try the in
  15. I have made progress in being able to get past the SATA disk error so thanks to those prior forum members who have helped so far. I now get stuck at the 55 / 56% mark as others have when trying to install the pat file onto a new baremetal install (Dell Optiplex 9020 i5 4570 installing DS918+ 42214.pat) I recall seeing something about this on prior pages but can anyone point me in the right direction to try not to read 45 pages of history? A search on 55% / 56% didn't throw anything up for me. Thanks
  16. Do you have the link for the .pat file that you used for the fresh install?
  17. That line in my grub.cfg file is as follows: linux /zImage netif_num=1 earlycon=uart8250,io,0x3f8,115200n8 syno_hdd_powerup_seq=1 syno_hdd_detect=0 elevator=elevator root=/dev/md0 loglevel=15 log_buf_len=32M mac1=123456789012 vid=0x0781 pid=0x5572 console=ttyS0,115200n8 sn=xxxxxxxxxxxxx earlyprintk syno_port_thaw=1 HddHotplug=0 withefi syno_hw_version=DS918+ vender_format_version=2 Did you add the DiskIdxMap= SataPortMap= SasIdxMap= values to the end of that line? Also, how did you derive what the SataPortMap value needed to be? Cheers for the h
  18. My spare baremetal PC (Optiplex 9020 SFF) starts the boot from USB and gets stuck at the Booting Kernel message. I can then find the device from my laptop by either using find.synology.com or the IP address. The issue I have from there is that I get the error message that others appear to have had. We've detected an error on the hard drives (3,4,5,6) and the SATA ports have also been disabled. I have tried this using both UEFI and Legacy boot from within the BIOS and get the same issue. Does anyone have any tips to get past this point?
  19. Can you clarify the following please when mounting this img using osfmount........ Is it only the first partition that contains the appropriate grub.cfg file that needs to be adjusted to match PID / VID / SN / MAC and that the location for the grub file is \boot\grub? Or is there another file located elsewhere that I need to enter this detail into? Cheers
  20. Can I ask a quick q on this please. What OS were you using to craft the image in the first place and get your loader operating successfully? I have a spare Optiplex 9020 that I am thinking to re-purpose for this instead of using my windows based surface. It would be convenient to re-purpose as the Optiplex has the same hardware in it that my actual Prod Xpenology NAS is running as I secured 2 of them when work was relocating. I would be planning to use it as a dual purpose test bed. Jun's loader worked with no issues on that hardware and the OS comes up as a 918+. From
  21. Does that mean you are running Plex Server on the Shield and Xpenology is just serving the storage side of things?