steve23094

Members
  • Content count

    12
  • Joined

  • Last visited

Community Reputation

1 Neutral

About steve23094

  • Rank
    Newbie

Recent Profile Visitors

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

  1. steve23094

    How do I recover from a failed update?

    It’s a Sandisk. I’ll look into getting another one just in case.
  2. steve23094

    How do I recover from a failed update?

    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.
  3. steve23094

    How do I recover from a failed update?

    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?
  4. steve23094

    How do I recover from a failed update?

    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'
  5. steve23094

    How do I recover from a failed update?

    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.
  6. steve23094

    DSM 6.1.4-15217 Update 5

    - 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.
  7. steve23094

    How do I recover from a failed update?

    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.
  8. I'm wondering whether the serial number I sourced is wrong. What is the correct place to get them from now?
  9. So I recently upgraded my bare metal box to 6.1.3 running the DS3615xs profile. Everything seems to be operating okay but in the info section of DSM the serial number is blank, should it be? I seem to remember my previous version had a serial number present. I'm using the native MAC address of my NIC. I have edited the grub.cfg file and included a serial number generated from here:- https://xpenology.github.io/serial_generator/serial_generator_new.html (Just as an aside, is there an easy way to access the grub.cfg file through the NAS? Unplugging it and mounting it into macOS is a bit of a pain).
  10. I was right. You're no longer allowed to write to /Volumes. For anybody else: Change the reference from Volumes to another folder. I used /tmp e.g. mkdir /tmp/efi and sudo mount -t msdos /dev/disk2s1 /tmp/efi
  11. Quote from Polanskiman Hide Hello, This doesn't work. I presume you have to rename the loader file to synoboot.img because they are named as DS3617xs 6.1 Jun's Mod V1.02b etc. I did that. The problem is the mkdir /Volumes/efi step. It results in a Permission denied. I'm running macOS 10.12.6. I think you have tried to create a directory where it's no longer allowed. Thank you.