trevmlt1

@ WujcioPafcio What do you mean you couldn't find the 918? You have a serial port added to your VM so on boot, watch the console (click on the console in the upper right, not the one on the left side panel) . Once it has booted up, the IP address of the machine is listed a few lines up. Should tell you exactly where it is. You are also installing the virtio drivers, so use the virtio network device - not e1000. If the 3622+ runs, the 918 should as well. The 920 requires you to manually do the device tree map (complicated process, and not automated - you have to do it), and you can't add drives that aren't there later is my understanding so it's not a really good choice. I would give the 918 another try, with the serial console open on boot and scroll back a bit to see what the IP assigned is. I have found the method of using the find.synology.com less than reliable when trying to find a new install.

I figured this out. Basically it was a sataportmap problem, combined with trying to install from a sata drive (would not work unless I installed using USB for some reason.

@Autastic - this happened to me too. First run through using this method, I forgot to arrow up to boot from USB - this will guarantee it fails. In order to fix it I had to detach the passed through drives and reset the drives (sfdisk --delete /dev/sdX) and then pass them through again to the vm. I used 7.1.0-42661-1 and it installed without issue. Make sure your satamap is acceptable - I used 8 and 00 in my set up.

I am trying to install DS3622xs+ in a Proxmox vm. I have tried with both passed through hard drives, and virtual disks (both SATA and as an experiment, SCSI). In watching the console, things go sideways here (I compared console output to a working 3615 installation using Redpill and TC): Running /usr/syno/etc/rc.d/J03ssdpd.sh... [ 28.042093] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities /usr/bin/minissdpd -i eth0 [ 28.046248] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) (15): upnp:rootdevice (51): uuid:upnp_SynologyNAS-3234a5beed2c::upnp:rootdevice (60): Synology/synology_broadwellnk_3622xs+/7.1-42661/10.168.2.242 (45): http://10.168.2.242:5000/description-eth0.xml Connected. done. /usr/syno/bin/reg_ssdp_service 10.168.2.242 3234a5beed2c 7.1-42661 synology_broadwellnk_3622xs+ eth0 Running /usr/syno/etc/rc.d/J04synoagentregisterd.sh... Starting synoagentregisterd... Running /usr/syno/etc/rc.d/J30DisableNCQ.sh... [ 28.085033] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities Running /usr/syno/etc/rc.d/J80ADTFanControl.sh... [ 28.087964] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) ADT Set FAN SPEED /usr/syno/etc/rc.d/J80ADTFanControl.sh: line 41: can't create /tmp/ADTFanPath//pwm1_high_freq: nonexistent directory /usr/syno/etc/rc.d/J80ADTFanControl.sh: line 43: can't create /tmp/ADTFanPath//pwm1_syno_control: nonexistent directory /usr/syno/etc/rc.d/J80ADTFanControl.sh: line 50: can't create /tmp/ADTFanPath//pwm1: nonexistent directory /usr/syno/etc/rc.d/J80ADTFanControl.sh: line 41: can't create /tmp/ADTFanPath//pwm2_high_freq: nonexistent directory /usr/syno/etc/rc.d/J80ADTFanControl.sh: line 43: can't create /tmp/ADTFanPath//pwm2_syno_control: nonexistent directory /usr/syno/etc/rc.d/J80ADTFanControl.sh: line 50: can't create /tmp/ADTFanPath//pwm2: nonexistent directory Running /usr/syno/etc/rc.d/J98nbnsd.sh... Starting nbnsd... Running /usr/syno/etc/rc.d/J99avahi.sh... [ 28.110277] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities Any idea what would be causing this? I have folllowed same process for the 3622 installation as my working 3615, but due to these errors while installing, the 3622 says no disks installed when going to the ip address of the newly created 3622 and trying to install the img In the terminal, the following just keeps repeating over and over once the 3622 vm is booted up: SynologyNAS login: [ 31.508279] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 31.512853] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 31.856901] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 31.861286] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 31.896898] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 31.899604] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 31.913092] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities [ 31.915862] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) [ 31.947043] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something [ 31.949552] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY [ 31.951414] <redpill/smart_shim.c:334> sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=-22, attempting to emulate something [ 31.953917] <redpill/smart_shim.c:274> Generating completely fake ATA IDENTITY Help!