IceBoosteR

Members
  • Content Count

    56
  • Joined

  • Last visited

Community Reputation

3 Neutral

1 Follower

About IceBoosteR

  • Rank
    Regular Member

Recent Profile Visitors

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

  1. 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
  2. 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 intereste
  3. 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.
  4. 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"
  5. 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
  6. - 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
  7. 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!
  8. - 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
  9. - 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
  10. 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
  11. 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.
  12. 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
  13. Welp, haven't seen that. Yeah will defenetly wait. Still, question remains for the future
  14. 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.