• Announcements

    • Polanskiman

      DSM 6.2-23739 - WARNING   05/23/2018

      This is a MAJOR update of DSM. DO NOT UPDATE TO DSM 6.2 with Jun's loader 1.02b or earlier. Your box will be bricked.  You have been warned.   https://www.synology.com/en-global/releaseNote/DS3615xs
    • Polanskiman

      Email server issues - FIXED   06/14/2018

      We have been experiencing email server issues. We are working on it. Bear with us. Thank you. ------------- Problem has been fixed. You might receive duplicate emails. Sorry for that.

TWiST

Members
  • Content count

    40
  • Joined

  • Last visited

Community Reputation

0 Neutral

About TWiST

  • Rank
    Junior Member
  1. Progress of 6.2 loader

    Thank you so much for taking the time to share your info with us!
  2. Progress of 6.2 loader

    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
  3. Progress of 6.2 loader

    Does anyone know where we can donate to @jun for his amazing efforts in keeping this community alive?
  4. DSM 6.1.x Loader

    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.
  5. DSM 6.1.x Loader

    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!
  6. Amazing write-up! Thank you for taking the time to put it together for the community.
  7. DSM 6.1.x Loader

    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!!
  8. DSM 6.1.x Loader

    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!
  9. DSM 6.1.x 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!
  10. DSM 6.1.x Loader

    Has anyone with a LSI 9211-8i controller done an upgrade with the new alpha loader?
  11. DSM 6.1.x Loader

    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.
  12. 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!
  13. 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.
  14. DSM 6.1.x Loader

    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.
  15. 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.