Jump to content
XPEnology Community

nick w

Member
  • Posts

    70
  • Joined

  • Last visited

Posts posted by nick w

  1. Polanskiman said:
    theimpimp said:
    theimpimp said:
    I'm hoping someone can help me too :smile:.

     

    I had an HP Gen8 Microserver running 5.2 for a while now. It is a “stock” Gen8 Microserver running nothing unusual or out of the ordinary. I finally got fed up of the limits of 5.X and thought I’d make the jump, especially with this wonderfully helpful tutorial and several reports of Gen8 Microservers operating correctly. The machine is fully loaded, with 4 drives set up in SHR and a SSD acting as a cache disk.....I followed all the steps, and all was going fine and saw that I was upgrading - however upon final reboot, the Microserver seems to have gone into a loop showing as “recoverable” and always rebooting to the “recoverable" state, but never successfully booting to DSM. I have my router giving out a fixed IP to the MAC address of the server, and correctly copied by VID, PID, MAC1, MAC2 and also the serial from my old 5.2 install across. Synology Assistant shows it as being on Version 6.0.2-8451 currently.

     

    Does anyone have any ideas? I've tried searching for other people with the "recoverable" loop issue but they seem to either have solved it themselves and not posted how or it was easy solutions like VID/PID mismatch - could it be worth trying a diff USB stick? I figure it has to be an issue with the update applied though as it can be found via the Synology Assistant... Stumped! :sad: Is there anyway of "Reapplying" the manual update pat file in case it was a bad upload or somesuch? Is there a way to wipe the DSM update but retain the data and try again? Any thoughts welcome & very much appreciated! :smile:

     

    Make sure Bios is configured properly to start with and that all required info on grub file is correct. Careful with typos. Reboot your router before starting an install to make sure it's running fresh.

     

    You can start with a re-install or force install see if that fixes anything. Otherwise you can wipe the DSM partition with a live ubuntu USB drive then install DSM again. All settings and apps will be gone obviously but your data is on a different partition so it should be safe. Since you have 4 drives the DSM partitions are normally these: dev/sda1, dev/sdb1, dev/sdc1, and dev/sdd1. Here is a tutorial I made on how to access the partitions in case you want to make a backup priori doing anything just in case: https://xpenology.com/forum/topic/7004-tutorial-how-to-access-dsms-data-system-partitions/

    I think there were a few gen8 questions in the original Jun loader thread. Also check there.

     

    Sent while on the move

  2. Hello

     

    I am hoping someone out there is able to help. I have just upgraded my baremetal HP N54L withJuns loader to DSM 6.0.2. Since upgrading, my synology is unable to see my DVT Tuner, Nanostick 290e

     

    I have tried everything but i am expecting the drivers are not included in the image on DSM. Is anyone able to point me into a guide so i can attempt it?

    Or is there someone able to help guide me though doing it?

     

    https://stevekerrison.com/290e/

     

    I have enough knowledge to drive round a Linux OS, but compiling against source code is a few levels above me!

     

     

    Thanks

    Nick

  3. Building out my test environment again but before i start working on building a VM with DSM 5.2-5644 i wanted to make sure its working?

    I can see the downloads are available for the VMDK.

     

    I have seen Trantors topic and a few others saying they updated to 5.2-5644 and now have issues

     

    This is a brand new VM for the DSM 5.2-5644 install

     

    Thanks

    N

  4. I thought that I would share an interesting twist....

    I upgraded my second XPEnology box (to 5.2-5565), applied no Updates - and am seeing some of the same issues.

     

    So - it is "interesting" that downgrading resolved my issues previously...

    But it would appear that the "cause" may not in fact be the updates.

     

    I read that 5.2-5592 is forthcoming - so it will be interesting to see what results from that in comparison.

    Yeah. Would be interesting when we get 5595 5.2 bootloader

     

    Sent from my Nexus 6 using Tapatalk

  5. So my upgrade path to 5.2

     

    I was on DSM 5.0 Update 7

    I upgraded to 5.1 5522

    Then upgraded to 5.1 5055 (had application issues after upgrade, apps wouldnt run or install.)

    Upgraded to 5.2 - 1

    Upgraded to 5.2 - 2

     

    I havent found any issues yet

    My DSM boots quickly. I havent had any hangs or had to perform a forced shutdown

  6. running ESXI means i can safeguard updated by taking snapshots

    I also have loads of VMs running, windows 10/8.1 server 2012 and some linux boxes to dabble with....

     

    You could do each one and see which you prefer.. i would go the ESXi route, it adds a bit more flexibility.

     

    Just to add, i use TvHeadend, i stream live terrestrial through the house and this needs to go on a baremetal install. so no ESXi....

×
×
  • Create New...