andyf

Can you not get a PC or Mac and create a LAN interface on it that is in the same VLAN (10 shown above). At that point, both the NAS and the 'PC' should be able to see each other?

Sure, I realise they aren't being copied for some reason, but wondered if we knew why, or if anything could be done in the bootloader to fix it? Could we add another grub option to do specifically run a script to do the copying? Not a fix as such but it might make it easier to recover systems in that state.

I've noticed a number of posts recently where people say they attempted an update, but afterwards the system was unreachable, but if they copy the drivers from the update folder to the drivers folder it appears to fix it? I've had similar problems on my G8 a number of times - the update appears to go fine but then the system just vanishes from the network. Usually I end up doing a fresh install and migrating my data, which works fine. Do we know why some updates are failing in this way, and why specifically the copying fixes it? Andy.

Only way I could get my Gen8 to install was to ensure I had set the correct Ethernet MAC matching the actual hardware in the Grub config. If I left the default or tried to use a 'real' MAC I ended up in the repeating loop too.

I'll say this more politely than many people on here might... You cannot do that. Read all the posts. You must Set the PID/VID. You are getting an error that is documented about 100 times on this forum. Read all the posts. This might help too. http://bfy.tw/Arjn

What do you mean by correct MAC? I'm using the same MAC that worked for 5.2 install. However 6 fails with infinite recovery. Thanks a lot! I'm now using the actual hardware MAC that is baked into the network interface rather than the default one that was in the grub config file.

In the end I thought I'd try a fresh install using the same new USB key but a blank data drive, as a test. This failed too, in a similar but different way. Instead of going in to a 'recover' loop, it ended up repeatedly going through the install loop - uploading g the pat file etc. After a reboot it would do the same again. I figured at this point it was something to do with my USB stick. What I had done was to not set the correct MAC addresses when I set the PID/VID. I assumed that they were only if you wanted to use use the Synology DDNS type features.I had left them set to the default values. As soon as I entered the correct MAC values for my hardware it all seemed to go ok - The clean install worked just by rebooting (It had obviously installed ok) and I also managed to the use this to recover the data from my previous 5.2 install. I've never seen it flagged here that it is important to set the MAC addresses correctly. Maybe it was just a coincidence? Andy.

Thanks. I thought I had mentioned but I must have forgotten in my panic... HI, It's a completely standard HP Gen8 G1610T Celeron Microserver, all standard hardware.

Help. I have a HP Gen8 Microserver that has been running 5.2 for a while now. I though 6.x was stable enough to finally bite the bullet and upgrade. The machine is fully loaded, with two pairs of two hard drives, configured as two pairs of Synology RAID units. I followed all the steps outlined in the first post to install 1.01 (Or so I thought). All seemed to go ok, and it allowed me to migrate my settings. However, on final reboot it came back as 'recoverable' in Synology Assistant, with a dynamic IP address. SA shows it as being on Version 6.0.2-8451 currently. Selecting 'recover' just causes a reboot and no change, as people have mentioned on other threads. Can anybody suggest a way that I can either: - Get 6.x to work from my current situation, maintaining my settings and data - Downgrade back to 5.2 (I have the original boot USB stick untouched) - Get 6.x to work as a clean install but not losing any data? I will happily reinstall my apps if I need to, but would rather not lose data if at all possible. Any other options? I assume I can't just switch back to my original boot USB and reinstall..... maybe? Haven't tried that as didn't want to risk breaking it further. Thanks in advance, any help is much appreciated. Andy.

I still don't get it... What are you doing on the Synology that needs so many cores? Is it massive video transcoding, bitcoin mining or something else? If its purely for file serving then surely that isn't CPU bound and 8 cores is plenty, and if it is for 'something else' that is CPU heavy, then surely those tasks could be offloaded to a different VM running on the same bare metal, using all the other cores, either Synology or Linux/Windows? You could use ESXI, and have 3 Synology VM instances, each with 8 cores if you are so tied to Synology, or a single Synology VM with 8 (or less) cores and a linux VM with the other cores to do your other CPU heavy tasks?

If you are set on using Xpenology for your NAS needs Id say a a good solution would be to use the box to virtualise - Run Xpenology as a VM and give it 8 cores if you like (Although I don't really see any need whatsoever for so many just for Xpenology) and then run whatever other VMs you need for whatever it is you want to do with the other spare 16 (or is it 24???) cores! Andy.

I think your deductions are right - I experienced something similar. I originally had an ESXI virtualised setup - USB boot, DSM virtual machine installed onto an SSD. After all booted/installed/updated I added two new 3TB drives and created a SHR volume spanning the two. Long story short, ESXI wasn't stable, so I decided to move to bare metal. Removed the SSD and put in a USB key with the DSM installer and booted. To my surprise, Is booted straight into DSM, and i didn't need to reinstall the DSM software. Can only assume that whenever you create a new Volume in DSM it also installs the DSM software onto it - As somebody else suggested, this is a good form of fault tolerance as it will still boot after losing *any* drive (assuming you have more than 1!)

Thanks for confirming that, I thought I was going mad for a while!

Hi All. Hopefully somebody can explain how this works to me... I had a vanilla setup as outlined on Xpenology.nl using ESXI on an HP Gen8 Microserver. USB Key to boot ESXI, ESXI data store on a 256GB SSD, and a pair of 3TB WD drives mapped through as RDM drives into the Synology install. I did the initial install before the two 3TB drives were added - And the volume on these was created after all the initial DSM install For whatever reason, I couldn't make it stable. Would be fine for an unspecified amount of time, and then the load average would increases, and increase, although CPU/IO/Memory/Disk access were all really insignificant. Eventually it would freeze, and couldn't even be stopped by the ESXI manager. So I decided to scrap ESXI and go bare metal. I installed Xpenoboot onto a new USB key, removed the ESXI boot key and booted Xpenoboot instead. I selected the update/install option and let it run. I then used the Synology assistant to find the device and went to it via the web browser, expecting it to be a initial install page that I had seen before, asking me to upload the main pat file. However, I was greeted with a fully installed DSM unit, with all of the setup that I had in its previous ESXI incarnation, ready for me to log in. My only conclusion was that the DSM files had somehow been moved onto the main 3TB volume, although that wasn't even installed when I originally installed under ESXI. So I guess my question is: Where is the DSM software actually running from? Can I remove the SSD that was used as the ESXI datastore - I can't see how this is possibly being used as it only contained ESXI VMDK/VMX files? Thanks for reading my long and confusing post! Andy.

Because your server has 4 bonded LAN ports but the PC you're pulling the file down onto only has a single Gb port?