blu001

Used arpl-1.0-beta2.vmdk-flat.zip on ESXI 7.0u3 and microserver gen8, with success; needs SataPortmap 18 and DiskIdxMap 1B00 otherwise didn't see HDs on LSI HBA passtrough; with those parameters I still have a "dumb drive" on slot 1

For release v1.0-beta2 which .vmdk file should I use for ESXI 7.0 u3? arpl-1.0-beta2.vmdk-flat.zip or arpl-1.0-beta2.vmdk-dyn.zip? Thank you P.S. Thank you @fbelavenuto for the great work

yes, same output tc@box:~$ ./rploader.sh listmods now Testing modules.alias.json -> File OK ------------------------------------------------------------------------------------------------ It looks that you will need the following modules : Found VGA Controller : pciid 1234d00001111 Required Extension : bochs_drm bochs_drm Searching for matching extension for bochs_drm Found SATA Controller : pciid 8086d00002922 Required Extension : ahci Searching for matching extension for ahci Found SATA Controller : pciid 8086d00002922 Required Extension : ahci Searching for matching extension for ahci Found Ethernet Interface : pciid 1af4d00001000 Required Extension : No matching extension ------------------------------------------------------------------------------------------------

Anyone successful to install on microserver gen8 and Proxmox? When I reboot after building I can't reach the vm (no ping). I've tried virtio, E1000 and Realtek adapters in Proxmox, with no success. For Proxmox I've used this configuration from user haydibe (changed disk and memory size and the name of the file downloaded from github): # set vm id id=930 # create image directory, download and uncomporess mkdir -p /var/lib/vz/images/930 curl --location https://github.com/pocopico/tinycore-redpill/raw/main/tinycore-redpill.v0.4.4.img.gz --output /var/lib/vz/images/930/tinycore-redpill.v0.4.4.img.gz gzip --decompress /var/lib/vz/images/930/tinycore-redpill.v0.4.4.img.gz --keep # create vm qm create 930 \ --args "-drive 'if=none,id=synoboot,format=raw,file=/var/lib/vz/images/930/tinycore-redpill.v0.4.4.img' -device 'qemu-xhci,addr=0x18' -device 'usb-storage,drive=synoboot,bootindex=5'" \ --cores 2 \ --cpu host \ --machine q35 \ --memory 4096 \ --name DSM \ --net0 virtio,bridge=vmbr0 \ --numa 0 \ --onboot 0 \ --ostype l26 \ --scsihw virtio-scsi-pci \ --sata0 local-lvm:vm-930-disk-0,discard=on,size=32G,ssd=1 \ --sockets 1 \ --serial0 socket \ --serial1 socket \ --tablet 1 # create disk for sata0 pvesm alloc local-lvm 930 vm-930-disk-0 32G Then I started the vm, opened a terminal, read the ip of the vm via ifconfig to use with ssh: ssh tc@<vm-ip> with pwd P@ssw0rd Then these steps, as per pocopico post (plus point a2 to match the mac of user_config.json with that of the vm): 4. Check the contents of user_config.json, if satisfied keep or else run : a. Change you serial and mac address by running ./rploader.sh serialgen DS3615xs a2. edit user_config.json to change the mac to same of the proxmox vm b. Update user_config.json with your VID:PID of your usb stick by running ./rploader.sh identifyusb now c. Update user_config.json with your SataPortMap and DiskIdxMap by running ./rploader.sh satamap now d. Backup your changes to local loader disk by running ./rploader.sh backup now 5. ./rploader.sh build bromolow-7.0.1-42218 (no errors) 6. sudo reboot This is what I can see on the serial port after booting: Is there any known problem with Microserver gen8 embedded ethernet adapter? thank you

after the upgrade I had problems with samba shares, I was able to access public folders, but not the folders requiring authentication I tried everything from inside DiskStation web interface, but without success, so I came up with this solution: ssh admin@<DiskStation_ip> ssh access to your DiskStation; you will be asked for the admin password sudo -i for root privileges; you will be asked for the admin password smbpasswd -a <user> for every DiskStation user who needs samba access to shared folders; you will be asked for a password for every user that's all, just in case someone has the same problem bye

ciao, nella sezione inglese ho scritto punto per punto come ho aggiornato dalla 5.2 alla 6.1.2, ma io utilizzo esxi, per cui il mio post non è utile per le installazioni bare metal questo il link: ciao

Hello, my first post and I really want to say thank you to all the community I've upgraded with success from 5.2-5967.1 update 3 to 6.1.2-15132 with loader 1.02b esxi 6.0 update 2 on Microserver gen8 with xeon E3 1220L v2 1 ssd for datastore on internal controller and passthrough of a LSi 9211-8i flashed in IT mode with 4 HDDs migration, no clean install and volume repair what I've done: 1) download the image file from first post here (I've used loader 1.02b ds3615) 2) edit settings of your current vm with xpenoboot 5.2 and write down MAC address 3) login to your DSM 5.2 web interface and write down serial number; shutdown the vm 4) download and install OSFmount, then mount the image file downloaded at point 1 (untick "read-only drive"); choose partiton 0 15MB 5) with notepad++ or similar edit grub.cfg with serial and MAC address from point 2 and 3, you can also change the default timeout; I haven't changed anything related to vid and pid 6) download and install StarWind V2V Image converter; convert the image file with modified grub.cfg (choose VWware ESX server image) 7) this will result in 2 files synoboot.wmdk and synoboot-flat.wmdk 8) upload them to the same datastore where you have xpenoboot.wmdk; you can use datastore browser to upload files 9) edit settings of the vm and delete the hard disk pointing to xpenoboot.vmdk virtual disk 10) add new hard disk scsi 0:0 independent non persistent pointing to synoboot.vmdk 11) I haven't added any serial port 12) start the vm and open immediately the console, because you have to select the third entry of the boot menu, the one related to esxi (I wasn't enough quick and needed a vm reset..) 13) open a web browser to find.synology.com 14) connect, install, migrate, manual install with the latest pat file you can download from links here https://xpenology.com/forum/topic/7294-links-to-dsm-and-critical-updates/ 15) in my case the ip was changed, so log in and update it, then update packeges in the package center... backup and replication is now called hyperbackup hope this helps someone bye