Jump to content
XPEnology Community

HeyelTeomim

Rookie
  • Posts

    8
  • Joined

  • Last visited

Recent Profile Visitors

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

HeyelTeomim's Achievements

Newbie

Newbie (1/7)

1

Reputation

  1. I guess that the lack of responses qualifies my hunch that this is, at best, a grey area. I'm gonna go for a non-Xpenology solution for the Plex part. Shame, as it would have been nice to limit the number of always-on appliances in the house.
  2. This seems to be a recurring topic. I've read many threads without seeing a clear pattern apart from many unsuccessful attempts including arcane incantations and what not I understand that I need to base on the DS918+ image as HW transcoding is from Haswell generation. But instead of asking "Does my stuff work" I am just going to ask the following: If I want to build an Xpenology server that actually supports Plex HW transcoding (with Plex Pass version) out of the box and I don't want a Celeron CPU - what should I choose? Kaby Lake? Coffee Lake? Or is this just a lost cause on Xpenology and I should look at running Plex on something else (if I need HW transcoding)? Thanks in advance!
  3. @flyride Any advice om CyberPower models? - I've read a couple of reviews that indicate that they have a lot of fan noise, even when they're not recharging.
  4. - Outcome of the update: SUCCESSFUL - DSM version prior update: DSM 6.2.3-25426 - Loader version and model: JUN'S LOADER v1.03b DS3617XS (modified to MBR only) - Using custom extra.lzma: NO - Installation type: BAREMETAL - Intel DQ77KB - 3470 + Intel Core i5-3470T + Samsung mSATA 256GB (MZMTE256HMHP-000L1) - Additional comments: Update via DSM GUI. 10 mins. Reboot required.
  5. I was looking at the list of compatible UPS units over at Synology (https://www.synology.com/en-global/compatibility?search_by=category&category=upses&p=1) but it seems that support (at least listed) for the DS3617XS unit is scarce. I am wondering what dictates this - obviously, the HCL deals with what fits with Synology HW and does not take Xpenology into account - but are there "built-in" limitations in the actual DSM SW that prevent connecting a given UPS and having it work? Or is the lack of entries for DS3617XS simply a matter of not really having tested it? If someone has recommendations on an APC unit that they know works with DS3617XS, don't be shy ;-)
  6. There's a pretty good explanation with visuals here: https://old.idmedia.no/projects/xpenology/adding-more-than-12-hard-drives-to-xpenology/#:~:text=in your browser.-,Adding more than 12 hard drives to XPenology,support 12 disks by default.
  7. @flyride Thank you for your response. I have progressed now and found that the problem was multipronged. But you got me started on the right path, which is what I was asking for - so thank you! Here's the breakdown of what I ended up doing: 1. First off, apologies for confusing the UEFI+CSM. I had not read correctly in the BIOS. It is either UEFI, Legacy or UEFI + Legacy. I have now set to Legacy. 2. This did not solve everything, alas. After some tinkering, I figured out that my BIOS does not take kindly to Legacy + "Boot USB devices first" as well as "Boot from removable media" - so I disabled these last two. Now the only items checked are "Legacy" and "Allow boot from USB" 3. With this, I was able to move on to detecting the DSM if I manually selected the USB stick from the boot menu (intercepting with F10) at POST. However, if I let it try to boot by itself, I got an error stating that there was no bootable device 4. After some rummaging around the forum, I figured out that it might be down to my (quite old) motherboard maybe not being able to boot automatically from a USB stick that used GPT partioning. And there was an .ing file of the 1.02b bootloader in the instructions for these cases. But I needed 1.03b 5. After some more digging, I stumbled across a post from @wimmetje (see inserted link below) where he took the 1.02b MBR image and replaced all of the files with those from the 1.03b loader, which worked for him. 6. So I replicated that, using the 1.02 MBR image, mounted the two FAT partitions and replaced the files with those from the 1.03b loader (modified with PID, VID etc) 7. I was now able to let the computer boot unattended, directly in to the GRUB menu - and after a little while, I could see it in the Synology Assistant. I have since moved on to installing the 6.2.3-25426 PAT file and am exploring this brand new world The DSM even sees my add-on PCIe x1 4-port SATA card (Marvell 9215-based) There is still much to learn, but I am on my way now! Modifying the bootloader MBR image
  8. I am trying to get a baremetal install working on the following hardware: Intel DQ77MK motherboard with 8GB RAM Intel i7-3770 CPU 4x Hitachi 750GB HDD BIOS is set to UEFI+CSM, serial port enabled (that seems to be a thing), AHCI mode on, boot from USB as 1st priority. It boots and I can get to the screen where I am instructed to try and locate the DSM from either find.synology.com or the Synology Assistant. Unfortunately, neither sees anything. And I waited for a long time, periodically checking. If I look at my router log, no IP seems to be assigned. The physical layer is up (I can see from the NIC led on the computer and the switch, blinking green) I'm stuck as I don't really know what to look for. I think it's a networking thing, but the NIC should be supported (Intel 82574L). I browsed for the extra.lzma file but it seems to be for an earlier version of the bootloader + PAT. I'm also not sure this is the right solution. According to this post, it should work OOTB: But it doesn't If anyone can point me in a direction for troubleshooting, I'd be much obliged! What I did: I got the 1.03b loader and the 6.2.3 PAT file here (1st post): I have followed the steps here and manually updated the grub.cfg (I found that using the 'c' option in the grub loader didn't persist the changes for some weird reason): Have double-checked MAC adresses, serial no generated, PID, VID.
×
×
  • Create New...