Invaliduser
-
Posts
18 -
Joined
-
Last visited
Invaliduser's Achievements
Newbie (1/7)
4
Reputation
-
Thank you again Pocopico and everyone else that has contributed to this! Quick note for those using proxmox with a DS3622xs+ build and want to get "better" hard drive performance from your SATA drives. I've been playing around with drive configs and I'm getting much better performance attaching the storage drives in Proxmox as SCSI rather than SATA. This is kind of a duh moment... but I didn't realize the 3622xs+ would recognize a SCSI storage drive and I didn't realized the performance would increase that dramatically. My hardware is a pretty generic gigabyte motherboard with a Ryzen 3 3200G, 2 WD Red 4TB Drives in ZFS connected to the integrated SATA controller. I built the Proxmox vm using DS3622xs+, Processor Type = host, Storage Drives initially = SATA. Running drive stress test as follows on my storage drives attached as SATA: dd bs=1M count=2048 if=/dev/zero of=/volume1/downloads/testx conv=fdatasync 2048+0 records in 2048+0 records out 2147483648 bytes (2.1 GB, 2.0 GiB) copied, 40.42 s, 53.1 MB/s ^^Terrible^^ I powered off the VM, detached the storage drives, and reattached as SCSI. New stress test: dd bs=1M count=2048 if=/dev/zero of=/volume1/downloads/testx conv=fdatasync 2048+0 records in 2048+0 records out 2147483648 bytes (2.1 GB, 2.0 GiB) copied, 12.7126 s, 169 MB/s ^^Much better.^^ Note that doing this, your storage drives will show up as drive 13, 14, 15, etc and will not display in the storage manager overview graphic. I'm assuming this is because the 3266xs+ uses SATA for the front slots disk 1 - 12. Note that this is only for your storage drives and not the boot drive.
-
Booting Kernel is where it stops. This is normal.
-
Are you generating a new mac address for the 7.0.1 build? If so, you will need to assign that mac address to the VM's network device.
-
Yes, I was successful. But a stuck install seems to be fairly common right now. I might build another and see if anything has changed.
-
That uses a dual core architecture. You need broadwell-7.0.1-42218 that the DS3617 uses
-
Which build did you use?
-
Stopping at "booting the kernel" is normal. Use find.synology.com to discover the VM on your network. If additional troubleshooting is needed you will need to setup a serial interface with the VM to check the boot process.
-
GUI - use Winscp, filezilla, or similar to extract immediately after building. Or something like sshfs via command line.
-
If you are able to connect via serial, you will see the IP Address being assigned.
-
It may be the volume mapping. On my install (broadwell 7.0.1-xxxxx) (i'm still testing everything for now) I was able to download the images from the registry and import the container settings from my previous 6.2 install. All looks to be working fine.
-
Now you can focus on cleaning that desk 😉
-
I'm using proxmox... but I followed the instructions here https://xpenology.club/install-dsm-7-on-baremetal-or-vm/ Post your output and someone may be able to help.
-
I'm not too familiar with VMware, but in proxmox you would assign a serial port to the vm, then from the host's shell, qm terminal VMID.
-
Do you have a serial connection on the VM to terminal in and monitor boot progress?
-
VM or baremetal?
