Polanskiman

Tutorial: Install/Migrate DSM 5.2 to 6.0.2 (Jun's loader)

Recommended Posts

On 3/10/2018 at 12:11 PM, lippi said:

I read that others had a problem with hp machines booting. The problem is that. is there any other solution? 5.1 boot works. juns loader does not boot. Thanks

 

HP Compaq 6000 Pro Microtower

 

according to someone who has already tried, it does not work even with the mbr loader so use a different hardware or maybe try open media vault instead of dsm

 

 

Share this post


Link to post
Share on other sites
1 hour ago, IG-88 said:

synology also provides a md5 file so you can check and be 100% sure the file is ok

 

i'm using V1.5 (1015) with win10 x64 (fcu), so its not working for you (for whatever reason)

 

no it has to be DS36xx not RS, RS stands for rackstation (19") thats a different product

Not sure how to quote line by line....

 

I've tried all different versions of the pat files and all are saying corrupt but it may be the fact I'm using the wrong one.

I'm using version 2 of OSFMount which may explain my issue there.

The RS file may be another reason why it's not working. Perhaps I should read more carefully.

Share this post


Link to post
Share on other sites

if you use the loader for ds3617xs (there are loaders for 3 different models, so choose wisely, also use loader 1.02b) then your file for installing would be

https://usdl.synology.com/download/DSM/release/6.1.5/15254/DSM_DS3617xs_15254.pat

 

edit: sorry thats was for DSM 6.1 as we are in the 6.0.x section here it has to be loader 1.01 and DSM 6.0 file

https://usdl.synology.com/download/DSM/release/6.0.3/8754/DSM_DS3617xs_8754.pat

 

 

 

28 minutes ago, adelphia said:

Not sure how to quote line by line....

mark the text in the post you want to quote from, when marked a little box appears "quote this" and when you click on it the passage appears in the answering box at the end below the last post

 

28 minutes ago, adelphia said:

I'm using version 2 of OSFMount which may explain my issue there.

 

also its the x64 version (osfmount_x64.exe) you have to use

Edited by IG-88

Share this post


Link to post
Share on other sites
5 minutes ago, IG-88 said:

if you use the loader for ds3617xs (there are loaders for 3 different models, so choose wisely, also use loader 1.02b) then your file for installing would be

https://usdl.synology.com/download/DSM/release/6.1.5/15254/DSM_DS3617xs_15254.pat

I think 1.02b is the one I'm using but I'll redownload and ensure that is the case (I'm going to remove all my loaders and pat files I've downloaded to date so as to start fresh)

 

6 minutes ago, IG-88 said:

mark the text in the post you want to quote from, when marked a little box appears "quote this" and when you click on it the passage appears in the answering box at the end below the last post

Thanks. Now I do.

 

7 minutes ago, IG-88 said:

also its the x64 version (osfmount_x64.exe) you have to use

Yup that's the one I've got. The 32bit version won't even install on 64bit. Perhaps I should get hold of 1.5 version (if there's an archive for it on the site).

Share this post


Link to post
Share on other sites
3 minutes ago, adelphia said:

I think 1.02b is the one I'm using but I'll redownload and ensure that is the case (I'm going to remove all my loaders and pat files I've downloaded to date so as to start fresh)

 

see my edited version above

1.01 loader -> DSM 6.0.x

1.02 loader -> DSM 6.1.x

Share this post


Link to post
Share on other sites
2 minutes ago, IG-88 said:

see my edited version above

1.01 loader -> DSM 6.0.x

1.02 loader -> DSM 6.1.x

Would you recommend going straight to 6.1.x or 6.0.x and upgrading? I am starting on a virgin machine so there will be no chance of data loss. I'm also working with 4 drives to make a RAID if that matters.

Share this post


Link to post
Share on other sites
2 minutes ago, adelphia said:

Would you recommend going straight to 6.1.x or 6.0.x and upgrading? I am starting on a virgin machine so there will be no chance of data loss. I'm also working with 4 drives to make a RAID if that matters.

 

depends on the hardware, if the storage uses linux ahci driver then 6.1 is the best choice

so whats the hardware (network card and storage or if its onboard then name the mainboard)?

 

dsm is all about software raid, 4 disks (same) i'd use raid5 if you plan to user different disks and still use as much space as possible there is the SHR mode (has to activated manually for 3615/3617 before creating the volume after install), if you want to read about SHR go to synology.com they gave a good knowledge base and faq section

Share this post


Link to post
Share on other sites

OK, I may have been a dooshbag here. I was trying to get this to work on an SD card but I think it may have to be on an actual physical flash drive. Yup, switch to a flash drive and worked 1st time. Grrr.

Share this post


Link to post
Share on other sites
3 hours ago, adelphia said:

I was trying to get this to work on an SD card

 

waht did you use for vid/pid?

maybe it would work if you use the usb vid/pid of this device? (i guess that device has vid/pid and it will not be dependent on the sd card)

to find out vid/pid you would have to boot a live linux on that system as its an internal device

Share this post


Link to post
Share on other sites
9 hours ago, IG-88 said:

waht did you use for vid/pid?

 

I got the information from Device Manager in Windows following the tutorial from Jun. The VID/PID was of the device as it was the same with or without an SD card in the reader. Having said that, USBFlashInfo doesn't even detect it as a flash drive which is why I said it looks like it can't be done on an SD card.

 

I would much rather I could as it "looks nicer" using an almost hidden SD card in an internal card reader than having a flash drive sticking out and taking up one of the few spare USB ports I have.

Edited by adelphia
Corrected info

Share this post


Link to post
Share on other sites
10 minutes ago, adelphia said:

I got the information from Device Manager in Windows following the tutorial from Jun. The VID/PID was of the device as it was the same with or without an SD card in the reader. Having said that, USBFlashInfo doesn't even detect it as a flash drive which is why I said it looks like it can't be done on a flash card.

if it did not work that way i wouldn't do anything further, just next plan b or c

plan b, you took a normal usb flsh drive, so maybe plan c will be good:

the "looks nicer" thing is easy, there are small usb flash drives like this

https://www.sandisk.com/home/usb-flash/cruzer-fit

with that you could even use it in the front when your case is black or when your front usb is behind a small flap

 

Share this post


Link to post
Share on other sites

Thanks for the info, at least I know I wasn't going wrong there.

 

I've added one of those Cruzers to my Amazon list so I'll pick one up next week, I didn't realize you could get them so small for a large capacity. I think it's pointless going above 16GB; in fact I would have chosen the 8GB except that it's more expensive than the 16GB right now. Do you know if you can format and use the part of the drive that's not utilized for the XPEnology boot drive (once the drive has been imaged of course) which will be almost the full capacity of the drive.

Share this post


Link to post
Share on other sites
2 hours ago, adelphia said:

Do you know if you can format and use the part of the drive that's not utilized for the XPEnology boot drive (once the drive has been imaged of course) which will be almost the full capacity of the drive.

i theory you could add a partition and use the rest but some os may have troulbe using it (not linux)

i cant see any value as the device has to stay in the nas to boot it up

get over thinking im MB or GB think TB and then this few GB are nothing to worry about ;-)

 

the san was just what i had (chosen years ago)

there is also Intenso Slim/Micro Line, Hama FlashPen Smartly/Jelly, PNY Hook Micro, aricona Mini or Transcend TS16GJF710S

 

Share this post


Link to post
Share on other sites

Dear all,

 

Thank you for everything. You saved me. I will explain how maybe it can help somebody else.

1. My Xpenology 5.2 on HP Proliant sever was working fine  until I got a message from my server than one of my two Raid drive failed and was degrated.

2. After several attempts started and there I should replace one of the two drives or backup and press repair drive as a given option from Synology.

3. Instead (stupid me) I downloaded the Time backup Package for storage. It screwed everything up. Unable to shh with putty, find the server through synology assistant.  Nothing would work and believe me I was about to quit everything and try to save my files through Linux from another desktop that I tried and worked in the past.

 

4. Of course after I screwed up, I found out that the "Time backup " Package created same issue to others.

5. I followed the instructions  (Jun's loader) and thank you very much bypassing the OSF step 5 and everything worked great. I managed to Install as described  on my AMD HP Proliant.

6. This saved me from heart attack if there was a slight chance that I lost my files.

7. Thank you all and specially to Polanskiman for writing such a great instructions with all necessary warnings.

 

Dimitris from Athens Greece

 

PS The Time backup package showed after although is not available from synology any more and  from Package center I unistall it to be safe.

DO NOT INSTALL "TIME BACKUP" PACKAGE IF IN 5.2. 

 

Share this post


Link to post
Share on other sites
On 9/24/2017 at 11:36 PM, creisey said:

thanks guys i could reach the interface now, but unfortunately its not recognize the harddrive 

 

But, you must change the partition type for usb (6.02/6.1) from gpt to mbr, and do copy  files to converted partitions.

I also have atom 230 (not 330, but the same), it can run DSM 6.1.x.

 

But, I can't run dsm 6.2 on my hardware. that's my problem. 

Share this post


Link to post
Share on other sites
On 11/20/2016 at 9:13 AM, Polanskiman said:

 

Download the loader, unzip it and put the image file (synoboot.img) directly on the desktop.

1 - If your flash drive is plugged, unplug it.

2 - Open terminal. Issue the following commands:

 


cd /
cd ~/Desktop
diskutil list
 

The last command should bring up the list of your drives. Below is what it shows on mine:


TlMBP:Desktop Tl$ cd /
TlMBP:/ Tl$ cd ~/Desktop
TlMBP:Desktop Tl$ diskutil list
/dev/disk0
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *500.1 GB   disk0
  1:                        EFI EFI                     209.7 MB   disk0s1
  2:          Apple_CoreStorage                         200.3 GB   disk0s2
  3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
  4:                  Apple_HFS Funky                   298.8 GB   disk0s4
/dev/disk1
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:                  Apple_HFS Yosemite               *199.9 GB   disk1
                                Logical Volume on disk0s2
                                CC0A6E92-5D3B-4FF8-A35F-ACF567B573CD
                                Unencrypted
 

Now plug your flash drive and issue the diskutil list command again:


TlMBP:Desktop Tl$ diskutil list
/dev/disk0
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *500.1 GB   disk0
  1:                        EFI EFI                     209.7 MB   disk0s1
  2:          Apple_CoreStorage                         200.3 GB   disk0s2
  3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
  4:                  Apple_HFS Funky                   298.8 GB   disk0s4
/dev/disk1
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:                  Apple_HFS Yosemite               *199.9 GB   disk1
                                Logical Volume on disk0s2
                                CC0A6E92-5D3B-4FF8-A35F-ACF567B573CD
                                Unencrypted
/dev/disk2
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:     FDisk_partition_scheme                        *31.0 GB    disk2
  1:                 DOS_FAT_32                         41.1 MB    disk2s1
  2:                 DOS_FAT_32                         49.4 MB    disk2s2
 

You can see my flash drive (31GB) now with the identifier disk2. Note that your flash drive identifier could be something else (disk3, disk4...) so don't just copy paste.

 

Now issue the following command:


sudo diskutil unmountDisk /dev/disk2
 

You might be asked for your password. Here is what I get:


TlMBP:Desktop Tl$ diskutil unmountDisk /dev/disk2
Unmount of all volumes on disk2 was successful
 

Then issue the following command. Same comment: BE SURE TO USE THE RIGHT IDENTIFIER. There is no turning back on this one. If you mistakenly use the identifier of some other disk, it will overwrite it with the image. SO BE VERY CAREFUL.


sudo dd if=synoboot.img of=/dev/rdisk2 bs=1m
 

You should see this:


TlMBP:Desktop Tl$ sudo dd if=synoboot.img of=/dev/rdisk2 bs=1m
50+0 records in
50+0 records out
 

You are done.

 

If you want to access the content of the drive you have to issue the following commands:

Verify again your flash drive identifier. YES AGAIN. You will need the disk partition identifier this time:


diskutil list
You should get this:

TlMBP:Desktop Tl$ diskutil list
/dev/disk0
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *500.1 GB   disk0
  1:                        EFI EFI                     209.7 MB   disk0s1
  2:          Apple_CoreStorage                         200.3 GB   disk0s2
  3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
  4:                  Apple_HFS Funky                   298.8 GB   disk0s4
/dev/disk1
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:                  Apple_HFS Yosemite               *199.9 GB   disk1
                                Logical Volume on disk0s2
                                CC0A6E92-5D3B-4FF8-A35F-ACF567B573CD
                                Unencrypted
/dev/disk2
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *31.0 GB    disk2
  1:                        EFI NO NAME                 31.5 MB    disk2s1
  2: 0FC63DAF-8483-4772-8E79-3D69D8477DE4               15.7 MB    disk2s2
  3:        Bios Boot Partition                         4.2 MB     disk2s3
 

Note the EFI NO NAME partition with the identifier disk2s1 of the flash drive. This is the one we want.

 

If you are on MAC OS El Capitan or earlier then issue the following:


mkdir /Volumes/efi
If you are on MAC OS Sierra then issue the following:

mkdir /tmp/efi
(Since Sierra, /Volumes is no longer world-writeable. One needs to be root to create folders in /Volumes)

 

Followed by:

If you are on MAC OS El Capitan or earlier then issue the following:


sudo mount -t msdos /dev/disk2s1 /Volumes/efi
or 
If you are on MAC OS Sierra then issue the following

sudo mount -t msdos /dev/disk2s1 /tmp/efi

 

Your flash drive is now mounted. Edit what you need and eject when done. If you need to mount the flash drive again issue the last 2 commands. Always beware of the disk ID.

 

@Polanskiman, really nice tutorial for macOS, thanks!! Just a question, how can I mount the 30Mb partition in order to change the extra.lzma for a new one?? This is not explained in macOS...

 

Thanks!!

Edited by ed_co

Share this post


Link to post
Share on other sites
On 11/20/2016 at 8:13 AM, Polanskiman said:

 

Download the loader, unzip it and put the image file (synoboot.img) directly on the desktop.

1 - If your flash drive is plugged, unplug it.

2 - Open terminal. Issue the following commands:

 


cd /
cd ~/Desktop
diskutil list
 

The last command should bring up the list of your drives. Below is what it shows on mine:


TlMBP:Desktop Tl$ cd /
TlMBP:/ Tl$ cd ~/Desktop
TlMBP:Desktop Tl$ diskutil list
/dev/disk0
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *500.1 GB   disk0
  1:                        EFI EFI                     209.7 MB   disk0s1
  2:          Apple_CoreStorage                         200.3 GB   disk0s2
  3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
  4:                  Apple_HFS Funky                   298.8 GB   disk0s4
/dev/disk1
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:                  Apple_HFS Yosemite               *199.9 GB   disk1
                                Logical Volume on disk0s2
                                CC0A6E92-5D3B-4FF8-A35F-ACF567B573CD
                                Unencrypted
 

Now plug your flash drive and issue the diskutil list command again:


TlMBP:Desktop Tl$ diskutil list
/dev/disk0
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *500.1 GB   disk0
  1:                        EFI EFI                     209.7 MB   disk0s1
  2:          Apple_CoreStorage                         200.3 GB   disk0s2
  3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
  4:                  Apple_HFS Funky                   298.8 GB   disk0s4
/dev/disk1
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:                  Apple_HFS Yosemite               *199.9 GB   disk1
                                Logical Volume on disk0s2
                                CC0A6E92-5D3B-4FF8-A35F-ACF567B573CD
                                Unencrypted
/dev/disk2
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:     FDisk_partition_scheme                        *31.0 GB    disk2
  1:                 DOS_FAT_32                         41.1 MB    disk2s1
  2:                 DOS_FAT_32                         49.4 MB    disk2s2
 

You can see my flash drive (31GB) now with the identifier disk2. Note that your flash drive identifier could be something else (disk3, disk4...) so don't just copy paste.

 

Now issue the following command:


sudo diskutil unmountDisk /dev/disk2
 

You might be asked for your password. Here is what I get:


TlMBP:Desktop Tl$ diskutil unmountDisk /dev/disk2
Unmount of all volumes on disk2 was successful
 

Then issue the following command. Same comment: BE SURE TO USE THE RIGHT IDENTIFIER. There is no turning back on this one. If you mistakenly use the identifier of some other disk, it will overwrite it with the image. SO BE VERY CAREFUL.


sudo dd if=synoboot.img of=/dev/rdisk2 bs=1m
 

You should see this:


TlMBP:Desktop Tl$ sudo dd if=synoboot.img of=/dev/rdisk2 bs=1m
50+0 records in
50+0 records out
 

You are done.

 

If you want to access the content of the drive you have to issue the following commands:

Verify again your flash drive identifier. YES AGAIN. You will need the disk partition identifier this time:


diskutil list
You should get this:

TlMBP:Desktop Tl$ diskutil list
/dev/disk0
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *500.1 GB   disk0
  1:                        EFI EFI                     209.7 MB   disk0s1
  2:          Apple_CoreStorage                         200.3 GB   disk0s2
  3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
  4:                  Apple_HFS Funky                   298.8 GB   disk0s4
/dev/disk1
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:                  Apple_HFS Yosemite               *199.9 GB   disk1
                                Logical Volume on disk0s2
                                CC0A6E92-5D3B-4FF8-A35F-ACF567B573CD
                                Unencrypted
/dev/disk2
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *31.0 GB    disk2
  1:                        EFI NO NAME                 31.5 MB    disk2s1
  2: 0FC63DAF-8483-4772-8E79-3D69D8477DE4               15.7 MB    disk2s2
  3:        Bios Boot Partition                         4.2 MB     disk2s3
 

Note the EFI NO NAME partition with the identifier disk2s1 of the flash drive. This is the one we want.

 

If you are on MAC OS El Capitan or earlier then issue the following:


mkdir /Volumes/efi
If you are on MAC OS Sierra then issue the following:

mkdir /tmp/efi
(Since Sierra, /Volumes is no longer world-writeable. One needs to be root to create folders in /Volumes)

 

Followed by:

If you are on MAC OS El Capitan or earlier then issue the following:


sudo mount -t msdos /dev/disk2s1 /Volumes/efi
or 
If you are on MAC OS Sierra then issue the following

sudo mount -t msdos /dev/disk2s1 /tmp/efi

 

Your flash drive is now mounted. Edit what you need and eject when done. If you need to mount the flash drive again issue the last 2 commands. Always beware of the disk ID.

 

I'm very grateful for this and it has been so helpful. I do have an odd issue though. Sometimes I get as far as unmounting the usb stick and then issue the command to write the synoboot image. At this point occasionally it will work, but most of the time I get 'No such file or directory'. I'm not quite sure what makes it work any more. The file is definitely on the desktop, so it must be something to do with the directory I'm addressing. I know nothing of terminal commands, so would welcome any ideas please.

 

EDIT - I may have solved my issue myself. I issued the command 'clear' into the terminal window. Not sure if that was what made it work. Then I pasted the instructions into a plain text document. Then copied the instructions from that. But all working perfectly now.  Left in case anyone else has the issue on a mac.

Edited by blue max
solved

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.