IceBoosteR

Members
  • Content Count

    47
  • Joined

  • Last visited

Community Reputation

1 Neutral

About IceBoosteR

  • Rank
    Junior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Oh okey thanks. Where are you living? I've seen some post from you in German, so I assume you do live there. I am using a Supermicro mainboard with a Xeon E3-1270v3 used server gear. It is relatively cheap to purchase, 32GB of ECC memory (which I do use in all my servers) and with 4C/8T more then enough power to run DSM and two VMs. Looking into newer models I have not seen any other CPU-Mainboard combination that could hit that cost-to-power (P/L) ratio. Only looking into the AMD side that would make me to switch, but as you mentioned, Intel only for the DSM... I can send you a link to the offer where I bought my CPU, offer is still there. Can send you a PM if you like. Mhh interesting thought! Unfortunate that it would not work in your config - but yeah, not tested yet so some small risk involved. I guess detaching all disks of that array might be the safest option (including a full backup of course) Oh okey, cool stuff. Yeah I read that this is now limited, but on the 918+ model only, right? As to my server-grade-hardware, only the 3615xs loader worked for me out of the box (LSI adapter, Mellanox ConnectX-3 10Gbit and the onboard SATA), the others didn't work. I am also looking to upgrade my main rig to AMD, but I spend more money in the past years on server stuff as to my main rig (still i7 6700K+GTX1070) and thats still powerful enough for me Best, Ice
  2. IceBoosteR

    DSM 6.2 Loader

    BTRFS is all fine to be used on linux if you need to recover. Honestly I would not do this with OMV, AFAIK you cannot just "mount" it in the GUI. You will need to do this on the CMD whatsoever and they I would highly recommend to used a distro like Ubuntu to get this done. Documentation is good, plenty of stuff on the internet and latest kernel and ports avaiable. Just in case something went wrong. Also I would not go on EXT4 nowadays on Synology as BTRFS has good (exlusive) features and is well maintained and updated by Synology.
  3. Really, on 6.1? So I am using the tools and DSM itself heavily and I am really happy with that. As this system is my productive one, I would like to stay at the latest release Anyhow, so @IG-88 are you using a custom synoinfo with edited port config? This is my main concern, to end up with a failed (SHR-2)-RAID array. Keep going on your hardware upgrade - today I just received my 24 Bay rackmount case :LOL: Best, Ice
  4. Welp, haven't seen that. Yeah will defenetly wait. Still, question remains for the future
  5. Okey. Yes of course backup is available but it is always good to have other thoughts if this is really an appropriate way to do it.
  6. Hi everyone, the newest upgrade from Synology arrived (v.6.2.3) and I do plan do update my box (running at v.6.2.2) to that release. Now I have 12 disk in my server in two pools (SHR2 - 10 disks) and (RAID1 - 2 disks) so I had to edit the synoinfo file to reflect my storage controller configuration. That was no issue when I started with the box and only applied minor updates afterwards. While the intermediate update is now and intermediatze one, I suggest they will also patch the synoinfo file. So I need to edit this once again after an successful update. The problem is tho, if I am doing this straight away, my array of 10 disks will not be usable anymore and propably break - as more than 2 disks will become unavailable after reboot. Of course, I want to prevent myself from such a situation. Of course, a backup is available, but honestly, better to not use it,right Some while ago while browsing the forum I found a post from a member who may found a solution for this, but I am unable to find it ... AFAIK he added a spare drive to his system, before performing the update. Then he disconnects all the drives from his pool (on a physical side eg. pulling of the SATA cable) and reboots with only that one drive. Once that is successful he performs all actions needed and reboots the system with all drives connected again. As the system partition from DSM is now out of sync a quick "repair" is required - but after that all is fine. So I wanted to ask you how you're doing these updates. If the above method works, I think I could do it with: 1. Saving the synoinfo file safely 2. Reboot without the SHR2 array connected 3. Perform the update (with only the RAID-1 connected) 4. Edit the synoinfo again 5. Reboot with the SHR2-array connected 6. Rebuild DSM partion 7. Enjoy Any help and/or input is very appreciated THX
  7. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 - Loader version and model: JUN'S LOADER v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - Supermicro X10SLL-F, Intel Xeon E3-1270v3, 32GB ECC RAM - Additional comment: reboot required
  8. Hi, you gave me the correct hint. I was trying to install the full installation from here: https://www.synology.com/de-de/support/download/DS3615xs#firmware I thought that was the correct one. But instead I just need to apply the update which is only 43 MB! Working now. Thank you buddy! -IceBoosteR
  9. Hello guys, I'm running Xpenology currently on a Supermicro X10 with a Xeon E3-1270v3 and 32GB of ECC RAM and I am very happy with that setup. The version I am running (the only on which I was able to install) is the 1.03b loader for the 3615xs. I am running DSM 6.2.2-24922. Now recently there was DSM 6.2.2-24922-4 launched and when I do search for updates the syste msays it is the newest version installed. I assumed this is an error. So I downloaded the .pat file and tried a manual update. It does not start at all. Message is: "The DSM version is not downgradeable. The applied DSM must be newer than the current one". This must also be an error. Anyone experienced this aswell? How can I fix this? IF you need more anwers for the system and/or setup plase let me know. Thank you!
  10. We can close the thread now. I have managed to get it to work. Had to choose the 3615xs version which was now working for me because of magic - CLOSED-
  11. Tried again with different thumb drives, same behaviour. I am pretty sure that it is not VID and PID....
  12. Do have a problem with nested virtualisation now. Would be awesome if someone could point me to the solution of the error 13 for instance. Thx
  13. Did the trick now with ESXi. I am booting from an USB drive ESXi 6.7 and using another drive as USB datastore for the VMDK. Passing through the onboard SATA and one of the NICs and it is working fine. Would be better to have it all baremetal but nevermind...
  14. Update: Installed it on the same thumb drive using ESXI.... But that would break all my config, no dedicated sata controller and so on. An idea would be great.