LoliveT1

Update 5.1 5004 error

Recommended Posts

Hello,

 

I am installing my first NAS on a Proliant N54L, and I have newbie questions.

 

Fisrt of all, I have followed the tutorial here.

 

1 / The check box for creating SHR volume was checked : after install the system start a verification of the HDD.

But I never manage to apply the update 5.1 5004 as explained (neither manual or auto), I get an error message "temporary directory access error"

As I thought the verification could be the problem, I stopped it, without better success for update.

 

How could I apply this update ?

 

2 / At the step of creating the volume, I didn't get the choices as said in the tutorial, the system indicate a volume already created and ok.

Should I need to delete the volume, and start a full creation with the verification HDD complete ?

 

3 / And last question, how to connect to my NAS from Openelec : I have read differents share option (NFS, Webdav) but I don't know which is the best way.

 

Many thanks for your help.

 

Edit : I have read not to install this update 5.1 5004. So I just need to install the update 5.0 4528 (2). How to solve this error message in order to apply the update ?

Share this post


Link to post
Share on other sites

Ok, that's what I have read after my post.

And also all the bugs with this update.

 

But I am still unable to apply the update 5.0 4528 (2) due to error message about the temporary directory.

 

And about my others interrogations, any idea ?

Share this post


Link to post
Share on other sites

Are you using the SED method?

 

sed 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info> /autoupd@te.info1
mv /autoupd@te.info1 /autoupd@te.info

 

If you create a user task you can run it manually the next time you need to apply a minor update.

Share this post


Link to post
Share on other sites
Ok, that's what I have read after my post.

And also all the bugs with this update.

 

But I am still unable to apply the update 5.0 4528 (2) due to error message about the temporary directory.

 

And about my others interrogations, any idea ?

 

for new user, those steps maybe critical

 

following the steps in this thread, post#1

http://xpenology.com/forum/viewtopic.php?f=15&t=2999

Share this post


Link to post
Share on other sites
Are you using the SED method?

 

sed 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info> /autoupd@te.info1
mv /autoupd@te.info1 /autoupd@te.info

 

If you create a user task you can run it manually the next time you need to apply a minor update.

I don't know waht is the SED method, but it the same step in the tutorial I have followed.

The command lines in SSH don't work : no such file or directory.

 

ad911 : the thread show the same steps I have followed in the tutorial.

 

I made the installation with version 5.0 4493.

But unable to update to 5.0 4528 (2).

 

Do I need to remake the complete install, directly from DSM 5.0 4528 (boot image and install complete), applying update 2, and to let the HDD verification finishing before creating the volume ?

Do I need to delete the volume before ?

Share this post


Link to post
Share on other sites

The command lines in SSH don't work : no such file or directory.

 

 

It does work, you have to goto the next step before sending the command :smile:

Share this post


Link to post
Share on other sites

The command lines in SSH don't work : no such file or directory.

 

 

It does work, you have to goto the next step before sending the command :smile:

:?: Sorry, I don't understand : which next step before sending the ssh command ?

Next step is applying the update once the ssh command done ...

Share this post


Link to post
Share on other sites

Are you loging in as root or as admin. If you log in as admin you will get this error. You have to log in as root to make it work. The password ought to be the same as for admin.

Share this post


Link to post
Share on other sites

I have tried the two methods : download the update files (auto update), and select the .pat file (manual update), without any success in both cases.

I am not at home today and this week-end, so I can't try anything.

Share this post


Link to post
Share on other sites

Hi all,

 

I have exactly the same problem as above

Installed on Baremetal

First installed 4528, then after testing update1, runs ok

Update 2 wont run, ik have followed the dutch http://www.xpenology.nl/installation-ds ... -update-2/ installation help

 

so upload the pat file, wait for DSM finisch the upload

Then login SSH as root

pasting the first sed command gives me the error.

Share this post


Link to post
Share on other sites

And this command also fails?

sed -i 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info

 

I've just used this command today to upgrade my N54L from 4493U7 to 4528U2 without any problems.

Share this post


Link to post
Share on other sites

Why are we helping this guy to install an update that won't work?

 

OP, don't go to 5.1 yet, stick with 5.0. We need an update nanoboot to get the latest version to work.

Share this post


Link to post
Share on other sites

Just realized something - are you trying to do a Synology upgrade from 4493 to 4528? In that case you have to follow the migration method. You won't loose any data or settings when migrating from 4493 to 4528 - at least I didn't. :smile:

The "SED thing" is ONLY when applying an update within the same version, 4528 -> 4528 update 2. The same version but a minor update.

Share this post


Link to post
Share on other sites
Just realized something - are you trying to do a Synology upgrade from 4493 to 4528? In that case you have to follow the migration method. You won't loose any data or settings when migrating from 4493 to 4528 - at least I didn't. :smile:

The "SED thing" is ONLY when applying an update within the same version, 4528 -> 4528 update 2. The same version but a minor update.

Great, I think that's the answer !!

I have followed the tutorial, but it didn't explain the difference between update and migration.

As in auto update, it only propose 5.1 5004, it never works.

So I will try this evening migration to 4528, then 4528 update2.

 

And about my others questions :

2 / At the step of creating the volume, I didn't get the choices as said in the tutorial, the system indicate a volume already created and ok.

Should I need to delete the volume, and start a full creation with the verification HDD complete ?

 

3 / And last question, how to connect to my NAS from Openelec : I have read differents share option (NFS, Webdav) but I don't know which is the best way.

Share this post


Link to post
Share on other sites

And about my others questions :

2 / At the step of creating the volume, I didn't get the choices as said in the tutorial, the system indicate a volume already created and ok.

Should I need to delete the volume, and start a full creation with the verification HDD complete ?

No need to delete the volume just to recreate it. :wink:

 

I can't answer your 3. question. :???:

Share this post


Link to post
Share on other sites

No need to delete the volume just to recreate it. :wink:

 

I can't answer your 3. question. :???:

Ok, but I don't have the option to recreate it ...

In the volume window, I can only delete the selected volume.

 

I have seen you have 4To HDD in your Proliant N54L. I believed the Proliant could only use 2 or 3 To HDD ?

Share this post


Link to post
Share on other sites

I have migrate to 5.0 4528.

But impossible to update 4528 update 2.

I am connected with SSH as root.

The command line SED gives an error message : no such file or directory

 

Still the same problem

Share this post


Link to post
Share on other sites

rather than the SSH login I tried the alternative and built a task using the same command string. No need to login as SSH, just execute task through scheduler

Share this post


Link to post
Share on other sites

OK, I have found an answer in the comments here http://www.xpenology.nl/installation-ds ... -update-2/

 

I need to force the auto MAJ by settings the MAJ to keep the actual DSM.

The system propose to download 4528 Update 2 (instead of 5.1 5004)

Then the SSH command lines works now because the download create this famous directory.

 

I manage to apply the 4528 Update 2.

Edited by Guest

Share this post


Link to post
Share on other sites

This is what i see in the logs:

 

Nov 19 01:09:29 NAS2 entry.cgi_SYNO.Core.Upgrade[1].start[32691]: Upgrade.cpp:225 Verify checksum of [//upd@te]...

Nov 19 01:09:30 NAS2 entry.cgi_SYNO.Core.Upgrade[1].start[32691]: Upgrade.cpp:230 Pass checksum of //upd@te...

Nov 19 01:09:30 NAS2 entry.cgi_SYNO.Core.Upgrade[1].start[32691]: Upgrade.cpp:306 Executing [//upd@te/updater -v / -x > /dev/null 2>&1]

Nov 19 01:09:30 NAS2 updater: updater.c:5011 Start of the updater...

Nov 19 01:09:30 NAS2 updater: updater.c:5120 This is X86 platform

Nov 19 01:09:30 NAS2 updater: updater.c:5123 ==== Start flash update ====

Nov 19 01:09:30 NAS2 updater: updater.c:5135 The SynoBoot partitions exist.

Nov 19 01:09:30 NAS2 updater: updater.c:2406 orgBuildNumber = 4528, newBuildNumber=5004

Nov 19 01:09:30 NAS2 updater: updater.c:2494 [CheckPackageSize] Find [1] internal volume, external volume count= [0]

Nov 19 01:09:30 NAS2 updater: updater.c:2511 CheckPackageSize, err=0

Nov 19 01:09:30 NAS2 updater: updater.c:3176 SYNORedBootUpdCheckAndApply(3176): Skip bootloader update, no uboot_do_upd.sh exists

Nov 19 01:09:30 NAS2 updater: updater.c:354 fail to backup images. cp -f /tmp/bootmnt/rd.gz //synob@ckup

Nov 19 01:09:30 NAS2 updater: updater.c:493 checksum geneterated by [/bin/grep -i zImage checksum.syno >> /tmp/checksum.syno.tmp]

Nov 19 01:09:30 NAS2 updater: updater.c:512 file [zImage] is being copied to [/tmp/bootmnt]

Nov 19 01:09:30 NAS2 updater: updater.c:520 file [/tmp/bootmnt/zImage] process done.

Nov 19 01:09:30 NAS2 updater: updater.c:493 checksum geneterated by [/bin/grep -i rd.gz checksum.syno >> /tmp/checksum.syno.tmp]

Nov 19 01:09:30 NAS2 updater: updater.c:512 file [rd.gz] is being copied to [/tmp/bootmnt]

Nov 19 01:09:31 NAS2 updater: updater.c:520 file [/tmp/bootmnt/rd.gz] process done.

Nov 19 01:09:31 NAS2 updater: updater.c:493 checksum geneterated by [/bin/grep -i grub_cksum.syno checksum.syno >> /tmp/checksum.syno.tmp]

Nov 19 01:09:31 NAS2 updater: updater.c:512 file [grub_cksum.syno] is being copied to [/tmp/bootmnt]

Nov 19 01:09:31 NAS2 updater: updater.c:520 file [/tmp/bootmnt/grub_cksum.syno] process done.

Nov 19 01:09:31 NAS2 updater: updater.c:507 file [/tmp/bootmnt/hda1.tgz] is being removed

Nov 19 01:09:31 NAS2 updater: updater.c:520 file [/tmp/bootmnt/hda1.tgz] process done.

Nov 19 01:09:31 NAS2 updater: updater.c:507 file [/tmp/bootmnt/updater] is being removed

Nov 19 01:09:31 NAS2 updater: updater.c:520 file [/tmp/bootmnt/updater] process done.

Nov 19 01:09:31 NAS2 updater: updater.c:507 file [/tmp/bootmnt/VERSION] is being removed

Nov 19 01:09:31 NAS2 updater: updater.c:520 file [/tmp/bootmnt/VERSION] process done.

Nov 19 01:09:31 NAS2 updater: updater.c:530 checksum file updated by [/bin/cp -f /tmp/checksum.syno.tmp /tmp/bootmnt/checksum.syno]

Nov 19 01:09:39 NAS2 updater: updater.c:1136 GRUB upgrade needed file does not exist

Nov 19 01:09:39 NAS2 updater: updater.c:1516 Kernel Version: 3.2.40

Nov 19 01:09:39 NAS2 updater: updater.c:1596 failed to get old BIOS version

Nov 19 01:09:39 NAS2 updater: updater.c:5373 fail to upgrade BIOS

Nov 19 01:09:39 NAS2 updater: updater.c:610 Restoring [zImage]

Nov 19 01:09:39 NAS2 updater: updater.c:621 Copying file [//synob@ckup/zImage] as [/tmp/bootmnt/zImage], result[0]

Nov 19 01:09:39 NAS2 updater: updater.c:610 Restoring [rd.gz]

Nov 19 01:09:39 NAS2 updater: updater.c:624 Removing file [/tmp/bootmnt/rd.gz], result[0]

Nov 19 01:09:39 NAS2 updater: updater.c:607 Skip restoring [vendor]

Nov 19 01:09:39 NAS2 updater: updater.c:610 Restoring [grub_cksum.syno]

Nov 19 01:09:39 NAS2 updater: updater.c:624 Removing file [/tmp/bootmnt/grub_cksum.syno], result[0]

Nov 19 01:09:39 NAS2 updater: updater.c:610 Restoring [hda1.tgz]

Nov 19 01:09:39 NAS2 updater: updater.c:624 Removing file [/tmp/bootmnt/hda1.tgz], result[-1]

Nov 19 01:09:39 NAS2 updater: updater.c:628 Restore [hda1.tgz] fail, remove it from synoboot

Nov 19 01:09:39 NAS2 updater: updater.c:610 Restoring [updater]

Nov 19 01:09:39 NAS2 updater: updater.c:624 Removing file [/tmp/bootmnt/updater], result[-1]

Nov 19 01:09:39 NAS2 updater: updater.c:628 Restore [updater] fail, remove it from synoboot

Nov 19 01:09:39 NAS2 updater: updater.c:610 Restoring [VERSION]

Nov 19 01:09:39 NAS2 updater: updater.c:624 Removing file [/tmp/bootmnt/VERSION], result[-1]

Nov 19 01:09:39 NAS2 updater: updater.c:628 Restore [VERSION] fail, remove it from synoboot

Nov 19 01:09:39 NAS2 updater: updater.c:610 Restoring [checksum.syno]

Nov 19 01:09:39 NAS2 updater: updater.c:624 Removing file [/tmp/bootmnt/checksum.syno], result[0]

Nov 19 01:09:39 NAS2 updater: updater.c:5675 fail to rollback flash (restore)

Nov 19 01:09:39 NAS2 updater: updater.c:5711 Failed to accomplish the update! (errno = 21)

Nov 19 01:09:39 NAS2 entry.cgi_SYNO.Core.Upgrade[1].start[32691]: Upgrade.cpp:309 failed to system cmd=[//upd@te/updater -v / -x > /dev/null 2>&1], r=5376

Nov 19 01:09:39 NAS2 entry.cgi_SYNO.Core.Upgrade[1].start[32691]: Upgrade.cpp:478 Failed to unpack firmware.

Nov 19 01:09:41 NAS2 synoimgbkptool: (926) [err] network.cpp:19 lookup[]: [0x1000 net_sep_ip.c:27]

Nov 19 01:09:41 NAS2 synoimgbkptool: (932) [err] network.cpp:19 lookup[]: [0x1000 net_sep_ip.c:27]

Nov 19 01:09:42 NAS2 avahi-daemon[485]: Failed to add service 'NAS2' of type '_http._tcp', ignoring service group (/usr/syno/avahi/services/http.service): Invalid record

Nov 19 01:09:42 NAS2 avahi-daemon[1093]: Failed to add service 'NAS2' of type '_http._tcp', ignoring service group (/usr/syno/avahi/services/http.service): Invalid record

Nov 19 01:09:43 NAS2 CUPS: Starting cupsd...

Nov 19 01:09:43 NAS2 cupsd[1344]: [conf.c:1893] Filter "pstoraster" not found.

Nov 19 01:09:43 NAS2 avahi-daemon[1198]: Failed to add service 'NAS2' of type '_http._tcp', ignoring service group (/usr/syno/avahi/services/http.service): Invalid record

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