bod
-
Posts
16 -
Joined
-
Last visited
Posts posted by bod
-
-
Can someone rename this thread title to BETA as it's misleading people (well those that can't be bothered to read the thread).
BETA BETA BETA BETA BETA..............................
-
More detail required. Bare metal? Virtual? Hardware?
-
That comment about taking risks... It's data we're talking about here. Taking risks is not in my dictionary in the case of data, and it shouldn't be in yours.
I'll give it a shot soon.
Wow - really missed the point. Not all data is equal so your comment is pointless.
Like I said - if you don't want to take risks then this is not the solution for you.
If you do like to take risks, and you backup your data (which you should be doing anyway), then go for it. I am just trying to stop people who mention "risk" in their post from taking a risk.
-
Yep - it's all in this forum already.
-
All the answers are in this forum and if they are not then what you decide to do is a risk. That's life - if you don't want risk then don't try it.
-
Control panel > Task Scheduler > Create > User defined script. Call it something like update script. User: root, and paste in this...
sed 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info> /autoupd@te.info1
mv /autoupd@te.info1 /autoupd@te.info
Now go to updates and download the update. DO NOT update yet. Go back to task scheduler, select the script you just created and press run. Then back to the update and update.
-
Do a search? There are many post on this already.
Can someone post a link tobit. Needs to be in english
All you needed to do was click on the English (Union Jack) flag for English.
-
Do a search? There are many post on this already.
-
1 - It won't transcode 1080p. You need either a much more powerful CPU or a DS415play which has a dedicated hardware decoder.
2 - If all you want is a NAS then just go with bare metal install. No harm in trying both - what you got to lose?
3 - No - if DSM is corrupted just re-install it. You should have a backup anyway of the files are that important.
4 - Highly unlikely to experience data loss in domestic situations due to power loss.
-
Please could you try setting up a Power Off / On in Task Scheduler and see if it changes the BIOS settings?
Can you confirm what BIOS it is? ie AMIBIOS.
Thanks
-
Did a lot more testing. Most success found with this BIOS...
http://www.hardwareluxx.de/community/f1 ... st21503128
If you don't touch Task Scheduler then my N54L keeps it's BIOS settings. As soon as you create a task and restart - BIOS is changed. Even if you use Advanced Power Management pack it changes the the BIOS.
"The Bays" BIOS gets changed no matter what.
The changes made to the BIOS in both cases most people won't probably even notice. Splash Screen gets re-enabled. After Power Loss gets set to Last State.
I even tried an old MSI motherboard (P35 Platinum - about 4 to 5 years old). This has a AMI BIOS and it too got changed - more significantly than the N54L it created checksum errors.
-
First off a big thanks Bod you are after saving me a fair amount of time here, I was just starting to plan out my own upgrade stumbled across your post which is pretty awesome so thanks for that!!
Question if you don't mind
Are you running Couchpotato or Sickbeard or any of those types packages by any chance?
If yes did they work after the upgrade?
If you aren't no problem thanks for the post all the same really helpful.
Gen
No - sorry - not running any of those packages.
-
Hi All,
Can someone in the forum agree with my theory:
All American Megatrend BIOS motherboards HAS NO problem on BIOS resetting,
after it has installed DSM 5.0 based the latest 64bit = DSM_DS3612xs_4493.pat software?
AH...HA!
Someone in the forum has discovered that American Megatrend BIOS motherboards has NO problem on BIOS resetting just like I predicted earlier.
Check out the link here: http://xpenology.com/forum/viewtopic.php?f=2&t=3508&p=21258#p21258
HP N54L with American Megatrend BIOS suffers with BIOS resetting. So AMIBIOS do suffer.
Now using DSM 5.0.4493 Update 3. Was using 4.2.3211 with same problem.
I have tried manual time update instead of NTP.
Disabled all DSM Tasks and Power Management.
Tried Nanoboot x86 and Nanoboot x64.
Changes BIOS every restart.
-
Backup YOUR Config - Backup YOUR Data - YOUR RESPONSIBILITY.
Thanks to all who spent their valued time creating files and previous documentation and hosting that has allowed me to do this.
I used this process on a bare system and an update from 4.2.3211 on two HP N54L. DS3612xs - x64 files.
***Install DSM5***
Nanoboot - NB_x64_5031_DSM_50-4493_Xpenology_nl.img from:
https://drive.google.com/file/d/0B8bHHU ... sp=sharing
Syno PAT file from:
http://ukdl.synology.com/download/DSM/5 ... s_4493.pat
Win32DiskImager
http://sourceforge.net/projects/win32di ... t/download
Install Win32DiskImager
Format USB stick to FAT32
Use Win32DiskImager to put Nanoboot image on USB
Put USB in HP and Power UP
Synology Assistant > Right click 'Install' > Browse to PAT file > Install
WAIT
***UPDATE 3 for 4493***
Download update file from here:
http://ukdl.synology.com/download/criti ... 3612xs.pat
Logon to Syno > Control Panel > Terminal & SNMP > Enable SSH Service
Control Panel > Update & Restore >Update Settings > Important Updates Only checked
Manual DSM Update > Browse to PAT file > OK > DO NOT CLICK YES AT NEXT STAGE
Open an ssh session (eg with putty) to your DiskStation.
Log in as 'root' and use the password you setup for your admin access.
Enter the following command transfers:
sed 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info > /autoupd@te.info1
mv /autoupd@te.info1 /autoupd@te.info
Go back to Syno Update and choose YES.
WAIT
Control Panel > Terminal & SNMP > Disable SSH Service
***Changing Serial***
Logon to Syno > Control Panel > Terminal & SNMP > Enable SSH Service
Download WinSCP Portable:
http://winscp.net/download/winscp554.zip
Launch WinSCP > New Site >
File Protocol = SCP
Enter IP Address
Enter User & Pass
SAVE
Login
Right Hand Pane > VolumeUSB1 > USBShare > boot > grub
In both instances below change the SN= to something else (I just change the last 4 digits)
Edit menu_install.lst > save
Edit menu_nano.lst > save
Restart Syno > Use Syno Assistant to check Serial.
Control Panel > Terminal & SNMP > Disable SSH Service
Package Center > Update all your packages.
Done
-
The latest Nanoboot linked in this thread doesn't work with 4493 from the Synos website. Well it didn't for me. It would get to about 40% and then fail everytime.
Also, the update process didn't work either - "States failed or corrupt file". I have created a new set of instructions that worked for me for a bare metal and upgrade from 4.2 on a HP N54L on a seperate thread.
This thread helped me though so thank you.
Troubleshooting crash issue, help appreciated
in Archives
Posted
Sorry if it sounds obvious but that's a hardware issue - 90% sure motherboard.