Dfds

If you mean can you use the USB as the boot loader & data storage then no you can't.

Have you tried backing up the configuration, I can't remember if it includes download station but it's worth a try.

The bootloader image is only 15mb, hence the 15mb partition. Why do you want to expand the partition anyway, it's not really useable.

I believe SABNZBD will prevent the HDD's spinning down.

Yes, just put that image on a USB and boot from it.

There was an issue with expanding SHR arrays with 5.1 which seems to have been solved with a test build from sancome, see page 3 about halfway down this thread for the image. viewtopic.php?f=2&t=5233&start=20

Sorry Poechi, it's not working for me.

It depends on how you have presented the disks to ESX1, if you used RDM then you should be able to create a USB drive based on the same version of xpenology you were using in ESXi & boot from it. However if you used VMDK file you will probably need to backup your files & restore manually.

Don't worry about the format of the old USB, just use something like win32diskimager to create a new one USB.

I can't help you with Hyper-V & I think most people are either running bare metal or ESXi, I've run both & not had the issues you have.

You might want to try reading through the forums before posting, if you had you would know that DSM 5.1 hasn't been implemented in Xpenology yet. Various people on here are working on it & will hopefully get it working, till then DSM 5.0 is as far as you can go.

As I said a screen shot would help.

I don't think you'll get the extra space just by upgrading one disk, I believe you will only get the extra space by upgrading 2 or more disks.

SHR & Raid 5 are the same, did you have a look at the calculator I linked to, a screenshot from storage manager/volume would probably help.

Are you sure you're using SHR & not raid 1. According to the Synology raid checker the amount of free space you have is correct for a raid 1 array, 3 of your disks are being used for protection & only 1 for data. https://www.synology.com/en-us/support/RAID_calculator

If you're intending to run in a commercial environment you really should purchase genuine Synology hardware, that way you have access to Synology support & all the latest updates.

What hardware platform & version of DSM are you trying to install?

Thanks to everyone who is working on getting 5.1 to work your efforts are appreciated, enjoy the holidays with your loved ones 5.1 can wait for a while. I hope you all have a great Christmas & a Happy New Year

If you're running under ESXi none of these things work or show correctly, it's a known problem & can't be fixed. If they're important to you need to run bare metal. I'd also suggest that you do a bit of reading on the forums to familiarise yourself a bit more with Xpenology.

Hi Wenlez, I'm not sure if having the disks as JBOD would make any difference, but the only way to know for sure would be to test it out.

Sadly there isn't any way round this as DSM wasn't deigned to work that way.

Happy to help test on either ESXi or N54L bare metal if needed.

Let the virtual server handle the disks.

X64/DS3612xs

Try adding the following to /etc.defaults/ddns_provider.conf [123-reg.co.uk] modulepath=DynDNS queryurl=www.123-reg.co.uk/api/?hostname=__HOSTNAME__&myip=__MYIP__ I can't guarantee it will work, but it's worth a try.