steve23094

Members
  • Content Count

    20
  • Joined

  • Last visited

Community Reputation

1 Neutral

About steve23094

  • Rank
    Junior Member

Recent Profile Visitors

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

  1. Thanks for your reply. i found a post here from someone that said they had 6.2 running with an i219. Maybe it was a typo. Nevertheless I have tried to roll back with the same result. So something else is going on.
  2. Thank you for your reply. There is no link to a PAT in the 6.2 loader thread. However, I have tried both 6.2 and 6.2.1. I have tried to rollback using both 3615 and 918. I have tried deleting the system partitions, mentioned in my original post. TBH. I have almost given up because I’m not getting any help here. I’m considering buying a 918+. My only concerns with that is the disks are encrypted, I assume that shouldn’t cause a problem otherwise nobody would ever be able to migrate in that situation. But I don’t know what order my disks are in and I know you have to install them in the correct order. Obviously I can’t boot into DSM to check. I might not have installed them in order by SATA connector on my motherboard, because of cabling issues in my case. What happens if I install the disks in the wrong order? Does it destroy your array? Or do you get the opportunity to swap them around?
  3. God damn it. I have tried to roll back to 6.1 and 6.1.7 and keep getting 'The file is probably corrupted'. I now have a bricked system. Can nobody help?
  4. steve23094

    DSM 6.2 Loader

    Any chance somebody can please take a quick look at my thread here? https://xpenology.com/forum/topic/14255-failed-to-install-file-the-file-is-probably-corrupted/ I’m stuck on an install and would really appreciate some guidance. Thanks in advance.
  5. I’m really hoping someone can help out with this as to what I can try next, because right now I have a hosed system.
  6. Just an extra bit of info I mistakenly left out. My CPU is an Intel i3-6300T, which is Skylake.
  7. So I have been trying to migrate from a DS3615XS with Jun's loader 1.02b to DS918+ and Jun's loader 1.04b. I have a baremetal Asus Z170M Plus which has an Intel I219V NIC. Posts by other users say that this is a compatible NIC. My NAS is being picked up by the Synology app and web service, it is listed as a 918 and migratable, Jun's loader appears to load fine. I have tried using a manual install of PAT 6.2 and 6.21. I am getting the error message, 'Failed to install file. The file is probably corrupted (13)'. I know this is often an error in your PID or VID so I have attached screenshots of my PID/VID and Grub file. I have also tried downloading the latest PAT direct to the device, and receive an error message, 'Failed to download the DSM installation file. Please check the network connection and try again (46)'. I think there might be a clue here. Right now I have probably blown away my DSM installation, I was getting desperate so I tried a fresh DSM install migration (formatting DSM, but keeping your data).
  8. All this divergence is getting confusing. I’m running a 3615, bare metal, 6.1.7, with i3 6300t Skylake, EFI boot. Am I better waiting until everything sorts itself out into one loader? Or maybe Change my system from 3615 to 918?
  9. It’s a Sandisk. I’ll look into getting another one just in case.
  10. I don't really know tbh. I'm just relieved it came back to life. Perhaps it's an indication my USB key is failing? I selected to recover and everything sprung back to life. All my settings and data was intact, DSM now running 6.1.4-15217 Update 5. I breathed a big sigh of relief.
  11. So some good news. I have managed to get the text from the loader up on screen. The server is discoverable from the app and the web assistant. In the web assistant the server says 'Recoverable'. I'm a bit nervous about what to do now my versions are out of sync so I don't screw anything up. What is the best next step to take?
  12. I have rebuilt my USB stick (fourth time). This is the content of my grub.cfg file: set vid=0x0781 set pid=0x5583 set sn=1130LWN018623 set mac1=1CB72CAFA20D set rootdev=/dev/md0 set netif_num=1 set extra_args_3615='' 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 syno_port_thaw=1' set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=1 SasIdxMap=0' set default='0' set timeout='4' set fallback='1'
  13. I can boot okay with a Live Ubuntu image. The XPE boot disk is the problem, I’m not getting any text. I don’t have a spare disk lying around, so I’m not sure how I can fix the out of sync problem.
  14. - Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.1.4 15217 - Update 3 - Loader version and model: Jun's Loader v1.02b - DS3615xs - Installation type: Baremetal (Asus Z170M Plus) - Additional comments: Hosed my system. More details here: EDIT by Polanskiman: issue has been resolved. Problem was unrelated to the update but rather to the USB key.
  15. Hi, I was running DSM 6.1.4-15217 Update 3 with Jun's 1.02b loader. Everything was operating fine until I tried to upgrade to Update 5 via the web interface. Now my server won't boot. The upgrade appeared to go okay but on reboot my Xpenology server wouldn't start up. I'm running on bare metal on an Asus Z170M Plus m/board. I tried re-imaging my USB key again and it still won't boot. My BIOS splash screen shows up but the text that is normally displayed with the loader doesn't. Synology Assistant app or web interface can't find the server. I'm running a Mac and don't have access to Windows. I'm using the method here to create my USB key, the same I used successfully previously. Thanks.