bearcat

What happend to your USB bootstick? Make sure your BIOS use USB as Primary (or only) bootmedia. Try the USB stick in another computer, to make sure it's still bootable.

Ok, to me your question seems a bit "unspecific" so I have to ask: what is you want to do, that your are not beeing able to do? Are you looking for a way to connect to your NAS and it services from the "outside"? That will be hard to do, as your "external" IP is actually a "internal" IP and you have no access to manually forward ports in your ISP's router (if I get you right). Will it be of any help if you are able to have a "Remote Desktop" way into your DSM ? There is a TeamViewer App for Synology that might work for you.

@flo89 Cool When you say updated, I take it as you flashed a new BIOS, what version did you install? (and what version did you have?) The 1.04b loader has so far been built to be used with the DS918+ "clones", the microserver G7 is not compatible for now, due to restricsions on hardware/drivers working with it. AMD vs. Intel CPU is 1 of the problems. I can see that @Lestat tried, with no luck.

Oops, my mistake, there is no physical serial port on the G7

@flo89 Most users of the Microserver G7 are using a "hacked" version of the BIOS, to be able to set all drives, including the 1 designed for ODD as AHCI, 3GB/s. Personally I'm using the one released by "TheBay", it's old but proven to work. btw: 1 change you must make in your BIOS, is to disable "C1" edit: if disabled, also enable the serial port in BIOS. you should be able to see more output by using a serial cable connected to the server and a terminal program.

@roadx 🔫 Bang 🔫 Bang just kidding, that's true AMD could have been an issue but it should not be it in this case. In my home, I have 4 running G7 Microservers (and 1 G8), 1 N40L like flo89, and 3 N54L, basicly the same computers, with the 54 using a slightly faster AMD CPU. And I'm not the only one, as can bee seen ie. here where Lestat have been successfully updating to DSM 6.2-23739 Update 2 from DSM 6.1.7 15284, based on Jun's loader v1.03b - DS3615xs, baremetal, no extra.lzma used. So with 1.03b as a base, flo89 should be able to find his N40L on the network after the first boot, then manually provide the .pat and install DSM 6.x @flo89 : Are you using the original or modified BIOS?

@flo89 That's very strange... are you sure your cable is working, and your grub.cfg is correct?

@klutch14u : I might be "swearing in the church", but have you considered using anyting else as a Virtual NFS server? "Back in the days", when I attended an ESXi course, we used Openfiler as an application to host NFS and iSCSI storage to be used for Vmotion. They have a VMware appliance download available here. I know, it's getting old and looks like its abandoned, but it worked great at the time we used it.If you have time to "play around", I guess most Linux based servers can be set up as a Virtual NFS server. edit: BTW: I think I remember I had better NFS performance on my HP N54L (baremetal) while using DSM 5.2 than after I updated to DSM 6.2, so if you make a new VM, with DSM 6.x, you should compare with your current one.

I'm not sure how well you know the "Virtual World", but lets just "KISS" (as I don't have time/patience to make you understand the difference on physical and virtual components, lets just say: anything anyone can bang there head into , is physical ) Yes, change the the wmware settings to e1000e instead of the e1000 you have been using on your VM for the NAS.

@flo89 Stay with the 1.03b DS3615xs, verify that you have edited your "grub.cfg" correctly. Then you *should* get an IP adress, (as all others who are using the Microserver G7) and can manually install DSM 6.2 (but make sure you do NOT update to 6.2.1!) If you can "live" with the good and stable DSM 6.1.7, you can use 1.02b, DS3615xs instead (with no risk of updating->BRICK).

This is how I have done it: 1 - Prepare a new USB bootstick. (what version do you have, and what will you be using next? ) 2 - Download the .pat file you are going to use (to do a manual installation later on) 3 - Uninstall any extra packages form the Package Center 4 - Delete all users (but NOT the admin user) 5 - Power down your NAS 6 - Replace the connected USB bootstick with the new one 7 - Boot for the new USB bootstick 8 - "Find" you NAS, manually install your .pat 9 - "Migrate" your disks, if asked: delete all settings, keep data. 10 - Start messing it up again ;-D Attention: by doing it like this, you can't make any changes to your Raid setup, Volumes or filesystems. disclaimer: before doing anything of the above, make sure you have validated backups of all your files, in at least 3 physical locations '

@ExSL so if I get you correctly,: you could not activate CSM when you where in Legacy mode? You can only activate CSM when in UEFI mode, and with any of those 2 combinations you are not able to connect to the DHCP server? @hoidoi Since I'm referring to a post you made, I tagged you and hope you can shed some light on this Like, what BIOS version are you running on the Gen10?

@marvine Actually, those are NOT physical nic's, they are drivers for your virtual nic's, used by your VM, but YES that is the driver you need to change for the virtual nic (or nics) you are using for your Virtual XPEnology NAS. If you have only 1 vnic in your VM, then that is the one to change.

The virtual nic, used for your virtual machine. As noted here that's what you need to use in ESXi if your are on DSM 6.2.1 or highter.

@marvine Try change your vnic from E1000 to E1000E

@Eduardo From what I have read in here, Jun's 1.03 and DS3617xs seems to be working with DSM 6.2 on the Gen 10, if you add a supported Intel based nic, you can use 6.2.1 update 2 (the current "latest and greatest").

@ExSL Hello, and welcome It would be helpfull if you posted what version of the bootloader and DSM you have tried. According to this post, you can try Jun's bootloader v1.03b, with DS3615xs or DS3617xs with either DSM 6.1.7 or DSM 6.2. But as the same user have posted : "I changed the boot type from UEFI to Legacy and activated CSM. After this, the NAS was visible. My HP Gen10 Microserver runs Loader 1.03b and DS3617xs." so you might have to check your BIOS setting for this.

@startouch1 What do you use as vnic? If not e1000e, try it

The Asus P10S-M WS have 8 integrated SATA ports + 1 M.2, I guess thats why. If you need all 8 porst for HDD, then you must add an extra SATA controller to connect "normal" SSDs to use as cache.

@ilteris: I see your nic, RTL8110SC, beeing mentioned here So I guess you must try jun's 1.02b bootloader and inject the "extra.lzma", (how-to can be found in the forums). Try first the one based on DS3615, and manually install DSM 6.1.x

@J0hnny Seems like you need to use DS918+ if you want to use NVMe cache.

@J0hnny On what port on your mainboard is the SSD connected ?

@Gohrilla : normally, when adding a drive to a storage pool, the "wizzard" will automaticly expand the volume with the available free space. Sometimes you may have to manually expand it. But, when using SHR, as can see in the Raid Calculator I linked to above, there are some things, due to SHR, that will limit the available space. Currently you should have 19TB available space, 8TB beeing used as "protection" and 2TB are "wasted" unused space, all due to SHR. (if we round up the numbers shown in your pic's, it all add's up, some space on each disk is used for system/swap).

@Gohrilla : This is because you are using SHR on that pool, and its normal. edit: do you have a picture of the "Volume" info? Did you try there to expand your volume?

@MrJonesiii : you can use the DSM 6.2 with your current internal nic, but it will nag you to install 6.2.1 and if you do, your out of luck... So, your way to start with the N54L, and an Intel-based nic, will be a safe and good path to follow