sandyring

Would be great if someone could give me some tips on this one (someone who knows what they are doing :-)). I've been playing with this on and off for a while, using many different guides and different USB sticks - slowly trying to get towards the goal of getting an old HP microserver gen 8 intel celeron 2.3ghz which was running 7.0.1-42218 via Juns loader up to a newer version using redpill. I haven't wiped any of the drives and am trying to migrate, just used this guide most recently to get to where i am now: I was intially getting the corrupted message when trying to upload a pat file, but that seems to have been resolved by using all the commands in the above guide (some weren't in other guides i noticed). Anyway i am now in the scenario where i try to upload a pat file (have tried DSM_DS3615xs_42218.pat and DSM_DS3615xs_42962.pat) but it gets to 8x/9x% reboots and then comes back to the install screen again. I've read lots, one says about getting logs as below for some clues cat /var/log/junior_reason cat /var/log/*rc* none of these exist (using winscp to browser the file structure); I also saw a very similar thread about a script which would seem to fix this issue, but it looked to be hosted on gitlab but has since gone. I've also got an older HP Server Gen 6 to upgrade if i ever manage to get this newer one done, that's on 6.0.2. Any assistance / wizardry much appreciated!.

Hi all, this is a bit of a weird one, i have 2 x HP Microservers which have been running a version of 6.1 for sometime, so decided to take the plunge to 6.2-23739 using bootloader 1.03b. I updated the first one absolutely fine and it doesn't appear to have any issues (this is my backup device); the second one appeared to perform the update ok, but i'm seeing behaviour of the installed apps constantly stopping. Looking in the logs i do see: Info System 2021/01/02 13:28:44 user System successfully stopped [scemd]. Info System 2021/01/02 13:28:40 user System successfully stopped [NTP service]. Info System 2021/01/02 13:28:40 user System successfully stopped [FTP service]. Info System 2021/01/02 13:28:39 user System successfully stopped [synomount]. Info System 2021/01/02 13:28:39 user System successfully stopped [Hotplug Service]. Info System 2021/01/02 13:28:38 user System successfully stopped [Rsync]. Info System 2021/01/02 13:28:38 sandyring System successfully stopped [FTPS service]. Info System 2021/01/02 13:28:38 user System successfully stopped [Windows file service]. Info System 2021/01/02 13:28:37 user System successfully stopped [NTP Client Service]. Info System 2021/01/02 13:28:37 user System successfully stopped [Apple file service]. Info System 2021/01/02 13:28:36 user System successfully stopped [Windows network discovery]. does anyone have any idea why this one device keeps stopping the above which i assume are causing these more widespread issues?. thanks in advance!

I sincerely hope someone can help me on this, there is a virtual beer in it for anyone who can work their magic!; I've spent so many hours on this now, it's driving me insane. I have a HP Microserver Gen8 which was initially running 5.02 BIOS J06 06/06/2014 (from what I read the Bios being out of date shouldn't make any difference to this); initially of course I wanted to upgrade and migrate data, however no matter what I did following either of the 2 guides I found below, seemingly as far as I could get was being stuck in a seemingly never ending constant 'recover' loop, you hit recover, the device seemingly goes away and does it's thing, reboots, and then you are back to where you were 10 mins ago. Here are the guides I've been following: I also tried: https://github.com/XPEnology/JunLoader/wiki/Installing-DSM-6.0-Bare-Metal Elements I've not been sure on are the following due to it working before on previous 5.02 and me not needing to change anything: 'HDDs are booting in AHCI mode and not in IDE. Finally, if disabled, also enable the serial port in BIOS', am i correct in this assumption?...... I'll also note at this juncture that I tried re-install and force install.... So next, I removed the 4 drives which have data on, and installed a spare drive (on a recommendation), that someone else who had a similar situation, managed to get a drive updated and running this way, and then swapped in the other drives and got them updated that way. Just to clarify, I connected this spare drive to a window laptop - removed all partitions so that it's just an unallocated drive in the hope the Xpenology setup would see it as a new drive/install.... Once the new drive is installed, i do a bare metal install from the menu, then i see the black screen on the Microserver: decompressing Linux.... Parsing ELF... done. booting the kernel I used find.synology, connect to the device (which at this point under status says: not installed), and have the big ' Set up' button as the only option. At this stage I have manual install or 'install the latest DSM', I hit manual install and then browse to the DSM_DS3615xs_15152.pat file I have locally as per the above instructions. I now get the 'installing Diskstation manager' screen - 'uploading DSM installation manager' at the bottom, the device reboots. I go back into find.synology, it comes up with 'connect', the status is now 'recoverable'....i am not back in the 'recover' loop as above.. I've also tried the extra.lzma ramdisk, no difference. WHAT ON EARTH AM I DOING WRONG?!.....

thanks huxmut, I did try the reinstall and force install, but still in a loop. Good idea re the old pid and vid though, will try that!. Would dropping in the other drives loose the data though?

bump :-$

I hope someone can help me here, I've done quite a bit of searching, tried some things, but nothing has worked. Firstly, I've got a HP Microserver gen 8 which was running 5.2, I followed this tutorial: All was going well until I got to part 9:, essentially during an attempted migration it's appears to be stuck in a loop: Welcome back with the recover button, you click the recover button, the server reboots, but you find yourself stuck in a loop back at exactly the same recover screen 5 mins later....