TWiST
-
Posts
46 -
Joined
-
Last visited
Posts posted by TWiST
-
-
3 hours ago, turbo21psi said:
1.03a2 seems to be working just fine on Supermicro X10SLM+-F with E3-1220v3. Motherboard has 2 NIC ports and both are detected, LACP bond working. No additional sata or nic card, just onboard for now. USB 3.0 ports work fine, was able to get over 100mbps transfer rate.
Videostation doesn't seem to work for some files, is that the transcoding issue? I don't really intend on using that app, but I thought I'd test it. DSM doesn't crash though, just some videos will not play.
So far it seems pretty good to me. Only have it up for a few hours but no random crashes or anything. Most of the things I tried are working. Plex, AD integration, NIC Bonding.
I only have 1 spare disk for testing so I haven't tried making RAID arrays yet.
Anything other things I should be testing? I'm open for suggestions.
Did you test to see if Plex server transcoding was working? I can understand transcoding not working for Synology's built in apps, but having it not work for Plex would be an issue.
-
No problem, it is people like you that make Synology lock down there systems and make it more difficult for us because you take advantage of there services they provide for paying customers. It is very easy to be able to get your own DDNS service for free, as well as the other services Synology offers. Why take advantage and ruin it for everyone?
-
No, buy Synology to have a valid serial, otherwise you don't get to take advantage of some of there services. I think that is a fair trade off for us to be able to build our own custom systems using Xpenology.
-
I am pretty sure if you buy one, it will come with a valid serial number.
-
Huge thanks to @IG-88 for packaging the 9211 drivers! I have 2 of those cards I use for my array, but I am currently using a 2600k CPU, so it looks like it will be time to upgrade. I will do some testing with my current array disconnected and see how it all pans out and let everyone know the results.
-
58 minutes ago, stefauresi said:
I have 1 x PERC H310 cross flashed to LSI-9211-8i IT Mode but not recognized by DSM (no driver in loader 1.03a2....)
I use 2 x 8Tb , 3 x 6Tb and 1 x SSD 850 Pro 256Gb ( Motherboard Sata controller )
I roll back to DS916+ 6.1.7 for HW transcoding (activation ok but no HW in Video station or Plex)
Thank you so much for taking the time to share your info with us!
-
15 hours ago, stefauresi said:
Hi,
I migrated successfully bare metal 6.1.7 (DS3617xs) to 6.2 (DS918+)
I am curious how many drives you have in a volume and how many volumes.
My Specs for reference
P8Z68-V/GEN3 Motherboard
i7-2600k CPU @ 3.4Ghz
16GB RAM
2 x PERC H310 crossflashed to LSI-9211-8i IT Mode
7 x 3TB WD Red
4 x 4TB WD Red
All in a Rosewill 4U 15 bay chassis.
Currently on the 1.01 loader with DSM 6.1.7-15284
-
Does anyone know where we can donate to @jun for his amazing efforts in keeping this community alive?
-
Any news on stable 6.1 Jun?
Many thanks!
You can check my post from March 12th 2017 where I commented during and after my upgrade and I have been having zero issues since. I run Plex, docker containers with several programs, and have 7 x 3TB drives in 1 array and another 3 x drives 2TB drives in a separate array. So I would say Alpha is running just fine.
I have not followed up much since I read that the source code was released. If it really was released, then I would imagine there are people working on something shinier as we speak.
-
sorry for reply later.
to access the primary Synology partition, first manul build the /dev/md0 array device
mdadm --build /dev/md0 --level=1 --raid-devices=NUMOFHDDS /dev/sda1 /dev/sdX1...
I was able to get myself all squared away, even with the time change against me haha. But I really appreciate you responding to my question, thanks you!
-
Amazing write-up!
Thank you for taking the time to put it together for the community.
-
I found this post in here by jun in response to a question about mounting the primary partitions.
jun wrote:
DSM seems by default create system raid arrary with big endian metadata, and normally x86 devices use little endian metadata on these arrays
so /dev/md0 can not be auto detected by normal linux distributions, unless you could find a big endian linux box
But linux hackers are kind enough to provide some obscure command line options to make peoples life easier.
you can use follow command to exam foreign endian arrary members
mdadm -Ee0.swap /dev/sda1
and use follow command to assemble an arrary and fix byte order in one go
mdadm -AU byteorder /dev/md0 /dev/sda1 /dev/sdb1 ...
DSM will convert it back to its preferred endian on next boot, so no further action requried.
I attempted the commands and got some mixed results, but no mounted drives, I have 7 drives in this array.
sudo mdadm -AU byteorder /dev/md0 /dev/sda1 /dev/sdb1
mdadm: /dev/md0 assembled from 2 drives, need 7 to start --run to insist
Now I thought that might be incorrect so next I ran it with all 7
sudo mdadm -AU byteorder /dev/md0 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1 /dev/sdf1 /dev/sdg1
mdadm: no super block found on /dev/sda1 (expected magic a92349b, got f987efd4)
Then I just got the same error trying the first command and decided to reboot and here I am haha.
***Update
after the reboot I was still getting the magic number error command and I ran
mdadm -A -s
AND BOOM! It loaded BOTH partitions! Time to make some changes and see if the lib/modules cp fixes my box as well.
***Update 2
When I put my USB flash for jun loader back in it booted me up and prompted me to reinstall synology and then said it was formatting the system partition and what not and has now rebooted again and now I am setting it up from scratch it looks like, setting the device name, username, etc etc.
Now that I have completed the setup, I see that my important data is still intact, but all of my Synology config is lost, which I can live with!!
-
boot your nas with linux livecd, build /dev/md0 , and copy all files in /lib/modules/update to /lib/modules.
it's working for me.
Hi,this week end i migrated my baremetal microserver g8 from DSM 6.0xx update 9 to the last DSM 6.1 u1 with jun 1.02 alpha bootloader.
BUT, migrate option was ok, but after a reboot, no network interface ! i was connected on ilo (or VSP) and i don't have login prompt (since DSM 6!). the user EMA had the same problem, and he has connected via VSP to copy network library to the good directory. but me i can't !
How can i have the login prompt (like under dsm 5?)
For information, as i can't migrate (
) i reinstall dsm (2nd option) and network is ok, and DSM 6.1 u1 is ok on my g8. AND I DON'T LOOSE MY DATA !!! (only my apps/configuration )Quick question for ya @plutoGhost I am booting with Ubuntu and mdadm -A -s and got my array built and accessible, but I am only able to see my storage data partition, not the primary Synology partition? How can I mount the other partition on the array with the lib/modules folder?
Thanks!
-
Has anyone with a LSI 9211-8i controller done an upgrade with the new alpha loader?
I have this LSI controller.
The new loader is able to load but after DSM install, it is not responsive to any power commands via DSM web GUI, eg. Shutdown or restart.
Anyone else experiencing power issues?
I am also using the 9211-8i and it works flawlessly with both of the latest loaders. The disk order makes no sense, but I can live with that. Shutdown / reboot works fine as well.
I really appreciate you guys getting back to me about your own personal experiences. I will probably go ahead and upgrade this week and let you guys know how it goes.
Thanks!
-
Has anyone with a LSI 9211-8i controller done an upgrade with the new alpha loader?
-
I was lucky to downgrade from 6.1 to 6.0 U9. It is not so hard as it seems. Maybe tomorrow I'll provide a guide, but now I'm falling asleep.
Yes please do enlighten us on your procedure as I am getting the uneasy feeling that many people will start updating to 6.1 and then start crying like babies.
I am currently advising this method viewtopic.php?f=2&t=13288 by adapting the version numbers but since I haven't tried it myself I can vouch for that.
And if they do, they only have themselves to blame. I got no sympathy for 90% of the lazy community here that cannot even be bother to make a cursory Google search for ANYTHING.
-
I have a dream that one day even the Hyper-V option, a much hated and disregarded hypervisor, greatly improved over the years, will be made available to the DSM users around the world.
Did you try to convert the VMware image to Hyper-V and give it a try? I have had a ton of different VMware images ive converted and worked fine, always worth a shot in the name of SCIENCE!
-
so yeah why people insist on something that is broken is beyond me, i'm running jun's loader on bare metal on asrock with quad i210, xeon e3 32gb ecc and 8 x 3tb WD red and M1015 on HBA, my point (besides bragging a little haha) is that with a bit of effort everything pretty much works with jun's loader, yes it will be nice when 2.3 is release and we gain further ability to run a wider range of hardware but until then your best bet is jun's loader
I am right with ya man, system has been running fantastic!
My Specs for reference
P8Z68-V/GEN3 Motherboard
i7-2600k CPU @ 3.4Ghz
16GB RAM
2 x PERC H310 crossflashed to LSI-9211-8i IT Mode
7 x WD Red 3TB
All in a Rosewill 4U 15 bay chassis.
-
Just wanted to share some information with the 3 people that will actually bother to search this thread lol.
I needed a couple more networking ports for my bare metal install and ordered this dual port card off of Amazon and it was detected right away using 1.01 loader.
So if anyone needs a dual port Intel NIC i350, this one works great right out of the box!
Did you do anything else to get it working? I have an I354 motherboard with that doesn't work even though they typically use the same drivers.
No sir, it was just plug and play, I did not even have to edit the MAC address in the loader nor make any changes to it at all.
-
I thought I would go out on a limb and see if anybody has tried to use Virtual DSM manager with DSM6 under Jun 1.01 loader on bare metal. I was originally trying this so I could have a Virtual DSM of DSM 6.1 and mess with the new Samba AD DC packages, but once I kept messing with it I have found I am unable to get anything to run under Virtual DSM Manager.
I am able to load and create an image, but when i try to start it I get a failed to load error, then if I try to delete it, it fails to delete and if I attempt to remove the cluster it fails as well. I did find a way thru the CLI to break the cluster and thus forcing delete of everything it created, but it does not delete the data on the volume you have to do that manually from the @Repository dir.
If anyone else decides to have a go with this, the command I used to break the cluster so it can be removed is in this folder;
/volume1/@appstore/Virtualization/bin
./etcdctl member list
and then remove it.
-
Just wanted to share some information with the 3 people that will actually bother to search this thread lol.
I needed a couple more networking ports for my bare metal install and ordered this dual port card off of Amazon and it was detected right away using 1.01 loader.
So if anyone needs a dual port Intel NIC i350, this one works great right out of the box!
-
Any of you guys continue to work on this past the August posts? I just learned of this coming with DSM 6.1 and now that we have DSM 6 I thought I might try to get it running in Docker since Docker 5.2 was a bit neutered.
Some info I found that may help;
https://wiki.samba.org/index.php/Settin ... Controller
-
Have you guys seen this about the 6.1 Beta, it sounds more like locking it down more, then keeping things "secure" lol.
"Package Center auto-repair: If some packages become broken after a DSM upgrade and require an update, DSM can now automatically fix them during the upgrade to ensure the entire process is smooth.
DSM code sign: Much like your phone is able to block applications from untrusted sources, your Synology NAS can also block DSM patches that don't match the right sign code, adding an extra layer of security to your stored data.
SMB 4.4 upgrade for sparse file support, saving space while archiving image files of virtual machines."
One thing that does look awesome though is the Samba 4.4 AD-DC, that is going to be a game changer for small business, I am actually looking to try to install Samba inside of Docker in DSM 6 to see if I can get that functionality now, obviously minus there new GUI for it.
I did find a post here from August of some people trying to get this working as well, maybe I can revive it heh.
Also on bare metal using Jun 1.01 Update 4 installed without an issue.
-
i updated also succesfully my n54l to dsm 6 update 2 with no problem changed the vid / pid and sn and mac but quick connect no longer works and the sn and mac is correct.
i used http://quickconnector.orgfree.com/index.php
any sugestions ?
Yes, set-up a domain here > https://www.changeip.com/accounts/cart. ... roduct&i=0 and install the ddns updater 2 package. Configure the domain and port forwarding job done.
thats not was i was asking about i know i can set it up on no ip aswell but i like the futures working like an original synology.You asked for a suggestion and he gave you one. The least you could do is give him a thanks.
If you like all features to work like in an original Synology then I recommend you buy an original Synology product. By using QC you are raping Synology services which is normally exclusively intended for its customers. In fact it's a bad idea to use QC on an XPenology box as it gives a bad reputation to this project.
Took the words right out of my mouth. I already got my system all upgraded to 6 using v1.01 and am happy as a clam (are clams that happy?), but I still read all the new posts in this thread every couple days and most of the people that come in here looking for help are brutal.
Progress of 6.2 loader
in Developer Discussion Room
Posted
Awesome testing, thanks so much!