BillB

I'd like to add my thanks to Polanskiman and to those who have added their personal experiences by way of reassurance for those of us who don't have the knowledge to do it unaided. Your public-spirited work is appeciated. If it helps others in a similar situation, I upgraded my N54L from 5.2 to 6.13 and thence to update 8 (specifically 6.1.3-15152 Update 8) without any software issues. I disabled the C1E on the Bios before starting. (F10 on boot, bottom of screen) The whole process was quite quick and, although I didn't need it, yes I most certainly did a backup first. I set the MAC addresses in the boot stick setup described by Polanskiman and all my settings were retained just so. I did encounter two issues, both of which are already documented here: I needed to use a new USB stick - I got the 'file may be corrupted' report with a usb stick that had previously been OK but a fresh Verbatim 'store'n'go' worked fine (I used USBview to read the PID/VID). I appeared to have problems with no output to my monitor which turned out to be the Dsub on the rear of the N54l (This happened at my first attempt to update which was momentarily alarming!)- I only mention this as I saw someone else report a similar problem so there may possibly be a weakness with the connector on the N54L. Thanks to all

No, but there doesn't seem anything critical in update 8- but I suppose subsequent updates may well contain something important. Since Krnage succeeded it is clearly possible to apply the update. I tried a couple of downloads without any joy so presumably it fails some sort of check of the existing software. As it appears to do no harm attempting the update it should be possible to try a couple of ideas without risk...

I have a Gen7 N54L and it runs happily on DSM 6.0.2-8451 update 7 thanks to this thread. Emboldened by Vodka2014 (thanks!) I tried to update to Update 8 but although it runs to completion at 100% it then comes up with a 'Failed to update the file. The file is probably corrupt.' message and reverts to update 7. I'm not going to loose any sleep over this update, but I hope the information is of some help at least!

Can you tell me what (with 2 SATA disks attached on your N54L) value you used for "SataPortMap=xx"? Did you set it via the Append command or directly in the .CFG file on the ISO? It didn't arise- I had a working DSM 5.2 and I just used the stock values in the .CFG file: set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=1 SasIdxMap=0' All the setup values copied across from the earlier version without me having to intervene (or really think about them!) Hope that is of some help.

Well, it all behaves now thank you. Another Usb stick appeared to do the trick, but I can't be absoloutely certain nothing else changed so it could just be co-incidence. Anyway I appreciate the help. Incidentally, for the benefit of those following the same path, the subsequent upgrade to DSM 6.0.2-8451 Update 7 on my N56L seems to have gone without a hitch.

Thanks, I've checked and rechecked the VID/PID several times but I haven't tried reloading the Pat file so I'll give it a go and report back... And having doublechecked the VID/PID again and tried 3 downloads of the PAT file, exactly the same I'm afraid..... I'm off to find yet another USB stick just in case but, to be honest, I'm not too hopeful that is the cause.

First off, thanks to Jun, Polanskiman and all who have contributed to this. Its appreciated by someone who does not have the skills to achieve this for myself! I have had DSM 5.2 running fine on an N54L / 2x2TB disks booting from a USB stick for some time. I have followed the migrate procedure which works fine up to the “Failed to install the file. The file is probably corrupted . (13)” I’ve double checked that I have changed the PID and VIDs correctly – I’ve tried it with a couple of differnet USB sticks including one identical to the one used for the (still working) earlier version 5.2. I’ve since trawled this thread and Jun’s new loader thread to see if anyone else had encountered the same issue. Nothing found. I’m therefore working on the assumption I have missed something obvious- but I can’t for the life of me see what- has anyone been here before or can point me in the right direction? Thanks!