Tibag

Members
  • Content count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Tibag

  • Rank
    Newbie

Recent Profile Visitors

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

  1. Tibag

    DSM 6.2 Loader

    That's a typo, sorry, 1.03b. 😉 So guys, anyone successfully got 1.03b on ESXI 5.x on a N54L? 🤔
  2. Tibag

    DSM 6.2 Loader

    Actually I installed DS3615xs initially. But now my issue is that DS3615xs 1.03b won't get the network to work so I am definitely stuck ; even as a very fresh install without my data HDD plugged in. I tried the DS3617xs 1.03b and same result, fresh install and nothing on the network. The boot looks like that: Is it supposed to show more as the 1.02b used to? Like "booting kernerl..."?
  3. Tibag

    DSM 6.2 Loader

    So I just spent 4 hours trying to get it back to work. I ended up trying something like But I can't get my Syno to be on the network with 1.03b. I've just tried again: 1.02b fresh image: I can find the NAS via Assistant 1.03c fresh image: I can't find the NAS, even checked my rooter and it doesn't give it an IP. I checked the MAC matched on grub file and it does. I am running ESXI 6 on an HP N54L. It's really odd as I had the feeling it worked on my very first attempt. I am maybe doing something wrong but it seems that bootloader is not working on a setup like mine. I now have to reinstall 6.1... 😝
  4. Tibag

    DSM 6.2 Loader

    Thanks mate ; I should have read the big red announcement with the latest update... So, I have my synoboot.img on my ESXI. I take it and replace the 3 files with the ones from the DSM_DS3615xs_23739.pat? Then boot on it and it should reinstall? Edit: I tried that and it doesn't work. Note that my DSM_DS3615xs_23739.pat didn't contain the "extra" file. Any idea?
  5. Tibag

    DSM 6.2 Loader

    Many thanks Jun, you are such a star! I gave it a try on my N54L using ESXI 5.5. I change my boot image and the assistant found my NAS and suggested a repair. It restarted and came back. Then I tried an auto-update via DSM but the NAS didn't come back (Assistant was not finding it anymore). Then I put back my old boot image (1.02b) and I repaired again but DSM doesn't come back. Did I brick it? Can you help? Thanks!
  6. Tibag

    RAID group crashed following upgrade

    Agreed, I am not storing anything I am not backing up elsewhere so I am not too worried. It's also weird a WD RED HDD would fail after 3.5 years?...
  7. Tibag

    RAID group crashed following upgrade

    Okay, it seems like I've just been unlucky. My HDD had some failing sectors ; I could access all my files but DSM would complain (on any version, 6.2 update 1 or 5). I backed up my files, plugged it back on my PC with Windows, installed the Western Digital Data LifeGuard Diagnostics and verified disk. It found some bad sectors and fixed them. Then a did a deep format, it took ~6h. Put it back in my N54L and ran again the installation. I've recreated my RAID group, it's currently checking the disk but so far so good (before it would fail around 5% of the check).
  8. Tibag

    DSM 6.1.4-15217 Update 5 CRASHED

    Do we have a way to downgrade to previous update?
  9. Hi all, Today I have successfully upgraded my 6.0.1 to 6.1.4 on my N54L using the loader 1.02b and ESXi. After updating all my apps I decided to apply the update 5 via the UI / auto download. When it came back I got my RAID group crashed. I've tried to: rebuild by RAID group, like done there: recreate my ESXi image to force a repair After recreating my RAID group and rebooting I can see the group is healthy (cat /proc/mdstat shows state "U"), even from DSM, and it crashes after a few seconds being logged in. Any idea what could be causing that? I checked /var/log/messages and can't see anything helpful. Thanks
  10. Hello, Je suis sur un N54L avec ESXI , Jun 1.02a (je crois) et DSM 6.02 u9. Quelqu'un a-t-il fait l'upgrade pour le loader 1.02b? Je suis pas sur de la procedure via ESXI. Je m'etais dit: recuperer mon synoboot.vmdk extraire mon precedent grub file creer un nouveau synoboot.vmdk avec l'ancien grub remplacer ma VM pour utiliser ce nouveau vmdk Seulement voila j'arrive pas a ouvrir mon synoboot.vmfk avec OSFMount mais le fichier est si petit (1KB) que c'est pas etonant. Du jpense que je peux pas faire comme ca. Des suggestions? Merci