blessendor
-
Posts
39 -
Joined
-
Last visited
-
Days Won
1
Posts posted by blessendor
-
-
3 minutes ago, Bar1 said:
[ 49.526119] VMware vmxnet3 virtual NIC driver - version 1.1.30.0-k-NAPI
Seems you don't know how to read somebodies lessons)
vmxnet3 instead intel e1000? Really?
-
Release (to install with bootloader)
https://archive.synology.com/download/DSM/release/6.2/23739/
Update for release (from installed DSM)
https://archive.synology.com/download/DSM/criticalupdate/update_pack/
-
You must read once more my next post:
And second one:
And use correct boot loader.
Latest 1.04 bootloader don't work for me also (with Proxmox).
-
1 minute ago, Bar1 said:
I am not winning here
can someone please recommend a good guide?
I posted above my VM config file, why you can't try luck with it?
-
4 hours ago, Bar1 said:
Hi everyone, i am really struggling here.
I checked grub.cfg and its got the following:
set sn=A8ODN02468
set mac1=0011322CA603so i changed my mac and serial number to match but i still can't boot.
EDIT: ok changing bios to seabios, i managed to install but now its just saying: booting from hard drive....
You can't change this serial from this READY to use a bootloader if you do not change vid=0x058f
and pid=0x6387 - serial depends on vid/pid. You can leave as is MAC also if you do not plan to run several DSM boxes in this LAN (so you must have different MACs and IPs). -
1 hour ago, codedmind said:
And what are the changes needed in the args line ?
If you don't want to use USB loader style - just remove full args line and setup your VM to boot from sata disk as usual.
-
2 hours ago, wenlez said:
Thanks, @blessendor . I love the fact that I can use the Boot loader in a USB mode, so I can use all 6 SATA ports.
However, it seems I can't update with the bootload as USB.
What do you mean?
-
There is no SATA images format in PVE therms - it's only variant of the bus.
From my example you can
Just edit "/etc/pve/qemu-server/VM_ID.conf"
sata1: /absolute/path/to/your/img/file/synoboot.img
After saving config - you will see this disk in your PVE GUI as SATA.
-
6 minutes ago, codedmind said:
@blessendor thanks for your post. What version of dsm are you running? And what version of loader? Do you convert the img format to raw?
Thanks
Jun's image is already in raw format, so you do not need to convert it, but maybe you need to mount it (with kpartx and mount cmds in the linux) and change a grub.cfg file to correctly your server's MAC address.
I posted version above: Last tested and worked for me is 6.2 update 2 with bootloader 1.03 (DS3617).
https://mega.nz/#F!yQpw0YTI!DQqIzUCG2RbBtQ6YieScWg!OZw2QKwT
During the first time boot you must install DSM with the option "Install manually", otherwise it will download the latest version which will not work with this loader.
It's much better to start your VM with CLI command: "qm start VM_ID; qm terminal VM_ID" - so you will see all booting process in the console. -
9 hours ago, codedmind said:
My config example
(Disclaimer: I need to see serial numbers in the DSM storage manager - so I found that only SATA bus can provide correct disk info for DSM, so I use scsi0 for Synology OS (vm-108-disk-1.raw) installing and bootloader via USB (vm-108-disk-0.raw), bcs QEMU support six SATA disks only. If you do not care about hard disk serial info - you can use SCSI bus for all, or SATA for all if you have less then six disks to use).
args: -device ich9-usb-ehci1,id=usb,multifunction=on,bus=pci.0,addr=0xa -drive file=/var/lib/vz/images/108/vm-108-disk-0.raw,format=raw,if=none,id=drive-usb-disk2 -device usb-storage,bus=usb.0,port=2,drive=drive-usb-disk2,id=usb-disk2,bootindex=1,removable=off -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-hpet -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -realtime mlock=off -machine pc-i440fx-2.9,accel=kvm,usb=off,vmport=off,dump-guest-core=off
bios: seabios
bootdisk: scsi0
cores: 8
memory: 10240
name: DSM
net0: e1000=00:50:56:00:33:58,bridge=vmbr0
net1: e1000=33:1F:86:91:68:B2,bridge=vmbr1
numa: 0
onboot: 1
ostype: l26
serial0: socket
smbios1: uuid=a3583e20-e589-4fdd-866b-a4863e5b8ea4
sockets: 1
tablet: 0
scsihw: megasasscsi0: local:108/vm-108-disk-1.raw,size=10G
sata0: /dev/disk/by-id/ata-HGST_HSB823BSI0_LSGTYY1LAGS4K6H,serial=LSGTYY1LAGS4K6H,backup=0
sata1: /dev/disk/by-id/ata-HGST_HSB823BSI0_LSGTYY1LAGSD4UH,serial=LSGTYY1LAGSD4UH,backup=0
sata2: /dev/disk/by-id/ata-HGST_HSB823BSI0_LSGTYY1LAGRPT7H,serial=LSGTYY1LAGRPT7H,backup=0
sata3: /dev/disk/by-id/ata-HGST_HSB823BSI0_LSGTYY1LAGS1WYH,serial=LSGTYY1LAGS1WYH,backup=0
sata4: /dev/disk/by-id/ata-HGST_HSB823BSI0_LSGTYY1LAGS97DH,serial=LSGTYY1LAGS97DH,backup=0
sata5: /dev/disk/by-id/ata-HGST_HSB823BSI0_LSGTYY1LAGSGN3H,serial=LSGTYY1LAGSGN3H,backup=0 -
I can't boot my Proxmox VM with this loader (https://mega.nz/#F!Fgk01YoT!7fN9Uxe4lpzZWPLXPMONMA)
All I can see is blinking cursor via qm terminal and standard info about Jun's loader via VNC console.
System not booting.
Last tested and worked for me is 6.2 update 2 with bootloader 1.03 (DS3617).
-
I can't boot my Proxmox VM with this loader (https://mega.nz/#F!Fgk01YoT!7fN9Uxe4lpzZWPLXPMONMA)
All I can see is blinking cursor via qm terminal and standard info about Jun's loader via VNC console.
System not booting.
Last tested and worked for me is 6.2 update 2 with bootloader 1.03 (DS3617).
Tutorial: DSM 6.x on Proxmox
in Tutorials and Guides
Posted
Sorry, U'r right, it's just a synology's modules loading and vmxnet3 also there.
You will not see IP ion the terminal boot log after install - log in (type your admin username and password here - which you choose during install.
Then execute 'ip a' command, and you will see your interface addresses.
Or you can check your DHCP server for latest leases address (belong to your mac).