Jump to content
XPEnology Community

Working DSM 6


oktisme

Recommended Posts

It will work on real hardware with the ISO as long as you have fully compatible hardware out-of-box. Drivers cannot be added without the kernel source. Few network cards are compatible but you can try.

Where can we check the full list of compatible hardware? In addition to the network card, what would be the other crucial hardware components to make this work? I take it the cpu and raid controller would be in that list.

 

Only the network card that is giving people trouble. CPU and raid controller (must be in IT mode if you use an add-in card) are invisible to the OS so DSM doesn't care - note how xpenology always mis-id the CPU/core? it's because the value strings are hard coded, not read off of the actual CPU.

Thanks Dynax. Do we have a full list of DSM 6 out-of-box compatible network cards?

For e1000e, based on the following link, these NICs should run fine. I have one setup with Intel 82579LM so I just might be in luck.

 

https://downloadcenter.intel.com/download/15817

Intel® 82573L Gigabit Ethernet Controller

Intel® 82572EI Gigabit Ethernet Controller

Intel® 82571EB Gigabit Ethernet Controller

Intel® 82573E Gigabit Ethernet Controller

Intel® 82573V Gigabit Ethernet Controller

Intel® 82567 Gigabit Ethernet Controller

Intel® 82574L Gigabit Ethernet Controller

Intel® 82566MM Gigabit Ethernet PHY

Intel® 82566MC Gigabit Ethernet PHY

Intel® 82566DM Gigabit Ethernet PHY

Intel® 82566DC Gigabit Ethernet PHY

Intel® 82563EB Gigabit Ethernet PHY

Intel® 82574IT Gigabit Ethernet Controller

Intel® 82583V Gigabit Ethernet Controller

Intel® 82579LM Gigabit Ethernet PHY

Intel® Gigabit CT Desktop Adapter

Intel® PRO/1000 PF Dual Port Server Adapter

Intel® PRO/1000 PF Quad Port Server Adapter

Intel® PRO/1000 PF Server Adapter

Intel® PRO/1000 PT Desktop Adapter

Intel® PRO/1000 PT Dual Port Server Adapter

Intel® PRO/1000 PT Quad Port Low Profile Server Adapter

Intel® PRO/1000 PT Quad Port Server Adapter

Intel® PRO/1000 PT Server Adapter

Intel® 82579V Gigabit Ethernet PHY

Intel® 82577LC Gigabit Ethernet PHY

Intel® 82577LM Gigabit Ethernet PHY

Intel® 82578DC Gigabit Ethernet PHY

Intel® 82578DM Gigabit Ethernet PHY

Intel® Ethernet Connection I217-LM

Intel® Ethernet Connection I217-V

Intel® Ethernet Connection I218-V

Intel® Ethernet Connection I218-LM

Link to comment
Share on other sites

Accoring dmesg, dsm6 uses version 3.1.0.2 of e1000e.ko:

[ 21.114377] e1000e: Intel® PRO/1000 Network Driver - 3.1.0.2-NAPI

[ 21.115449] e1000e: Copyright© 1999 - 2014 Intel Corporation.

[ 21.116475] e1000e 0000:03:00.0: Disabling ASPM L0s L1

[ 21.118093] e1000e 0000:03:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode

[ 21.119842] e1000e 0000:03:00.0: irq 73 for MSI/MSI-X

[ 21.223181] e1000e 0000:03:00.0 eth0: registered PHC clock

[ 21.224112] e1000e 0000:03:00.0 eth0: (PCI Express:2.5GT/s:Width x1) 00:0c:29:b4:4a:d1

[ 21.225487] e1000e 0000:03:00.0 eth0: Intel® PRO/1000 Network Connection

 

https://downloadcenter.intel.com/downlo ... der-Linux-

Link to comment
Share on other sites

[spoiler=ls /lib/modules]8021q.ko carl9170.ko freq_table.ko l2tp_core.ko pci-stub.ko snd-mixer-oss.ko veth.ko

8188eu.ko cbc.ko ftdi_sio.ko l2tp_ppp.ko ppp_async.ko snd-page-alloc.ko vfat.ko

8192cu.ko cdc-acm.ko fuse.ko lfdd_drv.ko ppp_deflate.ko snd-pcm.ko vhost.ko

8812au.ko cdc_ether.ko gf128mul.ko libcrc32c.ko ppp_generic.ko snd-pcm-oss.ko vhost_net.ko

8821au.ko cfg80211.ko glue_helper.ko libiscsi.ko ppp_mppe.ko snd-rawmidi.ko vhost_scsi.ko

ablk_helper.ko cifs.ko gre.ko libiscsi_tcp.ko pppoe.ko snd-seq-device.ko xfrm4_mode_beet.ko

acpi-cpufreq.ko cls_fw.ko hfsplus.ko llc.ko pppox.ko snd-timer.ko xfrm4_mode_transport.ko

adt7475.ko cls_u32.ko hid-generic.ko loop.ko ppp_synctty.ko snd-usb-audio.ko xfrm4_mode_tunnel.ko

aesni-intel.ko compat.ko hid.ko lrw.ko pptp.ko snd-usb-hiface.ko xfrm4_tunnel.ko

aes-x86_64.ko compat_xtables.ko hidp.ko mac80211.ko processor.ko snd-usbmidi-lib.ko xfrm6_mode_beet.ko

af_key.ko cpufreq_conservative.ko hmac.ko macvlan.ko psnap.ko soundcore.ko xfrm6_mode_transport.ko

ah4.ko cpufreq_ondemand.ko i2c-algo-bit.ko md4.ko quota_tree.ko stp.ko xfrm6_mode_tunnel.ko

ah6.ko cpufreq_performance.ko i2c-i801.ko md5.ko quota_v2.ko synoacl_vfs.ko xfrm6_tunnel.ko

amifldrv_mod.o cpufreq_powersave.ko i40e.ko mdio.ko r8712u.ko synobios.ko xfrm_algo.ko

ansi_cprng.ko cpufreq_stats.ko igb.ko mlx4_core.ko rfcomm.ko syno_extent_pool.ko xfrm_ipcomp.ko

appletalk.ko crc32c-intel.ko ioatdma.ko mlx4_en.ko rodsp_ep.ko syno_flashcache_control.ko xfrm_user.ko

arc4.ko crc-ccitt.ko ip6table_filter.ko mlx_compat.ko rpcsec_gss_krb5.ko target_core_ep.ko xhci-hcd.ko

ath3k.ko crc-itu-t.ko ip6table_mangle.ko mperf.ko rt2800lib.ko target_core_file.ko x_tables.ko

ath9k_common.ko cryptd.ko ip6_tables.ko mpt2sas.ko rt2800usb.ko target_core_iblock.ko xt_addrtype.ko

ath9k_htc.ko cts.ko ipcomp6.ko nf_conntrack_ipv4.ko rt2x00lib.ko target_core_mod.ko xt_conntrack.ko

ath9k_hw.ko dca.ko ipcomp.ko nf_conntrack_ipv6.ko rt2x00usb.ko tcm_loop.ko xt_geoip.ko

ath9k.ko deflate.ko ip_set_hash_ip.ko nf_conntrack.ko rtl8187.ko thermal_sys.ko xt_iprange.ko

ath.ko des_generic.ko ip_set.ko nf_conntrack_pptp.ko rtl8192c-common.ko tn40xx.ko xt_limit.ko

aufs.ko dm-snapshot.ko iptable_filter.ko nf_conntrack_proto_gre.ko rtl8192cu.ko tun.ko xt_LOG.ko

authencesn.ko drbd.ko iptable_mangle.ko nf_defrag_ipv4.ko rtl_usb.ko tunnel4.ko xt_mac.ko

authenc.ko e1000e.ko iptable_nat.ko nf_defrag_ipv6.ko rtlwifi.ko tunnel6.ko xt_mark.ko

backports_dvb ecb.ko ip_tables.ko nf_nat_ipv4.ko sch_htb.ko udf.ko xt_multiport.ko

bcm203x.ko ecryptfs.ko ipt_MASQUERADE.ko nf_nat.ko sch_netem.ko uhci-hcd.ko xt_nat.ko

be2net.ko eeprom_93cx6.ko ip_tunnel.ko nf_nat_pptp.ko sch_sfq.ko usb-common.ko xt_NFQUEUE.ko

bfusb.ko ehci-hcd.ko ipv6.ko nf_nat_proto_gre.ko sg.ko usbcore.ko xt_recent.ko

bluetooth.ko ehci-pci.ko iscsi_target_mod.ko nfnetlink.ko sha1_generic.ko usbhid.ko xt_REDIRECT.ko

bnx2x.ko esp4.ko iscsi_tcp.ko nfnetlink_queue.ko sha256_generic.ko usbip-core.ko xt_set.ko

bonding.ko esp6.ko iscsi_trgt.ko nfsd.ko sha512_generic.ko usbip-host.ko xt_state.ko

bpa10x.ko etxhci-hcd.ko isfl_drv_x64.ko n_hdlc.ko sierra.ko usblp.ko xt_TCPMSS.ko

bridge.ko exportfs.ko isofs.ko openvswitch.ko sit.ko usbnet.ko xt_tcpudp.ko

bsd_comp.ko fat.ko ixgbe.ko option.ko slhc.ko usbserial.ko zd1211rw.ko

btrfs.ko flashcache.ko kvm-intel.ko output.ko snd-hwdep.ko usb-storage.ko zlib_deflate.ko

btusb.ko flashcache_syno.ko kvm.ko p8022.ko snd.ko usb_wwan.ko zram.ko

 

 

nic:

be2net.ko (hp),

e1000e.ko: Intel® PRO/1000 Network Driver - 3.1.0.2-NAPI

i40e.ko: intel® Ethernet Connection XL710 Network Driver - version 1.3.47

igb.ko: Intel® Gigabit Ethernet Network Driver - version 5.2.17

ixgbe.ko: Intel® 10 Gigabit PCI Express Network Driver - version 4.3.13

tn40xx.ko: ITehuti Network Driver, 0.3.6.11.2

bnx2x.ko: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 1.713.00

 

wlan: rtl8187.ko, rtl8192c-common.ko, rtl8192cu.ko, rt2800lib.ko, r8712u.ko, zd1211rw,ath3k.ko, ath9k.ko, carl9170.ko

storage: mpt2sas.ko (LSI) version 20.00.00.00

 

Those are the kernel modules i could identify (more or less)

Edited by Guest
Link to comment
Share on other sites

I managed to launch DSM 6 with iso image in virtualbox. Every reboot I have to select Install option. BTRFS seems to work after manual mount /dev/vg1/volume_1 /volume1.

 

How do You use img image, to install? - in my installations, boot-vmdk is overwritten, and I cannot boot.

Edited by Guest
Link to comment
Share on other sites

Hi everybody !

 

I'm new here, I'm following this thread for a while and today I'm succesfully running DSM 6 Update 1 in a virtual machine (dedicated server with Proxmox).

I'm using ISO pat files from hawie/okstime (see here : viewtopic.php?f=2&t=16114&start=210#p67587)

 

It only works in "install" mode, but it's working fine for now. And BTRFS doesn't work, only EXT4.

 

Before I was running DSM 5.2 for a while, in Proxmox too, with a ISO file for booting too, and it works flawlessly.

 

Well, this is pretty great. My Dell Optiplex 780 just so happens to be generic enough that I am confirmed booting bare metal to a 100% working DSM 6. The only BIOS setting I had to change was switching SATA operation from legacy (default) to RAID On. From there, I booted the flash drive I placed the latest .img on and booted from "install." Incredible how fast this boots...seriously, from power off to active network connection it was only a few seconds. From there, find.synology.com, upload the pat file, restart and let it use the "run" option. This boot took a little longer as it did the install list. After that was finished I sat at the "system is getting ready" progress bar. I thought this was the point of no return, but after waiting about two minutes it greeted me with the welcome screen! Entered a server name, username, password, etc and finished setup. Created a BTRFS volume (SHR, btrfs) and had the immediate crash issue as others have described. More on this in a moment. Then I ran (successfully) Update 1 from the Control Panel. Then enabled SSH. Logged into SSH and ran: mount /dev/vg1000/lv /volume1 and voila! There's my BTRFS volume mounted with no errors/issues. Created a new shared folder and verified everything is working as it should. Very...very cool.

 

Control Panel Update & Restore:

http://imgur.com/J9yHW7C

 

Control Panel Info Center:

http://imgur.com/WxdycQw

 

Storage Manger/Volume:

http://imgur.com/6vWBTCj

 

Thanks for your post !

 

I tried the command "mount /dev/vg1000/lv /volume1" and it seems the volume is mounted with no error. But I tried to use the "Snapshot replication" app and tried to make a snapshot, but it doesn't work :sad:

Here is what the /var/log/messages says :

 

Jul 18 21:39:54 DSM6test synoscgi_SYNO.Core.Share.Snapshot_1_create[28411]: snapshot_create.c:122 Faild to create subvolume /volume1/@sharesnap/Documents/GMT+02-2016.07.18-21.39.54.

Jul 18 21:39:54 DSM6test synoscgi_SYNO.Core.Share.Snapshot_1_create[28411]: snapshot_create.c:316 Failed to create snapshot

[0x2A00 snapshot_create.c:123]

 

Did you try this ?

 

 

(Sorry for my english ...)

Link to comment
Share on other sites

Not sure if it was confirmed yet but I've been able to install DSM6 on my HP Micro N36L using "Install" and "Run" works after a reboot, including the built in NIC. You still have to manually mount the BTRFS volume after a reboot but otherwise it's working. I've been able to install several packages (VPN, Cloudsync, MariaDB, Webserver) and all seem to be working fine. Only issue is after a reboot, the volume is crashed (unmounted) so all of the packages will fail to start until it's manually mounted again.

Edited by Guest
Link to comment
Share on other sites

Hi everybody !

 

I'm new here, I'm following this thread for a while and today I'm succesfully running DSM 6 Update 1 in a virtual machine (dedicated server with Proxmox).

I'm using ISO pat files from hawie/okstime (see here : viewtopic.php?f=2&t=16114&start=210#p67587)

 

It only works in "install" mode, but it's working fine for now. And BTRFS doesn't work, only EXT4.

 

Before I was running DSM 5.2 for a while, in Proxmox too, with a ISO file for booting too, and it works flawlessly.

 

Well, this is pretty great. My Dell Optiplex 780 just so happens to be generic enough that I am confirmed booting bare metal to a 100% working DSM 6. The only BIOS setting I had to change was switching SATA operation from legacy (default) to RAID On. From there, I booted the flash drive I placed the latest .img on and booted from "install." Incredible how fast this boots...seriously, from power off to active network connection it was only a few seconds. From there, find.synology.com, upload the pat file, restart and let it use the "run" option. This boot took a little longer as it did the install list. After that was finished I sat at the "system is getting ready" progress bar. I thought this was the point of no return, but after waiting about two minutes it greeted me with the welcome screen! Entered a server name, username, password, etc and finished setup. Created a BTRFS volume (SHR, btrfs) and had the immediate crash issue as others have described. More on this in a moment. Then I ran (successfully) Update 1 from the Control Panel. Then enabled SSH. Logged into SSH and ran: mount /dev/vg1000/lv /volume1 and voila! There's my BTRFS volume mounted with no errors/issues. Created a new shared folder and verified everything is working as it should. Very...very cool.

 

Control Panel Update & Restore:

http://imgur.com/J9yHW7C

 

Control Panel Info Center:

http://imgur.com/WxdycQw

 

Storage Manger/Volume:

http://imgur.com/6vWBTCj

 

Thanks for your post !

 

I tried the command "mount /dev/vg1000/lv /volume1" and it seems the volume is mounted with no error. But I tried to use the "Snapshot replication" app and tried to make a snapshot, but it doesn't work :sad:

Here is what the /var/log/messages says :

 

Jul 18 21:39:54 DSM6test synoscgi_SYNO.Core.Share.Snapshot_1_create[28411]: snapshot_create.c:122 Faild to create subvolume /volume1/@sharesnap/Documents/GMT+02-2016.07.18-21.39.54.

Jul 18 21:39:54 DSM6test synoscgi_SYNO.Core.Share.Snapshot_1_create[28411]: snapshot_create.c:316 Failed to create snapshot

[0x2A00 snapshot_create.c:123]

 

Did you try this ?

 

 

(Sorry for my english ...)

 

 

I have the same issue when I try to take a Snapshot using Snapshot replication

Link to comment
Share on other sites

Hey y'all,

 

Someone said he'd rather be lucky than good. When it comes to 'results' I suppose some great discoveries happened by accident and I'm not saying that this is one of those. Heck

I don't even want to repeat the process in order to say it's repeatable so I'm just going to post it here and leave it up to someone who's bored enough to give it a try. I'm sure the techies in here could easily explain the why....

 

You see--the main reason I had wanted to upgrade to DSM6 was to see btrfs at work in my ESXi setup but no matter what I tried I was unsuccessful. I have a Lenovo TS140 stock which I just added a cheap marvell IO SATA controller and hooked up a couple of 3TB drives and a couple of SSDs hooked up to the onboard ATA controller. I had been using ESXi6 as my only OS with several VMs including DSM5 and the recently installed DSM6 courtesy of this thread (no real significant data stored, just media files managed by PLEX running in DSM).

 

Seeing a post of a successful bare metal install here, I decided to try to see if I could do the same. So I disabled the SSD in BIOS where ESXi6 and all the VMs (so I didn't have to re-install everything again) are installed and sure enough I was able to configure DSM6 (by that I meant using the 'INSTALL' option only). I proceeded to create a SHR-BTRFS volume out of the pair of 3TB drives and as expected it crashed the volume immediately after. I tried to manually mount the volumes as suggested in the posts and it didn't work for me. For some reason it couldn't find the volume1 folder as mount point. Long story short, I gave up, re-enabled the ESXi boot drive and rebooted back to my ESXi6 and powered up the VMs. Now the DSM6-VM had those same pair of 3TB in a SHR-EXT4 configuration (using PCIe passthrough). And I fully anticipated a crashed volume because of the failed bare metal install which is what I got; but lo and behold, this time it gave me a REPAIR option! Which I promptly clicked on and voila--I have a fully working SHR-BTRFS volume in my DSM6 VM which was what I had been wanting in the first place! I guess the VM just mounted the volume correctlu since it was passthrough....

 

:mrgreen:

Link to comment
Share on other sites

Sorry but I'm getting a bit confused with all the different responses. Can someone confirm that everything works in a baremetal setup as long as the hardware (mainly the NIC) is compatible (brtfs, volumes mounting, SHR, updatable os, packages install, etc.) ?

If it does, can I politely ask to write a step-by-step instructions including the proper img and pat files to download?

Link to comment
Share on other sites

Sorry but I'm getting a bit confused with all the different responses. Can someone confirm that everything works in a baremetal setup as long as the hardware (mainly the NIC) is compatible (brtfs, volumes mounting, SHR, updatable os, packages install, etc.) ?

If it does, can I politely ask to write a step-by-step instructions including the proper img and pat files to download?

 

From what stout has said, He has baremetal DSM6 working. This includes btrfs but only with MANUALLY mounting the Volume first (this would need to be done at every boot). It seems he has official packages installing however I'm not sure about community ones.

 

Perhaps @cstout could post his steps including the .img and .pat files he used to get his working?

I have a similar machine at home that I might try with - providing enough of it works.

Link to comment
Share on other sites

So I installed the DSM 6 directly to the PC, which I use on DSM5. Everything works fine except for the ability to create something other than SHR. But that's okay, I do not need another disc format. Thank community.

Link to comment
Share on other sites

So I installed the DSM 6 directly to the PC, which I use on DSM5. Everything works fine except for the ability to create something other than SHR. But that's okay, I do not need another disc format. Thank community.

 

What hardware do you have, Specifically NIC?

What .img did you use on the boot USB?

 

Also, What is 'Everything Works'? QuickConnect, Community Packages, etc?

Link to comment
Share on other sites

Today I've attempted a baremetal install on my box with a NIC (Intel 82579LM) that should be compatible with e1000e driver but right after I boot from the USB and select install option it freezes on the following screen:

2016_07_19_00h30_34.png

 

As per Cstout, I've tried changing the SATA mode in the BIOS to RAID without any luck.

I used the following IMG (DSM_DS3615xs_7393_boot.img) file posted by Dynax on page 24:

https://mega.nz/#!w9RkULAR!3_Hhvp7yX3kcPEnl36xFFoJQP-OzBOQsfkRBzxw1ONY

 

Also, I've tried to make a bootable USB out of the ISO (DSM_DS3615xs_7393.iso) posted by Oktisme (page 22) with Rufus and it froze on the same screen shown above.

https://mega.nz/#!5UFiAYAR!KVy46LyxA73XlJE50eD3SriE2XbVMF-AyGQ2CRFhfVs

 

Any idea how to get past this? Maybe those four Tux pictures mean something? lol

Link to comment
Share on other sites

I finally got DSM 6.0 working properly on ESXi 5.5. Brtf works w/o manual re-mount. Snapshot works. vmware-tool works (community packages). Update via web GUI to 6.0u1 also works. I had to use PCI pass-through to get the NIC to work properly. Make sure your NIC is in the support list. Mine is 82574L

There are a few waiting periods so DSM takes a while to come up. Just keep an eye on your CPU usage, when you see the CPU begins to get utilized then the loading process is almost done.

Hardware version is 10. Boot drive id IDE 0:0. In ESXi 5.5u1, you'll need to use PCI pass-thru for the supported NIC. Point this IDE drive to the vmdk file. Then upload the pat file for installation, then use the web gui to update to u1. On my test machine, I have another smaller SATA drive (don't forget the SATA part in VM hardware) to install DSM onto for testing.

 

vmdk:

https://mega.nz/#!Vl5zAZaK!f3vf8gK1NfQE ... MK8udUT5J4

 

pat file:

https://mega.nz/#!5xQTwZ4C!yyxSLcGPHHZ8 ... kzHWAm5zvs

 

setup screen shots:

https://mega.nz/#!98p11YbS!l55cnw-3G6d8 ... pWle1zh3uQ

Link to comment
Share on other sites

Today I've attempted a baremetal install on my box with a NIC (Intel 82579LM) that should be compatible with e1000e driver but right after I boot from the USB and select install option it freezes on the following screen:

2016_07_19_00h30_34.png

 

As per Cstout, I've tried changing the SATA mode in the BIOS to RAID without any luck.

I used the following IMG (DSM_DS3615xs_7393_boot.img) file posted by Dynax on page 24:

https://mega.nz/#!w9RkULAR!3_Hhvp7yX3kcPEnl36xFFoJQP-OzBOQsfkRBzxw1ONY

 

Also, I've tried to make a bootable USB out of the ISO (DSM_DS3615xs_7393.iso) posted by Oktisme (page 22) with Rufus and it froze on the same screen shown above.

https://mega.nz/#!5UFiAYAR!KVy46LyxA73XlJE50eD3SriE2XbVMF-AyGQ2CRFhfVs

 

Any idea how to get past this? Maybe those four Tux pictures mean something? lol

 

when you get to that screen, go to http://find.synology.com (or synology assistant) to continue with the setup. Either way brtf is not working on my boot file. See my above post for a better more complete setup.

Link to comment
Share on other sites

Sorry but I'm getting a bit confused with all the different responses. Can someone confirm that everything works in a baremetal setup as long as the hardware (mainly the NIC) is compatible (brtfs, volumes mounting, SHR, updatable os, packages install, etc.) ?

If it does, can I politely ask to write a step-by-step instructions including the proper img and pat files to download?

 

From what stout has said, He has baremetal DSM6 working. This includes btrfs but only with MANUALLY mounting the Volume first (this would need to be done at every boot). It seems he has official packages installing however I'm not sure about community ones.

 

Perhaps @cstout could post his steps including the .img and .pat files he used to get his working?

I have a similar machine at home that I might try with - providing enough of it works.

 

I just used the last link from @dynax for the .img:

https://mega.nz/#!w9RkULAR!3_Hhvp7yX3kc ... kRBzxw1ONY

 

I used the pat from @oktisme:

https://mega.nz/#!sQlWSC5C!tgGduyY5bze3 ... 87PrPkx4fc

 

Yes, BTRFS only with manually mounting the volume: same issue everybody seems to be having currently.

 

I currently don't have time to write up a more detailed step-by-step, but if your'e familiar with the bare metal process from v5 just follow my rough outline of steps from my last post and use the files I linked above and you'll be in business (if your hw is compatible). Hope this helps!

 

I've only tested official packages (all working) and I don't currently use any community packages.

Link to comment
Share on other sites

Thanks Dynax for the updates. I might take the ESXi 5.5 path if it's all working for you.

In xpenboot 5.2 i didn't see this screen with four Tux and that's what threw me off. I was anle to connect to it through find.synology.com and complete the setup. Next I updated DSM to the latest version. As soon as I attempted to create SHR with brtfs it crashed but running the manual mount command as root via SSH fixed it instantly. I was then able to create a new share and install some packages. However, many packages wouldn't install due to missing pgsql. Then I restarted DSM and volume crashed again. Once again, the manual mount command fixed it but my share was gone. :cry:

Therefore this procedure doesnt seem to be valid for production setup. I will test ESXi workaround from Dynax and let you know.

Link to comment
Share on other sites

Thanks Dynax for the updates. I might take the ESXi 5.5 path if it's all working for you.

In xpenboot 5.2 i didn't see this screen with four Tux and that's what threw me off. I was anle to connect to it through find.synology.com and complete the setup. Next I updated DSM to the latest version. As soon as I attempted to create SHR with brtfs it crashed but running the manual mount command as root via SSH fixed it instantly. I was then able to create a new share and install some packages. However, many packages wouldn't install due to missing pgsql. Then I restarted DSM and volume crashed again. Once again, the manual mount command fixed it but my share was gone. :cry:

Therefore this procedure doesnt seem to be valid for production setup. I will test ESXi workaround from Dynax and let you know.

 

Try this img for bare metal. Your Nic is in the support list, it should work.

 

https://mega.nz/#!E1JnjJZa!fDv55PFxgH0i ... VHvT3YpUZo

 

There are 2 places to load the drivers (at boot time and after boot time). I am wondering if anyone is looking at the later approach. People used it too add a secondary unsupported Nic to DSM 5.x previously (but no one has tried that with a primary Nic)

Link to comment
Share on other sites

Hi guys, my setup on esxi 6.0 works like a harm, even btrfs without a problems, at least Web gui don't shows any, didn't check logs. But I'm having problems with docker dsm and virtual dsm manager. With docker dsm I can configure and start new dsm6 but Web gui shows me blank page. With virtual dsm Manger is problem, when I create virtual dsm I can't start it, I can't delete it, nothing works here.

 

Few other packages checked and works, except Mongodb, let's encrypt works great. New Web server package looks great, mailsplus server with mailplus client also looking good.

Link to comment
Share on other sites

Man, you're on fire Dynax. I will test the latest img in baremetal today. Between running baremetal and on ESXi, what are the main advantages of each? I would assume the only reason to go with hypervisor is to run multi environments but there is probably also a noticable performance hit vs baremetal, correct? Also, why not go with the latest esxi 6? Looks like Chege had good luck with it.

@Chege: which img did you use?

Link to comment
Share on other sites

Man, you're on fire Dynax. I will test the latest img in baremetal today. Between running baremetal and on ESXi, what are the main advantages of each? I would assume the only reason to go with hypervisor is to run multi environments but there is probably also a noticable performance hit vs baremetal, correct? Also, why not go with the latest esxi 6? Looks like Chege had good luck with it.

@Chege: which img did you use?

I had it working on ESXi6 as well. However my CPU didn't support vt-d so I couldn't pass through my disks to the vm and I didn't want to create volumes using my disks.

 

I didnt use an IMG to set it up though. I used the ovf files backbon page 7. It worked great (except for quickconnect). Everything else was working wonderfully.

 

@substorm - interested to hear how you go with Dynax's boot IMG on baremetal.

 

Sent from my SM-G928I using Tapatalk

Link to comment
Share on other sites

I'm having dell 2950, so I don't have vt-d either.

 

I'm using little bit modified ovf from this post. I changed 2nd disk size to 160gb and added one more disk 100gb. During import i did chose thin provisioning and when dsm 1st start then shows disk error, but after creating raid group error been fixed and all is fine now. Modifying other parameters like ram, CPU or Ethernet also is not a problem, vm works fine.

 

viewtopic.php?f=2&t=16114&start=60#p65508

Link to comment
Share on other sites

Good. Try to use BTRFS functionality, and see if it works... :?:

 

The functionality seems to work. I've only tried Hyper backup and Cloud Station ShareSynch....

 

But it's still bugging me why during the baremetal install, the mount command to fix the crash btrfs volume1

$ mount /dev/lg1000/lv/volume1

gives me an error that says it can't find the volume1 in /etc/fstab ???

 

Does anyone know what I did wrong there?

 

TIA.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...