Search the Community
Showing results for tags 'dsm62'.
Found 2 results
Hi all ! First of all, thank you developers for the wonderful work on Xpenology project ! Does anyone know why the SATA disks show up as SCSI in DSM virtualized ? This will generate errors in the interface when I check the Health of the disks. I am running DSM 6.2.2, Jun 1.04b, DS918+, in Esxi 6.7 on Asrock J4105-ITX board. I have 3 disks in my VM: 1. the synoboot image (/dev/hda) 2. a virtual disk on SATA1:0 3. a Hitachi hdd on a SATA controller, using PCI Passthrough. synodisk --enum ************ Disk Info *************** >> Disk id: 1 >> Slot id: -1 >> Disk path: /dev/sda >> Disk model: Virtual SATA Hard Drive >> Total capacity: 0.05 GB >> Tempeture: -1 C ************ Disk Info *************** >> Disk id: 2 >> Slot id: -1 >> Disk path: /dev/sdb >> Disk model: Virtual SATA Hard Drive >> Total capacity: 16.00 GB >> Tempeture: -1 C ************ Disk Info *************** >> Disk id: 4 >> Slot id: -1 >> Disk path: /dev/sdd >> Disk model: HTS545050B9A300 >> Total capacity: 465.76 GB >> Tempeture: 29 C smartctl --scan /dev/hda -d ata # /dev/hda, ATA device /dev/sdb -d scsi # /dev/sdb, SCSI device /dev/sdd -d scsi # /dev/sdd, SCSI device As you can see the HDD is seen as SCSI. udevadm info --query=property --name /dev/sdd DEVNAME=/dev/sdd DEVPATH=/devices/pci0000:00/0000:00:17.0/0000:13:00.0/ata4/host3/target3:0:0/3:0:0:0/block/sdd DEVTYPE=disk ID_PART_TABLE_TYPE=gpt MAJOR=8 MINOR=48 PHYSDEVBUS=scsi PHYSDEVDRIVER=sd PHYSDEVPATH=/devices/pci0000:00/0000:00:17.0/0000:13:00.0/ata4/host3/target3:0:0/3:0:0:0 SUBSYSTEM=block SYNO_DEV_DISKPORTTYPE=SATA SYNO_INFO_PLATFORM_NAME=apollolake SYNO_KERNEL_VERSION=4.4 USEC_INITIALIZED=779574 So all disks, even though are on SATA controllers show up as SCSI and smartctl fails for them. If I try to get SMART info, I get an error: smartctl -a /dev/sdd SMART support is: Unavailable - device lacks SMART capability. But if I add -d ata, it works. SMART support is: Available - device has SMART capability. Anyone can shed some light how to make the disk be seen as SATA instead of SCSI? Thank you !
Hi this is how I managed to get DSM 6.2 running on the free VMWare Workstation Player 15. I know there are other tutorials for VMWare Workstation Pro and the procedure is quite similar. Following on of these tutorials (https://xpenology.com/forum/topic/13006-tutorial-vmware-workstation-dsm-62-install-esxi-compatible) brought me very close to my goal but still I had to do some try and error, therefore I am sharing my piece of the cake here. Please note: This is how I made it work, dont blame me if this is not working for you. 1. Loader Download Jun's Loader v1.03b DS3617xs Synoboot_3617.zip | 19.5 MB | MD5 = 94d18efbc349da2bd45d6e57adabc54f 2. Convert Loader img to vmdk with Starwind V2V Image Converter (free) 3. Run the "new vm wizzard" on VMWare Workstation Player The wizzard always creates a data hd, you can use this as your first data hd or delete it later. Finish the wizard Now edit the virtual machine settings This is what I do usually - Change cpu and ram to 4/4 - remove cd, soundcard, printer - change LAN to bridged - add x more scsi hds (same settings as when using the wizard) Copy the two vmdk files from the conversion above and add as a SATA hd (select the 1k file) and select keep existing format This is how my setup looks after that Power up the vm and you will realize it doesnt boot – change bios boot order and after saving select VMWare while booting (you need to be real quick this is only showing for some secs). Find your ds via find.synology.com and run installation as usual (I downloaded latest 6.2. using the link on xpenology to be sure to use a supported version). When the HD erase notification appears it should show you all your data hds you added – I added 1 boot hd and 3 data hds so 3 hds should be shown. Takeaways: - I was using an old version of Starwind V2V converter, this converted the image but apparently sth was different and it didnt really boot up correctly (no LAN). - When configuring the synoboot as scsi I was not able to connect to my nas (didnt get an IP from DHCP) - I had to select VMWare/ESXi on boot otherwise no data hd was shown during installation and dsm installation failed - I tried the same with DS918+, but this got me into a installation loop - Tested upgrade to 6.2.1. after that ds was broken – I guess the loader is not ready for it yet – so make sure auto update is disabled Again, this is just my thoughts and how I managed it. Maybe things in this are wrong or understood wrong by me - but at least this is how I managed to get it running. Cheers