Jump to content
XPEnology Community

MGPhiber

Transition Member
  • Posts

    8
  • Joined

  • Last visited

Posts posted by MGPhiber

  1. On 9/9/2019 at 7:55 PM, Bi0sh0ck said:

    Hmmm ... it could be that the error occurs by directly updating V5 to the current version!  One must not forget V6.0 was a master update!  Please write your mistake in the community!  Maybe someone had the same mistake

     

    Hi everyone !

    Resolved!

    After repeating the error by removing the data disks and replay the procedure with only 1 test disk:

    You are right, Bi0sh0ck!

    I was foolishly wrong to switch directly from version 5.x directly to 6.2.2 update 3.

    Here is the correct procedure: I reset the DSM partition on ALL the disks on the raid with wonderful Minitool Partition Wizard *free*

    https://www.partitionwizard.com/free-partition-manager.html

    like this excellent post of  XoioX:

     

    No weird in/out with precious data disk, no volume restorations and/or fixes ....

    The NAS resurrects completly clean as "installable" (migration was + by previous broken procedure)

    All done with *BASE* DSM v6.2 (DSM_DS3615xs_24922.pat) download from official page synology for DS3615xs and immediatly after, the latest update (6.2.2 update 3 in today case)

    Double boot, as for everyone in DSM Update reporting, and all working fine!

    Thanks again Bi0sh0ck, and happy XPEnology to all!

    Byeeeeeeeeee

     

     

     

  2. On 3/1/2019 at 1:42 PM, XoioX said:

     Hello, everybody,

    I already posted this in the german forum, but maybe it helps here too.

    Unfortunately I also made the mistake to update from 6.2 to 6.2.1 and the system was no longer available. But after some trial and error I found a solution:

     I removed every single one of the hard disks of the raid system and connected them to the PC with a USB adapter. There I used the free partitioning tool Minitool Partition Wizzard to run a wipe on the 2.37GB partition (overwriting the partition with zeros). This is the system partition of the DSM.

    Caution: You are not allowed to do anything on the other partitions and the installation order of the hard disks must also be observed.

    Then I created a new 1.03 Bootloader USB stick and started the system. The Synology Finder found the DSM and didn't show any installation. I then manually installed the DSM_DS3617xs_23739.pat file.

    After the first start the old volume was detected error free. All data was still there. Only the packages had to be reinstalled.

    I think the solution will work with all versions.

     

    Exceptional solution ! working on v5.x and v6.2x. 0 problems! No multiple boot, no volume corruption to fix. Nothing! Only NAS ready to be installed/upgradable!

     

     

  3. I have been using my xpenology v 5.x on Baremetal HP Microserver GEN8 for the last 2 years with no problem....
    I haven't been able to update the plex app for several months, so I decided to update it to v6.x given ALL the feedback + on DSM update reporting....
    I made a complete backup and starting from DSM 5.2-5967 Update9 (latest) and I made the boot key following the tutorial and directly with the DSM DSM 6.2.2 Update 3 (latest)
    Everything good!
    Xpenology has been reborn as upgradable. I performed the migration operation successfully (it is also in the logs)
    Problems begin :(
    If I click on the control panel i get the error in attach
    If clik ok i go on but try to configure the network cards i get the no response for infinite time

    In DHCP mode all (network share by example) working fine. App not tested

     

    i replicate the procedure by replacing the network card with another one of the same type (HP NC360T) and I have also rebuilt, changing the boot key, wit no success

    Any idea please?

    Many Thanks in advance.

     

    screen1.JPG

    screen2.JPG

  4. - Outcome of the installation/update: SUCCESSFUL

    - DSM version prior update: DSM 5.2-5967 Update 8

    - Loader version and model: XPEnoboot 5.2-5967.1 DS3615xs

    - Using custom extra.lzma: NO

    - Installation type: BAREMETAL - HP Microserver Gen8

    - Additional comments: OK after the first reboot.

  5. ciao

    io uso tutti i giorni la configurazione standard del GEN8, come processore e ram, e con la versione 5.x plex mi lavora splendidamente fino a 1080p. se invece provo a fargli distribuire la codifica H265, diventa impossibile fruire dei contenuti. questione di processore di sicuro. non credo che la cosa migliori con la v6

    ciao

     

  6. Buongiorno a tutti

    Non riesco a capire perche dalle versioni successive alla PlexMediaServer-1.13.2.5142-3ba6662e9-x86.spk ottengo sempre che il pacchetto non e' supportato dalla mia piattatorma.

    Sono ancora sulla "vecchia" DSM 5.2-5967 Update 8 (ultimo aggiornamento) e dalle FAQ del produttore mi pare di capire che il supporto non sia stato dismesso.....Qualcuno ha lo stesso mio problema?Grazie

  7. Ciao kiukko !

    Siccome mi piacerebbe implementarlo anche sulla mia di nas ( premesso che ho aggiornato solo all 'ultimissima patch della 5.2), ha voglia di scrivere per bene come si fa, o postare qualche link valido?

    Mi piacerebbe che si accendesse da sola quando i miei figli quadrano qualche cartone o io parto a fare qualche backup.

    Grazie

     

  8. Io lo cambiato direttamente con il synology e l'editor di testo suo... riavviato e apposto

    Sai che non ho capito ? :?:

     

    l'editor non l'ho mica capito dove sta', ma siccome non ho avuto per niente voglia di smontare la chiavetta di boot, ho fatto cosi:

     

    file station

    usbshare1

    syslinux.cfg ----download

    editarlo (sono 3 ricorrenze)

    caricamento

    caricamento-sovrascrivi

    riavviato l'unita'

    (si controlla tutto velocemente con il synology assistant)

     

    devo applicarmi invece per iniettare un MAC address di Synology come costruttore, mi piacerebbe averla al 100% come un originale per poterci legare senza timore qualsiasi servizio.....

×
×
  • Create New...