Jump to content
XPEnology Community


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

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

IceBoosteR's Achievements

Regular Member

Regular Member (3/7)



  1. Abolsutely interesting video. I was just about to get my hands down on a ds920+ and migrate my data to hot (DS920+) and archive data (Unraid) which is currently a single host on Xpenology. But the migration would be a nightmare, and the option to run DSM in ESXi would be awesome (natively). However I guess they will check of a valid license, because they mentioned it is just for a migration/backup intention, so could be an issue for assigning more disks etc. They strongly mentioned the Synology Ecosystem....
  2. Hey there, today was an interesting day. I finally got all parts together and decided to upgrade my server to support more drives. 5 hours later, and two heart attacks, I finally got everything running. But lets start from the beginning. (I am not mentioning my self-made problems of updating my BIOS which I shared here (3 posts total): So I ahave currently 10 disk plus two SSDs in my setup and want to expand my storage. Case has 24 hot-swap ports, so all fine. Already have 6 (4 usable via SAS cable atm) internal ports and am using an LSI SAS 9220-8i for 8 more ports. Of course my synoinfo file was adjusted to handle 12/14 drives. Now I bought another controller, LSI SAS 9300-8i which can also handle 8 ports. Good news is, DSM support SAS2 and SAS3 (but obviously I am using SATA6Gb/s) natively. Now I had to adjust my synoinfo to allow myself the 22 ports I need. So I thought I would be smart, obviously that one did not work out well I am using the 3615xs with 1.03b Default Synology configuration: esataportcfg="0xff000" internalportcfg="0xfff" usbportcfg="0x300000" maxdisks="12" config I had working with my one SAS controller: internalportcfg="0x3fff" usbportcfg="0x300000" esataportcfg="0xfc000" maxdisks="14" Now I thought, well lets add these 22 drives I can use total (8+8+6) but I still wanted to be able to mount USB drives, you newer know. I found online that one guy was able to use 48 hard drives, so I assumed this worked. Used a hex to binary editor and wanted to have the following 22 disks, 0 esata, 2 usb esataportcfg="0x0" internalportcfg="0xfffff" usbportcfg="0xc00000" maxdisks="22" WARNING: That did not work! So what happend? I think either I messed up with the configuration, or the system/DMS is not able to handle so many disks. Either way, because I thought I could not harm anything, 'cause I just added the support for more drives, I saved and rebooted. MEEEEP So system came online and just saw four disks, those on the internal controller. That were both SSD (in one pool; healthy) and two disks from my second Storage Pool (10 disks, SHR2). System state CRITICAL, Volume crashed. All apps - gone! Oh well. So I hoped that the system were unable to mount the volume, but was just performing read-only operations on it. The other part of me hoped, as 2 out of 10 were there, that in worst case if I bring the rest online, I could repair the array. Needless to say I have made a full backup before, but my pulse was anyhow over 120 xD One other thing that worried me was the fact that synology might use internal "System Change numbers/sequeces" like databases do - to identify the status of a volume. More to that later. I did some reseach online and foudn this page: https://zective.com/code/xpenology/ (Note I do not own that site or have anything to do with it - and it Chinese!) Google was my friend so I inserted the defaults on top - and it showed me that my maximum seems to be 22 disks. So I inserted what I needed, screwed over esata and USB and gone full internal ports. Configuration as follow: 22 disks, 0 esata, 0 usb esataportcfg="0x0" internalportcfg="0x3fffff" usbportcfg="0x0" maxdisks="22" Aaaand I rebooted. System came back online, now showing 22 available disks. SSD was still healthy and my SHR2 pool was back in the GAME! Man I felt happy. So I assume the following happend: - every disk has a small piece for the DSM system on it - there is a sequence number stored to save the "latest status" - when trying to mount the volume/bring the array online with just two than 10 disks, it failed, and the disks were not touched - once the needed number of drives came back online (8+) the array gets mounted, data was there and not touched - System partitions on all these 10 drives were out of sync and showed amber. Had to click "repair" in storage overview, and DSM applied the increments from the intact SSDs (latest status/sequence) to all the drives - Synology services were all offline, had to restart them all manually So far so good! Not seeing any issue with the services in general, snapshots are there, but config for the next snapshots were gone. Nevermind, easy to recreate them. I am now running a full scrub on the pool, just checking for errors. I will also verify the file integrity for my super critical files with a 1:1 check, but thats more for me to sleep better. TLDR; doing "serverstuff" can be exiting and is sometimes replacing a good old coffee. Thanks everyone who has made it to the end! -IceBoosteR
  3. IceBoosteR

    DSM 6.2 Loader

    Sorry, yes, was kinda in hurry... Anyway - you are right, I am using DS3615xs with loader 1.03b Actually I know that page, but accidently overlooked the boot method. I am doing so much with computers and servers that I have not well thought about this - as monstly the boot option is UEFI these days. Glad that I could figure it out and Supermicro is providing a very good upgrade/downgrade path. Thanks to the Internet Archive I now also have a recovery BIOS version, just in case. 1.04b 918+ was not working on my Supermicro. For reference on this thread, if someone is interested, setup is: Intel Xeon E3-1270v3 32GB ECC RAM Supermicro X10SLL-F LSI SAS9300-8i and LSI SAS9220-8i TLDR; Layer 8 aka user problem
  4. IceBoosteR

    DSM 6.2 Loader

    Update on my issue: Reverted back to V3.2 thanks to the https://archive.org/donate/ Issue is the same. I am assuming it's because I selected UEFI:MyUSBDrive in the bootorder as the first one. Could get the system now to boot with selecting the non-UEFI version. Will flash again to V3.3. and try again. Edit: Good news, it was NOT the actual BIOS update causing the problem. I am now back at V3.3 and imagine that, choosing the normal option to boot from USB instead of the UEFI one fixed it! So TIL, do not use (U)EFI mode on DSM/Xpenology.
  5. IceBoosteR

    DSM 6.2 Loader

    Hey there, made a BIOS update from V3.2 to V3.3 on my Supermicro X10SLL-F. Unfortunately I am now having an issue on my production box, I got stucked at booting DSM, lloks like a grub issue: "Trying to terminate EFI services again" Anyone has an idea how to get this fixed? will update anyway here if I found a way! BTW: Release notes here: https://www.supermicro.com/about/policies/disclaimer.cfm?SoftwareItemID=11734&type=releasenote "Reinstall Boot option did not work either"
  6. Finally did the upgrade. Man I swear I will not do this again! I lost the /etc.defaults/synoinfo.conf entirely, which means Synology replaced it with the default. That causes two disks of my SHR-2 to be out of the array, so pool is degraded. I managed to recover everything so disks are back visible (and not esata disks) but the whole procedure is something I do not recommend. Running completely without redundancy is dangerous, and I have seen no other way to recover the file before the system wents online and see, that two disks are missing. Now the server is shut down as tomorrow electricians want to do some work. I will not risks anything while rebuilding, so I will wait until they finieshed their work. Gladly I did a full backup. Bottom line I did forget about that issue before I did the upgrade, so I also did not pull out the disks before or something. Luckily the update went fine, and now I am hoping the best (fingers crossed). Will do a byte-by-byte-check after the rebuild to make sure everything is fine....
  7. - Outcome of the update: SUCCESFULL - DSM version prior update: DSM 6.2.3-25426 - Loader version and model: JUN'S LOADER v1.03b DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - Supermicro X10SLL-F, 32GB ECC RAM, Xeon E3-1270v3, 10GBit NIC Mellanox ConnectX-3, LSI SAS2008 IT-Mode - Additional comment: Reboot required, custom synoinfo
  8. Thank you for the script! I had the issue that my config was changed back to the defaults, which caused a degraded array (8 of 10 disks only visible). However, I have used that script before figuring out that the config was not up to date, and I guess your script did part of the job Now its working and I can start to repair my array. Thanks for your work!
  9. - Outcome of the update: SUCCESFULL - DSM version prior update: DSM 6.2.2-24922- update 6 - Loader version and model: JUN'S LOADER v1.03b DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - Supermicro X10SLL-F, 32GB ECC RAM, Xeon E3-1270v3, 10GBit NIC Mellanox ConnectX-3, LSI SAS2008 IT-Mode - Additional comment: Reboot required, custom synoinfo, RAID degraded. I have 14 disks, all in SHR2. When rebooted after upgrade, default was back to 12 so my array was degraded! Be cautious! Had to change synoinfo and use fixsynology.sh
  10. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922- update 4 - Loader version and model: JUN'S LOADER v1.03b DS3615xs - Using custom extra.lzma: NO - Installation type: BAREMETAL - Supermicro X10SLL-F, 32GB ECC RAM, Xeon E3-1270v3, 10GBit NIC Mellanox ConnectX-3, LSI SAS2008 IT-Mode - Additional comment: Reboot required, custom synoinfo
  11. 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
  12. 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.
  13. 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
  14. Welp, haven't seen that. Yeah will defenetly wait. Still, question remains for the future
  15. 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.
  • Create New...