sandisxxx

Members
  • Content Count

    102
  • Joined

  • Last visited

Community Reputation

4 Neutral

About sandisxxx

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. My DSM is back in the original state. I cannot express my thanks to IG-88 for his incredible advice. @phinemariatry to follow IG-88's reply here and you should be fine. In case you struggle I will try to help you as IG-88 helped me. Just PM me here and I will help you. Many MANY thanks to IG-88 for his knowledge and willingness. You do not see too many people like him nowadays. Cheers.
  2. Axel, I am following the advice by IG-88 now, you need some experience there, but it is followable. IG-88 is communicating with me and really does extreme good job. I will report how it all ended up with some details, that could help you as well. But there are some things you need to do, like create a linux USB etc etc, which you should be able to find elsewhere, how to do that. By the way in my case I have updated to 6.2.4 which does crash on the HP Micro Gen8 apparently, so the process basically is to revert to 6.2.3...
  3. Thanks for the valuable input, I will boot into a linux distro to check. Actually I am not really sure if I applied update 3 or 6.2.4. I will also check the C1e (but this is unlikely). I will read the article and come back. I still have the original USB though - would that help in any way? Is there a way how to tell what update I actually applied using the Linux bootable distro?
  4. Well there is another user having the same issue. Question is, what was wrong and more importantly, how to recover from the state?
  5. Hello, I have reported this in the Updates reporting section as well, if this is against the rules - please delete my post. If there is someone that can help - will be much appreciated. Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 Update 2 - Loader version and model: Jun's Loader v1.03b DS3615XS - Using custom extra.lzma: No - Installation type: BAREMETAL - HP ProLiant MicroServer GEN8 Here are some of my details - please advice if you can: After applying this update, the system rebooted and it boots into
  6. Outcome of the update: UNSUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 Update 2 - Loader version and model: Jun's Loader v1.03b DS3615XS - Using custom extra.lzma: No - Installation type: BAREMETAL - HP ProLiant MicroServer GEN8 Here are some of my details - please advice if you can: After applying this update, the system rebooted and it boots into synoboot, like normal. However the system is not visible in the network (checked also my DHCP if it got a different IP address by chance). I have tried to create a new USB from scratch. I
  7. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 - Loader version and model: Jun's Loader v1.03b DS3615XS - Using custom extra.lzma: No - Installation type: BAREMETAL - HP ProLiant MicroServer GEN8 - Additional comment: Did not need FixSynoboot.sh, installed via Web GUI, reboot required
  8. Hello community. What if the output of my Xpenology (HP Microserver Gen8, bare metal, Juns loader 1.03b with no extra lzma, Version DS3615xs / 6.2.3 25426, no PCIE Network card, just the stock ones) ls /dev/synoboot* looks like this? /dev/synoboot /dev/synoboot1 /dev/synoboot2 /dev/synoboot3 Is it safe to install the normal way via the Control panel? Or the script has to be executed before? Thanks in advance.
  9. Thanks for great advice! Everything worked as expected. The 10 minutes when the box was not responding to ping took hours Hope this helps also others with same config. Gerat work!
  10. Found it: 1) Enable SSH and ssh into your DiskStation 2) Become root ( sudo -i ) 3) Make a mount point ( mkdir -p /tmp/mountMe ) 4) cd into /dev ( cd /dev ) 5) mount synoboot2 to your mount point ( mount -t vfat synoboot2 /tmp/mountMe ) Now I see the extra.lzma modified that has 4MiB in size so now I just replace the file with the original from 1.03b that has some 1,8MiB ? Then I use the web interface to manually install the DSM_DS3615xs_25426.pat? Please correct me if I am wrong.
  11. Can you please tell me how to overwrite the extra.lzma from the synoboot2 partition of the USB boot drive? I have tried to mount it but I got some error that I can not understand really.
  12. Thanks for this very useful advice. Can someone share the original extra.lzma file from Jun's loader 1.03b for us pretty please?
  13. In that case, what should I do when I wanted to upgrade to 6.2.3 when on the lzma for 6.2.X with DS3615xs? Do I have to create a new USB bootable without the extra lzma and the pat file of 6.2.3?