Jump to content
XPEnology Community

Giml

Rookie
  • Posts

    3
  • Joined

  • Last visited

Recent Profile Visitors

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

Giml's Achievements

Newbie

Newbie (1/7)

0

Reputation

  1. Hello Kimf, I meant assuming your boot loader is stored on hard disk or ssd (and not on an USB device), then you have to set your disk type to SATA (eventually IDE) for the synoboot and not USB. PS1: Using KVM, I can't see why it would be relevant to use an USB device to boot (with the boot loader stored on this USB device) PS2: I wrote this post because it seemed to me that some although storing the loader on disk, they put USB in disk type, which explains their difficulties.
  2. Hello, Not sure too if still relevant. But, I've experience myself this message "Screen will stop updating, please got to find.synology.com" WITH NOTHING MORE HAPPENED. In my environment, the reason was the disk type. KVM seems always set it by default to IDE. I just had to change it to SATA. And then, the installation run fine. As mentioned in other post threads, if you use KVM, the disk type must NOT be USB but SATA (or eventually IDE if you are still using IDE disk). I didn't have to modify something else, no need in my environment to set/modify loader parameters.
  3. Loader version and type: 3615xs: DSM version in use (including critical update): DSM 6.2.3-25426 Using custom modules/ramdisk?: No Hardware details : Using KVM on Ubuntu 20.04 LTS. Motherboard: ASUS A320M-K AM4 mATX AMD Everything Works OK! Thank you very much. Great job !
×
×
  • Create New...