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

ferno

Members
  • Content count

    25
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ferno

  • Rank
    Junior Member
  1. DSM 5.2-5967 Update 2

    Ok since nobody answered i went ahead and did the upgrade. Works fine!
  2. DSM 5.2-5967 Update 2

    Nobody did this update?
  3. DSM 5.2-5967 Update 2

    Hi Everybody, I know for sure this question has been asked before but have been searching through the forum and cant find it so I am just going to ask it again. I have been running DSM 5.2-5967 Update 1 for a while now and am quite content with it, down want to move to DSM 6 just yet especially because there is no working Virtual Box package for DSM 6. So for the 5.2 version I am missing one update the DSM 5.2-5967 Update 2, now I am wondering if I can just safely update to this update though the DSM update feature or if I have to look into a new boot loader en go trough safe PAT downloads to safely update it. Has anybody updated to DSM 5.2-5967 Update 2 from DSM 5.2-5967 Update 1 just from the synology gui without having any issues? I know I am not running the latest boot loader but don't want to change that as it is running rock solid, just want to apply DSM 5.2-5967 Update 2 because of the UPNP security issue it covers. Hopefully someone that did this update wants to share his experience here. Regards and thank in advance! Ferno
  4. DSM 6.1.x Loader

    yes and yes. Don't forget the serial, Id and sata thing in the grub.cfg an the ramdisk copy.
  5. DSM 6.1.x Loader

    Hum, I can't get it installed on my N40L? The loader gets to booting the kernel but the server doesn't show in Synology assistant and no IP address is being assigned by the router. It seems like the nic isn't supported or something? I used the img linked on page 10 and the ramdisk file from page one EFI img (6688 KB), made the grub config changes but no joy. Which model Gen7 did you get it running on? Hi, On the N40L with 8 GB ram. Running fine, even the upgrade to Update 2 worked. Only issue I have eis the shutdown that hangs sometimes and the improper shutdown error in the log. Did you do the serial and id of the usb stick in the grub.cfg thing? That is important too.
  6. DSM 6.1.x Loader

    HI Have it working on a G7. Did not update to update 2 though. Did not do anything special other then using the bare metal mixed boot loader (viewtopic.php?f=2&t=20216&start=90#p73344) and copy of the fixed ramdisk. Will try the upgrade to update 2 shortly an report back Ok, Just did the update to update 2, went fine, the only issue I have is the Server not shutting down properly and the error reporting it after the reboot. Anyone found a fix for that yet?
  7. DSM 6.1.x Loader

    HI Have it working on a G7. Did not update to update 2 though. Did not do anything special other then using the bare metal mixed boot loader (viewtopic.php?f=2&t=20216&start=90#p73344) and copy of the fixed ramdisk. Will try the upgrade to update 2 shortly an report back
  8. DISK Group / Volume keep crashing

    Hi, Have been having this issue also, its driving me crazy as there is no consistency to it. At a certain point I thought I had figured it out and thought the culprit was filling up all 12 bays but after a while my new setup (with only 7 vmdk files) ended up with a crashed volume also.
  9. HP MicroServer Gen8 - ESXi v6 - Disk Errors

    Hi, We have almost the same setup. Do you have the 40 degree celsius bug? That the ILO always show 40 degree Celsius for the CPU temperature? I also have some issues but not the same one you are experiencing. Mine are more related to volumes crashing even though I have had the same setup running in the past without any issues. Mine started when I upgraded to the new xpenoboot but even when I went back still having the same issues. BTW. I use vodka files not RDW. I am now running on a new host (HP ML310e Gen8 v2) and without raid, just a couple of big volumes too see if that stays intact.
  10. Hi, I just spent half a day solving this issue while pulling the few hairs I have left out of my head so I thought to share this. After installing my xpenology on a esxi 6 host everything seemed to go smoothly, but after a while my package center stopped working. For all packages, community kept loading for ages until it timed out en synology packages got the error synology server not available. After searching for hours and trying all the fixes I came across that had some resemblance I finally found it. here: https://xpenology.us/forum/general-disc ... nter-error The time settings on my sinology host, it was set to 2014. After I fixed that an the regional settings in xpenology package center started working fine again. Thought I should share, maybe it helps someone out.
  11. Don't fill all 12 Bays!

    OK, I have tried the expansion to 20 drives, At first I did not manage to get it running, but after some filling I got it running. But same issue, when I use the 20 drives volume crashes and when I leave one drive empty everything works fine. Even though I can live with this situation it seems like there is a real issue with xpenology, at least when using ESX and vmdk's
  12. Don't fill all 12 Bays!

    Hi Good Point, Since I still want to have (SHR)RAID in synology I opted for a smaller size VMDK so I won't loose too much space because of the parity drive. AFAIK, DSM has no awareness of which drives vmdks physically reside on. So, with multiple vmdks per physical drive, I think you're at risk of SHR reporting that it's resilient, when in fact it isn't (because data and parity reside in separate vmdks on the same physical drive) I think that, in this scenario, you need to mirror physical drive topology in the logical topology and have a single vmdk per physical drive. Hi, yes, I am aware of that, I just use the RAID to create a larger volume, and even knowing that since I do not have real redundancy I should opt for no spare drive (raid 0) I thought (and my thought proved right a couple of times) this way ik I somehow mess with one of the vodka's I won't be screwed right away.
  13. Don't fill all 12 Bays!

    Hi Good Point, Since I still want to have (SHR)RAID in synology I opted for a smaller size VMDK so I won't loose too much space because of the parity drive.
  14. Don't fill all 12 Bays!

    How much power does this badboy draw?? Power is one of the things I pay attention to as it runs 24x7. My Proliant server now with 4 3Tb wd Red drives and 16GB ram only draws 59 Watt running ESXi 6, xpenology (with loads of services on it) VM, Vcenter VM and one windows 2012 R2 server core edition. I think that is pretty sweet since my original DS1512+ draw 50 Watt with 5 drives but did not have the punch to transcode several streams in plex and no Hypervisor options.