Jump to content
XPEnology Community

Working DSM 6


oktisme

Recommended Posts

so you are saying that your virtual box installation works flawless and every feature in DSM6 works like it should?

 

Did you ever try to open a shell and take a look at the output of dmesg? No? You should do so, it looks everything else then trustworthy.

Well the intendet use case has no error in dmesg at all.

 

But hey, trust your personal data to an inconsistant os.. It's up to you!

Link to comment
Share on other sites

Hey fine work!

 

I only had a question: do you have a *.IMG (from the *.ISO) for boot from regular hardware without an DVD-ROM Device?

 

Thanks

 

many greets

 

I put the img together and uploaded it here:

 

https://mega.nz/#!w9RkULAR

Updated link w/o key:

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

 

works fine under esxi 5.5. After install the pat 7393 file, you can use the GUI to update to DSM6.0 U1.

 

I wouldn't call this working properly because brtfs doesn't work (everything does).

 

Use Install to Install and Run to Run. You have 30 sec to make a selection.

 

Edit: Sorry, first time using mega, I didn't realize there's a key for sharing. Here's the updated link

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

Edited by Guest
Link to comment
Share on other sites

It does not support VirtualBox, Hyper-V or baremetal system. No network card will be found.

 

 

 

- What does not support virtualbox?

 

https://yadi.sk/i/bcgMvmLJtHcAn

 

You won't be able to use the new file system. it "works" for you because you use a modified xpe boot image which loads the drivers (Install option).

 

If you use the "Run" option, you won't be able to load network driver so the NAS can't connect to your network.

Link to comment
Share on other sites

 

Richard Ferlow wrote:

haydibe wrote:It does not support VirtualBox, Hyper-V or baremetal system. No network card will be found.

- What does not support virtualbox?

https://yadi.sk/i/bcgMvmLJtHcAn

 

You won't be able to use the new file system. it "works" for you because you use a modified xpe boot image which loads the drivers (Install option).

If you use the "Run" option, you won't be able to load network driver so the NAS can't connect to your network.

What is the side effect if we sticking with "Install" option as default boot choice to get the network support? Everything except brtfs will work well?

Any methods to get the network driver work (compiled and integrated) in "Run" mode? I think there is some one claiming to have beta phase DSM6.0 kernel source, can we make benefit of that before Synology releases the complete sources? 

 

 

Posted via Xpenology.us

Link to comment
Share on other sites

 

Richard Ferlow wrote:

haydibe wrote:It does not support VirtualBox, Hyper-V or baremetal system. No network card will be found.

- What does not support virtualbox?

https://yadi.sk/i/bcgMvmLJtHcAn

 

You won't be able to use the new file system. it "works" for you because you use a modified xpe boot image which loads the drivers (Install option).

If you use the "Run" option, you won't be able to load network driver so the NAS can't connect to your network.

What is the side effect if we sticking with "Install" option as default boot choice to get the network support? Everything except brtfs will work well?

Any methods to get the network driver work (compiled and integrated) in "Run" mode? I think there is some one claiming to have beta phase DSM6.0 kernel source, can we make benefit of that before Synology releases the complete sources? 

 

 

Posted via Xpenology.us

Link to comment
Share on other sites

1st time I have seen password request. I D/L the file a week ago and it worked fine. Not sure what to tell you

 

This is a slightly different file for use with ESXi as an image file (img). I didn't know how to properly share in mega. I put in an updated link w/o password.

 

Minor changes such as extending the menu wait time, let DSM loads with both Run or Install options, first HDD starts at HD 1 etc.

 

btrfs still won't work until the source code is release for proper recompile/built. Update via the web GUI to DSM 6U1 works fine (with my very limited testing on my ESXi 5.5 -- convert the img to vmdk file first).

Link to comment
Share on other sites

I use ESXI 6 and btrfs works fine for me. My setup is under test since 14 days. I just have mount a small virtual drive. I wait more time before moving my Raid1 from DSM5.2 to DSM6 but to me it looks really good !

 

Can you post your boot vmdk file?

 

Thanks

Link to comment
Share on other sites

I tested your vmdk in vmware and works pretty fine, thank guys!

 

but i would like to use it on KVM (because I use unraid as a backend I prefer this storage system more than typical mdadm raid) and share volumes over NFS

 

Anyone know how can I install it on KVM?

Link to comment
Share on other sites

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

Link to comment
Share on other sites

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.

 

So you mentioned about the ISO (I believe you mean the boot image?), is it inside the VM image? Can you split it out because I am planning to use bare metal to test.

Link to comment
Share on other sites

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

 

so far so good! The official e1000e driver, support your NIC, intel 82567LM.

I tried one 82574L (id 8086-10D3), no lucky :cry:

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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