Jump to content
XPEnology Community

htc2010

Member
  • Posts

    42
  • Joined

  • Last visited

Everything posted by htc2010

  1. I recently plugged in an APC BR1000G UPS into my Xpenology box but find that Xpenology does not detect the UPS. Is there a compatibility list for UPS units or shouldn't they all be universal within their brand? Plugged in via USB. Thoughts?
  2. Does anyone know of a mod pack for DNSCrypt for Synology/Xpenology? I like the option to be able to use it as a DNS server for internal use, but would love to take it a step further and apply an encryption wrapper on top for use in general.
  3. I had this issue when using an external graphics card. So long as you are using the onboard, it should be fine. On a bare-metal install, once you've selected the "upgrade/install" option, you should see a whole mess of command lines pop up, and then stop at "Disk Station Login" at which point you should be able to use the Synology assistant to detect the device and install through your PC's web browser.
  4. I have a mix of video formats on my DS but am really frustrated at how poorly the DS Photo App and Media Server handle video. I know a lot of people have the same issue and many have tried all sorts of fixes, but there does not seem to be a cure-all for compatibility. But overall, I'm trying to understand what the difference is between using the DS Photo Station web portal to view video and using the Photo Station App? I noticed that when using the web portal, pretty much most if not all videos play without issue. but on the DS Photo App, most don't. And on DLNA, it's somewhere in between in terms of compatibility. In my setup: 1) Media indexing is enabled, in the correct folders 2) Mobile Playback is enabled 3) Photo Station & Media Server packages are installed Does anyone have specific experience with this and a general recommendation on a compatible video format that is good for DS Photo use?
  5. AH, I see, thank you! It just seemed odd how the periodicity of this error is so consistent! On my 411j, it was literally 1 disk always having 1 reconnect, every single month. It was so normal an occurence that I thought it was normal for disk 1 to behave this way! I will keep an eye on the disk and see how it goes. Thank you.
  6. For my particular upgrade from Update 3 to 4, I had no issue at all and did not even need to reboot to get my volumes remounted. However, for upgrades in general, I noticed that if you reboot and select migrate/upgrade right when Xpenoboot begins, and then run the Update patch from within DSM, the update seems to install much smoother without any issue. When running the patch in a standard boot, I notice a system hang and then require a hard reboot.
  7. Each month, my Xpenology box sends me an email laying out hard drive health. There is one attribute that I am unsure of: Drive Reconnect Count <---- Bad Sector Count Disk Re-Identification Count What exactly does a drive reconnect count indicate?
  8. Did any system services have to be manually restarted like with update 3? e.g., media server, ups service, re-mount volumes, etc etc etc?
  9. Unless you absolutely need the storage space, avoid using JBOD and use a RAID array since this is exactly what the NAS is for. As you add more drives, Synology's disk manager can add and expand the array as needed. It's a very straight forward process once you get there. RAID1 at a minimum, RAID5 if there are not enough drives available and space is a premium, or RAID10 if you just want performance and don't have a terribly large amount of data to handle.
  10. Yes, I can confirm that update 3 works. Just reboot into upgrade/migrate mode, run the updater from control panel. I let the system download it directly and update it and reboot the first time. Confirmed, first reboot, volumes are missing. Reboot again and volumes come back. Per YoungHo, gotta re-enable user home service as well as re-run the media indexing function. So far, these services need to be manually restarted, even after the 2nd reboot: 1. User Home Service 2. Media Indexing 3. Log Center 4. Backup Service I have a bare-metal install with no apps other than default so I'm not sure what else might be effected. Can anyone confirm any other system services/apps that needed a manual stop/start to get back going after update 3 installation? Add your comments here!
  11. Does this update pathway apply to update 3? I just got my Xpenology box setup last night, got up to patch 2 and realized that 5592 patch 2 is already up to patch 3 when looking at the update manager in the control panel. Is it safe to download this patch directly from Synology and perform a manual update or should I wait until that patch is released on xpenology.me? Thanks in advance!
  12. I have my Xpenology box running and I can now confirm some of these details that I was inquiring about over the past day. And Diverge, thank you for that detail. Based on what I just did with my server, that is exactly what happens. Originally, I had DSM installed directly onto my SATA DoM without any other drives attached. Then I added the RAID array separately. Once I got it all working, I converted the SATA DOM into an SSD cache drive, which required it to be wiped. In doing so, the device went into degraded mode right away, rebooted, and repaired itself, using the installed copies on the other drives. Extremely good fail safe, I'm loving it. So yes, using an SSD really makes no difference in terms of storage performance. It's all installed into every drive anyway. However, having an SSD attached for an iSCSI drive attached as a cache drive will be a nice way to push things over the edge!
  13. All the parts came and I finished assembling. Now I GET IT. So for everyone else who came into the same situation as myself: the reason that you MUST use a USB stick is that the installer for DS installs itself in a psuedo-RAID fashion across all physical disks as part of its scripted installer. It does not overwrite USB. By booting from my DOM and attempting to install DS, it would be attempting to install to every physical drive, effectively installing OVER the bootloader and rendering the device unbootable. I see where Cyanlab's mod comes in, which allows you to get this working without a USB stick! So what I ultimately did is this ... Unplug all HDD's except the DOM. This forces DS to install directly to the DOM, effectively putting the OS on a separate, standalone drive. Then after updating and configuring, plug in the HDD array. In reality, I have a feeling that DS will install itself over to the array anyway as a failsafe, but that's kind of an under the hood thing that I'm not privy to. So far, so good. Update 2 installed perfectly. Does anyone have any insight on how DS installs itself from drive to drive?
  14. Thank you for that link! Converting a QNAP device to Synology ... QNAP engineers should have a heart attack seeing that, LOL. Thank you for the link. I'm anxiously awaiting all my pieces arriving today ... Got my motherboard, PCIe SATA controller, and case. Just waiting on the drives today. Will be mounting 3x500GB 2.5" drives into this tiny little 65 watt Antec ISK 300 case.
  15. superb ... I'm actually coming from a strictly no-linux background. I'm going to use a cloning utility to dump my 16GB bootable USB to my 16GB DOM module. That part'll be easy ... The last of my components are coming today - can't wait!
  16. Thanks for clarifying. It does basically answer my question that it will work, albeit in a roundabout way as I mentioned in the OP. It's really just about aesthetics. I have a cheapy USB flash drive but don't like it sticking out of the system. Too easy to get knocked out, thus the reason I want to either put the bootloader onto the SATA DoM inside the chassis. Alternatively, I could also boot from a USB stick, do the initial install to the DoM, and then add the HDD's after. This, I assume, will put the DS OS directly onto the SSD device and use the RAID array for storage, as opposed to being installed onto the array directly, correct?
  17. Is there a specific reason why the boot images must be run from a USB stick or LiveCD? Other than the obvious need to have a quick way to update boot images or OS images, is there any other technical reason why the boot image has to be on a stick? I have a SATA DoM I want to use for this purpose and was wondering if XPenology would still install if I (1) cloned a USB to the SATA disk-on-module,(2) set the SATA DoM as boot drive, and (3) installed the OS using the standard installer from tutorials, and (4) created my RAID5 array using the 3 hard drives attached to a PCIe SATA III controller card? Similarly, I notice that other NAS distros do allow you to specifically install to a standalone drive in the server if available or allow an install to another USB stick. I just don't see that option available with XPenology. Alternatively, I was hoping to "force" the installation to go onto the disk-on-module by using a standard install procedure using a USB stick, and then attaching my RAID array separately, to get the added benefit of a standalone install on an SSD. Has anyone tried either instance? Lastly, I am aware that installing XPenology using either method yields very minimal performance benefits; I'm just curious to know if it's possible as a strictly academic exercise - that and my need to just use up the spare parts I have sitting around. Many Thanks in Advance! PS: Yes, I have seen the Cyanlabs tutorial on installing without a USB stick. However, that method seems outdated using DSM 5.0. I would like to attempt the above with DSM 5.2.
×
×
  • Create New...