steve23094

How do I recover from a failed update?

Recommended Posts

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.

Edited by steve23094

Share this post


Link to post
Share on other sites

I would first disconnect your raid drives to avoid data corruption

Then test your hardware will boot with a live ubuntu image to make sure its all ok.

You might need to reset the bios to defaults and then setup again for XPE boot disk

Test your XPE boot disk works and you can find the diskstation

If that all works then your hardware should be working ok.

However your XPE boot disk will be out of sync with your installed version so;

Use a spare HDD -  boot XPE and install DSM6.1, then go though the updates to 6.1.4 U5, that will update your boot disk to match the DSM on your raid drives.

Then you can shutdown, disconnect the spare hdd, reconnect your raid and boot up

 

Share this post


Link to post
Share on other sites

Sounds like you have video output from the box and if I understand you you get the normal BIOS output but you do not see the normal output from booting the stick, e.g., you should see the menu, and after a few seconds, the screen should post a few lines of text indicating it's begun booting and then nothing more will appear there.

 

If you are not getting that output then find.synology.com won't work.

 

Rebuilding the stick may have caused a problem if you were not careful to rebuild the grub.cfg with the correct vid, pid, SN and possibly mac. Building the stick on a mac is simpler than on a Windows machine, simply 

 

sudo dd if=/path/to/102b.img of=/dev/disk3 bs=1m

 

in terminal. determine the correct /dev/disk3 path using diskutil list. Your USB stick will be /dev/diskN.

 

Then you need to mount the EFI folder of the stick, edit grub.cfg, set the vid/pid/SN/mac, unmount and done. 

 

So that should be your focus, getting the system to display the right text on boot.

Share this post


Link to post
Share on other sites
9 minutes ago, sbv3000 said:

I would first disconnect your raid drives to avoid data corruption

Then test your hardware will boot with a live ubuntu image to make sure its all ok.

You might need to reset the bios to defaults and then setup again for XPE boot disk

Test your XPE boot disk works and you can find the diskstation

If that all works then your hardware should be working ok.

However your XPE boot disk will be out of sync with your installed version so;

Use a spare HDD -  boot XPE and install DSM6.1, then go though the updates to 6.1.4 U5, that will update your boot disk to match the DSM on your raid drives.

Then you can shutdown, disconnect the spare hdd, reconnect your raid and boot up

 

 

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.

Share this post


Link to post
Share on other sites
19 minutes ago, steve23094 said:

 

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.

You could also try a serial connection for diagnostic output (assuming you can somehow connect serial from the mac)

once you resolve the boot issue and can find the nas on the lan then you may also find its 'migratable' (rather than needing to get the boot usb to the same version) you may be able to reinstall the DSM version that matches the boot disk then once you are reinstalled you can update to 6.1 4 again.

Share this post


Link to post
Share on other sites
14 hours ago, aol said:

Sounds like you have video output from the box and if I understand you you get the normal BIOS output but you do not see the normal output from booting the stick, e.g., you should see the menu, and after a few seconds, the screen should post a few lines of text indicating it's begun booting and then nothing more will appear there.

 

If you are not getting that output then find.synology.com won't work.

 

Rebuilding the stick may have caused a problem if you were not careful to rebuild the grub.cfg with the correct vid, pid, SN and possibly mac. Building the stick on a mac is simpler than on a Windows machine, simply 

 

sudo dd if=/path/to/102b.img of=/dev/disk3 bs=1m

 

in terminal. determine the correct /dev/disk3 path using diskutil list. Your USB stick will be /dev/diskN.

 

Then you need to mount the EFI folder of the stick, edit grub.cfg, set the vid/pid/SN/mac, unmount and done. 

 

So that should be your focus, getting the system to display the right text on boot.

 

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'


 

Share this post


Link to post
Share on other sites
13 hours ago, steve23094 said:

 

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'


 

that all looks 'ok' so in theory...

as a test, try a fresh image but only change the vid/pid, ie leave the default s/n and mac, see it boots and is findable

Share this post


Link to post
Share on other sites

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?

Share this post


Link to post
Share on other sites

Great news. Curious what you think was the thing that got you going?

 

As far as the next step, I would think if SynoOS says the array is recoverable then you'll be fine, but I would understand you wanting to get a second opinion. Keep in mind the SynoOS files, and the data in the RAID array, are separate. You can migrate the SynoOS (e.g. from a DS3615xs to a 3617xs model) and the data won't change, just the SynoOS will need to know what sort of RAID array it's working with (this is migrating, the same thing as if you physically moved the drives in one NAS box to another NAS box). I would think recoverable is between healthy and migratable, that is, less work will need to be done to get your data back, but I could certainly be wrong. Anyway my vote is to trust SynoOS, if it says your data is recoverable and it will let you click a button to recover it, then that's probably the right thing to do.

Share this post


Link to post
Share on other sites

When I had simialr problem, I successfully made this with NO STORED DATA LOSS:
 

1) Disconnect all the drives
2) Run the jun's loader as reinstall
3) Find device by find.synology.com or Assistant - there were no drives in the system.
4) Leave browser's Synology page opened, do not shut down device.
5) Plug disks back in (no matter, if the machine supports hotswap or not)
6) After a few minutes repeatedly refresh Synology's page (see step 4)
7) After succesfuly loaded installation page reinstall system. Do not forget to check manual upgardes only.

Notes:
a) Stored files will be kept untouched, but apps, settings and other data will be removed.
   Settings can be restored via previously saved ones.
b) If reinstallation crashes, reset your device and go through standard "1st time" instalation process.
   It should go now, because the OS's partition is formated allready by step 7)

Note: This is not 100% my own know-how, but I do not remeber its source, sorry.
I just modified it a bit.
 

Note 2:
Make sure, your HW is OK. I also tested NAS disks separately for their health. After that I tested functionality of HW with two another disks by fresh XPE install.
Then I used proceeding mentioned above.

Edited by Fireball

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

This looks to me like a USB issue or simply a file corruption in the loader during the computer reboot. USB keys are not the most reliable devices that's why I chose high-end usb keys for bootloaders. I never use el cheapo usb keys or free usb keys you get in events. I have probably over 30 of those laying around but only use them for testing purposes and non-critical applications. Even high-end usb keys may in certain events go bad.

Share this post


Link to post
Share on other sites
49 minutes ago, Polanskiman said:

This looks to me like a USB issue or simply a file corruption in the loader during the computer reboot. USB keys are not the most reliable devices that's why I chose high-end usb keys for bootloaders. I never use el cheapo usb keys or free usb keys you get in events. I have probably over 30 of those laying around but only use them for testing purposes and non-critical applications. Even high-end usb keys may in certain events go bad.

 

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

Share this post


Link to post
Share on other sites
10 hours ago, steve23094 said:

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.

thats good news

if you dont do so already, I'd setup an 'external' backup of your critical data, usb drive, a cloud service etc 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now