• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Franks4fingers

  • Rank
    Junior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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)?
  2. 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
  3. 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?
  4. 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?
  5. "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?
  6. @pocopicoIt looks like I do not have synoboot in the directory structure. Any ideas how I rectify that?
  7. Got there in the end. Just working out the rest now....Linux isn't my strong point.
  8. @pocopico - I can telnet to the box and have managed to get in with root. I will see what I can find.
  9. 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
  10. 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?
  11. 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.
  12. 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
  13. 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
  14. Do you have the link for the .pat file that you used for the fresh install?