Thorlaf Posted December 7, 2018 Share #926 Posted December 7, 2018 Well, as you may know, Realtek makes more than 1 model of nic's, and without knowing exactly what your model is, I can only "read the tarot-cards" or guess. In one of my test-setups, using Asrock Q1900-ITX, the nic is a RTL8111GR, this works both with : bootloader 1.03 DS3617, DSM up to, and including 6.2 update2, but not 6.2.1 bootloader 1.04 918+, DSM 6.2.1-23824 - Update 1 with no problem. If you try to make a new fresh install, based on 1.03 3615/3617, make sure to download the 6.2 pat file and install it manually and do not update to 6.2.1 then maybe it will work for you. hi bearcat,do u know if RTL8111H is working with 6.2.1? Thanks in advanceRegards Thorlaf Gesendet von meinem ONEPLUS A3003 mit Tapatalk Quote Link to comment Share on other sites More sharing options...
Thorlaf Posted December 7, 2018 Share #927 Posted December 7, 2018 On 12/3/2018 at 11:49 AM, bearcat said: @xp_1409 You may use the serial provided, or you can just alter it a bit, both things will work (as long as you have only 1 NAS in you LAN using*that* serial). Will all Synology Services work with this method? I want to use WOL and Photostation with automated resizing. Thanks in advance again Quote Link to comment Share on other sites More sharing options...
roadx Posted December 7, 2018 Share #928 Posted December 7, 2018 @bearcat: The only info known by me related to my server's NICs (there are two of them, on-board) is the info found on the Gigabyte site and is the one as it showed in the signature. I have no idea which kind of particular controller do I have. On the Realtek site ( https://realtek-download.com/realtek-pcie-gbe-family-controller/ ), they said: Realtek PCIe GBE Family Controller RTL8111B / RTL8168B / RTL8111 / RTL8168 / RTL8111C / RTL8111CP / RTL8111D (L) / RTL8168C / RTL8111DP / RTL8111E / RTL8168E / RTL8111F / RTL8411/ RTL8111G / RTL8111GUS / RTL8411B(N)RTL8118AS Anyway, I succeed to save the files from inside the server's (user) partition, where I found all user(s) files and structure (the one containing my files), but... (as you can see, always is a "but..." ) Despite my server has one SATA III HDD (3Tb, 2.5" form), the DSM software make 4 partitions on him: one big pure ext4 partition (for user's usage) which I could accessed 'normally' and 3 other partitions which seems to be some RAID-like partitions (for OS and DSM stuff, I guess...) Ok! In order to have some results in making the server working again, I want to go into the DSM's root structure to see if I could find there the famous '/.xpenoboot' directory, which I read about it around here. Some guys said (if I understood well), if this directory is deleted, then, on re-boot (using BL 1.02b as before), it could be possible to obtain an working server having the 'old' version (in my case, 6.1.7) instead of 6.2 because the real upgrade (from 6.1.x to 6.2) would have to be executed upon restart, but the real restart never occur because the BL (v1.02b) was not compatible with the preparations made by the upgrade core before restart. Maybe is wrong what I understood... So, I need to "see" somehow those RAID-like partitions (from a Linux live USB). I read something about this (how it could be possible to see them) around here, but frankly, I don't remember well on which page I read about the DSM and 'mdadm' stuff. (and are a lot of pages... - btw: maybe the admin(s) would make another particular thread for VMware & ESXi stuff... just saying...) Somebody could help me to refresh my 'pointers'? Thank you, again for your answer(s)! (last edit): maybe here? I would see... Quote Link to comment Share on other sites More sharing options...
Bar1 Posted December 7, 2018 Share #929 Posted December 7, 2018 Hi everyone...not sure if it was mentioned before. Running proxmox, trying to install 6.2, the grub screen comes on for 1 second and then the VM is switching off......what am i missing ? Quote Link to comment Share on other sites More sharing options...
kazuni Posted December 7, 2018 Share #930 Posted December 7, 2018 1 hour ago, Bar1 said: Hi everyone...not sure if it was mentioned before. Running proxmox, trying to install 6.2, the grub screen comes on for 1 second and then the VM is switching off......what am i missing ? post your .conf? Quote Link to comment Share on other sites More sharing options...
kazuni Posted December 7, 2018 Share #931 Posted December 7, 2018 (edited) 4 hours ago, Thorlaf said: Will all Synology Services work with this method? I want to use WOL and Photostation with automated resizing. Thanks in advance again They work fine. The only things so far that does not work with valid serials and MACs are Synology Quickconnect, Package purchases and Synology.me DDNS. Edited December 7, 2018 by kazuni 1 Quote Link to comment Share on other sites More sharing options...
Bar1 Posted December 7, 2018 Share #932 Posted December 7, 2018 agent: 1 args: -device 'piix3-usb-uhci,addr=0x18' -drive 'id=synoboot,file=/var/lib/vz/images/102/synoboot.img,if=none,format=raw' -device 'usb-storage,id=synoboot,drive=synoboot' bios: ovmf bootdisk: sata0 cores: 1 efidisk0: local-zfs:vm-102-disk-1,size=128K ide2: none,media=cdrom memory: 2000 name: 1-DSM net0: e1000=0E:69:70:F5:F6:5A,bridge=vmbr0 numa: 0 ostype: l26 sata0: local-zfs:vm-102-disk-0,size=20G scsihw: virtio-scsi-pci smbios1: uuid=5493a726-0a20-4c4a-a6c6-53ab7062e8ab sockets: 1 vmgenid: 56e9aba4-ba92-4c3a-80af-73c3a186f5e5 Quote Link to comment Share on other sites More sharing options...
kazuni Posted December 7, 2018 Share #933 Posted December 7, 2018 19 minutes ago, Bar1 said: agent: 1 args: -device 'piix3-usb-uhci,addr=0x18' -drive 'id=synoboot,file=/var/lib/vz/images/102/synoboot.img,if=none,format=raw' -device 'usb-storage,id=synoboot,drive=synoboot' bios: ovmf bootdisk: sata0 cores: 1 efidisk0: local-zfs:vm-102-disk-1,size=128K ide2: none,media=cdrom memory: 2000 name: 1-DSM net0: e1000=0E:69:70:F5:F6:5A,bridge=vmbr0 <- Change the MAC to match the ones from synoboot.img numa: 0 ostype: l26 sata0: local-zfs:vm-102-disk-0,size=20G scsihw: virtio-scsi-pci smbios1: uuid=5493a726-0a20-4c4a-a6c6-53ab7062e8ab sockets: 1 vmgenid: 56e9aba4-ba92-4c3a-80af-73c3a186f5e5 Also, when you boot up, hang the pc to bios and check if the boot order is correct Quote Link to comment Share on other sites More sharing options...
Bar1 Posted December 7, 2018 Share #934 Posted December 7, 2018 4 minutes ago, kazuni said: Also, when you boot up, hang the pc to bios and check if the boot order is correct where do i find the mac address? Quote Link to comment Share on other sites More sharing options...
kazuni Posted December 7, 2018 Share #935 Posted December 7, 2018 Just now, Bar1 said: where do i find the mac address? if you havent' modified the synoboot.img, the common mac Jun will use is 00:11:32:12:34:56 afaicr. Quote Link to comment Share on other sites More sharing options...
Bar1 Posted December 7, 2018 Share #936 Posted December 7, 2018 not working....what synoboot should i be using? Quote Link to comment Share on other sites More sharing options...
marvine Posted December 7, 2018 Share #937 Posted December 7, 2018 Hi guys, Im setting up a new XPE on vmware esxi 6.7. Is there a new VMDK file ready for 1.04b ? Thanks thanks Quote Link to comment Share on other sites More sharing options...
luchuma Posted December 7, 2018 Share #938 Posted December 7, 2018 why do you think there should be new vmdk? thats all you need # Disk DescriptorFile version=1 CID=6ccf51e5 parentCID=ffffffff isNativeSnapshot="no" createType="vmfs" # Extent description RW 102400 VMFS "synoboot.img" 0 # The Disk Data Base #DDB ddb.adapterType = "lsilogic" ddb.deletable = "true" ddb.encoding = "UTF-8" ddb.longContentID = "7e24a756b77e33e24ac940cc6ccf51e5" ddb.thinProvisioned = "1" ddb.uuid = "60 00 C2 9a ee da ca 33-df 5e 04 3f 80 55 f9 62" ddb.virtualHWVersion = "10" 1 Quote Link to comment Share on other sites More sharing options...
marvine Posted December 7, 2018 Share #939 Posted December 7, 2018 Because it hangs here any idea what could be wrong ? I also cant find it on the network Quote Link to comment Share on other sites More sharing options...
luchuma Posted December 7, 2018 Share #940 Posted December 7, 2018 its not problem with vmdk it works proper thats why you see that screen. so you are running 918 loader - what hardware do you have? Quote Link to comment Share on other sites More sharing options...
marvine Posted December 7, 2018 Share #941 Posted December 7, 2018 (edited) Haha okay didnt know that and inside the vmdk do i need to change there something last time i did not change anything? Yes using the latest 918 loader and choose the esxi boot option HPE ML10 with the custom HP image loaded with all drivers I guess i spotted the problem already Networking Host name IP addresses ^^ its empty wich nic type you use ext 3 or e1000 ? Edited December 7, 2018 by marvine Quote Link to comment Share on other sites More sharing options...
luchuma Posted December 7, 2018 Share #942 Posted December 7, 2018 you need to set the same macaddress in synoboot img and vm config Quote Link to comment Share on other sites More sharing options...
marvine Posted December 7, 2018 Share #943 Posted December 7, 2018 Thanks i will adjust that then i guess you mean the Mac adress from the network card ? Quote Link to comment Share on other sites More sharing options...
luchuma Posted December 7, 2018 Share #944 Posted December 7, 2018 check tutorial section, its all there Quote Link to comment Share on other sites More sharing options...
marvine Posted December 7, 2018 Share #945 Posted December 7, 2018 2 minutes ago, luchuma said: check tutorial section, its all there Thanks! will do long time ago hah Quote Link to comment Share on other sites More sharing options...
Captainfingerbang Posted December 7, 2018 Share #946 Posted December 7, 2018 I hate to be this guy but i'm under the weather and need to update DSM to get the update for Moments I'm on DSM 6.2-23739 DS3615xs and want to update to 6.2.1-23824 could someone remind me what loader i need for 6.2.1-23824? Quote Link to comment Share on other sites More sharing options...
dholdi Posted December 7, 2018 Share #947 Posted December 7, 2018 1.03b Quote Link to comment Share on other sites More sharing options...
Captainfingerbang Posted December 7, 2018 Share #948 Posted December 7, 2018 Thanks dholdi Quote Link to comment Share on other sites More sharing options...
Xeno Posted December 7, 2018 Share #949 Posted December 7, 2018 I have successfully downgraded from DSM 6.2.1-23824 back to DSM 6.2-23739 Update 2. Everything is working properly and no more volume crash.. Big thanks to Jun, 1.03b worked perfectly! Also a big thanks to FOXBI for creating this awesome little tool Quote Link to comment Share on other sites More sharing options...
wingspinner Posted December 8, 2018 Share #950 Posted December 8, 2018 Wrt the ds918+ loader that Jun originally started the topic with, works perfectly so far in my system: - HPE ML350 Gen9 - Two E5-2667 V3 processors (Haswell) - 72 gb total memory - on board SATA with Ssd for boot - LSI 3000 series HBA not in pass-through with seven 4TB SAS drives - ESXI6.7 u1 - VM set for 4 processors w/virtualization pass-through enabled, 8gb memory, boot on sata0:0, 35 gb VD on sata0:1, sas drives RDM physical on LSI SCSI Parallel installed as single volume raid 6 BTRFS. Installed latest DSM update. SAS drives appeare on disks 3-9. Everything works just like my real ds918+ except this is much more responsive and uses SAS drives. CPU-info shows 4 processors just as configured. After perusing the sources on github and noticing some code that appeared to restrict the kernel to using only two cores, the one question is can anyone confirm that the kernel will actually use more than two cores? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.